From owner-freebsd-hackers Tue Sep 21 0: 0:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mg-20425427-42.ricochet.net (mg-20425427-42.ricochet.net [204.254.27.42]) by hub.freebsd.org (Postfix) with ESMTP id 430BB14C1B for ; Tue, 21 Sep 1999 00:00:19 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by mg-20425427-42.ricochet.net (8.9.1/8.8.7) id AAA21103; Tue, 21 Sep 1999 00:00:12 -0700 (PDT) Message-ID: <19990921000009.54622@hydrogen.fircrest.net> Date: Tue, 21 Sep 1999 00:00:09 -0700 From: John-Mark Gurney To: Julian Elischer Cc: Brian Beattie , "Matthew N. Dodd" , Chuck Robey , Wayne Cuddy , FreeBSD Hackers List Subject: Re: what is devfs? References: <19990920231629.26284@hydrogen.fircrest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Julian Elischer on Mon, Sep 20, 1999 at 11:28:11PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message