Julian Elischer scribbled this message on Sep 20:
> > 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...
>
> I think at this stage you've gone overboard..
>
> part of the definition of devfs is that a device shows up on mount
> with it's canonical name.. On each new mount every time, even if you've
> mounted it in 10 different places.
I didn't flat out state it, but I think persistant should NOT be done
via an underlying node, but via a daemon... and then this would be a
moot point as you'd just configure the daemon to do what you need to
do, or run an /etc/rc.devfs script which sets the permission properly..
a) all existing device nodes show up
b) all nodes are gives root:wheel 0600 permissions at start
that is all I'm looking for... anything else is stupid or complex...
hell, a daemon could be something as simple as a script that constantly
sees if a device has root:wheel 0600 permissions, and set them correctly
if they don't...
persitance is stupid UNLESS it is complete persitance... and you've said
that complete persitance is to complex, so lets go w/ no persitance, and
default secure premissions...
--
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
