From 4b0a74914925fae61301bb16e4413ad932c41500 Mon Sep 17 00:00:00 2001 From: Chern Lee Date: Fri, 7 Sep 2001 00:33:25 +0000 Subject: [PATCH] Change intrusive usage of man entities to tags. --- .../books/handbook/backups/chapter.sgml | 157 ++++++++++-------- 1 file changed, 84 insertions(+), 73 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml index ddff76e5f5..fdd5fbea41 100644 --- a/en_US.ISO8859-1/books/handbook/backups/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/backups/chapter.sgml @@ -1,7 +1,7 @@ @@ -213,9 +213,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready Use the front panel button to eject the tape. - Re-insert the tape and &man.dump.8; data to the tape. + Re-insert the tape and dump data to the tape. - &man.dump.8; will report DUMP: End of tape + dump will report DUMP: End of tape detected and the console will show: HARDWARE FAILURE info:280 asc:80,96. @@ -244,23 +244,24 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready dump restore - The traditional Unix backup programs are &man.dump.8; and - &man.restore.8;. They operate on the drive as a collection of - disk blocks, below the abstractions of files, links and - directories that are created by the filesystems. &man.dump.8; - backs up an entire filesystem on a device. It is unable to - backup only part of a filesystem or a directory tree that - spans more than one filesystem. &man.dump.8; does not write files and + The traditional Unix backup programs are + dump and restore. They + operate on the drive as a collection of disk blocks, below the + abstractions of files, links and directories that are created by + the filesystems. dump backs up an entire + filesystem on a device. It is unable to backup only part of a + filesystem or a directory tree that spans more than one + filesystem. dump does not write files and directories to tape, but rather writes the raw data blocks that comprise files and directories. - If you use &man.dump.8; on your root directory, you + If you use dump on your root directory, you would not back up /home, /usr or many other directories since these are typically mount points for other filesystems or symbolic links into those filesystems. - &man.dump.8; has quirks that remain from its early days in + dumphas quirks that remain from its early days in Version 6 of AT&T Unix (circa 1975). The default parameters are suitable for 9-track tapes (6250 bpi), not the high-density media available today (up to 62,182 ftpi). These @@ -269,12 +270,12 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready rhosts It is also possible to backup data across the network to a - tape drive attached to another computer with &man.rdump.8; and - &man.rrestore.8;. Both programs rely upon &man.rcmd.3; and - &man.ruserok.3; to access the remote tape drive. Therefore, + tape drive attached to another computer with rdump and + rrestore. Both programs rely upon rcmd and + ruserok to access the remote tape drive. Therefore, the user performing the backup must have rhosts access to the remote computer. The - arguments to &man.rdump.8; and &man.rrestore.8; must be suitable + arguments to rdump and rrestore must be suitable to use on the remote computer. (e.g. When rdumping from a FreeBSD computer to an Exabyte tape drive connected to a Sun called @@ -284,9 +285,9 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready allowing rhosts commands. Evaluate your situation carefully. - It is also possible to use &man.rdump.8; and - &man.rrestore.8; in a more secure fashion over - &man.ssh.1;. + It is also possible to use rdump and + rrestore in a more secure fashion over + ssh. Using <command>rdump</command> over <application>ssh</application> @@ -304,27 +305,31 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready tar - &man.tar.1; also dates back to Version 6 of AT&T Unix (circa 1975). - &man.tar.1; operates in cooperation with the filesystem; &man.tar.1; - writes files and directories to tape. &man.tar.1; does not support the + &man.tar.1; also dates back to Version 6 of AT&T Unix + (circa 1975). tar operates in cooperation + with the filesystem; tar writes files and + directories to tape. tar does not support the full range of options that are available from &man.cpio.1;, but - &man.tar.1; does not require the unusual command pipeline that - &man.cpio.1; uses. + tar does not require the unusual command + pipeline that cpio uses. - tar - Most versions of &man.tar.1; do not support backups across the - network. The GNU version of &man.tar.1;, which FreeBSD utilizes, - supports remote devices using the same syntax as &man.rdump.8;. To - &man.tar.1; to an Exabyte tape drive connected to a Sun called - komodo, use: /usr/bin/tar cf - komodo:/dev/nrsa8 . 2>&1. For versions without remote - device support, you can use a pipeline and &man.rsh.1; to send the - data to a remote tape drive. + tar + Most versions of tar do not support + backups across the network. The GNU version of + tar, which FreeBSD utilizes, supports remote + devices using the same syntax as rdump. To + tar to an Exabyte tape drive connected to a + Sun called komodo, use: /usr/bin/tar + cf komodo:/dev/nrsa8 . 2>&1. For versions without + remote device support, you can use a pipeline and + rsh to send the data to a remote tape + drive. &prompt.root; tar cf - . | rsh hostname dd of=tape-device obs=20b - If you are worried about the security of backing up over a network - you should use the &man.ssh.1; command instead of &man.rsh.1;. + If you are worried about the security of backing up over a + network you should use the ssh command + instead of rsh. @@ -334,18 +339,19 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready cpio - &man.cpio.1; is the original Unix file interchange tape program - for magnetic media. &man.cpio.1; has options (among many others) to - perform byte-swapping, write a number of different archive formats, - and pipe the data to other programs. This last feature makes - &man.cpio.1; and excellent choice for installation media. - &man.cpio.1; does not know how to walk the directory tree and a list - of files must be provided through stdin. - cpio + &man.cpio.1; is the original Unix file interchange tape + program for magnetic media. cpio has options + (among many others) to perform byte-swapping, write a number of + different archive formats, and pipe the data to other programs. + This last feature makes cpio and excellent + choice for installation media. cpio does not + know how to walk the directory tree and a list of files must be + provided through stdin. + cpio - &man.cpio.1; does not support backups across the network. You can - use a pipeline and &man.rsh.1; to send the data to a remote tape - drive. + cpio does not support backups across + the network. You can use a pipeline and rsh + to send the data to a remote tape drive. &prompt.root; for f in directory_list; do find $f >> backup.list @@ -370,14 +376,17 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready POSIX IEEE - &man.pax.1; is IEEE/POSIX's answer to &man.tar.1; and - &man.cpio.1;. Over the years the various versions of &man.tar.1; - and &man.cpio.1; have gotten slightly incompatible. So rather than - fight it out to fully standardize them, POSIX created a new archive - utility. &man.pax.1; attempts to read and write many of the various - &man.cpio.1; and &man.tar.1; formats, plus new formats of its own. - Its command set more resembles &man.cpio.1; than &man.tar.1;. - + &man.pax.1; is IEEE/POSIX's answer to + tar and cpio. Over the + years the various versions of tar and + cpio have gotten slightly incompatible. So + rather than fight it out to fully standardize them, POSIX + created a new archive utility. pax attempts + to read and write many of the various cpio + and tar formats, plus new formats of its own. + Its command set more resembles cpio than + tar. + <application>Amanda</application> @@ -443,7 +452,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready &man.dump.8; Period. Elizabeth D. Zwicky torture tested all the backup programs discussed here. The clear choice for preserving all your data and all the peculiarities of Unix - filesystems is &man.dump.8;. Elizabeth created filesystems containing + filesystems is dump. Elizabeth created filesystems containing a large variety of unusual conditions (and some not so unusual ones) and tested each program by doing a backup and restore of those filesystems. The peculiarities included: files with holes, files with @@ -485,11 +494,11 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready Otherwise, you have to create two custom bootable floppies which have a kernel that can mount all of your disks and access your tape drive. These floppies must contain: - &man.fdisk.8;, &man.disklabel.8;, &man.newfs.8;, - &man.mount.8;, and whichever backup program you use. These - programs must be statically linked. If you use - &man.dump.8;, the floppy must contain - &man.restore.8;. + fdisk, disklabel, + newfs, mount, and + whichever backup program you use. These programs must be + statically linked. If you use dump, the + floppy must contain restore. Third, create backup tapes regularly. Any changes that you make after your last backup may be irretrievably lost. Write-protect the @@ -709,11 +718,11 @@ echo "The floppy has been unmounted and is now ready."]]> newfs - Try to &man.mount.8; (e.g. mount /dev/da0a + Try to mount (e.g. mount /dev/da0a /mnt) the root partition of your first disk. If the - disklabel was damaged, use &man.disklabel.8; to re-partition and + disklabel was damaged, use disklabel to re-partition and label the disk to match the label that you printed and saved. Use - &man.newfs.8; to re-create the filesystems. Re-mount the root + newfs to re-create the filesystems. Re-mount the root partition of the floppy read-write (mount -u -o rw /mnt). Use your backup program and backup tapes to recover the data for this filesystem (e.g. restore vrf @@ -779,16 +788,17 @@ echo "The floppy has been unmounted and is now ready."]]> So How Do I Backup My Data to Floppies? The best way to backup to floppy disk is to use - &man.tar.1; with the (multi volume) option, which - allows backups to span multiple floppies. + tar with the (multi + volume) option, which allows backups to span multiple + floppies. To backup all the files in the current directory and sub-directory use this (as root): &prompt.root; tar Mcvf /dev/fd0 * - When the first floppy is full &man.tar.1; will prompt you to - insert the next volume (because &man.tar.1; is media independent it + When the first floppy is full tar will prompt you to + insert the next volume (because tar is media independent it refers to volumes. In this context it means floppy disk) Prepare volume #2 for /dev/fd0 and hit return: @@ -807,10 +817,11 @@ echo "The floppy has been unmounted and is now ready."]]> compression - Unfortunately, &man.tar.1; will not allow the + Unfortunately, tar will not allow the option to be used for multi-volume archives. - You could, of course, &man.gzip.1; all the files, &man.tar.1; them to - the floppies, then &man.gunzip.1; the files again! + You could, of course, gzip all the files, + tar them to the floppies, then + gunzip the files again! @@ -826,14 +837,14 @@ echo "The floppy has been unmounted and is now ready."]]> &prompt.root; tar Mxvf /dev/fd0 filename - &man.tar.1; will prompt you to insert subsequent floppies until it + tar will prompt you to insert subsequent floppies until it finds the required file. Alternatively, if you know which floppy the file is on then you can simply insert that floppy and use the same command as above. Note that if the first file on the floppy is a continuation from the - previous one then &man.tar.1; will warn you that it cannot restore it, - even if you have not asked it to! + previous one then tar will warn you that it cannot + restore it, even if you have not asked it to!