Clean upstart for factory test

src/scripts/mod_for_factory_scripts/200patchInitScript

 #!/bin/bash
 
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 echo "Applying patch to init scripts."
 pushd ${ROOT_FS_DIR}
 
 patch -d ${ROOT_FS_DIR} -Np1 <<EOF
+--- old/etc/init/ui.conf        2010-04-28 21:28:38.886069000 -0700
++++ new/etc/init/ui.conf        2010-04-28 21:29:42.676163000 -0700
+@@ -5,7 +5,8 @@
+ description   "Chrome OS user interface"
+ author        "chromium-os-dev@googlegroups.com"
+ 
+-start on stopping startup
++# start on stopping startup

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

I don't think it's necessary to keep it as comment.

++start on never

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

Isn't having no start on stanza equivalent?

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

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

+ stop on starting halt or starting reboot
+ 
+ respawn
+EOF
+
+patch -d ${ROOT_FS_DIR} -Np1 <<EOF
 diff -Naur old/etc/init/dump-boot-stats.conf new/etc/init/dump-boot-stats.conf
---- old/etc/init/dump-boot-stats.conf   2010-04-05 21:33:11.000000000 -0700
-+++ new/etc/init/dump-boot-stats.conf   2010-04-05 21:00:48.000000000 -0700
-@@ -7,7 +7,7 @@
+--- old/etc/init/dump-boot-stats.conf   2010-04-28 21:35:33.785340000 -0700
++++ new/etc/init/dump-boot-stats.conf   2010-04-28 21:36:28.819984000 -0700
+@@ -7,7 +7,8 @@
  # when login-prompt-ready is received, grabs the current uptime and
  # disk stats.  Also sends uptime to metrics client for perf dashboard
  
 -start on login-prompt-ready
++# start on login-prompt-ready

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

Same as above.

 +start on stopping startup
  
  # This is run-once rather than a service.
  task
 EOF
 
 cat > ${ROOT_FS_DIR}/etc/init/factory.conf <<EOF
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 description   "Chrome OS factory startup stub"
 author        "chromium-os-dev@googlegroups.com"
 
-start on stopping autotest
-
-script
-
-cd /usr/local/autotest
-if [ ! -e factory_started ]; then
-  touch factory_started
-  date >> /var/log/factory.log
-  cp -f site_tests/suite_Factory/control.full control
-  ./bin/autotest control >> /var/log/factory.log 2>&1
-fi
-end script
-EOF
-
-cat > ${ROOT_FS_DIR}/etc/init/autotest.conf <<EOF
-# Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
-# Use of this source code is governed by a BSD-style license that can be
-# found in the LICENSE file.
-
-description   "Chrome OS autotest startup stub"
-author        "chromium-os-dev@googlegroups.com"
-
 start on started udev
 
 script
-# Sleep as the current upstart sequence gives no clear completion signal.
-# TODO: investigate generating authoritative bootup finished event.
-sleep 10
+
 cd /usr/local/autotest
 date >> /var/log/factory.log
-./tools/autotest >> /var/log/factory.log 2>&1
+if [ ! -e factory_started ]; then
+  touch factory_started
+  cp -f site_tests/suite_Factory/control.full control
+  ./bin/autotest control >> /var/log/factory.log 2>&1
+else
+  ./tools/autotest >> /var/log/factory.log 2>&1
+fi
 end script
 EOF
 
-cat > ${ROOT_FS_DIR}/etc/init/tty1.conf <<EOF
+cat > ${ROOT_FS_DIR}/etc/init/factorylog.conf <<EOF
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-start on startup
+start on started factory
 stop on starting halt or starting reboot
 
 respawn
 script
-cd /
-/sbin/agetty 38400 tty1 linux -l /bin/bash -n
+tail -F /var/log/factory.log > /dev/tty1

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

"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]

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]

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

 end script
 EOF
 
 patch -d ${ROOT_FS_DIR} -Np1 <<EOF
 diff -Naur old/sbin/chromeos_startup new/sbin/chromeos_startup
 --- old/sbin/chromeos_startup   2010-04-05 21:33:52.000000000 -0700
 +++ new/sbin/chromeos_startup   2010-04-05 21:38:02.000000000 -0700
 @@ -20,18 +20,12 @@
  
  # Moblin trick: Disable blinking cursor. Without this a splash screen
@@ skipping 10 matching lines @@
 -then
 -  /usr/bin/ply-image /usr/share/chromeos-assets/images/login_splash.png &
 -fi
 -
  mount -n -t tmpfs tmp /tmp
  mount -n -t tmpfs -onosuid,nodev shmfs /dev/shm
  mount -n -t devpts -onoexec,nosuid,gid=5,mode=0620 devpts /dev/pts
 EOF
 
 popd