3 ms·
Not really, I use a dozen init systems, each for a different situation, and I'm interested in keeping it that way. The problem is that systemd is that is being
by e7620 12y ago
Not really, I use a dozen init systems, each for a different situation, and I'm interested in keeping it that way. The problem is that systemd is that is being forcefully pushed to all distros. For instance, by merging udev with systemd.
Maybe those forks don't add nothing for you, but for me they're beneficial, because I think Darwinian evolution also applies to software.
- api 12y ago> I use a dozen init systems, each for a different situation, and I'm interested in keeping it that way. You might like that, but it makes life hell for developers who write and package any kind of daemon/service.
- e7620 12y agoAbsolutely not, only if they depend on systemd. If they follow UNIX conventions, they don't need to edit a single file. Writing a daemon init script was a solved problem decades ago, and that script will serve for every init system.
- api 12y agoNope. Some systemd distros do not support daemon init scripts done the old way.
- digi_owl 12y agoI keep seeing this, and i keep wondering why said developers are doing any packaging at all. A binary and clear instructions on how it is launched from a command line should suffice for any competent admin. He should then be able to fit it into the boot scheme of whatever system he is maintaining.