#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 [EMAIL PROTECTED]):
Replying to [comment:25 Bryan Kadzban]: > This seems to be what we did in the 6.2 book (http://www.linuxfromscratch.org/lfs/view/6.2/chapter07/network.html for instance)? Note all the exceptions below the example rules; that list is longer now. Should we keep that list in the book (including additions to it), or expect the user to find it on their own? Or not support that hardware (which I think is equivalent to "expect the user to find it on their own")? Or something else? The long list of exceptions is a red herring. Moreover, it explains why modern versions of udev write rules this way, so it counts as educational content. What really matters is that the rule matches the correct device uniquely, and we should state this goal explicitly and provide a way to check this (e.g., say that the *_rename interface will appear after the reboot in the case of an error). -- Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2057#comment:28> 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
