On Saturday 29 March 2008, Denys Vlasenko wrote: > On Saturday 29 March 2008 08:00, Mike Frysinger wrote: > > On Saturday 29 March 2008, Vladimir Dronnikov wrote: > > > > please do not top post > > > > > 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? > > > > the mdev.txt explains the expected behavior. if the destination ends in > > a /, then the device node is moved there and the old name is symlinked. > > if the destination does not end in a /, then the device node is renamed > > to that > > The point is, it is not "renamed to that" (in current mdev). > > Rule > > sda 0:0 444 >disk/scsiA > > results in this being created: > > /dev: > drwxr-xr-x disk > lrwxrwxrwx sda -> disk/sda > /dev/disk: > br--r--r-- sda > > while it should be > > /dev: > drwxr-xr-x disk > lrwxrwxrwx sda -> disk/scsiA > /dev/disk: > br--r--r-- scsiA > > Right?
i thought i tested that use case ... yes, doing "sda ....>disk/moo/cow/scsiA" should create disk/moo/cow/, move sda to disk/moo/cow/scsiA, and then symlink sda to disk/moo/cow/scsiA. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
