Re: /var/run/

Conrad Knauer wrote:

> On 1/5/07, Scott Walde <scott@waldetech.ca> wrote:
>
>> It seems to me that Upstart is running contrary to the basic philosophy
>> of Unix:
>>
>> (i) Make each program do one thing well. To do a new job, build afresh
>> rather than complicate old programs by adding new features.
>> - Doug McIlroy (/The Bell System Technical Journal)
>
>
> Not that I know too much about the deep inner workings of a Linux
> system, but from what I have read about upstart, it sounds like its
> actually doing just that. Certainly they are building anew with
> upstart, rather than adding another layer onto something. In
> addition, they are apparently arguing that there is really only one
> job being done but that it is currently being divided up among several
> programs, creating unnecessary overlap. Consider the "Rationale"
> section of https://wiki.ubuntu.com/ReplacementInitDiscussion

I still fail to see how at/anacron/cron and inetd and init are
variations of the same task, other than the most vague idea that "they
are all ways of starting programs/services." (so is the command line...
are we somehow going to move that into upstart too?) Their functions
are quite different. I stand by my statement that putting
at/cron/anacron/inetd functionality into upstart is contrary to the KISS
principle.

The idea of having PID 1 listening on a few dozen ports just seems a
little scary to me.

ttyl
srw
Received on Sat Jan 6 00:29:37 2007