Comments on: Upstart in Universe http://www.netsplit.com/2006/08/26/upstart-in-universe/ Just another WordPress weblog Wed, 20 Aug 2008 20:40:24 +0000 http://wordpress.org/?v=2.6.1 By: Tony http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-722 Tony Wed, 20 Feb 2008 19:47:38 +0000 #comment-722 As far as I understand, common scripts as sysvconfig or ksysv will not work anymore with upstart? As far as I understand, common scripts as sysvconfig or ksysv will not work anymore with upstart?

]]> By: jakepain http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-707 jakepain Thu, 27 Dec 2007 09:04:25 +0000 #comment-707 hello,scott, I have a program! What's the relation between udev and upstart? I know udev can receive "event" from linux kernel,but does it emit "event" to upstart init daemon? hello,scott,
I have a program!
What’s the relation between udev and upstart?
I know udev can receive “event” from linux kernel,but does it emit “event” to upstart init daemon?

]]> By: Ian http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-25 Ian Sat, 27 Jan 2007 16:04:22 +0000 #comment-25 While this is probably old news to most I just discovered it when a friend came to me worried that his new installation of Ubuntu was borked because he couldnt find /etc/init.d. He was putting off rebooting because of this fear that the system would never boot again. Long story short this page is one of the first things I found trying to compare upstart to launchd and init. 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 this is probably old news to most I just discovered it when a friend came to me worried that his new installation of Ubuntu was borked because he couldnt find /etc/init.d. He was putting off rebooting because of this fear that the system would never boot again. Long story short this page is one of the first things I found trying to compare upstart to launchd and init.

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.

]]> By: Pablo http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-24 Pablo Mon, 30 Oct 2006 10:28:04 +0000 #comment-24 As far as I understand, common scripts as sysvconfig or ksysv will not work anymore with upstart? As far as I understand, common scripts as sysvconfig or ksysv will not work anymore with upstart?

]]> By: Jim http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-23 Jim Fri, 06 Oct 2006 02:59:32 +0000 #comment-23 Re: Doug 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. Re: Doug

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.

]]> By: Jim http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-22 Jim Fri, 06 Oct 2006 02:59:14 +0000 #comment-22 Re: Doug 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. Re: Doug

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.

]]> By: Jim http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-21 Jim Fri, 06 Oct 2006 02:59:04 +0000 #comment-21 Re: Doug 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. Re: Doug

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.

]]> By: Doug Goldstein http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-20 Doug Goldstein Mon, 02 Oct 2006 16:49:10 +0000 #comment-20 You're contradicting yourself a bit. You're saying upstart replaces init, cron, inetd, and possibly other daemons. However further down your argument against using D-BUS is the classic UNIX argument of do one thing and do it right. No reason to fold everything into "init". You’re contradicting yourself a bit. You’re saying upstart replaces init, cron, inetd, and possibly other daemons. However further down your argument against using D-BUS is the classic UNIX argument of do one thing and do it right. No reason to fold everything into “init”.

]]> By: Lars http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-19 Lars Fri, 29 Sep 2006 08:28:53 +0000 #comment-19 Hi, this concept seems a good replacement for the olde init procedure. But what about the runlevels? Will they survive the init compatibility? Means: When the compatibility of init isn't needed anymore, are there different runlevels left? Or does this have to be realized and managed by event scripts? Thanks Lars Hi,

this concept seems a good replacement for the olde init procedure.
But what about the runlevels?
Will they survive the init compatibility?
Means: When the compatibility of init isn’t needed anymore, are there different runlevels left? Or does this have to be realized and managed by event scripts?

Thanks
Lars

]]> By: Rafael Peregrino http://www.netsplit.com/2006/08/26/upstart-in-universe/#comment-18 Rafael Peregrino Fri, 29 Sep 2006 00:28:50 +0000 #comment-18 Hi Scott, Please have a look at runit and DJB Daemontools. I think they are also very good tools for replacing init. * runit was created by Debian Developer Gerrit Pape: http://smarden.org/runit/ * DJB Daemontools can be found at: http://cr.yp.to/daemontools.html Best regards, Rafael Peregrino da Silva Editor in Chief Linux Magazine Brasil Hi Scott,

Please have a look at runit and DJB Daemontools. I think they are also very good tools for replacing init.

* runit was created by Debian Developer Gerrit Pape:

http://smarden.org/runit/

* DJB Daemontools can be found at:

http://cr.yp.to/daemontools.html

Best regards,

Rafael Peregrino da Silva
Editor in Chief
Linux Magazine Brasil

]]>