On Thursday, September 15, 2011 07:15:27 PM Neil Bothwick wrote: > On Thu, 15 Sep 2011 17:37:53 +0200, Joost Roeleveld wrote: > > There are 3 solutions for this: > > 1) The easy way out: the whole user-space must be available before udev > > 2) udev actually includes correct error-handling for this and retries > > 3) udev splits this into 2 seperate tools > > 4) udev remains one tool but with two modes of operation. when in > early-boot mode, it can only run a restricted set of rules - such as > those using LVM, RAID, cryptsetup, network device naming. When switched > to "full" mode later in the boot process, it loads the rest of the rules.
Yes, I've been thinking about this option as well, after some comments on the gentoo-dev list. > Which rules it runs it early-boot mode could be decided by adding a flag > to the rule to mark it acceptable for early boot usage. That way, > existing rules would automatically be deferred unless package > maintainers update the rules for those they know will work early in the > boot process. > > It saves writing/learning/debugging a new tool and gives maximum > compatibility with existing configurations. > > This is pretty similar in concept to your suggestion 3, but a different > approach to its implementation. And might be the "simpler" option. Currently, I'm planning on checking if the "retry"-queue can be abused for this purpose. -- Joost
