On Mon, 12 Sep 2011 11:34:17 +0200, Joost Roeleveld wrote:

> > I wonder if it could be done more simply. udevd loads but only parses
> > those rule files marked as suitable for early boot time. Later in the
> > boot it switches to "full" mode and loads all rule files.
> > 
> > This is so simple it is either pure genius or completely naive and
> > unworkable. I know which option my money is on...  
> 
> This would depend on wether or not udev (or whatever program handles
> the events) can pick specific events out of the queue.
> 
> I think the events are placed on a queue waiting for some process to
> handle them and that process then does the following in an endless loop:
> 1) get event from queue
> 2) handle event
> 
> In order to split the 2 options, there needs to be something that sorts
> them between "init-level" and "run-level" events where "init-level" is
> what is needed/possible during boot.
 
If the rules are not loaded, the events are ignored. They are not
run handled until the full set of rules are loaded later on.

Alternatively, the first rules file parsed would do whatever is necessary
for other rules to be handled, such as doing whatever is necessary
to make all programs and libraries available. Then it would be the
responsible of who/whatever adds the rules to make sure the setup is
complete.


-- 
Neil Bothwick

To be sure of hitting the target, shoot first and call whatever you hit
the target.