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
** Changed in: upstart (Ubuntu)
Importance: Untriaged => Medium
Assignee: (unassigned) => Scott James Remnant
Status: Unconfirmed => Confirmed
--
doesn't deal with init scripts that require user input
https://launchpad.net/bugs/58794
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
