doesn't deal with init scripts that require user input

-------- Forwarded Message --------
From: Thom May <email address hidden>
To: <email address hidden>
Subject: Re: User Survey
Date: Sun, 3 Sep 2006 15:57:54 +0100

Hey,
* Scott James Remnant (<email address hidden>) wrote :
> Hi there to everyone that's joined recently,
>
> I'd like to do a quick survey to see who here is using upstart on their
> machine instead of sysvinit, and how they're getting on with it?
>

I just switched my laptop over. Some notes based on that:

My /home is a cryptdisk setup - I'm usually prompted for a passphrase during
boot by /etc/init.d/cryptdisks but this didn't occur when booting with
upstart. (Do you want bugs filed for this in launchpad?)

My wireless is WPA'd and that didn't come up - I'm using the new style wpa
configuration via /etc/network/interfaces

Besides that, it all seemed to work pretty nicely. (although getting a
login prompt on a VT that early was something of a shock :-) )

Cheers,
-Thom

_______________________________________________
upstart-devel mailing list
<email address hidden>
http://lists.netsplit.com/mailman/listinfo/upstart-devel
--
Scott James Remnant
<email address hidden>

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

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.

Fixed with cryptsetup 1.0.3-3ubuntu3

hi, I have Edgy, and cryptodisks seems to doesn't not work.
It says Key reading error at boot.
I have upstart 0.2.7-7 so, that proposed patch doesn't fix my problem. I tried to reinstall upstart, but this doesn't not help me.

Please see the cryptdisk bug page