Installing UNIX Sixth Edition - Revision history

Jnc: /* Installation tape contents */ Also a directory

2024-06-28T18:58:52Z

‎Installation tape contents: Also a directory

Jnc: /* Programs */ Mention devices for each driver

2024-03-27T03:35:07Z

‎Programs: Mention devices for each driver

Jnc: /* External links */ +source for all the modules

2024-02-15T18:17:40Z

‎External links: +source for all the modules

Jnc: Down side of distributing as file system images

2023-03-18T11:20:52Z

Down side of distributing as file system images

Jnc: /* See also */ Consistent caps

2021-03-10T17:08:52Z

‎See also: Consistent caps

Jnc: /* See also */ comp list

2019-03-03T01:42:10Z

‎See also: comp list

Jnc: /* See also */ add

2019-01-29T21:51:28Z

‎See also: add

Jnc: better cat

2018-12-14T19:09:42Z

better cat

Jnc: +cat

2018-12-14T13:41:39Z

+cat

Jnc: Proper conjjunction

2018-06-01T20:43:03Z

Proper conjjunction

@@ Line 17: / Line 17: @@
 ==Installation tape contents==
-The V6 distribution tape contains a large number of 512-byte records; the first 101 512-byte tape blocks contain a number of small programs, including tape and disk bootstraps, and programs to copy the tape contents to disk.
+The V6 distribution tape contains a large number of 512-byte records; the first 101 512-byte tape blocks contain a number of small programs, including tape and disk bootstraps, and programs to copy the tape contents to disk, and a [[directory]] which indicates what files are there.
-* Block 0 on tape - mboot (TM11 tape bootstrap)
+* Block 0 on tape - 'mboot' (TM11 tape bootstrap)
-* Block 1 on tape - hboot (TM02 tape bootstrap)
+* Block 1 on tape - 'hboot' (TM02 tape bootstrap)
 * Block 2-24 - a tp-format directory section for the following section
 * Block 25-xx - stand-alone programs, including tape->disk copy programs
