freebsd-nq/share/man/man5/devfs.rules.5
Giorgos Keramidas d854ee0742 Add manpages for devfs.conf and devfs.rules. These have been
initially written by Roland, but hacked for a while by me.  Any
good parts are the results of Roland's hard work.  Any typos or
style mistakes are mine.

Submitted by:	Roland Smith <rsmith@xs4all.nl>
PR:		docs/63808, docs/75433, docs/80458, docs/80459
MFC after:	2 weeks
2005-05-17 17:52:27 +00:00

93 lines
2.8 KiB
Groff

.\" Copyright (c) 2004 Roland Smith <rsmith@xs4all.nl>
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD$
.\"
.Dd May 17, 2005
.Dt DEVFS.RULES 5
.Os
.Sh NAME
.Nm devfs.rules
.Nd devfs configuration information
.Sh DESCRIPTION
The
.Nm
file provides an easy way to create and apply
.Xr devfs 8
rules, even for devices that are not available at boot.
.Pp
For devices available at boot, see
.Xr devfs.conf 5 .
.Pp
The format of this file is simple.
Empty lines and lines beginning with a hash sign
.Pq Ql #
are ignored.
A line between brackets denotes the start of a ruleset.
In the brackets should be the name of the ruleset and its number,
separated by an equal sign.
.Pp
Other lines are rule specifications as documented in
.Xr devfs 8 ,
in the section
.Dq "Rule Specification" .
These lines are prepended with
.Dq Li rule
and are passed to
.Xr devfs 8
by the startup scripts of the system.
It is important to put path elements that contain
.Xr glob 3
special characters between quotes.
.Sh EXAMPLES
To make all the partitions of
.Xr da 4
devices readable and writable by their owner and the
.Dq Li usb
group, the following rule may be used:
.Bd -literal -offset indent
add path 'da*s*' mode 0660 group usb
.Ed
.Pp
To make all the
.Xr uscanner 4
devices accessible to their owner and the
.Dq Li usb
group, a similar rule may be used:
.Bd -literal -offset indent
add path 'uscanner*' mode 0660 group usb
.Ed
.Sh FILES
.Bl -tag -compact
.It Pa /etc/devfs.rules
.It Pa /etc/defaults/devfs.rules
.El
.Sh SEE ALSO
.Xr glob 3 ,
.Xr devfs 5 ,
.Xr devfs.conf 5 ,
.Xr devfs 8
.Sh AUTHORS
.An "Roland Smith" Aq rsmith@xs4all.nl