Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Sep 2004 12:55:26 -0400
From:      John Baldwin <jhb@FreeBSD.org>
To:        freebsd-mobile@FreeBSD.org
Cc:        Jochen Gensch <incmc@gmx.de>
Subject:   Re: FreeBSD 5.3-BETA6 available
Message-ID:  <200409271255.26828.jhb@FreeBSD.org>
In-Reply-To: <41583D40.3030008@gmx.de>
References:  <415720FD.8080603@samsco.org> <200409271053.47904.jhb@FreeBSD.org> <41583D40.3030008@gmx.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 27 September 2004 12:18 pm, Jochen Gensch wrote:
> John Baldwin wrote:
> > You need to use persistent devfs rules rather than the one-time boot fix
> > that devfs.conf does to get the devfs permissions you want/need.
>
> Could you tell where to find information about that? devfs(8) and (5)
> don't help me very much with this.

Err, the third paragraph and beyond are all about rules.

DEVFS(8)                FreeBSD System Manager's Manual               DEVFS(8)

NAME
     devfs -- DEVFS control

SYNOPSIS
     devfs [-m mount-point] keyword argument ...

DESCRIPTION
     The devfs utility provides an interface to manipulate properties of
     devfs(5) mounts.

     The keyword argument determines the context for the rest of the argu-
     ments.  For example, most of the commands related to the rule subsystem
     must be preceded by the rule keyword.  The following flags are common to
     all keywords:

           -m mount-point
                       Operate on mount-point, which is expected to be a
                       devfs(5) mount.  If this option is not specified, devfs
                       operates on /dev.

   Rule Subsystem
     The devfs(5) rule subsystem provides a way for the administrator of a
     system to control the attributes of DEVFS nodes.  Each DEVFS mount-point
     has a ``ruleset'', or a list of rules, associated with it.  When a device
     driver creates a new node, all the rules in the ruleset associated with
     each mount-point are applied (see below) before the node becomes visible
     to the userland.  This permits the administrator to change the proper-
     ties, including the visibility, of certain nodes.  For example, one might
     want to hide all disk nodes in a jail(2)'s /dev.

As far as having these actions done automatically on boot, look at 
the /etc/defaults/devfs.rules file.  You can make a custom one in /etc.

-- 
John Baldwin <jhb@FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409271255.26828.jhb>