Setting up the Third Berkeley Software Tape - Revision history

Jnc: Better cat

2023-01-17T01:01:19Z

Better cat

← Older revision		Revision as of 01:01, 17 January 2023
Line 670:		Line 670:

	[[Category: UNIX Practical Guides]]		[[Category: UNIX Practical Guides]]
	[[Category: Documentation]]		[[Category: UNIX Documentation]]

Jnc: heal split sentence

2022-06-19T18:50:57Z

heal split sentence

← Older revision		Revision as of 18:50, 19 June 2022
Line 9:		Line 9:
	Department of Electrical Engineering and Computer Science		Department of Electrical Engineering and Computer Science
	University of California, Berkeley		University of California, Berkeley
	Berkeley, California 94720		Berkeley, California 94720
	</pre>		</pre>

	The distribution tape can be used only a DEC		The distribution tape can be used only a DEC
	VAX-11/780<sup>1</sup> with RM03 or RP06 disks and with TE16 tape		VAX-11/780<sup>1</sup> with RM03 or RP06 disks and with TE16 tape
	drives. We have the ability to make tapes for systems with		drives. We have the ability to make tapes for systems with
	UNIBUS<sup>1</sup> disks, but such tapes are inherently rather system specific, and will not be discussed here. The tape consists		UNIBUS<sup>1</sup> disks, but such tapes are inherently rather system specific, and will not be discussed here. The tape consists
	of some preliminary bootstrapping programs followed by one		of some preliminary bootstrapping programs followed by one
	dump of a filesystem (see dump(1)) and one tape archive		dump of a filesystem (see dump(1)) and one tape archive
	image (see tar(1)); if needed, individual files can be		image (see tar(1)); if needed, individual files can be
	extracted after the initial construction of the filesystems.		extracted after the initial construction of the filesystems.

	If you are set up to do it, it is a good idea immediately to make a copy of the tape to guard against disaster.		If you are set up to do it, it is a good idea immediately to make a copy of the tape to guard against disaster.
	The tape is 9-track 1600 BPI and contains some 512-byte		The tape is 9-track 1600 BPI and contains some 512-byte
	records followed by many 10240-byte records. There are		records followed by many 10240-byte records. There are
	interspersed tapemarks; end-of-tape is signalled by a double		interspersed tapemarks; end-of-tape is signalled by a double
	end-of-file.		end-of-file.

	The tape contains binary images of the system and all		The tape contains binary images of the system and all
	the user level programs, along with source and manual sections for them. There are about 4200 UNIX<sup>2</sup> files altogether. The first tape file contains bootstrapping programs. The second tape file is to be put on one filesystem called the 'root filesystem', and contains essential binaries and enough other files to allow the system to run. The third tape file has all of the source and documentation. Altogether the files provided on the tape occupy approximately 40000 512 byte blocks.		the user level programs, along with source and manual sections for them. There are about 4200 UNIX<sup>2</sup> files altogether. The first tape file contains bootstrapping programs. The second tape file is to be put on one filesystem called the 'root filesystem', and contains essential binaries and enough other files to allow the system to run. The third tape file has all of the source and documentation. Altogether the files provided on the tape occupy approximately 40000 512 byte blocks.

	*An early version of this paper appeared under the title ''Setting up the Berkeley Virtual Memory Extensions to the UNIX Operating System'' and, no doubt, references to this paper by this name exist elsewhere in the documentation.		UNIX traditionally talks in terms of 512 character blocks, and for consistency across different versions of UNIX and to avoid mass confusion, user programs in the Virtual Vax version of the system also talk in terms of 512 blocks, despite the fact that the file system allocates 1024 byte blocks of disk space. All user programs such as ls(1) and du(1) speak in terms of 512 byte blocks; only system maintenance programs such as mkfs(1), icheck(1), dump(1), and df(1), speak to 1024 byte blocks. It is true that i/o is most efficient in 1024 byte quantities, but it is most natural for the user to think of this as ''2 blocks at a time.'' In any case, packs remain sectored 512 bytes per sector, and at the lowest driver levels the system deals with 512 byte disk records.

			*An early version of this paper appeared under the title ''Setting up the Berkeley Virtual Memory Extensions to the UNIX Operating System'' and, no doubt, references to this paper by this name exist elsewhere in the documentation.

	: Portions of this document are adapted from ''Setting Up Unix/32V Version 1.0'' by Thomas B. London and John F. Reiser.		: Portions of this document are adapted from ''Setting Up Unix/32V Version 1.0'' by Thomas B. London and John F. Reiser.

	1 - DEC, VAX, UNIBUS and MASSBUS are trademarks of Digital Equipment Corporation.<br>		<sup>1</sup> - DEC, VAX, UNIBUS and MASSBUS are trademarks of Digital Equipment Corporation.<br>
	2 - UNIX is a Trademark of Bell Laboratories.		<sup>2</sup> - UNIX is a Trademark of Bell Laboratories.

	~~UNIX traditionally talks in terms of 512 character blocks, and for consistency across different~~

	== Making a disk from tape ==		== Making a disk from tape ==
