Failed systemd install ruined my boot, trying to restore sysvinit
Just as I'm about to call it the day and go to sleep I wonder if trying to replace KDM for slim is part of the problem. But that's probably unlikely.
As I installed systemd, replacing sysv, as it's supposed to, the PC wasn't able to reboot by "shutdown -r now" - I guess it has something to do with the uninstalling of sysv. I tried "halt" but contrarily to my expectations, apparently it just makes the PC literally halt rather than shut down. I've then shut down by holding the power button (just pressing it once wasn't triggering a proper shutdown either). After that I've not been able to boot on my Debian Wheezy install properly, it always end up not running the init scripts properly with the message:
"/etc/init.d/[whatever] can't open /lib/lsb/init-functions"
"whatever" being things like "mountall", "urandom", "procps", dozens of things, actually these are the bulk of the boot messages, more things not working than working. I think that the only thing that gets done is mounting the drives but maybe not even that.
I've tried chrooting into it through an live AntiX CD, trying to reinstall sysv, switch for upstart, systemd again, and then sysv again, none of these attemps worked, the boot is always unfinished on that "control D or password for maintenance" point.
In this last attempt for some reason apt/dpkg eventually got locked and I can't use it anymore (aptitude says something along the lines of a file on /var/aptitude/lock not existing or something, and then it only "dry runs").
I've googled a little bit for such terms but I haven't find any situation that's similar enough so far. Part of the reason why I tried it to begin with, I've found a couple of people saying that they installed systemd on Debian with no problem, so I thought it couldn't get into much trouble, at most something that would be easily reversible. What a fool I am.
So, anyone thinks there's something relatively simple I could be missing, before I go on and reinstall the whole OS?
Last edited by the dsc; 11-20-2012 at 01:18 AM.
Reason: unambiguous title