http://bugs.linuxfromscratch.org/show_bug.cgi?id=1068

           Summary: Migration to managed hotplug events incomplete
           Product: Linux From Scratch
           Version: SVN
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P4
         Component: Book
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]
         QAContact: [email protected]


Although the "udev" initscript now sets /proc/sys/kernel/hotplug   
to /sbin/udevsend, there are a few more steps to do.   
   
1) To avoid future incarnations of Bug 842 and prevent junk device nodes from   
appearing in the real /dev (right now we just ignore them), add the following  
commands to hotplug installation instructions:   
   
rm /sbin/hotplug   # because /sbin/udevsend does everything /sbin/hotplug did   
sed -i s@/sbin/hotplug@/etc/hotplug/pci.agent@ /etc/hotplug/pci.rc   
  
In "Short descriptions", remove the description of /sbin/hotplug, or, better,  
replace it with the reference to udevsend.  
  
2) On the udev page, optionally add the following command:  
  
rm /etc/hotplug.d/default/10-udev.hotplug 
 
That symlink is needed only in non-managed mode. In managed mode, if this 
symlink is present, the following happens: 
 
a) The kernel calls /sbin/udevsend in order to inform userspace about the 
hotplug event 
b) udevsend transfers that information to udevd 
c) udevd calls handlers in /etc/dev.d and /etc/hotplug.d, including that 
symlink 
d) /sbin/udevsend is called again through that symlink. It detects a loop and 
exits immediately. 
 
Removal of that symlink optimizes things a bit by removing that loop.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
-- 
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