It's really nice when dbus crash on a +systemd started system, the desktop (kde) obviously is broken but you loose the console too.
Why? because system start them on demand, but cannot work w/o dbus so Ctrl+Alt+F2 bring you to nowhere ...
Ctrl+Alt+Canc? No way systemd is locked
Solution? Hard reboot, if the kernel is compiled with some magic press Ctrl+print+S for an emergency sync of the disk, followed by Ctrl+print+B to reboot.
How it happened? Trying to port the gentoo linux-vserver start scripts, which mess with containers /probably/.
What systemd should do? It should start at least one getty for a console at boot_time, always, the other could still be optional.
And yes this mean that I'm trying systemd, sigh.
Shared publiclyView activity