Environment Variables passed to init?

[Scott James Remnant]

On Tue, 2007-10-30 at 13:37 +0100, Wolf Paul wrote:

> Please pardon me if this list is not the proper venue for this
> question; I could not figure out a more appopriate place to ask it.
> 
> In the past, on SysV-Init based Linux distros I managed to set up my
> notebook to boot into different networking and other environments by
> setting up multiple entries in Grub for the various locations, with
> LOCATION=xxxx appended to the kernel parameter line. 
> 
> This would get passed to init as an environment variable, so that
> in /etc/rc.d/rc.sysinit I could
> call an appropriate script to set up networking and other aspects of
> the required environment for
> that location. 
> 
> It seems to me that the Upstart "init" does not pass such environment
> variables to the scripts it calls, and thus this method of setting up
> a location-dependent boot environment no longer works.
> 
> Is this observation correct? 
> 
It is correct; though it should be possible to specify in a job's
definition which environment variables you *do* what passed through.
This is to allow jobs to ensure consistent environments to run in.

Scott
-- 
Have you ever, ever felt like this?
Had strange things happen?  Are you going round the twist?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/upstart-devel/attachments/20071030/0624416c/attachment.pgp