Sweep man pages replacing ad -> ada.

Approved by: re (blackend) MFC after: 1 week X-MFC note: stable/9 only
rbrich · Oct 1, 2013 · 3f9b259 · 3f9b259
1 parent a5307f0
commit 3f9b259
Show file tree

Hide file tree

Showing 21 changed files with 87 additions and 87 deletions.
diff --git a/bin/dd/dd.1 b/bin/dd/dd.1
@@ -32,7 +32,7 @@
 .\"     @(#)dd.1	8.2 (Berkeley) 1/13/94
 .\" $FreeBSD$
 .\"
-.Dd January 23, 2009
+.Dd October 1, 2013
 .Dt DD 1
 .Os
 .Sh NAME
@@ -378,12 +378,12 @@ will exit.
 .Sh EXAMPLES
 Check that a disk drive contains no bad blocks:
 .Pp
-.Dl "dd if=/dev/ad0 of=/dev/null bs=1m"
+.Dl "dd if=/dev/ada0 of=/dev/null bs=1m"
 .Pp
 Do a refresh of a disk drive, in order to prevent presently
 recoverable read errors from progressing into unrecoverable read errors:
 .Pp
-.Dl "dd if=/dev/ad0 of=/dev/ad0 bs=1m"
+.Dl "dd if=/dev/ada0 of=/dev/ada0 bs=1m"
 .Pp
 Remove parity bit from a file:
 .Pp

diff --git a/sbin/bsdlabel/bsdlabel.8 b/sbin/bsdlabel/bsdlabel.8
@@ -31,7 +31,7 @@
 .\"	@(#)disklabel.8	8.2 (Berkeley) 4/19/94
 .\" $FreeBSD$
 .\"
-.Dd March 5, 2011
+.Dd October 1, 2013
 .Dt BSDLABEL 8
 .Os
 .Sh NAME
@@ -457,9 +457,9 @@ such as
 and
 .Cm * ,
 which could be used as a source file for
-.Dq Li "bsdlabel -R ad0s1 new_label_file" :
+.Dq Li "bsdlabel -R ada0s1 new_label_file" :
 .Bd -literal -offset 4n
-# /dev/ad0s1:
+# /dev/ada0s1:
 
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]

diff --git a/sbin/ccdconfig/ccdconfig.8 b/sbin/ccdconfig/ccdconfig.8
@@ -28,7 +28,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd July 17, 1995
+.Dd October 1, 2013
 .Dt CCDCONFIG 8
 .Os
 .Sh NAME
@@ -180,7 +180,7 @@ and read it from
 mdadm --create --chunk=32 --level=0 --raid-devices=2 /dev/md0 \\
    /dev/hda1 /dev/hdb1
 # Make the RAID-0 just created available on FreeBSD:
-ccdconfig -c /dev/ccd0 32 linux /dev/ad0s1 /dev/ad0s2
+ccdconfig -c /dev/ccd0 32 linux /dev/ada0s1 /dev/ada0s2
 .Ed
 .Pp
 When you create a new ccd disk you generally want to

diff --git a/sbin/fdisk/fdisk.8 b/sbin/fdisk/fdisk.8
@@ -1,6 +1,6 @@
 .\" $FreeBSD$
 .\"
-.Dd May 24, 2009
+.Dd October 1, 2013
 .Dt FDISK 8
 .Os
 .Sh NAME
@@ -159,7 +159,7 @@ mounted root device.
 When called with no arguments, it prints the sector 0 slice table.
 An example follows:
 .Bd -literal
-	******* Working on device /dev/ad0 *******
+	******* Working on device /dev/ada0 *******
 	parameters extracted from in-core disklabel are:
 	cylinders=769 heads=15 sectors/track=33 (495 blks/cyl)
 

diff --git a/sbin/gbde/gbde.8 b/sbin/gbde/gbde.8
@@ -31,7 +31,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd February 8, 2006
+.Dd October 1, 2013
 .Dt GBDE 8
 .Os
 .Sh NAME
@@ -207,35 +207,35 @@ used).
 .Sh EXAMPLES
 To initialize a device, using default parameters:
 .Pp
-.Dl "gbde init /dev/ad0s1f -L /etc/ad0s1f.lock"
+.Dl "gbde init /dev/ada0s1f -L /etc/ada0s1f.lock"
 .Pp
 To attach an encrypted device:
 .Pp
