[Bug 74664] Re: Boot parameters not passed to init scripts

2008-10-31 Thread Scott James Remnant
Still affects Ubuntu ** Changed in: upstart (Ubuntu) Status: Invalid => Triaged -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs m

[Bug 74664] Re: Boot parameters not passed to init scripts

2008-08-13 Thread Scott James Remnant
** Changed in: upstart Status: Fix Committed => Fix Released -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-b

[Bug 74664] Re: Boot parameters not passed to init scripts

2008-03-07 Thread Scott James Remnant
This was committed in trunk a while back with the new environment code. ** Changed in: upstart Status: Triaged => Fix Committed -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notification because you are a member of Ubuntu Bugs, w

[Bug 74664] Re: Boot parameters not passed to init scripts

2007-10-08 Thread Scott James Remnant
The intent is that the job should be able to specify "env PATH TERM" etc. (ie. without values) and have those passed through. ** Changed in: upstart Status: Confirmed => Triaged -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notif

[Bug 74664] Re: Boot parameters not passed to init scripts

2007-06-14 Thread Scott James Remnant
** Changed in: upstart (upstream) Target: 0.3 => 0.5 -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bug

[Bug 74664] Re: Boot parameters not passed to init scripts

2007-05-23 Thread Scott James Remnant
Rejecting the Ubuntu portion of this bug, since it's an upstream problem ** Changed in: upstart (Ubuntu) Status: Confirmed => Rejected -- Boot parameters not passed to init scripts https://bugs.launchpad.net/bugs/74664 You received this bug notification because you are a member of Ubuntu

[Bug 74664] Re: Boot parameters not passed to init scripts

2007-03-20 Thread Scott James Remnant
** Changed in: upstart (upstream) Assignee: Scott James Remnant => (unassigned) -- Boot parameters not passed to init scripts https://launchpad.net/bugs/74664 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 74664] Re: Boot parameters not passed to init scripts

2007-02-06 Thread Scott James Remnant
Not wishlist: this functionality existed in sysvinit ** Changed in: upstart (Ubuntu) Importance: Undecided => Wishlist ** Changed in: upstart (upstream) Importance: Wishlist => Low ** Changed in: upstart (Ubuntu) Importance: Wishlist => Low -- Boot parameters not passed to init script

[Bug 74664] Re: Boot parameters not passed to init scripts

2006-12-09 Thread Jonathan Watts
I can confirm this bug. It's causing problems with my dual boot setup (native Kubuntu or Kubuntu under coLinux on WinXP), as I was relying on passing a COLINUX variable to my colinux script so I can use the correct set of config files (fstab, network/interfaces, etc.). ** Changed in: upstart (Ubu

[Bug 74664] Re: Boot parameters not passed to init scripts

2006-12-07 Thread Scott James Remnant
These boot parameters are set by the kernel in the environment of init. While upstart does have a goal to make the environment of its jobs consistent, it should be possible for a job to say which environment variables it wants to receive. So just like we pass PATH and TERM from the kernel, we sho