hardware initialization

Hi,

I have thought a bit about our scheme of hardware initialization, and suggest
the follwoing changes to enhance our udev support:

1. system.init: use /sbin/udevsend as kernel hotplug mechanism (instead of
					hotplug)
                don't call hotplug scripts (use hotplug.init)
				don't configure kernel by calling /etc/conf/kernel (goes into
					kernel.init)
2. pcmcia.init: reschedule after udevd.init
3. hotplug.init: reschedule right after udevd.init
4. kernel.init: call /etc/conf/kernel

So we have this workflow:
kernel knows to call udevsend -> udevd is started -> hardware is configured

I am still a bit unclear about how and why everything should be in those places.
I only know that hal needs udevsend as proc/kernel/hotplug to work, and it is a
cool thing for us to have automounting of devices. This makes linux much more
userfriendly, not only for desktop users.

Please post your thoughts here, I have just been called to a conference and will
be back online in about a week.

Ciao

Andreas

_______________________________________________
rock-devel mailing list
[email protected]
http://www.rocklinux.net/mailman/listinfo/rock-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFDgZ0R2A9/vRi9PS4RAnLKAJwLtsIiE0JDw4ikSfyGaHDWRyBYpQCfX3pp
kQ/u6e9ZuEKt2AVKSnwqStE=
=oqKb
-----END PGP SIGNATURE-----