#2057: Udev-114
------------------------------------------+---------------------------------
 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):

 Sigh.  ;-)

 They completely removed the "installation-time" part of the script.
 According to the commit messages
 
(http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=9b23e594bf2533b7fadeea1680b186e4775cfe17
 and
 
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=dcfa2acce30c0574bcec761b72cad4141da78e1b
 are the commits: if we revert this, we'll have to revert chunks of both),
 it looks like they removed it because it was "keeping a second blacklist
 outside the rules files".

 They also had some comment about "this should be called by triggering
 events, not by looping", but I have no idea what that's supposed to mean.
 Obviously it needs to be called in a loop when a distro gets installed,
 otherwise the user isn't going to have a clue what names their devices
 will have.

 Er, hold on, I think I get it now.  They're saying that instead of running
 what we have in the book, you need to run something like:

 {{{
 for dir in /sys/class/net/*/ ; do
     echo "add" >$dir/uevent
 done
 }}}

 after installing the files, to pre-generate the rules.  That seems a lot
 more direct (closer to what actually should be happening) anyway.

 The only problem is, udevd is running outside the chroot, so it won't
 update the new system's rules files.  It'll only process the host's
 already-in-place rules, and the script won't ever get called.  If we kill
 udevd and restart it from inside chroot, the process could end up yanking
 devices out from under the host and renaming them.  Neither choice is
 good.

 I'll see if I can find out from the -devel list how we're supposed to
 handle this from inside chroot...

-- 
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2057#comment:2>
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

Reply via email to