In comment #50 I ask if the "filesystem" and "net-device-up IFACE=lo" events are not issued or issued when /sbin/init doesn't yet know about /etc/init/rc-sysinit.conf .
I now see, in a "runlevel unknown" boot _AND_ a "runlevel N 2" boot that each /var/log/boot.log records that both events happen _and_ the rc-sysinit state goes from "waiting" to "starting". Both boot files are the same length: 730 lines. >From examining the boot.log files I think that, although the order is >different, all the same activities are accomplished before the filesystem event is asserted. The end of the boot.log file, in either case, reads: <tty> init: rpc_pipefs goal changed from stop to start init: rpc_pipefs state changed from waiting to starting init: Handling starting event init: rpc_pipefs state changed from starting to pre-start init: rpc_pipefs pre-start process (835) init: Handling filesystem event <<< init: rsyslog goal changed from stop to start init: rsyslog state changed from waiting to starting init: plymouth-log goal changed from stop to start init: plymouth-log state changed from waiting to starting init: ssh goal changed from stop to start init: ssh state changed from waiting to starting init: rc-sysinit goal changed from stop to start init: rc-sysinit state changed from waiting to starting <<< init: Handling starting event init: rsyslog state changed from starting to pre-start init: rsyslog state changed from pre-start to spawned </tty> Next stop, pulling apart the syslogs. -- 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
