I've another configuration where this update-grub "undocumented feature" is a problem.
I'm using several (20) Hardy+LTSP servers with 2 (strictly) identical disks, mounted in amovible disk racks. The second one is a "backup mirror" of the first one (using an initial dd copy). Every night, a rsync routine updates the second disk, and the system is rebooted. t's a kind of mirror backup, a compromise between RAID and regular backup. In case of first (boot) disk crash, users just need to swap disk racks and reboot to get a running system within a couple of minutes, which is the main goal of this approach (used in public schools). The only solution to get this to work is to use device names (i.e /dev/sd?) in menu.lst, not UUIDs. I can't use different UUIDS for the 2 disks: in that case, the 2 menu.lst files would be different. Rsync will overwrite any change, and reboot after a disk crash will not work. I can't use identical UUIDS for the 2 disks: in that case, grub randomly boots from first or second disk... So I need to get a menu.lst using disk device names instead of UUIDs. And update-grub (launched automatically at every kernel update) gently wipes out my kopt option... I think it's definitely a bug: update-grub MUST keep the "kopt" option just like it reads it from menu.lst, and must not try to reset to another value (containing UUIDs). Pierre -- edgy update-grub destroys kopt https://bugs.launchpad.net/bugs/62195 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
