I am here from a duplicate of this bug, and I see this issue as a huge deal. my experience with this issue:
1) an upgrade of a production server at our co-location from dapper to hardy resulted in botched grub settings, I am still digging through backups to determine the contents of fstab prior to the upgrade. After the upgrade the fstab was pointed to the incorrect device (via uuid) this resulted in an unbootable system and a 60 mile round trip drive out to our co-location to rescue the machine. dist upgrades should not touch my fstab, I like it just how it is. Neither should my operating system determine what is best for me, there is other software I can pay for to do that. I have grub configured just how I want it, please just move my current options to the new grub menu item. 2) This evening I added two hard drives to my home server. In the process of doing this, the UUID entries in both the grub menu and the fstab created problems with the new hard drives (duplicate entries). So, since /dev/ locations change so often that they are no longer reliable, I too feel that UUIDs are non-reliable either. In the ubuntu server distributions use of UUIDs should be disabled, and legacy /dev/ support should be re-inserted. Use of /dev/ locations on my home server would have prevented the problems I experienced this evening. Addition and subtraction of USB and transient devices are not expected on server hardware. -- 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
