It's probably a bad idea to start (another) discussion on this topic, but... While the original (Debian Fork) made some ridiculous claims, this is not a fair comparison to make. As a neutral party I don't think I've seen anyone make the argument that SysVinit is any good, just that some other options may be better, and they should at least be an option. When you compare systemd with something like OpenRC the obvious…
Shall we fork Fedora?
21–30 of 49 posts
Re: Shall we fork Fedora?
#22Programs have many bugs. I'd rather debug that shell script than debug systemd.
Re: Shall we fork Fedora?
#23Trying to work out which linux dist to switch to. Obviously one that doesn't use systemd. So what choices do I have?
Linux from scratch has a runit-for-lfs project here: https://code.google.com/p/runit-for-lfs/
github mirror: https://github.com/inthecloud247/runit-for-lfs
I've also been keeping an eye on voidlinux: http://www.voidlinux.eu
Re: Shall we fork Fedora?
#24Trying to work out which linux dist to switch to. Obviously one that doesn't use systemd. So what choices do I have?
Re: Shall we fork Fedora?
#25Trying to work out which linux dist to switch to. Obviously one that doesn't use systemd. So what choices do I have?
Re: Shall we fork Fedora?
#26NB not taking a position, just making a prediction
Re: Shall we fork Fedora?
#27From the debianfork.org page, which this is apparently mocking: "Why don't you do that yourselves? We are excluded from voting on the issue: only few of us have the time and patience to interact with Debian on a voluntary basis." If you don't have the time and patience to contribute to a project like Debian, how are you planning to muster up the time and patience to run a full-on FORK of Debian?
[edit/clarification] Since this seems to be one of the most prominent critiques, we'd like to clarify this point. With lack of time and patience we refer to our possibility to be involved in a complex bureaucratic system like the one governing Debian. While we respect this way of working, we think that our time is better invested in new directions, also according to our expertise.
Re: Shall we fork Fedora?
#28It's probably a bad idea to start (another) discussion on this topic, but... While the original (Debian Fork) made some ridiculous claims, this is not a fair comparison to make. As a neutral party I don't think I've seen anyone make the argument that SysVinit is any good, just that some other options may be better, and they should at least be an option. When you compare systemd with something like OpenRC the obvious…
#!/bin/sh
sv check slapd postgresql mysql >/dev/null || exit 0
exec /usr/sbin/sendmail -bs -bd -q5m start
https://github.com/inthecloud247/runit-for-lfs/blob/master/b...Re: Shall we fork Fedora?
#29From the debianfork.org page, which this is apparently mocking: "Why don't you do that yourselves? We are excluded from voting on the issue: only few of us have the time and patience to interact with Debian on a voluntary basis." If you don't have the time and patience to contribute to a project like Debian, how are you planning to muster up the time and patience to run a full-on FORK of Debian?
Re: Shall we fork Fedora?
#30The argument presented is very weak. Yes, the service file is smaller and simpler, but I actually understand perfectly the init file, whereas to understand how systemd processes the service file I'd have to actually read all of systemd's source code. Programs have many bugs. I'd rather debug that shell script than debug systemd.
The shell script approach violates the DRY principle--it's probably super similar to some 50 other init scripts on the same system. systemd, in principle, removes the boilerplate so that the bug would only have to be fixed once.