From owner-freebsd-stable@FreeBSD.ORG Tue Dec 13 17:20:06 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E696416A41F for ; Tue, 13 Dec 2005 17:20:06 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 1729A43D64 for ; Tue, 13 Dec 2005 17:20:05 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 13 Dec 2005 17:20:04 -0000 Received: from p54A7C94A.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.201.74] by mail.gmx.net (mp034) with SMTP; 13 Dec 2005 18:20:04 +0100 X-Authenticated: #5465401 Message-ID: <439F02B3.60707@gmx.de> Date: Tue, 13 Dec 2005 18:19:47 +0100 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <439EF8B5.4030702@gmx.de> <20051213165416.GE71643@pc5-179.lri.fr> In-Reply-To: <20051213165416.GE71643@pc5-179.lri.fr> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Subject: Re: devfs doesn't set access rights X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2005 17:20:07 -0000 It's a simple and working solution and I think it simply should be made default for ALL attach events. To me it makes more sense than having 2 different systems for the same thing. Anyway, now I'm going to set up a devfs.rules (and learn a new different syntax for doing exactly the same thing). This looks like something that could have been in the unix haters handbook. Brooks Davis wrote: > This is normal. devfs.conf is for boot only, you need devfs.rules for > runtime. Unfortunatly, the documentation of this fact and the > docuementation of devfs.rules sucks. > > -- Brooks Marwan Burelle wrote: > One possibility is to call /etc/rc.d/devfs when a device is attached > in /etc/devd.conf (take a look at devd(8) and devd.conf(5)) > > For exemple, I have something like this in my /etc/devd.conf : > > attach 100 { > device-name "umass[0-9]+" ; > action "/bin/sleep 3; /etc/rc.d/devfs restart" ; > }; > > "attach" : what kind of event > "100" : as usual, for ordering rules > "device-name ..." : the device concerned > "action ... " : what to do, here I use sleep, because action is called > when the attach event arrives, not when the device node is created. > > There maybe a better way, but "it works"© ;)