>Imho just adding the option to turn that behavior off without also making it >default will break a huge number of systems upon >upgrading to karmic in a >very subtle way. > >Nobody would expect such strange mount / fsck behavior changes. And this new >behavior breaks on almost every server box >that mounts user / service data >from a different filesystem.
Agree with that 100%. I had the problem on my system when applications started with no input/output filesystems mounted. This default will break many systems. This cannot be the default. > After that the screen went black and the diskactivity light lighted up. After a couple of minutes it was still doing that. So I pulled the plug on my laptop and fired it up again. I removed the splash and quiet option from grub and booted. I then saw fsck was running. Agree with that too. Had the OS misbehaviour too but guessed correctly that the filesystems are being checked. Some indication for the FS checking should be added -- boot process isn't paused while fsck runs on partition: boot process is completed with fsck running in the background preventing partition from mounting https://bugs.launchpad.net/bugs/439604 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
