From: "Łukasz Oleś" <lukaszoles@gmail.com>
To: Colin Watson <cjwatson@ubuntu.com>
Cc: Thomas Schmidt <tschmidt@debian.org>,
606719@bugs.debian.org, debian-release@lists.debian.org,
grub-devel@gnu.org
Subject: Re: Bug#606719: "Normal" kernel being before the Xen hypervisor in Squeeze
Date: Thu, 30 Dec 2010 19:25:06 +0100 [thread overview]
Message-ID: <201012301925.07473.lukaszoles@gmail.com> (raw)
In-Reply-To: <20101219114715.GZ12396@riva.ucam.org>
Hello,
On Sunday 19 December 2010 12:47:15 Colin Watson wrote:
> On Sun, Dec 12, 2010 at 11:48:56AM +0100, Thomas Schmidt wrote:
> > Am Sonntag, den 12.12.2010, 14:18 +0800 schrieb Thomas Goirand:
> > > For me, it's a grave regression that can put a production environment
> > > into big troubles, and it would deserved a RC for me, but because:
> > > - of Julien's opinion
> > > - that the RT should have the final word
> > > - that I respect this view
> > > - that delaying Squeeze just for this might not be a good idea
> > > - not everyone really cares much about Xen in Debian
> > >
> > > ... then I sent my report as a wishlist as requested.
> >
> > I also agree that this needs to be resolved before the release and in my
> > opinion this bugs severity should be at least important, if not critical
> > because it will "break" Xen dom0 functionality of existing systems when
> > they are upgraded from Lenny to Squeeze.
> >
> > Of course this could be "fixed" by the user of the package by selecting
> > an appropriate GRUB_DEFAULT value, but this is likely to break if new
> > kernel versions are installed.
> >
> > The appropriate fix is very simple, just rename /etc/grub.d/20_linux_xen
> > to /etc/grub.d/09_linux_xen or some other number in the range of 06-09.
>
> I'd prefer this to be decided upstream. What do people on grub-devel
> think? It does make some sense that the default should be to use Xen if
> it's present, IMO.
>
> (See http://bugs.debian.org/606719 for the full history of this bug.)
Any update on this? I have also run into this issue
Regards,
--
Łukasz Oleś
prev parent reply other threads:[~2010-12-30 18:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4D025316.4090300@debian.org>
[not found] ` <20101210164002.GK2287@patate.is-a-geek.org>
[not found] ` <20101211165102.GB7399@lupin.powdarrmonkey.net>
[not found] ` <20101211170316.GN5063@radis.liafa.jussieu.fr>
[not found] ` <4D04694F.5050706@debian.org>
[not found] ` <1292150936.3881.15.camel@s710.lan>
2010-12-19 11:47 ` Bug#606719: "Normal" kernel being before the Xen hypervisor in Squeeze Colin Watson
2010-12-30 18:25 ` Łukasz Oleś [this message]
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=201012301925.07473.lukaszoles@gmail.com \
--to=lukaszoles@gmail.com \
--cc=606719@bugs.debian.org \
--cc=cjwatson@ubuntu.com \
--cc=debian-release@lists.debian.org \
--cc=grub-devel@gnu.org \
--cc=tschmidt@debian.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).