<p><br> On Mar 21, 2012 10:04 PM, "Alan Mackenzie" <<a href="mailto:acm@muc.de">acm@muc.de</a>> wrote:<br> ><br> > Hello again,<br> ><br> > On Wed, Mar 21, 2012 at 08:12:40PM +0700, Pandu Poluan wrote:<br> > > On Mar 21, 2012 8:07 PM, "Alan Mackenzie" <<a href="mailto:acm@muc.de">acm@muc.de</a>> wrote:<br> ><br> > > > On Wed, Mar 21, 2012 at 07:49:02PM +0700, Pandu Poluan wrote:<br> > > > > Strange...<br> ><br> > > > > Do you use mdev to handle hotplugs, btw?<br> ><br> > > > You mean, like sticking in a USB stick, or turning my printer on? Yes, I<br> > > > do.<br> ><br> ><br> > > No, I mean, did you do :<br> ><br> > > echo /bin/mdev > /proc/sys/kernel/hotplug<br> ><br> > No I haven't. I don't understand at all what this is about. Any chance<br> > of a quick summary?<br> ></p> <p>According to the busybox documentation, /proc/sys/kernel/hotplug contains the path to a program that will be invoked on hotplug events (hotplug here means the creation of a new device node under /dev, not necessarily actually plugging something onto the box).</p> <p>Doing the above 'echo' will result in kernel invoking mdev when a hotplug event fires; mdev will then act upon the newly-created device node according to the 'recipe' in /etc/mdev.conf, e.g., chown-ing the node, renaming/moving the node, making a symlink, or even triggering a script.</p> <p>The above line should go right after the 'mdev -s' line in linuxrc.</p> <p>> > (ensure beforehand that /bin/mdev is a symlink to /bin/busybox)<br> ><br> > my /sbin/mdev is an indirect symlink to /bin/busybox as follows:<br> > ^<br> ><br> > /sbin/mdev -> /bin/bb -> busybox<br> ><br> > Presumably this would be OK.<br> ></p> <p>I think so...</p> <p>Rgds,<br> </p>