Remove single-space hard sentence breaks. These degrade the quality
of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
This commit is contained in:
parent
ef8f7ac935
commit
f63f700eea
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=57669
@ -132,7 +132,8 @@ The
|
||||
.Bx 4.4
|
||||
system differs from historical 4BSD systems in that the system call
|
||||
.Xr chown 2
|
||||
has been changed to follow symbolic links. The
|
||||
has been changed to follow symbolic links.
|
||||
The
|
||||
.Xr lchown 2
|
||||
system call was added later when the limitations of the new
|
||||
.Xr chown 2
|
||||
|
@ -163,8 +163,10 @@ in an effort to be backward compatible with older export file formats.
|
||||
exports strictly according to the spec (RFC 2054 and RFC 2055) can
|
||||
be done with the
|
||||
.Fl public
|
||||
flag. However, this flag in itself allows r/w access to all files in
|
||||
the filesystem, not requiring reserved ports and not remapping uids. It
|
||||
flag.
|
||||
However, this flag in itself allows r/w access to all files in
|
||||
the filesystem, not requiring reserved ports and not remapping uids.
|
||||
It
|
||||
is only provided to conform to the spec, and should normally not be used.
|
||||
For a
|
||||
.Tn WebNFS
|
||||
@ -186,7 +188,8 @@ A
|
||||
option can be used to specify a file whose handle will be returned if
|
||||
a directory is looked up using the public filehandle (
|
||||
.Tn WebNFS Ns ).
|
||||
This is to mimic the behavior of URLs. If no
|
||||
This is to mimic the behavior of URLs.
|
||||
If no
|
||||
.Fl index
|
||||
option is specified, a directory filehandle will be returned as usual.
|
||||
The
|
||||
|
@ -67,7 +67,8 @@ Any of the comma separated fields may be empty to specify a ``wildcard'' value
|
||||
or may consist of the string ``-'' to specify ``no valid value''.
|
||||
The members of the list may be separated by whitespace and/or commas;
|
||||
the ``\e'' character may be used at the end of a line to specify
|
||||
line continuation. Lines are limited to 1024 characters.
|
||||
line continuation.
|
||||
Lines are limited to 1024 characters.
|
||||
The functions specified in
|
||||
.Xr getnetgrent 3
|
||||
should normally be used to access the
|
||||
@ -82,25 +83,29 @@ are only used in conjunction with
|
||||
.Tn NIS
|
||||
and local
|
||||
.Pa /etc/netgroup
|
||||
files are ignored. With
|
||||
files are ignored.
|
||||
With
|
||||
.Fx ,
|
||||
.Nm Ns s
|
||||
can be used with either
|
||||
.Tn NIS
|
||||
or local files, but there are certain
|
||||
caveats to consider. The existing
|
||||
caveats to consider.
|
||||
The existing
|
||||
.Nm
|
||||
system is extremely inefficient where
|
||||
.Fn innetgr 3
|
||||
lookups are concerned since
|
||||
.Nm
|
||||
memberships are computed on the fly. By contrast, the
|
||||
memberships are computed on the fly.
|
||||
By contrast, the
|
||||
.Tn NIS
|
||||
.Nm
|
||||
database consists of three separate maps (netgroup, netgroup.byuser
|
||||
and netgroup.byhost) that are keyed to allow
|
||||
.Fn innetgr 3
|
||||
lookups to be done quickly. The
|
||||
lookups to be done quickly.
|
||||
The
|
||||
.Fx
|
||||
.Nm
|
||||
system can interact with the
|
||||
@ -152,7 +157,8 @@ token, the local data and the
|
||||
netgroup
|
||||
map will be processed as a single combined
|
||||
.Nm
|
||||
database. While this configuration is the most flexible, it
|
||||
database.
|
||||
While this configuration is the most flexible, it
|
||||
is also the least efficient: in particular,
|
||||
.Fn innetgr 3
|
||||
lookups will be especially slow if the
|
||||
|
@ -163,8 +163,10 @@ in an effort to be backward compatible with older export file formats.
|
||||
exports strictly according to the spec (RFC 2054 and RFC 2055) can
|
||||
be done with the
|
||||
.Fl public
|
||||
flag. However, this flag in itself allows r/w access to all files in
|
||||
the filesystem, not requiring reserved ports and not remapping uids. It
|
||||
flag.
|
||||
However, this flag in itself allows r/w access to all files in
|
||||
the filesystem, not requiring reserved ports and not remapping uids.
|
||||
It
|
||||
is only provided to conform to the spec, and should normally not be used.
|
||||
For a
|
||||
.Tn WebNFS
|
||||
@ -186,7 +188,8 @@ A
|
||||
option can be used to specify a file whose handle will be returned if
|
||||
a directory is looked up using the public filehandle (
|
||||
.Tn WebNFS Ns ).
|
||||
This is to mimic the behavior of URLs. If no
|
||||
This is to mimic the behavior of URLs.
|
||||
If no
|
||||
.Fl index
|
||||
option is specified, a directory filehandle will be returned as usual.
|
||||
The
|
||||
|
@ -67,7 +67,8 @@ Any of the comma separated fields may be empty to specify a ``wildcard'' value
|
||||
or may consist of the string ``-'' to specify ``no valid value''.
|
||||
The members of the list may be separated by whitespace and/or commas;
|
||||
the ``\e'' character may be used at the end of a line to specify
|
||||
line continuation. Lines are limited to 1024 characters.
|
||||
line continuation.
|
||||
Lines are limited to 1024 characters.
|
||||
The functions specified in
|
||||
.Xr getnetgrent 3
|
||||
should normally be used to access the
|
||||
@ -82,25 +83,29 @@ are only used in conjunction with
|
||||
.Tn NIS
|
||||
and local
|
||||
.Pa /etc/netgroup
|
||||
files are ignored. With
|
||||
files are ignored.
|
||||
With
|
||||
.Fx ,
|
||||
.Nm Ns s
|
||||
can be used with either
|
||||
.Tn NIS
|
||||
or local files, but there are certain
|
||||
caveats to consider. The existing
|
||||
caveats to consider.
|
||||
The existing
|
||||
.Nm
|
||||
system is extremely inefficient where
|
||||
.Fn innetgr 3
|
||||
lookups are concerned since
|
||||
.Nm
|
||||
memberships are computed on the fly. By contrast, the
|
||||
memberships are computed on the fly.
|
||||
By contrast, the
|
||||
.Tn NIS
|
||||
.Nm
|
||||
database consists of three separate maps (netgroup, netgroup.byuser
|
||||
and netgroup.byhost) that are keyed to allow
|
||||
.Fn innetgr 3
|
||||
lookups to be done quickly. The
|
||||
lookups to be done quickly.
|
||||
The
|
||||
.Fx
|
||||
.Nm
|
||||
system can interact with the
|
||||
@ -152,7 +157,8 @@ token, the local data and the
|
||||
netgroup
|
||||
map will be processed as a single combined
|
||||
.Nm
|
||||
database. While this configuration is the most flexible, it
|
||||
database.
|
||||
While this configuration is the most flexible, it
|
||||
is also the least efficient: in particular,
|
||||
.Fn innetgr 3
|
||||
lookups will be especially slow if the
|
||||
|
Loading…
Reference in New Issue
Block a user