On Tue, Sep 13, 2011 at 08:04:14AM +0100, Neil Bothwick wrote > This is why the whole /usr issue is irrelevant and not a fix at all. All > it does is avoid the most common breakages caused by udev trying to run > all its rules too early in the boot process. Putting /var on / would > "fix" your example, but what if a rule required access to an NFS mount? > > Every time you fix one of these breakages, you are kludging around the > real problem.
How many people really need to run *ARBITRARY* binaries that early in the boot process? The 1% who do shouldn't force the other 99% of us to go with initramfs or a Windows C:\ drive. I've masked out pam and hal and dbus in package.mask and my system runs fine with out them. This thread reminds me of the old joke that an elephant is actually a mouse designed by a committee. Trying to cover every possible edge case with a one-size-fits-all solution doesn't work without bloating everybody's system. If someone wants an arbitrary binary really early in bootup, link it statically and save to /etc/udev/bin or where ever, and leave the other 99% of us to ignore initramfs. Is this from the same Redhat that brought us BlueCurve and made Pulseadio the default on their OS? -- Walter Dnes <waltd...@waltdnes.org>