-.Dl "gbde attach ad0s1f -l /etc/ad0s1f.lock"
+.Dl "gbde attach ada0s1f -l /etc/ada0s1f.lock"
 .Pp
 The encrypted device has the suffix
 .Pa .bde
 so a typical
 command to create and mount a file system would be:
 .Pp
-.Dl "newfs /dev/ad0s1f.bde"
-.Dl "mount /dev/ad0s1f.bde /secret"
+.Dl "newfs /dev/ada0s1f.bde"
+.Dl "mount /dev/ada0s1f.bde /secret"
 .Pp
 To detach an encrypted device:
 .Pp
-.Dl "gbde detach ad0s1f"
+.Dl "gbde detach ada0s1f"
 .Pp
 Please notice that detaching an encrypted device corresponds to
 physically removing it, do not forget to unmount the file system first.
 .Pp
 To initialize the second key using a detached lockfile and a trivial
 pass-phrase:
 .Pp
-.Dl "gbde setkey ad0s1f -n 2 -P foo -L key2.lockfile"
+.Dl "gbde setkey ada0s1f -n 2 -P foo -L key2.lockfile"
 .Pp
 To destroy all copies of the masterkey:
 .Pp
-.Dl "gbde destroy ad0s1f -n -1"
+.Dl "gbde destroy ada0s1f -n -1"
 .Sh SEE ALSO
 .Xr gbde 4 ,
 .Xr geom 4

diff --git a/sbin/geom/class/eli/geli.8 b/sbin/geom/class/eli/geli.8
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd July 5, 2013
+.Dd October 1, 2013
 .Dt GELI 8
 .Os
 .Sh NAME
@@ -841,20 +841,20 @@ Create an encrypted provider for use by the user, but remember that users
 forget their passphrases, so backup the Master Key with your own random key:
 .Bd -literal -offset indent
 # dd if=/dev/random of=/mnt/pendrive/keys/`hostname` bs=64 count=1
-# geli init -P -K /mnt/pendrive/keys/`hostname` /dev/ad0s1e
-# geli backup /dev/ad0s1e /mnt/pendrive/backups/`hostname`
+# geli init -P -K /mnt/pendrive/keys/`hostname` /dev/ada0s1e
+# geli backup /dev/ada0s1e /mnt/pendrive/backups/`hostname`
 (use key number 0, so the encrypted Master Key will be re-encrypted by this)
-# geli setkey -n 0 -k /mnt/pendrive/keys/`hostname` /dev/ad0s1e
+# geli setkey -n 0 -k /mnt/pendrive/keys/`hostname` /dev/ada0s1e
 (allow the user to enter his passphrase)
 Enter new passphrase:
 Reenter new passphrase:
 .Ed
 .Pp
 Encrypted swap partition setup:
 .Bd -literal -offset indent
-# dd if=/dev/random of=/dev/ad0s1b bs=1m
-# geli onetime -d -e 3des ad0s1b
-# swapon /dev/ad0s1b.eli
+# dd if=/dev/random of=/dev/ada0s1b bs=1m
+# geli onetime -d -e 3des ada0s1b
+# swapon /dev/ada0s1b.eli
 .Ed
 .Pp
 The example below shows how to configure two providers which will be attached

diff --git a/sbin/geom/class/shsec/gshsec.8 b/sbin/geom/class/shsec/gshsec.8
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd January 8, 2005
+.Dd October 1, 2013
 .Dt GSHSEC 8
 .Os
 .Sh NAME
@@ -108,7 +108,7 @@ Exit status is 0 on success, and 1 if the command fails.
 The following example shows how to create a shared secret device.
 The secret will be split between a slice on a local disk and a USB Pen drive.
 .Bd -literal -offset indent
-gshsec label -v secret /dev/ad0s1 /dev/da0
+gshsec label -v secret /dev/ada0s1 /dev/da0
 newfs /dev/shsec/secret
 .Ed
 .Pp

diff --git a/sbin/geom/class/virstor/gvirstor.8 b/sbin/geom/class/virstor/gvirstor.8
@@ -24,7 +24,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd August 3, 2012
+.Dd October 1, 2013
 .Dt GVIRSTOR 8
 .Os
 .Sh NAME
