On Mon, 12 Sep 2011 11:07:12 +0200, Joost Roeleveld wrote: > > I'd like to know why these functions cannot be separated, run the > > command to populate /dev early on, then start the udev daemon after > > the filesystems have been mounted. > > > > Some sort of early boot rules file would need to be used to handle > > things like setting up symlinks for block devices to avoid breaking > > some users' fstabs. > > Yes, which means "udev" would need to be split into: > * devd (which controls the /dev-tree) > * plugd (which handles all the "hotplug-events" where special things > happen) > > The communication between the 2 could be done using a > simple /dev/udev_pipe device. "devd" throws events onto the pipe and > plugd handles these events.
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... -- Neil Bothwick Diarrhoea is hereditary, it runs in your genes.
signature.asc
Description: PGP signature
