>From a user's standpoint, Install should not ever automatically put UUID's in fstab that Ubuntu does not need to run. If I want to mount some file system I can do it, I don't need Ubuntu making it a boot requirement for some file system that is not integral to the Ubuntu being installed.
A good example is Places, Network. That finds out what systems are on the network without doing an obligatory fsck during boot and demanding that every system on the network that was there during install be there as a condition of boot. I think I can do all I need if Places Network or something similar found the other file systems that are not needed for boot. Personally I have no problem with making a directory on /media and mounting /dev/sd whatever when I need to. I do have a problem with boot stalling because fsck can't find a file system I don't need anyway. As it is, every time I do a new install, I go back and reboot previously installed systems which then hang on boot because fsck can't check a UUID that format changed, I do exit or whatever to get by that, then sudo gedit /etc/fstab and comment out the obsoleted UUID's. I presume I could patch in the current UUID's but by this time I'm usually angry at having to do it at all. This whole mess would be much less complicated if format didn't change the UUID's. What's the absolute requirement to change the UUID's anyway? On this three boot system, there's one swap partition that is used by whichever Ubuntu I'm booting at the moment. Every install always reformats the one swap. Again. I don't recall the swap ever being a problem on boot. Jerry -- fsck Unable to resolve UUID https://bugs.launchpad.net/bugs/106209 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
