[21:30] <soren> How does upstart determine if it's being run in a chroot? AIUI, it's meant to start upstart if it's run as root inside a chroot, but that doesn't seem to be happening. Instead it just seems to try to connect to an existing upstart instance (which fails, since it's a chroot on an Android device )
[21:39] <soren> Oh, is it perhaps not supposed to run a new upstart, but simply allow it to run jobs in the "system" upstart in a contained fashion?