*** /old/doc/2.10/setup.2.11/0.t	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
*** /old/doc/2.10/setup.2.11/1.t	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:
*** /old/doc/2.10/setup.2.11/2.t	Wed Dec 19 09:48:28 1990
--- /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.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.
  .\"
! .\"	@(#)2.t	1.4 (GTE) 8/24/92
  .\"
  .ds lq ``
  .ds rq ''
***************
*** 79,84 ****
--- 79,90 ----
  sure that the write ring is not inserted.
  Then use the normal bootstrap ROM, console monitor or other
  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
  172526 is the address of the TM-11 current memory address register;
***************
*** 87,97 ****
  .DS
  .TS
  l l.
  012700	(mov $172526, r0)
  172526
  010040	(mov r0, -(r0))
  012740	(mov $60003, -(r0))
! 060003
  000777	(br .)
  .TE
  .DE
--- 93,105 ----
  .DS
  .TS
  l l.
+ 012700  (mov $unit, r1)
+ 000000    (normally unit 0)
  012700	(mov $172526, r0)
  172526
  010040	(mov r0, -(r0))
  012740	(mov $60003, -(r0))
! 060003    (if unit 1 use 060403, etc)
  000777	(br .)
  .TE
  .DE
***************
*** 101,141 ****
  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
! The bootstrap can be forced to set up the machine for a different
! class of PDP-11 by placing an appropriate value in the console switch register
! (if there is one) while booting it.
! The value to use is the PDP-11 class, interpreted as an \fIoctal\fP number
! (use, for example, 070 for an 11/70).
! \fBWarning:\fP  some old DEC bootstraps use the switch
! register to indicate where to boot from.
! On such machines, if the value in the switch register indicates
! an incorrect CPU, be sure to reset the switches immediately after
! initiating the tape bootstrap.
  .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
***************
*** 155,164 ****
  Disk	Root File System Size
  	  (1K-byte blocks)
  
- br	9120 (T300)
  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
***************
*** 199,205 ****
  072	Ampex Capricorn
  073	SI, CDC 9775 (direct)
  074	SI 6100, Fuji Eagle 2351A
! 075	Emulex SC01B or SI 9400, Fuji 160
  076	Emulex SC-21, Ampex 815 cylinder RM05
  077	Diva Comp V, Ampex 9300
  .TE
--- 190,196 ----
  072	Ampex Capricorn
  073	SI, CDC 9775 (direct)
  074	SI 6100, Fuji Eagle 2351A
! 075	Emulex SC01B/SC03B or SI 9400, Fuji 160 (in RM80 mode)
  076	Emulex SC-21, Ampex 815 cylinder RM05
  077	Diva Comp V, Ampex 9300
  .TE
***************
*** 207,231 ****
  Check the drive type number in your controller manual,
  or halt the CPU and examine this register.
  If the value does not correspond to the actual drive type,
! you must place the correct value in the switch
! register after the tape bootstrap is running
! and before any attempt is made to access the drive.
  This will override the drive type register.
  This value must be present at the time each program
  (including the bootstrap itself) first tries to access the disk.
! On machines without a switch register, the \fIxptype\fP 
! variable can be patched in memory.  After starting each utility
  but before accessing the disk, halt the CPU, place the new drive type
! number at the proper memory location with the console switches or monitor,
! and then continue.  The location of \fIxptype\fP in each utility is
! .\"CHECK - XXX
! mkfs:  034146, restor:  040054, icheck:  035002 and boot:  0634640
! (the location for boot is higher because it relocates itself).
  Once UNIX itself is booted (see section ``\fBStep 4: booting UNIX\fP'') you must
! patch it also.
  .PP
  Finally, determine the proper interleaving factors \fIm\fP and \fIn\fP
! for your disk and CPU combination from the following table.
  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,
--- 198,234 ----
  Check the drive type number in your controller manual,
  or halt the CPU and examine this register.
  If the value does not correspond to the actual drive type,
! you must patch the \fIxptype\fP variable in memory
! before any attempt is made to access the drive.
  This will override the drive type register.
  This value must be present at the time each program
  (including the bootstrap itself) first tries to access the disk.
! After starting each utility
  but before accessing the disk, halt the CPU, place the new drive type
! number at the proper memory location using the front panel or monitor
! and then continue.  The address of \fIxptype\fP in each utility is
! printed out on the console the first time the disc is accessed.
! Because \fBboot\fP relocates itself you must remember to add 0600000 
! to the address of \fIxptype\fP.
! .PP
  Once UNIX itself is booted (see section ``\fBStep 4: booting UNIX\fP'') you must
