[175594] in North American Network Operators' Group
Re: Linux: concerns over systemd adoption and Debian's decision to
daemon@ATHENA.MIT.EDU (Jay Ashworth)
Fri Oct 24 16:33:54 2014
X-Original-To: nanog@nanog.org
Date: Fri, 24 Oct 2014 16:29:48 -0400 (EDT)
From: Jay Ashworth <jra@baylink.com>
To: NANOG <nanog@nanog.org>
In-Reply-To: <54495BFD.4010205@pari.edu>
Errors-To: nanog-bounces@nanog.org
----- Original Message -----
> From: "Lamar Owen" <lowen@pari.edu>
> Speaking from my own experience, the actually relevant and
> package-specific guts of the typical initscript could be easily
> replaced by a simple text configuration that simply gives:
>
> 1.) What to start
> 2.) When to start it (traditional initscripts work on a linear
> timeline
> of priority slots; systemd units have more flexibility)
> 3.) How to start it (command line options)
>
> This should not need to be an executable script. This is what systemd
> brings to the table (Upstart brought some of this, too).
That is a perfectly valid point. We don't dislike systemd because it does
that. We dislike it because it doesn't *only* do that.
Cheers,
-- jr 'see also IPv6' a
--
Jay R. Ashworth Baylink jra@baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII
St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274
