From owner-freebsd-arch Mon Nov 26 19:25:29 2001 Delivered-To: freebsd-arch@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id C3B6337B417 for ; Mon, 26 Nov 2001 19:25:25 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.4) id fAR3P6e25466; Mon, 26 Nov 2001 22:25:06 -0500 (EST) (envelope-from wollman) Date: Mon, 26 Nov 2001 22:25:06 -0500 (EST) From: Garrett Wollman Message-Id: <200111270325.fAR3P6e25466@khavrinen.lcs.mit.edu> To: mjacob@feral.com Subject: Re: Anybody working on devd? In-Reply-To: <20011126230600$59b3@traf.lcs.mit.edu> References: <20011126212937.AD31B380D@overcee.netplex.com.au> Organization: MIT Laboratory for Computer Science Cc: arch@FreeBSD.org Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20011126230600$59b3@traf.lcs.mit.edu> you write: >It seems to me wrong to do 'adjustments'. Either you have a model that trusts >drivers to do the right thing when the call make_dev, or you don't. My site policy about what permissions certain device nodes should have should not, and in some cases probably cannot, be written directly into a device driver. The driver should use the most conservative possible settings -- in most cases, root:wheel/600 -- and let user-land code apply whatever policy is desired. We already have mechanisms for expressing some of that policy (e.g., /etc/fbtab) but it's not cognizant of transient devices. That's part of the problem which needs to be solved. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message