@@ -161,7 +161,7 @@ size
 .Pq 4 MiB ,
 with two physical devices for backing storage.
 .Bd -literal -offset indent
-.No gvirstor label -v Ar mydata Ar /dev/ad4 Ar /dev/ad6
+.No gvirstor label -v Ar mydata Ar /dev/ada4 Ar /dev/ada6
 .No newfs Ar /dev/virstor/mydata
 .Ed
 .Pp
@@ -170,11 +170,11 @@ From now on, the virtual device will be available via the
 device entry.
 To add a new physical device / component to an active virstor device:
 .Bd -literal -offset indent
-.No gvirstor add Ar mydata Ar ad8
+.No gvirstor add Ar mydata Ar ada8
 .Ed
 .Pp
 This will add physical storage of
-.Ar ad8
+.Ar ada8
 to
 .Pa /dev/virstor/mydata
 device.

diff --git a/sbin/gvinum/gvinum.8 b/sbin/gvinum/gvinum.8
@@ -28,7 +28,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd April 10, 2009
+.Dd October 1, 2013
 .Dt GVINUM 8
 .Os
 .Sh NAME
@@ -279,27 +279,27 @@ directory with device nodes for
 objects
 .El
 .Sh EXAMPLES
-To create a mirror on disks /dev/ad1 and /dev/ad2, create a filesystem, mount,
-unmount and then stop
+To create a mirror on disks /dev/ada1 and /dev/ada2, create a filesystem,
+mount, unmount and then stop
 .Ic gvinum :
 .Pp
-.Dl "gvinum mirror /dev/ad1 /dev/ad2"
+.Dl "gvinum mirror /dev/ada1 /dev/ada2"
 .Dl "newfs /dev/gvinum/gvinumvolume0"
 .Dl "mount /dev/gvinum/gvinumvolume0 /mnt"
 .Dl "..."
 .Dl "unmount /mnt"
 .Dl "gvinum stop"
 .Pp
-To create a striped mirror on disks /dev/ad1 /dev/ad2 /dev/ad3 and /dev/ad4
-named "data" and create a filesystem:
+To create a striped mirror on disks /dev/ada1 /dev/ada2 /dev/ada3 and
+/dev/ada4 named "data" and create a filesystem:
 .Pp
-.Dl "gvinum mirror -s -n data /dev/ad1 /dev/ad2 /dev/ad3 /dev/ad4"
+.Dl "gvinum mirror -s -n data /dev/ada1 /dev/ada2 /dev/ada3 /dev/ada4"
 .Dl "newfs /dev/gvinum/data"
 .Pp
-To create a raid5 array on disks /dev/ad1 /dev/ad2 and /dev/ad3, with stripesize
-493k you can use the raid5 command:
+To create a raid5 array on disks /dev/ada1 /dev/ada2 and /dev/ada3,
+with stripesize 493k you can use the raid5 command:
 .Pp
-.Dl "gvinum raid5 -s 493k /dev/ad1 /dev/ad2 /dev/ad3"
+.Dl "gvinum raid5 -s 493k /dev/ada1 /dev/ada2 /dev/ada3"
 .Pp
 Then the volume will be created automatically.
 Afterwards, you have to initialize the volume:
@@ -313,9 +313,9 @@ The list command will give you information about its progress.
 Imagine that one of the drives fails, and the output of 'printconfig' looks
 something like this:
 .Pp
-.Dl "drive gvinumdrive1 device /dev/ad2"
+.Dl "drive gvinumdrive1 device /dev/ada2"
 .Dl "drive gvinumdrive2 device /dev/???"
-.Dl "drive gvinumdrive0 device /dev/ad1"
+.Dl "drive gvinumdrive0 device /dev/ada1"
 .Dl "volume myraid5vol"
 .Dl "plex name myraid5vol.p0 org raid5 986s vol myraid5vol"
 .Dl "sd name myraid5vol.p0.s2 drive gvinumdrive2 len 32538s driveoffset 265s"
@@ -327,7 +327,7 @@ something like this:
 .Pp
 Create a new drive with this configuration:
 .Pp
-.Dl "drive gdrive4 device /dev/ad4"
+.Dl "drive gdrive4 device /dev/ada4"
 .Pp
 Then move the stale subdisk to the new drive:
 .Pp
