init: support chroots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Release Notes for Ubuntu |
Fix Released
|
Undecided
|
Unassigned | ||
upstart |
Fix Released
|
Wishlist
|
James Hunt | ||
upstart (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Karmic |
Won't Fix
|
Medium
|
Unassigned |
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://
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/
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/
#!/bin/sh
exit 101
Changed in upstart (Ubuntu Karmic): | |
importance: | Undecided → High |
milestone: | none → ubuntu-9.10-beta |
status: | New → Triaged |
summary: |
- blows up package upgrades in a chroot + misc: packages cannot be upgraded in a chroot |
Changed in upstart (Ubuntu Karmic): | |
milestone: | ubuntu-9.10-beta → none |
importance: | High → Medium |
Changed in upstart (Ubuntu): | |
status: | Triaged → Won't Fix |
security vulnerability: | no → yes |
visibility: | public → private |
security vulnerability: | yes → no |
visibility: | private → public |
Changed in upstart: | |
status: | Triaged → In Progress |
assignee: | nobody → James Hunt (jamesodhunt) |
Changed in upstart: | |
status: | In Progress → Fix Released |
yes.... I also have this issue:
start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/ upstart: Connection refused
In fact how to fix it?