Clean upstart for factory test

Clean upstart for factory test
* Leave ui.conf there, not run by default.
* dump autotest log into /dev/tty1
* Don't let tty1 eat keayboard events.

[Tom Wai-Hong Tam, 2010-04-30 02:45:30]

LGTM. It's great that easily to see the autotest output.

http://codereview.chromium.org/1742018/diff/1/3
File src/scripts/mod_for_factory_scripts/200patchInitScript (right):

http://codereview.chromium.org/1742018/diff/1/3#newcode18
src/scripts/mod_for_factory_scripts/200patchInitScript:18: +# start on stopping
startup
I don't think it's necessary to keep it as comment.

http://codereview.chromium.org/1742018/diff/1/3#newcode34
src/scripts/mod_for_factory_scripts/200patchInitScript:34: +# start on
login-prompt-ready
Same as above.

http://codereview.chromium.org/1742018/diff/1/3#newcode75
src/scripts/mod_for_factory_scripts/200patchInitScript:75: tail -F
/var/log/factory.log > /dev/tty1
"tail -n 48 -F /var/log/factory.log > /dev/tty1" looks like resuming the
previous screen after reboot.

[Tammo Spalink, 2010-04-30 03:28:34]

Yes, very nice.

On 2010/04/30 02:45:30, Tom Wai-Hong Tam wrote:
> LGTM. It's great that easily to see the autotest output.
> 
> http://codereview.chromium.org/1742018/diff/1/3
> File src/scripts/mod_for_factory_scripts/200patchInitScript (right):
> 
> http://codereview.chromium.org/1742018/diff/1/3#newcode18
> src/scripts/mod_for_factory_scripts/200patchInitScript:18: +# start on
stopping
> startup
> I don't think it's necessary to keep it as comment.
> 
> http://codereview.chromium.org/1742018/diff/1/3#newcode34
> src/scripts/mod_for_factory_scripts/200patchInitScript:34: +# start on
> login-prompt-ready
> Same as above.
> 
> http://codereview.chromium.org/1742018/diff/1/3#newcode75
> src/scripts/mod_for_factory_scripts/200patchInitScript:75: tail -F
> /var/log/factory.log > /dev/tty1
> "tail -n 48 -F /var/log/factory.log > /dev/tty1" looks like resuming the
> previous screen after reboot.

[kmixter1, 2010-04-30 19:20:12]

LGTM

http://codereview.chromium.org/1742018/diff/1/3
File src/scripts/mod_for_factory_scripts/200patchInitScript (right):

http://codereview.chromium.org/1742018/diff/1/3#newcode19
src/scripts/mod_for_factory_scripts/200patchInitScript:19: +start on never
Isn't having no start on stanza equivalent?

http://codereview.chromium.org/1742018/diff/1/3#newcode75
src/scripts/mod_for_factory_scripts/200patchInitScript:75: tail -F
/var/log/factory.log > /dev/tty1
So text mode is up on VT1 until X is started?  Who starts X now that keyboard
test I know does not?

[Nick Sanders, 2010-05-04 03:41:26]

http://codereview.chromium.org/1742018/diff/1/3
File src/scripts/mod_for_factory_scripts/200patchInitScript (right):

http://codereview.chromium.org/1742018/diff/1/3#newcode19
src/scripts/mod_for_factory_scripts/200patchInitScript:19: +start on never
On 2010/04/30 19:20:12, kmixter1 wrote:
> Isn't having no start on stanza equivalent?

Not sure, but this makes it clear on first glance that ui.conf will not start

http://codereview.chromium.org/1742018/diff/1/3#newcode75
src/scripts/mod_for_factory_scripts/200patchInitScript:75: tail -F
/var/log/factory.log > /dev/tty1
On 2010/04/30 19:20:12, kmixter1 wrote:
> So text mode is up on VT1 until X is started?  Who starts X now that keyboard
> test I know does not?

The keyboard test still starts X, as of now. Tammo is working on pulling out X
start into upstart.