From owner-freebsd-current Tue Nov 5 12:49:19 2002 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 B36EA37B401 for ; Tue, 5 Nov 2002 12:49:18 -0800 (PST) Received: from phalanx.trit.org (phalanx.trit.org [63.198.170.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BA1943E75 for ; Tue, 5 Nov 2002 12:49:18 -0800 (PST) (envelope-from dima@trit.org) Received: from harpoon.trit.org (harpoon.trit.org [192.168.4.193]) by phalanx.trit.org (Postfix) with ESMTP id 2DC741A222; Tue, 5 Nov 2002 20:49:17 +0000 (UTC) Received: from harpoon.trit.org (localhost [127.0.0.1]) by harpoon.trit.org (8.12.6/8.12.5) with ESMTP id gA5KnACA001113; Tue, 5 Nov 2002 20:49:15 GMT (envelope-from dima@trit.org) Received: (from dima@localhost) by harpoon.trit.org (8.12.6/8.12.6/Submit) id gA5KnASB001112; Tue, 5 Nov 2002 20:49:10 GMT X-Authentication-Warning: harpoon.trit.org: dima set sender to dima@trit.org using -f Date: Tue, 5 Nov 2002 20:49:10 +0000 From: Dima Dorfman To: Dan Nelson Cc: Andrew Lankford , current@FreeBSD.ORG Subject: Re: What's the status of devfs(8)? Message-ID: <20021105204910.GF641@trit.org> References: <20021105044708.LIEA1469.out010.verizon.net@verizon.net> <20021105185757.GB641@trit.org> <20021105194146.GB35777@dan.emsphone.com> <20021105201910.GD641@trit.org> <20021105203822.GD35777@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021105203822.GD35777@dan.emsphone.com> User-Agent: Mutt/1.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Nelson wrote: > to. Maybe /sbin/devfs could check which set is active and print an > error message like "Cannot modify ruleset 0" if a user tries to mess > with it? That would let the user know that rulesets are important and > they had better go reread the manpage. I just sent a patch to do that. > Or alternatively, change that example /dev/speaker rule in the manpage > to "devfs rule apply path speaker mode 666", so that people who only > care about fixing the speaker permissions (like me and apparently > Andrew Lankford) can just stick that command in /etc/rc.local and be > done :) The example was really meant to describe "This is how things are done", not "This is how to fix the speaker permissions". Ideally the way I want people to do this is to put something like this in rc.conf: devfs_ruleset_10=/etc/devfs.rules.10 and put their rules into /etc/devfs.rules.10 like this: path speaker mode 660 Of course, that isn't implemented yet. I should probably try to get to that before 5.0-RELEASE . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message