Hm. I’m not sure what I’m doing. The sulogin hack worked. When I logged
in the output of «initctl list» was:

rc stop/waiting
udev start/running, process 1111
mountall-net stop/waiting
upstart-udev-bridge start/running, process 1109
rsyslog stop/waiting
avahi-daemon stop/waiting
hwclock-save stop/waiting
dbus stop/waiting
atd stop/waiting
control-alt-delete start/running, process 1425
hwclock stop/waiting
module-init-tools stop/waiting
mountall start/running, process 1090
cron stop/waiting
rcS stop/waiting
acpid stop/waiting
hal stop/waiting
dbus-reconnect stop/waiting
rc-sysinit stop/waiting
udevtrigger stop/waiting
anacron stop/waiting
tty2 stop/waiting
udev-finish stop/waiting
rsyslog-kmsg stop/waiting
hostname stop/waiting
mountall-reboot stop/waiting
udevmonitor stop/waiting
network-interface (wmaster0) start/running
network-interface (lo) start/running
network-interface (eth0) start/running
network-interface (wlan0) start/running
mountall-shell stop/waiting
tty1 stop/waiting
networking stop/waiting
dmesg stop/waiting
procps stop/waiting


That is, mountall was running, but the local disk was not mounted at all. The 
ethernet and root mount already were up courtesy of the initrd of course.

So I ran «mount -a», which worked fine. Other than that I was in a
pretty much uninitialized state. rsyslog, dbusm avahi-daemon etc. were
not running, and I’m not sure networking is supposed to be in stopped
state.

Then I ran «init 5» and the scripts in rc5.d ran, but I had to «start
rsyslog» and «start dbus» manually.

Is this in some way my own fuckup? I just dist-upgraded after all?!?

-- 
new mountall exits with code 1. only root shell using PXE netboot.
https://bugs.launchpad.net/bugs/430348
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

Reply via email to