It failed to install the initscripts package because apt bailed out
apt —fix-broken install got you a little closer, but the screenshot didn’t say they tried that
My bet is this worked when systemd was first introduced, but since there’s not much use for it now, and sysvinit is deprecated, it just doesn’t accidentally work anymore
I was curious too, so I tried it in a virtual machine
It half installed sysvinit, systemd failed to get fully removed, and apt gave up due to too many post-install errors
The reboot threw me into an init that asked for me to specify the runlevel (since there wasn’t anything in init.d)
I guess they didn’t understand the difference between that question and a logged in shell
My guess before trying it was that they somehow got stuck in Grub’s shell
Yeah i remember debian installs sysvinit if you apt remove systemd and installs systemd if you apt remove sysvinit
haha why does debian bother adding this rule if the system will be left in broken state anyway
Maybe because its still not a broken state? They could still add init files ig
(As the tester above) It is a broken state
It failed to install the
initscriptspackage because apt bailed outapt —fix-broken installgot you a little closer, but the screenshot didn’t say they tried thatMy bet is this worked when systemd was first introduced, but since there’s not much use for it now, and sysvinit is deprecated, it just doesn’t accidentally work anymore
I mean you still can use cli? So you can technically make an init file and boot?
You can’t - it’s just asking what runlevel to launch, and there are no files for any runlevel
You’d need to add init=/bin/sh through grub at that point
How are you running apt then?
I didn’t after breaking it and rebooting
I restored the snapshot from before breaking the system and tried to see what would happen if I didn’t just reboot after apt bailed out