this post was submitted on 19 Apr 2024
888 points (98.9% liked)

linuxmemes

20880 readers
6 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
888
systemdeez nuts (sh.itjust.works)
submitted 7 months ago by [email protected] to c/[email protected]
206 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 7 months ago (1 children)

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

[–] [email protected] 4 points 7 months ago (1 children)

Yeah i remember debian installs sysvinit if you apt remove systemd and installs systemd if you apt remove sysvinit

[–] [email protected] 2 points 7 months ago (1 children)

haha why does debian bother adding this rule if the system will be left in broken state anyway

[–] [email protected] 2 points 7 months ago (2 children)

Maybe because its still not a broken state? They could still add init files ig

[–] [email protected] 1 points 7 months ago (1 children)

(As the tester above) It is a broken state

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

[–] [email protected] 1 points 7 months ago (1 children)

I mean you still can use cli? So you can technically make an init file and boot?

[–] [email protected] 1 points 7 months ago (1 children)

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

[–] [email protected] 1 points 7 months ago (1 children)

How are you running apt then?

[–] [email protected] 1 points 7 months ago (1 children)

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

[–] [email protected] 1 points 7 months ago

Oh okay

[–] [email protected] -1 points 7 months ago

As long as you can run vim, gcc and make, it's not broken.