On (2002/07/17 01:52), Dima Dorfman wrote:

> The devfs(8) manual page is a pretty good reference of the existing
> features and semantics, but it lacks polish needed to be able to serve
> as an introduction.

Actually, I think it's brilliant.

The only nits are the weird sections, which made it hard for me to find
my way around.  For example, the examples are all in an Examples
subsection of the non-standard RULE SUBSYSTEM section, so I didn't see
that there were examples when I first looked for them.

I'd suggest the attached patch, to make it easier for manpage die-hards
to navigate.

Great job, man!


Index: devfs.8
RCS file: /home/ncvs/src/sbin/devfs/devfs.8,v
retrieving revision 1.1
diff -u -d -r1.1 devfs.8
--- devfs.8     17 Jul 2002 01:46:47 -0000      1.1
+++ devfs.8     17 Jul 2002 16:25:02 -0000
@@ -62,7 +62,7 @@
 operates on
 .Pa /dev .
+.Ss Rule Subsystem
 .Xr devfs 5
 rule subsystem provides a way for the administrator of a system to control
@@ -207,9 +207,7 @@
 .It Cm unhide
 Unhide the node.
-.Ss Notes
-.Bl -bullet -offset indent
 Rulesets are created by the kernel at the first reference,
 and destroyed when the last reference disappears.
 E.g., a ruleset is created when a rule is added to it or when it is set
@@ -218,12 +216,12 @@
 and no other references to it exist
 (i.e., it is not included by any rules, and it is not the current ruleset
 for any mount-point).
 Ruleset number 0 is the default ruleset for all new mount-points.
 It is always empty, cannot be modified or deleted, and does not show up
 in the output of
 .Cm showsets .
 Rules and rulesets are unique to the entire system,
 not a particular mount-point.
 I.e., a
@@ -232,8 +230,7 @@
 .Fl m .
 The mount-point is only relevant when changing what its current ruleset is,
 or when using one of the apply commands.
-.Ss Examples
 When the system boots,
 the only ruleset that exists is ruleset number 0;
 since the latter may not be modified, we have to create another ruleset

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to