From owner-freebsd-current@FreeBSD.ORG  Fri Feb 13 07:32:54 2004
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 CAECA16A4CE; Fri, 13 Feb 2004 07:32:54 -0800 (PST)
Received: from gvr.gvr.org (gvr-gw.gvr.org [80.126.103.228])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5D00043D1D; Fri, 13 Feb 2004 07:32:54 -0800 (PST)
	(envelope-from guido@gvr.org)
Received: by gvr.gvr.org (Postfix, from userid 657)
	id AE2782D; Fri, 13 Feb 2004 16:32:53 +0100 (CET)
Date: Fri, 13 Feb 2004 16:32:53 +0100
From: Guido van Rooij <guido@gvr.org>
To: "Brian F. Feldman" <green@freebsd.org>
Message-ID: <20040213153253.GA13951@gvr.gvr.org>
References: <20040213144338.GA13380@gvr.gvr.org>
	<200402131507.i1DF74Tm044520@green.homeunix.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200402131507.i1DF74Tm044520@green.homeunix.org>
cc: Dag-Erling =?iso-8859-15?Q?Sm=F8rgrav?= <des@des.no>
cc: current@freebsd.org
Subject: Re: usb devices and devfs settings
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: Fri, 13 Feb 2004 15:32:54 -0000

On Fri, Feb 13, 2004 at 10:07:04AM -0500, Brian F. Feldman wrote:
> > 
> > Indeed. However, I don't really understand the purpos of devfs.conf
> > then: why a one time bootup config file, when you have a mechanism
> > that works like in devfs(8)? Why not rewrite devfs.conf in the
> > devfs(8) way, load the rulesets and do an apply?
> 
> Unfortunately, that doesn't change the permissions of already-created device 
> nodes.

It does. With applyset:

     Note that if any such nodes already exist, their
     mode will not be changed unless this rule (or ruleset) is explicitly
     applied (see below).  The mode will be changed if the node is created
     after the rule is added (e.g., the atspeaker module is loaded after the
     above rule is added).

           devfs rule applyset

     Apply all the rules in the current ruleset to all the existing nodes.

-Guido