2014-10-21 17:24 GMT+02:00 Robert Lemmen <rober...@semistable.com>:
> hi matthias,
>
> On Tue, Oct 21, 2014 at 04:35:20PM +0200, Matthias Urlichs wrote:
>> [...]
>> first place. Having ten processes responsible for bits&pieces of what
>> systemd-as-PID1 does instead of one isn't a benefit -- not if all you gain
>> by that is nine additional processes.
>>
>> "It's a big monolithic thing, and big monolithic things are bad and evil
>> and non-Unix-y, so there!!1!" is not a valid argument.
>
> but that's the thing, to some (e.g. me) ten separate processes that each
> do a fairly small thing with understandable interfaces between them is
> an *enormous* benefit over one bigger thing that does all that in an
> integrated fashion. to the point that even if the one big thing would
> have nice,additional features, I would still opt for the decomposed
> one.
Well, you just now described systemd. The systemd project develops
many small tools which do one thing ant interact together via defined
interfaces.
The init daemon is a bit more powerful that sysvinit, but it still
only does what it is supposed to do: Starting, stopping and monitoring
services. The other tools under the systemd umbrella do different
things.
Did you play around with systemd already?
Cheers,
Matthias
--
Debian Developer | Freedesktop-Developer
I welcome VSRE emails. See http://vsre.info/
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/CAKNHny8Uh=+wC=8k60m1raifbh4ssbo-v8ky6usdblol6hd...@mail.gmail.com
