ralph's update for 3100 install, plus edits for same by kirk

[unix-history] / usr / src / share / doc / smm / 01.setup / 2.t

diff --git a/usr/src/share/doc/smm/01.setup/2.t b/usr/src/share/doc/smm/01.setup/2.t
index 5671157..a665749 100644 (file)
--- a/usr/src/share/doc/smm/01.setup/2.t
+++ b/usr/src/share/doc/smm/01.setup/2.t
@@ -3,7 +3,7 @@
 .\"
 .\" %sccs.include.redist.roff%
 .\"
 .\"
 .\" %sccs.include.redist.roff%
 .\"

-.\"    @(#)2.t 6.6 (Berkeley) %G%
+.\"    @(#)2.t 6.8 (Berkeley) %G%

 .\"
 .ds lq ``
 .ds rq ''
 .\"
 .ds lq ``
 .ds rq ''


@@ -24,10 +24,10 @@ In either case, it is highly desirable to read and understand
 the remainder of this document before proceeding.
 .NH 2
 Bootstrapping from the tape
 the remainder of this document before proceeding.
 .NH 2
 Bootstrapping from the tape

-.PP
+.LP

 The set of files on the distribution tape are as follows:
 .IP 1)
 The set of files on the distribution tape are as follows:
 .IP 1)

-dd (HP300 and DecStation) or dump (Sparc) image of the root filesystem
+dd (HP300 and DECstation) or dump (SPARC) image of the root filesystem

 .IP 2)
 tar image of the
 .Pn /var
 .IP 2)
 tar image of the
 .Pn /var


@@ -45,7 +45,7 @@ tar image of the rest of
 .IP 6)
 (8mm tape only) tar image of
 .Pn /usr/src/X11R5
 .IP 6)
 (8mm tape only) tar image of
 .Pn /usr/src/X11R5

-.PP
+.LP

 The tape bootstrap procedure used to create a
 working system involves the following major steps:
 .IP 1)
 The tape bootstrap procedure used to create a
 working system involves the following major steps:
 .IP 1)


@@ -63,13 +63,12 @@ Extract the system and utility source files as desired.
 .PP
 The following sections describe the above steps in detail.
 The details of the first step vary between architectures.
 .PP
 The following sections describe the above steps in detail.
 The details of the first step vary between architectures.

-The specific steps for the HP300, Sparc, and DecStation are
+The specific steps for the HP300, SPARC, and DECstation are

 given in the next three sections respectively.
 You should follow the instructions for your particular architecture.
 In all sections,
 commands you are expected to type are shown in italics, while that
 information printed by the system is shown emboldened.
 given in the next three sections respectively.
 You should follow the instructions for your particular architecture.
 In all sections,
 commands you are expected to type are shown in italics, while that
 information printed by the system is shown emboldened.

-.PP

 .NH 2
 Booting the HP300
 .NH 3
 .NH 2
 Booting the HP300
 .NH 3


@@ -134,7 +133,7 @@ configured for Domain/OS, EISA and VME bus adaptors, audio, the centronics
 port, 1/2" tape drives (7980), CD-ROM, and the PVRX/TVRX 3D graphics displays.
 .NH 3
 Standalone device file naming
 port, 1/2" tape drives (7980), CD-ROM, and the PVRX/TVRX 3D graphics displays.
 .NH 3
 Standalone device file naming

-.PP
+.LP

 The standalone system device name syntax on the HP300 is of the form:
 .DS
 xx(a,c,u,p)
 The standalone system device name syntax on the HP300 is of the form:
 .DS
 xx(a,c,u,p)


@@ -209,11 +208,12 @@ There are two approaches to getting the root filesystem from tape to disk.
 If you have an extra disk, the easiest approach is to use
 .Xr dd (1)
 under HP-UX to copy the root filesystem image from the tape to the beginning
 If you have an extra disk, the easiest approach is to use
 .Xr dd (1)
 under HP-UX to copy the root filesystem image from the tape to the beginning

-of the second disk. 
+of the second disk.

 For HPs, the root filesystem image is the first file on the tape.
 It includes a disklabel and bootblock along with the root filesystem.
 An example command to copy the image from tape to the beginning of a disk is:
 .DS
 For HPs, the root filesystem image is the first file on the tape.
 It includes a disklabel and bootblock along with the root filesystem.
 An example command to copy the image from tape to the beginning of a disk is:
 .DS

