On 07/01/2010 10:18 AM, Wout wrote: > So /dev/console exists but isn't immediately "ready for work". It appears it > becomes fully functional later (otherwise it would not be possible to start > the failing services manually). > Can we figure out at what point /dev/console becomes functional? > > In the meantime two workarounds seem doable, both assuming /dev/console > doesn't depend on anything started during boot: > 1. A boot script that doesn't complete until /dev/console works, make > rc/rc-sysinit boot sequence depend on it. > 2. A patch in upstart that waits until /dev/console works. > > Any thoughts?
I think if Scott's analysis is correct then the correct solution would be to have the kernel buffer anything received on /dev/console until it's ready to display it. Anyone for reassigning this bug to the kernel? Regards, Michael -- CUPS and other system services not starting at boot https://bugs.launchpad.net/bugs/554172 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