It's a simple and working solution and I think it simply should be made default for ALL attach events. To me it makes more sense than having 2 different systems for the same thing.
Anyway, now I'm going to set up a devfs.rules (and learn a new different syntax for doing exactly the same thing). This looks like something that could have been in the unix haters handbook. Brooks Davis wrote: > This is normal. devfs.conf is for boot only, you need devfs.rules for > runtime. Unfortunatly, the documentation of this fact and the > docuementation of devfs.rules sucks. > > -- Brooks Marwan Burelle wrote: > One possibility is to call /etc/rc.d/devfs when a device is attached > in /etc/devd.conf (take a look at devd(8) and devd.conf(5)) > > For exemple, I have something like this in my /etc/devd.conf : > > attach 100 { > device-name "umass[0-9]+" ; > action "/bin/sleep 3; /etc/rc.d/devfs restart" ; > }; > > "attach" : what kind of event > "100" : as usual, for ordering rules > "device-name ..." : the device concerned > "action ... " : what to do, here I use sleep, because action is called > when the attach event arrives, not when the device node is created. > > There maybe a better way, but "it works"© ;) _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"