mdoc(7) police: s/BSD/.Bx/ where appropriate.
This commit is contained in:
Ruslan Ermilov
parent
e423aa38ba
commit
753d686d34
@ -181,7 +181,9 @@ The value
|
||||
.Cm oldascii
|
||||
specifies the one used in historic
|
||||
.Tn AT&T
|
||||
and pre-4.3BSD-reno systems.
|
||||
and
|
||||
.No pre- Ns Bx 4.3 reno
|
||||
systems.
|
||||
.It Cm block
|
||||
Treats the input as a sequence of newline or end-of-file terminated variable
|
||||
length records independent of input and output block boundaries.
|
||||
@ -226,7 +228,9 @@ and
|
||||
.Cm oldibm
|
||||
are maps used in historic
|
||||
.Tn AT&T
|
||||
and pre-4.3BSD-reno systems.
|
||||
and
|
||||
.No pre- Ns Bx 4.3 reno
|
||||
systems.
|
||||
.It Cm lcase
|
||||
Transform uppercase characters into lowercase characters.
|
||||
.It Cm noerror
|
||||
|
||||
@ -135,7 +135,9 @@ permissions, are not used by the system and cannot be changed.
|
||||
.Pp
|
||||
The
|
||||
.Bx 4.4
|
||||
system differs from historical 4BSD systems in that the system call
|
||||
system differs from historical
|
||||
.Bx 4
|
||||
systems in that the system call
|
||||
.Xr chown 2
|
||||
has been changed to follow symbolic links.
|
||||
The
|
||||
@ -238,7 +240,9 @@ option is specified.
|
||||
.Pp
|
||||
The
|
||||
.Bx 4.4
|
||||
system differs from historical 4BSD systems in that the
|
||||
system differs from historical
|
||||
.Bx 4
|
||||
systems in that the
|
||||
.Nm chown
|
||||
and
|
||||
.Nm chgrp
|
||||
|
||||
@ -727,7 +727,10 @@ by this format) which may be truncated by this format is detected by
|
||||
.Nm
|
||||
and is repaired.
|
||||
.It Ar tar
|
||||
The old BSD tar format as found in BSD4.3.
|
||||
The old
|
||||
.Bx
|
||||
tar format as found in
|
||||
.Bx 4.3 .
|
||||
The default blocksize for this format is 10240 bytes.
|
||||
Pathnames stored by this format must be 100 characters or less in length.
|
||||
Only
|
||||
|
||||
@ -68,7 +68,7 @@ as per
|
||||
.It Fl e
|
||||
Display all the current settings for the terminal to standard output
|
||||
in the traditional
|
||||
.Tn BSD
|
||||
.Bx
|
||||
``all'' and ``everything'' formats.
|
||||
.It Fl f
|
||||
Open and use the terminal named by
|
||||
|
||||
@ -343,4 +343,5 @@ file distributed with am-utils.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm amd
|
||||
utility first appeared in 4.4BSD.
|
||||
utility first appeared in
|
||||
.Bx 4.4 .
|
||||
|
||||
@ -210,4 +210,5 @@ file distributed with
|
||||
.Nm am-utils .
|
||||
.Sh HISTORY
|
||||
.Nm Amq
|
||||
first appeared in 4.4BSD.
|
||||
first appeared in
|
||||
.Bx 4.4 .
|
||||
|
||||
@ -462,7 +462,8 @@ is willing to receive an 8 bit data stream.
|
||||
Requests that the client handle flow control
|
||||
characters remotely.
|
||||
.It "DO ECHO"
|
||||
This is not really supported, but is sent to identify a 4.2BSD
|
||||
This is not really supported, but is sent to identify a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1
|
||||
client, which will improperly respond with
|
||||
.Dv WILL ECHO .
|
||||
@ -593,11 +594,13 @@ Some
|
||||
.Tn TELNET
|
||||
commands are only partially implemented.
|
||||
.Pp
|
||||
Because of bugs in the original 4.2 BSD
|
||||
Because of bugs in the original
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 ,
|
||||
.Nm
|
||||
performs some dubious protocol exchanges to try to discover if the remote
|
||||
client is, in fact, a 4.2 BSD
|
||||
client is, in fact, a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 .
|
||||
.Pp
|
||||
Binary mode
|
||||
|
||||
@ -462,7 +462,8 @@ is willing to receive an 8 bit data stream.
|
||||
Requests that the client handle flow control
|
||||
characters remotely.
|
||||
.It "DO ECHO"
|
||||
This is not really supported, but is sent to identify a 4.2BSD
|
||||
This is not really supported, but is sent to identify a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1
|
||||
client, which will improperly respond with
|
||||
.Dv WILL ECHO .
|
||||
@ -593,11 +594,13 @@ Some
|
||||
.Tn TELNET
|
||||
commands are only partially implemented.
|
||||
.Pp
|
||||
Because of bugs in the original 4.2 BSD
|
||||
Because of bugs in the original
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 ,
|
||||
.Nm
|
||||
performs some dubious protocol exchanges to try to discover if the remote
|
||||
client is, in fact, a 4.2 BSD
|
||||
client is, in fact, a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 .
|
||||
.Pp
|
||||
Binary mode
|
||||
|
||||
@ -153,4 +153,5 @@ default output file.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
utility first appeared in 4.4BSD.
|
||||
utility first appeared in
|
||||
.Bx 4.4 .
|
||||
|
||||
@ -239,7 +239,8 @@ Discard all local symbols in the input files.
|
||||
Trace the manipulations inflicted on
|
||||
.Ar symbol
|
||||
.It Fl Z
|
||||
Make a 386BSD
|
||||
Make a
|
||||
.Bx 386
|
||||
.Dv ZMAGIC
|
||||
output file.
|
||||
.It Fl z
|
||||
|
||||
@ -239,7 +239,8 @@ Discard all local symbols in the input files.
|
||||
Trace the manipulations inflicted on
|
||||
.Ar symbol
|
||||
.It Fl Z
|
||||
Make a 386BSD
|
||||
Make a
|
||||
.Bx 386
|
||||
.Dv ZMAGIC
|
||||
output file.
|
||||
.It Fl z
|
||||
|
||||
@ -122,7 +122,8 @@ netgroup database file
|
||||
The netgroup members have three string fields to maintain compatibility
|
||||
with other vendor implementations, however it is not obvious what use the
|
||||
.Sy domain
|
||||
string has within BSD.
|
||||
string has within
|
||||
.Bx .
|
||||
.Sh BUGS
|
||||
The function
|
||||
.Fn getnetgrent
|
||||
|
||||
@ -472,7 +472,9 @@ member of
|
||||
Note that you should not assign SIG_DFL or SIG_IGN this way.
|
||||
.Pp
|
||||
If the SA_SIGINFO flag is not set, the handler function should match
|
||||
either the ANSI C or traditional BSD prototype and be pointed to by
|
||||
either the ANSI C or traditional
|
||||
.Bx
|
||||
prototype and be pointed to by
|
||||
the
|
||||
.Dv sa_handler
|
||||
member of
|
||||
@ -486,9 +488,13 @@ The
|
||||
member declaration in
|
||||
.Fx
|
||||
include files is that of ANSI C (as required by POSIX),
|
||||
so a function pointer of a BSD-style function needs to be casted to
|
||||
so a function pointer of a
|
||||
.Bx Ns -style
|
||||
function needs to be casted to
|
||||
compile without warning.
|
||||
The traditional BSD style is not portable and since its capabilities
|
||||
The traditional
|
||||
.Bx
|
||||
style is not portable and since its capabilities
|
||||
are a full subset of a SA_SIGINFO handler,
|
||||
its use is deprecated.
|
||||
.Pp
|
||||
@ -500,7 +506,9 @@ values from <signal.h>.
|
||||
.Pp
|
||||
The
|
||||
.Fa code
|
||||
argument of the BSD-style handler and the
|
||||
argument of the
|
||||
.Bx Ns -style
|
||||
handler and the
|
||||
.Dv si_code
|
||||
member of the
|
||||
.Dv info
|
||||
@ -514,7 +522,9 @@ values for SIGFPE.
|
||||
.Pp
|
||||
The
|
||||
.Fa scp
|
||||
argument to a BSD-style handler points to an instance of struct
|
||||
argument to a
|
||||
.Bx Ns -style
|
||||
handler points to an instance of struct
|
||||
sigcontext.
|
||||
.Pp
|
||||
The
|
||||
@ -567,7 +577,7 @@ as are the signals,
|
||||
and
|
||||
.Dv SIGINFO .
|
||||
Those signals are available on most
|
||||
.Tn BSD Ns \-derived
|
||||
.Bx Ns \-derived
|
||||
systems.
|
||||
The
|
||||
.Dv SA_NODEFER
|
||||
|
||||
@ -85,7 +85,7 @@ This system call is used by the trampoline code and
|
||||
when returning from a signal to the previously executing program.
|
||||
.Sh NOTES
|
||||
This system call is not available in 4.2
|
||||
.Tn BSD
|
||||
.Bx
|
||||
hence it should not be used if backward compatibility is needed.
|
||||
.Sh RETURN VALUES
|
||||
If successful, the system call does not return.
|
||||
|
||||
@ -100,4 +100,5 @@ points outside the process's allocated address space.
|
||||
.Sh HISTORY
|
||||
An
|
||||
.Fn undelete
|
||||
function call first appeared in 4.4BSD-Lite.
|
||||
function call first appeared in
|
||||
.Bx 4.4 Lite .
|
||||
|
||||
@ -522,7 +522,10 @@ go here; Peter Dufault first read about it in a 1989 Sun Expert magazine.
|
||||
The new CCB data structures are derived from the CAM-2 and CAM-3
|
||||
specifications.
|
||||
.Pp
|
||||
Peter Dufault implemented a clone of SGI's interface in 386bsd that
|
||||
.An Peter Dufault
|
||||
implemented a clone of SGI's interface in
|
||||
.Bx 386
|
||||
that
|
||||
led to the original
|
||||
.Fx
|
||||
.Tn SCSI
|
||||
|
||||
@ -180,7 +180,9 @@ values for a
|
||||
.It CHUNK_PAST_1024
|
||||
This chunk cannot be booted from because it extends past cylinder 1024.
|
||||
.It CHUNK_BSD_COMPAT
|
||||
This chunk is in the BSD-compatibility, and has a short name too, i.e.\&
|
||||
This chunk is in the
|
||||
.Bx Ns -compatibility ,
|
||||
and has a short name too, i.e.\&
|
||||
.Ql wd0s4f -> wd0f .
|
||||
.It CHUNK_ALIGN
|
||||
This chunk should be aligned.
|
||||
|
||||
@ -72,7 +72,9 @@ Accordingly, the generic portion of the interface (i.e.,
|
||||
.Fn kvm_write ,
|
||||
and
|
||||
.Fn kvm_nlist )
|
||||
has been incorporated into the BSD interface. Indeed, many kvm
|
||||
has been incorporated into the
|
||||
.Bx
|
||||
interface. Indeed, many kvm
|
||||
applications (i.e., debuggers and statistical monitors) use only
|
||||
this subset of the interface.
|
||||
.Pp
|
||||
@ -84,7 +86,9 @@ Finally, the Sun kvm error reporting semantics are poorly defined.
|
||||
The library can be configured either to print errors to stderr automatically,
|
||||
or to print no error messages at all.
|
||||
In the latter case, the nature of the error cannot be determined.
|
||||
To overcome this, the BSD interface includes a
|
||||
To overcome this, the
|
||||
.Bx
|
||||
interface includes a
|
||||
routine,
|
||||
.Xr kvm_geterr 3 ,
|
||||
to return (not print out) the error message
|
||||
|
||||
@ -131,7 +131,9 @@ call.
|
||||
.Pp
|
||||
The
|
||||
.Fn kvm_openfiles
|
||||
function provides BSD style error reporting.
|
||||
function provides
|
||||
.Bx
|
||||
style error reporting.
|
||||
Here, error messages are not printed out by the library.
|
||||
Instead, the application obtains the error message
|
||||
corresponding to the most recent kvm library call using
|
||||
@ -174,7 +176,9 @@ function returns 0 on success and -1 on failure.
|
||||
.Sh BUGS
|
||||
There should not be two open calls. The ill-defined error semantics
|
||||
of the Sun library and the desire to have a backward-compatible library
|
||||
for BSD left little choice.
|
||||
for
|
||||
.Bx
|
||||
left little choice.
|
||||
.Sh SEE ALSO
|
||||
.Xr open 2 ,
|
||||
.Xr kvm 3 ,
|
||||
|
||||
@ -35,7 +35,9 @@
|
||||
.Sh DESCRIPTION
|
||||
.Nm
|
||||
provides a set of supporting functions for standalone
|
||||
applications, mimicking where possible the standard BSD programming
|
||||
applications, mimicking where possible the standard
|
||||
.Bx
|
||||
programming
|
||||
environment. The following sections group these functions by kind.
|
||||
Unless specifically described here, see the corresponding section 3
|
||||
manpages for the given functions.
|
||||
@ -573,7 +575,9 @@ structures. The following filesystem handlers are supplied by
|
||||
the consumer may supply other filesystems of their own:
|
||||
.Bl -hang -width "cd9660_fsops "
|
||||
.It ufs_fsops
|
||||
The BSD UFS.
|
||||
The
|
||||
.Bx
|
||||
UFS.
|
||||
.It ext2fs_fsops
|
||||
Linux ext2fs filesystem.
|
||||
.It tftp_fsops
|
||||
|
||||
@ -451,7 +451,8 @@ is willing to receive an 8 bit data stream.
|
||||
Requests that the client handle flow control
|
||||
characters remotely.
|
||||
.It "DO ECHO"
|
||||
This is not really supported, but is sent to identify a 4.2BSD
|
||||
This is not really supported, but is sent to identify a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1
|
||||
client, which will improperly respond with
|
||||
.Dv WILL ECHO .
|
||||
@ -608,11 +609,13 @@ Some
|
||||
.Tn TELNET
|
||||
commands are only partially implemented.
|
||||
.Pp
|
||||
Because of bugs in the original 4.2 BSD
|
||||
Because of bugs in the original
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 ,
|
||||
.Nm
|
||||
performs some dubious protocol exchanges to try to discover if the remote
|
||||
client is, in fact, a 4.2 BSD
|
||||
client is, in fact, a
|
||||
.Bx 4.2
|
||||
.Xr telnet 1 .
|
||||
.Pp
|
||||
Binary mode
|
||||
|
||||
@ -886,7 +886,9 @@ or
|
||||
thus replacing the
|
||||
.Em fdisk
|
||||
table by the dummy one in the bootstrap program. This is only of
|
||||
concern if the disk is fully dedicated, so that the BSD disklabel
|
||||
concern if the disk is fully dedicated, so that the
|
||||
.Bx
|
||||
disklabel
|
||||
starts at absolute block 0 on the disk.
|
||||
.Pp
|
||||
.Nm
|
||||
|
||||
@ -717,7 +717,9 @@ utility and
|
||||
.Xr scsi 3
|
||||
library, written by Julian Elischer and Peter Dufault. The
|
||||
.Xr scsi 8
|
||||
program first appeared in 386BSD 0.1.2.4, and first appeared in
|
||||
program first appeared in
|
||||
.Bx 386 0.1.2.4 ,
|
||||
and first appeared in
|
||||
.Fx
|
||||
in
|
||||
.Fx 2.0.5 .
|
||||
|
||||
@ -57,6 +57,7 @@ dialout devices
|
||||
.Sh AUTHORS
|
||||
.An Christopher G. Demetriou
|
||||
.Sh HISTORY
|
||||
Originally part of cgd's com package patches, version 0.2.1, to 386BSD 0.1.
|
||||
Originally part of cgd's com package patches, version 0.2.1, to
|
||||
.Bx 386 0.1 .
|
||||
Once controlled bidirectional capabilities. Little is left to control now
|
||||
that these capabilities are standard.
|
||||
|
||||
@ -57,10 +57,14 @@ implementation is used (see RFC-1548, RFC-1549).
|
||||
.It cisco
|
||||
Set the link-level protocol: Cisco/HDLC (see RFC-1547).
|
||||
This protocol is intended for compatibility with old models of Cisco routers,
|
||||
and with early versions of BSD/386 drivers.
|
||||
and with early versions of
|
||||
.Tn BSD/386
|
||||
drivers.
|
||||
The extensive usage of this protocol is not recommended.
|
||||
.It ext
|
||||
Use the external link-level protocol suite (for BSD/386 only).
|
||||
Use the external link-level protocol suite (for
|
||||
.Tn BSD/386
|
||||
only).
|
||||
.It "+keepalive, -keepalive"
|
||||
Enable the automatic line state control sub-protocol.
|
||||
This setting is not significant when the external link-level protocol is used.
|
||||
@ -297,7 +301,8 @@ cxconfig cx0 hdlc 256000 cisco +keepalive -extclock
|
||||
ifconfig cx0 200.1.1.1 200.1.1.2 up
|
||||
.Ed
|
||||
.Pp
|
||||
Set up the channel 1 of the adapter Sigma-840 under BSD/386.
|
||||
Set up the channel 1 of the adapter Sigma-840 under
|
||||
.Tn BSD/386 .
|
||||
Synchronous 64 kbit/sec leased line, external clock source.
|
||||
Synchronous mode, interface V.35, external protocol suite:
|
||||
.Bd -literal
|
||||
|
||||
@ -886,7 +886,9 @@ or
|
||||
thus replacing the
|
||||
.Em fdisk
|
||||
table by the dummy one in the bootstrap program. This is only of
|
||||
concern if the disk is fully dedicated, so that the BSD disklabel
|
||||
concern if the disk is fully dedicated, so that the
|
||||
.Bx
|
||||
disklabel
|
||||
starts at absolute block 0 on the disk.
|
||||
.Pp
|
||||
.Nm
|
||||
|
||||
@ -57,10 +57,14 @@ implementation is used (see RFC-1548, RFC-1549).
|
||||
.It cisco
|
||||
Set the link-level protocol: Cisco/HDLC (see RFC-1547).
|
||||
This protocol is intended for compatibility with old models of Cisco routers,
|
||||
and with early versions of BSD/386 drivers.
|
||||
and with early versions of
|
||||
.Tn BSD/386
|
||||
drivers.
|
||||
The extensive usage of this protocol is not recommended.
|
||||
.It ext
|
||||
Use the external link-level protocol suite (for BSD/386 only).
|
||||
Use the external link-level protocol suite (for
|
||||
.Tn BSD/386
|
||||
only).
|
||||
.It "+keepalive, -keepalive"
|
||||
Enable the automatic line state control sub-protocol.
|
||||
This setting is not significant when the external link-level protocol is used.
|
||||
@ -297,7 +301,8 @@ cxconfig cx0 hdlc 256000 cisco +keepalive -extclock
|
||||
ifconfig cx0 200.1.1.1 200.1.1.2 up
|
||||
.Ed
|
||||
.Pp
|
||||
Set up the channel 1 of the adapter Sigma-840 under BSD/386.
|
||||
Set up the channel 1 of the adapter Sigma-840 under
|
||||
.Tn BSD/386 .
|
||||
Synchronous 64 kbit/sec leased line, external clock source.
|
||||
Synchronous mode, interface V.35, external protocol suite:
|
||||
.Bd -literal
|
||||
|
||||
@ -155,10 +155,14 @@ There is a 60 second delay between each attempt.
|
||||
Use TCP transport instead of UDP.
|
||||
This is recommended for servers that are not on the same LAN cable as
|
||||
the client.
|
||||
(NB: This is NOT supported by most non-BSD servers.)
|
||||
(NB: This is NOT supported by most
|
||||
.No non- Ns Bx
|
||||
servers.)
|
||||
.It Fl U
|
||||
Force the mount protocol to use UDP transport, even for TCP NFS mounts.
|
||||
(Necessary for some old BSD servers.)
|
||||
(Necessary for some old
|
||||
.Bx
|
||||
servers.)
|
||||
.It Fl a
|
||||
Set the read-ahead count to the specified value.
|
||||
This may be in the range of 0 - 4, and determines how many blocks
|
||||
@ -349,4 +353,6 @@ to have limited success.
|
||||
For clients mounting servers that are not on the same
|
||||
LAN cable or that tend to be overloaded,
|
||||
TCP transport is strongly recommended,
|
||||
but unfortunately this is restricted to mostly 4.4BSD servers.
|
||||
but unfortunately this is restricted to mostly
|
||||
.Bx 4.4
|
||||
servers.
|
||||
|
||||
@ -215,7 +215,9 @@ Documentation from NetWare NDK.
|
||||
.Pp
|
||||
Ncpfs for Linux - written by
|
||||
.An Volker Lendecke Aq lendecke@math.uni\-goettingen.de .
|
||||
He granted me permission to publish parts of his code under BSD-style license,
|
||||
He granted me permission to publish parts of his code under
|
||||
.Bx Ns -style
|
||||
license,
|
||||
.Pp
|
||||
"Interrupt List" from
|
||||
.An Ralf Brown ,
|
||||
|
||||
@ -82,7 +82,7 @@ Volume label (up to 11 characters). The label should consist of
|
||||
only those characters permitted in regular DOS (8+3) filenames.
|
||||
.It Fl O Ar OEM
|
||||
OEM string (up to 8 characters). The default is
|
||||
"BSD 4.4".
|
||||
.Qq Li "BSD 4.4" .
|
||||
.It Fl S Ar sector-size
|
||||
Number of bytes per sector. Acceptable values are powers of 2
|
||||
in the range 128 through 32768.
|
||||
|
||||
@ -144,7 +144,9 @@ SCSI disk on any supported SCSI controller
|
||||
The unit number of the drive on the interface being used.
|
||||
0 for the first drive, 1 for the second drive, etc.
|
||||
.It Ar part
|
||||
The partition letter inside the BSD portion of the disk. See
|
||||
The partition letter inside the
|
||||
.Bx
|
||||
portion of the disk. See
|
||||
.Xr disklabel 8 .
|
||||
By convention, only partition
|
||||
.Ql a
|
||||
|
||||
@ -721,7 +721,9 @@ Data link protocols with variable length headers are not currently supported.
|
||||
.Sh HISTORY
|
||||
The Enet packet filter was created in 1980 by Mike Accetta and
|
||||
Rick Rashid at Carnegie-Mellon University. Jeffrey Mogul, at
|
||||
Stanford, ported the code to BSD and continued its development from
|
||||
Stanford, ported the code to
|
||||
.Bx
|
||||
and continued its development from
|
||||
1983 on. Since then, it has evolved into the Ultrix Packet Filter
|
||||
at
|
||||
.Tn DEC ,
|
||||
|
||||
@ -105,7 +105,8 @@ have the latest firmware for your controller.
|
||||
.Sh AUTHORS
|
||||
.An -nosplit
|
||||
.An Julian Elischer
|
||||
wrote a driver for the Multimaster cards that appeared in the 386BSD
|
||||
wrote a driver for the Multimaster cards that appeared in the
|
||||
.Bx 386
|
||||
patch kit. The driver was rewritten by
|
||||
.An Justin T. Gibbs
|
||||
to take advantage of new board features and work with the CAM SCSI framework in
|
||||
@ -133,4 +134,6 @@ ISA/VL Bus Driver Attachment
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
driver first appeared in the 386BSD patch kit.
|
||||
driver first appeared in the
|
||||
.Bx 386
|
||||
patch kit.
|
||||
|
||||
@ -451,7 +451,9 @@ This
|
||||
.Nm
|
||||
driver is based upon the
|
||||
.Nm
|
||||
driver written by Julian Elischer, which appeared in 386BSD 0.1. The
|
||||
driver written by Julian Elischer, which appeared in
|
||||
.Bx 386 0.1 .
|
||||
The
|
||||
CAM version of the
|
||||
.Nm
|
||||
driver was written by Kenneth Merry and first appeared in
|
||||
|
||||
@ -304,4 +304,5 @@ codes to the ioctls described here.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
driver appeared in 386BSD 0.1.
|
||||
driver appeared in
|
||||
.Bx 386 0.1 .
|
||||
|
||||
@ -579,7 +579,8 @@ methods.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
debugger was developed for Mach, and ported to 386BSD 0.1.
|
||||
debugger was developed for Mach, and ported to
|
||||
.Bx 386 0.1 .
|
||||
This manual page translated from
|
||||
.Fl man
|
||||
macros by Garrett Wollman.
|
||||
|
||||
@ -122,7 +122,9 @@ and may be supported by future versions of the driver.
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/(r)mcd0a -compact
|
||||
.It Pa /dev/(r)mcd0a
|
||||
accesses BSD partition on the disc.
|
||||
accesses
|
||||
.Bx
|
||||
partition on the disc.
|
||||
Normally, there is only
|
||||
one file system on a CD-ROM disc.
|
||||
.It Pa /dev/(r)mcd0c
|
||||
|
||||
@ -43,7 +43,9 @@ card or a compatible clone.
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/[r]scd0a -compact
|
||||
.It Pa /dev/[r]scd0a
|
||||
accesses BSD partition on the disc.
|
||||
accesses
|
||||
.Bx
|
||||
partition on the disc.
|
||||
Normally, there is only
|
||||
one file system on a CDROM disc.
|
||||
.It Pa /dev/[r]scd0c
|
||||
|
||||
@ -65,7 +65,9 @@ This whole interface is a crude hack to produce STREAMS semantics
|
||||
through emulation over sockes.
|
||||
.Pp
|
||||
Programmers who hope to be able to use this interface to provide
|
||||
SVR4 STREAMS services to BSD applications will be sorely disappointed.
|
||||
SVR4 STREAMS services to
|
||||
.Bx
|
||||
applications will be sorely disappointed.
|
||||
.Sh SEE ALSO
|
||||
.Xr svr4 4
|
||||
.Sh HISTORY
|
||||
|
||||
@ -7,7 +7,9 @@
|
||||
.Nm natm
|
||||
.Nd Native Mode ATM protocol layer
|
||||
.Sh DESCRIPTION
|
||||
The BSD ATM software comes with a
|
||||
The
|
||||
.Bx
|
||||
ATM software comes with a
|
||||
.Em native mode ATM protocol layer
|
||||
which provides socket level access to AAL0 and AAL5 virtual circuits.
|
||||
To enable this protocol layer, add
|
||||
|
||||
@ -297,7 +297,8 @@ An example is the node type
|
||||
.Em socket
|
||||
which is both a netgraph node and a
|
||||
.Xr socket 2
|
||||
BSD socket in the protocol family
|
||||
.Bx
|
||||
socket in the protocol family
|
||||
.Dv PF_NETGRAPH .
|
||||
Socket nodes allow user processes to participate in
|
||||
.Nm .
|
||||
|
||||
@ -45,7 +45,9 @@
|
||||
.Sh DESCRIPTION
|
||||
A
|
||||
.Nm ksocket
|
||||
node is both a netgraph node and a BSD socket. The
|
||||
node is both a netgraph node and a
|
||||
.Bx
|
||||
socket. The
|
||||
.Nm
|
||||
node type allows one to open a socket inside the kernel and have
|
||||
it appear as a Netgraph node. The
|
||||
|
||||
@ -47,11 +47,15 @@
|
||||
.Sh DESCRIPTION
|
||||
A
|
||||
.Nm socket
|
||||
node is both a BSD socket and a netgraph node. The
|
||||
node is both a
|
||||
.Bx
|
||||
socket and a netgraph node. The
|
||||
.Nm
|
||||
node type allows user-mode processes to participate in the kernel
|
||||
.Xr netgraph 4
|
||||
networking subsystem using the BSD socket interface. The process must have
|
||||
networking subsystem using the
|
||||
.Bx
|
||||
socket interface. The process must have
|
||||
root privileges to be able to create netgraph sockets however once created,
|
||||
any process that has one may use it.
|
||||
.Pp
|
||||
|
||||
@ -691,7 +691,8 @@ Documents the various compile-time options to tailor
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
driver has been developed for and contributed to 386BSD 0.1.
|
||||
driver has been developed for and contributed to
|
||||
.Bx 386 0.1 .
|
||||
Since then
|
||||
.Nm
|
||||
has become a standard part of
|
||||
|
||||
@ -100,13 +100,17 @@ Currently the following screen saver modules are available:
|
||||
.It Pa blank_saver.ko
|
||||
This screen saver simply blanks the screen.
|
||||
.It Pa daemon_saver.ko
|
||||
Animated BSD Daemon screen saver.
|
||||
Animated
|
||||
.Bx
|
||||
Daemon screen saver.
|
||||
.It Pa fade_saver.ko
|
||||
The screen will gradually fade away.
|
||||
.It Pa green_saver.ko
|
||||
If the monitor supports power saving mode, it will be turned off.
|
||||
.It Pa logo_saver.ko
|
||||
Animated graphical BSD Daemon.
|
||||
Animated graphical
|
||||
.Bx
|
||||
Daemon.
|
||||
.It Pa rain_saver.ko
|
||||
Draws a shower on the screen.
|
||||
.It Pa snake_saver.ko
|
||||
|
||||
@ -299,7 +299,9 @@ which was ported from the
|
||||
driver to Linux-1.2.13.
|
||||
The original
|
||||
.Xr ncr 4
|
||||
driver was written for 386BSD and
|
||||
driver was written for
|
||||
.Bx 386
|
||||
and
|
||||
.Fx
|
||||
by
|
||||
.An Wolfgang Stanglmeier
|
||||
|
||||
@ -554,7 +554,9 @@ segment resides in memory.
|
||||
.It Dv p_paddr
|
||||
On systems for which physical addressing is relevant, this member is
|
||||
reserved for the segment's physical address.
|
||||
Under BSD this member is
|
||||
Under
|
||||
.Bx
|
||||
this member is
|
||||
not used and must be zero.
|
||||
.It Dv p_filesz
|
||||
This member holds the number of bytes in the file image of the segment.
|
||||
|
||||
@ -37,7 +37,8 @@
|
||||
.Fd #include <time.h>
|
||||
.Sh DESCRIPTION
|
||||
.Ql HZ
|
||||
is not part of the application interface in BSD.
|
||||
is not part of the application interface in
|
||||
.Bx .
|
||||
.Pp
|
||||
There are many different real and virtual (timekeeping) clocks with
|
||||
different frequencies:
|
||||
@ -107,14 +108,18 @@ The mc14618a clock. This is a real clock with a nominal frequency of
|
||||
clock. It isn't available to applications.
|
||||
.It
|
||||
The microseconds clock. This is a virtual clock with frequency
|
||||
1000000. It is used for most timekeeping in BSD and is exported
|
||||
1000000. It is used for most timekeeping in
|
||||
.Bx
|
||||
and is exported
|
||||
to applications in
|
||||
.Xr getrusage 2 ,
|
||||
.Xr gettimeofday 2 ,
|
||||
.Xr select 2 ,
|
||||
.Xr getitimer 2 ,
|
||||
etc... This is the clock that should normally be used
|
||||
by BSD applications.
|
||||
by
|
||||
.Bx
|
||||
applications.
|
||||
.It
|
||||
The i8254 clock. This is a real clock/timer with a nominal frequency of
|
||||
1193182. It is divided down to give the scheduling clock. It isn't
|
||||
|
||||
@ -588,7 +588,8 @@ see
|
||||
.Xr tzfile 5
|
||||
.El
|
||||
.It Pa src/
|
||||
BSD, third-party, and/or local source files
|
||||
.Bx ,
|
||||
third-party, and/or local source files
|
||||
.Pp
|
||||
.Bl -tag -width "kerberosIV/" -compact
|
||||
.It Pa bin/
|
||||
|
||||
@ -40,7 +40,9 @@ administrators to install applications.
|
||||
Each
|
||||
.Em port
|
||||
contains any patches necessary to make the original
|
||||
application source code compile and run on BSD. Compiling an
|
||||
application source code compile and run on
|
||||
.Bx .
|
||||
Compiling an
|
||||
application is as simple as typing
|
||||
.Ic make build
|
||||
in the port directory! The
|
||||
|
||||
@ -502,7 +502,8 @@ and attempts to restore the chain to its original state.
|
||||
See above.
|
||||
.Sh HISTORY
|
||||
.\" Please correct me if I'm wrong
|
||||
Mbufs appeared in an early version of BSD.
|
||||
Mbufs appeared in an early version of
|
||||
.Bx .
|
||||
Besides for being used for network packets, they were used
|
||||
to store various dynamic structures, such as routing table
|
||||
entries, interface addresses, protocol control blocks, etc.
|
||||
|
||||
@ -85,7 +85,9 @@ is a test macro that sorts out when extensions should be
|
||||
visible. It is defined in <sys/_posix.h>.
|
||||
.Pp
|
||||
In normal C program development
|
||||
only _POSIX_VERSION is set, permitting BSD extensions to
|
||||
only _POSIX_VERSION is set, permitting
|
||||
.Bx
|
||||
extensions to
|
||||
appear to the programs. However, when adding new functionality mandated
|
||||
by POSIX.1B, it
|
||||
is important to satisfy the requirements added by the
|
||||
@ -99,16 +101,21 @@ is present to conditionalize POSIX.1B extensions that were historically
|
||||
in the system. These are visible when _POSIX_SOURCE and _POSIX_C_SOURCE
|
||||
are not set at all or when _POSIX_C_SOURCE enables POSIX.1B features.
|
||||
The intent of this feature test is to permit hiding the new extensions
|
||||
while still letting BSD extensions show up to avoid breaking existing
|
||||
while still letting
|
||||
.Bx
|
||||
extensions show up to avoid breaking existing
|
||||
programs without trying to use the "big hammer" of _POSIX_C_SOURCE.
|
||||
.Pp
|
||||
Some recent additions to header files
|
||||
are new enough that they should be changed to
|
||||
be dependent on _P1003_1B_VISIBLE instead of _HISTORICALLY.
|
||||
.Pp
|
||||
Traditional BSD headers (e.g., mmap.h) now specified
|
||||
Traditional
|
||||
.Bx
|
||||
headers (e.g., mmap.h) now specified
|
||||
in POSIX.1B can include <sys/_posix.h> and conditionalize
|
||||
BSD extensions on _P1003_1B_VISIBLE_HISTORICALLY.
|
||||
.Bx
|
||||
extensions on _P1003_1B_VISIBLE_HISTORICALLY.
|
||||
.Sh NON STANDARD TEST MACROS
|
||||
.Bd -literal -offset 0i
|
||||
_P1003_1B_INCLUDE_MAYBES
|
||||
|
||||
@ -593,8 +593,8 @@ or
|
||||
.Sh HISTORY
|
||||
This man page is largely based on the src/admin/style/style file from
|
||||
the
|
||||
.Tn BSD
|
||||
4.4-Lite2 release, with updates to reflect the current practice and
|
||||
.Bx 4.4 Lite2
|
||||
release, with updates to reflect the current practice and
|
||||
desire of the
|
||||
.Fx
|
||||
project.
|
||||
|
||||
@ -209,6 +209,8 @@ in the paper
|
||||
.%T "Hashed and Hierarchical Timing Wheels: Data Structures for the Efficient Implementation of a Timer Facility"
|
||||
in the
|
||||
.%B "Proceedings of the 11th ACM Annual Symposium on Operating Systems Principles" .
|
||||
The current implementation replaces the long standing BSD linked list
|
||||
The current implementation replaces the long standing
|
||||
.Bx
|
||||
linked list
|
||||
callout mechanism which offered O(n) insertion and removal running time
|
||||
but did not generate or require handles for untimeout operations.
|
||||
|
||||
@ -158,7 +158,9 @@ entries, and that one by random selection.
|
||||
The
|
||||
.Ar group
|
||||
field is the group that the user will be placed in at login.
|
||||
Since BSD supports multiple groups (see
|
||||
Since
|
||||
.Bx
|
||||
supports multiple groups (see
|
||||
.Xr groups 1 )
|
||||
this field currently has little special meaning.
|
||||
This field may be filled in with either a number or a group name (see
|
||||
|
||||
@ -760,4 +760,5 @@ For this to work, the X programmer's kit must have been installed.
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
program first appeared in BSD/386.
|
||||
program first appeared in
|
||||
.Tn BSD/386 .
|
||||
|
||||
@ -55,7 +55,9 @@ releases the lock, and removes the
|
||||
.Ar file
|
||||
unless the
|
||||
.Fl k
|
||||
option is specified. BSD-style locking is used, as described in
|
||||
option is specified.
|
||||
.Bx Ns -style
|
||||
locking is used, as described in
|
||||
.Xr flock 2 ;
|
||||
the mere existence of the
|
||||
.Ar file
|
||||
|
||||
@ -336,7 +336,9 @@ command appeared in
|
||||
.Pp
|
||||
Extensions regarding the
|
||||
.Xr st 4
|
||||
driver appeared in 386BSD 0.1 as a separate
|
||||
driver appeared in
|
||||
.Bx 386 0.1
|
||||
as a separate
|
||||
.Xr st 1
|
||||
command, and have been merged into the
|
||||
.Nm
|
||||
|
||||
@ -249,7 +249,9 @@ Strip out non-printable characters from file1.
|
||||
.D1 Li "tr -cd \*q[:print:]\*q < file1"
|
||||
.Sh COMPATIBILITY
|
||||
System V has historically implemented character ranges using the syntax
|
||||
``[c-c]'' instead of the ``c-c'' used by historic BSD implementations and
|
||||
``[c-c]'' instead of the ``c-c'' used by historic
|
||||
.Bx
|
||||
implementations and
|
||||
standardized by POSIX.
|
||||
System V shell scripts should work under this implementation as long as
|
||||
the range is intended to map in another range, i.e. the command
|
||||
|
||||
@ -358,7 +358,9 @@ and
|
||||
options have been deleted from the
|
||||
.Nm
|
||||
utility.
|
||||
None of them were documented in 4.3BSD and all are of limited utility at
|
||||
None of them were documented in
|
||||
.Bx 4.3
|
||||
and all are of limited utility at
|
||||
best.
|
||||
The
|
||||
.Fl a ,
|
||||
|
||||
@ -97,7 +97,10 @@ characters delimited by <space>, <tab> or <newline> characters''.
|
||||
The implementation, however, didn't handle non-printing characters
|
||||
correctly so that `` ^D^E '' counted as 6 spaces, while ``foo^D^Ebar''
|
||||
counted as 8 characters.
|
||||
4BSD systems after 4.3BSD modified the implementation to be consistent
|
||||
.Bx 4
|
||||
systems after
|
||||
.Bx 4.3
|
||||
modified the implementation to be consistent
|
||||
with the documentation.
|
||||
This implementation defines a ``word'' in terms of the
|
||||
.Xr isspace 3
|
||||
|
||||
@ -154,7 +154,9 @@ user in
|
||||
.Pa /tmp
|
||||
or
|
||||
.Pa /var/tmp
|
||||
as symbolic links on 4.4BSD filesystems do not contain information
|
||||
as symbolic links on
|
||||
.Bx 4.4
|
||||
filesystems do not contain information
|
||||
as to who created them. Also, there may be other files created in
|
||||
.Pa /var/mail
|
||||
other than
|
||||
|
||||
@ -52,7 +52,9 @@ Note that what are referred to here as
|
||||
.Dq slices
|
||||
are typically called
|
||||
.Dq partitions
|
||||
in non-BSD documentation relating to the PC.
|
||||
in
|
||||
.No non- Ns Bx
|
||||
documentation relating to the PC.
|
||||
Typically, only non-removable disks are sliced.
|
||||
.Pp
|
||||
The
|
||||
|
||||
@ -92,6 +92,10 @@ Exit status is 0 if no errors were detected, 1 if errors were found in
|
||||
a distribution, and 2 if usage errors, inaccessible input files, or
|
||||
other system errors were encountered.
|
||||
.Sh NOTES
|
||||
Both BSD and DOS versions of
|
||||
Both
|
||||
.Bx
|
||||
and
|
||||
.Tn DOS
|
||||
versions of
|
||||
.Nm
|
||||
are available.
|
||||
|
||||
@ -157,12 +157,16 @@ to extract the configuration information, use the command
|
||||
strings kernel | grep ___
|
||||
.Ed
|
||||
.Sh DEBUG KERNELS
|
||||
Traditional BSD kernels compiled without symbols due to the heavy load on the
|
||||
Traditional
|
||||
.Bx
|
||||
kernels compiled without symbols due to the heavy load on the
|
||||
system when compiling a
|
||||
.Dq debug
|
||||
kernel. A debug kernel contains complete symbols for all the source files, and
|
||||
enables an experienced kernel programmer to analyse the cause of a problem. The
|
||||
debuggers available prior to 4.4BSD-Lite were able to find some information
|
||||
debuggers available prior to
|
||||
.Bx 4.4 Lite
|
||||
were able to find some information
|
||||
from a normal kernel;
|
||||
.Xr gdb 1
|
||||
provides very little support for normal kernels, and a debug kernel is needed
|
||||
|
||||
@ -86,7 +86,9 @@ may not.
|
||||
.Ev LOGNAME
|
||||
variable is sometimes called
|
||||
.Ev USER
|
||||
on BSD systems...
|
||||
on
|
||||
.Bx
|
||||
systems...
|
||||
On these systems,
|
||||
.Ev USER
|
||||
will be set also).
|
||||
@ -223,20 +225,33 @@ MAILTO=paul
|
||||
.Xr cron 8
|
||||
.Sh EXTENSIONS
|
||||
When specifying day of week, both day 0 and day 7 will be considered Sunday.
|
||||
BSD and ATT seem to disagree about this.
|
||||
.Bx
|
||||
and
|
||||
.Tn ATT
|
||||
seem to disagree about this.
|
||||
.Pp
|
||||
Lists and ranges are allowed to co-exist in the same field. "1-3,7-9" would
|
||||
be rejected by ATT or BSD cron -- they want to see "1-3" or "7,8,9" ONLY.
|
||||
be rejected by
|
||||
.Tn ATT
|
||||
or
|
||||
.Bx
|
||||
cron -- they want to see "1-3" or "7,8,9" ONLY.
|
||||
.Pp
|
||||
Ranges can include "steps", so "1-9/2" is the same as "1,3,5,7,9".
|
||||
.Pp
|
||||
Names of months or days of the week can be specified by name.
|
||||
.Pp
|
||||
Environment variables can be set in the crontab. In BSD or ATT, the
|
||||
Environment variables can be set in the crontab. In
|
||||
.Bx
|
||||
or
|
||||
.Tn ATT ,
|
||||
the
|
||||
environment handed to child processes is basically the one from
|
||||
.Pa /etc/rc .
|
||||
.Pp
|
||||
Command output is mailed to the crontab owner (BSD can't do this), can be
|
||||
Command output is mailed to the crontab owner
|
||||
.No ( Bx
|
||||
can't do this), can be
|
||||
mailed to a person other than the crontab owner (SysV can't do this), or the
|
||||
feature can be turned off and no mail will be sent at all (SysV can't do this
|
||||
either).
|
||||
|
||||
@ -75,7 +75,9 @@ hiding all unnecessary symbols.
|
||||
.Nm
|
||||
places specific requirements on package
|
||||
.Pa Makefile Ns s
|
||||
which make it unsuitable for use with non-BSD sources.
|
||||
which make it unsuitable for use with
|
||||
.No non- Ns Bx
|
||||
sources.
|
||||
In particular, the
|
||||
.Pa Makefile
|
||||
must contain the target
|
||||
@ -417,7 +419,9 @@ Some shuffling in the order of
|
||||
libraries may be required, and in some rare cases two libraries may
|
||||
have an unresolvable conflict and thus cannot be crunched together.
|
||||
.Pp
|
||||
Some versions of the BSD build environment do not by default build the
|
||||
Some versions of the
|
||||
.Bx
|
||||
build environment do not by default build the
|
||||
intermediate object file for single-source file programs.
|
||||
The
|
||||
.Dq Li make objs
|
||||
|
||||
@ -157,7 +157,8 @@ appropriate information written to diagnostic output).
|
||||
.Xr newfs_msdos 8
|
||||
.Sh HISTORY
|
||||
.Nm Fdformat
|
||||
has been developed for 386BSD 0.1
|
||||
has been developed for
|
||||
.Bx 386 0.1
|
||||
and upgraded to the new
|
||||
.Xr fdc 4
|
||||
floppy disk driver.
|
||||
|
||||
@ -180,7 +180,8 @@ There are two types of services that
|
||||
can start: standard and TCPMUX.
|
||||
A standard service has a well-known port assigned to it;
|
||||
it may be a service that implements an official Internet standard or is a
|
||||
BSD-specific service.
|
||||
.Bx Ns -specific
|
||||
service.
|
||||
As described in
|
||||
.Tn RFC 1078 ,
|
||||
TCPMUX services are nonstandard services that do not have a
|
||||
|
||||
@ -215,7 +215,9 @@ Documentation from NetWare NDK.
|
||||
.Pp
|
||||
Ncpfs for Linux - written by
|
||||
.An Volker Lendecke Aq lendecke@math.uni\-goettingen.de .
|
||||
He granted me permission to publish parts of his code under BSD-style license,
|
||||
He granted me permission to publish parts of his code under
|
||||
.Bx Ns -style
|
||||
license,
|
||||
.Pp
|
||||
"Interrupt List" from
|
||||
.An Ralf Brown ,
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user