#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 [EMAIL PROTECTED]):
Thanks for tackling this Bryan!
Given the generally low number of situations that by-path persistence
would actually be useful for I'd say not to bother with it. It may be
worth mentioning why by-path persistence isn't suitable for NICs (or more
generally any device on the USB, PCMCIA or firewire buses, I guess).
Actually, I remember a discussion some time ago about a proposal to have
the kernel probe devices in parallel during bootup. If that happens, I'm
not sure that by-path persistence will be suitable for anything, right?
So, let's not bother patching Udev, we'll describe by-path and by-id for
CD drives. We'll describe by-mac for network interfaces.
It'd be nice if we could get the fact that one shouldn't use by-path
persistence on USB and other such easily hotpluggable buses into a warning
box, as I believe it warrants one. I can't see a way of rearranging the
text so that it flows properly though!
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/1912#comment:9>
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
