From owner-freebsd-current Sun Mar 3 17:52:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 8C98437B402 for ; Sun, 3 Mar 2002 17:52:12 -0800 (PST) Received: from pool0165.cvx40-bradley.dialup.earthlink.net ([216.244.42.165] helo=mindspring.com) by albatross.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16hhdq-0002zi-00; Sun, 03 Mar 2002 17:51:54 -0800 Message-ID: <3C82D32B.1E1A6E9A@mindspring.com> Date: Sun, 03 Mar 2002 17:51:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: Poul-Henning Kamp , David Malone , cjclark@alum.mit.edu, current@FreeBSD.ORG Subject: Re: devfs(5) Permissions References: <25568.1015186619@critter.freebsd.dk> <3C828BC7.22A80633@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've often thought that owner, group, and mode should be defaulted in the registration process for the device. This would let defaults be set in the source code, so in the worst case, you can rebuild the kernel to get them. This would also allow low granularity persistance to be handled in teh same way that kernel visual configuration handles it, or by minimally permitting modification of the data section of the kernel binary. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message