Gabor Gombas wrote: > > IMHO this looks more and more like the udev rules has to be split into > at least two categories: > > - a basic set that is used during boot and early system setup. Services > in rcS.d are allowed to rely on these rules only, and these rules must > not rely on anything outside the root file system. > > - an extended set that is activated at the beginning of rc[2345].d and > contains all the bells and whistles GNOME & co. wants. > > The separation can be done by depending on an environment variable that > only gets set using udevadm when transitioning to the default initlevel. > Or even better, let's export the current initlevel as an env. variable > in udevd, and let rules in the extended set test for that. The add event for e.g. a disk (partition) will be during early boot. For your proposal to work, you'd need some kind of replay mechanism, which allows udev to replay the add/remove events when /usr is available the extended ruleset is activated. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
Attachment:
signature.asc
Description: OpenPGP digital signature