On Sun, 2007-11-18 at 13:17 +0100, Marc Blumentritt wrote: > Natanael Copa schrieb: > > I started with a mdev.conf i found somwhere (probably tinderbox) > > I actually think they never worked for me either. IIRC i checked the bb > > source and wondered if the links were supposed to work at all. I for got > > to remove them (or was too lazy) > > > > I am now more or less done with mdev configuration (s. attached tar > ball, which is based on your scripts). I tried to create device files > with mdev in a way, that /dev looks like created by udev. To use this > with baselayout-2, you have to create /dev/null in > /lib/rcscripts/addons/mdev-start.sh inside the function seed_dev (s. tar > ball). > > usb device file creation is not dependent on kernel option > CONFIG_USB_DEVICE_CLASS anymore, since this option is marked DEPRECATED.
great! > There is only one question left. If I unplugged a usb device, I also > unload the usb bus driver. Does this make sense? What happens, if two > usb devices are plugged in and one is removed? I believe that if the driver is in use, the removal of module will silently fail. ( .... 2>/dev/null) If the second device is unsused, I guess the module will be unloaded. For me this is acceptable since i believe it will rarely cause any problems in real life. > This is certainly not perfect, but it does work me. It is not a full > udev replacement. I would be more than happy if it does the job "good enough". Might be we should include this ina separate ebuild/project together with the busybox init.d scripts? > I'm happy about any comments. I had a short look at your scripts and first impression was: clean, readable, well commented shell code. Beautiful! I look forward to test in the comming week. Thanks a lot for you work on this. Higly appreciated! -nc -- [EMAIL PROTECTED] mailing list
