Comment on [deleted]
communism@lemmy.ml 1 day ago
Alpine already uses OpenRC. There’s no option to use systemd with Alpine.
Popular alternatives include runit (which Void uses), OpenRC (Gentoo and Alpine), s6, sysVinit, dinit. The suckless people have also written some suckless inits—I think one of them’s called sinit.
So what are the alternatives that work with both Alpine and Debian?
None. On Alpine you can only use OpenRC and on Debian you can only use systemd. Most distros don’t let you change out the init system. If you want systemdless Debian look into Devuan.
Judging from this post, I would say you should not be looking to change out your init system as, no disrespect intended, but you really don’t seem to know what you’re talking about. You don’t even know what init systems your operating systems (Alpine and Debian) are using, let alone the details of different init systems.
Some people have strong opinions about init systems. They are nerds with reasons behind those opinions. You don’t seem to have many reasons and you don’t seem to be particularly invested in the debate. I would say it’s not worth your time to change operating system (which is what you would need to do to change your init) just because you heard vaguely that systemd is bad. If you reach a point where init system matters to you, then you won’t need to be asking the questions you’re asking in the OP.
lambalicious@lemmy.sdf.org 1 day ago
Fake news. On Debian you can use both sysvinit and openrc (I have six servers on sysvinit, tho I do actually intend to shift them to systemd later mostly because of the container management goodies).
Mostly agreeing here. For selfhosting the init system matters barely any, since past the default distro setup one would be doing most of everything with Docker, Podman, etc. At that point, none of the usual Linux religious wars matter much (you can perfectl edit a compose file with nano).
communism@lemmy.ml 1 day ago
Huh really? Then why does Devuan exist? (I don’t use Debian for context)
lambalicious@lemmy.sdf.org 1 day ago
Because it was not always the case that sysvinit was supported - things were sorta “accidentally hazy” for a while. There was a time (I think during Debian 9 and 10) that systemd not only was the default, but was also enforcedly linked against a large part of the stack (you couldn’t have a desktop environment, PulseAudio or NetworkManager without systemd, for example).
This led to the rise of projects like Devuan, that provide a working system that installs without systemd by default; Antix’s
nosystemd
repo, which allows to install components of the Debian stack without the enforced systemd dependency; and laterlibam-elogind-compat
which aided shimming some of systemd’s requirements under elogind.Nowadays at least, the only hard part of not using systemd in Debian is 1.- switching (from or to) seems to require rescue mode and 2.- you lose some of the container management goodies (for eg.: Podman services).
communism@lemmy.ml 23 hours ago
I see, that’s interesting. Well glad that it’s not hard to switch away from systemd on Debian for those who want it—although I still think if you don’t want systemd you should just pick another distro, given that the Debian installer doesn’t let you pick another init.