On Sun, 2011-04-17 at 00:26 -0500, DJ Lucas wrote: > Ahh...lightbulb. This is why we currently have the udev-retry in our > bootscripts. Are the ids files accessed directly by external programs or > by the utility libraries/programs? Provide a common library to access > the files (if not done already) and install into the root and place the > ids files into the libexecdir, problem solved.
I don't pretend to follow the details - I'm going mostly by the statements made by systemd-developer Lennart Poettering on the subject, in response to some of the more recent arguments on the subject: http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken Looking on my own system, examples of offending rules seem to be things like 78-sound-card.rules, which uses the *descriptions* associated with USB device IDs to classify whether a device is a headphone, microphone, speaker, etc. A bit hacky, perhaps (and that file admits as much), but I suppose it's the only way to deal with some hardware. As to why that's an issue at boot time, I *assume* that if the id files aren't present when the hardware is detected on boot, the device won't be correctly recognised. It won't break the boot, but it will cause problems when the user tries using their USB speakers or whatever. Simon.
signature.asc
Description: This is a digitally signed message part
-- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
