Date: Sat, 18 Aug 2001 16:39:28 +0100 From: John Murphy <jfm@blueyonder.co.uk> To: freebsd-gnats-submit@freebsd.org Subject: docs/29848: Handbook Chapter 13 (Backups) minor changes Message-ID: <um2tnt0jifm9fdffdd2v8t7jvaotvurvvg@4ax.com>
next in thread | raw e-mail | index | archive | help
>Number: 29848
>Category: docs
>Synopsis: Handbook Chapter 13 (Backups) minor changes
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Sat Aug 18 08:40:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: John Murphy
>Release: FreeBSD 4.3-STABLE i386
>Organization:
>Environment:
>Description:
doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml
Removed XXX* and XXX
=46ixed some minor typos etc.
Changed tabs to spaces in Example 13-2. A Script for Creating a Bootable =
=46loppy
(should make it look better).
>How-To-Repeat:
>Fix:
Apply the following diff to:
doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml Revision 1.42
--- chapter Fri Aug 17 21:48:26 2001
+++ chapter.patched Fri Aug 17 21:48:29 2001
@@ -132,7 +132,7 @@
</sect2>
=20
<sect2 id=3D"backups-tapebackups-mini">
- <title>XXX* Mini-Cartridge</title>
+ <title>Mini-Cartridge</title>
=20
<para></para>
</sect2>
@@ -186,7 +186,7 @@
the several minutes that would be required for other tapes. Software
such as SAMS:Alexandria can operate forty or more AIT tape libraries,
communicating directly with the tape's memory chip to display the
- contents on screen, determine what files where backed up to which
+ contents on screen, determine what files were backed up to which
tape, locate the correct tape, load it, and restore the data from the
tape.</para>
=20
@@ -323,7 +323,7 @@
=20
<screen>&prompt.root; <userinput>tar cf - . | rsh =
<replaceable>hostname</replaceable> dd =
of=3D<replaceable>tape-device</replaceable> =
obs=3D20b</userinput></screen>
=20
- <para>If you are worried about the security of backing over a =
network
+ <para>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;.</para>
</sect2>
=20
@@ -336,7 +336,7 @@
=20
<para>&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 archives format,
+ 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
@@ -393,9 +393,9 @@
rather than a single program. An Amanda server will backup to
a single tape drive any number of computers that have Amanda
clients and a network connection to the Amanda server. A
- common problem at locations with a number of large disks is
- the length of time required to backup to data directly to tape
- exceeds the amount of time available for the task. Amanda
+ common problem, at locations with a number of large disks, is
+ that the length of time required to backup the data directly to
+ tape exceeds the amount of time available for the task. Amanda
solves this problem. Amanda can use a "holding disk" to
backup several filesystems at the same time. Amanda creates
"archive sets": a group of tapes used over a period of time to
@@ -405,7 +405,7 @@
Restoring a damaged filesystem requires the most recent full
backup and the incremental backups.</para>
=20
- <para>The configuration file provides fine control backups and the
+ <para>The configuration file provides fine control of backups and =
the
network traffic that Amanda generates. Amanda will use any of the
above backup programs to write the data to tape. Amanda is available
as either a port or a package, it is not installed by default.</para>
@@ -445,7 +445,7 @@
choice for preserving all your data and all the peculiarities of Unix
filesystems is &man.dump.8;. 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 that
+ and tested each program by doing a backup and restore of those
filesystems. The peculiarities included: files with holes, files with
holes and a block of nulls, files with funny characters in their
names, unreadable and unwritable files, devices, files that change
@@ -483,7 +483,7 @@
step three.</para>
=20
<para>Otherwise, you have to create two custom bootable
- floppies which has a kernel that can mount all of your disks
+ 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
@@ -565,44 +565,44 @@
The MINI kernel does not exist, please create one.
Here is an example config file:
#
-# MINI -- A kernel to get FreeBSD on onto a disk.
+# MINI -- A kernel to get FreeBSD onto a disk.
#
-machine "i386"
-cpu "I486_CPU"
-ident MINI
-maxusers 5
+machine "i386"
+cpu "I486_CPU"
+ident MINI
+maxusers 5
=20
-options INET # needed for _tcp _icmpstat _ipstat
- # _udpstat _tcpstat _udb
-options FFS #Berkeley Fast File System
-options FAT_CURSOR #block cursor in syscons or pccons
-options SCSI_DELAY=3D15 #Be pessimistic about Joe SCSI device
-options NCONS=3D2 #1 virtual consoles
-options USERCONFIG #Allow user configuration with -c XXX
+options INET # needed for _tcp _icmpstat =
_ipstat
+ # _udpstat _tcpstat =
_udb
+options FFS #Berkeley Fast File System
+options FAT_CURSOR #block cursor in syscons or =
pccons
+options SCSI_DELAY=3D15 #Be pessimistic about Joe SCSI=
device
+options NCONS=3D2 #1 virtual consoles
+options USERCONFIG #Allow user configuration with =
-c
=20
-config kernel root on da0 swap on da0 and da1 dumps on da0
+config kernel root on da0 swap on da0 and da1 dumps on da0
=20
-controller isa0
-controller pci0
+controller isa0
+controller pci0
=20
-controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
-disk fd0 at fdc0 drive 0
+controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector =
fdintr
+disk fd0 at fdc0 drive 0
=20
-controller ncr0
+controller ncr0
=20
-controller scbus0
+controller scbus0
=20
-device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
-device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
+device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
+device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
=20
-device da0
-device da1
-device da2
+device da0
+device da1
+device da2
=20
-device sa0
+device sa0
=20
-pseudo-device loop # required by INET
-pseudo-device gzip # Exec gzipped a.out's
+pseudo-device loop # required by INET
+pseudo-device gzip # Exec gzipped a.out's
EOM
exit 1
fi
@@ -644,7 +644,7 @@
# create minimum filesystem table
#
cat > /mnt/etc/fstab <<EOM
-/dev/fd0a / ufs rw 1 1
+/dev/fd0a / ufs rw 1 1
EOM
=20
#
@@ -769,10 +769,10 @@
<para>However, if you have no other method of backing up your data=
then
floppy disks are better than no backup at all.</para>
=20
- <para>If you do have to use floppy disks then ensure that you use =
good
- quality ones. Floppies that have been lying around the office for a
- couple of years are a bad choice. Ideally use new ones from a
- reputable manufacturer.</para>
+ <para>If you <emphasis>do</emphasis> have to use floppy disks then=
ensure
+ that you use good quality ones. Floppies that have been lying =
around
+ the office for a couple of years are a bad choice. Ideally use =
new ones
+ from a reputable manufacturer.</para>
</sect2>
=20
<sect2 id=3D"floppies-creating">
>Release-Note:
>Audit-Trail:
>Unformatted:
X-send-pr-version: 3.113
X-GNATS-Notify:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?um2tnt0jifm9fdffdd2v8t7jvaotvurvvg>