-
Notifications
You must be signed in to change notification settings - Fork 10
/
Copy pathsetup.txt
6477 lines (4167 loc) · 213 KB
/
setup.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Installing and Operating 4.3BSD-Quasijarus UNIX*
on the VAX|
November 18, 2003
Michael J. Karels
Chris Torek
James M. Bloom
Marshall Kirk McKusick
Samuel J. Leffler
William N. Joy
Computer Systems Research Group
Department of Electrical Engineering and Computer Science
University of California, Berkeley
Berkeley, California 94720
(415) 642-7780
Michael Sokolov
Quasijarus Project
International Free Computing Task Force
http://ifctfvax.Harhan.ORG/Quasijarus/
ABSTRACT
This document contains instructions for the
installation and operation of the 4.3BSD-
Quasijarus release of the VAX UNIX system, as dis-
tributed by Quasijarus Consortium.
It discusses procedures for installing UNIX
on a new VAX, and for upgrading an existing 4.2BSD
or 4.3BSD VAX UNIX system to the new release. An
explanation of how to lay out file systems on
available disks, how to set up terminal lines and
user accounts, and how to do system-specific
*UNIX is a register trademark of AT&T in the USA and
other countries.
+DEC, VAX, IDC, SBI, UNIBUS and MASSBUS are trademarks
of Digital Equipment Corporation.
December 6, 2003
SMM:1-2lling and Operating 4.3BSD-Quasijarus UNIX on the VAX
tailoring is provided. A description of how to
install and configure the networking facilities
included with 4.3BSD-Quasijarus is included.
Finally, the document details system operation
procedures: shutdown and startup, hardware error
reporting and diagnosis, file system backup pro-
cedures, resource control, performance monitoring,
and procedures for recompiling and reinstalling
system software.
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX-3
1. INTRODUCTION
This document explains how to install the 4.3BSD-
Quasijarus release of the Berkeley version of UNIX for the
VAX on your system. Because of the file system organization
used in 4.3BSD-Quasijarus, if you are not currently running
4.2BSD or 4.3BSD you will have to do a full bootstrap from
the distribution tape. The procedure for performing a full
bootstrap is outlined in chapter 2. The process includes
booting standalone utilities from tape to format a disk if
necessary, then to copy a small root filesystem image onto a
swap area. This filesystem is then booted and used to
extract a dump of a standard root filesystem. Finally, that
root filesystem is booted, and the remainder of the system
binaries and sources are read from the archives on the
tape(s).
The technique for upgrading a 4.2BSD or 4.3BSD system
is described in chapter 3 of this document. As 4.3BSD-
Quasijarus is upward-compatible with 4.2BSD, the upgrade
procedure involves extracting a new set of system binaries
onto new root and /usr filesystems. The sources are then
extracted, and local configuration files are merged into the
new system. 4.2BSD and 4.3BSD user filesystems may be
upgraded in place, and 4.2BSD and 4.3BSD binaries may be
used with 4.3BSD-Quasijarus in the course of the conversion.
It is desirable to recompile most local software after the
conversion, as there are many changes and performance
improvements in the standard libraries.
1.1. Hardware supported
Note that some VAX models are identical to others in
all respects except speed. The VAX 8650 will be hereafter
referred to as a VAX 8600; likewise, the VAX 8250 will be
referred to as a VAX 8200, the VAX-11/785 as an 11/780, and
the 11/725 as an 11/730. These names are sometimes shor-
tened to ``8600,'' ``8200,'' ``780,'' ``750,'' and ``730.''
MicroVAXen are often referred to by their CPU board names,
i.e., KA630 for MicroVAX II, KA650 for MicroVAX 3, and KA655
for MicroVAX 3+.
This distribution can be booted on a VAX 8600, VAX
8200, VAX-11/780, VAX-11/750, VAX-11/730, or MicroVAX
II/3/3+ cpu with at least 2 megabytes of memory, and any of
the following disks:
December 6, 2003
SMM:1-4lling and Operating 4.3BSD-Quasijarus UNIX on the VAX
DEC MASSBUS: RM03, RM05, RM80, RP06, RP07
EMULEX MASSBUS: AMPEX Capricorn, 9300, CDC 9766, 9775,
FUJITSU 2351 Eagle, 2361*
DEC UNIBUS: RK07, RL02, RA??*, RC25
EMULEX SC-21V, SC-31 AMPEX DM980, Capricorn, 9300,
UNIBUS*: CDC 9762, 9766, FUJITSU 160M, 330M
EMULEX SC-31 UNIBUS*: FUJITSU 2351 Eagle
DEC IDC: R80, RL02
DEC BI: RA??*
DEC QBUS: RD53, RD54, RA??*, RF??*
The tape drives supported by this distribution are:
DEC MASSBUS: TE16, TU45, TU77, TU78
EMULEX MASSBUS: TC-7000
DEC UNIBUS: TS11, TU80, TU81+
EMULEX TC-11, AVIV UNIBUS: KENNEDY 9300, STC, CIPHER
TU45 UNIBUS: SI 9700
DEC BI: TU81+
DEC QBUS: TK50, TK70, TU80, TU81+
The tapes and disks may be on any available UNIBUS or
MASSBUS adapter at any slot.
This distribution does not support the DEC CI780 or the
HSC50 disk controller. As such, this distribution will not
boot on the standard VAX 8600 cluster configurations. You
will need to configure your system to use only UNIBUS,
MASSBUS, and BI bus disk and tape devices. In addition,
only 9-track (TU81) tapes are supported on VAXBI, TK50 and
TK70 are not. BI Ethernet and terminal controllers are not
supported either, for this reason, although it can be
* Other compatible UNIBUS controllers and drives may be
easily usable with the system, but may require minor
modifications to the system to allow bootstrapping.
The EMULEX disk and SI tape controllers, and the drives
shown here are known to work as bootstrap devices.
Known RA drives are RA60, RA7[0123], RA8[012], and
RA9[02]. Known RF drives are RF3[0156] and RF7[1234].
Other SMD and MSCP drives may be used once pack labels
are written, but bootstrapping will be a problem since
the procedure currently relies on compiled-in disk
tables.
+ The TU81 support is untested but is identical to the
TK50 code.
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX-5
bootstrapped, a VAX 8200 without a UNIBUS would not be very
useful.
1.2. Distribution format
The basic distribution is available in the following
formats:
* 1600bpi 9-track 2400' magnetic tapes (2)
* 6250bpi 9-track 2400' magnetic tape (1)
* TK50 tape cartridge (1)
The following console media are available for VAX processors
that use them:
* RX01 console floppy disk for 11/780
* TU58 console cassette for 11/750 and 11/730
* RX50 console floppy disk for 8200
* RL02 console pack for 8600
Installation on any machine requires a tape unit. Since cer-
tain standard VAX packages do not include a tape drive, this
means one must either borrow one from another VAX system or
one must be purchased separately. The console media distri-
buted with the system are not suitable for use as opera-
tional console media for 11/780, 11/730 and 8600 processors
because they do not contain CPU microcode or front end pro-
cessor code. Their intended use is only for installation.
The distribution does not fit on several standard VAX
configurations that contain only small disks. If your
hardware configuration does not provide at least 75 Mega-
bytes of disk space you can still install the distribution,
but you will probably have to operate without source for the
user level commands and, possibly, the source for the
operating system. The RK07-only distribution format once
provided by our group is no longer available. Further, no
attempt has ever been made to install the system on the
standard VAX-11/730 hardware configuration from DEC that
contains only dual RL02 disk drives (though the distribution
tape may be bootstrapped on an RL211 controller and the sys-
tem provides support for RL02 disk drives either on an IDC
or an RL211). The labels on the distribution tape(s) show
the amount of disk space each tape file occupies, these
should be used in selecting file system layouts on systems
with little disk space.
If you have the facilities, it is a good idea to copy
the magnetic tape(s) in the distribution kit to guard
against disaster. The tapes contain some 512-byte records
followed by many 10240-byte records. There are interspersed
tape marks; end-of-tape is signaled by a double end-of-file.
The first file on the tape contains preliminary bootstrap-
ping programs. This is followed by a binary image of a 3
December 6, 2003
SMM:1-6lling and Operating 4.3BSD-Quasijarus UNIX on the VAX
megabyte ``mini root'' file system. Following the mini root
file is a full dump of the root file system (see dump(8)*).
Additional files on the tape(s) contain tape archive images
(see tar(1)). See Appendix A for a description of the con-
tents and format of the tape(s).
1.3. VAX hardware terminology
This section gives a short discussion of VAX hardware
terminology to help you get your bearings.
If you have MASSBUS disks and tapes it is necessary to
know the MASSBUS that they are attached to, at least for the
purposes of bootstrapping and system description. The
MASSBUSes can have up to 8 devices attached to them. A disk
counts as a device. A tape formatter counts as a device,
and several tape drives may be attached to a formatter. If
you have a separate MASSBUS adapter for a disk and one for a
tape then it is conventional to put the disk as unit 0 on
the MASSBUS with the lowest ``TR'' number, and the tape for-
matter as unit 0 on the next MASSBUS. On a 11/780 this
would correspond to having the disk on ``mba0'' at ``tr8''
and the tape on ``mba1'' at ``tr9''. Here the MASSBUS
adapter with the lowest TR number has been called ``mba0''
and the one with the next lowest number is called ``mba1''.
To find out the MASSBUS that your tape and disk are on
you can examine the cabling and the unit numbers or your
site maintenance guide. Do not be fooled into thinking that
the number on the front of the tape drive is a device
number; it is a slave number, one of several possible tapes
on the single tape formatter. For bootstrapping, the slave
number must be 0. The formatter unit number may be anything
distinct from the other numbers on the same MASSBUS, but you
must know what it is.
The MASSBUS devices are known by several different
names by DEC software and by UNIX. At various times it is
necessary to know both names. There is, of course, the name
of the device like ``RM03'' or ``RM80''; these are easy to
remember because they are printed on the front of the dev-
ice. DEC also names devices based on the driver name in the
system using a convention that reflects the interconnect
topology of the machine. The first letter of such a name is
a ``D'' for a disk, the second letter depends on the type of
the drive, ``DR'' for RM03, RM05, and RM80's, ``DB'' for
RP06's. The next letter is related to the interconnect; DEC
calls the first MASSBUS or UNIBUS adapter ``A'', the second
``B'', etc. Thus, ``DRA'' is an RM drive on the first
MASSBUS adapter. Finally, the name ends in a digit
* References of the form X(Y) mean the subsection named
X in section Y of the UNIX programmer's manual.
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX-7
corresponding to the unit number for the device on the
MASSBUS: e.g., ``DRA0'' is a disk at the first device slot
on the first MASSBUS adapter and is an RM disk.
1.4. UNIX device naming
UNIX has a set of names for devices which are different
from the DEC software names for the devices. The following
table lists both the DEC and UNIX names for the supported
devices:
Hardware UNIX DEC
RM disks hp DR
RP disks hp DB
MASSBUS TE/TU tapes ht MT
TU78 tape mt MF
RK disks hk DM
RL disks rl DL
TS tapes ts MS
UDA disks ra DU
RC25 disks ra DU
IDC disks rb DQ
UNIBUS SMD disks up
TM tapes tm
TMSCP tapes tms MU
UNIBUS TU tapes ut
BI KDB disks kra DU
Here UNIBUS SMD disks are disks on an RM-emulating con-
troller on the UNIBUS, and TM tapes are tapes on a con-
troller that emulates the DEC TM11. UNIBUS TU tapes are
tapes on a UNIBUS controller that emulates the DEC TU45.
IDC disks are disks on an 11/730 Integral Disk Controller.
TS tapes are tapes on a controller compatible with the DEC
TS11 (e.g. a TU80). TMSCP tapes include the TU81 and TK50.
The normal standalone system, used to bootstrap the
full UNIX system, uses device names:
xx(a,c,d,p)
where xx is any of the UNIX device names in the table above.
The parameters a, c, and d are the adapter, controller, and
drive numbers respectively. The adapter is the index number
of the MASSBUS or UNIBUS (with the first one found as number
0). The controller (or ``device'') number is the index
number of the device on that adapter. The drive number is
the index of the disk drive on that controller (or, for
MASSBUS tapes, of the formatter). The p value is inter-
preted differently for tapes and disks: for disks it is a
disk partition (in the range 0-7); for tapes it is a file
December 6, 2003
SMM:1-8lling and Operating 4.3BSD-Quasijarus UNIX on the VAX
number on the tape.* For example, partition 7 of drive 2 on
an RA81 connected to the only UDA50 on UNIBUS 1 would be
``ra(1,0,2,7)''. Normally, the adapter and controller will
both be 0; it may therefore be omitted from the device
specification, and most of the examples in this document do
so. When not running standalone, this partition would nor-
mally be available as ``/dev/ra2g''. Here the prefix
``/dev'' is the name of the directory where all ``special
files'' normally live, the ``ra'' serves the obvious pur-
pose, the ``2'' identifies this as a partition of hp drive
number ``2'' and the ``g'' identifies this as the seventh
partition.
On the VAX 8200, the adapter numbering is controlled by
the ordering of the nodes on the BI; the BI is probed from
low node numbers towards high. Hence if there are two KDB50
adapters, one at node 4, and one at node 7, the one at node
4 is kdb0, and the one at node 7 is kdb1. The numbering for
UNIBUS adapters works similarly. Usually, the first UNIBUS
on an 8200 is at node 0; you will need this node number to
boot from tape. Although DEC apparently doesn't want you to
know this, BI KLESI (TU81 controller) is actually a UNIBUS
adapter with a UNIBUS KLESI behind it. Unlike DEC software
UNIX treats it as a regular UNIBUS adapter, and it must be
taken into account when counting UNIBUS adapters. Other VAX
models do not permit such chaotic ordering of adapters.
In all simple cases, where only a single controller is
present, a drive with unit number 0 (in its unit plug on the
front of the drive) will be called unit 0 in its UNIX file
name. This is not, however, strictly necessary, since the
system has a level of indirection in this naming. If there
are multiple controllers, the disk unit numbers will nor-
mally be counted sequentially across controllers. This can
be taken advantage of to make the system less dependent on
the interconnect topology, and to make reconfiguration after
hardware failure extremely easy.
Each UNIX physical disk is divided into at most 8 logi-
cal disk partitions, each of which may occupy any consecu-
tive cylinder range on the physical device. The cylinders
occupied by the 8 partitions for each drive type are speci-
fied initially in the disk description file /etc/disktab
(c.f. disktab(5)). The partition information and descrip-
tion of the drive geometry are written in the first sector
of each disk with the disklabel(8) program; currently, this
is possible on hp and ra disks, but not on the other types
of disks on the VAX. Each partition may be used for either
* Note that while a tape file consists of a single data
stream, the distribution tape(s) have data structures
in these files. Although the tape(s) contain only 6
tape files, they comprise several thousand UNIX files.
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX-9
a raw data area such as a paging area or to store a UNIX
file system. It is conventional for the first partition on
a disk to be used to store a root file system, from which
UNIX may be bootstrapped. The second partition is tradi-
tionally used as a paging area, and the rest of the disk is
divided into spaces for additional ``mounted file systems''
by use of one or more additional partitions.
The third logical partition of each physical disk also
has a conventional usage: it allows access to the entire
physical device, in many cases including bad sector forward-
ing information recorded at the end of the disk (one track
plus 126 sectors). It is occasionally used to store a sin-
gle large file system or to access the entire pack when mak-
ing a copy of it on another. Care must be taken if using
this partition not to overwrite the last few tracks and
thereby clobber the bad sector information. Note that the
sector containing the disk label is normally write-protected
so that it is not accidentally overwritten. Pack-to-pack
copies should normally skip the first 16 sectors of a pack,
which contain the label and the initial bootstrap for some
processors.
1.5. UNIX devices: block and raw
UNIX makes a distinction between ``block'' and ``raw''
(character) devices. Each disk has a block device interface
where the system makes the device byte addressable and you
can write a single byte in the middle of the disk. The sys-
tem will read out the data from the disk sector, insert the
byte you gave it and put the modified data back. The disks
with the names ``/dev/xx0a'', etc are block devices. There
are also raw devices available. These have names like
``/dev/rxx0a'', the ``r'' here standing for ``raw''. Raw
devices bypass the buffer cache and use DMA directly to/from
the program's I/O buffers; they are normally restricted to
full-sector transfers. In the bootstrap procedures we will
often suggest using the raw devices, because these tend to
work faster. Raw devices are used when making new filesys-
tems, when checking unmounted filesystems, or for copying
quiescent filesystems. The block devices are used to mount
file systems, or when operating on a mounted filesystem such
as the root.
You should be aware that it is sometimes important
whether to use the character device (for efficiency) or not
(because it wouldn't work, e.g. to write a single byte in
the middle of a sector). Don't change the instructions by
using the wrong type of device indiscriminately.
December 6, 2003
SMM:1-10ling and Operating 4.3BSD-Quasijarus UNIX on the VAX
2. BOOTSTRAP PROCEDURE
This section explains the bootstrap procedure that can
be used to get the kernel supplied with this distribution
running on your machine. If you are not currently running
4.2BSD or 4.3BSD you will have to do a full bootstrap.
Chapter 3 describes how to upgrade an existing 4.2BSD or
4.3BSD system. programs. An understanding of the opera-
tions used in a full bootstrap is very helpful in performing
an upgrade as well. In either case, it is highly desirable
to read and understand the remainder of this document before
proceeding.
2.1. Converting pre-4.2BSD Systems
The file system format was changed between 3BSD and
4.0BSD, and again between 4.1BSD and 4.2BSD. At a minimum
you will have to dump any old file systems, and then restore
them onto the 4.3BSD-Quasijarus file system. Sites running
3BSD or 32/V may be able to modify the restore program to
understand the old 512 byte block file system, but this has
never been tried. The dump format used in 4.0BSD and 4.1BSD
is backward-compatible with that used in 4.3BSD-Quasijarus
(which is unchanged from 4.2BSD). That is, the 4.3BSD-
Quasijarus restore program understands how to read 4.0BSD
and 4.1BSD dump tapes, although 4.3BSD-Quasijarus dump tapes
cannot be restored under 4.0BSD or 4.1BSD. It is also
desirable to make a convenient copy of system configuration
files for use as guides when setting up the new system; the
list of files to save from 4.2BSD systems in chapter 3 may
be used as a guideline.
The first step is to dump your file systems with
dump(8). For the utmost of safety this should be done to
magtape. However, if you enjoy gambling with your life (or
you have a VERY friendly user community) and you have enough
disk space, you can try converting your file systems while
copying to a new disk partition by piping the output of dump
directly into restore after bringing up 4.3BSD-Quasijarus.
If you select the latter tack, a version of the 4.1BSD dump
program that runs under 4.3BSD-Quasijarus is provided in
/etc/dump.4.1. Beware that file systems created under
4.3BSD-Quasijarus can use about 5-10% more disk space for
file system related information than under 4.1BSD. Thus,
before dumping each file system it is a good idea to remove
any files that may be easily regenerated. Since all pro-
grams should be recompiled under the new system, your best
bet is to remove any object files. File systems with at
least 10% free space on them should restore into an
equivalently sized 4.3BSD-Quasijarus file system without
problem.
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX11
2.2. Booting from tape
The tape bootstrap procedure used to create a working
system involves the following major steps:
1) Format a disk pack with the format program.
2) Copy a ``mini root'' file system from the tape onto the
swap area of the disk.
3) Boot the UNIX system on the ``mini root''.
4) Restore the full root file system using restore(8).
5) Build a console floppy, cassette, or RL02 pack for
bootstrapping.
6) Reboot the completed root file system.
7) Label the disks with the disklabel(8) program.
8) Build and restore the /usr file system from tape with
tar(1).
9) Extract the system and utility files and contributed
software as desired.
Certain of these steps are dependent on your hardware
configuration. Formatting the disk pack used for the root
file system may require using the DEC standard formatting
programs. Also, if you are bootstrapping the system on an
11/750, no console cassette is usually required.
Bootstrapping an 8600 is a bit more difficult than
bootstrapping the other machines. The procedures for load-
ing the toggle program and reading the tape bootstrap moni-
tor described in Appendix B must be used if you do not have
access to a console RL02 pack with a UNIX bootstrap. Such a
pack may be made on an 8600 already running UNIX, or on
another 4.3BSD-Quasijarus system with an RL02 drive using
the procedures in 4.1.1. One may be required to enter the
toggle program more than once. After the bootstrap monitor
is loaded, device addresses will be the same as if the
machine were an 11/780. UNIBUS and MASSBUS adaptors are
numbered from zero across both SBIA's (if present).
The following sections describe the above steps in
detail. In these sections references to disk drives are of
the form xx(n,m) and references to files on tape drives are
of the form yy(n,m) where xx and yy are names described in
section 1.4 and n and m are the unit and offset numbers
described in section 1.4. Commands you are expected to type
are shown in italics, while that information printed by the
system is shown emboldened. These instructions were
December 6, 2003
SMM:1-12ling and Operating 4.3BSD-Quasijarus UNIX on the VAX
originally written for large VAXen that use console media.
MicroVAXen have no console media, if you are bootstrapping a
MicroVAX, see Appendix B.
Throughout the installation steps the reboot switch on
a 780 or 730 should be set to off; on an 8600 or 750 set the
power-on action to halt. (In normal operation a 780 or 730
will have the reboot switch on and an 8600 or 750 will have
the power-on action set to reboot/restart.) On an 8200 the
keyswitches should be set to Enable/Update for bootstrapping
and maintenance (Secure/Autostart in normal operation); on a
MicroVAX II the switch on the rear I/O panel should be
turned up to enable halts (halts are disabled in normal
operation).
If you encounter problems while following the instruc-
tions in this part of the document, refer to Appendix C for
help in troubleshooting.
2.2.1. Step 1: formatting the disk
All disks used with 4.3BSD-Quasijarus should be format-
ted to insure the proper handling of physically corrupted
disk sectors. If you have DEC disk drives, you should use
the standard DEC formatter to format your disks. If not,
the format program included in the distribution, or a vendor
supplied formatting program, may be used to format disks.
The format program is capable of formatting any of the fol-
lowing supported distribution devices:
EMULEX MASSBUS: AMPEX Capricorn, 9300, CDC 9766, 9775,
FUJITSU 330M, 2351 Eagle
EMULEX SC-21V, SC-31 AMPEX 9300, Capricorn, CDC 9730, 9766,
UNIBUS: FUJITSU 160M, 330M
EMULEX SC-31 UNIBUS: FUJITSU 2351 Eagle
The format program is for hp/up SMD disks only. MSCP
disks usually do not require formatting. If you need to
format an MSCP disk, you will need to use formatting utili-
ties provided by the drive or controller vendor, format will
not help you.
If you have run a pre-4.1BSD version of UNIX on the
packs you are planning to use for bootstrapping it is likely
that the bad sector information on the packs has been des-
troyed, since it was accessible as normal data in the last
several tracks of the disk. You should therefore run the
formatter again to make sure the information is valid.
On an 11/750, to use a disk pack as a bootstrap device,
sectors 0 through 15, the disk sectors in the file ``/boot''
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX13
(the program that loads the system image), and the file sys-
tem indices that lead to this file must not have any errors.
On an 8600, 11/780, or 11/730, the ``boot'' program is
loaded from the console medium and includes device drivers
for the ``hp'' and ``up'' disks that do ECC correction and
bad sector forwarding; consequently, on these machines the
system may be bootstrapped on these disks even if the disk
is not error free in critical locations. In general, if the
first 15884 sectors of your disk are clean you are safe; if
not you can take your chances.
To load the format program, insert the distribution
TU58 cassette or RX01 floppy disk in the appropriate console
device (on the 11/730 use cassette 0) and do the following
steps.
If you have an 8600 and no RL02 pack with UNIX stan-
dalone programs start the bootstrap monitor using the pro-
cedure described in Appendix B. Then give the command:
=format
If you have an 11/780 give the commands:
>>>HALT
>>>UNJAM
>>>INIT
>>>LOAD FORMAT
>>>START 2
If you have an 11/750 give the commands:
>>>I
>>>B DDA0
=format
If you have an 11/730 give the commands:
>>>H
>>>I
>>>L DD0:FORMAT
>>>S 2
The format program should now be running and awaiting
your input:
Disk format/check utility
Enable debugging (1=bse, 2=ecc, 3=bse+ecc)?
December 6, 2003
SMM:1-14ling and Operating 4.3BSD-Quasijarus UNIX on the VAX
If you made a mistake loading the program off the TU58
cassette or using the bootstrap monitor loaded for the 8600
the ``='' prompt should reappear and you can retype the pro-
gram name. If something else happened, you may have a bad
distribution cassette or floppy, or your hardware may be
broken; refer to Appendix C for help in troubleshooting. If
you are unable to load programs off the distributed console
medium, consult Appendix B for an alternate (more painful)
approach.
Format will create sector headers and verify the
integrity of each sector formatted. Remember format runs
only on the up and hp drives listed above. Format will
prompt for the information required as shown below. Ques-
tions with default answers appear with the default in
parentheses at the prompt; a carriage return will take the
default. If you err in answering questions, ``Delete''
erases the last character typed, and ``^U'' erases the
current input line.
Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? 0
Device to format? xx(0,0)
...(the old bad sector table is read; ignore any errors that occur here)...
Formatting drive xx0 on adaptor 0: verify (yes/no)? yes
Device data: #cylinders=842, #tracks=20, #sectors=48
Starting cylinder (0):(hit RETURN to accept the defaults)
Starting track (0):
Ending cylinder (841):
Ending track (19):
Available test patterns are:
1 - (f00f) RH750 worst case
2 - (ec6d) media worst case
3 - (a5a5) alternating 1's and 0's
4 - (ffff) Severe burnin (up to 48 passes)
Pattern (one of the above, other to restart)? 2
Maximum number of bit errors to allow for soft ECC (3):
Start formatting...make sure the drive is online
...(soft ecc's and other errors are reported as they occur)...
...(if 4 write check errors were found, the program terminates like this)...
Errors:
Bad sector: 0
Write check: 4
Hard ECC: 0
Other hard: 0
Marked bad: 0
Skipped: 0
Total of 4 hard errors revectored.
Writing bad sector table at block 524256
...(524256 is the block # of the first block in the bad sector table)...
Done
Once the root device has been formatted, format will prompt
for another disk to format. Halt the machine by typing
``control-P'' and ``H'' (the ``H'' is necessary only on the
December 6, 2003
Installing and Operating 4.3BSD-Quasijarus UNIX on theMVAX15
780 and 8600, but does not hurt on the other machines).
Enable debugging (1=bse, 2=ecc, 3=bse+ecc)?^P
>>>H
It may be necessary to format other drives before con-
structing file systems on them; this can be done at a later
time with the steps just performed. Format can also be used
in an extended test mode (pattern 4) that uses numerous test
patterns in up to 48 passes to detect as many disk surface
errors as possible; this test may be run for many hours,
depending on the CPU and controller. On an 11/780, this can
be sped up significantly by setting the clock fast. It may
be run for some number of passes, then either terminated or
continued according to the errors found to that point.
2.2.2. Step 2: copying the mini-root file system
The second step is to run a simple program, copy, which
copies a small root file system into the second partition of
the disk. This file system will serve as the base for
creating the actual root file system to be restored. The
version of the operating system maintained on the ``mini-
root'' file system understands that it should not swap on
top of itself, thereby allowing double use of the disk par-
tition. Copy is loaded just as the format program was
loaded; for example, if not using console media, one must
enter the toggle and the bootstrap monitor as described in
Appendix B and then:
(copy mini root file system)
=copy
From: yy(y,1) (unit y, second tape file)
To: xx(x,1) (mini root is on drive x; second partition)
Copy completed: 308 records copied
From:
while for an 8200:
(copy mini root file system)
>>>B/R5:800 CSA1 (or CSA2 if using the 2nd diskette slot)
BOOT58>LOAD COPY
BOOT58>START 2
From: yy(y,1) (unit y, second tape file)
To: xx(x,1) (mini root is on drive x; second partition)
Copy completed: 308 records copied
From:
for an 11/780:
December 6, 2003
SMM:1-16ling and Operating 4.3BSD-Quasijarus UNIX on the VAX
(copy mini root file system)