Generated.

[homepage.git] / blog / data / 2010-06-06-upstart.txt

diff --git a/blog/data/2010-06-06-upstart.txt b/blog/data/2010-06-06-upstart.txt
index eb12f3b925460aa1213b09bca1e25974e916f092..57b0260925df56e0ae8e6939e71dfb691376dcee 100644 (file)
--- a/blog/data/2010-06-06-upstart.txt
+++ b/blog/data/2010-06-06-upstart.txt
@@ -1,17 +1,18 @@
 Title: Upstart or sysvinit - as init.d scripts see it
-Tags: english, debian, debian edu
+Tags: english, debian, bootsystem
 Date: 2010-06-06 23:55
 
 <p>If Debian is to migrate to upstart on Linux, I expect some init.d
-scripts to migrate (some of) their operations to upstart, and will
-need a way to behave differently when used with sysvinit and with
-upstart.  Because of this, I had a look at the environment variables
-set when a init.d script is running under upstart, and when it is
-not.</p>
+scripts to migrate (some of) their operations to upstart job while
+keeping the init.d for hurd and kfreebsd.  The packages with such
+needs will need a way to get their init.d scripts to behave
+differently when used with sysvinit and with upstart.  Because of
+this, I had a look at the environment variables set when a init.d
+script is running under upstart, and when it is not.</p>
 
-<p>With upstart, I notice these environment variables are set like
-this for a script started from rcS.d/ (ignoring some irrelevant
-ones):</p>
+<p>With upstart, I notice these environment variables are set when a
+script is started from rcS.d/ (ignoring some irrelevant ones like
+COLUMNS):</p>
 
 <blockquote><pre>
 DEFAULT_RUNLEVEL=2
@@ -36,7 +37,7 @@ runlevel=S
 </pre></blockquote>
 
 <p>The RUNLEVEL and PREVLEVEL environment variables passed on from
-sysvinit is not set by upstart.  Not sure if it is intentional or not
+sysvinit are not set by upstart.  Not sure if it is intentional or not
 to not be compatible with sysvinit in this regard.</p>
 
 <p>For scripts needing to behave differently when upstart is used,