From owner-freebsd-current@FreeBSD.ORG  Thu May 15 13:55:46 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9FFC037B401
	for <current@freebsd.org>; Thu, 15 May 2003 13:55:46 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 75CA043FA3
	for <current@freebsd.org>; Thu, 15 May 2003 13:55:45 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h4FKtfxm003219;
	Thu, 15 May 2003 22:55:42 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: jeff@walters.name
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 15 May 2003 16:53:43 EDT."
             <200305151653.43540.jeff@walters.name> 
Date: Thu, 15 May 2003 22:55:41 +0200
Message-ID: <3218.1053032141@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: Comment on devfs.conf 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 May 2003 20:55:46 -0000

In message <200305151653.43540.jeff@walters.name>, Jeff Walters writes:
>The new /etc/devfs.conf arrangement is a good thing but it doesn't work for 
>devices that are created on the fly after boot, and it gives an error on 
>wildcards on device names.  
>
>I suggest for /etc/rc.d/devfs that instead of changing the permissions and 
>ownerships directly on device nodes, create a default devfs ruleset based on 
>/etc/devfs.conf entries and apply the set.  For example, previously you could 
>modify /etc/rc.devfs with the logic like:

I must admit that I should have looked at this, now that I have, I fully
agree:  The policy setup at boot should be not just applied once, but
made the default ruleset.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.