On Thursday 28 June 2007, Mike wrote: > On Thursday 28 June 2007, Jason Curl wrote: > > I'm using BusyBox 1.5.0 and I can't get mdev to work as I would expect. > > It's only populating a very small subset of devices in the kernel. > > you've probably disabled the deprecated sysfs kernel option ... older > versions > of mdev wont work in that case, you have to enable the kernel option or grab > the fix out of current trunk
Checked the kernel configuration file and sysfs_deprecated is disabled as you suggested. I don't know where I was supposed to find that info - a wiki site for these tools maybe? Google sucks in finding the latest info about BusyBox. With the latest svn snapshot tarball I rebuilt the system and it populates the /dev as expected. Before the hint, I noticed 1.6.0 doesn't work and then saw in SVN the fix was applied rather recently. Do we know when the next official BusyBox will be built? Simply downloading and replacing 'mdev.c' doesn't work on 1.6.0 as there are changes to features also. As a nice feature, does it exist in the newest mdev.conf the ability to specify the name of the device that should be created? From what I can determine, mdev parses through /sys/block and then /sys/class looking for files that are "dev" and then create the relevant node (the directory name and the node provided by the file dev). As I have an embedded device, I would like to give USB devices names based on their driver, node position in the USB tree (not serial number) so it's predetermined what device name a USB device would be. Looks like the mdev.c code is easy enough to understand, it's all the configuration stuff that will bog me down to a halt. I don't want to add bloat, but getting scripts to do this for me would make the bloat even more. Thanks, Jason. _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
