init: cannot be run as a PID other than 1
sysvinit supports --init to make it operate as if it's pid 1 even if it's not pid 1. Upstart not only doesn't support this functionality, but it dies if it receives parameters that it doesn't understand.
My use case: The OLPC has a special process that does a bunch of boot and security stuff before kicking off /sbin/init. With sysvinit and --init, this works fine. If Upstart is installed, it errors out with: "init: invalid option: --init"
Thus, if using an Ubuntu image on an OLPC, you must replace Upstart with sysvinit, which has an impact on various levels of Ubuntu integration work. :-)
There are quite a few other use cases, from the clever to the crack-addled, so it would be nice to fix this for Upstart.
|Scott James Remnant (Canonical) (canonical-scott) wrote : Re: upstart cannot be run as a PID other than 1||#7|
|Changed in upstart:|
|importance:||Undecided → Wishlist|