-* Block 98 on tape - hpuboot (RP04 disk bootstrap)
+* Block 98 on tape - 'hpuboot' (RP04 disk bootstrap)
-* Block 99 on tape - rpuboot (RP03 disk bootstrap)
+* Block 99 on tape - 'rpuboot' (RP03 disk bootstrap)
-* Block 100 on tape - rkuboot (RK05 disk bootstrap)
+* Block 100 on tape - 'rkuboot' (RK05 disk bootstrap)
-After that, blocks 101-4100 are an image of an RK05 pack containing a UNIX root partition, which contains everything needed to allow UNIX to run: all the commands, and the source for the operating system (to allow reconfiguration of the OS to match the system's hardware); blocks 4101-8100 are an image of an RK05 pack which contains source for all the commands; and blocks 8101-12100 are an RK05 pack image which contains all the documentation.
+After that, blocks 101-4100 are an image of an RK05 pack containing a UNIX root [[partition]], which contains everything needed to allow UNIX to run: all the commands, and the [[source]] for the operating system (to allow reconfiguration of the OS to match the system's hardware); blocks 4101-8100 are an image of an RK05 pack which contains source for all the commands; and blocks 8101-12100 are an RK05 pack image which contains all the documentation.
-The copying programs (6 of them, one for each possible tape/disk combination) are stored in the block "25-xx" area, along with a number of other miscellanous small stand-alone programs.
+The copying programs (6 of them, one for each possible tape/disk combination) are stored in the block "25-xx" area, along with a number of other miscellaneous small stand-alone programs.
 ===Tp-format directory===

@@ Line 39: / Line 39: @@
 ==Programs==
-The first stage tape bootstrap is "tpboot.s"; this is assembled with either "tm.s" or "ht.s" to produce the first-stage bootstrap that goes in blocks 0 and 1 of the tape. It takes as input a file-name, for installing UNIX, normally 'xxyy' as above, entered at the console. It then reads the tp-format directory off the tape, and looks for that file-name in it, and if found, loads and starts it.
+The first stage tape bootstrap is "tpboot.s"; this is assembled with either "tm.s" (the TM11 [[device driver]]) or "ht.s" (the TM02 driver) to produce the first-stage bootstrap that goes in blocks 0 and 1 of the tape. It takes as input a file-name, for installing UNIX, normally 'xxyy' as above, entered at the console. It then reads the tp-format directory off the tape, and looks for that file-name in it, and if found, loads and starts it.
-"mcopy.s" is the tape copier program, assembled with either "tm.s" or "ht.s", and one of "rk.s", "rp.s" and "hp.s", to produce the 'xxyy' files above.
+"mcopy.s" is the tape copier program, assembled with either "tm.s" or "ht.s", and one of "rk.s" (RK11 driver), "rp.s" (RP11 driver) and "hp.s" (RP04 driver), to produce the 'xxyy' files above.
 "fsboot.s" is the disk bootstrap, assembled with "rk.s", "rp.s" or "hp.s" to produce the various disk bootstraps.

@@ Line 58: / Line 58: @@
 ** [[Running UNIX v6 in SIMH]]
 * [[Installing UNIX Sixth Edition on Ersatz-11]]
 [[Category: UNIX]]

@@ Line 1: / Line 1: @@
-There is a [[Setting up UNIX - Sixth Edition]] document, but it is mostly a checklist of what to do to install [[UNIX Sixth Edition]] on a [[PDP-11]] (one of the models supporting [[PDP-11 Memory Management|memory management]]); it does not provide any technical detail on what is actually happening.
+There is a [[Setting up UNIX - Sixth Edition]] document, but it is mostly a checklist of what to do to install [[UNIX Sixth Edition]] on a [[PDP-11]] (one of the PDP-11 models supporting [[PDP-11 Memory Management|memory management]]); it does not provide any technical detail on what is actually happening.
 UNIX Sixth Edition (often called UNIX V6) was normally installed from a tape; it was possible to install UNIX on a machine without a [[magnetic tape drive|tape drive]], by copying [[disk pack]]s with UNIX on them, but this was not Bell Laboratories' usual distribution method. Thus, installing UNIX V6 usually required a machine with a tape drive, and one or more [[disk drive]]s.
@@ Line 5: / Line 5: @@
 The supported tape drives were the [[TU10]], on a [[TM11]] [[UNIBUS]] controller; or the [[TU16]], on a [[TM02]] [[MASSBUS]] controller. The supported disk drives were the [[RK05]], on an [[RK11]] UNIBUS controller, the [[RP03]] on an [[RP11]] UNIBUS controller, or the [[RP04]], with an internal controller which connected to a MASSBUS.
-The installation process for V6 seems superficially to be much like [[Installing UNIX Seventh Edition|that for V7]], in that a tape is used, which contained a number of small stand-alone programs, followed by the [[UNIX file system|file-systems]], but the similarity is purely superficial; the details of the process are wholly different.
+The installation process for V6 seems superficially to be much like [[Installing UNIX Seventh Edition|that for V7]], in that a tape is used, which contained a number of small stand-alone programs, followed by the [[file system]]s, but the similarity is purely superficial; the details of the process are wholly different.
 ==Installation process==
@@ Line 11: / Line 11: @@
 The first stage is a tape bootstrap (loaded from block 0, or block 1, depending on the tape drive/controller on the system). That is then used to load an intermediate stage, a tape to disk copier (named 'xxyy',  where 'xx' is "tm" or "ht", and 'yy' is "rk", "rp" or "hp"; as appropriate to the machine's hardware configuration).
-That program is used to copy 3 complete file system images from the tape, to disk pack(s); it is also used to install an appropriate disk bootstrap in block 0 of the root disk drive. Once that has all been done, it is possible to boot UNIX from disk.
+That program is used to copy 3 complete RK pack file system images from the tape, to disk pack(s); it is also used to install an appropriate disk bootstrap in block 0 of the root disk drive. Once that has all been done, it is possible to boot UNIX from disk.
-It is not possible to boot V6 Unix directly from a V6 distribution tape (as one can with V7); all one can do is copy the disk images from the tape to the disk, and then boot from the disk.
+It is not possible to boot V6 Unix directly from a V6 distribution tape (as one can with V7); all one can do is copy the disk images from the tape to the disk, and then boot from the disk. Also, since the file systems are provided as images of complete functional [[UNIX file system]]s, it is not possible to install them properly on different disks; to put the contents on different sized disks, one has to perform additional steps once the system is up and running.
 ==Installation tape contents==

@@ Line 50: / Line 50: @@
 * [[UNIX V6 internals]]
-* [[Unix V6 kernel memory layout]]
+* [[UNIX V6 kernel memory layout]]
-** [[Unix V6 dump analysis]]
+** [[UNIX V6 dump analysis]]
 * [[Setting up UNIX Sixth Edition]]
 ** [[Upgrading UNIX Sixth Edition]]
 ** [[Running UNIX V6 on an -11/23]]
-* [[Installing Unix v6 (PDP-11) on SIMH]]
+* [[Installing UNIX v6 (PDP-11) on SIMH]]
-** [[Running Unix v6 in SIMH]]
+** [[Running UNIX v6 in SIMH]]
 * [[Installing UNIX Sixth Edition on Ersatz-11]]
 [[Category: UNIX]]

← Older revision		Revision as of 21:51, 29 January 2019
Line 46:		Line 46:

	mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).		mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).
		+
		+	==See also==
		+
		+	* [[Unix V6 kernel memory layout]]
		+	** [[Unix V6 dump analysis]]
		+	* [[Upgrading UNIX Sixth Edition]]
		+	* [[Running UNIX V6 on an -11/23]]
		+	* [[Unix V6 kernel memory layout]]
		+	* [[Installing Unix v6 (PDP-11) on SIMH]]
		+	** [[Running Unix v6 in SIMH]]
		+	* [[Installing UNIX Sixth Edition on Ersatz-11]]

	[[Category: UNIX]]		[[Category: UNIX]]

← Older revision		Revision as of 19:09, 14 December 2018
Line 47:		Line 47:
	mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).		mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).

−	[[Category: ~~Unix OS's~~]]	+	[[Category: UNIX]]

← Older revision		Revision as of 13:41, 14 December 2018
Line 46:		Line 46:

	mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).		mcopy.s uses R5 (which contains a pointer to the console print/input routines), but does not set it up (or contain the console routines); it is set up by tpboot.s, which will have run previously (to load the appropriate disk-controller-specific version of mcopy off the tape).
		+
		+	[[Category: Unix OS's]]