english(4) police.
This commit is contained in:
parent
72aba11981
commit
fec6546e12
@ -83,5 +83,5 @@ function appeared in
|
||||
.Sh BUGS
|
||||
The
|
||||
.Fn devname
|
||||
function returns a poiner to an internal static object;
|
||||
function returns a pointer to an internal static object;
|
||||
thus, subsequent calls will modify the same buffer.
|
||||
|
@ -32,7 +32,7 @@
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm dirname
|
||||
.Nd extract the directory portition of a pathname
|
||||
.Nd extract the directory part of a pathname
|
||||
.Sh SYNOPSIS
|
||||
.In libgen.h
|
||||
.Ft char *
|
||||
|
@ -60,6 +60,6 @@ hardware page size.
|
||||
.Xr sbrk 2
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Fn getpagesze
|
||||
.Fn getpagesize
|
||||
function appeared in
|
||||
.Bx 4.2 .
|
||||
|
@ -168,7 +168,7 @@ The
|
||||
and
|
||||
.Dv SIGTTOU
|
||||
signals (stop signal generated from keyboard or due to terminal I/O
|
||||
from a background proccess) are treated specially.
|
||||
from a background process) are treated specially.
|
||||
When the process is resumed after it has been stopped,
|
||||
.Fn readpassphrase
|
||||
will reprint the prompt and the user may then enter a passphrase.
|
||||
|
@ -46,7 +46,7 @@ function destroys the unnamed semaphore pointed to by
|
||||
After a successful call to
|
||||
.Fn sem_destroy ,
|
||||
.Fa sem
|
||||
is unuseable until re-initialized by another call to
|
||||
is unusable until re-initialized by another call to
|
||||
.Fn sem_init .
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std sem_destroy
|
||||
|
@ -96,7 +96,7 @@ function.
|
||||
The input and output baud rates are found in the termios structure.
|
||||
The unsigned integer
|
||||
.Li speed_t
|
||||
is typdef'd in the include file
|
||||
is typedef'd in the include file
|
||||
.Aq Pa termios.h .
|
||||
The value of the integer corresponds directly to the baud rate being
|
||||
represented, however, the following symbolic values are defined.
|
||||
|
@ -68,7 +68,7 @@ specifies the watch address,
|
||||
specifies the size in bytes of the area to be watched (1, 2, or 4 bytes),
|
||||
and
|
||||
.Fa access
|
||||
specifes the type of watch point:
|
||||
specifies the type of watch point:
|
||||
.Pp
|
||||
.Bd -literal -offset indent -compact
|
||||
DBREG_DR7_EXEC An execution breakpoint.
|
||||
|
@ -66,7 +66,7 @@
|
||||
.Sh DESCRIPTION
|
||||
.\"
|
||||
Building and parsing the Hop-by-Hop and Destination options is
|
||||
complicated due to alignment constranints, padding and
|
||||
complicated due to alignment constraints, padding and
|
||||
ancillary data manipulation.
|
||||
RFC2292 defines a set of functions to help the application.
|
||||
The function prototypes for
|
||||
|
@ -89,7 +89,7 @@ set to the name of the source,
|
||||
.Va cb
|
||||
defined as a function which handles that source, and
|
||||
.Va cb_data
|
||||
is used to pass arbritrary data to the callback function.
|
||||
is used to pass arbitrary data to the callback function.
|
||||
The last entry in
|
||||
.Va dtab
|
||||
should contain
|
||||
@ -161,7 +161,7 @@ list of the type
|
||||
.Va va_list .
|
||||
.Ss Valid source types
|
||||
Whilst there is support for arbitrary sources, the following
|
||||
#defines for commonly implementated sources are available:
|
||||
#defines for commonly implemented sources are available:
|
||||
.Bl -column NS_COMPAT COMPAT -offset indent
|
||||
.It Sy "#define value"
|
||||
.It "NSSRC_FILES ""files"""
|
||||
|
@ -41,7 +41,7 @@
|
||||
permits file systems to export Access Control Lists via the VFS, and
|
||||
provides a library for userland access to and manipulation of these ACLs.
|
||||
Not all file systems provide support for ACLs, and some may require that
|
||||
ACL support be explicitely enabled by the administrator.
|
||||
ACL support be explicitly enabled by the administrator.
|
||||
The library calls include routines to allocate, duplicate, retrieve, set,
|
||||
and validate ACLs associated with file objects.
|
||||
As well as the POSIX.1e routines, there are a number of non-portable
|
||||
|
@ -66,7 +66,7 @@ then the value returned by
|
||||
will be a pointer to type
|
||||
.Vt gid_t .
|
||||
.Pp
|
||||
If the value of the tag type in the ACL enty referred to by
|
||||
If the value of the tag type in the ACL entry referred to by
|
||||
.Fa entry_d
|
||||
is
|
||||
.Dv ACL_UNDEFINED_TAG , ACL_USER_OBJ , ACL_GROUP_OBJ ,
|
||||
|
@ -42,7 +42,7 @@
|
||||
The
|
||||
.Fn acl_get_tag_type
|
||||
function
|
||||
is a POSIX.1e call that returs the tag type for the ACL entry
|
||||
is a POSIX.1e call that returns the tag type for the ACL entry
|
||||
.Fa entry_d .
|
||||
Upon successful completion, the location referred to by the argument
|
||||
.Fa tag_type_p
|
||||
|
@ -101,7 +101,7 @@ Setting MAC labels is not supported
|
||||
by the file referenced by
|
||||
.Fa fd .
|
||||
.It Bq Er EPERM
|
||||
The calling process had insufficient privelege
|
||||
The calling process had insufficient privilege
|
||||
to change the MAC label.
|
||||
.It Bq Er EROFS
|
||||
File system for the object being modified
|
||||
|
@ -298,7 +298,7 @@ struct netbuf {
|
||||
};
|
||||
|
||||
/*
|
||||
* The format of the addres and options arguments of the XTI t_bind call.
|
||||
* The format of the address and options arguments of the XTI t_bind call.
|
||||
* Only provided for compatibility, it should not be used other than
|
||||
* as an argument to svc_tli_create().
|
||||
*/
|
||||
|
@ -132,7 +132,7 @@ appropriately; otherwise the
|
||||
.Fn aio_return
|
||||
system call must be called, and will return -1, and
|
||||
.Fn aio_error
|
||||
must be called to determine the actual calue that would have been
|
||||
must be called to determine the actual value that would have been
|
||||
returned in
|
||||
.Va errno .
|
||||
.Pp
|
||||
|
@ -4,7 +4,7 @@
|
||||
.\" All rights reserved.
|
||||
.\"
|
||||
.\" This software was written by William Studenmund of the
|
||||
.\" Numerical Aerospace Similation Facility, NASA Ames Research Center.
|
||||
.\" Numerical Aerospace Simulation Facility, NASA Ames Research Center.
|
||||
.\"
|
||||
.\" Redistribution and use in source and binary forms, with or without
|
||||
.\" modification, are permitted provided that the following conditions
|
||||
@ -87,7 +87,7 @@ provide the functionality of the
|
||||
.Xr fstat 2
|
||||
and
|
||||
.Xr fstatfs 2
|
||||
calls except that they return information for the file refered to by
|
||||
calls except that they return information for the file referred to by
|
||||
.Fa fhp
|
||||
rather than an open file.
|
||||
.Sh RETURN VALUES
|
||||
@ -105,7 +105,7 @@ In addition to the errors returned by
|
||||
.Xr fstat 2 ,
|
||||
and
|
||||
.Xr fstatfs 2
|
||||
respectivly,
|
||||
respectively,
|
||||
.Fn fhopen ,
|
||||
.Fn fhstat ,
|
||||
and
|
||||
|
@ -121,7 +121,7 @@ For more information see the MAP_NOSYNC section of
|
||||
.It Dv MADV_AUTOSYNC
|
||||
Undoes the effects of MADV_NOSYNC for any future pages dirtied within the
|
||||
address range. The effect on pages already dirtied is indeterminate - they
|
||||
may or may not be reverted. You can guarentee reversion by using the
|
||||
may or may not be reverted. You can guarantee reversion by using the
|
||||
.Xr msync 2
|
||||
or
|
||||
.Xr fsync 2
|
||||
|
@ -150,7 +150,7 @@ struct nfsd_srvargs {
|
||||
struct ucred nsd_cr; /* Cred. uid maps to */
|
||||
int nsd_authlen; /* Length of auth string (ret) */
|
||||
u_char *nsd_authstr; /* Auth string (ret) */
|
||||
int nsd_verflen; /* and the verfier */
|
||||
int nsd_verflen; /* and the verifier */
|
||||
u_char *nsd_verfstr;
|
||||
struct timeval nsd_timestamp; /* timestamp from verifier */
|
||||
u_int32_t nsd_ttl; /* credential ttl (sec) */
|
||||
|
@ -484,7 +484,7 @@ the
|
||||
.Dv sa_handler
|
||||
member of
|
||||
.Dv struct sigaction .
|
||||
In pratice,
|
||||
In practice,
|
||||
.Fx
|
||||
always sends the three arguments of the latter and since the ANSI C
|
||||
prototype is a subset, both will work.
|
||||
@ -517,7 +517,7 @@ handler and the
|
||||
.Dv si_code
|
||||
member of the
|
||||
.Dv info
|
||||
argument to a SA_SIGINFO handler contain a numeric code explaning the
|
||||
argument to a SA_SIGINFO handler contain a numeric code explaining the
|
||||
cause of the signal, usually one of the
|
||||
.Dv SI_...
|
||||
values from
|
||||
|
@ -85,7 +85,7 @@ PF_XTP eXpress Transfer Protocol,
|
||||
PF_COIP Connection-Oriented IP, aka ST II,
|
||||
PF_CNT Computer Network Technology,
|
||||
PF_SIP Simple Internet Protocol,
|
||||
PF_IPX Novell Intenet Packet eXchange protocol,
|
||||
PF_IPX Novell Internet Packet eXchange protocol,
|
||||
PF_RTIP Help Identify RTIP packets,
|
||||
PF_PIP Help Identify PIP packets,
|
||||
PF_ISDN Integrated Services Digital Network,
|
||||
|
@ -78,7 +78,7 @@ The
|
||||
system call
|
||||
can normally be used just like
|
||||
.Xr fork 2 .
|
||||
It does not work, however, to return while running in the childs context
|
||||
It does not work, however, to return while running in the child's context
|
||||
from the procedure that called
|
||||
.Fn vfork
|
||||
since the eventual return from
|
||||
|
@ -44,7 +44,7 @@ Value returned as
|
||||
.Fa dst
|
||||
is supposed to be used in conjunction with
|
||||
.Fn pthread_attr_get*
|
||||
functions to retrive individual values from
|
||||
functions to retrieve individual values from
|
||||
.Vt pthread_attr_t
|
||||
structure.
|
||||
Parameter
|
||||
|
@ -87,7 +87,7 @@ functions copy the value of the attribute that corresponds to each function name
|
||||
to the location pointed to by the second function parameter.
|
||||
.Sh RETURN VALUES
|
||||
If successful, these functions return 0.
|
||||
Otherwise, an error number is returned to indicacte the error.
|
||||
Otherwise, an error number is returned to indicate the error.
|
||||
.Sh ERRORS
|
||||
.Fn pthread_mutexattr_init
|
||||
will fail if:
|
||||
|
@ -46,7 +46,7 @@ function destroys the unnamed semaphore pointed to by
|
||||
After a successful call to
|
||||
.Fn sem_destroy ,
|
||||
.Fa sem
|
||||
is unuseable until re-initialized by another call to
|
||||
is unusable until re-initialized by another call to
|
||||
.Fn sem_init .
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std sem_destroy
|
||||
|
@ -233,17 +233,17 @@ typedef enum {
|
||||
CAM_MSG_BUF_PHYS = 0x00080000,/* Message buffer ptr is physical*/
|
||||
CAM_SNS_BUF_PHYS = 0x00100000,/* Autosense data ptr is physical*/
|
||||
CAM_DATA_PHYS = 0x00200000,/* SG/Buffer data ptrs are phys. */
|
||||
CAM_CDB_PHYS = 0x00400000,/* CDB poiner is physical */
|
||||
CAM_CDB_PHYS = 0x00400000,/* CDB pointer is physical */
|
||||
CAM_ENG_SGLIST = 0x00800000,/* SG list is for the HBA engine */
|
||||
|
||||
/* Phase cognizant mode flags */
|
||||
CAM_DIS_AUTOSRP = 0x01000000,/* Diable autosave/restore ptrs */
|
||||
CAM_DIS_AUTODISC = 0x02000000,/* Disable auto disconnect */
|
||||
CAM_TGT_CCB_AVAIL = 0x04000000,/* Target CCB available */
|
||||
CAM_TGT_PHASE_MODE = 0x08000000,/* The SIM runs in phase mode */
|
||||
CAM_MSGB_VALID = 0x20000000,/* Message buffer valid */
|
||||
CAM_STATUS_VALID = 0x40000000,/* Status buffer valid */
|
||||
CAM_DATAB_VALID = 0x80000000,/* Data buffer valid */
|
||||
CAM_DIS_AUTOSRP = 0x01000000,/* Disable autosave/restore ptrs */
|
||||
CAM_DIS_AUTODISC = 0x02000000,/* Disable auto disconnect */
|
||||
CAM_TGT_CCB_AVAIL = 0x04000000,/* Target CCB available */
|
||||
CAM_TGT_PHASE_MODE = 0x08000000,/* The SIM runs in phase mode */
|
||||
CAM_MSGB_VALID = 0x20000000,/* Message buffer valid */
|
||||
CAM_STATUS_VALID = 0x40000000,/* Status buffer valid */
|
||||
CAM_DATAB_VALID = 0x80000000,/* Data buffer valid */
|
||||
|
||||
/* Host target Mode flags */
|
||||
CAM_TERM_IO = 0x20000000,/* Terminate I/O Message sup. */
|
||||
@ -427,7 +427,7 @@ used as the seek value.
|
||||
operates like
|
||||
.Fn csio_decode
|
||||
except that instead of placing the decoded contents of the buffer in
|
||||
varardic arguments, the decoded buffer contents are returned to the user
|
||||
variadic arguments, the decoded buffer contents are returned to the user
|
||||
via the
|
||||
.Fn arg_put
|
||||
function that is passed in.
|
||||
|
@ -180,7 +180,7 @@ MD5
|
||||
Blowfish
|
||||
.El
|
||||
.Pp
|
||||
Other crypt formats may be easilly added. An example salt would be:
|
||||
Other crypt formats may be easily added. An example salt would be:
|
||||
.Bl -tag -offset indent
|
||||
.It Cm "$3$thesalt$rest"
|
||||
.El
|
||||
|
@ -105,7 +105,7 @@ struct devinfo_dev {
|
||||
char *dd_location; /* Where bus thinks dev at */
|
||||
uint32_t dd_devflags; /* API flags */
|
||||
uint16_t dd_flags; /* internal dev flags */
|
||||
device_state_t dd_state; /* attacement state of dev */
|
||||
device_state_t dd_state; /* attachment state of dev */
|
||||
};
|
||||
|
||||
struct devinfo_rman {
|
||||
|
@ -376,7 +376,7 @@ Cut the entire line and save in cut buffer.
|
||||
Cut area between mark and cursor and save in cut buffer.
|
||||
.It Ic em-copy-region
|
||||
Copy area between mark and cursor to cut buffer.
|
||||
.It Ic em-gosmacs-traspose
|
||||
.It Ic em-gosmacs-transpose
|
||||
Exchange the two characters before the cursor.
|
||||
.It Ic em-next-word
|
||||
Move next to end of current word.
|
||||
|
@ -42,7 +42,7 @@ To avoid version and autoconfiguration issues, the library has been
|
||||
renamed to
|
||||
.Nm
|
||||
rather than retain the original eXpat library and include file names
|
||||
to prevent confusion and autoconfiguation issues for 3rd party
|
||||
to prevent confusion and autoconfiguration issues for 3rd party
|
||||
software.
|
||||
.Sh SEE ALSO
|
||||
For full documentation, please see the eXpat webpage at
|
||||
|
@ -512,10 +512,10 @@ This variable is used if and only if connected to an HTTP proxy, and
|
||||
is ignored if a user and/or a password were specified in the proxy
|
||||
URL.
|
||||
.It Ev HTTP_REFERER
|
||||
Specifies the referer URL to use for HTTP requests.
|
||||
Specifies the referrer URL to use for HTTP requests.
|
||||
If set to
|
||||
.Dq auto ,
|
||||
the document URL will be used as referer URL.
|
||||
the document URL will be used as referrer URL.
|
||||
.It Ev HTTP_USER_AGENT
|
||||
Specifies the User-Agent string to use for HTTP requests.
|
||||
This can be useful when working with HTTP origin or proxy servers that
|
||||
|
@ -111,7 +111,7 @@ more about what happened if you're familiar with FTP error codes).
|
||||
returns a human readable version of the supplied server failure code.
|
||||
.Pp
|
||||
.Fn ftpGet
|
||||
attempts to retreive the file named by the
|
||||
attempts to retrieve the file named by the
|
||||
.Fa file
|
||||
argument (which is assumed to be relative to the FTP server's current directory,
|
||||
see
|
||||
@ -169,7 +169,7 @@ to boolean value
|
||||
.Fa status .
|
||||
.Pp
|
||||
.Fn ftpGetURL
|
||||
attempts to retreive the file named by the supplied
|
||||
attempts to retrieve the file named by the supplied
|
||||
.Fa URL
|
||||
and can be considered equivalent to the combined
|
||||
.Fn ftpLogin ,
|
||||
|
@ -178,7 +178,7 @@ Both
|
||||
.Ar src
|
||||
and
|
||||
.Ar dst
|
||||
can be omited.
|
||||
can be omitted.
|
||||
.Pp
|
||||
.Ar level
|
||||
must be set to one of the following:
|
||||
|
@ -232,7 +232,7 @@ in
|
||||
.Tn ASCII
|
||||
format; however, this results in additional messages being
|
||||
sent which may interfere with debugging. At even higher levels,
|
||||
even these additional messagages will be displayed, etc.
|
||||
even these additional messages will be displayed, etc.
|
||||
.Pp
|
||||
Note that
|
||||
.Xr select 2
|
||||
|
@ -83,7 +83,7 @@ authentication attempt was declined.
|
||||
.It Cm no_anon
|
||||
Disallow anonymous access.
|
||||
.It Cm ignore
|
||||
Ingnore the password supplied,
|
||||
Ignore the password supplied,
|
||||
and do not use its constituent parts
|
||||
(username and hostname)
|
||||
as
|
||||
|
@ -84,7 +84,7 @@ debugging information at
|
||||
level.
|
||||
.It Cm auth_as_self
|
||||
This option will require the user
|
||||
to authenticate themself as the user
|
||||
to authenticate himself as the user
|
||||
given by
|
||||
.Xr getlogin 2 ,
|
||||
not as the account they are attempting to access.
|
||||
|
@ -105,7 +105,7 @@ except that if the previously obtained password fails,
|
||||
the user is prompted for another password.
|
||||
.It Cm auth_as_self
|
||||
This option will require the user
|
||||
to authenticate themself as the user
|
||||
to authenticate himself as the user
|
||||
given by
|
||||
.Xr getlogin 2 ,
|
||||
not as the account they are attempting to access.
|
||||
|
@ -87,7 +87,7 @@ functions copy the value of the attribute that corresponds to each function name
|
||||
to the location pointed to by the second function parameter.
|
||||
.Sh RETURN VALUES
|
||||
If successful, these functions return 0.
|
||||
Otherwise, an error number is returned to indicacte the error.
|
||||
Otherwise, an error number is returned to indicate the error.
|
||||
.Sh ERRORS
|
||||
.Fn pthread_mutexattr_init
|
||||
will fail if:
|
||||
|
@ -46,7 +46,7 @@ function destroys the unnamed semaphore pointed to by
|
||||
After a successful call to
|
||||
.Fn sem_destroy ,
|
||||
.Fa sem
|
||||
is unuseable until re-initialized by another call to
|
||||
is unusable until re-initialized by another call to
|
||||
.Fn sem_init .
|
||||
.Sh RETURN VALUES
|
||||
.Rv -std sem_destroy
|
||||
|
@ -42,7 +42,7 @@
|
||||
.Sh DESCRIPTION
|
||||
The function
|
||||
.Fn auth_getval
|
||||
returns the value assocated with the field called
|
||||
returns the value associated with the field called
|
||||
.Fa name
|
||||
or NULL if no such field is found or the auth file cannot be opened.
|
||||
.Sh SEE ALSO
|
||||
|
@ -351,7 +351,7 @@ The suffix used determines the units, and multiple values and
|
||||
units may be used in combination (e.g. 1m500k = 1.5 megabytes).
|
||||
A value with no suffix is interpreted as bytes, B as 512-byte
|
||||
blocks, K as kilobytes, M as megabytes, G as gigabytes and T as
|
||||
terrabytes.
|
||||
terabytes.
|
||||
Case is ignored.
|
||||
The error value is returned if there is a login capabilities database
|
||||
error, if an invalid suffix is used, or if a numeric value cannot be
|
||||
|
@ -40,7 +40,7 @@
|
||||
.Nm hypotf ,
|
||||
.Nm cabs ,
|
||||
.Nm cabsf
|
||||
.Nd euclidean distance and complex absolute value functions
|
||||
.Nd Euclidean distance and complex absolute value functions
|
||||
.Sh LIBRARY
|
||||
.Lb libm
|
||||
.Sh SYNOPSIS
|
||||
|
@ -467,7 +467,7 @@ comments.
|
||||
Defining a virtual host for the primary IP address or hostname
|
||||
changes the default for ftp logins to that address.
|
||||
The 'user', 'statfile', 'welcome' and 'motd' fields may be left
|
||||
blank, or a single hypen '-' used to indicate that the default
|
||||
blank, or a single hyphen '-' used to indicate that the default
|
||||
value is to be used.
|
||||
.Pp
|
||||
As with any anonymous login configuration, due care must be given
|
||||
|
@ -427,7 +427,7 @@ Note that the
|
||||
.Ql \ep
|
||||
sequence is only valid for send strings and causes a half-second
|
||||
pause between sending the previous and next characters.
|
||||
Hexidecimal values are, at most, 2 hex digits long, and octal
|
||||
Hexadecimal values are, at most, 2 hex digits long, and octal
|
||||
values are a maximum of 3 octal digits.
|
||||
.Pp
|
||||
The
|
||||
|
@ -105,7 +105,7 @@ Note that all files created by
|
||||
are owner readable and writable only for security reasons. Since the
|
||||
.Tn NIS
|
||||
maps and the directory in which they reside are normally owned by
|
||||
root, this prevents non-privleged users from making unauthorized
|
||||
root, this prevents non-privileged users from making unauthorized
|
||||
modifications.
|
||||
.Pp
|
||||
In order to maintain consistency across all
|
||||
|
@ -858,7 +858,7 @@ the whole ATMARP table will be displayed.
|
||||
If a host name or IP address is specified, only information about the
|
||||
given host is displayed.
|
||||
.PP
|
||||
This command dislays both information that has been learned dynamically
|
||||
This command displays both information that has been learned dynamically
|
||||
(through one form or another of ATMARP and via SCSP) and information
|
||||
which has been configured by the user (through the \fIadd ARP\fP
|
||||
subcommand).
|
||||
|
@ -47,7 +47,7 @@ Enable debugging messages and run in the foreground instead of
|
||||
becoming a daemon.
|
||||
.El
|
||||
.Sh IMPLEMENTATION NOTES
|
||||
.Nm
|
||||
.Nm
|
||||
is a system daemon that runs in the background all the time.
|
||||
Whenever a device is added to or removed from the device tree,
|
||||
.Nm
|
||||
@ -66,7 +66,7 @@ to use a table to locate and load via
|
||||
.Xr kldload 8
|
||||
the proper driver for an unrecognized device that is added to the system.
|
||||
.Pp
|
||||
.Nm
|
||||
.Nm
|
||||
hooks into the
|
||||
.Xr devctl 4
|
||||
device driver.
|
||||
@ -74,8 +74,8 @@ This device driver has hooks into the device configuration system.
|
||||
When nodes are added or deleted from the tree, this device will
|
||||
deliver information about the event to
|
||||
.Nm .
|
||||
Once
|
||||
.Nm
|
||||
Once
|
||||
.Nm
|
||||
has parsed the message, it will search its action list for that kind
|
||||
of event and perform the action with the highest matching value.
|
||||
For most mundane uses, the default handlers are adequate.
|
||||
@ -84,8 +84,8 @@ aspect of what happens.
|
||||
.Pp
|
||||
.Nm
|
||||
reads /etc/devd.conf and uses that file to drive the rest of the process.
|
||||
While the format of this file is described in
|
||||
.Xr devd.conf 5
|
||||
While the format of this file is described in
|
||||
.Xr devd.conf 5
|
||||
some basics are covered here.
|
||||
In the options section, one can define multiple directories to search
|
||||
for config files.
|
||||
@ -102,4 +102,4 @@ config files.
|
||||
.An M. Warner Losh
|
||||
.Sh BUGS
|
||||
devd currently always runs "/etc/devd-generic $device $startstop" for
|
||||
all device events, reguardless of what the config file says to do.
|
||||
all device events, regardless of what the config file says to do.
|
||||
|
@ -50,7 +50,7 @@
|
||||
.Sh OVERVIEW
|
||||
.Ss General Syntax
|
||||
A
|
||||
.Xr devd 8
|
||||
.Xr devd 8
|
||||
configuration consists of two general features, statements
|
||||
and comments.
|
||||
All statements end with a semicolon.
|
||||
|
@ -71,7 +71,7 @@ after the system has completed going multiuser, with the
|
||||
flag to do checking on all the file systems
|
||||
that can do background checking.
|
||||
Unlike the foreground checking,
|
||||
the background checking is started asynchonously
|
||||
the background checking is started asynchronously
|
||||
so that other system activity can proceed
|
||||
even on the file systems that are being checked.
|
||||
.Pp
|
||||
@ -129,7 +129,7 @@ Enter preen mode.
|
||||
In preen mode, only a restricted class of innocuous
|
||||
file system inconsistencies will be corrected.
|
||||
If unexpected inconsistencies caused by hardware or
|
||||
software failures are encounted, the check program
|
||||
software failures are encountered, the check program
|
||||
will exit with a failure.
|
||||
See the manual pages for the individual check programs
|
||||
for a list of the sorts of failures that they correct
|
||||
|
@ -389,7 +389,7 @@ So
|
||||
.Ar out
|
||||
is required (and
|
||||
.Ar in
|
||||
invalid) whenver
|
||||
invalid) whenever
|
||||
.Ar xmit
|
||||
is used.
|
||||
Specifying
|
||||
|
@ -143,7 +143,7 @@ do not run
|
||||
.Xr mdconfig 8
|
||||
to try to detach the unit before attaching it.
|
||||
.It Fl d Ar rotdelay
|
||||
Specify the mininum time in milliseconds required to initiate another
|
||||
Specify the minimum time in milliseconds required to initiate another
|
||||
disk transfer on the same cylinder.
|
||||
Modern disks with read/write-behind achieve higher performance without
|
||||
this feature,
|
||||
|
@ -82,7 +82,7 @@ To mount an hpfs volume located in /dev/wd1s1:
|
||||
.Ed
|
||||
.Sh WRITING
|
||||
There is limited writing ability and it is not well-tested.
|
||||
It is strongly recomended to mount readonly!
|
||||
It is strongly recommended to mount readonly!
|
||||
.Sh SEE ALSO
|
||||
.Xr mount 2 ,
|
||||
.Xr unmount 2 ,
|
||||
@ -91,7 +91,7 @@ It is strongly recomended to mount readonly!
|
||||
.Sh HISTORY
|
||||
The
|
||||
.Nm
|
||||
utility first appered in
|
||||
utility first appeared in
|
||||
.Fx 3.0 .
|
||||
.Sh AUTHORS
|
||||
HPFS kernel implementation,
|
||||
|
@ -242,7 +242,7 @@ is not one of this machine's interface addresses, an error is
|
||||
returned and nothing is sent.
|
||||
.It Fl t Ar timeout
|
||||
Specify a timeout, in seconds, before ping exits regardless of how
|
||||
many packets have been recieved.
|
||||
many packets have been received.
|
||||
.It Fl T Ar ttl
|
||||
Set the IP Time To Live for multicasted packets.
|
||||
This flag only applies if the ping destination is a multicast address.
|
||||
|
@ -38,29 +38,29 @@
|
||||
.\"
|
||||
.\" Copyright (c) 1995 Carnegie-Mellon University.
|
||||
.\" All rights reserved.
|
||||
.\"
|
||||
.\"
|
||||
.\" Author: Mark Holland
|
||||
.\"
|
||||
.\"
|
||||
.\" Permission to use, copy, modify and distribute this software and
|
||||
.\" its documentation is hereby granted, provided that both the copyright
|
||||
.\" notice and this permission notice appear in all copies of the
|
||||
.\" software, derivative works or modified versions, and any portions
|
||||
.\" thereof, and that both notices appear in supporting documentation.
|
||||
.\"
|
||||
.\"
|
||||
.\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
|
||||
.\" CONDITION. CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND
|
||||
.\" FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
|
||||
.\"
|
||||
.\"
|
||||
.\" Carnegie Mellon requests users of this software to return to
|
||||
.\"
|
||||
.\"
|
||||
.\" Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU
|
||||
.\" School of Computer Science
|
||||
.\" Carnegie Mellon University
|
||||
.\" Pittsburgh PA 15213-3890
|
||||
.\"
|
||||
.\"
|
||||
.\" any improvements or extensions that they make and grant Carnegie the
|
||||
.\" rights to redistribute these changes.
|
||||
.\"
|
||||
.\"
|
||||
.Dd November 6, 1998
|
||||
.Dt RAIDCTL 8
|
||||
.Os
|
||||
@ -69,62 +69,62 @@
|
||||
.Nd configuration utility for the RAIDframe disk driver
|
||||
.Sh SYNOPSIS
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl a Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Fl A Op yes | no | root
|
||||
.Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Fl B Ar dev
|
||||
.Op Fl v
|
||||
.Fl B Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl c Ar config_file
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl C Ar config_file
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl f Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl F Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl g Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl i Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl I Ar serial_number Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl p Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl P Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl r Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl R Ar component Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Fl s Ar dev
|
||||
.Op Fl v
|
||||
.Fl s Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl S Ar dev
|
||||
.Nm
|
||||
.Op Fl v
|
||||
.Op Fl v
|
||||
.Fl u Ar dev
|
||||
.Sh DESCRIPTION
|
||||
.Nm
|
||||
is the user-land control program for
|
||||
.Xr raid 4 ,
|
||||
the RAIDframe disk device.
|
||||
the RAIDframe disk device.
|
||||
.Nm
|
||||
is primarily used to dynamically configure and unconfigure RAIDframe disk
|
||||
devices. For more information about the RAIDframe disk device, see
|
||||
@ -133,18 +133,18 @@ devices. For more information about the RAIDframe disk device, see
|
||||
This document assumes the reader has at least rudimentary knowledge of
|
||||
RAID and RAID concepts.
|
||||
.Pp
|
||||
The command-line options for
|
||||
The command-line options for
|
||||
.Nm
|
||||
are as follows:
|
||||
.Bl -tag -width indent
|
||||
.It Fl a Ar component Ar dev
|
||||
Add
|
||||
Add
|
||||
.Ar component
|
||||
as a hot spare for the device
|
||||
as a hot spare for the device
|
||||
.Ar dev .
|
||||
.It Fl A Ic yes Ar dev
|
||||
Make the RAID set auto-configurable. The RAID set will be
|
||||
automatically configured at boot
|
||||
automatically configured at boot
|
||||
.Ar before
|
||||
the root file system is
|
||||
mounted. Note that all components of the set must be of type RAID in the
|
||||
@ -154,20 +154,20 @@ Turn off auto-configuration for the RAID set.
|
||||
.It Fl A Ic root Ar dev
|
||||
Make the RAID set auto-configurable, and also mark the set as being
|
||||
eligible to be the root partition. A RAID set configured this way
|
||||
will
|
||||
will
|
||||
.Ar override
|
||||
the use of the boot disk as the root device. All components of the
|
||||
set must be of type RAID in the disklabel. Note that the kernel being
|
||||
booted must currently reside on a non-RAID set.
|
||||
.It Fl B Ar dev
|
||||
Initiate a copyback of reconstructed data from a spare disk to
|
||||
its original disk. This is performed after a component has failed,
|
||||
Initiate a copyback of reconstructed data from a spare disk to
|
||||
its original disk. This is performed after a component has failed,
|
||||
and the failed drive has been reconstructed onto a spare drive.
|
||||
.It Fl c Ar config_file
|
||||
Configure a RAIDframe device
|
||||
Configure a RAIDframe device
|
||||
according to the configuration given in
|
||||
.Ar config_file .
|
||||
A description of the contents of
|
||||
A description of the contents of
|
||||
.Ar config_file
|
||||
is given later.
|
||||
.It Fl C Ar config_file
|
||||
@ -176,12 +176,12 @@ As for
|
||||
but forces the configuration to take place. This is required the
|
||||
first time a RAID set is configured.
|
||||
.It Fl f Ar component Ar dev
|
||||
This marks the specified
|
||||
This marks the specified
|
||||
.Ar component
|
||||
as having failed, but does not initiate a reconstruction of that
|
||||
component.
|
||||
component.
|
||||
.It Fl F Ar component Ar dev
|
||||
Fails the specified
|
||||
Fails the specified
|
||||
.Ar component
|
||||
of the device, and immediately begin a reconstruction of the failed
|
||||
disk onto an available hot spare. This is one of the mechanisms used to start
|
||||
@ -190,19 +190,19 @@ the reconstruction process if a component does have a hardware failure.
|
||||
Get the component label for the specified component.
|
||||
.It Fl i Ar dev
|
||||
Initialize the RAID device. In particular, (re-write) the parity on
|
||||
the selected device. This
|
||||
the selected device. This
|
||||
.Ar MUST
|
||||
be done for
|
||||
.Ar all
|
||||
be done for
|
||||
.Ar all
|
||||
RAID sets before the RAID device is labeled and before
|
||||
file systems are created on the RAID device.
|
||||
.It Fl I Ar serial_number Ar dev
|
||||
Initialize the component labels on each component of the device.
|
||||
.Ar serial_number
|
||||
Initialize the component labels on each component of the device.
|
||||
.Ar serial_number
|
||||
is used as one of the keys in determining whether a
|
||||
particular set of components belong to the same RAID set. While not
|
||||
strictly enforced, different serial numbers should be used for
|
||||
different RAID sets. This step
|
||||
different RAID sets. This step
|
||||
.Ar MUST
|
||||
be performed when a new RAID set is created.
|
||||
.It Fl p Ar dev
|
||||
@ -215,34 +215,34 @@ This is normally used after a system crash (and before a
|
||||
.Xr fsck 8 )
|
||||
to ensure the integrity of the parity.
|
||||
.It Fl r Ar component Ar dev
|
||||
Remove the spare disk specified by
|
||||
.Ar component
|
||||
Remove the spare disk specified by
|
||||
.Ar component
|
||||
from the set of available spare components.
|
||||
.It Fl R Ar component Ar dev
|
||||
Fails the specified
|
||||
.Ar component ,
|
||||
if necessary, and immediately begins a reconstruction back to
|
||||
Fails the specified
|
||||
.Ar component ,
|
||||
if necessary, and immediately begins a reconstruction back to
|
||||
.Ar component .
|
||||
This is useful for reconstructing back onto a component after
|
||||
it has been replaced following a failure.
|
||||
.It Fl s Ar dev
|
||||
Display the status of the RAIDframe device for each of the components
|
||||
and spares.
|
||||
and spares.
|
||||
.It Fl S Ar dev
|
||||
Check the status of parity re-writing, component reconstruction, and
|
||||
component copyback. The output indicates the amount of progress
|
||||
achieved in each of these areas.
|
||||
.It Fl u Ar dev
|
||||
Unconfigure the RAIDframe device.
|
||||
.It Fl v
|
||||
.It Fl v
|
||||
Be more verbose. For operations such as reconstructions, parity
|
||||
re-writing, and copybacks, provide a progress indicator.
|
||||
.El
|
||||
.Pp
|
||||
The device used by
|
||||
The device used by
|
||||
.Nm
|
||||
is specified by
|
||||
.Ar dev .
|
||||
is specified by
|
||||
.Ar dev .
|
||||
.Ar dev
|
||||
may be either the full name of the device, e.g. /dev/rraid0d,
|
||||
for the i386 architecture, and /dev/rraid0c
|
||||
@ -250,31 +250,31 @@ for all others, or just simply raid0 (for /dev/rraid0d).
|
||||
.Pp
|
||||
The format of the configuration file is complex, and
|
||||
only an abbreviated treatment is given here. In the configuration
|
||||
files, a
|
||||
files, a
|
||||
.Sq #
|
||||
indicates the beginning of a comment.
|
||||
.Pp
|
||||
There are 4 required sections of a configuration file, and 2
|
||||
optional sections. Each section begins with a
|
||||
.Sq START ,
|
||||
optional sections. Each section begins with a
|
||||
.Sq START ,
|
||||
followed by
|
||||
the section name, and the configuration parameters associated with that
|
||||
section. The first section is the
|
||||
section. The first section is the
|
||||
.Sq array
|
||||
section, and it specifies
|
||||
the number of rows, columns, and spare disks in the RAID set. For
|
||||
example:
|
||||
example:
|
||||
.Bd -unfilled -offset indent
|
||||
START array
|
||||
1 3 0
|
||||
.Ed
|
||||
.Pp
|
||||
indicates an array with 1 row, 3 columns, and 0 spare disks. Note
|
||||
that although multi-dimensional arrays may be specified, they are
|
||||
that although multi-dimensional arrays may be specified, they are
|
||||
.Ar NOT
|
||||
supported in the driver.
|
||||
.Pp
|
||||
The second section, the
|
||||
The second section, the
|
||||
.Sq disks
|
||||
section, specifies the actual
|
||||
components of the device. For example:
|
||||
@ -287,42 +287,42 @@ START disks
|
||||
.Pp
|
||||
specifies the three component disks to be used in the RAID device. If
|
||||
any of the specified drives cannot be found when the RAID device is
|
||||
configured, then they will be marked as
|
||||
.Sq failed ,
|
||||
configured, then they will be marked as
|
||||
.Sq failed ,
|
||||
and the system will
|
||||
operate in degraded mode. Note that it is
|
||||
operate in degraded mode. Note that it is
|
||||
.Ar imperative
|
||||
that the order of the components in the configuration file does not
|
||||
change between configurations of a RAID device. Changing the order
|
||||
of the components will result in data loss if the set is configured
|
||||
with the
|
||||
with the
|
||||
.Fl C
|
||||
option. In normal circumstances, the RAID set will not configure if
|
||||
only
|
||||
.Fl c
|
||||
is specified, and the components are out-of-order.
|
||||
is specified, and the components are out-of-order.
|
||||
.Pp
|
||||
The next section, which is the
|
||||
The next section, which is the
|
||||
.Sq spare
|
||||
section, is optional, and, if
|
||||
present, specifies the devices to be used as
|
||||
present, specifies the devices to be used as
|
||||
.Sq hot spares
|
||||
-- devices
|
||||
which are on-line, but are not actively used by the RAID driver unless
|
||||
one of the main components fail. A simple
|
||||
one of the main components fail. A simple
|
||||
.Sq spare
|
||||
section might be:
|
||||
.Bd -unfilled -offset indent
|
||||
START spare
|
||||
START spare
|
||||
/dev/da3s1e
|
||||
.Ed
|
||||
.Pp
|
||||
for a configuration with a single spare component. If no spare drives
|
||||
are to be used in the configuration, then the
|
||||
are to be used in the configuration, then the
|
||||
.Sq spare
|
||||
section may be omitted.
|
||||
.Pp
|
||||
The next section is the
|
||||
The next section is the
|
||||
.Sq layout
|
||||
section. This section describes the
|
||||
general layout parameters for the RAID device, and provides such
|
||||
@ -345,9 +345,9 @@ While certain values above 1 are permitted, a discussion of valid
|
||||
values and the consequences of using anything other than 1 are outside
|
||||
the scope of this document. The last value in this section (5 in this
|
||||
example) indicates the parity configuration desired. Valid entries
|
||||
include:
|
||||
include:
|
||||
.Bl -tag -width inde
|
||||
.It 0
|
||||
.It 0
|
||||
RAID level 0. No parity, only simple striping.
|
||||
.It 1
|
||||
RAID level 1. Mirroring. The parity is the mirror.
|
||||
@ -360,12 +360,12 @@ all components.
|
||||
.El
|
||||
.Pp
|
||||
There are other valid entries here, including those for Even-Odd
|
||||
parity, RAID level 5 with rotated sparing, Chained declustering,
|
||||
parity, RAID level 5 with rotated sparing, Chained declustering,
|
||||
and Interleaved declustering, but as of this writing the code for
|
||||
those parity operations has not been tested with
|
||||
those parity operations has not been tested with
|
||||
.Fx .
|
||||
.Pp
|
||||
The next required section is the
|
||||
The next required section is the
|
||||
.Sq queue
|
||||
section. This is most often
|
||||
specified as:
|
||||
@ -375,15 +375,15 @@ fifo 100
|
||||
.Ed
|
||||
.Pp
|
||||
where the queuing method is specified as fifo (first-in, first-out),
|
||||
and the size of the per-component queue is limited to 100 requests.
|
||||
and the size of the per-component queue is limited to 100 requests.
|
||||
Other queuing methods may also be specified, but a discussion of them
|
||||
is beyond the scope of this document.
|
||||
.Pp
|
||||
The final section, the
|
||||
The final section, the
|
||||
.Sq debug
|
||||
section, is optional. For more details
|
||||
on this the reader is referred to the RAIDframe documentation
|
||||
discussed in the
|
||||
discussed in the
|
||||
.Sx HISTORY
|
||||
section.
|
||||
|
||||
@ -400,17 +400,17 @@ with the use of
|
||||
and that they understand how the component reconstruction process
|
||||
works. The examples in this section will focus on configuring a
|
||||
number of different RAID sets of varying degrees of redundancy.
|
||||
By working through these examples, administrators should be able to
|
||||
By working through these examples, administrators should be able to
|
||||
develop a good feel for how to configure a RAID set, and how to
|
||||
initiate reconstruction of failed components.
|
||||
.Pp
|
||||
In the following examples
|
||||
.Sq raid0
|
||||
will be used to denote the RAID device. Depending on the
|
||||
architecture,
|
||||
.Sq /dev/rraid0c
|
||||
or
|
||||
.Sq /dev/rraid0d
|
||||
architecture,
|
||||
.Sq /dev/rraid0c
|
||||
or
|
||||
.Sq /dev/rraid0d
|
||||
may be used in place of
|
||||
.Sq raid0 .
|
||||
.Pp
|
||||
@ -426,9 +426,9 @@ f: 1800000 200495 RAID # (Cyl. 405*- 4041*)
|
||||
.Ed
|
||||
.Pp
|
||||
While
|
||||
.Dv FS_BSDFFS
|
||||
.Dv FS_BSDFFS
|
||||
will also work as the component type, the type
|
||||
.Dv FS_RAID
|
||||
.Dv FS_RAID
|
||||
is preferred for RAIDframe use, as it is required for features such as
|
||||
auto-configuration. As part of the initial configuration of each RAID
|
||||
set, each component will be given a
|
||||
@ -447,7 +447,7 @@ required for the auto-detection and auto-configuration of RAID sets at
|
||||
boot time. For a component label to be considered valid, that
|
||||
particular component label must be in agreement with the other
|
||||
component labels in the set. For example, the serial number,
|
||||
.Sq modification counter ,
|
||||
.Sq modification counter ,
|
||||
number of rows and number of columns must all
|
||||
be in agreement. If any of these are different, then the component is
|
||||
not considered to be part of the set. See
|
||||
@ -455,10 +455,10 @@ not considered to be part of the set. See
|
||||
for more information about component labels.
|
||||
.Pp
|
||||
Once the components have been identified, and the disks have
|
||||
appropriate labels,
|
||||
appropriate labels,
|
||||
.Nm
|
||||
is then used to configure the
|
||||
.Xr raid 4
|
||||
.Xr raid 4
|
||||
device. To configure the device, a configuration
|
||||
file which looks something like:
|
||||
.Bd -unfilled -offset indent
|
||||
@ -538,16 +538,16 @@ the RAID 5 case above. Note as well that RAID 1 sets are currently
|
||||
limited to only 2 components. At present, n-way mirroring is not
|
||||
possible.
|
||||
.Pp
|
||||
The first time a RAID set is configured, the
|
||||
The first time a RAID set is configured, the
|
||||
.Fl C
|
||||
option must be used:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -C raid0.conf
|
||||
.Ed
|
||||
.Pp
|
||||
where
|
||||
where
|
||||
.Sq raid0.conf
|
||||
is the name of the RAID configuration file. The
|
||||
is the name of the RAID configuration file. The
|
||||
.Fl C
|
||||
forces the configuration to succeed, even if any of the component
|
||||
labels are incorrect. The
|
||||
@ -556,36 +556,36 @@ option should not be used lightly in
|
||||
situations other than initial configurations, as if
|
||||
the system is refusing to configure a RAID set, there is probably a
|
||||
very good reason for it. After the initial configuration is done (and
|
||||
appropriate component labels are added with the
|
||||
appropriate component labels are added with the
|
||||
.Fl I
|
||||
option) then raid0 can be configured normally with:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -c raid0.conf
|
||||
.Ed
|
||||
.Pp
|
||||
When the RAID set is configured for the first time, it is
|
||||
When the RAID set is configured for the first time, it is
|
||||
necessary to initialize the component labels, and to initialize the
|
||||
parity on the RAID set. Initializing the component labels is done with:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -I 112341 raid0
|
||||
.Ed
|
||||
.Pp
|
||||
where
|
||||
where
|
||||
.Sq 112341
|
||||
is a user-specified serial number for the RAID set. This
|
||||
initialization step is
|
||||
.Ar required
|
||||
initialization step is
|
||||
.Ar required
|
||||
for all RAID sets. As well, using different
|
||||
serial numbers between RAID sets is
|
||||
.Ar strongly encouraged ,
|
||||
serial numbers between RAID sets is
|
||||
.Ar strongly encouraged ,
|
||||
as using the same serial number for all RAID sets will only serve to
|
||||
decrease the usefulness of the component label checking.
|
||||
.Pp
|
||||
Initializing the RAID set is done via the
|
||||
.Fl i
|
||||
option. This initialization
|
||||
option. This initialization
|
||||
.Ar MUST
|
||||
be done for
|
||||
be done for
|
||||
.Ar all
|
||||
RAID sets, since among other things it verifies that the parity (if
|
||||
any) on the RAID set is correct. Since this initialization may be
|
||||
@ -605,7 +605,7 @@ Parity Re-write status:
|
||||
10% |**** | ETA: 06:03 /
|
||||
.Ed
|
||||
.Pp
|
||||
The output provides a
|
||||
The output provides a
|
||||
.Sq Percent Complete
|
||||
in both a numeric and graphical format, as well as an estimated time
|
||||
to completion of the operation.
|
||||
@ -616,7 +616,7 @@ part of RAID, it is critical that the parity is correct
|
||||
as much as possible. If the parity is not correct, then there is no
|
||||
guarantee that data will not be lost if a component fails.
|
||||
.Pp
|
||||
Once the parity is known to be correct,
|
||||
Once the parity is known to be correct,
|
||||
it is then safe to perform
|
||||
.Xr disklabel 8 ,
|
||||
.Xr newfs 8 ,
|
||||
@ -653,13 +653,13 @@ fifo 100
|
||||
/dev/da0s1e is the real component, and will be the second disk of a RAID 1
|
||||
set. The component /dev/da6s1e, which must exist, but have no physical
|
||||
device associated with it, is simply used as a placeholder.
|
||||
Configuration (using
|
||||
Configuration (using
|
||||
.Fl C
|
||||
and
|
||||
and
|
||||
.Fl I Ar 12345
|
||||
as above) proceeds normally, but initialization of the RAID set will
|
||||
have to wait until all physical components are present. After
|
||||
configuration, this set can be used normally, but will be operating
|
||||
configuration, this set can be used normally, but will be operating
|
||||
in degraded mode. Once a second physical component is obtained, it
|
||||
can be hot-added, the existing data mirrored, and normal operation
|
||||
resumed.
|
||||
@ -731,11 +731,11 @@ Copyback is 100% complete.
|
||||
This indicates that all is well with the RAID set. Of importance here
|
||||
are the component lines which read
|
||||
.Sq optimal ,
|
||||
and the
|
||||
and the
|
||||
.Sq Parity status
|
||||
line which indicates that the parity is up-to-date. Note that if
|
||||
there are file systems open on the RAID set, the individual components
|
||||
will not be
|
||||
will not be
|
||||
.Sq clean
|
||||
but the set as a whole can still be clean.
|
||||
.Pp
|
||||
@ -776,21 +776,21 @@ Spares:
|
||||
/dev/da4s1e: spare
|
||||
.Ed
|
||||
.Pp
|
||||
Note that with the use of
|
||||
Note that with the use of
|
||||
.Fl f
|
||||
a reconstruction has not been started. To both fail the disk and
|
||||
start a reconstruction, the
|
||||
start a reconstruction, the
|
||||
.Fl F
|
||||
option must be used:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -F /dev/da2s1e raid0
|
||||
.Ed
|
||||
.Pp
|
||||
The
|
||||
The
|
||||
.Fl f
|
||||
option may be used first, and then the
|
||||
.Fl F
|
||||
option used later, on the same disk, if desired.
|
||||
option used later, on the same disk, if desired.
|
||||
Immediately after the reconstruction is started, the status will report:
|
||||
.Bd -unfilled -offset indent
|
||||
Components:
|
||||
@ -807,7 +807,7 @@ Copyback is 100% complete.
|
||||
.Ed
|
||||
.Pp
|
||||
This indicates that a reconstruction is in progress. To find out how
|
||||
the reconstruction is progressing the
|
||||
the reconstruction is progressing the
|
||||
.Fl S
|
||||
option may be used. This will indicate the progress in terms of the
|
||||
percentage of the reconstruction that is completed. When the
|
||||
@ -829,12 +829,12 @@ Copyback is 100% complete.
|
||||
.Ed
|
||||
.Pp
|
||||
At this point there are at least two options. First, if /dev/da2s1e is
|
||||
known to be good (i.e. the failure was either caused by
|
||||
known to be good (i.e. the failure was either caused by
|
||||
.Fl f
|
||||
or
|
||||
or
|
||||
.Fl F ,
|
||||
or the failed disk was replaced), then a copyback of the data can
|
||||
be initiated with the
|
||||
or the failed disk was replaced), then a copyback of the data can
|
||||
be initiated with the
|
||||
.Fl B
|
||||
option. In this example, this would copy the entire contents of
|
||||
/dev/da4s1e to /dev/da2s1e. Once the copyback procedure is complete, the
|
||||
@ -864,12 +864,12 @@ START drives
|
||||
.Ed
|
||||
.Pp
|
||||
This can be done as /dev/da4s1e is completely interchangeable with
|
||||
/dev/da2s1e at this point. Note that extreme care must be taken when
|
||||
/dev/da2s1e at this point. Note that extreme care must be taken when
|
||||
changing the order of the drives in a configuration. This is one of
|
||||
the few instances where the devices and/or their orderings can be
|
||||
changed without loss of data! In general, the ordering of components
|
||||
in a configuration file should
|
||||
.Ar never
|
||||
in a configuration file should
|
||||
.Ar never
|
||||
be changed.
|
||||
.Pp
|
||||
If a component fails and there are no hot spares
|
||||
@ -898,11 +898,11 @@ Spares:
|
||||
/dev/da4s1e: spare
|
||||
.Ed
|
||||
.Pp
|
||||
Reconstruction could then take place using
|
||||
Reconstruction could then take place using
|
||||
.Fl F
|
||||
as describe above.
|
||||
.Pp
|
||||
A second option is to rebuild directly onto /dev/da2s1e. Once the disk
|
||||
A second option is to rebuild directly onto /dev/da2s1e. Once the disk
|
||||
containing /dev/da2s1e has been replaced, one can simply use:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -R /dev/da2s1e raid0
|
||||
@ -948,8 +948,8 @@ raidctl -a /dev/da3s1e raid0
|
||||
raidctl -F component1 raid0
|
||||
.Ed
|
||||
.Pp
|
||||
at which point the data missing from
|
||||
.Sq component1
|
||||
at which point the data missing from
|
||||
.Sq component1
|
||||
would be reconstructed onto /dev/da3s1e.
|
||||
.Pp
|
||||
.Ss RAID on RAID
|
||||
@ -1004,7 +1004,7 @@ configured correctly, even if the SCSI ID's of the component disks
|
||||
have become scrambled.
|
||||
.Pp
|
||||
Having a system's root file system (/) on a RAID set is also allowed,
|
||||
with the
|
||||
with the
|
||||
.Sq a
|
||||
partition of such a RAID set being used for /.
|
||||
To use raid0a as the root file system, simply use:
|
||||
@ -1017,7 +1017,7 @@ To return raid0a to be just an auto-configuring set simply use the
|
||||
arguments.
|
||||
.Pp
|
||||
Note that kernels can only be directly read from RAID 1 components on
|
||||
alpha and pmax architectures. On those architectures, the
|
||||
alpha and pmax architectures. On those architectures, the
|
||||
.Dv FS_RAID
|
||||
file system is recognized by the bootblocks, and will properly load the
|
||||
kernel directly from a RAID 1 component. For other architectures, or
|
||||
@ -1033,26 +1033,26 @@ user will be prompted to select the root device. At this time, RAID
|
||||
.Pp
|
||||
A typical RAID 1 setup with root on RAID might be as follows:
|
||||
.Bl -enum
|
||||
.It
|
||||
.It
|
||||
wd0a - a small partition, which contains a complete, bootable, basic
|
||||
NetBSD installation.
|
||||
NetBSD installation.
|
||||
.It
|
||||
wd1a - also contains a complete, bootable, basic NetBSD installation.
|
||||
.It
|
||||
.It
|
||||
wd0e and wd1e - a RAID 1 set, raid0, used for the root file system.
|
||||
.It
|
||||
wd0f and wd1f - a RAID 1 set, raid1, which will be used only for
|
||||
swap space.
|
||||
swap space.
|
||||
.It
|
||||
wd0g and wd1g - a RAID 1 set, raid2, used for /usr, /home, or other
|
||||
data, if desired.
|
||||
.It
|
||||
.It
|
||||
wd0h and wd0h - a RAID 1 set, raid3, if desired.
|
||||
.El
|
||||
.Pp
|
||||
RAID sets raid0, raid1, and raid2 are all marked as
|
||||
auto-configurable. raid0 is marked as being a root file system.
|
||||
When new kernels are installed, the kernel is not only copied to /,
|
||||
When new kernels are installed, the kernel is not only copied to /,
|
||||
but also to wd0a and wd1a. The kernel on wd0a is required, since that
|
||||
is the kernel the system boots from. The kernel on wd1a is also
|
||||
required, since that will be the kernel used should wd0 fail. The
|
||||
@ -1061,7 +1061,7 @@ available, in the event that one of the drives fail.
|
||||
.Pp
|
||||
There is no requirement that the root file system be on the same disk
|
||||
as the kernel. For example, obtaining the kernel from wd0a, and using
|
||||
da0s1e and da1s1e for raid0, and the root file system, is fine. It
|
||||
da0s1e and da1s1e for raid0, and the root file system, is fine. It
|
||||
.Ar is
|
||||
critical, however, that there be multiple kernels available, in the
|
||||
event of media failure.
|
||||
@ -1070,7 +1070,7 @@ Multi-layered RAID devices (such as a RAID 0 set made
|
||||
up of RAID 1 sets) are
|
||||
.Ar not
|
||||
supported as root devices or auto-configurable devices at this point.
|
||||
(Multi-layered RAID devices
|
||||
(Multi-layered RAID devices
|
||||
.Ar are
|
||||
supported in general, however, as mentioned earlier.) Note that in
|
||||
order to enable component auto-detection and auto-configuration of
|
||||
@ -1084,9 +1084,9 @@ must be in the kernel configuration file. See
|
||||
for more details.
|
||||
.Pp
|
||||
.Ss Unconfiguration
|
||||
The final operation performed by
|
||||
The final operation performed by
|
||||
.Nm
|
||||
is to unconfigure a
|
||||
is to unconfigure a
|
||||
.Xr raid 4
|
||||
device. This is accomplished via a simple:
|
||||
.Bd -unfilled -offset indent
|
||||
@ -1111,7 +1111,7 @@ Distribution of components among controllers
|
||||
IO bandwidth
|
||||
.It
|
||||
File system access patterns
|
||||
.It
|
||||
.It
|
||||
CPU speed
|
||||
.El
|
||||
.Pp
|
||||
@ -1138,13 +1138,13 @@ be calculated before the stripe is written, and then the stripe data
|
||||
and parity can be written in parallel. When the amount of data being
|
||||
written is less than a full stripe worth, the
|
||||
.Sq small write
|
||||
problem occurs. Since a
|
||||
problem occurs. Since a
|
||||
.Sq small write
|
||||
means only a portion of the stripe on the components is going to
|
||||
change, the data (and parity) on the components must be updated
|
||||
slightly differently. First, the
|
||||
slightly differently. First, the
|
||||
.Sq old parity
|
||||
and
|
||||
and
|
||||
.Sq old data
|
||||
must be read from the components. Then the new parity is constructed,
|
||||
using the new data to be written, and the old data and old parity.
|
||||
@ -1158,18 +1158,18 @@ from the system will use exactly one large stripe write. As is seen
|
||||
later, there are some file system dependencies which may come into play
|
||||
here as well.
|
||||
.Pp
|
||||
Since the size of a
|
||||
Since the size of a
|
||||
.Sq large IO
|
||||
is often (currently) only 32K or 64K, on a 5-drive RAID 5 set it may
|
||||
be desirable to select a SectPerSU value of 16 blocks (8K) or 32
|
||||
blocks (16K). Since there are 4 data sectors per stripe, the maximum
|
||||
data per stripe is 64 blocks (32K) or 128 blocks (64K). Again,
|
||||
empirical measurement will provide the best indicators of which
|
||||
values will yeild better performance.
|
||||
values will yield better performance.
|
||||
.Pp
|
||||
The parameters used for the file system are also critical to good
|
||||
performance. For
|
||||
.Xr newfs 8 ,
|
||||
performance. For
|
||||
.Xr newfs 8 ,
|
||||
for example, increasing the block size to 32K or 64K may improve
|
||||
performance dramatically. As well, changing the cylinders-per-group
|
||||
parameter from 16 to 32 or higher is often not only necessary for
|
||||
@ -1181,57 +1181,57 @@ Despite the length of this man-page, configuring a RAID set is a
|
||||
relatively straight-forward process. All that needs to be done is the
|
||||
following steps:
|
||||
.Bl -enum
|
||||
.It
|
||||
Use
|
||||
.Xr disklabel 8
|
||||
.It
|
||||
Use
|
||||
.Xr disklabel 8
|
||||
to create the components (of type RAID).
|
||||
.It
|
||||
Construct a RAID configuration file: e.g.
|
||||
.Sq raid0.conf
|
||||
.It
|
||||
Configure the RAID set with:
|
||||
.It
|
||||
Construct a RAID configuration file: e.g.
|
||||
.Sq raid0.conf
|
||||
.It
|
||||
Configure the RAID set with:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -C raid0.conf
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Initialize the component labels with:
|
||||
.It
|
||||
Initialize the component labels with:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -I 123456 raid0
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Initialize other important parts of the set with:
|
||||
.It
|
||||
Initialize other important parts of the set with:
|
||||
.Bd -unfilled -offset indent
|
||||
raidctl -i raid0
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Get the default label for the RAID set:
|
||||
Get the default label for the RAID set:
|
||||
.Bd -unfilled -offset indent
|
||||
disklabel raid0 > /tmp/label
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Edit the label:
|
||||
.It
|
||||
Edit the label:
|
||||
.Bd -unfilled -offset indent
|
||||
vi /tmp/label
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Put the new label on the RAID set:
|
||||
.It
|
||||
Put the new label on the RAID set:
|
||||
.Bd -unfilled -offset indent
|
||||
disklabel -R -r raid0 /tmp/label
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Create the file system:
|
||||
.It
|
||||
Create the file system:
|
||||
.Bd -unfilled -offset indent
|
||||
newfs /dev/rraid0e
|
||||
newfs /dev/rraid0e
|
||||
.Ed
|
||||
.Pp
|
||||
.It
|
||||
Mount the file system:
|
||||
Mount the file system:
|
||||
.Bd -unfilled -offset indent
|
||||
mount /dev/raid0e /mnt
|
||||
.Ed
|
||||
@ -1243,7 +1243,7 @@ raidctl -c raid0.conf
|
||||
.Ed
|
||||
.Pp
|
||||
To re-configure the RAID set the next time it is needed, or put
|
||||
raid0.conf into /etc where it will automatically be started by
|
||||
raid0.conf into /etc where it will automatically be started by
|
||||
the /etc/rc scripts.
|
||||
.El
|
||||
.Pp
|
||||
@ -1252,11 +1252,11 @@ Certain RAID levels (1, 4, 5, 6, and others) can protect against some
|
||||
data loss due to component failure. However the loss of two
|
||||
components of a RAID 4 or 5 system, or the loss of a single component
|
||||
of a RAID 0 system will result in the entire file system being lost.
|
||||
RAID is
|
||||
RAID is
|
||||
.Ar NOT
|
||||
a substitute for good backup practices.
|
||||
.Pp
|
||||
Recomputation of parity
|
||||
Recomputation of parity
|
||||
.Ar MUST
|
||||
be performed whenever there is a chance that it may have been
|
||||
compromised. This includes after system crashes, or before a RAID
|
||||
@ -1269,7 +1269,7 @@ is to use parity, but not keep the parity correct. At least with RAID
|
||||
.Sh FILES
|
||||
.Bl -tag -width /dev/XXrXraidX -compact
|
||||
.It Pa /dev/{,r}raid*
|
||||
.Cm raid
|
||||
.Cm raid
|
||||
device special files.
|
||||
.El
|
||||
.Pp
|
||||
@ -1282,7 +1282,7 @@ Hot-spare removal is currently not available.
|
||||
.Sh HISTORY
|
||||
RAIDframe is a framework for rapid prototyping of RAID structures
|
||||
developed by the folks at the Parallel Data Laboratory at Carnegie
|
||||
Mellon University (CMU).
|
||||
Mellon University (CMU).
|
||||
A more complete description of the internals and functionality of
|
||||
RAIDframe is found in the paper "RAIDframe: A Rapid Prototyping Tool
|
||||
for RAID Systems", by William V. Courtright II, Garth Gibson, Mark
|
||||
|
@ -83,7 +83,7 @@ Boot the specified
|
||||
on the next system boot.
|
||||
If the kernel boots successfully, the
|
||||
.Em default
|
||||
kernel will be booted on succesive boots, this is a one-shot option.
|
||||
kernel will be booted on successive boots, this is a one-shot option.
|
||||
If the boot fails, the system will continue attempting to boot
|
||||
.Ar kernel
|
||||
until the boot process is interrupted and a valid kernel booted.
|
||||
|
@ -470,7 +470,7 @@ both
|
||||
.Ar src
|
||||
and
|
||||
.Ar dst
|
||||
can be omited.
|
||||
can be omitted.
|
||||
.Ar level
|
||||
is to be one of the following:
|
||||
.Li default , use , require
|
||||
|
@ -207,7 +207,7 @@ configuration.
|
||||
.Op Fl r
|
||||
.Op Ar volume | plex | subdisk
|
||||
.Xc
|
||||
Reset statistisc counters for the specified objects, or for all objects if none
|
||||
Reset statistics counters for the specified objects, or for all objects if none
|
||||
are specified.
|
||||
.It Xo
|
||||
.Ic rm
|
||||
@ -2073,7 +2073,7 @@ volume raid setupstate
|
||||
.Ed
|
||||
.Pp
|
||||
Here the plexes are striped, increasing performance, and there are two of them,
|
||||
increasing reliablity. Note that this example shows the subdisks of the second
|
||||
increasing reliability. Note that this example shows the subdisks of the second
|
||||
plex in reverse order from the first plex. This is for performance reasons and
|
||||
will be discussed below. In addition, the volume specification includes the
|
||||
keyword
|
||||
|
@ -20,7 +20,7 @@ pass in from any to any
|
||||
block in log quick on ppp0 proto icmp from any to any icmp-type redir
|
||||
block in log quick on ppp0 proto tcp/udp all with short
|
||||
#
|
||||
# Block any IP spoofing atempts. (Packets "from" our network
|
||||
# Block any IP spoofing attempts. (Packets "from" our network
|
||||
# shouldn't be coming in from outside).
|
||||
#
|
||||
block in log quick on ppp0 from 192.168.4.0/24 to any
|
||||
|
@ -23,7 +23,7 @@ block in log quick on ppp0 proto icmp from any to any icmp-type redir
|
||||
block in log quick on ppp0 proto tcp/udp all with short
|
||||
block in log quick on ppp0 from any to any with ipopts
|
||||
#
|
||||
# Block any IP spoofing atempts. (Packets "from" our network
|
||||
# Block any IP spoofing attempts. (Packets "from" our network
|
||||
# shouldn't be coming in from outside).
|
||||
#
|
||||
block in log quick on ppp0 from 192.168.4.0/24 to any
|
||||
|
@ -44,7 +44,7 @@ Value returned as
|
||||
.Fa dst
|
||||
is supposed to be used in conjunction with
|
||||
.Fn pthread_attr_get*
|
||||
functions to retrive individual values from
|
||||
functions to retrieve individual values from
|
||||
.Vt pthread_attr_t
|
||||
structure.
|
||||
Parameter
|
||||
|
@ -87,7 +87,7 @@ functions copy the value of the attribute that corresponds to each function name
|
||||
to the location pointed to by the second function parameter.
|
||||
.Sh RETURN VALUES
|
||||
If successful, these functions return 0.
|
||||
Otherwise, an error number is returned to indicacte the error.
|
||||
Otherwise, an error number is returned to indicate the error.
|
||||
.Sh ERRORS
|
||||
.Fn pthread_mutexattr_init
|
||||
will fail if:
|
||||
|
@ -88,7 +88,7 @@ is enabled.
|
||||
Logically OR the following bits together:
|
||||
.Bl -column -offset indent Value Function
|
||||
.Em "Value Function"
|
||||
0x0001 Show miscellanious information
|
||||
0x0001 Show miscellaneous information
|
||||
0x0002 Show sense data
|
||||
0x0004 Show Serial EEPROM contents
|
||||
0x0008 Show bus termination settings
|
||||
@ -118,7 +118,7 @@ configuration option.
|
||||
The value assigned to this option should be a bitmap
|
||||
of all units where target mode is desired.
|
||||
For example, a value of 0x25 would enable target mode on units 0, 2, and 5.
|
||||
Note that target mode is only supoprted for ultra160 speeds and below.
|
||||
Note that target mode is only supported for ultra160 speeds and below.
|
||||
.Pp
|
||||
Per target configuration performed in the
|
||||
.Tn SCSI-Select
|
||||
|
@ -69,7 +69,7 @@ Perform a crypto operation against a previously setup session.
|
||||
.El
|
||||
.Sh FEATURES
|
||||
Depending on hardware being present, the following symmetric and
|
||||
assymetric cryptographic features are potentially available from
|
||||
asymmetric cryptographic features are potentially available from
|
||||
.Pa /dev/crypto :
|
||||
.Pp
|
||||
.Bl -tag -width ".Dv CRYPTO_RIPEMD160_HMAC" -offset indent -compact
|
||||
|
@ -126,10 +126,10 @@ A geom with attached consumers has a rank one higher than the
|
||||
highest rank of the geoms of the providers its consumers are
|
||||
attached to.
|
||||
.El
|
||||
.Sh "SPECIAL TOPOLOGICAL MANEUVRES"
|
||||
.Sh "SPECIAL TOPOLOGICAL MANEUVERS"
|
||||
In addition to the straightforward attach, which attaches a consumer
|
||||
to a provider, and dettach, which breaks the bond, a number of special
|
||||
toplogical maneuvres exists to facilitate configuration and to
|
||||
to a provider, and detach, which breaks the bond, a number of special
|
||||
topological maneuvers exists to facilitate configuration and to
|
||||
improve the overall flexibility.
|
||||
.Pp
|
||||
.Em TASTING
|
||||
@ -174,7 +174,7 @@ not loose quorum.
|
||||
When a provider is orphaned, this does not result in any immediate
|
||||
change in the topology, any attached consumers are still attached,
|
||||
any opened paths are still open, it is the responsibility of the
|
||||
geoms above to close and dettach as soon as this can happen.
|
||||
geoms above to close and detach as soon as this can happen.
|
||||
.Pp
|
||||
The typical scenario is that a device driver notices a disk has
|
||||
gone and orphans the provider for it.
|
||||
@ -184,11 +184,11 @@ Providers, which are not attached, are destroyed right away.
|
||||
Eventually at the toplevel the geom which interfaces
|
||||
to the DEVFS received an orphan event on its consumer and it
|
||||
calls destroy_dev(9) and does an explicit close if the
|
||||
device was open and then dettaches its consumer.
|
||||
device was open and then detaches its consumer.
|
||||
The provider below is now no longer attached to and can be
|
||||
destroyed, if the geom has no more providers it can dettach
|
||||
destroyed, if the geom has no more providers it can detach
|
||||
its consumer and selfdestruct and so the carnage passes back
|
||||
down the tree, until the original provider is dettached from
|
||||
down the tree, until the original provider is detached from
|
||||
and it can be destroyed by the geom serving the device driver.
|
||||
.Pp
|
||||
While this approach seems byzantine, it does provide the maximum
|
||||
@ -265,7 +265,7 @@ represented by struct bio, originate at a consumer,
|
||||
are scheduled on its attached provider, and when processed, returned
|
||||
to the consumer.
|
||||
It is important to realize that the struct bio which
|
||||
enters throuh the provider of a particular geom does not "come
|
||||
enters through the provider of a particular geom does not "come
|
||||
out on the other side".
|
||||
Even simple transformations like MBR and BSD will clone the
|
||||
struct bio, modify the clone, and schedule the clone on their
|
||||
|
@ -1,12 +1,12 @@
|
||||
.\" Copyright (c) 2002 Networks Associates Technology, Inc.
|
||||
.\" All rights reserved.
|
||||
.\"
|
||||
.\"
|
||||
.\" This software was developed for the FreeBSD Project by Chris
|
||||
.\" Costello at Safeport Network Services and NAI Labs, the Security
|
||||
.\" Research Division of Network Associates, Inc. under DARPA/SPAWAR
|
||||
.\" contract N66001-01-C-8035 ("CBOSS"), as part of the DARPA CHATS
|
||||
.\" research program.
|
||||
.\"
|
||||
.\"
|
||||
.\" Redistribution and use in source and binary forms, with or without
|
||||
.\" modification, are permitted provided that the following conditions
|
||||
.\" are met:
|
||||
@ -15,7 +15,7 @@
|
||||
.\" 2. Redistributions in binary form must reproduce the above copyright
|
||||
.\" notice, this list of conditions and the following disclaimer in the
|
||||
.\" documentation and/or other materials provided with the distribution.
|
||||
.\"
|
||||
.\"
|
||||
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
|
||||
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||
@ -27,7 +27,7 @@
|
||||
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
.\" SUCH DAMAGE.
|
||||
.\"
|
||||
.\"
|
||||
.\" $FreeBSD$
|
||||
.Dd NOVEMBER 18, 2002
|
||||
.Os
|
||||
@ -171,7 +171,7 @@ The Biba integrity model is also similar to
|
||||
with the exception that the dominance operator and access rules are reversed,
|
||||
preventing the downward flow of information rather than the upward flow of
|
||||
information.
|
||||
Multi-Level Security (MLS) protects the confentiality, rather than the
|
||||
Multi-Level Security (MLS) protects the confidentiality, rather than the
|
||||
integrity, of subjects and objects.
|
||||
.Sh SEE ALSO
|
||||
.Xr lomac 4 ,
|
||||
|
@ -59,7 +59,7 @@ A read-write integer variable that controls the HCI connection timeout, i.e.\&
|
||||
how long the HCI layer will wait for the
|
||||
.Dv Connection_Complete
|
||||
event.
|
||||
Normaly this should not be required as Bluetooth devices have
|
||||
Normally this should not be required as Bluetooth devices have
|
||||
connection timeout of their own and will send event back.
|
||||
This timeout
|
||||
is required to ensure that no connection will stall in case when the HCI
|
||||
|
@ -242,7 +242,7 @@ Not implemented.
|
||||
.It Dv SO_L2CAP_FLUSH
|
||||
Get (set) value of the flush timeout.
|
||||
.Bf -emphasis
|
||||
Not implemeted.
|
||||
Not implemented.
|
||||
.Ef
|
||||
.El
|
||||
.Sh HOOKS
|
||||
|
@ -207,7 +207,7 @@ SCO data packets that the Host Controller can have waiting for transmission in
|
||||
its buffers.
|
||||
.El
|
||||
.Pp
|
||||
As soon as HCI initialization has been successfuly performed, HCI control
|
||||
As soon as HCI initialization has been successfully performed, HCI control
|
||||
application must turn on
|
||||
.Dq inited
|
||||
bit for the node.
|
||||
@ -271,8 +271,8 @@ structure.
|
||||
.It Dv raw
|
||||
Raw hook.
|
||||
Every HCI frame (including HCI command frame) that goes in
|
||||
or out will be delivired to the hook.
|
||||
Usually Bluetooth raw HCI sockets layer is connected to the hook.
|
||||
or out will be delivered to the hook.
|
||||
Usually the Bluetooth raw HCI socket layer is connected to the hook.
|
||||
Single HCI frame contained in single
|
||||
.Vt mbuf
|
||||
structure.
|
||||
|
@ -766,7 +766,7 @@ At debug level 2, much more detailed information is logged.
|
||||
.Sh CAVEATS
|
||||
Many pad devices behave as if the first (left) button were pressed if
|
||||
the user `taps' the surface of the pad.
|
||||
In contrast, some pad products, e.g. some verions of ALPS GlidePoint
|
||||
In contrast, some pad products, e.g. some versions of ALPS GlidePoint
|
||||
and Interlink VersaPad, treat the tapping action
|
||||
as fourth button events.
|
||||
.Pp
|
||||
|
@ -303,7 +303,7 @@ recycling for a few minutes.
|
||||
.It tcp.inet.tcp.rexmit_{min,slop}
|
||||
Adjust the retransmit timer calculation for TCP. The slop is
|
||||
typically added to the raw calculation to take into account
|
||||
occassional variances that the SRTT (smoothed round trip time)
|
||||
occasional variances that the SRTT (smoothed round trip time)
|
||||
is unable to accomodate, while the minimum specifies an
|
||||
absolute minimum. While a number of TCP RFCs suggest a 1
|
||||
second minimum these RFCs tend to focus on streaming behavior
|
||||
|
@ -225,7 +225,7 @@ Dump the trace buffer from the card. The argument is
|
||||
.Vt "struct ti_trace_buf" .
|
||||
.It Dv ALT_ATTACH
|
||||
This ioctl is used for compatibility with Alteon's Solaris driver. They
|
||||
apparantly only have one character interface for debugging, so they have
|
||||
apparently only have one character interface for debugging, so they have
|
||||
to tell it which Tigon instance they want to debug. This ioctl is a noop
|
||||
for
|
||||
.Fx .
|
||||
|
@ -2073,7 +2073,7 @@ Set to
|
||||
by default.
|
||||
Set to
|
||||
.Dq Li YES
|
||||
to enable the display and funtionality of function key labels (as found
|
||||
to enable the display and functionality of function key labels (as found
|
||||
on
|
||||
.Tn Hewlett-Packard
|
||||
terminals such as the
|
||||
|
@ -528,7 +528,7 @@ TCP session disconnections.
|
||||
.Pp
|
||||
The
|
||||
.Va net.inet.tcp.delayed_ack
|
||||
TCP feature is largly misunderstood.
|
||||
TCP feature is largely misunderstood.
|
||||
Historically speaking, this feature
|
||||
was designed to allow the acknowledgement to transmitted data to be returned
|
||||
along with the response.
|
||||
@ -551,7 +551,7 @@ slightly delay the teardown of a connection, or slightly delay the ramp-up
|
||||
of a slow-start TCP connection.
|
||||
While we are not sure we believe that
|
||||
the several FAQs related to packages such as SAMBA and SQUID which advise
|
||||
turning off delayed acks may be refering to the slow-start issue.
|
||||
turning off delayed acks may be referring to the slow-start issue.
|
||||
In
|
||||
.Fx ,
|
||||
it would be more beneficial to increase the slow-start flightsize via
|
||||
|
@ -176,7 +176,7 @@ configuration suitable for bridges, routers and firewalls.
|
||||
.Pp
|
||||
The following configurations are also present but for reference
|
||||
only.
|
||||
Many of them are irrimediably out of date and no effort
|
||||
Many of them are irremediably out of date and no effort
|
||||
is done to keep them in good shape:
|
||||
.Bl -hang -width ".Pa bridge"
|
||||
.It Pa dial
|
||||
|
@ -93,10 +93,10 @@ be rewritten to make use of it.
|
||||
The
|
||||
.Nm
|
||||
functions were mostly imported from
|
||||
.Nx
|
||||
.Nx
|
||||
and it is intended that they remain synced between the
|
||||
two projects. With that in mind there are several variable
|
||||
defenitions that can help in this regard. They are:
|
||||
definitions that can help in this regard. They are:
|
||||
.Bl -tag -width 4n
|
||||
.It Ic OSTYPE
|
||||
Its value will be either
|
||||
@ -243,7 +243,7 @@ log it to the system log using
|
||||
.Xr logger 1 ,
|
||||
and
|
||||
return to the caller.
|
||||
The error message consists of the sript name
|
||||
The error message consists of the script name
|
||||
(from
|
||||
.Sy $0 ) ,
|
||||
followed by
|
||||
@ -251,7 +251,7 @@ followed by
|
||||
and then
|
||||
.Ar message .
|
||||
This function is intended to be used by developers
|
||||
as an aid to debuging scripts. It can be turned on or off
|
||||
as an aid to debugging scripts. It can be turned on or off
|
||||
by the
|
||||
.Xr rc.conf 5
|
||||
variable
|
||||
@ -296,7 +296,7 @@ The message consists of the script name
|
||||
followed by
|
||||
.Dq ": INFO: " ,
|
||||
and then
|
||||
.Ar mesage .
|
||||
.Ar message .
|
||||
The display of this informational output can be
|
||||
turned on or off by the
|
||||
.Xr rc.conf 5
|
||||
@ -531,7 +531,7 @@ checks and process (non-)existence checks.
|
||||
Shell commands to run if running
|
||||
.Ar argument Ns Sy _cmd
|
||||
or the default method for
|
||||
.Ar argument
|
||||
.Ar argument
|
||||
returned a zero exit code.
|
||||
.It Sy sig_stop
|
||||
Signal to send the processes to stop in the default
|
||||
@ -618,7 +618,7 @@ Argument provided to
|
||||
.Sy run_rc_command ,
|
||||
after fast and force processing has been performed.
|
||||
.It Sy rc_flags
|
||||
Flasg to start the default command with.
|
||||
Flags to start the default command with.
|
||||
Defaults to
|
||||
.Sy ${name}_flags ,
|
||||
unless overridden by the environment variable
|
||||
|
@ -107,7 +107,7 @@ the kernel will then disallow and further userland use of the filter.
|
||||
.Pp
|
||||
.Fn accept_filt_get
|
||||
is used internally to locate which accept filter to use via the
|
||||
.Fn setsocketopt
|
||||
.Fn setsockopt
|
||||
syscall.
|
||||
.Pp
|
||||
.Fn accept_filt_generic_mod_event
|
||||
|
@ -189,7 +189,7 @@ The
|
||||
MAC Framework was designed by
|
||||
.An Robert Watson ,
|
||||
and implemented by the Network Associates Laboratories Network Security
|
||||
(NETSEC), Secure Execution Environement (SEE), and Adaptive
|
||||
(NETSEC), Secure Execution Environment (SEE), and Adaptive
|
||||
Network Defense research groups.
|
||||
Network Associates Laboratory staff contributing to the CBOSS Project
|
||||
include (in alphabetical order):
|
||||
|
@ -59,7 +59,7 @@ The
|
||||
function implements the machine independent prelude to a thread context
|
||||
switch.
|
||||
It is called from only a few distinguished places in the kernel
|
||||
code as a result of the principle of non-preemtable kernel mode execution.
|
||||
code as a result of the principle of non-preemptable kernel mode execution.
|
||||
The various major uses of
|
||||
.Nm
|
||||
can be enumerated as follows:
|
||||
|
@ -29,7 +29,7 @@
|
||||
.Os
|
||||
.Sh NAME
|
||||
.Nm microseq
|
||||
.Nd ppbus microseqencer developer's guide
|
||||
.Nd ppbus microsequencer developer's guide
|
||||
.Sh SYNOPSIS
|
||||
.In sys/types.h
|
||||
.In dev/ppbus/ppbconf.h
|
||||
|
@ -259,7 +259,7 @@ types.
|
||||
qualifiers, and
|
||||
.Ic typedef Ns -names
|
||||
other than the one being declared.)
|
||||
Separate these identifers from asterisks using a single space.
|
||||
Separate these identifiers from asterisks using a single space.
|
||||
.Pp
|
||||
When declaring variables in structures, declare them sorted by use, then
|
||||
by size, and then in alphabetical order.
|
||||
|
@ -129,6 +129,6 @@ command to set the arguments without disrupting the value(s) of
|
||||
shell options varies from one shell version to another.
|
||||
.Pp
|
||||
Each shellscript has to carry complex code to parse arguments halfway
|
||||
correcty (like the example presented here). A better getopt-like tool
|
||||
correctly (like the example presented here). A better getopt-like tool
|
||||
would move much of the complexity into the tool and keep the client
|
||||
shell scripts simpler.
|
||||
|
@ -1265,7 +1265,7 @@ and not in
|
||||
while in the first example it's active in both, because in the first
|
||||
example the
|
||||
.B example
|
||||
startion condition is an
|
||||
start condition is an
|
||||
.I inclusive
|
||||
.B (%s)
|
||||
start condition.
|
||||
|
@ -369,7 +369,7 @@ The output format of tracing and of
|
||||
.Ic dumpdef
|
||||
are not specified in any standard,
|
||||
are likely to change and should not be relied upon.
|
||||
The current format of tracing is closely modelled on GNU-m4,
|
||||
The current format of tracing is closely modeled on GNU-m4,
|
||||
to allow
|
||||
.Nm autoconf
|
||||
to work.
|
||||
|
@ -106,7 +106,7 @@ options consistent with the GNU C compiler.
|
||||
.It Ev MKDEP_CPP
|
||||
Specifies the preprocessor to use. The default is "${CC} -E".
|
||||
.It Ev MKDEP_CPP_OPTS
|
||||
Specifie the non-CFLAGS options for the preprocessor. The default is
|
||||
Specifies the non-CFLAGS options for the preprocessor. The default is
|
||||
"-M".
|
||||
.El
|
||||
.Sh SEE ALSO
|
||||
|
@ -71,7 +71,7 @@ to place comments in the file.
|
||||
Following options are available:
|
||||
.Bl -tag -width indent
|
||||
.It Fl d
|
||||
Turns on debuging messages.
|
||||
Turns on debugging messages.
|
||||
.It Fl o
|
||||
Specify output file.
|
||||
.El
|
||||
|
@ -56,7 +56,7 @@ or a default value of 10.
|
||||
The lower the nice value of a process, the higher its scheduling priority.
|
||||
.Pp
|
||||
The superuser may specify a negative increment in order to run a utility
|
||||
with a higher scheduling prority.
|
||||
with a higher scheduling priority.
|
||||
.Pp
|
||||
Some shells may provide a builtin
|
||||
.Nm
|
||||
|
@ -466,12 +466,12 @@ Display a list of available devices.
|
||||
.Ar type , Ns Ar if , Ns Ar pass
|
||||
.Op | Ar ...
|
||||
.Xc
|
||||
Display devivces matching the given pattern. The basic matching
|
||||
Display devices matching the given pattern. The basic matching
|
||||
expressions are the same as those used in
|
||||
.Xr iostat 8
|
||||
with one difference. Instead of specifying multiple
|
||||
.Fl t
|
||||
arguments which are then ORed together, the user instead specifys multiple
|
||||
arguments which are then ORed together, the user instead specifies multiple
|
||||
matching expressions joined by the pipe
|
||||
.Pq Ql \&|
|
||||
character.
|
||||
|
@ -93,7 +93,7 @@ command appeared in
|
||||
.Sh BUGS
|
||||
.Bl -item
|
||||
.It
|
||||
Writting an image of a tape to a file does not preserve much more than
|
||||
Writing an image of a tape to a file does not preserve much more than
|
||||
the raw data.
|
||||
Block size(s) and tape EOF marks are lost which would
|
||||
otherwise be preserved in a tape-to-tape copy.
|
||||
|
@ -588,7 +588,7 @@ The host specification may be either a host name (see
|
||||
.Xr hosts 5 ) ,
|
||||
an Internet address specified in the \*(Lqdot notation\*(Rq (see
|
||||
.Xr inet 3 ) ,
|
||||
or IPv6 host name or IPv6 coloned-hexadecimal addreess.
|
||||
or IPv6 host name or IPv6 coloned-hexadecimal address.
|
||||
The
|
||||
.Fl l
|
||||
option may be used to specify the user name
|
||||
|
@ -72,7 +72,7 @@ it.
|
||||
Otherwise, this option has no effect.
|
||||
.It Fl h
|
||||
Print times in a human friendly format. Times are printed in minutes, hours,
|
||||
etc. as appropiate.
|
||||
etc. as appropriate.
|
||||
.It Fl l
|
||||
The contents of the
|
||||
.Em rusage
|
||||
|
@ -106,7 +106,7 @@ as a logical EOF marker.
|
||||
.It Fl I Ar replstr
|
||||
Execute
|
||||
.Ar utility
|
||||
for each input line, replacing one or more occurences of
|
||||
for each input line, replacing one or more occurrences of
|
||||
.Ar replstr
|
||||
in up to
|
||||
.Ar replacements
|
||||
|
@ -71,7 +71,7 @@ the OS. The information is stored in AML format.
|
||||
.Pp
|
||||
The AML interpreter can execute any of the Control Methods specified
|
||||
by users. When executed, it interprets the byte sequence in the
|
||||
Control Method of DSDT, and disassembles the opecodes that it
|
||||
Control Method of DSDT, and disassembles the opcodes that it
|
||||
recognizes into ASL
|
||||
(ACPI Source Language)
|
||||
format to be displayed.
|
||||
@ -204,7 +204,7 @@ characters are necessary for specifying objects which have less than four
|
||||
character string. Unless additional underscores specified, matching
|
||||
occurs as the beginning of word with the specified number of characters.
|
||||
.It Cm h
|
||||
.Em Show help messsage :
|
||||
.Em Show help message :
|
||||
Displays the command summary of
|
||||
.Nm .
|
||||
.El
|
||||
|
@ -91,7 +91,7 @@ the user's full name.
|
||||
Additionally, it may contain a comma separated
|
||||
list of values such as office number and work and home phones.
|
||||
If the
|
||||
name contains an amperstand it will be replaced by the capitalized
|
||||
name contains an ampersand it will be replaced by the capitalized
|
||||
login name when displayed by other programs.
|
||||
The
|
||||
.Ql \&:
|
||||
@ -248,7 +248,7 @@ argument may have one of the following values:
|
||||
.Bl -tag -width ".Cm random"
|
||||
.It Cm no
|
||||
Disable the password.
|
||||
Instead of an encrypted string, the passowrd field will contain a single
|
||||
Instead of an encrypted string, the password field will contain a single
|
||||
.Ql *
|
||||
character.
|
||||
The user may not log in until the super-user
|
||||
@ -366,7 +366,7 @@ option is used with a
|
||||
or
|
||||
.Cm none
|
||||
argument.
|
||||
Be carefull not to terminate this field with a closing
|
||||
Be careful not to terminate this field with a closing
|
||||
.Ql \&:
|
||||
because it will be treated as part of the password.
|
||||
.El
|
||||
@ -430,7 +430,7 @@ each line of the message file.
|
||||
This means that shell commands can also be embedded in the message file.
|
||||
The
|
||||
.Nm
|
||||
utility attemps to mitigate the possibility of an attacker using this
|
||||
utility attempts to mitigate the possibility of an attacker using this
|
||||
feature by refusing to evaluate the file if it is not owned and writeable
|
||||
only by the root user.
|
||||
In addition, shell special characters and operators will have to be
|
||||
|
@ -138,7 +138,7 @@ prompts on whether to remove the specified user and whether to remove
|
||||
the home directory.
|
||||
This option requires that either the
|
||||
.Fl f
|
||||
option be used, or one or more user names be given as commmand line
|
||||
option be used, or one or more user names be given as command line
|
||||
arguments.
|
||||
.It Ar username
|
||||
Identifies one or more users to be removed; if not present,
|
||||
|
@ -395,7 +395,7 @@ the factory default.
|
||||
Set the radio frequency of a given interface.
|
||||
The
|
||||
.Ar frequency
|
||||
should be specfied as a channel ID as shown in the table below.
|
||||
should be specified as a channel ID as shown in the table below.
|
||||
The
|
||||
list of available frequencies is dependent on radio regulations specified
|
||||
by regional authorities.
|
||||
@ -442,7 +442,7 @@ The default is 2312.
|
||||
.It Fl i Ar iface Fl r Ar RTS_threshold
|
||||
Set the RTS/CTS threshold for a given interface.
|
||||
This controls the
|
||||
number of bytes used for the RTS/CTS handhake boundary.
|
||||
number of bytes used for the RTS/CTS handshake boundary.
|
||||
The
|
||||
.Ar RTS_threshold
|
||||
can be any value between 0 and 2312.
|
||||
@ -487,7 +487,7 @@ secure than using
|
||||
authentication when WEP is enabled.
|
||||
.Pp
|
||||
Devices may alternate among all of the configured WEP keys when
|
||||
tranmitting packets.
|
||||
transmitting packets.
|
||||
Therefore, all configured keys (up to four) must agree.
|
||||
.Sh EXAMPLES
|
||||
.Bd -literal -offset indent
|
||||
|
@ -198,7 +198,7 @@ Other events will not be sent to
|
||||
.It
|
||||
command line syntax
|
||||
.Bd -ragged -offset indent
|
||||
In the example above, the three lines begining with
|
||||
In the example above, the three lines beginning with
|
||||
.Ql exec
|
||||
are commands for the event.
|
||||
Each line should be terminated with a semicolon.
|
||||
|
@ -59,7 +59,7 @@ leading or trailing blanks.
|
||||
The
|
||||
.Em name
|
||||
string may also be placed in quote (single or double, but matching)
|
||||
to preserve leading, traling or inner blanks.
|
||||
to preserve leading, trailing or inner blanks.
|
||||
.Pp
|
||||
Several environment variables are set up
|
||||
automatically by the
|
||||
|
@ -76,7 +76,7 @@ Possible values are:
|
||||
.Dq Li 2.88M ,
|
||||
or
|
||||
.Dq Li unknown .
|
||||
This information is primarily intented to be easily parsable by
|
||||
This information is primarily intended to be easily parsable by
|
||||
scripts.
|
||||
.Pp
|
||||
In order to add some descriptive text that makes the output better
|
||||
|
@ -49,7 +49,7 @@
|
||||
The
|
||||
.Nm
|
||||
utility configures the physical address for the generic IP tunnel
|
||||
inteface, such as "gif0".
|
||||
interface, such as "gif0".
|
||||
Argument
|
||||
.Ar physsrc
|
||||
and
|
||||
|
@ -45,7 +45,7 @@ is part of the isdn4bsd package and is used to detect DTMF tones in the
|
||||
audio stream.
|
||||
.Pp
|
||||
It reads audio G.711 A-Law coded data from stdin and outputs the detected
|
||||
numbers values as ASCII charcters to stdout.
|
||||
numbers values as ASCII characters to stdout.
|
||||
.Pp
|
||||
The detector is implemented as 8 narrow band-pass filters realized with
|
||||
an integer double-cross recursive algorithm. Various ad-hoc methods are
|
||||
|
@ -110,7 +110,7 @@ print layer 1 (I.430) INFO signals to monitor layer 1 activity (default off).
|
||||
switch displaying of Layer 2 (Q.921) frames off (default on).
|
||||
.It Fl n
|
||||
This option takes a numeric argument specifying the minimum
|
||||
frame size in octetts a frame must have to be displayed. (default 0)
|
||||
frame size in octets a frame must have to be displayed. (default 0)
|
||||
.It Fl o
|
||||
switch off writing trace output to a file (default on).
|
||||
.It Fl p
|
||||
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user