OK. I see mdev is a kind of hotspot.

Let us decide whether mdev is ever going to be a replacement for udev
while _running the real_ system, not just a simple tool which creates
simplest _initial_ /dev entries while being called from initramfs. If
it IS the patch is useful. Otherwise it seems noone would need extra
functionality...

Changing the meaning of '>' is for cases when one does not want to
have everything under /dev itself. E.g. all ALSA audio devices should
(historically at least) be placed in /dev/snd and not in /dev. Current
mdev would make 2 copies of such devices if a rule had exist to place
them to /dev/snd. Because '>' means to redirect/move in other common
OS places I found it reasonable to change its meaning. And '+' was
found again rather reasonable for _add a symlink_.

Again, let us decide what mdev is for!

--
Vladimir


2008/3/26, Denys Vlasenko <[EMAIL PROTECTED]>:
> On Tuesday 25 March 2008 17:28, [EMAIL PROTECTED] wrote:
> > Attached is a patch to add regexp substitution with rename clause. +154
> octets.
> > It is now possible to use more generic rules in mdev.conf --
> >
> > look at some cuts from my mdev.conf:
> > -----
> > # block devices
> > ([hs]d[a-z])                root:disk       660     >disk/%1/0
> > ([hs]d[a-z])([0-9]+)        root:disk       660     >disk/%1/%2
> > mmcblk([0-9]+)              root:disk       660     >disk/mmc/%1/0
> > mmcblk([0-9]+)p([0-9]+)     root:disk       660     >disk/mmc/%1/%2
> > -----
> > # network devices
> > (tun|tap)           root:network    660     >net/%1
> > -----
> >
> > I find it quite simple and intuitive comparing with lengthy listing of all
> possible cases.
> >
> > I tried to not touch existing mdev.c code too much -- just new code for
> %1..9 substitution itself added.
>
> Vladimir, the problem is that I do not use mdev.
> I need someone else to test the changes - or apply them "blindly",
> with only code examination and compile test.
>
> Are there active mdev users who can verify that it works,
> and doesn't totally break mdev?
>
> You can alleviate these concerns if you can create testsiute entries
> for mdev. Then anyone (e.g. me) can run quick test...
>
> > Next, the meaning of > in rename clause is changed to "move devnode to the
> specified location". In order to
> > both move devnode _and_ create a symlink to it in /dev (old meaning of >)
> one should use + instead of >.
>
> See? How can I know whether it breaks existing usage?
> --
> vda
>
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox

Reply via email to