My morning thoughts about "Default behavior for missing part set to
nobootwait" : in my opinion, this should not be done ! As if you are in
production system, your machine should only start if all prerequisites
are satisfied. Imagine what happens if you have /usr missing, with all
programs that should start, like apache, mysql, etc
dblade: you said "This also major issue on servers with remote only
access where interactive prompts would not be desired anyway", I have
just tested what happens with Debian Etch if there is wrong (missing)
devices in /etc/fstab : system don't boot, problem with fsck ("the
superblock could not be read......."). Same behavior on Hardy.
I think that if users really want to boot with missing parts, they
should explicitly add "nobootwait" to concerned fstab lines.
So for me:
* wait for user to press S/M is NOT a bug
* missing "splash" in grub2 conf IS a bug, that don't let users see why their
system won't boot
* Press S or M does not work for more than one partition on error IS a bug (LP:
#655616)
--
Boot hangs and unable to continue when automount disk in fstab is not available
(Off or Disconnected)
https://bugs.launchpad.net/bugs/571444
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
