On Saturday 29 March 2008, Vladimir Dronnikov wrote: > 2008/3/29, Mike Frysinger <[EMAIL PROTECTED]>: > > On Saturday 29 March 2008, Vladimir Dronnikov wrote: > > > > please do not top post > > It is much harder in elinks and web-mail but I'll try to do my best. > > > > 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 > > and the old name is symlinked. this way both moving and symlinking are > > supported. > > > > > If a user orders a certain device (and symlink) to be named MYTIMER > > > why mdev doesn't respect this? > > > > it works for me: > > input.* 0:0 0644 >input/ > > > > all input device nodes get placed into the input subdirectory and > > symlinked from the top directory. > > This is evident. But what if I want to name /dev/fb0 as /dev/fb? What > is the mdev.conf's rule?
fb0 0:0 0644 >fb -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
