| 2006-09-04 02:05:35 |
Sebastian Dröge |
bug |
|
|
added bug |
| 2006-09-04 02:05:49 |
Sebastian Dröge |
bug |
|
|
assigned to cryptsetup (Ubuntu) |
| 2006-09-04 02:07:17 |
Scott James Remnant (Canonical) |
bug |
|
|
added subscriber Thom May |
| 2006-09-04 02:09:30 |
Scott James Remnant (Canonical) |
upstart: status |
Unconfirmed |
Confirmed |
|
| 2006-09-04 02:09:30 |
Scott James Remnant (Canonical) |
upstart: importance |
Untriaged |
Medium |
|
| 2006-09-04 02:09:30 |
Scott James Remnant (Canonical) |
upstart: statusexplanation |
|
It's not so much that upstart "doesn't deal" with init scripts that require user input, the daemon itself is perfectly capable of providing jobs with a console if they need it. You just have to put "console output" in the job description file.
However by policy for edgy (due to the boot-message-logging spec) we're not expecting to provide output for most init scripts.
cryptsetup already has a method of dealing with usplash, as it has to get that out of the way, so it does not seem unreasonable that it also should have a method of dealing with upstart
Given we are talking about filesystems here, and the filesystem-handling init scripts are due to be changed into upstart jobs, perhaps cryptsetup should get the same treatment |
|
| 2006-09-04 02:09:30 |
Scott James Remnant (Canonical) |
upstart: assignee |
|
keybuk |
|
| 2006-09-06 20:50:03 |
Scott James Remnant (Canonical) |
upstart: status |
Confirmed |
Fix Committed |
|
| 2006-09-06 20:50:03 |
Scott James Remnant (Canonical) |
upstart: statusexplanation |
It's not so much that upstart "doesn't deal" with init scripts that require user input, the daemon itself is perfectly capable of providing jobs with a console if they need it. You just have to put "console output" in the job description file.
However by policy for edgy (due to the boot-message-logging spec) we're not expecting to provide output for most init scripts.
cryptsetup already has a method of dealing with usplash, as it has to get that out of the way, so it does not seem unreasonable that it also should have a method of dealing with upstart
Given we are talking about filesystems here, and the filesystem-handling init scripts are due to be changed into upstart jobs, perhaps cryptsetup should get the same treatment |
|
|
| 2006-09-06 20:50:10 |
Scott James Remnant (Canonical) |
cryptsetup: status |
Unconfirmed |
Confirmed |
|
| 2006-09-06 20:50:10 |
Scott James Remnant (Canonical) |
cryptsetup: assignee |
|
keybuk |
|
| 2006-09-06 20:50:10 |
Scott James Remnant (Canonical) |
cryptsetup: statusexplanation |
|
|
|
| 2006-09-06 21:15:20 |
Scott James Remnant (Canonical) |
upstart: status |
Fix Committed |
Fix Released |
|
| 2006-09-06 21:15:20 |
Scott James Remnant (Canonical) |
upstart: statusexplanation |
|
This is a "patch" fix that corrects the problem in the short term, the long term solution is to fix cryptsetup so it obtains a tty itself, or something.
upstart (0.2.1-6) edgy; urgency=low
.
* Make packages Essential, and change Depends to Pre-Depends so that the
packages work when unconfigured (nothing interesting is performed in
postinst). Ubuntu: #59005.
* Sync priority in debian/control with that in the archive (required)
* Drop warning of dire consequences if you install upstart, seeing as it's
installed by default.
.
* Add new startup-tasks and system-services packages which will contain
the /etc/event.d files themselves (other than the main ones).
* Move tty definitions into system-services.
* Modify tty definitions to start when the rcS task has finished. This
puts them in the "right" place when compared to gdm. Ubuntu: #58630.
.
* Correct rcS compatibility script to ignore any information in utmp so
that all scripts are always run. Ubuntu: #59203.
* Make rcS the console owner while it runs, temporary fix for
Ubuntu: #58609, #58794, #58796
* Include default control-alt-delete handler that reboots the machine. |
|
| 2006-09-21 02:06:29 |
Scott James Remnant (Canonical) |
cryptsetup: status |
Confirmed |
Fix Released |
|
| 2006-09-21 02:06:29 |
Scott James Remnant (Canonical) |
cryptsetup: statusexplanation |
|
Fixed with cryptsetup 1.0.3-3ubuntu3 |
|
| 2006-11-23 10:47:58 |
Ondřej Nový |
upstart: status |
Fix Released |
Confirmed |
|
| 2006-11-23 10:47:58 |
Ondřej Nový |
upstart: statusexplanation |
This is a "patch" fix that corrects the problem in the short term, the long term solution is to fix cryptsetup so it obtains a tty itself, or something.
upstart (0.2.1-6) edgy; urgency=low
.
* Make packages Essential, and change Depends to Pre-Depends so that the
packages work when unconfigured (nothing interesting is performed in
postinst). Ubuntu: #59005.
* Sync priority in debian/control with that in the archive (required)
* Drop warning of dire consequences if you install upstart, seeing as it's
installed by default.
.
* Add new startup-tasks and system-services packages which will contain
the /etc/event.d files themselves (other than the main ones).
* Move tty definitions into system-services.
* Modify tty definitions to start when the rcS task has finished. This
puts them in the "right" place when compared to gdm. Ubuntu: #58630.
.
* Correct rcS compatibility script to ignore any information in utmp so
that all scripts are always run. Ubuntu: #59203.
* Make rcS the console owner while it runs, temporary fix for
Ubuntu: #58609, #58794, #58796
* Include default control-alt-delete handler that reboots the machine. |
|
|
| 2006-11-23 11:00:01 |
Scott James Remnant (Canonical) |
upstart: status |
Confirmed |
Rejected |
|
| 2006-11-23 11:00:01 |
Scott James Remnant (Canonical) |
upstart: statusexplanation |
|
Please see the cryptdisk bug page |
|
