On Tue, 2009-03-10 at 08:06 +0000, Adam Spragg wrote: > Victor Lowther wrote: > > 4: Add a few udev rules that call scripts to configure a few key device > > types as they are detected, and have another process running that looks > > for the root filesystem to appear running in tandem with udev. > [snip] > > We have made large advances using the fourth approach > > Something that worries me slightly ... ISTR that a large part of the goal of > udev was to get device naming policy out of the kernel tree and into an > externally maintained module. > > But one of the goals of dracut seems to be to become part of the kernel > source tree. > > So, if dracut imports udev naming rules and, therefore, device naming > policy, and is in turn imported into the main kernel source tree, doesn't > that kind of defeat one of the main reasons for udev's existence? > > Is this something we need to worry about? Nope, we import our rules from the host system, so whatever policy decisions are made are someone else's policy decisions. > Adam Spragg. > -- Victor Lowther RHCE# 805008539634727 LPIC-2# LPI000140019 -- To unsubscribe from this list: send the line "unsubscribe initramfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
