upstart as init in a chroot

[Brian J. Murrell]

On Sun, 2007-25-03 at 18:37 +0100, Scott James Remnant wrote:

Much appreciate the response.  Thanx!

> This is not possible.
> 
> Upstart relies on being process #1 for various features to work, and
> expects to be granted the special handling that the kernel gives to that
> process.

Ahhh.  The kernel handles process #1 specially?  I did not realize this.
I thought it was more just "convention" that init got pid #1 (by nature
that it is the first process started.  What kind of special handling
does process #1 get from the kernel.  Feel free to just point to kernel
source and I can get into reading it if you like.

> In the future, we may allow for "stripped down" handling; without
> various useful features, possibly by communication with the real init,
> but this isn't on the cards any time soon.

What kind of useful features do you think would have to be missing from
an upstart init running in a chroot?

I guess it just seems entirely useful to be able to start a whole linux
system in a chroot by just calling it's init rather than having to start
everything you want to start in the chroot process by process.

b.

-- 
My other computer is your Microsoft Windows server.

Brian J. Murrell
-------------- 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/20070325/e4e6d104/attachment-0001.pgp