[Bug 430224] Re: init: support chroots

[Rolf Leggewie]

When we talk about releases we need to carefully differentiate whether
we talk about host or guest.  I'm usually more concerned about the guest
side of things.  If you have control over the host your options are
obviosly much better.  Although thinking about it, it's not really
pretty, either, I guess.  Because if I understand the comments here
correctly then none of the currently available LTS are candidates for
hosting a bunch of vservers because of problems with upstart.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/430224

Title:
  init: support chroots

Status in Release Notes for Ubuntu:
  Fix Released
Status in Upstart:
  Fix Released
Status in “upstart” package in Ubuntu:
  Fix Released
Status in “upstart” source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: upstart

  $ sudo chroot /media/karmic dpkg --configure -a
  Setting up cups (1.4.1-1) ...
  update-rc.d: warning: /etc/init.d/cups missing LSB information
  update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
  Rather than invoking init scripts through /etc/init.d, use the service(8)
  utility, e.g. service cups start

  Since the script you are attempting to invoke has been converted to an
  Upstart job, you may also use the start(8) utility, e.g. start cups
  start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused
  invoke-rc.d: initscript cups, action "start" failed.
  dpkg: error processing cups (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   cups

  
  WORKAROUND: Create an executable /media/karmic/usr/sbin/policy-rc.d with this in it:
  #!/bin/sh
  exit 101

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/430224/+subscriptions