Date: Sun, 13 Jun 1999 10:06:03 -0500 (CDT) From: chris@calldei.com To: FreeBSD-gnats-submit@freebsd.org Subject: docs/12184: [Patch] doc/en/handbook/backups/chapter.sgml refers to old devices Message-ID: <199906131506.KAA06073@holly.dyndns.org>
index | next in thread | raw e-mail
>Number: 12184
>Category: docs
>Synopsis: [Patch] doc/en/handbook/backups/chapter.sgml refers to old devices
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: doc-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jun 13 08:10:00 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Chris Costello
>Release: FreeBSD 4.0-CURRENT i386
>Organization:
None
>Environment:
$Id: chapter.sgml,v 1.7 1999/05/25 18:43:24 dwhite Exp $
>Description:
(Note: The priority on this PR is high because people wanting to learn how to
backup important data do not want to be confused by old device name references)
Changed sd to da
Changed st to sa
>How-To-Repeat:
View the backups section.
>Fix:
Index: chapter.sgml
===================================================================
RCS file: /home/ncvs/doc/en/handbook/backups/chapter.sgml,v
retrieving revision 1.7
diff -u -r1.7 chapter.sgml
--- chapter.sgml 1999/05/25 18:43:24 1.7
+++ chapter.sgml 1999/06/13 15:02:52
@@ -170,8 +170,8 @@
blank tape, the operation will fail. The console messages should be
similar to:</para>
- <screen>st0(ncr1:4:0): NOT READY asc:4,1
-st0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
+ <screen>sa0(ncr1:4:0): NOT READY asc:4,1
+sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>The tape does not contain an Identifier Block (block number 0).
All QIC tape drives since the adoption of QIC-525 standard write an
@@ -230,7 +230,7 @@
on the remote computer. (e.g. When <command>rdump</command>'ing from
a FreeBSD computer to an Exabyte tape drive connected to a Sun called
<hostid>komodo</hostid>, use: <command>/sbin/rdump 0dsbfu 54000 13000
- 126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</command>) Beware: there
+ 126 komodo:/dev/nrsa8 /dev/rda0a 2>&1</command>) Beware: there
are security implications to allowing <literal>rhosts</literal>
commands. Evaluate your situation carefully.</para>
</sect2>
@@ -250,7 +250,7 @@
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
<hostid>komodo</hostid>, use: <command>/usr/bin/tar cf
- komodo:/dev/nrst8 . 2>&1</command>. For versions without remote
+ komodo:/dev/nrsa8 . 2>&1</command>. For versions without remote
device support, you can use a pipeline and &man.rsh.1; to send the
data to a remote tape drive. (XXX add an example command)</para>
</sect2>
@@ -264,7 +264,7 @@
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 thru <filename>STDIN</filename>.</para>
+ of files must be provided through <filename>stdin</filename>.</para>
<para>&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
@@ -360,7 +360,7 @@
preparation for any disaster that may occur.</para>
<para>First, print the disklabel from each of your disks
- (<command>e.g. disklabel sd0 | lpr</command>), your filesystem table
+ (<command>e.g. disklabel da0 | lpr</command>), your filesystem table
(<command>/etc/fstab</command>) and all boot messages, two copies of
each.</para>
@@ -389,8 +389,8 @@
procedure. Store these notes with the bootable floppy, the
printouts and the backup tapes. You will be so distraught when
restoring that the notes may prevent you from destroying your backup
- tapes (How? In place of <command>tar xvf /dev/rst0</command>, you
- might accidently type <command>tar cvf /dev/rst0</command> and
+ tapes (How? In place of <command>tar xvf /dev/rsa0</command>, you
+ might accidently type <command>tar cvf /dev/rsa0</command> and
over-write your backup tape).</para>
<para>For an added measure of security, make bootable floppies and two
@@ -468,7 +468,7 @@
options NCONS=2 #1 virtual consoles
options USERCONFIG #Allow user configuration with -c XXX
-config kernel root on sd0 swap on sd0 and sd1 dumps on sd0
+config kernel root on da0 swap on da0 and da1 dumps on da0
controller isa0
controller pci0
@@ -483,11 +483,11 @@
device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
-device sd0
-device sd1
-device sd2
+device da0
+device da1
+device da2
-device st0
+device sa0
pseudo-device loop # required by INET
pseudo-device gzip # Exec gzipped a.out's
@@ -521,10 +521,10 @@
#
cd /mnt/dev
./MAKEDEV std
-./MAKEDEV sd0
-./MAKEDEV sd1
-./MAKEDEV sd2
-./MAKEDEV st0
+./MAKEDEV da0
+./MAKEDEV da1
+./MAKEDEV da2
+./MAKEDEV sa0
./MAKEDEV pty0
cd /
@@ -583,7 +583,7 @@
<para>Recover each filesystem separately.</para>
- <para>Try to &man.mount.8; (e.g. <command>mount /dev/sd0a
+ <para>Try to &man.mount.8; (e.g. <command>mount /dev/da0a
/mnt</command>) the root partition of your first disk. If the
disklabel was damaged, use &man.disklabel.8; to re-partition and
label the disk to match the label that your printed and saved. Use
@@ -591,7 +591,7 @@
partition of the floppy read-write (<command>mount -u -o rw
/mnt</command>). Use your backup program and backup tapes to
recover the data for this filesystem (e.g. <command>restore vrf
- /dev/st0</command>). Unmount the filesystem (e.g. <command>umount
+ /dev/sa0</command>). Unmount the filesystem (e.g. <command>umount
/mnt</command>) Repeat for each filesystem that was
damaged.</para>
>Release-Note:
>Audit-Trail:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199906131506.KAA06073>