diff options
Diffstat (limited to 'distrib/notes')
| -rw-r--r-- | distrib/notes/sun3/contents | 12 | ||||
| -rw-r--r-- | distrib/notes/sun3/hardware | 6 | ||||
| -rw-r--r-- | distrib/notes/sun3/install | 32 | ||||
| -rw-r--r-- | distrib/notes/sun3/prep | 8 | ||||
| -rw-r--r-- | distrib/notes/sun3/whatis | 2 | ||||
| -rw-r--r-- | distrib/notes/sun3/xfer | 4 |
6 files changed, 32 insertions, 32 deletions
diff --git a/distrib/notes/sun3/contents b/distrib/notes/sun3/contents index 1eb6964e2e2..63aec345be2 100644 --- a/distrib/notes/sun3/contents +++ b/distrib/notes/sun3/contents @@ -6,15 +6,15 @@ OpenBSDbsd OpenBSDrd - installboot The OpenBSD/sun3 boot loader installation + installboot The OpenBSD/MACHINE boot loader installation program. - bootxx The OpenBSD/sun3 boot block. - netboot The OpenBSD/sun3 network boot loader. - tapeboot The OpenBSD/sun3 tape boot loader. - ufsboot The OpenBSD/sun3 disk boot loader. + bootxx The OpenBSD/MACHINE boot block. + netboot The OpenBSD/MACHINE network boot loader. + tapeboot The OpenBSD/MACHINE tape boot loader. + ufsboot The OpenBSD/MACHINE disk boot loader. These files can be used to make a boot tape suitable for installing -OpenBSD/sun3. These files can also be used to configure an NFS server +OpenBSD/MACHINE. These files can also be used to configure an NFS server to support installation "over the network". See the section "Getting the OpenBSD System onto Useful Media" for instructions on either method. diff --git a/distrib/notes/sun3/hardware b/distrib/notes/sun3/hardware index 71bc0fdd9c4..f4eca39e5cb 100644 --- a/distrib/notes/sun3/hardware +++ b/distrib/notes/sun3/hardware @@ -1,10 +1,10 @@ -OpenBSD/sun3 OSREV runs on most Sun3 machines, including: +OpenBSD/MACHINE OSREV runs on most MACHINE machines, including: 3/50 3/60, 3/60LE 3/75, 3/110, 3/1[4568]0 3/2[68]0 -OpenBSD/sun3 OSREV does not run on the Sun 3/80 and Sun 3/4x0 (sun3x +OpenBSD/MACHINE OSREV does not run on the Sun 3/80 and Sun 3/4x0 (sun3x class) because the sun3x MMU and other devices are very different. The minimal configuration requires 4M of RAM and ~80MB of disk space. @@ -14,7 +14,7 @@ for sources or packages). To run X or compile the system, more memory is recommended. Acceptable performance requires 8MB of RAM, or 16 MB when running the X Window System. -The following Sun3 hardware is supported: +The following MACHINE hardware is supported: Serial ports (RS232): built-in ttya, ttyb diff --git a/distrib/notes/sun3/install b/distrib/notes/sun3/install index 5d1a2cdb06e..870ecf1468d 100644 --- a/distrib/notes/sun3/install +++ b/distrib/notes/sun3/install @@ -4,7 +4,7 @@ There are several ways to install OpenBSD onto a disk. The easiest way in terms of preliminary setup is to use the OpenBSD miniroot that can be booted off a tape. -If your Sun3 is hooked up in a network and you can find a server to +If your MACHINE is hooked up in a network and you can find a server to arrange for a diskless setup, which is a convenient way to install on a machine whose disk does not currently hold a usable operating system. This is difficult to get set up correctly the first time, but easy to @@ -63,14 +63,14 @@ command at the monitor prompt. Depending on the ethernet chip in your machine, this command takes one of the following forms: > b le()bsd.rd # for sun pizza boxes (3/50, 3/60) - > b ie()bsd.rd # for other sun3s + > b ie()bsd.rd # for other MACHINE This will cause the kernel provided by the diskless setup to be booted. After the initial probe messages you'll asked to start the install or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -In order to have a sun3 machine boot diskless by default, you need to +In order to have a MACHINE machine boot diskless by default, you need to do some nvram wizardry: > q 18 @@ -81,7 +81,7 @@ then, if your machine is a model 3/50 or 3/60, continue with: 00 00 00 -or, for other sun3 machines: +or, for other MACHINE machines: 69 65 00 @@ -174,13 +174,13 @@ OpenBSDBootMsgs the netmask to use and any interface-specific flags to set. The interface-specific flags are usually used to determine which media the network card is to use. This is driver dependent, but for the - sun3 le(4) driver, the flags usually carry meaning: + MACHINE le(4) driver, the flags usually carry meaning: -link0 -link1 Use existing setting (only setup by netboot) link0 -link1 Use UTP (twisted pair) port -link0 link1 Use AUI port -*** IMPORTANT - these are the correct setting for sun3 ethernet cards, +*** IMPORTANT - these are the correct setting for MACHINE ethernet cards, the suggestions shown by the install script are generic and may or may not be correct... @@ -222,7 +222,7 @@ If you will be running your OpenBSD system from a serial console, you may need to edit /etc/ttys and change the terminal type, and getty method from "sun" and "console" to "vt100" and "std.9600" or something similar. -In order to use 'tip' on OpenBSD/sun3, you'll need to edit /etc/ttys +In order to use 'tip' on OpenBSD/MACHINE, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. @@ -240,14 +240,14 @@ least the following pieces: etc{:--:}OSrev.tgz) gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary - a "/boot" file from a SunOS sun3 machine (not sun3x!) + a "/boot" file from a SunOS MACHINE machine (not sun3x!) a kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities are supplied in -the OpenBSD/sun3 distribution. +the OpenBSD/MACHINE distribution. You need to format and partition the disk using SunOS (since -OpenBSD/sun3 uses SunOS disk labels.) Give yourself adequate +OpenBSD/MACHINE uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. @@ -335,25 +335,25 @@ configured correctly. If you have problems, extract the diskless(8) manpage, find someone who's been through it before and use the host syslog and tcpdump(8) to get visibility of what's happening (or not). -Your sun3 expects to be able to download a second stage bootstrap +Your MACHINE expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename -corresponding to the machine's IP address. For example, a sun3 machine +corresponding to the machine's IP address. For example, a MACHINE machine which has been assigned IP address 130.115.144.11, will make an TFTP request for `8273900B'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). -You can find the boot program in `/usr/mdec/netboot' in the OpenBSD/sun3 +You can find the boot program in `/usr/mdec/netboot' in the OpenBSD/MACHINE distribution. Here's an example to illustrate this whole mess: server# cd /<client-root-dir>/usr/mdec - server# cp boot /tftpboot/boot.sun3.OpenBSD + server# cp boot /tftpboot/boot.MACHINE.OpenBSD server# cd /tftpboot - server# ln -s boot.sun3.OpenBSD 8273900B + server# ln -s boot.MACHINE.OpenBSD 8273900B After the boot program has been loaded into memory and given control by @@ -399,7 +399,7 @@ A few configuration files need to be edited: Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 - server:/export/exec/sun3.OpenBSD /usr nfs rw 0 0 + server:/export/exec/MACHINE.OpenBSD /usr nfs rw 0 0 Now you must populate the the `/dev' directory for your client. For this, you can simply change your working directory to `<root>/dev' diff --git a/distrib/notes/sun3/prep b/distrib/notes/sun3/prep index 70f8ead9a5e..bcd713f056a 100644 --- a/distrib/notes/sun3/prep +++ b/distrib/notes/sun3/prep @@ -1,11 +1,11 @@ -Sun3 machines usually need little or no preparation before installing -OpenBSD, other than the usual, well advised precaution of BACKING UP -ALL DATA on any attached storage devices. +Most MACHINE machines usually need little or no preparation before +installing OpenBSD, other than the usual, well advised precaution +of BACKING UP ALL DATA on any attached storage devices. You will need to know the SCSI target ID of the drive on which you will install OpenBSD. -It might be a good time to run the diagnostics on your Sun3. First, +It might be a good time to run the diagnostics on your MACHINE. First, attach a terminal to the "ttya" serial port, then set the "Diag/Norm" switch to the Diagnostic position, and power-on the machine. The Diag. switch setting forces console interaction to occur on ttya. diff --git a/distrib/notes/sun3/whatis b/distrib/notes/sun3/whatis index 1e438c90cad..3918543440b 100644 --- a/distrib/notes/sun3/whatis +++ b/distrib/notes/sun3/whatis @@ -1,2 +1,2 @@ -OpenBSD/sun3 OSREV is a port to the ``sun3'' series of workstations +OpenBSD/MACHINE OSREV is a port to the ``MACHINE'' series of workstations manufactured by Sun in the late 1980s. diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer index 9bf4e703707..5083062d71f 100644 --- a/distrib/notes/sun3/xfer +++ b/distrib/notes/sun3/xfer @@ -109,7 +109,7 @@ To install or upgrade OpenBSD using a tape, you need to do the following: And then: - cd .../OSREV/sun3 + cd .../OSREV/MACHINE sh -x /tmp/maketape @@ -117,7 +117,7 @@ To install or upgrade OpenBSD using a tape, you need to do the following: fetch the OpenBSD files from tape, but want to boot from another device, you can save time and space creating the tape this way: - cd .../OSREV/sun3 + cd .../OSREV/MACHINE sh -x /tmp/maketape noboot |