In the mean time, I find that if I issue sudo initctl emit filesystem
((initctl never exits, so I have to Ctl-C to make it die.)) sudo initclt emit net-device-up IFACE=lo & Then the boot completes and I get runlevel N 2 with all the goodies. I have 'init=/sbin/init --verbose' on the linux line that I am booting, so I see log entries about plymouth-log changing goals and state when I "emit filesystem". Then, when I "emit net-device-up IFACE=lo", I see lots of things starting, I've attached the syslog with blank lines inserted where the first and second "initctl emit ..." commands were run. I think this demonstrates that the events "filesystem" and "net-device-up IFACE=lo" EITHER are not being issued OR are being issued when the /etc/init/rc-sysinit.conf file has not yet been read by /sbin/init . ** Attachment added: "syslog" http://launchpadlibrarian.net/49092522/syslog -- Some services not started on boot, runlevel returns "unknown" https://bugs.launchpad.net/bugs/543506 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
