From: sms@WLV.IIPO.GTEGSC.COM (Steven M. Schultz)
Subject: Updates to the setup documents (#73)
Organization: GTE Government Systems
Date: Sat, 29 Aug 92 09:59:54 GMT

Subject: Updates to the setup documents (#73)
Index:	doc/2.10/setup.2.11/0,1,2.t 2.11BSD

Description:
	The installation documents were erroneous or outdated in several
	places.

	Over time various disc subsystems have been noted as being
	either unused (unusable is more likely) or not capable of
	being used to host the distribution kit.  These are more
	clearly identified (and removed from the current version of
	the system, e.g. RD51 and RC25 drives can be used as "data"
	discs but they are incapable of even containing a root filesystem 
	plus a swap area).

	/boot has  undergone quite a change since these documents
	were last updated - multiple controller/unit support (/boot
	can be loaded from _any_ unit or controller that the boot
	roms or toggle-in routine support) has been added.  The boot
	messages are different now - the cputype and CSR/unit are
	displayed in the boot message.

	*Many* new MSCP disk types are supported, the documents now
	give the parameters for them, etc.

	Also, it was time to reflect the new address of the maintainer
	(yours truly).

Repeat-By:

	Examination or actually trying to use the documents to install
	the present incarnation of the system.

Fix:
	Apply the patch below.

==============================cut here===================================
*** /usr/doc/2.10/setup.2.11/0.t.old	Wed Dec 19 09:57:03 1990
--- /usr/doc/2.10/setup.2.11/0.t	Mon Jul 20 21:29:08 1992
***************
*** 2,8 ****
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)0.t	1.0 (Contel) 7/5/90
  .\"
  .EH 'setup.2.11 - %''Installing and Operating 2.11BSD on the PDP-11'
  .OH 'Installing and Operating 2.11BSD on the PDP-11''Setup.2.11 - %'
--- 2,8 ----
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)0.t	2.0 (GTE) 7/20/92
  .\"
  .EH 'setup.2.11 - %''Installing and Operating 2.11BSD on the PDP-11'
  .OH 'Installing and Operating 2.11BSD on the PDP-11''Setup.2.11 - %'
