----- Original Message ----- > From: "Lamar Owen" <lo...@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 j...@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