Line 48:		Line 49:
	2. Mount a disk pack on drive 0.		2. Mount a disk pack on drive 0.

	3. Key in at 50000 and execute the following boot program: You may enter in lower-case, the LSI-11 will echo in upper-case. The machine's printouts are shown in bold-face, explanatory comments are within ( ). Terminate each line you type by carriage return or line-feed.		3. Key in at 50000 and execute the following boot program: You may enter in lower-case, the LSI-11 will echo in upper-case. The machine's printouts are shown in bold-face, explanatory comments are within ( ). Terminate each line you type by carriage return or line-feed.


	versions of UNIX and to avoid mass confusion, user programs in the Virtual Vax version of the system also talk in terms of 512 blocks, despite the fact that the file system allocates 1024 byte blocks of
	~~disk space. All user progras such as ls(1) and du(1) speak in terms of 512 byte blocks; only system maintenance programs such as mkfs(1), icheck(1), dump(1), and df(1), speak to 1024 byte~~
	blocks. It is true that i/o is most efficient in 1024 byte quantities, but it is most natural for the user to think of this as ''2 blocks at a time.'' In any case, packs remain sectored 512
	~~bytes per sector, and at the lowest driver levels the system deals with 512 byte disk records~~.

	<pre>		<pre>

Jnc: better cat, fix fmt errs

2018-12-31T19:05:42Z

better cat, fix fmt errs

Show changes

Jnc: +cat

2018-12-17T02:08:12Z

+cat

← Older revision		Revision as of 02:08, 17 December 2018
Line 669:		Line 669:
	William N. Joy		William N. Joy
	Ozalp Babaoglu		Ozalp Babaoglu

			[[Category: CSRG BSD]]

Neozeed: /* Special Files */

2009-10-20T19:30:20Z

Special Files

← Older revision		Revision as of 19:30, 20 October 2009
Line 340:		Line 340:
	== Special Files ==		== Special Files ==

	Next you must put in special files for the new devices in the directory /dev using ~~_ m_ k_ n_ o_ d~~(1). Print the configuration file /usr/src/sys/sys/conf.c. This is the major device		Next you must put in special files for the new devices in the directory /dev using mknod(1). Print the configuration file /usr/src/sys/sys/conf.c. This is the major device
	switch of each device class (block and character). There is one line for each device configured in your system and a null line for place holding for those devices not configured. The essential block special files were installed above; for any new devices, the major device number is selected by counting the line number (from zero) of the device's entry in the block configuration table. Thus the first entry in the table bdevsw would be major device zero. This number is also printed in the table along the right margin.		switch of each device class (block and character). There is one line for each device configured in your system and a null line for place holding for those devices not configured. The essential block special files were installed above; for any new devices, the major device number is selected by counting the line number (from zero) of the device's entry in the block configuration table. Thus the first entry in the table bdevsw would be major device zero. This number is also printed in the table along the right margin.

Neozeed: /* Booting UNIX */

2009-10-02T12:27:10Z

Booting UNIX

← Older revision		Revision as of 12:27, 2 October 2009
Line 169:		Line 169:

	<pre>		<pre>
	# # chk /dev/rrp0a		# chk /dev/rrp0a
	</pre>		</pre>

Line 197:		Line 197:

	<pre>		<pre>
	# #/etc/mkfs /dev/rrp0g 145673 (create empty user filesystem)		#/etc/mkfs /dev/rrp0g 145673 (create empty user filesystem)
	~~i is si iz ze e =~~ = ~~6 65 54 49 96 6~~ (this is the number of available inodes)		isize = 65496 (this is the number of available inodes)
	m m/ /n ~~n =~~ = ~~3 3 5 50 00 0~~ (freelist interleave parameters)		m/n = 3500 (freelist interleave parameters)
	# #/etc/mount /dev/rp0g /usr (mount the usr filesystem)		#/etc/mount /dev/rp0g /usr (mount the usr filesystem)
	# #cd /usr (make /usr the current directory)		#cd /usr (make /usr the current directory)
	# #cp /dev/rmt5 /dev/null (skip first tape file (tp format))		#cp /dev/rmt5 /dev/null (skip first tape file (tp format))
	# #cp /dev/rmt5 /dev/null (skip second tape file (root))		#cp /dev/rmt5 /dev/null (skip second tape file (root))
	# #tar xbf 20 /dev/rmt1 (extract the usr filesystem)		#tar xbf 20 /dev/rmt1 (extract the usr filesystem)
	# #cd / (back to root)		#cd / (back to root)
	# #/etc/umount /dev/rp0g (unmount /usr)		#/etc/umount /dev/rp0g (unmount /usr)
	</pre>		</pre>

