From owner-freebsd-hackers Sun Sep 19 23:25: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id AADE114A25 for ; Sun, 19 Sep 1999 23:25:07 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id CAA21460; Mon, 20 Sep 1999 02:20:07 -0400 (EDT) Date: Mon, 20 Sep 1999 02:20:06 -0400 (EDT) From: "Matthew N. Dodd" To: Chuck Robey Cc: Julian Elischer , Wayne Cuddy , FreeBSD Hackers List Subject: Re: what is devfs? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Sep 1999, Chuck Robey wrote: > But it was to the subject on the Subject: line, Julian. We know what side > you're on, but there are 2 sides to the argument. Isn't there some way > that it can be set up to *optionally* have permission persistence? Seems like a devfsd using the file monitoring hooks would work; you'd only update the persistent store if you were running devfsd. devfsd would read the store and init /dev with the contents. I think the only issue that would involve thinking would be whiteouts (and the actual devfsd code of course.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message