Boot messages in 2.6.8-524

[David Zeuthen]

On Sat, 2004-08-21 at 07:08 -0700, Steve G wrote:
> Aug 21 09:00:15 buildhost kernel: md: md driver 0.90.0 MAX_MD_DEVS=256,
> MD_SB_DISKS=27
> Aug 21 09:00:15 buildhost hal.hotplug[1684]: error sending message to hald
> Aug 21 09:00:15 buildhost kernel: NET: Registered protocol family 2
> Aug 21 09:00:15 buildhost kernel: IP: routing cache hash table of 2048 buckets,
> 64Kbytes
> Aug 21 09:00:15 buildhost kernel: TCP: Hash tables configured (established 262144
> bind 37449)
> 
> Hmmm something failed to send a message to hald. What was the dbus & hald boot
> priority?
> 

I'll probably remove that message from hal.hotplug.

> Aug 21 09:00:18 buildhost crond: crond startup succeeded
> Aug 21 09:00:18 buildhost anacron: anacron startup succeeded
> Aug 21 09:00:19 buildhost messagebus: messagebus startup succeeded
> Aug 21 09:00:19 buildhost haldaemon: haldaemon startup succeeded
> 
> OK, way down here at the very end haldaemon is active. Isn't this way late?
> 

Not really; the hal daemon probes sysfs when starting up (the equivalent
of 'coldplugging') so there is no need to move haldaemon (and it's
dependency messagebus) to an earlier stage until other initscripts needs
it (or an /etc/fstab that matches the installed drives since the
haldaemon invokes fstab-sync).

David