#1912: Possible bad interaction of udev rules for duplicate devices
--------------------------------------------+-------------------------------
Reporter: [EMAIL PROTECTED] | Owner: Bryan Kadzban
Type: defect | Status: new
Priority: normal | Milestone: 6.3
Component: Book | Version: SVN
Severity: normal | Resolution:
Keywords: |
--------------------------------------------+-------------------------------
Comment (by Bryan Kadzban):
http://marc.theaimsgroup.com/?t=117141229000004&r=1&w=2
See the second message. Basically, path-based persistence for NICs
doesn't work at all for USB (or other removable) NICs. It can't --
whenever the NIC is plugged into a different port, its physical path
changes. It'd probably work OK for PCI/PCIe cards, but even then, it's
only useful if the card is in a slot, not if it's built into the
motherboard.
So the question is, is it worth keeping the by-path persistence option in
the book for NICs? If so, I can commit the patch to patches, with a URL
to that thread. But given how it's going to break on a (probably) large
number of machines, I don't think it's worth it, unless maybe we
specifically say "this is probably only useful if your NIC is a plug-in
PCI or PCI-Express card, and you plan on putting a different NIC in its
slot it if it dies". I'm guessing that's a fairly low number of potential
users.
I still want to modify the chapter 7 text, though; as it is, it's not very
clear why you'd want to choose one form of persistence over the other.
(That's true for both CDs and NICs, but for NICs it can easily be argued
that we should remove the by-path persistence option altogether. So I'll
wait a bit for any comments on that, but I'd like to modify 7.12.1 fairly
soon.)
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1912#comment:8>
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
