Date: Tue, 5 Nov 2002 20:49:10 +0000 From: Dima Dorfman <dima@trit.org> To: Dan Nelson <dnelson@allantgroup.com> Cc: Andrew Lankford <arlankfo@141.com>, current@FreeBSD.ORG Subject: Re: What's the status of devfs(8)? Message-ID: <20021105204910.GF641@trit.org> In-Reply-To: <20021105203822.GD35777@dan.emsphone.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
Dan Nelson <dnelson@allantgroup.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021105204910.GF641>