mdev

[Vladimir Dronnikov]

Hello, list!

mdev_notes_usage contains only three fields definition (plus optional
command field).
But 4th field can be symlink definition either, right?

So I'm starting to lose the path: can one specify (I need that for
sure) both symlink definition and command to execute on device
creation/deletion?
If so, then the current parsing code is wrong.

Wouldn't it be better to require all five fields be present using,
say, a dot as a placeholder for unused field? This would make
mdev.conf less cryptic. (BTW, is there any standard mdev.conf, as udev
has its rules.d/?)

Also, I'd like to have $SUBSYSTEM envvar set, as udev does, to be able
to run commands for a whole bunch of devices regardless of their
names. E.g. for all PNP devices it is good to load specific modules
(if any).

Also, sometimes it is good to not stop at the first matching rules. It
can be implemented, say, via config-time switch. The rationale is to
reuse and generalize the rules as much as possible. I want, say, make
all sound devices owned by root:audio with 0660 mode, but some of them
I want to have 0666 mode. Two rules would do the magic.

Please, comment and critic the proposals. I got tired of udev
complexity, but some of its features are very useful, and can be
ported to mdev quite easily.

TIA,
--
Vladimir