From a145482cf625d5f04072fd1d20b5c2062cbe8e47 Mon Sep 17 00:00:00 2001 From: dd Date: Sun, 15 Jul 2001 07:53:42 +0000 Subject: Remove whitespace at EOL. --- sbin/atm/atm/atm.8 | 2 +- sbin/badsect/badsect.8 | 8 ++--- sbin/bsdlabel/bsdlabel.5 | 8 ++--- sbin/bsdlabel/bsdlabel.8 | 66 +++++++++++++++++++------------------- sbin/camcontrol/camcontrol.8 | 12 +++---- sbin/ccdconfig/ccdconfig.8 | 8 ++--- sbin/cxconfig/cxconfig.8 | 18 +++++------ sbin/disklabel/disklabel.5 | 8 ++--- sbin/disklabel/disklabel.8 | 66 +++++++++++++++++++------------------- sbin/dump/dump.8 | 2 +- sbin/dumpon/dumpon.8 | 12 +++---- sbin/fdisk/fdisk.8 | 2 +- sbin/fdisk_pc98/fdisk.8 | 4 +-- sbin/ffsinfo/ffsinfo.8 | 10 +++--- sbin/fsck/fsck.8 | 10 +++--- sbin/fsck_ffs/fsck_ffs.8 | 22 ++++++------- sbin/fsck_ifs/fsck_ifs.8 | 24 +++++++------- sbin/fsdb/fsdb.8 | 16 ++++----- sbin/growfs/growfs.8 | 36 ++++++++++----------- sbin/i386/cxconfig/cxconfig.8 | 18 +++++------ sbin/i386/fdisk/fdisk.8 | 2 +- sbin/i386/nextboot/nextboot.8 | 20 ++++++------ sbin/init/init.8 | 22 ++++++------- sbin/kget/kget.8 | 2 +- sbin/md5/md5.1 | 2 +- sbin/mdconfig/mdconfig.8 | 10 +++--- sbin/mknod/mknod.8 | 2 +- sbin/mount_nfs/mount_nfs.8 | 2 +- sbin/mount_ntfs/mount_ntfs.8 | 4 +-- sbin/mount_nullfs/mount_nullfs.8 | 32 +++++++++--------- sbin/mount_nwfs/mount_nwfs.8 | 30 ++++++++--------- sbin/mount_std/mount_std.8 | 12 +++---- sbin/mount_umapfs/mount_umapfs.8 | 34 ++++++++++---------- sbin/mount_unionfs/mount_unionfs.8 | 2 +- sbin/mountd/netgroup.5 | 4 +-- sbin/newfs/newfs.8 | 14 ++++---- sbin/nextboot/nextboot.8 | 20 ++++++------ sbin/nfsd/nfsd.8 | 4 +-- sbin/nologin/nologin.5 | 8 ++--- sbin/nologin/nologin.8 | 2 +- sbin/nos-tun/nos-tun.8 | 6 ++-- sbin/pc98/fdisk/fdisk.8 | 4 +-- sbin/ping/ping.8 | 14 ++++---- sbin/quotacheck/quotacheck.8 | 14 ++++---- sbin/reboot/boot_i386.8 | 26 +++++++-------- sbin/reboot/reboot.8 | 8 ++--- sbin/restore/restore.8 | 26 +++++++-------- sbin/route/route.8 | 28 ++++++++-------- sbin/slattach/slattach.8 | 6 ++-- 49 files changed, 356 insertions(+), 356 deletions(-) (limited to 'sbin') diff --git a/sbin/atm/atm/atm.8 b/sbin/atm/atm/atm.8 index 6776405..3988daa 100644 --- a/sbin/atm/atm/atm.8 +++ b/sbin/atm/atm/atm.8 @@ -103,7 +103,7 @@ IP management subcommands: [] .ti -5 .B atm set arpserver - | local [ ...] + | local [ ...] .ti -5 .B atm show ARP [] diff --git a/sbin/badsect/badsect.8 b/sbin/badsect/badsect.8 index 5aa4b01..7ac3e72 100644 --- a/sbin/badsect/badsect.8 +++ b/sbin/badsect/badsect.8 @@ -63,7 +63,7 @@ currently requires the running of the standard formatter. Thus to deal with a newly bad block or on disks where the drivers -do not support the bad-blocking standard +do not support the bad-blocking standard .Nm may be used to good effect. .Pp @@ -88,7 +88,7 @@ and run on the file system. The bad sectors should show up in two files or in the bad sector files and the free list. Have .Xr fsck -remove files containing the offending bad sectors, but +remove files containing the offending bad sectors, but .Em do not have it remove the .Pa BAD/ Ns Em nnnnn @@ -103,11 +103,11 @@ works by giving the specified sector numbers in a system call, creating an illegal file whose first block address is the block containing bad sector and whose name is the bad sector number. -When it is discovered by +When it is discovered by .Xr fsck 8 it will ask .Dq Li "HOLD BAD BLOCK \&?" . -A positive response will cause +A positive response will cause .Xr fsck 8 to convert the inode to a regular file containing the bad block. .Sh SEE ALSO diff --git a/sbin/bsdlabel/bsdlabel.5 b/sbin/bsdlabel/bsdlabel.5 index fcd4b0d..efd31df 100644 --- a/sbin/bsdlabel/bsdlabel.5 +++ b/sbin/bsdlabel/bsdlabel.5 @@ -84,7 +84,7 @@ A copy of the in-core label for a disk can be obtained with the .Xr ioctl 2 ; this works with a file descriptor for a block or character (``raw'') device for any partition of the disk. -The in-core copy of the label is set by the +The in-core copy of the label is set by the .Dv DIOCSDINFO .Xr ioctl 2 . The offset of a partition cannot generally be changed while it is open, @@ -92,7 +92,7 @@ nor can it be made smaller while it is open. One exception is that any change is allowed if no label was found on the disk, and the driver was able to construct only a skeletal label without partition information. -Finally, the +Finally, the .Dv DIOCWDINFO .Xr ioctl 2 operation sets the in-core label and then updates the on-disk label; @@ -162,7 +162,7 @@ struct disklabel { u_int16_t d_subtype; /* controller/d_type specific */ char d_typename[16]; /* type name, e.g. "eagle" */ - /* + /* * d_packname contains the pack identifier and is returned when * the disklabel is read off the disk or in-core copy. * d_boot0 and d_boot1 are the (optional) names of the @@ -412,7 +412,7 @@ struct dos_partition { unsigned char dp_mid; #define DOSMID_386BSD (0x14|0x80) /* 386bsd|bootable */ unsigned char dp_sid; -#define DOSSID_386BSD (0x44|0x80) /* 386bsd|active */ +#define DOSSID_386BSD (0x44|0x80) /* 386bsd|active */ unsigned char dp_dum1; unsigned char dp_dum2; unsigned char dp_ipl_sct; diff --git a/sbin/bsdlabel/bsdlabel.8 b/sbin/bsdlabel/bsdlabel.8 index 8c7e69d..8432686 100644 --- a/sbin/bsdlabel/bsdlabel.8 +++ b/sbin/bsdlabel/bsdlabel.8 @@ -118,7 +118,7 @@ is described under each command. .Pp .Ss Disk device name .Pp -All +All .Nm forms require a disk device name, which should always be the raw device name representing the disk or slice. For example @@ -142,7 +142,7 @@ will automatically prepend it. .Ss Reading the disk label .Pp To examine or save the label on a disk drive, use -.Nm +.Nm without options: .Pp .Nm @@ -163,7 +163,7 @@ if the disk has no label, or the partition types on the disk are incorrect, the kernel may have constructed or modified the label. If the .Fl r -flag is given, +flag is given, .Nm reads the label from the raw disk and displays it. Both versions are usually identical except in the case where a label has not yet been initialized or @@ -355,7 +355,7 @@ You should never use this command on a base disk unless you intend to create a .Dq dangerously-dedicated disk, such as .Ar da0 . -This command is typically run on a slice such as +This command is typically run on a slice such as .Ar da0s1 . .Pp .Nm @@ -371,7 +371,7 @@ This command is typically run on a slice such as .Pp This form corresponds to the .Dq write label -command described above. +command described above. In addition to writing a new volume label, it also installs the bootstrap. If run on a base disk this command will create a .Dq dangerously-dedicated @@ -394,7 +394,7 @@ disklabel that would have been written will be printed to stdout. .Pp This form corresponds to the .Dq restore label -command described above. +command described above. In addition to restoring the volume label, it also installs the bootstrap. If run on a base disk this command will create a .Dq dangerously-dedicated @@ -416,7 +416,7 @@ Specify the names explicitly with the .Fl b and .Fl s -flags. +flags. .Fl b indicates the primary boot program and .Fl s @@ -427,11 +427,11 @@ If the .Fl b and .Fl s -flags are not specified, but +flags are not specified, but .Ar disktype -was specified, the names of the programs are taken from the +was specified, the names of the programs are taken from the .Dq b0 -and +and .Dq b1 parameters of the .Xr disktab 5 @@ -475,7 +475,7 @@ to edit your newly created label, adding appropriate partitions. Finally newfs the filesystem partitions you created in the label. A typical disklabel partitioning scheme would be to have an .Dq a -partition +partition of approximately 128MB to hold the root filesystem, a .Dq b partition for @@ -520,7 +520,7 @@ label. The format is: # /dev/da1c: type: SCSI disk: da0s1 -label: +label: flags: bytes/sector: 512 sectors/track: 51 @@ -534,7 +534,7 @@ trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds -drivedata: 0 +drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] @@ -555,7 +555,7 @@ option when writing a label. .It Nm flags Flags may be .Ar removable , -.Ar ecc +.Ar ecc or .Ar badsect . .Ar removable @@ -564,7 +564,7 @@ is set for removable media drives, but no current driver evaluates this flag. .Ar ecc -is no longer supported; +is no longer supported; .Ar badsect specifies that the drive can perform bad sector remapping. .It Nm sectors/unit @@ -652,7 +652,7 @@ use. See the definitions starting with .Dv FS_UNUSED in -.Pa /usr/include/sys/disklabel.h +.Pa /usr/include/sys/disklabel.h for more details. .It fsize For @@ -679,7 +679,7 @@ cylinder boundary. .Sh EXAMPLES .Dl disklabel da0 .Pp -Display the in-core label for +Display the in-core label for .Pa da0s1 as obtained via .Pa /dev/da0s1 . @@ -693,7 +693,7 @@ label. Normally you specify the slice. .Pp .Dl disklabel da0s1 > savedlabel .Pp -Save the in-core label for +Save the in-core label for .Pa da0s1 into the file .Pa savedlabel . @@ -703,7 +703,7 @@ flag to restore the label at a later date. .Pp .Dl disklabel -w -r /dev/da0s1 da2212 foo .Pp -Create a label for +Create a label for .Pa da0s1 based on information for .Dq da2212 @@ -713,28 +713,28 @@ Any existing bootstrap code will be clobbered. .Pp .Dl disklabel -e -r da0s1 .Pp -Read the on-disk label for +Read the on-disk label for .Pa da0s1 , edit it and reinstall in-core as well as on-disk. Existing bootstrap code is unaffected. .Pp .Dl disklabel -e -r -n da0s1 .Pp -Read the on-disk label for +Read the on-disk label for .Pa da0s1 , edit it, and display what the new label would be (in sectors). It does NOT install the new label either in-core or on-disk. .Pp .Dl disklabel -r -w da0s1 auto .Pp -Try to auto-detect the required information from +Try to auto-detect the required information from .Pa da0s1 , and write a new label to the disk. Use another disklabel -e command to edit the partitioning and file system information. .Pp .Dl disklabel -R da0s1 savedlabel .Pp -Restore the on-disk and in-core label for +Restore the on-disk and in-core label for .Pa da0s1 from information in .Pa savedlabel . @@ -742,7 +742,7 @@ Existing bootstrap code is unaffected. .Pp .Dl disklabel -R -n da0s1 label_layout .Pp -Display what the label would be for +Display what the label would be for .Pa da0s1 using the partition layout in .Pa label_layout . @@ -755,7 +755,7 @@ partition sizes. .Pp .Dl disklabel -B da0s1 .Pp -Install a new bootstrap on +Install a new bootstrap on .Pa da0s1 . The boot code comes from .Pa /boot/boot1 @@ -801,7 +801,7 @@ which could be used as a source file for # /dev/ad0s1c: type: ESDI disk: ad0s1 -label: +label: flags: bytes/sector: 512 sectors/track: 63 @@ -815,16 +815,16 @@ trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds -drivedata: 0 +drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 400M 0 4.2BSD 4096 16384 75 # (Cyl. 0 - 812*) - b: 1G * swap - c: * * unused - e: 204800 * 4.2BSD - f: 5g * 4.2BSD - g: * * 4.2BSD + b: 1G * swap + c: * * unused + e: 204800 * 4.2BSD + f: 5g * 4.2BSD + g: * * 4.2BSD .Ed .Sh SEE ALSO .Xr ccd 4 , @@ -837,7 +837,7 @@ drivedata: 0 The kernel device drivers will not allow the size of a disk partition to be decreased or the offset of a partition to be changed while it is open. Some device drivers create a label containing only a single large partition -if a disk is unlabeled; thus, the label must be written to the +if a disk is unlabeled; thus, the label must be written to the .Dq a partition of the disk while it is open. This sometimes requires the desired label to be set in two steps, the first one creating at least one other diff --git a/sbin/camcontrol/camcontrol.8 b/sbin/camcontrol/camcontrol.8 index 7038d2a..4b537a3 100644 --- a/sbin/camcontrol/camcontrol.8 +++ b/sbin/camcontrol/camcontrol.8 @@ -52,7 +52,7 @@ .Op device id .Op generic args .Nm -.Ic inquiry +.Ic inquiry .Op device id .Op generic args .Op Fl D @@ -377,7 +377,7 @@ that is to be written. If the format is bytes of data will be read from standard input and written to the device. .El .It Ic debug -Turn on CAM debugging printfs in the kernel. This requires options CAMDEBUG +Turn on CAM debugging printfs in the kernel. This requires options CAMDEBUG in your kernel config file. WARNING: enabling debugging printfs currently causes an EXTREME number of kernel printfs. You may have difficulty turning off the debugging printfs once they start, since the kernel will be @@ -607,14 +607,14 @@ variable allows the user to specify an alternate mode page format file. .Pp The .Ev EDITOR -variable determines which text editor +variable determines which text editor .Nm starts when editing mode pages. .Sh FILES .Bl -tag -width /usr/share/misc/scsi_modes -compact .It Pa /usr/share/misc/scsi_modes is the SCSI mode format database. -.It Pa /dev/xpt0 +.It Pa /dev/xpt0 is the transport layer device. .It Pa /dev/pass* are the CAM application passthrough devices. @@ -717,7 +717,7 @@ utility and .Xr scsi 3 library, written by Julian Elischer and Peter Dufault. The .Xr scsi 8 -program first appeared in 386BSD 0.1.2.4, and first appeared in +program first appeared in 386BSD 0.1.2.4, and first appeared in .Fx in .Fx 2.0.5 . @@ -734,7 +734,7 @@ camcontrol cmd -n da -u 1 -c "00 00 00 00 00 v" 0x00 -v The sense information from the test unit ready command would not get printed out, since the first .Xr getopt 3 -call in +call in .Nm bails out when it sees the second argument to .Fl c diff --git a/sbin/ccdconfig/ccdconfig.8 b/sbin/ccdconfig/ccdconfig.8 index 6134148..2b77862 100644 --- a/sbin/ccdconfig/ccdconfig.8 +++ b/sbin/ccdconfig/ccdconfig.8 @@ -135,7 +135,7 @@ argument is optional. ccd0 16 none /dev/da2e /dev/da3e .Ed .Pp -The component devices need to name partitions of type +The component devices need to name partitions of type .Li FS_BSDFFS (or .Dq 4.2BSD @@ -144,7 +144,7 @@ as shown by .Sh EXAMPLES A number of ccdconfig examples are shown below. The arguments passed to ccdconfig are exactly the same as you might place in the -.Pa /etc/ccd.conf +.Pa /etc/ccd.conf configuration file. The first example creates a 4-disk stripe out of four scsi disk partitions. The stripe uses a 64 sector interleave. The second example is an example of a complex stripe/mirror combination. @@ -160,7 +160,7 @@ mirror. /dev/da2e is mirrored with /dev/da4e and assigned to ccd0. .Pp When you create a new ccd disk you generally want to .Nm disklabel -it before doing anything else. Once you create the initial label you can +it before doing anything else. Once you create the initial label you can edit it, adding additional partitions. The label itself takes up the first 16 sectors of the ccd disk. If all you are doing is creating filesystems with newfs, you do not have to worry about this as newfs will skip the @@ -186,7 +186,7 @@ device list making up the ccd disk, will usually destroy any prior data on that ccd disk. If this occurs it is usually a good idea to reinitialize the label before [re]constructing your ccd disk. .Sh RECOVERY -An error on a ccd disk is usually unrecoverable unless you are using the +An error on a ccd disk is usually unrecoverable unless you are using the mirroring option. But mirroring has its own perils: It assumes that both copies of the data at any given sector are the same. This holds true until a write error occurs or until you replace either side of the mirror. diff --git a/sbin/cxconfig/cxconfig.8 b/sbin/cxconfig/cxconfig.8 index a6701fe..40ebf79 100644 --- a/sbin/cxconfig/cxconfig.8 +++ b/sbin/cxconfig/cxconfig.8 @@ -10,17 +10,17 @@ .Op Fl a .Op Ar Op Ar