+.ft CW

 dd if=/dev/rmt/0m of=/dev/rdsk/1s0 bs=20b
 .DE
 The actual special file syntax may vary depending on unit numbers and
 dd if=/dev/rmt/0m of=/dev/rdsk/1s0 bs=20b
 .DE
 The actual special file syntax may vary depending on unit numbers and


@@ -226,7 +226,7 @@ man pages for details.
 .PP
 If you have only a single machine with a single disk,
 you need to use the more difficult approach of booting a
 .PP
 If you have only a single machine with a single disk,
 you need to use the more difficult approach of booting a

-standalone copy program, and using that to copy the 
+standalone copy program, and using that to copy the

 root filesystem image from the tape to the disk.
 If your distribution is on 8mm tape and you have an 8mm drive attached
 to the target machine, you should be able to boot from the distribution
 root filesystem image from the tape to the disk.
 If your distribution is on 8mm tape and you have an 8mm drive attached
 to the target machine, you should be able to boot from the distribution


@@ -238,6 +238,7 @@ To do this, you need to extract the first file of the distribution tape
 drive and then create a bootable cartridge or DAT tape.
 For example:
 .DS
 drive and then create a bootable cartridge or DAT tape.
 For example:
 .DS

+.ft CW

 dd if=/dev/rst0 of=bootimage bs=20b
 rcp bootimage foo:/tmp/bootimage
 <login to foo>
 dd if=/dev/rst0 of=bootimage bs=20b
 rcp bootimage foo:/tmp/bootimage
 <login to foo>


@@ -318,7 +319,7 @@ will be discussed later.
 .PP
 UNIX itself then runs for the first time and begins by printing out a banner
 identifying the release and
 .PP
 UNIX itself then runs for the first time and begins by printing out a banner
 identifying the release and

-version of the system that is in use and the date that it was compiled.  
+version of the system that is in use and the date that it was compiled. 

 .PP
 Next the
 .I mem
 .PP
 Next the
 .I mem


@@ -346,7 +347,7 @@ present in the configuration description
 is printed out at boot time as the system verifies that each device
 is present.
 .PP
 is printed out at boot time as the system verifies that each device
 is present.
 .PP

