Re: [gentoo-user] Debian just voted in systemd for default init system in jessie

[Yuri K. Shatroff]

24.02.2014 16:39, Mark David Dumlao пишет:
> On Mon, Feb 24, 2014 at 3:11 PM, Yuri K. Shatroff <yks-uno@××××××.ru> wrote:
>> 24.02.2014 02:32, Alan McKinnon wrote:
>>> [1] For lack of a better term, let's just call systemd here a "system
>>> controller". What is this ONE thing a system controller should do and do
>>> it well?
>>
>>
>> An init daemon generally does one thing well.
>
> it's obvious you haven't thought this through.
>
> consider, for a moment, that the "one thing well" that an init daemon
> is supposed to do is
> "run programs that do arbitrary things to get the system to an arbitrary state".
>
> do you not see a problem?

No. As you say, ``an init daemon is supposed to do is "run programs``, 
until here you're right, but then you start talking about things the 
init doesn't do but the programs do. In your wording, an init daemon is 
also a DBMS, an MTA, a network startup daemon, a firewall, a getty and 
whatever program runs on the system.
There was a post in this thread with a link to an opinion what an `ideal 
init` would do: just fork and exec anything in /etc/init.d or somewhere 
else.
In the real world, it's of course not so simple. But it doesn't mean you 
may imply init's responsibility for `arbitrary` tasks. If I write an ASM 
program with an illegal instruction, is it the init's problem? If my 
mail/web server is DDOSed, is it the init's problem? If my HDD dies, 
also the init's problem?

-- 
Regards,
Yuri K. Shatroff