Julian Elischer scribbled this message on Sep 20:
> > what happens in this case:
> > mount /devfs
> > cd /devfs
> > mv ttyd1 da0c # sure you don't normally do this but you CAN!
>
> da0c is now the name of the vissible alias of ttyd1
>
> > cd /
> > umount /devfs
> > mount /devfs
>
> ttyd1 is now the name of the visible alias of the device.
>
> >
> > sorry, that doesn't cut it as you loose your "dynamic" links from the
> > umount to mount, and we are back to the major/minor number to keep
> > track of which device node belongs to which device...
>
> no the "original" name is tracked.
>
> I don't see your problem
>
> the device reverts to it;s original name as it should....
>
> it remembers any permissions it was given under either name...
>
> I think this is good.
> you may think it's bad. why?
POLA! if we have persisten permissions and ownership, and we allow
renaming, then renaming should also be persistant... after the mount
again, da0c either no longer exists, or is no longer ttyd1... which
neither is an acceptable solution...
--
John-Mark Gurney Voice: +1 408 975 9651
Cu Networking
"The soul contains in itself the event that shall presently befall it.
The event is only the actualizing of its thought." -- Ralph Waldo Emerson
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
