summaryrefslogtreecommitdiffstats
path: root/sbin/bsdlabel
diff options
context:
space:
mode:
authordd <dd@FreeBSD.org>2001-07-15 07:53:42 +0000
committerdd <dd@FreeBSD.org>2001-07-15 07:53:42 +0000
commita145482cf625d5f04072fd1d20b5c2062cbe8e47 (patch)
treed6c008b8ae357e7c4c800baa477713b82a6ee2f2 /sbin/bsdlabel
parent0d7bb1fec635c87e914e57048716adc5a87cfe22 (diff)
downloadFreeBSD-src-a145482cf625d5f04072fd1d20b5c2062cbe8e47.zip
FreeBSD-src-a145482cf625d5f04072fd1d20b5c2062cbe8e47.tar.gz
Remove whitespace at EOL.
Diffstat (limited to 'sbin/bsdlabel')
-rw-r--r--sbin/bsdlabel/bsdlabel.58
-rw-r--r--sbin/bsdlabel/bsdlabel.866
2 files changed, 37 insertions, 37 deletions
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
OpenPOWER on IntegriCloud