On Mon, Nov 02, 2009 at 08:18:39AM -0000, Blue wrote: > Shouldn't this at least be fully consistent ? I mean ok, you do not wait > for non core filesystems, but you either do not wait with anything unless > bootwait is specified, or you wait with everything ?
No, the default is to wait only for those filesystems that are known to be required for successfully starting the other services. cryptsetup is a special case in that it interferes with gdm startup directly, regardless of where the related filesystems are mounted (and even if they're not mounted at all by default). We should try to find a better solution for Lucid on this issue that doesn't require use of bootwait. > Now, tty's will wait for any filesystem but gdm won't. Not true; both gdm and ttys wait for the same set of filesystems, gdm is just started first whereas ttys are started only after the rest of the init scripts run. -- 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/ slanga...@ubuntu.com vor...@debian.org -- cryptsetup devices not mounted on boot https://bugs.launchpad.net/bugs/430496 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
