man filesystems: fix xrefs after move to section 4

Reviewed by: des, imp
Pull Request: https://github.com/freebsd/freebsd-src/pull/1077

devfs(8): Remove references to /usr/share/examples/etc/devfs.conf

This file does not exist, remove it from the list of files to avoid
confusion. The example file is just /etc/devfs.conf.

Reviewed by: mhorne
Pull Request: https://github.com/freebsd/freebsd-src/pull/871

Remove $FreeBSD$: two-line nroff pattern

Remove /^\.\\"\n\.\\"\s*\$FreeBSD\$$\n/

add documentation that the rules need to be reloaded, and how to do it...

MFC after: 1 week

Add history section for devfs(8)
Move sentence to a new line as advised by igor.

PR: 212441
Approved by: bcr (mentor)
MFC after: 5 days
Differential Revision: https://reviews.freebsd.org/D8104

Clarify how "hide" and "unhide" commands work on directories.

Move EXAMPLES descriptions to before the actual command.

PR: 177870
Submitted by: Bjorn Heidotting <b.heidotting@yahoo.com>

mdoc: minor improvements to a few lists with tags.

Remove trailing whitespace per mdoc lint warning

Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days

A new jail(8) with a configuration file, to replace the work currently done
by /etc/rc.d/jail.

Create the altix project branch. The altix project will add support
for the SGI Altix 350 to FreeBSD/ia64. The hardware used for porting
is a two-module system, consisting of a base compute module and a
CPU expansion module. SGI's NUMAFlex architecture can be an excellent
platform to test CPU affinity and NUMA-aware features in FreeBSD.

Merge r204166 from head:

Document the interaction between /etc/devfs.conf and
/etc/defaults/devfs.conf

PR: docs/117308
Submitted by: Mel <mel.xyzzy rachie.is-a-geek.net> (partially)

Document the interaction between /etc/devfs.conf and
/etc/defaults/devfs.conf

PR: docs/117308
Submitted by: Mel <mel.xyzzy rachie.is-a-geek.net> (partially)
MFC after: 1 week

- Import the HEAD csup code which is the basis for the cvsmode work.

Support for filtering on major device number was removed in rev. 1.7 or
rule.c. Update man page example accordingly.

Submitted by: Mateusz Guzik <mjguzik@gmail.com>
PR: docs/124892

- I forgot to bump a date.

Approved by: keramida (mentor), trhodes (mentor) (implicit)

- add some files to FILES section and provide their description
- reference devfs.conf and devfs.rules in SEE ALSO section

Approved by: keramida (mentor), trhodes (mentor)
PR: docs/103347
MFC-after: 3 days

Markup fixes.

Approved by: re (blanket)

Use .Pa instead of .Xr to follow mdoc(7)
specifications.

Noticed by: trhodes
Approved by: trhodes (mentor)
MFC after: 1 day

Document the configuration files used.

PR: docs/79572
Submitted by: Josh Paetzel <josh@tcbug.org>
Approved by: trhodes (mentor)

Typo.

Submitted by: Hiroharu Tamaru <tamaru@myn.rcast.u-tokyo.ac.jp>

Remove filtering on major device number. These are assigned randomly
these days so filtering on them makes no sense other than as a foot-shooting
device.

Remove a useless use of cat, strip overzealous punctuation, and
clarify some text.

Parse file mode with setmode(3) for consistency with other programs
that do this kind of thing.

Get rid of duplicates.

Minor mdoc(7) cleanup, based on the PR below.

PR: docs/54826
Submitted by: Lukas Ertl <l.ertl@univie.ac.at>
Reviewed by: ru
Approved by: ceri (mentor)

Xref police: chmod(8) -> chmod(1).

mdoc(7) police: markup nits.

Approved by: re

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

Implement this (quoted from the updated man page): If the first token
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
(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
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