Comment 7 for bug 553374

Ah yes, the --verbose boot. Here's all the output in the surviving backscroll when I do that on the latest Lucid kernel (I don't suppose there's any way to copy this stuff directly under the circumstances):

{{{
init: ureadahead main process (377) became new process (380)
init: ureadahead state changed from spawned to post-start
init: ureadahead state changed from post-start to running
init: mountall state changed from starting to pre-start
init: mountall state changed from pre-start to spawned
init: mountall main process (381)
init: Handling started event
init: mountall main process (381) executable changed
init: Connection from private client
init: mountall main process (381) became new process (382)
init: mountall main process (382) became new process (383)
init: mountall state changed from spawned to post-start
init: mountall state changed from post-start to running
init: Handling started event
init: Handling mounted event
init: Handling mounted event
init: Handling mounted event
init: mounted-dev goal changed from stop to start
init: mounted-dev state changed from waiting to starting
init: Handling starting event
init: mounted-dev state changed from starting to pre-start
init: mounted-dev state changed from pre-start to spawned
init: mounted-dev main process (384)
init: mounted-dev state changed from spawned to post-start
init: mounted-dev state changed from post-start to running
init: Handling started event
init: mounted-dev main process (384) exited normally
init: mounted-dev goal changed from start to stop
init: mounted-dev state changed from running to stopping
init: Handling stopping event
init: mounted-dev state changed from stopping to killed
init: mounted-dev state changed from killed to post-stop
init: mounted-dev state changed from post-stop to waiting
init: Handling stopped event
init: Handling mounted event
init: Handling mounted event
init: Handling mounting event
init: Handling mounted event
init: Handling mounting event
init: Handling mounted event
init: Handling mounting event
init: Handling mounted event
init: Handling mounting event
init: Handling mounted event
init: Handling mounting event
init: Handling mouninit: Handling module-device-added event
init: Handling drivers-device-added event
init: Handling pci-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-added event
init: Handling sound-device-changed event
init: udevtrigger post-stop process (458) exited normally
init: udevtrigger state changed from post-stop to waiting
init: Handling stopped event
init: udevmonitor goal changed from start to stop
init: udevmonitor state changed from running to pre-stop
init: udevmonitor state changed from pre-stop to stopping
init: Handling stopping event
init: udevmonitor state changed from stopping to killed
init: Sending TERM signal to udevmonitor main process (433)
init: udevmonitor main process (433) exited normally
init: udevmonitor state changed from killed to post-stop
init: udevmonitor state changed from post-stop to waiting
init: Handling stopped event
init: plymouth-splash main process (962) exited normally
init: plymouth-splash goal changed from start to stop
init: plymouth-splash state changed from running to stopping
init: Handling stopping event
init: plymouth-splash state changed from stopping to killed
init: plymouth-splash state changed from killed to post-stop
init: plymouth-splash state changed from post-stop to waiting
init: Handling stopped event
}}}

(The "mouninit" was spelled sic... is it an un-init of some kind?)