this post was submitted on 19 Apr 2024
888 points (98.7% liked)
linuxmemes
21355 readers
1661 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
How the fuck is login and "the command line" still working? Maybe they did not reboot.
The reboot probably sent him straight to a virtual console.
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
Oh okay
As long as you can run
vim,gccandmake, it's not broken.initramfs recovery shell or they are trolling