Comment 10 for bug 46223
Revision history for this message
| Lonnie Lee Best (launchpad-startport) wrote Re: [DAPPER] update-grub doesn't work correctly with raid partitions | #10 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is still a problem on 6-6-2007:
http://
The update-grub command does a poor job of determining which partition the operating system in on.
Instead of using the "#groot" line in /boot/grub/menu.lst why doesn't it just look at the last kernel's root partition and use that as the default for the new kernel entry in /boot/grub/menu.lst ?
Would this be more resilient? No one who installs Ubuntu know to edit the "#groot" line to set the default. Dell certainly didn't know (see the link above). If you keep using the "#groot line to set the default root, then this needs to be a part of the installation process. There needs to be an option, during installation, that asks which partition is default. Or, during installation of Uubntu, perhaps a script can run to update the "#groot" value to which ever partition is mounted as root.
Actually, grub is foundational. It can be underneath several installations of Ubuntu Linux and multiple partitions. However, during a kernel update of one of these installations, the update-grub command is called. How can this command be aware of the "calling installation's root boot needs"?