Comment 4 for bug 499483
Revision history for this message
| Eskild Jacobsen (eskild-jacobsen) wrote | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
Hello Felix
I think you might have read this bug report a bit fast... This is actually for the kernel root= parameter. What I'm trying to point out, is that in order to use grub2 without UUID on file systems, the proposed solution will work great. File system UUID is a sure way to get into trouble if one is using image-based deployment (fog, ghost...), because one usually will have a new UUID on each filesystem, but kernel root=UUID=... will point to an non existing fs. Without being able to disable this feature and use for instance root=/dev/sda2 as a root device as opposed to root=UUID=... in the grub configuration one will have issues. Of course, one could do this manually, but it will fail every time you get a new kernel, or update your grub configuration. One could of course argue that one shouldn't use image based installations, but i beg to differ, and would like to point out that an image based deployment system is much faster than an installation based deployments.
I really hope you will take these considerations into account, because this really is a serious issue for us, and probably many others.
-Eskild
P.S. sorry about not using diff -u when I made the patch...