Re: hardware initialization

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andreas V. Meier wrote:
> 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.

Can you elaborate a bit more on how hardware detection will work then? Will udev
send hotplug events to the hotplug scripts or how is that going to work?
Mind you, I'm no expert in that field :)

Greetings,
	Benjamin

- --
Go away, or I will replace you with a very small shellscript!
	http://shellscripts.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDg1Yxr0OTeImXvg8RAtNwAJ4+bsfDQLIYzs3PMlT2PIdw/saQSACfR+7z
68FTNZNXR+YSHiXk0dTbd+s=
=JuG+
-----END PGP SIGNATURE-----