Line 214:		Line 214:

	<pre>		<pre>
	# # chk /dev/rrp0g		# chk /dev/rrp0g
	</pre>		</pre>

	In order to use the /usr file system, you should now remount it by saying		In order to use the /usr file system, you should now remount it by saying
	<pre>		<pre>
	# # /etc/mount /dev/rp0g /usr		# /etc/mount /dev/rp0g /usr
	</pre>		</pre>
	again.		again.

Neozeed: /* Making a disk from tape */

2009-09-26T18:07:57Z

Making a disk from tape

← Older revision		Revision as of 18:07, 26 September 2009
Line 54:		Line 54:

	<pre>		<pre>
	~~> >>~~ >> >HALT		>>>HALT
	~~> >>~~ >> >UNJAM		>>>UNJAM
	~~> >>~~ >> >INIT		>>>INIT
	~~> >>~~ >> >D 50000 20009FDE		>>>D 50000 20009FDE
	~~> >>~~ >> >D+ D0512001		>>>D+ D0512001
	~~> >>~~ >> >D+ 3204A101		>>>D+ 3204A101
	~~> >>~~ >> >D+ C114C08F		>>>D+ C114C08F
	~~> >>~~ >> >D+ A1D40424		>>>D+ A1D40424
	~~> >>~~ >> >D+ 008FD00C		>>>D+ 008FD00C
	~~> >>~~ >> >D+ C1800000		>>>D+ C1800000
	~~> >>~~ >> >D+ 8F320800		>>>D+ 8F320800
	~~> >>~~ >> >D+ 10A1FE00		>>>D+ 10A1FE00
	~~> >>~~ >> >D+ 00C139D0		>>>D+ 00C139D0
	~~> >>~~ >> >D+ 00000004		>>>D+ 00000004
	~~> >>~~ >> >E 50000/NE:A		>>>E 50000/NE:A
	... (machine prints out values, check typing)		... (machine prints out values, check typing)
	~~> >>~~ >> >START 50000		>>>START 50000
	</pre>		</pre>

Line 77:		Line 77:
	4. Start the CPU with		4. Start the CPU with
	<pre>		<pre>
	~~> >>~~ >> >START 0		>>>START 0
	</pre>		</pre>

	5. The console should type		5. The console should type
	<pre>		<pre>
	= =		=
	</pre>		</pre>

Line 105:		Line 105:
	(bring in RP06 verifier)		(bring in RP06 verifier)
	= =rpread		= =rpread
	~~d dr re ea ad d~~ : ~~: R Re ea ad d R RP P0 06 6/~~ /~~R RM M0 03 3 D Di is sk k~~		dread : Read RP06/RM03 Disk

	~~d di is sk k u un ni it t :~~ : 0 (specify unit zero)		disk unit: 0 (specify unit zero)
	~~s st ta ar rt t b bl lo oc ck k :~~ : 0 (start at block zero)		start block: 0 (start at block zero)
	n no o. ~~. b bl lo oc ck ks s :~~ : (default is entire pack)		no. blocks: (default is entire pack)

	(this procedure should take about 10 minutes)		(this procedure should take about 10 minutes)
	(some diagnostic messages may appear here)		(some diagnostic messages may appear here)
	# ~~# D Da at ta a C Ch he ec ck k e er rr ro or rs s :~~ : n nn n (number of soft errors)		#Data Check errors: nn (number of soft errors)
	# ~~# O Ot th he er r e er rr ro or rs s~~ : ~~: x~~ xx x (number of hard errors)		#Other errors: xx (number of hard errors)
	~~d di is sk k u un ni it t:~~ : -1 (exit from rpread)		disk unit: -1 (exit from rpread)

	= = (back to tape boot)		= (back to tape boot)
	</pre>		</pre>
	If the number of `Other errors' is not zero, consideration should be given to obtaining a clean pack before proceeding further.		If the number of `Other errors' is not zero, consideration should be given to obtaining a clean pack before proceeding further.
Line 124:		Line 124:
	<pre>		<pre>
	(bring in a standalone version of the _ m_ k_ f_ s (1) program)		(bring in a standalone version of the _ m_ k_ f_ s (1) program)
	= =mkfs		=mkfs
	~~f fi il le e s sy ys s s si iz ze e:~~ : 7942 (number of 1024 byte blocks in root)		file sys size: 7942 (number of 1024 byte blocks in root)
	~~f fi il le e s sy ys st te em m:~~ : hp(0,0) (root is on drive zero; first filsys there)		file system: hp(0,0) (root is on drive zero; first filsys there)
	~~i is si iz ze e =~~ = ~~5 50 07 72 2~~ (number of inodes in root filesystem)		isize = 5072 (number of inodes in root filesystem)
	m m/ /n n = = 3 3 5 50 00 0 (interleave parameters)		m m/ /n n = = 3 3 5 50 00 0 (interleave parameters)
	= = (back at tape boot level)		= = (back at tape boot level)
