Dan Nelson <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
