Moved this to be an Upstream bug.
I think that the most probably implementation will be that you declare
chroots in /etc/init.conf that you wish the init daemon to manage. init
will then also look in CHROOT/etc/init for jobs, and record these as
belonging to that chroot. All actions on these jobs will first result
in the chroot() to the right location.
To figure out still is how to make sure that "start apache" within a
chroot, starts the apache within the chroot and not the one outside.
It makes sense that "initctl list" only shows the jobs in your chroot
(or the real system).
The difficult bit is going to be dealing with things like events; I
think logically events are global (you can only have one udev running) -
but this means that "started apache" is an event - and that means
chroots won't necessarily work right?
** Summary changed:
- misc: packages cannot be upgraded in a chroot
+ init: support chroots
** Also affects: upstart
Importance: Undecided
Status: New
** Changed in: upstart
Status: New => Triaged
** Changed in: upstart
Importance: Undecided => Wishlist
** Changed in: upstart (Ubuntu)
Status: Confirmed => Invalid
--
init: support chroots
https://bugs.launchpad.net/bugs/430224
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
