Index: head/sbin/fdisk/fdisk.8 =================================================================== --- head/sbin/fdisk/fdisk.8 (revision 120997) +++ head/sbin/fdisk/fdisk.8 (revision 120998) @@ -1,457 +1,457 @@ .\" $FreeBSD$ .\" .Dd April 18, 2002 .Dt FDISK 8 .Os .Sh NAME .Nm fdisk .Nd PC slice table maintenance utility .Sh SYNOPSIS .Nm .Op Fl BIaistu .Op Fl b Ar bootcode .Op Fl 1234 .Op Ar disk .Nm .Fl f Ar configfile .Op Fl itv .Op Ar disk .Sh PROLOGUE In order for the BIOS to boot the kernel, certain conventions must be adhered to. Sector 0 of the disk must contain boot code, a slice table, and a magic number. BIOS slices can be used to break the disk up into several pieces. The BIOS brings in sector 0 and verifies the magic number. The sector 0 boot code then searches the slice table to determine which slice is marked .Dq active . This boot code then brings in the bootstrap from the active slice and, if marked bootable, runs it. Under .Tn DOS , you can have one or more slices with one active. The .Tn DOS .Nm utility can be used to divide space on the disk into slices and set one active. .Sh DESCRIPTION The .Fx utility, .Nm , serves a similar purpose to the .Tn DOS utility. The first form is used to display slice information or to interactively edit the slice table. The second is used to write a slice table using a .Ar configfile , and is designed to be used by other scripts/programs. .Pp Options are: .Bl -tag -width indent .It Fl a Change the active slice only. Ignored if .Fl f is given. .It Fl b Ar bootcode Get the boot code from the file .Ar bootcode . Default is .Pa /boot/mbr . .It Fl B Reinitialize the boot code contained in sector 0 of the disk. Ignored if .Fl f is given. .It Fl f Ar configfile Set slice values using the file .Ar configfile . The .Ar configfile always modifies existing slices, unless .Fl i is also given, in which case all existing slices are deleted (marked as .Dq unused ) before the .Ar configfile is read. The .Ar configfile can be .Sq Fl , in which case standard input is read. See .Sx CONFIGURATION FILE , below, for file syntax. .Pp .Em WARNING : when .Fl f is used, you are not asked if you really want to write the slices table (as you are in the interactive mode). Use with caution! .It Fl i Initialize sector 0 of the disk. This implies .Fl u , unless .Fl f is given. .It Fl I Initialize the contents of sector 0 for one .Fx slice covering the entire disk. .It Fl s Print summary information and exit. .It Fl t Test mode; do not write slice values. Generally used with the .Fl f option to see what would be written to the slice table. Implies .Fl v . .It Fl u Is used for updating (editing) sector 0 of the disk. Ignored if .Fl f is given. .It Fl v Be verbose. When .Fl f is used, .Nm prints out the slice table that is written to the disk. .It Fl 1234 Operate on a single slice table entry only. Ignored if .Fl f is given. .El .Pp The final disk name can be provided as a .Dq bare disk name only, e.g.\& .Pa da0 , or as a full pathname. If omitted, .Nm tries to figure out the default disk device name from the mounted root device. .Pp When called with no arguments, it prints the sector 0 slice table. An example follows: .Bd -literal ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=769 heads=15 sectors/track=33 (495 blks/cyl) parameters to be used for BIOS calculations are: cylinders=769 heads=15 sectors/track=33 (495 blks/cyl) Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 495, size 380160 (185 Meg), flag 0 beg: cyl 1/ sector 1/ head 0; end: cyl 768/ sector 33/ head 14 The data for partition 2 is: sysid 164,(unknown) start 378180, size 2475 (1 Meg), flag 0 beg: cyl 764/ sector 1/ head 0; end: cyl 768/ sector 33/ head 14 The data for partition 3 is: The data for partition 4 is: sysid 99,(ISC UNIX, other System V/386, GNU HURD or Mach) start 380656, size 224234 (109 Meg), flag 80 beg: cyl 769/ sector 2/ head 0; end: cyl 197/ sector 33/ head 14 .Ed .Pp The disk is divided into three slices that happen to fill the disk. The second slice overlaps the end of the first. (Used for debugging purposes.) .Bl -tag -width ".Em cyl , sector No and Em head" .It Em sysid is used to label the slice. .Fx reserves the magic number 165 decimal (A5 in hex). .It Xo .Em start and .Em size .Xc fields provide the start address and size of a slice in sectors. .It Em "flag 80" specifies that this is the active slice. .It Xo .Em cyl , sector and .Em head .Xc fields are used to specify the beginning and end addresses of the slice. .El .Pp .Em Note : these numbers are calculated using BIOS's understanding of the disk geometry and saved in the bootblock. .Pp The .Fl i and .Fl u flags are used to indicate that the slice data is to be updated. Unless the .Fl f option is also given, .Nm will enter a conversational mode. In this mode, no changes will be written to disk unless you explicitly tell .Nm to. .Pp The .Nm utility will display each slice and ask whether you want to edit it. If you say yes, .Nm will step through each field, show you the old value, and ask you for a new one. When you are done with the slice, .Nm will display it and ask you whether it is correct. It will then proceed to the next entry. .Pp Getting the .Em cyl , sector , and .Em head fields correct is tricky, so by default, they will be calculated for you; you can specify them if you choose to though. .Pp After all the slices are processed, you are given the option to change the .Dq active slice. Finally, when all the new data for sector 0 has been accumulated, you are asked to confirm whether you really want to rewrite it. .Pp The difference between the .Fl u and .Fl i flags is that the .Fl u flag just edits (updates) the fields as they appear on the disk, while the .Fl i flag is used to .Dq initialize sector 0; it will set up the last BIOS slice to use the whole disk for .Fx and make it active. .Sh NOTES The automatic calculation of starting cylinder etc. uses a set of figures that represent what the BIOS thinks the geometry of the drive is. These figures are taken from the in-core disklabel by default, but .Nm initially gives you an opportunity to change them. This allows you to create a bootblock that can work with drives that use geometry translation under the BIOS. .Pp If you hand craft your disk layout, please make sure that the .Fx slice starts on a cylinder boundary. A number of decisions made later may assume this. (This might not be necessary later.) .Pp Editing an existing slice will most likely result in the loss of all data in that slice. .Pp You should run .Nm interactively once or twice to see how it works. This is completely safe as long as you answer the last question in the negative. There are subtleties that .Nm detects that are not fully explained in this manual page. .Sh CONFIGURATION FILE When the .Fl f option is given, a disk's slice table can be written using values from a .Ar configfile . The syntax of this file is very simple; each line is either a comment or a specification, as follows: .Bl -tag -width indent .It Ic # Ar comment ... Lines beginning with a .Ic # are comments and are ignored. .It Ic g Ar spec1 spec2 spec3 Set the BIOS geometry used in slice calculations. There must be three values specified, with a letter preceding each number: .Bl -tag -width indent .It Cm c Ns Ar num Set the number of cylinders to .Ar num . .It Cm h Ns Ar num Set the number of heads to .Ar num . .It Cm s Ns Ar num Set the number of sectors/track to .Ar num . .El .Pp These specs can occur in any order, as the leading letter determines which value is which; however, all three must be specified. .Pp This line must occur before any lines that specify slice information. .Pp It is an error if the following is not true: .Bd -literal -offset indent 1 <= number of cylinders 1 <= number of heads <= 256 1 <= number of sectors/track < 64 .Ed .Pp The number of cylinders should be less than or equal to 1024, but this is not enforced, although a warning will be printed. Note that bootable .Fx slices (the .Dq Pa / file system) must lie completely within the first 1024 cylinders; if this is not true, booting may fail. Non-bootable slices do not have this restriction. .Pp Example (all of these are equivalent), for a disk with 1019 cylinders, 39 heads, and 63 sectors: .Bd -literal -offset indent g c1019 h39 s63 g h39 c1019 s63 g s63 h39 c1019 .Ed .It Ic p Ar slice type start length Set the slice given by .Ar slice (1-4) to type .Ar type , starting at sector .Ar start for .Ar length sectors. .Pp Only those slices explicitly mentioned by these lines are modified; any slice not referenced by a .Ic p line will not be modified. However, if an invalid slice table is present, or the .Fl i option is specified, all existing slice entries will be cleared (marked as unused), and these .Ic p lines will have to be used to explicitly set slice information. If multiple slices need to be set, multiple .Ic p lines must be specified; one for each slice. .Pp These slice lines must occur after any geometry specification lines, if one is present. .Pp The .Ar type is 165 for .Fx slices. Specifying a slice type of zero is the same as clearing the slice and marking it as unused; however, dummy values (such as .Dq 0 ) must still be specified for .Ar start and .Ar length . .Pp Note: the start offset will be rounded upwards to a head boundary if necessary, and the end offset will be rounded downwards to a cylinder boundary if necessary. .Pp Example: to clear slice 4 and mark it as unused: .Pp .Dl "p 4 0 0 0" .Pp Example: to set slice 1 to a .Fx slice, starting at sector 1 for 2503871 sectors (note: these numbers will be rounded upwards and downwards to correspond to head and cylinder boundaries): .Pp .Dl "p 1 165 1 2503871" .Pp .It Ic a Ar slice Make .Ar slice the active slice. Can occur anywhere in the config file, but only one must be present. .Pp Example: to make slice 1 the active slice: .Pp .Dl "a 1" .El .Sh FILES .Bl -tag -width ".Pa /boot/mbr" -compact .It Pa /boot/mbr The default boot code. .El .Sh SEE ALSO .Xr boot0cfg 8 , -.Xr disklabel 8 , +.Xr bsdlabel 8 , .Xr newfs 8 .Sh BUGS The default boot code will not necessarily handle all slice types correctly, in particular those introduced since .Tn MS-DOS 6.x. .Pp The entire utility should be made more user-friendly. .Pp Most users new to .Fx do not understand the difference between .Dq slice and .Dq partition , causing difficulty to adjust. .Pp You cannot use this command to completely dedicate a disk to .Fx . The -.Xr disklabel 8 +.Xr bsdlabel 8 command must be used for this. Index: head/sbin/mdconfig/mdconfig.8 =================================================================== --- head/sbin/mdconfig/mdconfig.8 (revision 120997) +++ head/sbin/mdconfig/mdconfig.8 (revision 120998) @@ -1,207 +1,207 @@ .\" Copyright (c) 1993 University of Utah. .\" Copyright (c) 1980, 1989, 1991, 1993 .\" The Regents of the University of California. All rights reserved. .\" Copyright (c) 2000 .\" Poul-Henning Kamp All rights reserved. .\" .\" This code is derived from software contributed to Berkeley by .\" the Systems Programming Group of the University of Utah Computer .\" Science Department. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 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. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by the University of .\" California, Berkeley and its contributors. .\" 4. Neither the name of the University nor the names of its contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS 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 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" 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. .\" .\" @(#)vnconfig.8 8.1 (Berkeley) 6/5/93 .\" from: src/usr.sbin/vnconfig/vnconfig.8,v 1.19 2000/12/27 15:30:29 .\" .\" $FreeBSD$ .\" .Dd December 31, 2000 .Dt MDCONFIG 8 .Os .Sh NAME .Nm mdconfig .Nd configure and enable memory disks .Sh SYNOPSIS .Nm .Fl a .Fl t Ar type .Op Fl n .Oo .Fl o .Oo Cm no Oc Ns Ar option .Oc .Op Fl s Ar size .Op Fl f Ar file .Op Fl S Ar sectorsize .Op Fl u Ar unit .Op Fl x Ar sectors/track .Op Fl y Ar heads/cyl .Nm .Fl d .Fl u Ar unit .Nm .Fl l .Op Fl n .Op Fl u Ar unit .Sh DESCRIPTION The .Nm utility configures and enables .Xr md 4 devices. .Pp Options indicate an action to be performed: .Bl -tag -width indent .It Fl a Attach a memory disk. This will configure and attach a memory disk with the parameters specified and attach it to the system. .It Fl d Detach a memory disk from the system and release all resources. .It Fl t Ar type Select the type of the memory disk. .Bl -tag -width "preload" .It Cm malloc Storage for this type of memory disk is allocated with .Xr malloc 9 . This limits the size to the malloc bucket limit in the kernel. .It Cm vnode A file specified with .Fl f Ar file becomes the backingstore for this memory disk. .It Cm swap swapspace is used to back this memory disk. .El .It Fl f Ar file Filename to use for the vnode type memory disk. .It Fl l List information about configured .Xr md 4 devices. If the .Fl u option is used in conjuction with this, the output is limited to information on the specified device. .It Fl n When printing md device names, print only the unit number without the md prefix. .It Fl s Ar size Size of the memory disk. .Ar Size is the number of 512 bytes sectors unless suffixed with a .Cm k , m , or .Cm g which denotes kilobyte, megabyte and gigabyte respectively. .It Fl S Ar sectorsize Sectorsize to use for malloc backed device. .It Fl x Ar sectors/track See description of .Fl y below. .It Fl y Ar heads/cylinder For malloc backed devices, the .Fl x and .Fl y options can be used to specify a synthetic geometry. This is useful for constructing bootable images for later download to other devices. .It Fl o Oo Cm no Oc Ns Ar option Set or reset options. .Bl -tag -width indent .It Oo Cm no Oc Ns Cm reserve Allocate and reserve all needed storage from the start, rather than as needed. .It Oo Cm no Oc Ns Cm cluster Enable clustering on this disk. .It Oo Cm no Oc Ns Cm compress Enable/Disable compression features to reduce memory usage. .It Oo Cm no Oc Ns Cm force Disable/Enable extra sanity checks to prevent the user from doing something that might adversely affect the system. .It Oo Cm no Oc Ns Cm readonly Enable/Disable readonly mode. .El .It Fl u Ar unit Request a specific unit number for the .Xr md 4 device instead of automatic allocation. .El .Sh EXAMPLES To create a 4 megabyte .Xr malloc 9 backed memory disk. The name of the allocated unit will be output on stdout like .Dq Li md3 : .Pp .Dl mdconfig -a -t malloc -s 4m .Pp To create a disk named .Pa /dev/md4 with .Pa /tmp/boot.flp as backing: .Pp .Dl mdconfig -a -t vnode -f /tmp/boot.flp -u 4 .Pp To detach and free all resources used by .Pa /dev/md4 : .Pp .Dl mdconfig -d -u 4 .Pp To create and mount a 128MByte swap backed file system on .Pa /tmp : .Bd -literal -offset indent mdconfig -a -t swap -s 128M -u 10 newfs -U /dev/md10 mount /dev/md10 /tmp chmod 1777 /tmp .Ed .Sh SEE ALSO .Xr md 4 , -.Xr disklabel 8 , +.Xr bsdlabel 8 , .Xr fdisk 8 , .Xr mdmfs 8 , .Xr malloc 9 .Sh HISTORY The .Nm utility first appeared in .Fx 5.0 as a cleaner replacement for the .Xr vn 4 and .Xr vnconfig 8 combo. .Sh AUTHORS The .Nm utility was written by .An Poul-Henning Kamp .Aq phk@FreeBSD.org . Index: head/sbin/newfs/newfs.8 =================================================================== --- head/sbin/newfs/newfs.8 (revision 120997) +++ head/sbin/newfs/newfs.8 (revision 120998) @@ -1,245 +1,245 @@ .\" Copyright (c) 1983, 1987, 1991, 1993, 1994 .\" The Regents of the University of California. All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 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. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by the University of .\" California, Berkeley and its contributors. .\" 4. Neither the name of the University nor the names of its contributors .\" may be used to endorse or promote products derived from this software .\" without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS 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 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" 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. .\" .\" @(#)newfs.8 8.6 (Berkeley) 5/3/95 .\" $FreeBSD$ .\" .Dd May 18, 2002 .Dt NEWFS 8 .Os .Sh NAME .Nm newfs .Nd construct a new UFS1/UFS2 file system .Sh SYNOPSIS .Nm .Op Fl NU .Op Fl L Ar volname .Op Fl O Ar filesystem-type .Op Fl S Ar sector-size .Op Fl T Ar disktype .Op Fl a Ar maxcontig .Op Fl b Ar block-size .Op Fl c Ar blocks-per-cylinder-group .Op Fl d Ar max-extent-size .Op Fl e Ar maxbpg .Op Fl f Ar frag-size .Op Fl g Ar avgfilesize .Op Fl h Ar avgfpdir .Op Fl i Ar bytes .Op Fl m Ar free-space .Op Fl o Ar optimization .Op Fl s Ar size .Ar special .Sh DESCRIPTION The .Nm utility is used to initialize and clear file systems before first use. Before running .Nm the disk must be labeled using -.Xr disklabel 8 . +.Xr bsdlabel 8 . The .Nm utility builds a file system on the specified special file. (We often refer to the .Dq special file as the .Dq disk , although the special file need not be a physical disk. In fact, it need not even be special.) Typically the defaults are reasonable, however .Nm has numerous options to allow the defaults to be selectively overridden. .Pp The following options define the general layout policies: .Bl -tag -width indent .It Fl L Ar volname Add a volume label to the new file system. .It Fl N Cause the file system parameters to be printed out without really creating the file system. .It Fl O Ar filesystem-type Use 1 to specify that a UFS1 format file system be built; use 2 to specify that a UFS2 format file system be built. The default format is UFS2. .It Fl T Ar disktype For backward compatibility. .It Fl U Enables soft updates on the new file system. .It Fl a Ar maxcontig Specify the maximum number of contiguous blocks that will be laid out before forcing a rotational delay. The default value is 16. See .Xr tunefs 8 for more details on how to set this option. .It Fl b Ar block-size The block size of the file system, in bytes. It must be a power of 2. The default size is 16384 bytes, and the smallest allowable size is 4096 bytes. The optimal block:fragment ratio is 8:1. Other ratios are possible, but are not recommended, and may produce poor results. .It Fl c Ar blocks-per-cylinder-group The number of blocks per cylinder group in a file system. The default is to compute the maximum allowed by the other parameters. This value is dependent on a number of other parameters, in particular the block size and the number of bytes per inode. .It Fl d Ar max-extent-size The file system may choose to store large files using extents. This parameter specifies the largest extent size that may be used. It is presently limited to its default value which is 16 times the file system blocksize. .It Fl e Ar maxbpg Indicate the maximum number of blocks any single file can allocate out of a cylinder group before it is forced to begin allocating blocks from another cylinder group. The default is about one quarter of the total blocks in a cylinder group. See .Xr tunefs 8 for more details on how to set this option. .It Fl f Ar frag-size The fragment size of the file system in bytes. It must be a power of two ranging in value between .Ar blocksize Ns /8 and .Ar blocksize . The default is 2048 bytes. .It Fl g Ar avgfilesize The expected average file size for the file system. .It Fl h Ar avgfpdir The expected average number of files per directory on the file system. .It Fl i Ar bytes Specify the density of inodes in the file system. The default is to create an inode for every .Pq 4 * Ar frag-size bytes of data space. If fewer inodes are desired, a larger number should be used; to create more inodes a smaller number should be given. One inode is required for each distinct file, so this value effectively specifies the average file size on the file system. .It Fl m Ar free-space The percentage of space reserved from normal users; the minimum free space threshold. The default value used is defined by .Dv MINFREE from .In ufs/ffs/fs.h , currently 8%. See .Xr tunefs 8 for more details on how to set this option. .It Fl o Ar optimization .Cm ( space or .Cm time ) . The file system can either be instructed to try to minimize the time spent allocating blocks, or to try to minimize the space fragmentation on the disk. If the value of minfree (see above) is less than 8%, the default is to optimize for .Cm space ; if the value of minfree is greater than or equal to 8%, the default is to optimize for .Cm time . See .Xr tunefs 8 for more details on how to set this option. .It Fl s Ar size The size of the file system in sectors. This value defaults to the size of the raw partition specified in .Ar special (in other words, .Nm will use the entire partition for the file system). .El .Pp The following options override the standard sizes for the disk geometry. Their default values are taken from the disk label. Changing these defaults is useful only when using .Nm to build a file system whose raw image will eventually be used on a different type of disk than the one on which it is initially created (for example on a write-once disk). Note that changing any of these values from their defaults will make it impossible for .Xr fsck 8 to find the alternate superblocks if the standard superblock is lost. .Bl -tag -width indent .It Fl S Ar sector-size The size of a sector in bytes (almost never anything but 512). .El .Sh EXAMPLES .Dl newfs /dev/ad3s1a .Pp Creates a new ufs file system on .Pa ad3s1a . The .Nm utility will use a block size of 16384 bytes, a fragment size of 2048 bytes and the largest possible number of blocks per cylinders group. These values tend to produce better performance for most applications than the historical defaults (8192 byte block size and 1024 byte fragment size). This large fragment size may lead to much wasted space on file systems that contain many small files. .Sh SEE ALSO .Xr fdformat 1 , .Xr disktab 5 , .Xr fs 5 , .Xr camcontrol 8 , -.Xr disklabel 8 , +.Xr bsdlabel 8 , .Xr dumpfs 8 , .Xr fsck 8 , .Xr mount 8 , .Xr tunefs 8 , .Xr vinum 8 .Rs .%A M. McKusick .%A W. Joy .%A S. Leffler .%A R. Fabry .%T A Fast File System for UNIX .%J ACM Transactions on Computer Systems 2 .%V 3 .%P pp 181-197 .%D August 1984 .%O (reprinted in the BSD System Manager's Manual) .Re .Sh HISTORY The .Nm utility appeared in .Bx 4.2 . Index: head/share/man/man4/vpo.4 =================================================================== --- head/share/man/man4/vpo.4 (revision 120997) +++ head/share/man/man4/vpo.4 (revision 120998) @@ -1,96 +1,96 @@ .\" Copyright (c) 1998, 1999, Nicolas Souchu .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 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 AUTHOR 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 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" 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 March 5, 1998 .Dt VPO 4 .Os .Sh NAME .Nm vpo .Nd parallel to SCSI interface driver .Sh SYNOPSIS .Cd "device vpo" .Pp For one or more SCSI busses: .Cd "device scbus" .Sh DESCRIPTION The primary purpose of the .Em vpo driver is to provide access to the Adaptec AIC-7110 SCSI controller built in the Iomega ZIP drive. But it should also work with the Iomega Jaz Traveller parallel to SCSI interface. .Pp The driver has been extended to the ZIP+ drive which is based on the Iomega Matchmaker Parallel to SCSI interface. .Sh USAGE The driver should let you use a printer connected to the drive while transferring data. .Pp DOS and .Fx file systems are supported. When mounting a DOS file system or formating a .Fx file system, check the slice of the disk with the .Xr fdisk 8 utility. .Pp In order to unixify a ZIP disk, put the following in /etc/disktab: .Bd -literal zip|zip 100:\\ :ty=removable:se#512:nc#96:nt#64:ns#32:\\ :pa#196608:oa#0:ba#4096:fa#512:\\ :pb#196608:ob#0:bb#4096:fb#512:\\ :pc#196608:oc#0:bc#4096:fc#512: .Ed .Pp and use -.Xr disklabel 8 . +.Xr bsdlabel 8 . .Pp If you have trouble with your driver, your parallel chipset may not run properly at the detected mode (NIBBLE, PS2 or EPP). Tune the .Xr ppc 4 bootflags to force other modes. .Sh SEE ALSO .Xr da 4 , .Xr lpt 4 , .Xr ppbus 4 , .Xr ppc 4 , .Xr scsi 4 .Sh BUGS During boot, the driver firstly try to detect a classic ZIP, then a ZIP+. The ZIP+ detection is intrusive and may send erroneous characters to your printer if the drive is not connected to your parallel port. .Sh HISTORY The .Nm manual page first appeared in .Fx 3.0 . .Sh AUTHORS This manual page was written by .An Nicolas Souchu .