[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Debian officially forked over systemd
- Subject: [Discuss] Debian officially forked over systemd
- From: blu at nedharvey.com (Edward Ned Harvey (blu))
- Date: Mon, 1 Dec 2014 00:09:48 +0000
- In-reply-to: <20141130181311.GA31891@dragontoe.org>
- References: <firstname.lastname@example.org> <7DF9948D-E0B1-4B9B-9665-4A21C5D91310@pioneer.ci.net> <20141130181311.GA31891@dragontoe.org>
> From: discuss-bounces+blu=nedharvey.com at blu.org [mailto:discuss- > bounces+blu=nedharvey.com at blu.org] On Behalf Of Derek Martin > > You can read the bug reports yourself to find real problems with > systemd breaking stuff Just as vague as everything I've ever read anti-systemd. > (you will find very little of that related to > sysvinit, which has been very solid for decades), Except for the existence of launchd/smf/upstart/systemd, intending to fix obvious problems of sysvinit, including the lack of dependencies and automatic actions, plus the need for programmers to "daemonize" everything that's meant to run as a daemon, which complicates the development effort. In short, I reject both the claim that systemd causes so many problems, and the idea that there's "nothing wrong with" sysvinit. Additionally, whenever I write something intended to run daemonized, I have to write *separate* sysvinit scripts for every distribution, because they all use different conventions. I don't have that problem with any of the modern replacements - launchd, smf, upstart, systemd.