All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Burns <xen.lists@burns.me.uk>
To: xen-devel@lists.xensource.com
Subject: Re: Re: F16, yum install xen, run grub2 or grubby as needed?
Date: Sun, 18 Sep 2011 20:53:29 +0100	[thread overview]
Message-ID: <CAE1-PRcO=7dBYxwJCq0L0Q6qcT=Nbnf4d2Sg3f=780MRxpKOaw@mail.gmail.com> (raw)
In-Reply-To: <20110916083533.GC884@phenom.oracle.com>

On 16 September 2011 09:35, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:

> On Thu, Sep 15, 2011 at 10:29:50PM +0100, M A Young wrote:
>> On Thu, 15 Sep 2011, Konrad Rzeszutek Wilk wrote:
>>
>>> realized that I had to manually do:
>>> grub2-mkconfig > /boot/grub2/grub.cfg

Yes, I've been manually running that too, but the resuling grub.cfg
file from when I manually regenerate it is subtly different from the
grub.cfg generated after automatically installing a new kernel ...

The one generated by manually running grub2-mkconfig creates a Xen
submenu with all the various kernels under it, whereas after
installing a new kernel, the one generated has all the xen + kernels
in the top level menu.

>> grub2 creates a
>> set of entries for each of xen-4.1.1.gz and its two symbolic links
>> xen-4.1.gz and xen.gz which is a bit untidy, so perhaps it makes
>> sense to remove the symbolic links.

I've submitted a bug with a patch to make the /etc/20_linux_xen helper
script ignore the symbol files and symbolic links, if there's no need
for the symbolic links the patch could be even simpler.

https://bugzilla.redhat.com/show_bug.cgi?id=738085

  reply	other threads:[~2011-09-18 19:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-15 15:46 F16, yum install xen, run grub2 or grubby as needed? Konrad Rzeszutek Wilk
2011-09-15 21:29 ` M A Young
2011-09-16  8:35   ` Konrad Rzeszutek Wilk
2011-09-18 19:53     ` Andy Burns [this message]
2011-09-21 18:08       ` Konrad Rzeszutek Wilk
2011-09-22  1:16         ` Andy Burns
2011-09-22  1:28         ` Andy Burns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAE1-PRcO=7dBYxwJCq0L0Q6qcT=Nbnf4d2Sg3f=780MRxpKOaw@mail.gmail.com' \
    --to=xen.lists@burns.me.uk \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.