Line 133:		Line 133:
	You now have a empty UNIX root filesystem. To restore the data which you need to boot the system, type		You now have a empty UNIX root filesystem. To restore the data which you need to boot the system, type
	<pre>		<pre>
	(bring in a standalone ~~_ r_ e_ s_ t_ o_ r~~(1) program)		(bring in a standalone restor(1) program)
	= =restor		=restor
	~~T Ta ap pe e?~~ ? ht(1,1) (1600 bpi, second tape file)		Tape? ht(1,1) (1600 bpi, second tape file)
	~~D Di is sk k?~~ ? hp(0,0) (into root file system)		Disk? hp(0,0) (into root file system)
	~~L La as st t c ch ha an nc ce e b be ef fo or re e s sc cr ri ib bb bl li in ng g o~~ on ~~n d di is sk k.~~ . (just hit return)		Last chance before scribbling on disk. (just hit return)
	(30 second pause, then tape should move)		(30 second pause, then tape should move)
	...		...
	= = (back at tape boot level)		= (back at tape boot level)
	</pre>		</pre>

Neozeed: /* Basics of Disk Layout */

2009-09-26T18:01:55Z

Basics of Disk Layout

← Older revision		Revision as of 18:01, 26 September 2009
Line 402:		Line 402:

	<pre>		<pre>
	~~> >>~~ >> >UNJAM		>>>UNJAM
	~~> >>~~ >> >INIT		>>>INIT
	~~> >>~~ >> >LOAD MKFS		>>>LOAD MKFS
	LOAD DONE, xxxx BYTES LOADED		LOAD DONE, xxxx BYTES LOADED
	~~> >>~~ >> >ST 2		>>>ST 2

	...		...

	~~> >>~~ >> >H		>>>H
	HALTED AT yyyy		HALTED AT yyyy
	~~> >>~~ >> >U		>>>U
	~~> >>~~ >> >I		>>>I
	~~> >>~~ >> >LOAD RESTOR		>>>LOAD RESTOR
	LOAD DONE, zzzz BYTES LOADED		LOAD DONE, zzzz BYTES LOADED

Neozeed: /* Regenerating the system */

2009-09-26T18:00:42Z

Regenerating the system

← Older revision		Revision as of 18:00, 26 September 2009
Line 499:		Line 499:

	<pre>		<pre>
	# # DESTDIR=/usr/newsys		# DESTDIR=/usr/newsys
	# # export DESTDIR		# export DESTDIR
	# # cd /usr		# cd /usr
	# # rm -r newsys		# rm -r newsys
	# # mkdir newsys		# mkdir newsys
	# # cd /usr/src/cmd		# cd /usr/src/cmd
	# # Admin/mk * > Admin/errs 2>& 1 &		# Admin/mk * > Admin/errs 2>& 1 &
	</pre>		</pre>

	This will take about 4 hours on a reasonably configured machine. When it finished you can move the hierarchy into the normal places using mv(1) and cp(1), and then execute		This will take about 4 hours on a reasonably configured machine. When it finished you can move the hierarchy into the normal places using mv(1) and cp(1), and then execute
	<pre>		<pre>
	# # DESTDIR=/		# DESTDIR=/
	# # export DESTDIR		# export DESTDIR
	# # cd /usr/src/cmd/Admin		# cd /usr/src/cmd/Admin
	# # mk ALIASES		# mk ALIASES
	# # mk MODES		# mk MODES
	</pre>		</pre>

	to link files together as necessary and to set all the right set-user-id bits.		to link files together as necessary and to set all the right set-user-id bits.

Neozeed: /* System Identification */

2009-09-26T17:59:44Z

System Identification

← Older revision		Revision as of 17:59, 26 September 2009
Line 433:		Line 433:
	to correspond to your system, and then recompile and install getty.vm(8) via:		to correspond to your system, and then recompile and install getty.vm(8) via:
	<pre>		<pre>
	# # cd /usr/src/cmd		# cd /usr/src/cmd
	# # DESTDIR=/		# DESTDIR=/
	# # export DESTDIR		# export DESTDIR
	# # Admin/mk getty.vm.c		# Admin/mk getty.vm.c
	</pre>		</pre>
	This will arrange for an appropriate banner to be printed on terminals before users log in.		This will arrange for an appropriate banner to be printed on terminals before users log in.