From owner-cvs-all Mon Feb 16 15:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA05034 for cvs-all-outgoing; Mon, 16 Feb 1998 15:33:33 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA05011; Mon, 16 Feb 1998 15:33:00 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id QAA02368; Mon, 16 Feb 1998 16:12:19 -0700 (MST) Message-Id: <199802162312.QAA02368@pluto.plutotech.com> X-Mailer: exmh version 2.0.1 12/23/97 To: Nate Williams cc: "Justin T. Gibbs" , Mike Smith , "John S. Dyson" , bde@zeta.org.au (Bruce Evans), dyson@FreeBSD.ORG, wollman@khavrinen.lcs.mit.edu, committers@FreeBSD.ORG, eivind@yes.no Subject: Re: devfs persistence In-reply-to: Your message of "Mon, 16 Feb 1998 16:05:35 MST." <199802162305.QAA25582@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Feb 1998 16:09:30 -0700 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk ... >With DEVFS, no such 'safety' margin exists, since the device is created >possibly with the administrator realizing it. I've already proposed a way to deal with this - you tell the system not to show new device arrivals unless they have explicit backing store (i.e. the administrator has acknowledged that the device exists and has proper permissions). Most people would not be interested in running this way, but for the security conscious, you can ask to get the old "MAKEDEV like" behavior back. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message