Christopher Conforti
2022-02-19 17:21:45 UTC
My Debian install is broken to the point where the package manager mostly
refuses to do anything useful. I can't reinstall because I need it for my
work and I can't waste time collecting all my software again. I need to
fix it from within, and I want to start by migrating away from systemd to
sinit. (You can find sinit on suckless.org)
Systemd is a bloated piece of garbage, the fuel of dumpster fires the
world over. It's a damn cancer upon the software world. I really don't
know if it's the cause of my system being broken; I suspect at this point
I have no way of knowing within a reasonable timeframe, since it's not
possible for a single human to understand it in its entirety because it's
just so damn complex and does WAY more than an init system should do.
It's equally likely that I did something stupid at some point--but again,
I can't seem to be able to know at this point. It's a damn headache to
work with, and I'm choosing its replacement as the first thing I'm going
to do to fix my horribly broken install, because why not?
Sinit is, in its entirety, less than 200 lines of code--that includes the
Makefile. I understand completely what it's doing, and how it's put
together. This convinces me that it is absolutely the right choice for
replacing systemd.
I don't know how to migrate to a different init system without bricking
my install--I've never had the need to do so; but now that I do, my
searches yield no useful information. I don't know what needs to be done
for a (relatively) seamless migration, and I've never actually used an
init system anything like sinit i.e., one with init scripts instead of
unit files.
Can anyone offer advice? Where can I find information on this?
refuses to do anything useful. I can't reinstall because I need it for my
work and I can't waste time collecting all my software again. I need to
fix it from within, and I want to start by migrating away from systemd to
sinit. (You can find sinit on suckless.org)
Systemd is a bloated piece of garbage, the fuel of dumpster fires the
world over. It's a damn cancer upon the software world. I really don't
know if it's the cause of my system being broken; I suspect at this point
I have no way of knowing within a reasonable timeframe, since it's not
possible for a single human to understand it in its entirety because it's
just so damn complex and does WAY more than an init system should do.
It's equally likely that I did something stupid at some point--but again,
I can't seem to be able to know at this point. It's a damn headache to
work with, and I'm choosing its replacement as the first thing I'm going
to do to fix my horribly broken install, because why not?
Sinit is, in its entirety, less than 200 lines of code--that includes the
Makefile. I understand completely what it's doing, and how it's put
together. This convinces me that it is absolutely the right choice for
replacing systemd.
I don't know how to migrate to a different init system without bricking
my install--I've never had the need to do so; but now that I do, my
searches yield no useful information. I don't know what needs to be done
for a (relatively) seamless migration, and I've never actually used an
init system anything like sinit i.e., one with init scripts instead of
unit files.
Can anyone offer advice? Where can I find information on this?