Mike Frysinger wrote: > On Thursday 28 June 2007, Jason Curl wrote: >> 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? > > no such thing exists > >> 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? > > all mdev functionality is explained in docs/mdev.txt > > if you want to change the name, write a little script to do so and have > mdev.conf execute it
Do all the hotplug variables set by the kernel propogate to the programs that mdev run? Without this, writing scripts would be very difficult (I'd have to parse the sysfs again, something that mdev just did). mdev already knows about the device, so a symlink option like udev has would save flash space overall (less scripts, faster and as an option in the menuconfig would mean only those who want it would use it). And the mdev.txt is pretty terse. There's no mention of having to mount 'proc'. And a "full" setup would run that script and then "exec" init. For the "firmware" directory, where do I find the filename in the kernel? I certainly can't grep for what I want. I would also suggest changing the numbers so that the first code snippet is [4-6] and the second is [1-3] that shows what really must come first even though it's not in that order in the document. Jason. _______________________________________________ busybox mailing list busybox@busybox.net http://busybox.net/cgi-bin/mailman/listinfo/busybox
