Add boot-services milestone marker for boot; fixed udev-addon init time.

boot-services.conf

Index: boot-services.conf
diff --git a/boot-services.conf b/boot-services.conf
new file mode 100644
index 0000000000000000000000000000000000000000..1e840d87cc8ae3b92c753b2021ede0ca7de16545
--- /dev/null
+++ b/boot-services.conf
@@ -0,0 +1,27 @@
+# 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     "Job to trigger boot services"
+author          "chromium-os-dev@chromium.org"
+
+# This job is used as a milestone marker for jobs that are run at
+# system boot right after chromeos_startup.
+#
+# Specifically, tasks that should start right after chromeos_startup should
+# use syntax like:
+#   start on starting boot-services
+#
+# Tasks that want to wait for all boot services to be finished should use

[jrbarnette, 2011/04/20 00:04:39]

s/finished/ready/

[diandersAtChromium, 2011/04/20 16:10:02]

Done.

+# syntax like:
+#   start on started boot-services
+#
+# TODO(dianders): Should anyone use a 'stop on' for boot-services?

[jrbarnette, 2011/04/20 00:04:39]

Yes, the syslog, dbus, and udev jobs should all say this:
  start on starting boot-services
  stop on stopping boot-services

The comment above (line 13) should say so.  You can then delete
the TODO.

[diandersAtChromium, 2011/04/20 16:10:02]

Done.

+
+# In startup.conf we see "telinit 2", which kicks us off.
+start on runlevel 2

[jrbarnette, 2011/04/20 00:04:39]

Add here the standard 'stop on' boilerplate:
  stop on starting halt or starting reboot

[diandersAtChromium, 2011/04/20 16:10:02]

Done.

+
+
+# We purposely omit the main process.  upstart marks us running
+# on the first event, and ignores all subsequent events until we
+# stop.