src/sbin/devfs, branch releng/5.0

mdoc(7) police: markup nits.

2002-12-09T13:06:34Z

Approved by: re

Treat the pathptrn field as a real pattern with the aid of fnmatch().

2002-10-08T04:21:54Z

Don't depend on pollution in (by way of

2002-07-29T17:09:21Z

) for definition of macros.

Nuke whitespace at EOL.

2002-07-28T06:59:40Z

What we're actually passing around is an ioctl request, not a command,

2002-07-28T06:57:13Z

and it's an unsigned long, not an int.

This compiles cleanly with WARNS=5 on i386 and alpha, so try to make

2002-07-28T06:52:47Z

sure that doesn't change.

Implement this (quoted from the updated man page): If the first token

2002-07-28T06:45:30Z

of a rule specification is a single dash (``-''), rules are read from the standard input and the rest of the specification is ignored.

Use more standard section names in an attempt to unconfuse new users

2002-07-28T03:58:12Z

(and make it easier to find stuff for the old ones). I originally put everything under one "RULE SUBSYSTEM" so it didn't look like devfs(8) is dedicated to the rule subsystem, but since nobody has any idea what else might go here, it's not worth confusing people just to save a little time for someone that might add something rule-unrelated to devfs(8) in a few years. Suggested by: sheldonh, phk

Introduce the DEVFS "rule" subsystem. DEVFS rules permit the

2002-07-17T01:46:48Z

administrator to define certain properties of new devfs nodes before they become visible to the userland. Both static (e.g., /dev/speaker) and dynamic (e.g., /dev/bpf*, some removable devices) nodes are supported. Each DEVFS mount may have a different ruleset assigned to it, permitting different policies to be implemented for things like jails. Approved by: phk