#2057: Udev-122 ------------------------------------------+--------------------------------- Reporter: [EMAIL PROTECTED] | Owner: [email protected] Type: enhancement | Status: new Priority: normal | Milestone: 7.0 Component: Book | Version: SVN Severity: normal | Resolution: Keywords: | ------------------------------------------+--------------------------------- Comment (by Bryan Kadzban):
Replying to [comment:30 LydianKnight]: > we could then try to write a udev rule for the devices based on its pci address space id rather to try anything else Yep; that's basically what is required if your card's driver gives it a random MAC address on every boot. The issue is that it fails once you move a card to a different slot. (Maybe that doesn't happen often, I'm not sure. At least not for PCI devices -- but it's a real problem for at least USB-connected NICs, if they get moved to another USB port.) And depending on how the rule gets written, two different USB NICs at the same position on two different USB buses (where, say, each bus has a unique PCI position because one is connected to a USB 2 add-in card, while the other is directly on the motherboard), could still collide. You'd have to use something like udev's path_id to generate the full path to the NIC, across all bus types. Anyway, that's basically just adding another type of persistence (one which the user could -- maybe -- generate a rule for manually, so it doesn't fall victim to some of the same issues as other in-chroot-rule- generation methods). But I still like udevtest, at least for the moment. :-) -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2057#comment:33> LFS Trac <http://wiki.linuxfromscratch.org/lfs/> Linux From Scratch: Your Distro, Your Rules. -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
