[10:56] <lcapriotti> hi, I'm trying to exec a text-based installer when system has completed booting: http://www.friendpaste.com/1DWFdkL9xtCR9mBXF5XQZL
[10:56] <lcapriotti> but the text installer cannot accept inputs
[10:57] <lcapriotti> the login prompt is shown instead, superimposed with installer text output
[10:57] <mgoetze> well, you should tell your login job not to start until the installer is done, of course
[10:58] <mgoetze> and then you'll want something like "exec < /dev/console" in your script
[10:59] <lcapriotti> what is I don't want/can't modify the tty1 upstart job?
[10:59] <lcapriotti> would something like exec su -c "myInstaller" -l work?
[11:03] <ion> exec openvt command
[11:04] <lcapriotti> pls speculate
[11:19] <lcapriotti> ion: exec openvt -s command worked, tks a lot!
[15:39] <kindjal> Is there a target date for upstart 0.10 (even roughly)?  I'm interested in the "automatic" and "manual" feature being discussed for the 0.10 release.
[15:41] <sadmac2> kindjal: its kind of in "when its done" mode, but I think we'd like to have it in the next 6 months
[15:41] <sadmac2> well, we'd like to have it today, and release dates are meant to be broken, but...
[15:42] <kindjal> Understood.  "it's done when it's done" is very understandable... I was just curious as to where it stood.  Thanks.
[15:43] <kindjal> If I require a "chkconfig" like functionality for upstart, am I thus sort of stuck with a "link job files into /etc/init" until then?
[15:47] <kindjal> By "chkconfig" I guess I really mean just "enable/disable" a job
[15:52] <sadmac2> kindjal: yes. though that's what chkconfig is anyway :)
[15:52] <kindjal> Yes... but upstart could eliminate the concept of "runlevel" which is sort of chkconfig's focus.