sharkfucker420, I just shot my OS in the heart, why isn’t it working?
lemmyreader, I think I would have preferred
sudo apt-get remove --purge systemd
Yeah, some old habits never die.
possiblylinux127, Holly shit this has 700 upvotes
kamen, Stupidity is entertaining.
steeznson, You can switch seamlessly between systemd and openrc on gentoo. Although it might be worth using one of the debian derivatives in this user’s case - not sure they should be messing with their system too much!
DrM, I updated my sources.list to something non-existing at some point and run
sudo apt update && sudo apt dist-upgrade -y && sudo apt autoremove
once and it also basically uninstalled everything. But that didn’t even matter, I popped in a recovery disk and could reinstall everything. Pretty great to be able to do all that with Linux, fuck everything up in an instant but after a few hours everything is back again
Tibi, Well you could have saved those hours if you were on one of those restrictive OSs. I mean why would anyone even wanna do that? /s
chrishazfun, It’s impressive how they know enough to use Stack Exchange for questions like this but not enough that removing SystemD is like ripping someones heart out on most distros.
kevincox, You greatly overestimate the intelligence of the average Stack Exchange question asker.
SomethingBurger, Smartest systemd hater.
chrishazfun, Putting pure diesel into a clearly labelled petrol V8 type situation
ulterno, They forgot that heart transplant requires replacing the removed heart with another one and then connecting the blood vessels before closing up.
You can’t just take it out and say “I’ll put in another one after dinner”
Abnorc, Maybe they knew, but wanted to see what would happen.
linearchaos, Then post about how horribly complicated Linux is.
woodgen, How the fuck is login and “the command line” still working? Maybe they did not reboot.
possiblylinux127, initramfs recovery shell or they are trolling
ozymandias117, 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
mexicancartel, Yeah i remember debian installs sysvinit if you apt remove systemd and installs systemd if you apt remove sysvinit
redcalcium, haha why does debian bother adding this rule if the system will be left in broken state anyway
mexicancartel, Maybe because its still not a broken state? They could still add init files ig
ozymandias117, (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 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
mexicancartel, I mean you still can use cli? So you can technically make an init file and boot?
ozymandias117, 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
mexicancartel, How are you running apt then?
ozymandias117, 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
mexicancartel, Oh okay
ulterno, As long as you can run
vim
,gcc
andmake
, it’s not broken.
why, The reboot probably sent him straight to a virtual console.
redcalcium, I believe you can install
runit
in debian. It’ll be like devuan but with extra steps.
dan, Yeah both runit and sysvinit are supported, but packages are no longer required to include sysvinit scripts, so there’s no guarantee that all software will work. Most have kept their sysvinit script though.
The main issue will be that systemd does a lot of stuff, so you’d have to install replacements for everything else it does - like a syslog daemon for logging, ntp client for clock syncing, DNS resolver, etc.
Treczoks, I removed and sold the wheels of my car, now it does not move.
k110111, Lol this reminds me of a time when I had KDE desktop environment installed on vanilla ubuntu. I thought I didn’t really need ubuntu’s default desktop environment and decided to ‘purge’ it. I quickly realized my f up when it deleted so many packages and ui started to act weird, I copied the shell’s output to a file just incase, and sure enough I couldn’t login with ui on next reboot. I was somehow able to login to shell and with some awk magic I was able to parse the text file to get all the packages I deleted and lo and behold everything worked just fine. Linux let’s you f’up your OS but it also let’s you fix it, it’s just a skill issue.
itsnotits,
- Linux lets* you
- also lets* you fix it
meekah, It’s no tits
Skepticpunk, Linux let’s you f’up your OS but it also let’s you fix it, it’s just a skill issue.
Yeah, there’s something about Linux that makes me feel like if something breaks in it, the only reason I can’t fix it personally is because I lack the skills to fix the problem. Just feels nice, really.
rolaulten, If your installing, or deleting something and your package manager is modifying more then a few packages: stop, read and think about what your about to do.
interdimensionalmeme, Install sysv, return to monke
harrys_balzac, Sell computer, return to monke
Fridgeratr, Best way to fix that is to go back in time and not do that
BCsven, Sudo snapper rollback…oh he’s on debian. nvm
MenacingPerson, Snapper works on all distros with BTRFS
BCsven, Sure but not as default install
ILikeBoobies, Run installation media and copy systemD over to the system
Allero, For real though, if you break ANYTHING in Linux, it can probably be repaired through live image on your flash drive.
CCF_100, I use BTRFS, and it randomly decided to corrupt like half of the system packages on my system after an update, but all I had to do to fix it was boot into a live environment and run a command to reinstall everything on my system. :P
possiblylinux127, Its been pretty stable for me
BCsven, Same 7 years with no issues
gatorboy326, Using btrfs for past 6 months in my kde environment, doesn’t encountered any problem like this. Pretty stable
CCF_100, It’s only really a problem if I try upgrading while low on space and also having disk compression enabled
pearsaltchocolatebar, No probably about it
possiblylinux127, Or just use the recovery shell. They did say they could log in.
Skepticpunk, Is it possible to chroot from a livedisk and reinstall systemd from that? I’d imagine the Internet connection would work just fine.
Kazumara, He uninstalled systemd, now his computer is not doing systemd things anymore by his retelling. Seems like it worked fine. Yet he asks for a solution of a problem. Maybe he needs to state the problem.
EvolvedTurtle, This is like the Linux equivalent of deleting system32
Kazumara, But system32 contains the NT kernel as well, so that’s worse. Uninstalling your init system on a Linux distro still leaves you with single user mode. You could probably reinstall an init system from there.
SirQuackTheDuck, Nah, more like deleting explorer.exe.
There’s isn’t really a Windows equivalent for this, as Windows doesn’t give you control on this level.
It’d be as if you could delete services.msc but also the runner behind it.
dubyakay, I did delete explorer.exe on an earlier iteration of Windows (possibly 98SE). I’ve just restored it with Windows Commander (now TCMD).
areyouevenreal, On Debian you can actually change init systems. Don’t know how hard it is and you are probably meant to install a new one after removing systemd, but it is possible at least.
lightnegative, Is it system32 or SySWow64 these days?
PoolloverNathan, System32 holds the 64-bit stuff and SysWOW64 holds the 32-bit stuff. This makes complete and total sense.
silliewous, I don’t think you’ll get a cli if you delete system32.
laurelraven, I think we sound test that.
For skyense.
MonkderDritte, I mean, it can work out if he installs an alternative init & rc and a wifi-manager first. And then recreates initrd. Maybe needs to migrate some dns stuff too.
oo1, install that rm -rf theme
Add comment