-The \*(lqroot device?\*(rq prompt was printed by the system 
+The \*(lqroot device?\*(rq prompt was printed by the system

 to ask you for the name of the root filesystem to use.
 This happens because the distribution system is a \fIgeneric\fP
 system, i.e., it can be bootstrapped on a cpu with its root device
 to ask you for the name of the root filesystem to use.
 This happens because the distribution system is a \fIgeneric\fP
 system, i.e., it can be bootstrapped on a cpu with its root device


@@ -369,7 +370,7 @@ that was executed by the root shell when it started.  This message
 is present to inform you as to what values the character erase,
 line erase, and interrupt characters have been set.
 .NH 4
 is present to inform you as to what values the character erase,
 line erase, and interrupt characters have been set.
 .NH 4

-Step 4: restoring the root filesystem
+Step 4: (optional) restoring the root filesystem

 .PP
 UNIX is now running,
 and the \fIUNIX Programmer's manual\fP applies.  The ``#'' is the prompt
 .PP
 UNIX is now running,
 and the \fIUNIX Programmer's manual\fP applies.  The ``#'' is the prompt


@@ -388,7 +389,7 @@ or peak performance is not an issue, you can skip this step and
 proceed directly to step 5.
 .PP
 Connect a second disk to your machine.
 proceed directly to step 5.
 .PP
 Connect a second disk to your machine.

-If you bootstraped using the two disk method, you can
+If you bootstrapped using the two disk method, you can

 overwrite your initial bootstrapping disk, as it will no longer
 be needed.
 .PP
 overwrite your initial bootstrapping disk, as it will no longer
 be needed.
 .PP


@@ -452,7 +453,7 @@ The hardware supported by \*(4B for the SPARC is as follows:
 .TS
 center box;
 lw(1i) lw(4i).
 .TS
 center box;
 lw(1i) lw(4i).

-CPUs    T{
+CPUs   T{

 SPARCstation 1 series (1, 1+, SLC, IPC) and
 SPARCstation 2 series (2, IPX).
 T}
 SPARCstation 1 series (1, 1+, SLC, IPC) and
 SPARCstation 2 series (2, IPX).
 T}


@@ -556,6 +557,7 @@ Mount the new root, then copy the SunOS
 into place and use the SunOS ``installboot'' program
 to enable disk-based booting:
 .DS
 into place and use the SunOS ``installboot'' program
 to enable disk-based booting:
 .DS

+.ft CW

 # mount /dev/sd3a /mnt
 # cp /boot /mnt/boot
 # umount /dev/sd3a
 # mount /dev/sd3a /mnt
 # cp /boot /mnt/boot
 # umount /dev/sd3a


@@ -570,6 +572,7 @@ does not handle the new \*(4B filesystem format.
 .IP 5)
 Mount the new root and restore the root.
 .DS
 .IP 5)
 Mount the new root and restore the root.
 .DS

+.ft CW

 # mount /dev/sd3a /mnt
 # cd /mnt
 # rrestore xf tapehost:/dev/nrst0
 # mount /dev/sd3a /mnt
 # cd /mnt
 # rrestore xf tapehost:/dev/nrst0


@@ -582,6 +585,7 @@ Boot the supplied kernel.  Configure the network, build
 .Pn /usr ,
 mount it, and restore it:
 .DS
 .Pn /usr ,
 mount it, and restore it:
 .DS

+.ft CW

 # halt
 ok boot disk3 -s                       [for old proms] OR
 ok boot sd(0,3)vmunix -s               [for new proms]
 # halt
 ok boot disk3 -s                       [for old proms] OR
 ok boot sd(0,3)vmunix -s               [for new proms]


@@ -597,6 +601,7 @@ ok boot sd(0,3)vmunix -s            [for new proms]
 .IP 7)
 At this point you may wish to set up \*(4B to reboot automatically:
 .DS
 .IP 7)
 At this point you may wish to set up \*(4B to reboot automatically:
 .DS

+.ft CW

 # halt
 ok setenv boot-from sd(0,3)vmunix      [for old proms] OR
 ok setenv boot-device disk3            [for new proms]
 # halt
 ok setenv boot-from sd(0,3)vmunix      [for old proms] OR
 ok setenv boot-device disk3            [for new proms]


@@ -612,6 +617,7 @@ If you wish to run SunOS binaries that use SunOS shared libraries, you
 simply need to copy all of the dynamic linker files from an existing
 SunOS system:
 .DS
 simply need to copy all of the dynamic linker files from an existing
 SunOS system:
 .DS

+.ft CW

 # rcp sunos-host:/etc/ld.so.cache /etc/
 # rcp sunos-host:'/usr/lib/*.so*' /usr/lib/
 .DE
 # rcp sunos-host:/etc/ld.so.cache /etc/
 # rcp sunos-host:'/usr/lib/*.so*' /usr/lib/
 .DE


@@ -619,32 +625,163 @@ The SunOS compiler and linker should be able to produce SunOS binaries
 under \*(4B, but this has not been tested.  If you plan to try it you
 will need the appropriate .sa files as well.
 .NH 2
 under \*(4B, but this has not been tested.  If you plan to try it you
 will need the appropriate .sa files as well.
 .NH 2

-Booting the DecStation
+Booting the DECstation

 .NH 3
 Supported hardware
 .NH 3
 Supported hardware

+.LP
+The hardware supported by \*(4B for the DECstation is as follows:
+.TS
+center box;
+lw(1i) lw(4i).
+CPUs   T{
+R2000 based (3100) and
+R3000 based (5000/200, 5000/20, 5000/25, 5000/1xx).
+T}
+_
+DISKs  T{
+SCSI-I (tested RZ23, RZ55, RZ57, Maxtor 8760S).
+T}
+_
+TAPEs  T{
+SCSI-I (tested DEC TK50, Archive DAT, Emulex MT02).
+T}
+_
+RS232  T{
+Internal DEC dc7085 and AMD 8530 based interfaces.
+T}
+_
+NETWORK        T{
+TURBOchannel PMAD-AA and internal LANCE based interfaces.
+T}
+_
+GRAPHICS       T{
+Terminal emulation and raw frame buffer support for
+3100 (color & monochrome),
+TURBOchannel PMAG-AA, PMAG-BA, PMAG-DV.
+T}
+_
+INPUT  T{
+Standard DEC keyboard (LK201) and mouse.
+T}
+_
+MISC   T{
+Battery-backed real time clock,
+internal and TURBOchannel PMAZ-AA SCSI interfaces.
+T}
+.TE
+.LP
+Major items not supported include the 5000/240 (there is code but not
+compiled in or tested),
+R4000 based machines, FDDI and audio interfaces.
+Diskless machines are not supported but booting kernels and bootstrapping
+over the network is supported on the 5000 series.

 .NH 3
 The Procedure
 .PP
 .NH 3
 The Procedure
 .PP

-Steps to bootstrap a system.
-.IP 1)
-Load kernel and root filesystem into memory with one of the PROM commands.
-This is the only step that depends on what type of machine you are using.
-The 'cnfg' PROM command will display what devices are available
-(DEC 5000 only).
-The 'm' argument tells the kernel to look for a root filesystem in memory.
+The first file on the distribution tape is a tar file which contains
+four files.
+The first step requires a running UNIX (or ULTRIX) system that can
+be used to extract the tar archive from the first file on the tape.
+The command:

 .DS
 .DS

-DEC 3100:      boot -f tz(0,5,0) m     # 5 is the SCSI id of the TK50
-DEC 5000:      boot 5/tz6 m            # 6 is the SCSI id of the TK50
-DEC 5000:      boot 6/tftp/bootfile m  # requires bootp on host
+.ft CW
+tar xf /dev/rmt0

 .DE
 .DE

-.IP 2)
-Format the disk if needed. Most SCSI disks are already formatted.
+will extract the following four files:

 .DS
 .DS

-format
+A) root.image: \fIdd\fP image of the root filesystem
+B) vmunix.tape: \fIdd\fP image for creating boot tapes
+C) vmunix.net: file for booting over the network
+D) root.dump: dump image of the root filesystem

 .DE
 .DE

-.IP 3)
-Label disks and create filesystems.
+There are three basic ways a system can be bootstrapped corresponding to the
+first three files.
+You may want to read the section on bootstrapping the HP300
+since many of the steps are similar.
+A spare, formatted SCSI disk is also useful.
+.NH 4
+Procedure A: copy root filesystem to disk
+.PP
+This procedure is similar to the HP300.
+If you have an extra disk, the easiest approach is to use \fIdd\fP\|(1)
+under ULTRIX to copy the root filesystem image to the beginning
+of the spare disk. 
+The root filesystem image includes a disklabel and bootblock along with the
+root filesystem.
+An example command to copy the image to the beginning of a disk is:
+.DS
+.ft CW
+dd if=root.image of=/dev/rz1c bs=20b
+.DE
+The actual special file syntax will vary depending on unit numbers and
+the version of ULTRIX that is running.
+This system is now ready to boot.
+You will probably want to change the disk label
+to create reasonable partitions for your machine (see section 4.2).
+You can then proceed to section 2.5 to install the rest of the system.
+.NH 4
+Procedure B: bootstrap from tape
+.PP
+If you have only a single machine with a single disk,
+you need to use the more difficult approach of booting a
+kernel and mini-root from tape or the network, and using it to restore
+the root filesystem.
+.PP
+First, you will need to create a boot tape. This can be done using
+\fIdd\fP as in the following example.
+.DS
+.ft CW
+dd if=vmunix.tape of=/dev/nrmt0 bs=1b
+dd if=root.dump of=/dev/nrmt0 bs=20b
+.DE
+The actual special file syntax for the tape drive will vary depending on
+unit numbers, tape device and the version of ULTRIX that is running.
+.PP
+The first file on the boot tape contains a boot header, kernel, and
+mini-root file system that the PROM can copy into memory.
+Installing from tape has only been tested
+on a 3100 and a 5000/200 using a TK50 tape drive. Here are two example
+PROM commands to boot from tape.
+.DS
+.ft CW
+DEC 3100:    boot \-f tz(0,5,0) m    # 5 is the SCSI id of the TK50
+DEC 5000:    boot 5/tz6 m           # 6 is the SCSI id of the TK50
+.DE
+The `m' argument tells the kernel to look for a root filesystem in memory.
+Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
+.NH 4
+Procedure C: bootstrap over the network
+.PP
+You will need a host machine that is running the \fIbootp\fP server 
+with the vmunix.net file installed in the default directory defined by the
+configuration file for \fIbootp\fP.
+Here are two example PROM commands to boot across the net:

 .DS
 .DS

+.ft CW
+DEC 3100:      boot \-f tftp()vmunix.net m
+DEC 5000:      boot 6/tftp/vmunix.net m
+.DE
+This command should load the kernel and mini-root into memory and
+run the same as the tape install (procedure B).
+The rest of the steps are the same except you will need to
+execute the following to start the networking:
+.DS
+.ft CW
+# mount -u /
+# echo 127.0.0.1 localhost >> /etc/hosts
+# echo <your.host.inet.number> myname.my.domain myname >> /etc/hosts
+# echo <friend.host.inet.number> myfriend.my.domain myfriend >> /etc/hosts
+# ifconfig le0 inet myname
+.DE
+Next you should proceed to section 2.4.3 to build a disk-based root filesystem.
+.NH 3
+Label disk and create the root filesystem.
+.LP
+There are five steps to create a disk-based root filesystem.
+.IP 1)
+Label the disk.
+.DS
+.ft CW

 # disklabel -W /dev/rrz?c              # This enables writing the label
 # disklabel -w -r -B /dev/rrz?c $DISKTYPE
 # newfs /dev/rrz?a
 # disklabel -W /dev/rrz?c              # This enables writing the label
 # disklabel -w -r -B /dev/rrz?c $DISKTYPE
 # newfs /dev/rrz?a


@@ -654,44 +791,64 @@ Label disks and create filesystems.
 .DE
 Supported disk types are listed in
 .Pn /etc/disktab .
 .DE
 Supported disk types are listed in
 .Pn /etc/disktab .

-Feel free to add to this list.
-.IP 4)
+.IP 3)

 Restore the root filesystem.
 .DS
 Restore the root filesystem.
 .DS

+.ft CW

 # mount \-u /
 # mount /dev/rz?a /a
 # cd /a
 # mount \-u /
 # mount /dev/rz?a /a
 # cd /a

+.DE
+.ti +0.4i
+If you are restoring locally (procedure B), run:
+.DS
+.ft CW

 # mt \-f /dev/nrmt0 rew
 # restore \-xsf 2 /dev/rmt0
 # mt \-f /dev/nrmt0 rew
 # restore \-xsf 2 /dev/rmt0

+.DE
+.ti +0.4i
+If you are restoring across the net (procedure c), run:
+.DS
+.ft CW
+# rrestore xf myfriend:/path/to/root.dump
+.DE
+.ti +0.4i
+When the restore finishes, clean up with:
+.DS
+.ft CW

 # cd /
 # sync
 # umount /a
 # fsck /dev/rz?a
 .DE
 # cd /
 # sync
 # umount /a
 # fsck /dev/rz?a
 .DE

-.IP 5)
-Initialize the PROM monitor to boot automatically.
+.IP 4)
+Reset the system and initialize the PROM monitor to boot automatically.

 .DS
 .DS

-# halt \-q
-
-DEC 3100:      setenv bootpath boot -f rz(0,?,0)vmunix
+.ft CW
+DEC 3100:      setenv bootpath boot \-f rz(0,?,0)vmunix

 DEC 5000:      setenv bootpath 5/rz?/vmunix -a
 .DE
 DEC 5000:      setenv bootpath 5/rz?/vmunix -a
 .DE

-.IP 6)
+.IP 5)

 After booting UNIX, you will need to create
 .Pn /dev/mouse
 After booting UNIX, you will need to create
 .Pn /dev/mouse

-to run X windows.
-Type `link /dev/xx /dev/mouse' where xx is one of the
-following:
+to run X windows as in the following example.
+.DS
+.ft CW
+rm /dev/mouse
+ln /dev/xx /dev/mouse
+.DE
+The 'xx' should be one of the following:

 .DS
 pm0    raw interface to PMAX graphics devices
 cfb0   raw interface to turbochannel PMAG-BA color frame buffer
 xcfb0  raw interface to maxine graphics devices
 mfb0   raw interface to mono graphics devices
 .DE
 .DS
 pm0    raw interface to PMAX graphics devices
 cfb0   raw interface to turbochannel PMAG-BA color frame buffer
 xcfb0  raw interface to maxine graphics devices
 mfb0   raw interface to mono graphics devices
 .DE

+You can then proceed to section 2.5 to install the rest of the system.

 .NH 2
 Installing the rest of the system
 .PP
 .NH 2
 Installing the rest of the system
 .PP

-All architectures now have a root filesystem up and running and now
+All architectures now have a root filesystem up and running and

 proceed from this point to extract the rest of the data from the tape.
 At a minimum you need to set up the
 .Pn /var
 proceed from this point to extract the rest of the data from the tape.
 At a minimum you need to set up the
 .Pn /var