! patch it also.  The \fIxp\fP driver in the \fBGENERIC\fP kernel prints to
! the console the address of \fIxp_drive\fP and \fIxp_controller\fP and delays
! for about 10 seconds.
  .PP
  Finally, determine the proper interleaving factors \fIm\fP and \fIn\fP
! for your disk from the following table.  Extensive testing has demonstrated
! that the choice of \fIm\fP is non critical (performance of a file system
! varying only by 3 to 4% for a wide range of \fIm\fP values).  Values for
! \fIm\fP within the range from  2 to 5 give almost identical performance.
! Increasing \fIm\fP too much actually causes degraded performance because
! the free blocks are too far apart.  Slower processors (such as the 73 and
! 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,
***************
*** 234,297 ****
  (rather than the controller mapping onto a different physical disk).
  Also, the rotational speed must be the same as the DEC disk
  for these numbers to apply.
  .KS
  .DS
  .TS
! cB s s s s s s s s
! l l l l l l l l l.
! Disk Interleaving Factors for Disk/CPU Combinations (\fIm\fP/\fIn\fP)
! CPU	23	24	34	40	44	45	53	55
  DISK
! RL01/2	7/10	6/10	6/10	6/10	4/10	5/10	4/10	5/10
! RK06/7	8/33	7/33	6/33	6/33	4/33	5/33	4/33	5/33
! RM02	11/80	10/80	8/80	8/80	6/80	7/80	6/80	7/80
! RM03	16/80	15/80	12/80	12/80	8/80	11/80	8/80	11/80
! RM05	16/304	15/304	12/304	12/304	8/304	11/304	8/304	11/304
! RP04/5/6	11/209	10/209	8/209	8/209	6/209	7/209	6/209	7/209
! RA60	21/84	21/84	17/84	17/84	12/84	15/84	12/84	15/84
! RA80	16/217	16/217	13/217	13/217	9/217	11/217	9/217	11/217
! RA81	26/357	26/357	21/357	21/357	14/357	18/357	14/357	17/357
! RA82	26/435	26/435	21/435	21/435	14/435	18/435	14/435	17/435
! RD51	1/36	1/36	1/36	1/36	1/36	1/36	1/36	1/36
! RQDX2\(ua	2/36	2/36	2/36	2/36	2/36	2/36	2/36	2/36
! RQDX3\(ua	7/36	7/36	7/36	7/36	7/36	7/36	7/36	7/36
! RC25	15/31	15/31	13/31	13/31	9/31	11/31	9/31	11/31
  .TE
- 
- .TS
- cB s s s s s
- l l l l l l.
- Disk Interleaving Factors for Disk/CPU Combinations (\fIm\fP/\fIn\fP)
- CPU	60	70	73	83	84	93	94
- DISK
- RL01/2	5/10	3/10	4/10	4/10	3/10	3/10	3/10
- RK06/7	5/33	3/33	4/33	4/33	3/33	3/33	3/33
- RM02	7/80	5/80	6/80	6/80	5/80	5/80	5/80
- RM03	11/80	7/80	9/80	9/80	7/80	7/80	7/80
- RM05	11/304	7/304	8/304	8/304	7/304	7/304	7/304
- RP04/5/6	7/209	5/209	6/209	6/209	5/209	5/209	5/209
- RA60	15/84	10/84	12/84	12/84	10/84	10/84	10/84
- RA80	11/217	7/217	9/217	9/217	7/217	7/217	7/217
- RA81	18/357	12/357	14/357	14/357	12/357	12/357	12/357
- RA82	18/435	12/435	14/435	14/435	12/435	12/435	12/435
- RD51	1/36	1/36	1/36	1/36	1/36	1/36	1/36
- RQDX2\(ua	2/36	2/36	2/36	2/36	2/36	2/36	2/36
- RQDX3\(ua	7/36	7/36	7/36	7/36	7/36	7/36	7/36
- RC25	11/31	7/31	9/31	9/31	7/31	7/31	7/31
- .TE
  .DE
  .KE
  .sp
- .FS
- .IP \(ua
- \fIm\fP/\fIn\fP numbers for RD52/53/54's are based on controller type
- (RQDX2 or RQDX3) rather than drive type.
- .FE
- 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.
  For \fIm\fP/\fIn\fP numbers for other drive types see \fI/etc/disktab\fP.
  .PP
  Then run the standalone version of the \fImkfs\fP (8) program.
  In the following procedure, substitute the correct types
--- 237,300 ----
  (rather than the controller mapping onto a different physical disk).
  Also, the rotational speed must be the same as the DEC disk
  for these numbers to apply.
+ .PP
+ The earlier tables went into great detail specifying separate tables for
+ each cpu type.  This is not necessary.  In several cases the \fIm\fP
+ values were too high or the \fIn\fP values were too low.  The following
+ table specifies the \fIn\fP parameter only.  The \fIm\fP parameter selection
+ was explained in a previous paragraph.
  .KS
  .DS
  .TS
! cB s
! l l.
! Disk Interleaving Factor (\fIn\fP)
  DISK
! RL01/2	20
! RK06/7	33
! RM02	80
! RM03	80
! 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.
  For \fIm\fP/\fIn\fP numbers for other drive types see \fI/etc/disktab\fP.
+ \fIn\fP would be calculated using the \fBnt\fP and \fBns\fP parameters
+ from \fI/etc/disktab\fP.  For a disc with 512 byte sectors compute \fIn\fP
+ by multiplying \fBns\fP times \fBnt\fP and dividing the result by 2.
  .PP
  Then run the standalone version of the \fImkfs\fP (8) program.
  In the following procedure, substitute the correct types
***************
*** 300,305 ****
--- 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)
***************
*** 312,317 ****
--- 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
***************
*** 321,337 ****
  .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
***************
*** 346,351 ****
--- 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
***************
*** 360,367 ****
  .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
***************
*** 371,377 ****
  .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,397 ****
  \fBNote:\fP If you are booting from an \fIxp\fP with a drive type
  that is not recognized, it will be necessary to patch the system before
  it first accesses the root file system.
! Halt the processor after it
! has begun printing the version string but before it has finished printing
! the ``mem = ...'' strings.
  Place the drive type number corresponding to your drive
! .\"CHECK - XXX
! at location 010622;
! the address for
! the first controller's CSR is 046552.
  If you plan to use any drives other than 0 before you recompile
! the system, you should patch these locations.
  Make the patches and continue the CPU.
  The value before patching must be zero.  If it is not, you have halted too
  late and should try again.
--- 399,420 ----
  \fBNote:\fP If you are booting from an \fIxp\fP with a drive type
  that is not recognized, it will be necessary to patch the system before
  it first accesses the root file system.
! The \fBGENERIC\fP kernel \fIxp\fP driver prints out the addresses of
! \fIxp_drive\fP and \fIxp_controller\fP and then delays for 10 seconds
! (approximately).
! Halt the processor after it has printed out the addresses
! but before the disk has been accessed.
! .PP
  Place the drive type number corresponding to your drive
! at the address of \fIxp_drive\fP plus 2.  Modify only the low byte, the
! 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.
  Make the patches and continue the CPU.
  The value before patching must be zero.  If it is not, you have halted too
  late and should try again.
***************
*** 413,418 ****
--- 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,
***************
*** 461,469 ****
  l l l.
  boot	driver	devices
  _
- bruboot	br	Contel BR1538/BR1711
  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
***************
*** 472,478 ****
  rm03uboot	xp	RM02/03
  rm05uboot	xp	RM05 or SI 9500, CDC 9766
  si51uboot	xp	SI 6100, Fujitsu Eagle 2351A
! si94uboot	xp	Emulex SC01B or SI 9400, Fujitsu 160
  .TE
  .DE
  Once this is done, booting from this disk will load and execute the block
--- 502,508 ----
  rm03uboot	xp	RM02/03
  rm05uboot	xp	RM05 or SI 9500, CDC 9766
  si51uboot	xp	SI 6100, Fujitsu Eagle 2351A
! si94uboot	xp	Emulex SC01B/SC03B or SI 9400, Fujitsu 160
  .TE
  .DE
  Once this is done, booting from this disk will load and execute the block
***************
*** 482,496 ****
  .DS
  .TS
  lw(1.5i) l.
- \fB>boot\fP	(printed by some block 0 boots)
- 
  .B
! \fInn\fPBoot	\fR(printed by /boot)\fP
  :
  .R
  .TE
  .DE
- The '>' is the prompt from the first bootstrap.
  It automatically boots /\fIboot\fP for you;
  if /\fIboot\fP is not found, the system will hang/loop forever.
  It is a very small and simple program, however, and can only
--- 512,523 ----
  .DS
  .TS
  lw(1.5i) l.
  .B
! \fInn\fPBoot from \fIdk\fP(\fIctlr\fP,0,\fIcsr\fP) \fR(printed by /boot)\fP
  :
  .R
  .TE
  .DE
  It automatically boots /\fIboot\fP for you;
  if /\fIboot\fP is not found, the system will hang/loop forever.
  It is a very small and simple program, however, and can only
***************
*** 498,506 ****
  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
***************
*** 516,522 ****
  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
***************
*** 529,535 ****
  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.
***************
*** 539,551 ****
  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
***************
*** 557,568 ****
  .DE
  .FS
  .IP \(ua
- The type of controller the RD52 and RD53 are on (RQDX2 or RQDX3) must
- be specified for proper file system free list spacing to be computed.  If
- you don't know what controller your RD is on, it is all right to guess,
- though the created file system may not perform as well.  The RD54 requires
- the RQDX3 controller not the RQDX2.
- .IP \(dd
  Unfortunately the \fInewfs\fP(8) program is relatively primitive and
  doesn't know the free list spacing for these non-DEC drives.  An
  appropriate \fImkfs\fP(8) command will have to be substituted for the
--- 606,611 ----
***************
*** 570,593 ****
  [hopefully] appropriate free list \fIm/n\fP numbers for some non-DEC
  disks.
  .FE
- Find the type of cpu that you have in the following table and
- commands in the right hand portion of the table:
- .DS
- .TS
- l l.
- PDP-11	Command
- ---	-------
- 44	\fB#\fP cpu=44
- 45	\fB#\fP cpu=45
- 55	\fB#\fP cpu=45
- 70	\fB#\fP cpu=70
- 73	\fB#\fP cpu=73
- 83	\fB#\fP cpu=83
- 84	\fB#\fP cpu=84
- 93	\fB#\fP cpu=93
- 94	\fB#\fP cpu=94
- .TE
- .DE
  Find the tape you have in the following table and execute the
  commands in the right hand portion of the table:
  .DS
--- 613,618 ----
***************
*** 596,602 ****
  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	\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
***************
*** 613,627 ****
  \fBNew password:\fP	(password will not echo)
  \fBRetype new password:\fP
  \fB#\fP hostname \fImysitename\fP	(set your hostname)
! \fB#\fP newfs ${name} ${type} ${cpu}	(create empty user file system)
  (this takes a few minutes)
  \fB#\fP mount /dev/${name} /usr	(mount the usr file system)
  \fB#\fP cd /usr	(make /usr the current directory)
  \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.
--- 638,655 ----
  \fBNew password:\fP	(password will not echo)
  \fBRetype new password:\fP
  \fB#\fP hostname \fImysitename\fP	(set your hostname)
! \fB#\fP newfs ${name} ${type}  (create empty user file system)
  (this takes a few minutes)
+ (if you wish to specify a different \fIm\fP value, use a command of the 
+  form: newfs -m # ${name} ${type}
+  where # is the \fIm\fP parameter and must be between 1 and 31)
  \fB#\fP mount /dev/${name} /usr	(mount the usr file system)
  \fB#\fP cd /usr	(make /usr the current directory)
  \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.
***************
*** 658,670 ****
  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
***************
*** 695,702 ****
  \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
*** /old/doc/2.10/setup.2.11/3.t	Sat Dec  8 18:38:07 1990
--- /usr/doc/2.10/setup.2.11/3.t	Tue May 28 16:09:47 1991
***************
*** 309,315 ****
  It includes the terminal type and security options that were previously
  in /etc/ttytype and /etc/securettys.
  .PP
! \fIsyslog\fP is the same as it ws under \(*Ps.
  See \fIsyslogd\fP\|(8) for details.
  It is used by many of the system daemons
  to monitor system problems more closely, for example
--- 309,315 ----
  It includes the terminal type and security options that were previously
  in /etc/ttytype and /etc/securettys.
  .PP
! \fIsyslog\fP is the same as it was under \*(Ps.
  See \fIsyslogd\fP\|(8) for details.
  It is used by many of the system daemons
  to monitor system problems more closely, for example
*** /old/doc/2.10/setup.2.11/4.t	Mon Dec 10 14:39:18 1990
--- /usr/doc/2.10/setup.2.11/4.t	Tue Dec 31 23:55:47 1991
***************
*** 28,48 ****
  .NH 2
  Creating a UNIX boot
  .PP
! The version of \fI/boot\fP distributed with the system is set up to boot
! \fIxp(0,0)unix\fP.  If you want to boot from a different file system
! easily and have auto-reboot supported, you will have to recompile the boot.
! This is done very simply as follows:
! .DS
! \fB#\fP cd /sys/pdpstand
! \fB#\fP make clean
! \fB#\fP make RB_DEFNAME="\fIdk\fP(\fIunit\fP,\fPoffset\fP)unix" boot
! \fB#\fP make install
! .DE
! Where \fIdk\fP is the two letter code for the device you want to auto-boot
! from, \fIunit\fP is the slave unit of said device, and \fIoffset\fP is the
! offset in \fI512-byte blocks\fP from the beginning of the selected disk,
! or the file number of the selected tape (note that auto-booting from tape
! is possible, but not recommended.)
  .NH 2
  Kernel configuration
  .PP
--- 28,40 ----
  .NH 2
  Creating a UNIX boot
  .PP
! \fI/boot\fP uses the device information passed to it from the bootstrap
! in determining the device, unit and file to load.   If an autoreboot
! is being done the kernel will have passed the device information to the 
! bootstrap as well as setting the autoreboot flag.
! .PP
! \fI/boot\fP does not require recompilation to adapt to a new autoreboot
! device.
  .NH 2
  Kernel configuration
  .PP
***************
*** 451,458 ****
  .DS
  \fB#\fP cd /dev
  \fB#\fP MAKEDEV ra1
! \fB#\fP newfs ra1c ra80 \fIcpu_type\fP
  (information about file system prints out)
  \fB#\fP mkdir /mnt
  \fB#\fP mount /dev/ra1c /mnt
  .DE
--- 443,452 ----
  .DS
  \fB#\fP cd /dev
  \fB#\fP MAKEDEV ra1
! \fB#\fP newfs ra1c ra80
  (information about file system prints out)
+ (to specify an alternate \fIm\fP value: newfs -m # ra1c ra80)
+ (where # is between 1 and 31)
  \fB#\fP mkdir /mnt
  \fB#\fP mount /dev/ra1c /mnt
  .DE
*** /old/lib/bugformat	Tue May 29 08:32:04 1990
--- /usr/lib/bugformat	Thu Dec 19 19:06:08 1991
***************
*** 1,5 ****
  Subject: Short summary of the problem
! Index:	<source directory>/<source file> 2.10BSD
  
  Description:
  	Detailed description of the problem, suggestion, or complaint.
--- 1,5 ----
  Subject: Short summary of the problem
! Index:	<source directory>/<source file> 2.11BSD
  
  Description:
  	Detailed description of the problem, suggestion, or complaint.
*** /old/lib/uucp/USERFILE	Sat Nov 15 22:45:12 1986
--- /usr/lib/uucp/USERFILE	Sun Mar 17 03:08:46 1991
***************
*** 1,3 ****
- ,rome /
- ,radc-lonex /
  , /usr/spool/uucppublic
--- 1 ----
*** /old/src/bin/adb/opset.c	Sun Dec 25 20:51:01 1988
--- /usr/src/bin/adb/opset.c	Tue Jun 30 22:54:03 1992
***************
*** 118,123 ****
--- 118,127 ----
  	0000000, 0170002, NOADDR, "seti",
  	0000000, 0170011, NOADDR, "setd",
  	0000000, 0170012, NOADDR, "setl",
+ 	0000000, 0000007, NOADDR, "mfpt",
+ 	0000077, 0007000, JMP, "csm",
+ 	0000077, 0007300, SINGLW, "wrtlck",
+ 	0000077, 0007200, SINGLW, "tstset",
  	0000777, 0004000, JSR,    "jsr",
  	0000777, 0074000, DOUBLE, "xor",
  	0000007, 0000200, SINGLE, "rts",
*** /old/src/bin/as/as12.s	Wed Dec 13 16:43:06 1989
--- /usr/src/bin/as/as12.s	Thu Aug 27 20:40:36 1992
***************
*** 26,32 ****
  	mov	$4,r1
  2:
  	clr	r2
! 	dvd	$10.,r2
  	add	$'0,r3
  	movb	r3,-(r0)
  	mov	r2,r3
--- 26,32 ----
  	mov	$4,r1
  2:
  	clr	r2
! 	div	$10.,r2
  	add	$'0,r3
  	movb	r3,-(r0)
  	mov	r2,r3
*** /old/src/bin/as/as14.s	Wed Dec 13 16:43:14 1989
--- /usr/src/bin/as/as14.s	Thu Aug 27 20:41:07 1992
***************
*** 146,154 ****
  	cmp	r0,$'9
  	bgt	1f
  	sub	$'0,r0
! 	mpy	$10.,r5
  	add	r0,r5
! 	als	$3,r1
  	add	r0,r1
  	br	1b
  1:
--- 146,154 ----
  	cmp	r0,$'9
  	bgt	1f
  	sub	$'0,r0
! 	mul	$10.,r5
  	add	r0,r5
! 	ash	$3,r1
  	add	r0,r1
  	br	1b
  1:
