On Sat, May 12, 2012 at 08:58:59PM -0400, Walter Dnes wrote > On Fri, May 11, 2012 at 02:02:59PM -0600, Michael J. Hammel wrote > > > Am I missing something? Is there a better way to auto-load modules for > > USB connected devices using mdev? Or am I headed in the right direction > > here? > > There's documentation at > http://git.busybox.net/busybox/plain/docs/mdev.txt which mentions... > > Mdev has two primary uses: initial population and dynamic updates. > > It goes on to give some examples. Is this what you're looking for?
I have a few additional questions along the same line... 1) Is it possible to determine more info about the device, so that we can "write mdev rules"? I'm talking manufacturer/serial#/etc. 2) Is it possible to somehow determine whether the system is booting up, or if it has already finished booting, and provide separate rules in /etc/mdev.conf? I obviously do not want to apply custom rules for USB sticks to my harddrive /dev/sda, which would result in an unbootable system. A heavy-handed approach would be to set up rules for (sd[b-z])([0-9]+) at the top of /etc/mdev.conf. In my case I have one built-in drive, which shows up as /dev/sda. It would be skipped by the above rule. People with 2 or more onboard drives would have to modify their rulesets accordingly. 3) If 2) above is possible, I may need to invoke scripts, rather than one-line commands. Where would be a good place to put them? A couple of ideas for script directories are /etc/mdev.d/ and /var/lib/mdev/ Is this a general thing or would it depend on the distro? -- Walter Dnes <[email protected]> _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
