On Sunday 12 May 2013 16:19, Denys Vlasenko wrote:
> > >>> From $DEVNAMEs I saw it looks like using it makes sense:
> > >> kernel already tells us the subdir, no need to code it up
> > >> in the rules.
> > >
> > > If so, then mdev -s needs a way to support this, somehow to get the
> > > snd/X, if that's not possible, I would highly suggest to basename $MDEV.
> 
> Looks like getting snd/X is not possible
> 
> > > Other, ugly but possible workaround would be for me to put a thingy in
> > > catch-all script to check if $MDEV contain slash (and since it hit
> > > catch-all it wasn't handled), if it does, then basename it, export MDEV,
> > > DEVPATH etc and exec /sbin/mdev. Sounds better than in-mdev basenaming it?
> > 
> > Hey Denys, any news or comment on this? I'd like to roll out new mdev on 
> > some of my deployments however I don't want do any workaround like 
> > described above if thats not desired solution to this very issue.
> 
> I don't know.
> 
> I don't want to ignore $DEVNAME. Its information is too useful.
> 
> Maybe we need to teach kernel to export DEVNAME in sysfs.

I spoke too soon! It is available:

# cat /sys/devices/pci0000:00/0000:00:07.0/sound/card0/controlC0/uevent
MAJOR=116
MINOR=7
DEVNAME=snd/controlC0
^^^^^^^^^^^^^^^^^^^^^

and I even have a patch...
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to