On Sun, Jan 18, 2009 at 03:10:06AM -0000, Tommy Williams wrote: > In the ubuntu server distributions use of UUIDs should be disabled, and > legacy /dev/ support should be re-inserted.
Definitely not. Servers are the systems *most* likely to be affected by non-persistent device names in general (because they're the most likely to have multiple disks on multiple interfaces); UUIDs are the most reliable method of addressing filesystems in spite of their limitations, so this is the correct way for Ubuntu to address them in /etc/fstab and menu.lst by default. > Use of /dev/ locations on my home server would have prevented the problems > I experienced this evening. UUID collisions between filesystems only happen if you clone a filesystem using dd or the equivalent. Conversely, a UUID reference only becomes invalid if you remove the disk or reformat the partition, at which point the admin needs to know to update the references in the config files. I'm sorry for any trouble the switch to UUIDs caused you, but there are workarounds for each of these two problems, so not supporting those two cases really is the lesser evil. In any event, this particular bug has been resolved for Ubuntu 8.10 and later so that update-grub will no longer insist on rewriting entries to use UUIDs after you've configured them manually. I would still recommend that you use UUIDs; even aside from the questions of unreliable device ordering, there are no guarantees from Linux upstream that the device naming scheme itself will remain the same in the future. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- 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
