[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    =?KOI8-R?Q?=EF=D4=D7=C5=D4:_=EF=D4=D7=C5=D4:_MDEV:_rename?=
From:       "Vladimir Dronnikov" <dronnikov () gmail ! com>
Date:       2008-03-29 6:39:54
Message-ID: 6784529b0803282339o3a4d60f2xfbc2fe3fcec938a8 () mail ! gmail ! com
[Download RAW message or body]

What was intentional, Mike? To move device node while leaving a
symlink to it? Or to not account the basename of new device node
location?

If a user orders a certain device (and symlink) to be named MYTIMER
why mdev doesn't respect this?

--
Vladimir

2008/3/29, Mike Frysinger <vapier@gentoo.org>:
> On Friday 28 March 2008, Denys Vlasenko wrote:
> > On Friday 28 March 2008 20:01, Vladimir Dronnikov wrote:
> > > Hello!
> > >
> > > Of course I can give an example:
> > >
> > > ---
> > > timer root:audio 660 >snd/TIMER
> > > ---
> > > ( Note the symbols case of rename clause. )
> > >
> > > Current SVN mdev moves /dev/timer to /dev/snd/timer and leaves symlink
> > > /dev/timer -> snd/timer. Note, not TIMER but timer...
> >
> > You mean
> >
> > timer root:audio 660 >snd/anything
> >
> > moves /dev/timer to /dev/snd/timer, and
> >
> > timer root:audio 660 >snd/anything/
> >
> > moves /dev/timer to /dev/snd/anything/timer.
> >
> > first one seems to be a bug, second one is ok.
>
> it was intentional behavior so people could get "make a symlink" or "move"
> at
> the same time without having to create extra code.  sometimes it does leave
> a
> slightly messier /dev, but so what ?
> -mike
>
_______________________________________________
busybox mailing list
busybox@busybox.net
http://busybox.net/cgi-bin/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]