From owner-freebsd-rc@FreeBSD.ORG  Thu Jun 30 13:14:03 2005
Return-Path: <owner-freebsd-rc@FreeBSD.ORG>
X-Original-To: freebsd-rc@freebsd.org
Delivered-To: freebsd-rc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E21D816A41C;
	Thu, 30 Jun 2005 13:14:03 +0000 (GMT)
	(envelope-from mmolteni@cisco.com)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 16AFB43D48;
	Thu, 30 Jun 2005 13:14:02 +0000 (GMT)
	(envelope-from mmolteni@cisco.com)
Received: from ams-core-1.cisco.com (144.254.224.150)
	by ams-iport-1.cisco.com with ESMTP; 30 Jun 2005 15:14:02 +0200
Received: from amsterdam.cisco.com (amsterdam.cisco.com [144.254.224.160])
	by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j5UDDwDg005365; 
	Thu, 30 Jun 2005 15:13:59 +0200 (MEST)
Received: from barbapapa.cisco.com (barbapapa.cisco.com [144.254.53.64])
	by amsterdam.cisco.com (8.12.10/8.12.6) with ESMTP id j5UDDukA015983;
	Thu, 30 Jun 2005 15:13:56 +0200 (MEST)
Received: by barbapapa.cisco.com (Postfix, from userid 1000)
	id 810AD9C; Thu, 30 Jun 2005 15:13:56 +0200 (CEST)
From: Marco Molteni <mmolteni@cisco.com>
To: Mike Makonnen <mtm@identd.net>
Date: Thu, 30 Jun 2005 15:13:54 +0200
User-Agent: KMail/1.8
References: <20050615162744.GP1053@kaiser.sig11.org>
	<20050629164550.GJ7953@kaiser.sig11.org>
	<20050630090855.GA1372@rogue.smit.lan>
In-Reply-To: <20050630090855.GA1372@rogue.smit.lan>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200506301513.55718.mmolteni@cisco.com>
Cc: Matteo Riondato <matteo@freebsd.org>, edwin@mavetju.org,
	freebsd-rc@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/63954: devfs loses permissions
X-BeenThere: freebsd-rc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussion related to /etc/rc.d design and implementation."
	<freebsd-rc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-rc>
List-Post: <mailto:freebsd-rc@freebsd.org>
List-Help: <mailto:freebsd-rc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-rc>,
	<mailto:freebsd-rc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jun 2005 13:14:04 -0000

On Thursday 30 June 2005 11:08, Mike Makonnen wrote:
> On Wed, Jun 29, 2005 at 06:45:50PM +0200, Matteo Riondato wrote:
> > Then having any other kind of rule in devfs.conf should is kind of
> > useless, at least for devices that can "disappear", since rules
> > referring to them will not be added do the devfs ruleset, and this
> > implies that one have to rerun /etc/rc.d/devfs after reinserting
> > the pcmcia nic or after launching tcpdump or whatever.
>
> Just to make it clear: devfs.rules is the correct way to do what you
> and the original poster wants. Once the rules have been applied it
> doesn't matter if the device is or isn't in /dev, whether you remove
> it or plug it in later. Once you run rc.d/devfs you don't have to
> rerun it again unless you add/change/remove the rules.

Mike,

Matteo was referring to devfs.conf, not devfs.rules.

devfs.conf should die, it is there to confuse people.

marco