-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Dan Nicholson wrote: > On Tue, Mar 11, 2008 at 3:03 PM, Nathan Coulson <[EMAIL PROTECTED]> > wrote: >> I was just looking at cd udev-config-20080217, >> >> Linux 2.6.24.3 (.2 headers), udev 113, > > Someone brought this up to me off list and I forgot to report it > here. Shouldn't the new rules only be used with newer udev
Um, yup. The current udev-config svn requires a udev that comes with its own rules file (Nathan: You can probably work around this by copying the 50-udev-default.rules file from any udev version after 113), and it looks like that's what got put into the udev-config-20080217 tarball. (Based on the date, that sounds about right. I believe I did the cleanup that broke against udev-113 sometime before the new year.) We can update the book to udev-118, but we're (well, I'm) still stuck trying to figure out how to handle pre-generating persistent-net rules. If we don't mind breaking that, we can just bump the udev version. What I'd *like* to do is get a way to create a "symlink" for network devices in the kernel; that way the persistent-net support could work just like the persistent-storage support in udev (udev creates symlinks with fixed names that point at different real devices). That would mean we wouldn't have to generate rules inside chroot, since the device (symlink) name that udev creates will be predictable (and therefore also can't change). But that's going to have to wait until at least 2.6.26, I think (if it gets in at all; I haven't even asked linux-netdev what they think yet). In the meantime, we probably need a working book. ;-) Looking at the svn log, it seems that r8485 was the one that added the update? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH1xY9S5vET1Wea5wRA1hRAKDQYnNbyJj4dRDMVwv4WoBdo2qZQACePu7V 8xjMoZezAdmhTgYfkIPwWgk= =976D -----END PGP SIGNATURE----- -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