***************
*** 13,26 ****
  .TL
  Installing and Operating \*(2B on the PDP-11
  .br
! November 1, 1990
  .AU
  Steven Schultz
  .AI
! Contel Federal Systems
  31717 La Tienda Drive
  Westlake Village CA 91359-5027
! sms@wlv.imsd.contel.com
  .de IR
  \\fI\\$1\|\\fP\\$2
  ..
--- 13,26 ----
  .TL
  Installing and Operating \*(2B on the PDP-11
  .br
! July 20, 1992
  .AU
  Steven Schultz
  .AI
! GTE Government Systems
  31717 La Tienda Drive
  Westlake Village CA 91359-5027
! sms@wlv.iipo.gtegsc.com
  .de IR
  \\fI\\$1\|\\fP\\$2
  ..
***************
*** 56,63 ****
  This release is not supported, and is emphatically \fBNOT\fP an official
  Berkeley release.
  It was called \*(2B because along with many fixes and
! enhancements, the filesystem has changed which mandated a version number
! change.
  .PP
  The ``bugs'' address supplied with this release
  will work for some unknown period of time; make sure
--- 56,62 ----
  This release is not supported, and is emphatically \fBNOT\fP an official
  Berkeley release.
  It was called \*(2B because along with many fixes and
! enhancements the filesystem has changed.
  .PP
  The ``bugs'' address supplied with this release
  will work for some unknown period of time; make sure
*** /usr/doc/2.10/setup.2.11/1.t.old	Sat Dec  8 18:15:25 1990
--- /usr/doc/2.10/setup.2.11/1.t	Tue Jul 21 21:19:58 1992
***************
*** 2,8 ****
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)1.t	1.0 (Contel) 7/5/90
  .\"
  .ds lq ``
  .ds rq ''
--- 2,8 ----
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)1.t	2.0 (GTE) 7/20/92
  .\"
  .ds lq ``
  .ds rq ''
***************
*** 64,80 ****
  .DS
  .TS
  lw(1.5i) l.
- RL01, RL02
  RK06, RK07
! RD51, RD52, RD53, RD54
! RA60, RA80, RA81, RA82
  RC25
  RM02, RM03, RM05
  RP04, RP05, RP06
! Ampex 9300, CDC 9766, Diva Comp V, Fuji 160, Fuji Eagle, Contel BR1538
  .TE
  .DE
  .PP
  The tape drives supported by this distribution are:
  .DS
  .TS
--- 64,87 ----
  .DS
  .TS
  lw(1.5i) l.
  RK06, RK07
! RD31, RD32, RD33, RD52, RD53, RD54
! RA60, RA70, RA71, RA72, RA73, RA80, RA81, RA82, RA90, RA92
! RZ23, RZ24, RZ25, RZ26
  RC25
  RM02, RM03, RM05
  RP04, RP05, RP06
! Ampex 9300, CDC 9766, Diva Comp V, Fuji 160, Fuji Eagle
  .TE
  .DE
  .PP
+ Other discs are supported (RX23, RX33, RX50, RD51) but are not large
+ enough to hold a root filesystem plus a swap partition.  Some discs
+ (the RL01 and RL02 for example) must be used in pairs (1 for the root
+ file system and the 2nd for swapping).  These discs
+ may be used as data discs or as standalone boot media, but are not useable
+ for loading the distribution.
+ .PP
  The tape drives supported by this distribution are:
  .DS
  .TS
***************
*** 82,95 ****
  TS11, TU80
  TM11, AVIV 6250/1600
  TE16, TU45, TU77
! TQK50, TK50\(dd
  .TE
  .DE
- .FS
- .IP \(dd
- The TMSCP driver should work with any TMSCP device (such as the TU81) but has
- only been actually tested/used with a TK50 on a 11/73.
- .FE
  Although \*(2B contains a kernel level floating point simulator, it has
  never been tested.  At the release of \*(Ps some thought was given
  to the possibility of lifting the separate I&D restriction, but that
--- 89,97 ----
  TS11, TU80
  TM11, AVIV 6250/1600
  TE16, TU45, TU77
! TK50, TU81, TU81+, TZ30
  .TE
  .DE
  Although \*(2B contains a kernel level floating point simulator, it has
  never been tested.  At the release of \*(Ps some thought was given
  to the possibility of lifting the separate I&D restriction, but that
***************
*** 213,221 ****
  l l.
  RK06, RK07 disks	hk
  RL01, RL02 disks	rl
- UDA disks	ra
- RC25 disks	ra
- RD51/52/53/54 disks	ra
  MSCP disks	ra
  RM02/03/05	xp
  RP04/05/06	xp
--- 215,220 ----
***************
*** 230,236 ****
  .DS
  .TS
  l l.
- Contel BR1538/BR1711	br      (not in the GENERIC kernel)
  SI 9500, CDC 9766	si
  Ampex Capricorn	xp
  SI, CDC 9775	xp
--- 229,234 ----
***************
*** 245,250 ****
--- 243,253 ----
  (even different types on the same controller).
  The \fBxp\fP driver handles RM02, RM03, RM05, RP04, RP05 and  RP06
  disks on DEC, Emulex, Diva, and SI UNIBUS or MASSBUS controllers.
+ .PP
+ MSCP discs and TMSCP tapes include SCSI drives attached to the 
+ RQZX1 controller on the PDP-11/93.  MSCP discs and TMSCP tapes also include
+ SCSI drives attached to the Emulex UC07 or UC08 Q-BUS controllers on Q-bus 
+ systems as well as the UC17 and UC18 controllers on UNIBUS systems.
  .PP
  The standalone system used to bootstrap the full UNIX system
  uses device names of the form:
*** /usr/doc/2.10/setup.2.11/2.t.old	Tue Dec 31 23:53:09 1991
--- /usr/doc/2.10/setup.2.11/2.t	Mon Aug 24 21:08:32 1992
***************
*** 2,8 ****
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)2.t	1.2 (Contel) 12/31/91
  .\"
  .ds lq ``
  .ds rq ''
--- 2,8 ----
  .\" All rights reserved.  The Berkeley software License Agreement
  .\" specifies the terms and conditions for redistribution.
  .\"
! .\"	@(#)2.t	1.4 (GTE) 8/24/92
  .\"
  .ds lq ``
  .ds rq ''
***************
*** 81,87 ****
  bootstrap to boot from the tape.
  .PP
  NOTE: The boot blocks expect the CSR of the booting controller in r0
! and the unit number in r1.
  .PP
  If no other means are available, the following code can be keyed in
  and executed at (say) 0100000 to boot from a TM tape drive (the magic number
--- 81,89 ----
  bootstrap to boot from the tape.
  .PP
  NOTE: The boot blocks expect the CSR of the booting controller in r0
! and the unit number in r1.  \fBboot\fP may be booted from any controller
! or unit, the earlier restrictions of controller 0 and unit 0 have been
! lifted.
  .PP
  If no other means are available, the following code can be keyed in
  and executed at (say) 0100000 to boot from a TM tape drive (the magic number
***************
*** 107,137 ****
  The console should type
  .DS
  .B
! \fInn\fPBoot
  :
  .R
  .DE
! where \fInn\fP is the CPU class on which it believes it is running.
! The value will be one of 24, 40, 44, 45, 70 or 73, depending on whether
  separate instruction and data (separate I/D) and/or a UNIBUS map are detected.
! It must be emphasized that \*(2B requires separate I/D.
! The CPUs in each class are:
! .DS
! .TS
! c l c c.
! Class	PDP-11	Separate I/D	UNIBUS map
! 24	24	-	+
! 40	23, 34, 34A, 40, 60	-	-
! 44	44	+	+
! 45	45, 55	+	-
! 70	70	+	+
! 73	73	+	-
! 83	83	+	-
! 84	84	+	+
! 93	93	+	-
! 94	94	+	+
! .TE
! .DE
  .PP
  You are now talking to the tape bootstrap monitor.
  At any point in the following procedure you can return
--- 109,133 ----
  The console should type
  .DS
  .B
! \fInn\fPBoot from \fIxx\fP(\fIctlr\fP,0,\fIcsr\fP)
  :
  .R
  .DE
! where \fInn\fP is the CPU type on which it believes it is running.
! The value will be one of 23, 24, 40, 44, 45, 53, 60, 70, 73, 83, 84, 93
! or 94 depending whether
  separate instruction and data (separate I/D) and/or a UNIBUS map are detected.
! For KDJ-11 systems the System Maintenance Register is examined to determine
! the cpu type.  At present \*(2B runs on the 44, 53, 70, 73, 83, 84, 93 and 94
! only.  It must be emphasized that \*(2B requires separate I/D.
! .sp
! \fIctlr\fP encodes the controller number and unit number that \fBBoot\fP
! was loaded from.  The top two bits (bits 6 and 7) are the controller
! number and the low three bits (bits 0, 1 and 2) are the unit number.
! .sp
! \fIcsr\fP is an octal number telling the CSR of the controller from which
! \fBBoot\fP was loaded.
! .sp
  .PP
  You are now talking to the tape bootstrap monitor.
  At any point in the following procedure you can return
***************
*** 151,160 ****
  Disk	Root File System Size
  	  (1K-byte blocks)
  
- br	9120 (T300 - not in the GENERIC kernel)
  hk	4158\(ua
! ra	7942 (RA60/80/81/82, RD54, RC25)
! 	4850 (RD51/52/53)
  rl01	5120\(dd
  rl02	10240\(dd
  xp	4800 (RM02/RM03)\(ua
--- 147,155 ----
  Disk	Root File System Size
  	  (1K-byte blocks)
  
  hk	4158\(ua
! ra	7942 (All RA, RZ and RD drives except RD52 and RD53)
! 	4850 (RD52/53 - \fBbarely useable\fP)
  rl01	5120\(dd
  rl02	10240\(dd
  xp	4800 (RM02/RM03)\(ua
***************
*** 231,238 ****
  44) may want to start with a \fIm\fP of 4 or 5, faster processors (such as the
  70 and 84) may start with a \fIm\fP of 3 or 4.
  On the other
! hand, the \fIn\fP value is fairly important - it should be the number
! of filesystem blocks contained by one cylinder of the disc.
  These numbers determine the layout of the free list that will be constructed;
  the proper interleaving will help increase the speed of the file system.
  If you have a non-DEC disk that emulates one of the disks listed,
--- 226,234 ----
  44) may want to start with a \fIm\fP of 4 or 5, faster processors (such as the
  70 and 84) may start with a \fIm\fP of 3 or 4.
  On the other
! hand, the \fIn\fP value is moderately important.  It should be the number
! of filesystem blocks contained by one cylinder of the disc but nothing
! bad will happen if you have to guess at a number.
  These numbers determine the layout of the free list that will be constructed;
  the proper interleaving will help increase the speed of the file system.
  If you have a non-DEC disk that emulates one of the disks listed,
***************
*** 252,258 ****
  .TS
  cB s
  l l.
! Disk Interleaving Factor for Disk/CPU Combinations (\fIn\fP)
  DISK
  RL01/2	20
  RK06/7	33
--- 248,254 ----
  .TS
  cB s
  l l.
! Disk Interleaving Factor (\fIn\fP)
  DISK
  RL01/2	20
  RK06/7	33
***************
*** 261,279 ****
  RM05	304
  RP04/5/6	209
  RA60	84
  RA80	217
  RA81	357
  RA82	435
! RD51	36
  RD52	63
  RD53	72
  RD54	127
! RC25	31
  .TE
  .DE
  .KE
  .sp
- For example, for an RP06 on an 11/70, \fIm\fP is 7 and \fIn\fP is 209.
  See
  \fImkfs\fP\|(8)
  for more explanation of the values of \fIm\fP and \fIn\fP.
--- 257,293 ----
  RM05	304
  RP04/5/6	209
  RA60	84
+ RA70	181
+ RA71	357
+ RA72	510
+ RA73	735
  RA80	217
  RA81	357
  RA82	435
! RA90	448
! RA92	448
! RC25	31
! RD31	34
! RD32	51
! RD33	59
  RD52	63
  RD53	72
  RD54	127
! RZ22	66
! RZ23	132
! RZ23L	78
! RZ24	152
! RZ24L	130
! RZ25	279
! RZ26	399
! RZ55	270
! RZ56	405
! RZ57	532
! RZ58	637
  .TE
  .DE
  .KE
  .sp
  See
  \fImkfs\fP\|(8)
  for more explanation of the values of \fIm\fP and \fIn\fP.
***************
*** 289,294 ****
--- 303,309 ----
  .TS
  lw(1.5i) l.
  \fB:\|\fP\fItp\|\fP(0,1)	(\fImkfs\fP is tape file 1)
+ \fBBoot: bootdev=0nnnn bootcsr=0mmmmmm\fP
  \fBMkfs\fP
  \fBfile system:\fP \fIdk\|\fP(0,0)	(root is the first file system on drive 0)
  \fBfile system size:\fP \fIsize\fP	(count of 1024 byte blocks in root)
***************
*** 301,306 ****
--- 316,327 ----
  \fB:\fP	(back at tape boot level)
  .TE
  .DE
+ .sp
+ The number \fBnnnn\fP is the device number of the device (high byte is the
+ major device number and the low byte is the unit number).  The \fBmmmmmm\fP
+ number is the CSR of the device.  This information is mainly used as 
+ a reminder and diagnostic/testing purposes.
+ .sp
  You now have an empty UNIX root file system.
  .NH 3
  Step 3: restoring the root file system
***************
*** 310,326 ****
  .TS
  lw(1.5i) l.
  \fB:\|\fP\fItp\|\fP(0,2)	(\fIrestor\fP is tape file 2)
  \fBRestor\fP
  \fBTape?\fP \fItp\|\fP(0,4)	(root \fIdump\fP is tape file 4)
  \fBDisk?\fP \fIdk\|\fP(0,0)	(into root file system)
! \fBLast chance before scribbling on disk.\fP
  .B
! end of tape
  Exit called
  \fInn\fPBoot
  \fB:\fR	(back at tape boot level)
  .R
  .TE
  .DE
  If you wish, you may use the \fIicheck\fP program on the tape,
  \fItp\|\fP(0,3), to check the consistency of the file system you have just
--- 331,350 ----
  .TS
  lw(1.5i) l.
  \fB:\|\fP\fItp\|\fP(0,2)	(\fIrestor\fP is tape file 2)
+ \fBBoot: bootdev=0nnnn bootcsr=0mmmmmm\fP
  \fBRestor\fP
  \fBTape?\fP \fItp\|\fP(0,4)	(root \fIdump\fP is tape file 4)
  \fBDisk?\fP \fIdk\|\fP(0,0)	(into root file system)
! \fBLast chance before scribbling on disk.\fP  (type a carriage return to start)
  .B
! End of tape			(appears on same line as message above)
  Exit called
  \fInn\fPBoot
  \fB:\fR	(back at tape boot level)
  .R
  .TE
+ .sp
+ This takes about 8 minutes with a TZ30 on a 11/93.
  .DE
  If you wish, you may use the \fIicheck\fP program on the tape,
  \fItp\|\fP(0,3), to check the consistency of the file system you have just
***************
*** 335,340 ****
--- 359,365 ----
  .TS
  lw(1.5i) l.
  \fB:\fP\fIdk\|\fP(0,0)\fIdk\^\fPunix\(ua	(bring in \fIdk\^\fPunix off root system)
+ \fBBoot: bootdev=0nnnn bootcsr=0mmmmmm\fP
  .TE
  .DE
  .FS
***************
*** 349,356 ****
  .DS
  .B
  .\"CHECK
! \*(2B BSD UNIX #1: Sun Jul 1 01:33:03 PDT 1990
!     root@wlonex.imsd.contel.com:/usr/src/sys/GENERIC
  phys mem  = \fI???\fP\(dd
  avail mem = \fI???\fP
  user mem  = \fI???\fP
--- 374,381 ----
  .DS
  .B
  .\"CHECK
! \*(2B BSD UNIX #1: Sat Jul 4 01:33:03 PDT 1992
!     root@wlonex.iipo.gtegsc.com:/usr/src/sys/GENERIC
  phys mem  = \fI???\fP\(dd
  avail mem = \fI???\fP
  user mem  = \fI???\fP
***************
*** 360,366 ****
  .R
  (Information about various devices will print;
  most of them will probably not be found until
! the addresses are set below.)
  .B
  erase=^?, kill=^U, intr=^C
  #
--- 385,394 ----
  .R
  (Information about various devices will print;
  most of them will probably not be found until
! the addresses are set below.  If an error message
! about a configuration is printed the file /unix
! likely does not exist or is not the same as \fIdk\fPunix.
! See below for how to handle this situation.
  .B
  erase=^?, kill=^U, intr=^C
  #
***************
*** 382,388 ****
  high byte is the drive unit number.
  The address for the first controller's CSR is \fIxp_controller\fP plus 4.
  It should be noted that at present the kernel may only be booted from a
! controller at the standard/first CSR.
  If you plan to use any drives other than 0 before you recompile
  the system, you should patch the location for those drives.  The \fIxp_drive\fP
  structure in the \fBGENERIC\fP kernel is 012 bytes long.
--- 410,417 ----
  high byte is the drive unit number.
  The address for the first controller's CSR is \fIxp_controller\fP plus 4.
  It should be noted that at present the kernel may only be booted from a
! controller at the standard/first CSR.  An exception to this is that a MSCP
! based kernel may be booted from drive 0 of any controller.
  If you plan to use any drives other than 0 before you recompile
  the system, you should patch the location for those drives.  The \fIxp_drive\fP
  structure in the \fBGENERIC\fP kernel is 012 bytes long.
***************
*** 407,412 ****
--- 436,449 ----
  can be edited to correspond to your hardware.  However, the tape drive of
  the correct type should have been detected and attached.
  .PP
+ If the error message \fBSERIOUS CONFIGURATION ERROR\fP or 
+ \fB configuration setup error\fP is printed then you must move \fIdk\fPunix
+ to /unix:  mv /\fIdk\fPunix /unix and reboot.  This is because 
+ \fIautoconfig\fP|(8)
+ only looks for the the name unix and this file does not exist
+ in the GENERIC case.   The root filesystem is very full, there is probably
+ not enough room to \fBcp\fP /\fIdk\fPunix /unix, use \fBmv\fP.
+ .PP
  The \*(lqerase ...\*(rq message is part of /.profile
  that was executed by the root shell when it started.  This message
  is present to remind you that the character erase,
***************
*** 455,463 ****
  l l l.
  boot	driver	devices
  _
- bruboot	br	Contel BR1538/BR1711 (not in the \fBGENERIC\fP kernel)
  hkuboot	hk	RK06/07
! rauboot	ra	RA60/80/81/82, RC25, RD51/52/53/54, RX50
  rkuboot	rk	RK05
  rluboot	rl	RL01/02
  si95uboot	si	SI 9500, CDC 9766
--- 492,499 ----
  l l l.
  boot	driver	devices
  _
  hkuboot	hk	RK06/07
! rauboot	ra	All RA, RD, RZ, RX (except RX01,02) and RC25 drives
  rkuboot	rk	RK05
  rluboot	rl	RL01/02
  si95uboot	si	SI 9500, CDC 9766
***************
*** 477,483 ****
  .TS
  lw(1.5i) l.
  .B
! \fInn\fPBoot	\fR(printed by /boot)\fP
  :
  .R
  .TE
--- 513,519 ----
  .TS
  lw(1.5i) l.
  .B
! \fInn\fPBoot from \fIdk\fP(\fIctlr\fP,0,\fIcsr\fP) \fR(printed by /boot)\fP
  :
  .R
  .TE
***************
*** 489,497 ****
  Once /boot is running and prints its ``: '' prompt,
  boot unix as above, using \fIdk\^\fPunix or unix as appropriate.
  .PP
! As distributed /\fIboot\fP will load \fIxp(0,0)unix\fP by default.
! If you are using a different drive type /\fIboot\fP will need to be
! recompiled later.
  .PP
  \fBNOTE:\fP NONE the primary bootstraps have a prompt or alternate program
  name capability because of space considerations.  No diagnostic message
--- 525,532 ----
  Once /boot is running and prints its ``: '' prompt,
  boot unix as above, using \fIdk\^\fPunix or unix as appropriate.
  .PP
! As distributed /\fIboot\fP will load \fIdk\fP(0,0)unix by default if a
! carriage return is typed at the \fB:\fP prompt.
  .PP
  \fBNOTE:\fP NONE the primary bootstraps have a prompt or alternate program
  name capability because of space considerations.  No diagnostic message
***************
*** 507,513 ****
  l l.
  \fB#\fP disk=hk	(if you have RK06's or RK07's)
  \fB#\fP disk=rl	(if you have RL01's or RL02's)
! \fB#\fP disk=ra	(if you have UDA50 or other MSCP storage module drives)
  \fB#\fP disk=xp	(if you have an RP06, RM03, RM05, or other SMD drive)
  .TE
  .DE
--- 542,548 ----
  l l.
  \fB#\fP disk=hk	(if you have RK06's or RK07's)
  \fB#\fP disk=rl	(if you have RL01's or RL02's)
! \fB#\fP disk=ra	(if you have an MSCP drive)
  \fB#\fP disk=xp	(if you have an RP06, RM03, RM05, or other SMD drive)
  .TE
  .DE
***************
*** 520,526 ****
  the system binaries and such and leaves no room for the system
  source.)  The partitions used below are those most appropriate in
  size.  Find the disk you have in the following table and
! execute the commands in the right hand portion of the table:
  .DS
  .TS
  l l.
--- 555,565 ----
  the system binaries and such and leaves no room for the system
  source.)  The partitions used below are those most appropriate in
  size.  Find the disk you have in the following table and
! execute the commands in the right hand portion of the table.  Some
! smaller discs (such as the RD51 and RL01/02) are not listed because they 
! do not have room to even begin loading /usr.  These smaller drives can be 
! used as data discs (perhaps to mount /tmp on) but are not useable for loading
! the /usr file system on to.
  .DS
  .TS
  l l.
***************
*** 530,542 ****
  DEC RP06	\fB#\fP name=xp0c; type=rp06
  DEC RK07	\fB#\fP name=hk0c; type=rk07
  DEC RA60	\fB#\fP name=ra0c; type=ra60
  DEC RA80	\fB#\fP name=ra0c; type=ra80
  DEC RA81	\fB#\fP name=ra0c; type=ra81
! DEC RA82	\fB#\fP name=ra0c; type=ra82
! DEC RC25	\fB#\fP name=ra0c; type=rc25
! DEC RD52	\fB#\fP name=ra0g; type=rd52-rqdx\fIn\fP\(ua
! DEC RD53	\fB#\fP name=ra0d; type=rd53-rqdx\fIn\fP\(ua
! DEC RD54	\fB#\fP name=ra0c; type=rd54-rqdx3
  -
  CDC 9766	\fB#\fP name=xp0e\(dd
  CDC 9775	\fB#\fP name=xp0e\(dd
--- 569,600 ----
  DEC RP06	\fB#\fP name=xp0c; type=rp06
  DEC RK07	\fB#\fP name=hk0c; type=rk07
  DEC RA60	\fB#\fP name=ra0c; type=ra60
+ DEC RA70	\fB#\fP name=ra0d; type=ra70
+ DEC RA71	\fB#\fP name=ra0d; type=ra71
+ DEC RA72	\fB#\fP name=ra0d; type=ra72
+ DEC RA73	\fB#\fP name=ra0d; type=ra73
  DEC RA80	\fB#\fP name=ra0c; type=ra80
  DEC RA81	\fB#\fP name=ra0c; type=ra81
! DEC RA82	\fB#\fP name=ra0d; type=ra82
! DEC RA90	\fB#\fP name=ra0d; type=ra90
! DEC RA91	\fB#\fP name=ra0d; type=ra91
! DEC RA92	\fB#\fP name=ra0d; type=ra92
! DEC RD32	\fB#\fP name=ra0g; type=rd32
! DEC RD33	\fB#\fP name=ra0g; type=rd33
! DEC RD52	\fB#\fP name=ra0g; type=rd52
! DEC RD53	\fB#\fP name=ra0d; type=rd53
! DEC RD54	\fB#\fP name=ra0g; type=rd54
! DEC RZ22	\fB#\fP name=ra0g; type=rz22
! DEC RZ23	\fB#\fP name=ra0g; type=rz23
! DEC RZ23L	\fB#\fP name=ra0g; type=rz23l
! DEC RZ24	\fB#\fP name=ra0d; type=rz24
! DEC RZ24L	\fB#\fP name=ra0d; type=rz24l
! DEC RZ25	\fB#\fP name=ra0d; type=rz25
! DEC RZ26	\fB#\fP name=ra0d; type=rz26
! DEC RZ55	\fB#\fP name=ra0d; type=rz55
! DEC RZ56	\fB#\fP name=ra0d; type=rz56
! DEC RZ57	\fB#\fP name=ra0d; type=rz57
! DEC RZ58	\fB#\fP name=ra0d; type=rz58
  -
  CDC 9766	\fB#\fP name=xp0e\(dd
  CDC 9775	\fB#\fP name=xp0e\(dd
***************
*** 563,569 ****
  DEC TM02/03, TE16/TU45/TU77	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV ht0; sync
  DEC TS11, TU80/TS05	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV ts0; sync
  DEC TM11, TU10/TE10/TS03	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync
! DEC TQK50, TK50/TU81	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tu0; sync
  EMULEX TC11	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync
  .TE
  .DE
--- 621,627 ----
  DEC TM02/03, TE16/TU45/TU77	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV ht0; sync
  DEC TS11, TU80/TS05	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV ts0; sync
  DEC TM11, TU10/TE10/TS03	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync
! DEC TMSCP, TK50/TZ30/TU81	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tu0; sync
  EMULEX TC11	\fB#\fP cd /dev; rm *mt*; ./MAKEDEV tm0; sync
  .TE
  .DE
***************
*** 590,597 ****
  \fB#\fP mt rew
  \fB#\fP mt fsf 5
  \fB#\fP tar xpbf 20 /dev/rmt12 	(extract all of usr except usr/src)
! (this takes about 15-20 minutes except for the TK50 which is \fBmuch\fP
! slower)
  .TE
  .DE
  The data on the sixth tape file has now been extracted.
--- 648,655 ----
  \fB#\fP mt rew
  \fB#\fP mt fsf 5
  \fB#\fP tar xpbf 20 /dev/rmt12 	(extract all of usr except usr/src)
! (this takes about 15-20 minutes except for the TK50 and TZ30 which are 
! \fBmuch\fP slower)
  .TE
  .DE
  The data on the sixth tape file has now been extracted.
***************
*** 628,640 ****
  should look something like:
  .DS
  .B
! ** /dev/r\fIxx\fP0h
  ** Last Mounted on /usr
  ** Phase 1 - Check Blocks and Sizes
  ** Phase 2 - Check Pathnames
  ** Phase 3 - Check Connectivity
  ** Phase 4 - Check Reference Counts
! ** Phase 5 - Check Cyl groups
  671 files, 3497 used, 137067 free
  .R
  .DE
--- 686,702 ----
  should look something like:
  .DS
  .B
! ** /dev/r\fIxx\fP0g
! File System: /usr
! 
! NEED SCRATCH FILE (179 BLKS)
! ENTER FILENAME:  /tmp/xxx
  ** Last Mounted on /usr
  ** Phase 1 - Check Blocks and Sizes
  ** Phase 2 - Check Pathnames
  ** Phase 3 - Check Connectivity
  ** Phase 4 - Check Reference Counts
! ** Phase 5 - Check Free List
  671 files, 3497 used, 137067 free
  .R
  .DE
***************
*** 665,672 ****
  \fB#\fP tar xpb 20
  .DE
  If you get an error at this point, most likely it was
! a problem with tape positioning.
! You can reposition the tape by rewinding it.
  .NH 2
  Additional conversion information
  .PP
--- 727,735 ----
  \fB#\fP tar xpb 20
  .DE
  If you get an error at this point, most likely it was
! a problem with tape positioning.  Rewind the tape and
! use the \fBmt\fP command to skip files, then retry the
! \fBtar\fP command.
  .NH 2
  Additional conversion information
  .PP
Newsgroups: comp.bugs.2bsd