Comment 81 for bug 543506

On Wed, Jun 09, 2010 at 01:06:20PM -0000, Olivier Debon wrote:
> What I could diff from syslog between a successful startup and a no runlevel situation is that only the 2 following messages are missing in the failure case:

For many of us, the solution is already in this Bug report. Namely:

 From comment #54
Comment out "console output" in all /etc/init/*.conf files that
have it.

 From comment #73
Add "started rsyslog" to the "start on" stanza in /etc/init/rc-sysinit.conf:
  start on ( filesystem
   and started rsyslog
   and net-device-up IFACE=lo
  )

 From comment #79
Add "init='/sbin/init --verbose'" to the linux boot line in grub.

Folks:
Have any of you found this insufficient? Was there anything else you had
to do to achieve reliable boots?

I can imagine that items in /etc/init.d/* and/or /etc/rc2.d/* that attempt
to write to /dev/console could get caught in the race condition between
/dev/console becoming writable and them running.

To my mind there should be an event when /dev/console _is_ writable,
but I don't know if one exists or how to make it happen.

--
 Mike Bianchi
 Foveal Systems

 973 822-2085

 <email address hidden>
 http://www.AutoAuditorium.com
 http://www.FovealMounts.com