On Thu, 2010-05-06 at 04:54 +0800, jidanni@jidanni.org wrote: > Package: linux-base > Version: 2.6.33-1~experimental.4 > Severity: wishlist > > Hello. I notice the linux-base package snoops around to get a list of > changes the user needs to approve. > > Well, there is one item it forgot to investigate: > If the user has > GRUB_DISABLE_LINUX_UUID=true in his grub configuration, > well, he will very likely get stuck in "waiting for the root filesystem" > and thus no be able to boot, at least with linux-image-2.6.33-2-686, > with more than a single partition. > > Therefore your script should perhaps poke around /boot/grub/grub.cfg, > update the entries there, and warn the user not to probably use > GRUB_DISABLE_LINUX_UUID=true anymore. Well, if you do that, it's your own problem. We cannot cover every possible strange configuration. > P.S., I am very curious, if one day, for some reason, the user finds > himself locked out of the system due to not having the proper UUID at > boot, whereas in the past, he could edit the boot command line (e.g., > by typing "e" in grub), and fill in some guesses like /dev/hda1, > /dev/hda2 etc. until he got the right one where the root filesystem > lives, but nowadays, with no alternative to the very long UUID strings, > there is no way he is going to guess it, so he won't be booting for a > very long while? [...] Device names still work, they just changed (and may change again if you have a USB storage device plugged in). Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part