hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2024-12-22 17:24:23 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix a bunch typos, one fix of which is from docs/10794

Browse Source
This commit is contained in:
Tim Vanderhoek 1999-04-30 06:37:16 +00:00
parent 430210c00b
commit d732587c28
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=46195
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
share/man/man4/da.4
View File

@ -23,7 +23,7 @@
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" $Id: sd.4,v 1.11 1997/04/01 04:04:09 jdp Exp $
.\" $Id: da.4,v 1.12 1998/10/16 03:28:12 ken Exp $
.\"
.Dd October 15, 1998
.Dt DA 4
@ -76,7 +76,7 @@ and
respectively.
.Pp
If an uninitialized disk is opened, the slice table will be
initialized with a ficticious
initialized with a fictitious
.Tn FreeBSD
slice spanning the entire disk. Similarly, if an uninitialized
(or
@ -86,14 +86,14 @@ by the drive and a single
.Sq Li c
partition encompassing the entire slice.
.Sh CACHE EFFECTS
Many direct access devices are equiped with read and/or write caches.
Many direct access devices are equipped with read and/or write caches.
Parameters affecting the device's cache are stored in mode page 8,
the caching control page. Mode pages can be examined and modified
via the
.Xr camcontrol 8
utility.
The read cache is used to store data from device initiated read ahead
The read cache is used to store data from device-initiated read ahead
operations as well as frequently used data. The read cache is transparant
to the user and can be enabled without any adverse effect. Most devices
with a read cache come from the factory with it enabled. The read cache
@ -115,7 +115,7 @@ Power Supply (UPS). The
device driver ensures that the cache and media are synchronized upon
final close of the device or an unexpected shutdown (panic) event. This
ensures that it is safe to disconnect power once the operating system
has reported that it has halted. The write cache can be enabeled by
has reported that it has halted. The write cache can be enabled by
setting the
.Tn WCE
(Write Cache Enable) bit in the caching control mode page.
@ -123,7 +123,7 @@ setting the
The
.Nm da
device driver will take full advantage of the SCSI feature known as tagged
queuing. Tagged queuing allows the device to process multiple transaction
queuing. Tagged queuing allows the device to process multiple transactions
concurrently, often re-ordering them to reduce the number and length of
seeks. To ensure that transactions to distant portions of the media,
which may be deferred indefinitely by servicing requests nearer the current
@ -132,10 +132,10 @@ transaction is sent every 15 seconds during continuous device operation.
.Sh BAD BLOCK RECOVERY
Direct Access devices have the capability of mapping out portions of
defective media. Media recovery parameters are located in mode page 1,
the Read-Write Error Recovery mode page. The most imporatant media
the Read-Write Error Recovery mode page. The most important media
remapping features are 'Auto Write Reallocation' and 'Auto Read
Reallocation' which can be enabled via the AWRE and ARRE bits,
respecitvely, of the Read-Write Error Recovery page.
respectively, of the Read-Write Error Recovery page.
Many devices do not ship from the factory with these feature enabled.
Mode pages can be examined and modified
via the
@ -164,7 +164,7 @@ drives incorporate their own bad-block mapping so this command is not
implemented.
.It Dv DIOCGDINFO
Read, from the kernel, the in-core copy of the disklabel for the
drive. This may be a ficticious disklabel if the drive has never
drive. This may be a fictitious disklabel if the drive has never
been initialized, in which case it will contain information read
from the
.Tn SCSI
@ -183,9 +183,9 @@ Give the driver a new disklabel to use. The driver
write the new disklabel to the disk.
.El
.Sh NOTES
If device becomes invalidated (media is removed, device becomes unresponsive)
If a device becomes invalidated (media is removed, device becomes unresponsive)
the disklabel and information held within the kernel about the device will
be invalided. To avoid corruption of a newly inserted piece of media or
be invalidated. To avoid corruption of a newly inserted piece of media or
a replacement device, all accesses to the device will be discarded until
the last file descriptor referencing the old device is closed. During this
period, all new open attempts will be rejected.