Attachment 2940 Details for Bug 8472 – file.diff

[patch] file.diff

file.diff (text/plain), 5.65 KB, created by Craig Leres on 1998-10-28 02:30:00 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Craig Leres

Created: 1998-10-28 02:30:00 UTC

Size: 5.65 KB

patch

obsolete

>*** da.4.virgin	Tue Oct 27 18:14:11 1998
>--- da.4	Tue Oct 27 18:21:01 1998
>***************
>*** 54,60 ****
>  .Tn SCSI
>  direct access device can be configured.
>  .Sh PARTITIONING
>! The 
>  .Nm
>  driver allows the disk to have two levels of partitioning.
>  One layer, called the
>--- 54,60 ----
>  .Tn SCSI
>  direct access device can be configured.
>  .Sh PARTITIONING
>! The
>  .Nm
>  driver allows the disk to have two levels of partitioning.
>  One layer, called the
>***************
>*** 76,82 ****
>  respectively.
>  .Pp
>  If an uninitialized disk is opened, the slice table will be
>! initialized with a ficticious
>  .Tn FreeBSD
>  slice spanning the entire disk.  Similarly, if an uninitialized
>  (or
>--- 76,82 ----
>  respectively.
>  .Pp
>  If an uninitialized disk is opened, the slice table will be
>! initialized with a fictious
>  .Tn FreeBSD
>  slice spanning the entire disk.  Similarly, if an uninitialized
>  (or
>***************
>*** 89,100 ****
>  Many direct access devices are equiped 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
>! 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
>  can be disabled by setting the
>--- 89,100 ----
>  Many direct access devices are equiped 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
>! operations as well as frequently used data.  The read cache is transparent
>  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
>  can be disabled by setting the
>***************
>*** 115,121 ****
>  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
>  setting the
>  .Tn WCE
>  (Write Cache Enable) bit in the caching control mode page.
>--- 115,121 ----
>  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 enabled by
>  setting the
>  .Tn WCE
>  (Write Cache Enable) bit in the caching control mode page.
>***************
>*** 132,144 ****
>  .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
>  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.
>  Many devices do not ship from the factory with these feature enabled.
>! Mode pages can be examined and modified 
>! via the 
>  .Xr camcontrol 8
>  utility.
>  .Sh KERNEL CONFIGURATION
>--- 132,144 ----
>  .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 important media
>  remapping features are 'Auto Write Reallocation' and 'Auto Read
>  Reallocation' which can be enabled via the AWRE and ARRE bits,
>! 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
>  .Xr camcontrol 8
>  utility.
>  .Sh KERNEL CONFIGURATION
>***************
>*** 149,170 ****
>  .Tn SCSI
>  bus.
>  .Sh IOCTLS
>! The following 
>  .Xr ioctl 2
>! calls apply to 
>  .Tn SCSI
>  disks as well as to other disks.  They are defined in the header file
>  .Aq Pa sys/disklabel.h .
>  .Pp
>  .Bl -tag -width DIOCSDINFO
>  .It Dv DIOCSBAD
>! Usually used to set up a bad-block mapping system on the disk. 
>  .Tn SCSI
>  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
>  been initialized, in which case it will contain information read
>  from the
>  .Tn SCSI
>--- 149,170 ----
>  .Tn SCSI
>  bus.
>  .Sh IOCTLS
>! The following
>  .Xr ioctl 2
>! calls apply to
>  .Tn SCSI
>  disks as well as to other disks.  They are defined in the header file
>  .Aq Pa sys/disklabel.h .
>  .Pp
>  .Bl -tag -width DIOCSDINFO
>  .It Dv DIOCSBAD
>! Usually used to set up a bad-block mapping system on the disk.
>  .Tn SCSI
>  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 fictious disklabel if the drive has never
>  been initialized, in which case it will contain information read
>  from the
>  .Tn SCSI
>***************
>*** 273,280 ****
>  .Xr wd 4 ,
>  .Xr disklabel 5 ,
>  .Xr disklabel 8 ,
>! .Xr fdisk 8 ,
>! .Xr da 9
>  .Sh HISTORY
>  The
>  .Nm
>--- 273,279 ----
>  .Xr wd 4 ,
>  .Xr disklabel 5 ,
>  .Xr disklabel 8 ,
>! .Xr fdisk 8
>  .Sh HISTORY
>  The
>  .Nm

Actions: View | Diff

Attachments on bug 8472: 2940