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ś -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