@@ -344,7 +344,7 @@ might be delayed.
 Given the configuration as in the previous example, growing a RAID-5 or STRIPED
 array is accomplished by using the grow command:
 .Pp
-.Dl "gvinum grow myraid5vol.p0 /dev/ad4"
+.Dl "gvinum grow myraid5vol.p0 /dev/ada4"
 .Pp
 If everything went ok, the plex state should now be set to growable.
 You can then start the growing with the

diff --git a/sbin/mount_msdosfs/mount_msdosfs.8 b/sbin/mount_msdosfs/mount_msdosfs.8
@@ -30,7 +30,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd December 23, 2008
+.Dd October 1, 2013
 .Dt MOUNT_MSDOSFS 8
 .Os
 .Sh NAME
@@ -182,14 +182,14 @@ Specify text file name with conversion table:
 .El
 .Sh EXAMPLES
 To mount a Russian MS-DOS file system located in
-.Pa /dev/ad1s1 :
+.Pa /dev/ada1s1 :
 .Pp
-.Dl "mount_msdosfs -L ru_RU.KOI8-R -D CP866 /dev/ad1s1 /mnt"
+.Dl "mount_msdosfs -L ru_RU.KOI8-R -D CP866 /dev/ada1s1 /mnt"
 .Pp
 To mount a Japanese MS-DOS file system located in
-.Pa /dev/ad1s1 :
+.Pa /dev/ada1s1 :
 .Pp
-.Dl "mount_msdosfs -L ja_JP.eucJP -D CP932 /dev/ad1s1 /mnt"
+.Dl "mount_msdosfs -L ja_JP.eucJP -D CP932 /dev/ada1s1 /mnt"
 .Sh SEE ALSO
 .Xr mount 2 ,
 .Xr unmount 2 ,

diff --git a/sbin/newfs/newfs.8 b/sbin/newfs/newfs.8
@@ -28,7 +28,7 @@
 .\"     @(#)newfs.8	8.6 (Berkeley) 5/3/95
 .\" $FreeBSD$
 .\"
-.Dd June 22, 2011
+.Dd October 1, 2013
 .Dt NEWFS 8
 .Os
 .Sh NAME
@@ -285,10 +285,10 @@ to find the alternate superblocks if the standard superblock is lost.
 The size of a sector in bytes (almost never anything but 512).
 .El
 .Sh EXAMPLES
-.Dl newfs /dev/ad3s1a
+.Dl newfs /dev/ada3s1a
 .Pp
 Creates a new ufs file system on
-.Pa ad3s1a .
+.Pa ada3s1a .
 The
 .Nm
 utility will use a block size of 32768 bytes, a fragment size of 4096 bytes

diff --git a/sbin/newfs_msdos/newfs_msdos.8 b/sbin/newfs_msdos/newfs_msdos.8
@@ -25,7 +25,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd July 25, 2010
+.Dd October 1, 2013
 .Dt NEWFS_MSDOS 8
 .Os
 .Sh NAME
@@ -209,9 +209,9 @@ The maximum file size is 4GB, even if the file system itself is bigger.
 Exit status is 0 on success and 1 on error.
 .Sh EXAMPLES
 Create a file system, using default parameters, on
-.Pa /dev/ad0s1 :
+.Pa /dev/ada0s1 :
 .Bd -literal -offset indent
-newfs_msdos /dev/ad0s1
+newfs_msdos /dev/ada0s1
 .Ed
 .Pp
 Create a standard 1.44M file system, with volume label

diff --git a/sbin/newfs_nandfs/newfs_nandfs.8 b/sbin/newfs_nandfs/newfs_nandfs.8
@@ -25,7 +25,7 @@
 .\"
 .\" $FreeBSD$
 .\"
-.Dd April 11, 2009
+.Dd October 1, 2013
 .Dt NEWFS_NANDFS 8
 .Os
 .Sh NAME
@@ -58,9 +58,9 @@ Percentage of reserved blocks (5 if not specified).
 Exit status is 0 on success and 1 on error.
 .Sh EXAMPLES
 Create a file system, using default parameters, on
-.Pa /dev/ad0s1 :
+.Pa /dev/ada0s1 :
 .Bd -literal -offset indent
-newfs_nandfs /dev/ad0s1
+newfs_nandfs /dev/ada0s1
 .Ed
 .Sh SEE ALSO
 .Xr disktab 5 ,