setup

unix v7是最后一个广泛发布的研究型UNIX版本

.TL
Setting Up
Unix
\- Seventh Edition
.AU
Charles B. Haley
Dennis M. Ritchie
.AI
.MH
.PP
The distribution tape can be used only on a DEC PDP11/45
or PDP11/70 with RP03, RP04, RP05, RP06 disks and with
a TU10, TU16, or TE16 tape drive.
It consists of some preliminary bootstrapping programs followed by
two file system images;
if needed, after the initial construction of the file systems
individual files can be extracted. (See restor(1))
.PP
If you are set up to do it,
it might be a good idea immediately to make a copy of the
tape to guard against disaster.
The tape is 9-track 800 BPI and contains some 512-byte records
followed by many 10240-byte records.
There are interspersed tapemarks.
.PP
The system as distributed contains binary images
of the system and all the user level programs, along with source
and manual sections for them\(emabout
2100 files altogether.
The binary images,
along with other
things needed to flesh out the file system enough so UNIX will run,
are to be put on one file system called the `root file system'.
The file system size required is about 5000 blocks.
The file second system has all of the source and documentation.
Altogether it amounts to more than 18,000 512-byte blocks.
.SH
Making a Disk From Tape
.PP
Perform the following bootstrap procedure to obtain
a disk with a root file system on it.
.IP 1.
Mount the magtape on drive 0 at load point.
.IP 2.
Mount a formatted disk pack on drive 0.
.IP 3.
Key in and execute at 100000
.RT
.DS
  TU10			  TU16/TE16
012700			Use the DEC ROM or other
172526			means to load block 1
010040			(i.e. second block) at 800 BPI
012740			into location 0 and transfer
060003			to 0.
000777
.DE
.IP
The tape should move and the CPU loop.
(The TU10 code is
.I
not
.R
the DEC bulk ROM for tape;
it reads block 0, not block 1.)
.IP 4.
If you used the above TU10 code, halt and restart the
CPU at 0, otherwise continue to the next step.
.IP 5.
The console should type
.DS
.I
Boot
:
.R
.DE
Copy the magtape to disk by the following procedure.
The machine's printouts are shown in italic,
explanatory comments are within ( ).
Terminate each line you type by carriage return or line-feed.
There are two classes of tape drives:
the name `tm' is used for the TU10, and `ht' is used for
the TU16 or TE16.
There are also two classes of disks:
`rp' is used for the RP03, and `hp' is used for the
RP04/5/6.
.PP
If you should make a mistake while typing, the character '#'
erases the last character typed up to the beginning of the line,
and the character '@' erases the entire line typed.
Some consoles cannot print lower case letters, adjust the
instructions accordingly.
.DS
(bring in the program mkfs)
\fI:\|\fRtm(0,3)		(use `ht(0,3)' for the TU16/TE16)
\fIfile system size:\fR 5000
\fIfile system:\fR rp(0,0)		(use `hp(0,0)' for RP04/5/6)
.I
isize = XX
m/n = XX
.R
(after a while)
.I
exit called
Boot
:
.R
.DE
This step makes an empty file system.
.IP 6.
The next thing to do is to restore the data
onto the new empty file system. To do this you respond to
the `\fI:\fR' printed in the last step with
.DS
(bring in the program restor)
\fI:\|\fRtm(0,4)		(`ht(0,4)' for TU16/TE16)
\fItape?\fR tm(0,5)	(use `ht(0,5)' for TU16/TE16)
\fIdisk?\fR rp(0,0)		(use `hp(0,0)' for RP04/5/6)
\fILast chance before scribbling on disk.\fR (you type return)
(the tape moves, perhaps 5-10 minutes pass)
\fIend of tape\fR
.I
Boot
:
.R
.DE
You now have a UNIX root file system.
.SH
Booting UNIX
.PP
You probably have
the bootstrap running, left over from the last step above;
if not,
repeat the boot process (step 3) again.
Then use one of the following:
.DS
\fI:\|\fRrp(0,0)rptmunix		(for RP03 and TU10)
\fI:\|\fRrp(0,0)rphtunix		(for RP03 and TU16/TE16)
\fI:\|\fRhp(0,0)hptmunix		(for RP04/5/6 and TU10)
\fI:\|\fRhp(0,0)hphtunix		(for RP04/5/6 and TU16/TE16)
.DE
The machine should type the following:
.DS
.I
mem = xxx
#
.R
.DE
The
.I
mem
.R
message gives the memory available to user programs
in bytes.
.PP
UNIX is now running,
and the `UNIX Programmer's manual' applies;
references below of the form X(Y) mean the subsection named
X in section Y of the manual.
The `#' is the prompt from the Shell,
and indicates you are the super-user.
The user name of the super-user is `root'
if you should find yourself in multi-user mode and
need to log in;
the password is also `root'.
.PP
To simplify your life later, rename the appropriate version
of the system as specified above plain `unix.'
For example, use mv (1) as follows if you have an RP04/5/6 and
a TU16 tape:
.DS
mv hphtunix unix
.DE
In the future, when you reboot,
you can type just
.DS
hp(0,0)unix
.DE
to the `:' prompt.
(Choose appropriately among `hp', `rp', `ht', `tm'
according to your configuration).
.PP
You now need to make some special file entries
in the dev directory. These specify what sort of disk you
are running on, what sort of tape drive you have,
and where the file systems are. 
For simplicity, this recipe creates fixed device names.
These names will be used below, and some of them are built into
various programs, so they are most convenient.
However, the names do not always represent the actual major and
minor device in the manner suggested in section 4 of the
Programmer's Manual.
For example, `rp3' will be used for the name of the file system
on which the user file system is put, even though it might be on an RP06
and is not logical device 3.
Also, this sequence will put the user file system on the same
disk drive as the root, which is not the best place
if you have more than one drive.
Thus the prescription below should be taken only as one example
of where to put things.
See also the section on `Disk layout' below.
.PP
In any event, change to the dev directory (cd(1)) and, if you like,
examine and perhaps change the makefile there (make (1)).
.DS
cd /dev
cat makefile
.DE
Then, use one of
.DS
make rp03
make rp04
make rp05
make rp06
.DE
depending on which disk you have.
Then, use one of
.DS
make tm
make ht
.DE
depending on which tape you have.
The file `rp0' refers to the root file system;
`swap' to the swap-space file system; `rp3' to the
user file system.
The devices `rrp0' and `rrp3' are the `raw' versions
of the disks.
Also, `mt0' is tape drive 0, at 800 BPI;
`rmt0' is the raw tape, on which large records can be read
and written;
`nrmt0' is raw tape with the quirk that it does not rewind
on close, which is a subterfuge that permits
multifile tapes to be handled.
.PP
The next thing to do is to extract the rest of the data from
the tape.
Comments are enclosed in ( ); don't type these.
The number in the first command is the
size of the file system;
it differs between RP03, RP04/5, and RP06.
.DS
/etc/mkfs /dev/rp3 74000	(153406 if on RP04/5, 322278 on RP06)
(The above command takes about 2-3 minutes on an RP03)
dd if=/dev/nrmt0 of=/dev/null bs=20b files=6	(skip 6 files on the tape)
restor rf /dev/rmt0 /dev/rp3	(restore the file system)
(Reply with a `return' (CR) to the `Last chance' message)
(The restor takes about 20-30 minutes)
.DE
All of the data on the tape has been extracted.
.PP
You may at this point mount the source
file system (mount(1)). To do this type the following:
.DS
/etc/mount /dev/rp3 /usr
.DE
The source and manual
pages are now available in subdirectories of /usr.
.PP
The above mount command is only needed if you
intend to play around with source on a single
user system, which you are going to do next.
The file system is mounted automatically when multi-user
mode is entered, by a command in the file
/etc/rc. (See `Disk Layout' below).
.PP
Before anything further is done the bootstrap
block on the disk (block 0) should be filled in.
This is done using the command
.DS
dd if=/usr/mdec/rpuboot of=/dev/rp0 count=1
.DE
if you have the RP03, or
.DS
dd if=/usr/mdec/hpuboot of=/dev/rp0 count=1
.DE
if you have an RP04/5/6.
Now the DEC disk bootstraps are usable.
See Boot Procedures(8) for further information.
.PP
Before UNIX is turned up completely,
a few configuration dependent exercises must be
performed.
At this point,
it would be wise to read all of the manuals
(especially `Regenerating System Software')
and to augment this reading with hand to hand
combat.
.SH
Reconfiguration
.PP
The UNIX system running is configured to run
with the given disk
and tape, a console, and no other device.
This is certainly not the correct
configuration.
You will have to correct the configuration table to reflect
the true state of your machine.
.PP
It is wise at this point to know how to recompile the system.
Print (cat(1))
the file /usr/sys/conf/makefile.
This file is input to the program `make(1)' which
if invoked with `make all' will recompile all of
the system source and
install it in the correct libraries.
.PP
The program mkconf(1) prepares files that
describe a given configuration (See mkconf(1)).
In the /usr/sys/conf directory,
the four files
\fIxy\fRconf
were input to mkconf to produce the four versions of the system
\fIxy\fRunix.
Pick the appropriate one, and edit it to add lines describing your own configuration.
(Remember the console typewriter is automatically included;
don't count it in the kl specification.)
Then run mkconf;
it will generate the files l.s
(trap vectors) c.c (configuration table),
and mch0.s.
Take a careful look at
l.s to make sure that all the devices that you
have are assembled in the correct interrupt vectors.
If your configuration is non-standard, you will
have to modify l.s to fit your configuration.
.PP
There are certain magic numbers and
configuration parameters imbedded in various
device drivers that you may want to change.
The device addresses of each device
are defined in each driver.
In case you have any non-standard device
addresses,
just change the address and recompile.
(The device drivers are in the directory
/usr/sys/dev.)
.PP
The DC11 driver is set to run 4 lines.
This can be changed in dc.c.
.PP
The DH11 driver is set to handle 3 DH11's with
a full complement of 48 lines.
If you have less, or more, 
you may want to edit dh.c.
.PP
The DN11 driver will handle 4 DN's.
Edit dn.c.
.PP
The DU11 driver can only handle a single DU.
This cannot be easily changed.
.PP
The KL/DL driver is set up to run
a single DL11-A, -B, or -C (the console)
and no DL11-E's.
To change this, edit
kl.c to have NKL11 reflect the total number of
DL11-ABC's and
NDL11 to reflect the number of DL11-E's.
So far as the driver is concerned,
the difference between the devices is
their address.
.PP
All of the disk and tape drivers
(rf.c, rk.c, rp.c, tm.c, tc.c,
hp.c, ht.c)
are set up to run 8 drives and should not
need to be changed.
The big disk drivers (rp.c and hp.c)
have partition tables in them which you
may want to experiment with.
.PP
After all the corrections
have been made,
use `make(1)' to recompile the system (or
recompile individually if you wish: use the makefile
as a guide).
If you compiled individually, say `make unix' in the
directory /usr/sys/conf.
The final object file (unix) should be
moved to the root, and then booted to try it out.
It is best to name it /nunix so as not to destroy
the working system until you're sure it does work.
See Boot Procedures(8) for a discussion
of booting.
Note:  before taking the system down,
always (!!) perform
a sync(1)
to force delayed output to the disk.
.SH
Special Files
.PP
Next you must put in special files for the new devices in
the directory /dev using mknod(1).
Print the configuration file