Its the IPC request that removes the need to include an explicit dependency model, and so simply skips over the impossible-to-overcome limitation in Upstart where the network might be required to boot, or might not be required for much of anything excpet Firefox. This also means that the duplication of configuration can be avoided: instead of editing the nfs files, then fstab, then the “network is needed for everything so start it first” event file for Upstart, everything just works since as soon as somebody asks for network, the network just comes up. Less config file editing. More just works.

Having worked with, supported and administered unix and linux systems for 17 or so years I think the idea presented here is great! A good replacement for the ‘just a bunch of scripts’ has been far far too long in coming, something at least launchd didnt manage to breach either. Its projects like this that get me excited about distributions like ubuntu and by extension debian.

While I’ve been familiarizing myself with upstart, I’ve been asking the same question. IMO, it can be viewed from a different viewpoint thought in regards to the UNIX philosophy.

You can view cron, inetd, anacron, etc as variations on the same theme. Starting jobs on time, network activity, etc. It may seem construed, but the current situations seems to me like wc were split up into four different commands, depending whether you want to count lines, characters. bytes or words.

It is of course due to historical reasons that jobs management is like this, but this is the rare exception where I don’t see merging functionalities as a necessarily bad thing. It is a fine line to walk though.

While I’ve been familiarizing myself with upstart, I’ve been asking the same question. IMO, it can be viewed from a different viewpoint thought in regards to the UNIX philosophy.

You can view cron, inetd, anacron, etc as variations on the same theme. Starting jobs on time, network activity, etc. It may seem construed, but the current situations seems to me like wc were split up into four different commands, depending whether you want to count lines, characters. bytes or words.

It is of course due to historical reasons that jobs management is like this, but this is the rare exception where I don’t see merging functionalities as a necessarily bad thing. It is a fine line to walk though.

While I’ve been familiarizing myself with upstart, I’ve been asking the same question. IMO, it can be viewed from a different viewpoint thought in regards to the UNIX philosophy.

You can view cron, inetd, anacron, etc as variations on the same theme. Starting jobs on time, network activity, etc. It may seem construed, but the current situations seems to me like wc were split up into four different commands, depending whether you want to count lines, characters. bytes or words.

It is of course due to historical reasons that jobs management is like this, but this is the rare exception where I don’t see merging functionalities as a necessarily bad thing. It is a fine line to walk though.