diff options
Diffstat (limited to 'distrib/notes/sun3')
| -rw-r--r-- | distrib/notes/sun3/contents | 120 | ||||
| -rw-r--r-- | distrib/notes/sun3/hardware | 55 | ||||
| -rw-r--r-- | distrib/notes/sun3/install | 174 | ||||
| -rw-r--r-- | distrib/notes/sun3/legal | 16 | ||||
| -rw-r--r-- | distrib/notes/sun3/prep | 25 | ||||
| -rw-r--r-- | distrib/notes/sun3/upgrade | 70 | ||||
| -rw-r--r-- | distrib/notes/sun3/whatis | 22 | ||||
| -rw-r--r-- | distrib/notes/sun3/xfer | 125 |
8 files changed, 607 insertions, 0 deletions
diff --git a/distrib/notes/sun3/contents b/distrib/notes/sun3/contents new file mode 100644 index 00000000000..4074b02144b --- /dev/null +++ b/distrib/notes/sun3/contents @@ -0,0 +1,120 @@ + +The sun3-specific portion of the NetBSD 1.1 release is found in the +"sun3" subdirectory of the distribution. That subdirectory is laid +out as follows: + +.../NetBSD-1.1/sun3/ + INSTALL.txt Installation notes; this file. + + install/ Boot programs, a GENERIC kernel, + a stand-alone RAMDISK kernel, + and a miniroot filesystem image. + see below. + + binary/ sun3 binary distribution sets; + see below. + + security/ sun3 security distribution; + see below. + +The NetBSD/sun3 "install" distribution contains files that can be +used to install NetBSD onto a completely "bare" sun3. The files +in the `.../install' directory are described below: + + miniroot.gz A gzipped copy of the miniroot filesystem. + This image is to be un-gzipped and copied + into the swap area of a disk. + + netbsd-rd.gz A gzipped copy of the "RAMDISK kernel" + for installing the miniroot filesystem. + + netbsd-gen.gz A gzipped GENERIC kernel (for upgrade) + + netboot A copy of the network boot program. + This is useful if you are installing + a diskless NetBSD/sun3 system. + + tapeboot A copy of the tape boot program, used + as the first segment of a boot tape. + +These files can be used to make a boot tape suitable for installing +NetBSD/sun3. These files can also be used to configure an NFS server +to support installation "over the network". See the section "Getting +the NetBSD System onto Useful Media" for instructions on either method. + +The NetBSD/sun3 binary distribution sets contain the binaries which +comprise the NetBSD 1.1 release for the sun3. There are seven binary +distribution sets, and the "security" distribution set. The binary +distribution sets can be found in the "sun3/binary" subdirectory of +the NetBSD 1.1 distribution tree, and are as follows: + + base11 The NetBSD/sun3 1.1 base binary distribution. You + MUST install this distribution set. It contains the + base NetBSD utilities that are necessary for the + system to run and be minimally functional. It + includes shared library support, and excludes + everything described below. + [ 7.2M gzipped, 19M uncompressed ] + + comp11 The NetBSD/sun3 Compiler tools. All of the tools + relating to C and C++. This set includes the system + include files (/usr/include), the linker, the compiler + tool chain, and the various system libraries (except + the shared libraries, which are included as part of the + base set). This set also includes the manual pages for + all of the utilities it contains, as well as the system + call and library manual pages. + [ 4.6M gzipped, 14.7M uncompressed ] + + etc11 This distribution set contains the system configuration + files that reside in /etc and in several other places. + This set MUST be installed if you are installing the + system from scratch, but should NOT be used if you are + upgrading. (If you are upgrading, it's recommended that + you get a copy of this set and CAREFULLY upgrade your + configuration files by hand.) + [ 64K gzipped, 348K uncompressed ] + + games11 This set includes the games and their manual pages. + [ 2.8M gzipped, 6.8M uncompressed ] + + man11 This set includes all of the manual pages for the + binaries and other software contained in the base set. + Note that it does not include any of the manual pages + that are included in the other sets. + [ 850K gzipped, 3.3M uncompressed ] + + misc11 This set includes the system dictionaries (which are + rather large), the typesettable document set, and + man pages for other architectures which happen to be + installed from the source tree by default. + [ 1.8M gzipped, 6.5M uncompressed ] + + text11 This set includes NetBSD's text processing tools, + including groff, all related programs, and their + manual pages. + [ 770K gzipped, 2.8M uncompressed ] + +The sun3 security distribution set is named "secr11" and can be found +in the "sun3/security" subdirectory of the NetBSD 1.1 distribution +tree. It contains executables which are built in the "src/domestic" portion +if the NetBSD source tree. It can only be found on those sites which carry +the complete NetBSD distribution and that can legally obtain it. (Remember, +because of United States law, this distribution set may not be exported to +locations outside of the United States and Canada.) +[ 128K gzipped, 275K uncompressed ] + +The sun3 binary distribution sets are distributed as gzipped tar files. +Each sun3 binary distribution set also has its own "CKSUMS" file, just +as the source distribution sets do. + +The instructions given for extracting the source sets work equally +well for the binary sets, but it is worth noting that if you use that +method, the files are extracted "below" the current directory. That +is, if you want to extract the binaries "into" your system, i.e. +replace the system binaries with them, you have to run the "tar xvfp" +from /. Also note that if you upgrade or install this way, those +programs that you are using at the time will NOT be replaced. If you +follow the normal installation or upgrade procedures, this will be +taken care of for you. + diff --git a/distrib/notes/sun3/hardware b/distrib/notes/sun3/hardware new file mode 100644 index 00000000000..f0a267597ea --- /dev/null +++ b/distrib/notes/sun3/hardware @@ -0,0 +1,55 @@ + +NetBSD/sun3 1.1 runs on most Sun3 machines, including: + 3/50, 3/60, 3/110 + 3/75, 3/150, 3/160 + 3/260, 3/280 + +NetBSD/sun3 1.1 does not run on the Sun3/80 (sun3x class) +because the sun3x MMU and other devices are very different. + +The minimal configuration requires 4M of RAM and ~80MB of disk space. +To install the entire system requires much more disk space (approx. +100MB additional space is necessary for full sources). To run X +or compile the system, more RAM is recommended. Good performance +requires 8MB of RAM, or 16 MB when running the X Window System. + +The following Sun3 hardware is supported: + + Serial ports (RS232): + built-in ttya, ttyb + + Video adapters: + bwtwo, cgtwo, cgfour + + Network interfaces: + On-board Lance Ethernet (le) + On-board or VME Intel Ethernet (ie) + + SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.) + On-board "si" (SCSI-3) [Note 1] + VME "si" (SCSI-3) board [Note 1] + + SMD Disks: (the big, heavy ones 8^) + Xylogics 450/451 [Note 2] + Xylogics 753/7053 [Note 2] + + Input devices: + Sun keyboard and mouse + + Miscellaneous: + Battery-backed real-time clock. + +Note 1: + The "si" driver now supports DMA and disconnect/reselect + but due to the imaturity of the DMA code, those features + are disabled by default. To enable DMA (and get faster + SCSI performance) patch the variable si_options in the + file /usr/src/sys/arch/sun3/dev/ncr_si.c as indicated. + +Note 2: + SMD disk support is almost ready, but could not be tested + in time for this release. Drivers are provided for the + Xylogics 450/451 and Xylogics 753/7053 VME boards only as + source code. They compile but have never touched a disk. + +If it's not on this list, there is no support for it in this release. diff --git a/distrib/notes/sun3/install b/distrib/notes/sun3/install new file mode 100644 index 00000000000..43446d32071 --- /dev/null +++ b/distrib/notes/sun3/install @@ -0,0 +1,174 @@ + +Installing NetBSD is a relatively complex process, but if you have +this document in hand it should not be too difficult. + +There are several ways to install NetBSD onto your disk. If your +machine has a tape drive the easiest way is "Installing from tape" +(details below). If your machine is on a network with a suitable +NFS server, then "Installing from NFS" is the next best method. +Otherwise, if you have another Sun machine running SunOS you can +initialize the disk on that machine and then move the disk. +(Installing from SunOS is not recommended.) + + +* Installing from tape: + +Create the NetBSD/sun3 1.1 boot tape as described in the section +entitled "Preparing a boot tape" and boot the tape. At the PROM +monitor prompt, use one of the commands: + >b st() + >b st(0,8,0) +The first example will use the tape on SCSI target 4, where the +second will use SCSI target 5. The '>' is the monitor prompt. + +After the tape loads, you should see many lines of configuration +messages, and then the following "welcome" screen: + + Welcome to the NetBSD/sun3 RAMDISK root! + +This environment is designed to do only three things: +1: Partititon your disk (use the command: edlabel /dev/rsd0c) +2: Copy a miniroot image into the swap partition (/dev/rsd0b) +3: Reboot (using the swap partition, i.e. /dev/sd?b). + +Copying the miniroot can be done several ways, allowing +the source of the miniroot image to be on any of these: + boot tape, NFS server, TFTP server, rsh server + +The easiest is loading from tape, which is done as follows: + mt -f /dev/nrst0 rewind + mt -f /dev/nrst0 fsf 2 + dd bs=32k if=/dev/nrst0 of=/dev/rsd0b +(For help with other methods, please see the install notes.) + +To reboot using the swap partition, first use "halt", +then at the PROM monitor prompt use a command like: + b sd(,,1) -s + +To view this message again, type: cat /.welcome + +[ End of "welcome" screen. ] + +Copy the miniroot as described in the welcome message, and +reboot from that just installed miniroot. See the section +entitled "Booting the miniroot" for details. + + +* Installing from NFS: + +Before you can install from NFS, you must have already configured +your NFS server to support your machine as a diskless client. +Instructions for configuring the server are found in the section +entitled "Getting the NetBSD System onto Useful Media" above. + +First, at the Sun PROM monitor prompt, enter a boot command +using the network interface as the boot device. On desktop +machines this is "le", and "ie" on the others. Examples: + + >b le() -s + >b ie() -s + +After the boot program loads the RAMDISK kernel, you should +see the welcome screen as shown in the "tape boot" section +above. You must configure the network interface before you +can use any network resources. For example the command: + + ssh> ifconfig le0 inet 192.233.20.198 up + +will bring up the network interface with that address. The next +step is to copy the miniroot from your server. This can be done +using either NFS or remote shell. (In the examples that follow, +the server has IP address 192.233.20.195) + +To load the miniroot from an NFS file: + + ssh> mount -r 192.233.20.195:/server/path /mnt + ssh> dd if=/mnt/miniroot of=/dev/rsd0b bs=8k + +To load the miniroot using rsh to the server: + + ssh> run -b dd if=/dev/pipe of=/dev/rsd0b bs=8k + ssh> run -o /dev/pipe rsh 192.233.20.195 zcat miniroot.gz + +Note that "ssh" does not use "sh" syntax. It is a very small +shell designed for the ramdisk kernel. The first command of the +above pair runs a "dd" in the background reading /dev/pipe. The +second of the pair runs an "rsh" command with its standard output +redirected to /dev/pipe. In ssh, the "help" command will show you +a list of commands and options (there are only a few). + + +* Booting the miniroot: + +If the miniroot was installed on partition 'b' of the disk with +SCSI target ID=0 then the PROM boot command would be: + >b sd(0,0,1) -s +With SCSI target ID=2, the the PROM is: + >b sd(0,10,1) -s + +The numbers in parentheses above are: + controller (usually zero) + unit number (SCSI ID * 8, in hexadecimal) + partition number + +Miniroot install program: +------------------------ + +The miniroot's install program is very simple to use. It will guide +you through the entire process, and is well automated. Additional +improvements are planned for future releases. + +The miniroot's install program will: + + * Allow you to place disklabels on additional disks. + The disk we are installing on should already have + been partitioned using the RAMDISK kernel. + + Note that partition sizes and offsets are expressed + in sectors. When you fill out the disklabel, you will + need to specify partition types and filesystem parameters. + If you're unsure what the these values should be, use the + following: + + fstype: 4.2BSD + fsize: 1024 + bsize: 4096 + cpg: 16 + + If the partition will be a swap partition, use the following: + + fstype: swap + fsize: 0 (or blank) + bsize: 0 (or blank) + cpg: 0 (or blank) + + The number of partitions is fixed at 8 (by the Sun PROM). + + * Create filesystems on target partitions. + + * Allow you to set up your system's network configuration. + Remember to specify host names without the domain name + appended to the end. For example use `foo' instead of + `foo.bar.org'. If, during the process of configuring + the network interfaces, you make a mistake, you will + be able to re-configure that interface by simply selecting + it for configuration again. + + * Mount target filesystems. You will be given the opportunity + to manually edit the resulting /etc/fstab. + + * Extract binary sets from the media of your choice. + + * Copy configuration information gathered during the + installation process to your root filesystem. + + * Make device nodes in your root filesystem. + + * Copy a new kernel onto your root partition. + + * Install a new boot block. + + * Check your filesystems for integrity. + +First-time installation on a system through a method other than the +installation program is possible, but strongly discouraged. diff --git a/distrib/notes/sun3/legal b/distrib/notes/sun3/legal new file mode 100644 index 00000000000..e237de43806 --- /dev/null +++ b/distrib/notes/sun3/legal @@ -0,0 +1,16 @@ + + This product includes software developed by the Computer + Systems Laboratory at the University of Utah. + + This product includes software developed by the University of + Vermont and State Agricultural College and Garrett A. Wollman. + + This product includes software developed by Charles D. Cranor. + + This product includes software developed by Adam Glass. + + This product includes software developed by Charles Hannum. + + This product includes software developed by David Jones. + + This product includes software developed by Gordon W. Ross. diff --git a/distrib/notes/sun3/prep b/distrib/notes/sun3/prep new file mode 100644 index 00000000000..e2ed99197ea --- /dev/null +++ b/distrib/notes/sun3/prep @@ -0,0 +1,25 @@ + +Sun3 machines usually need little or no preparation before installing +NetBSD, 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 NetBSD. Note that SunOS/sun3 uses confusing names for +the SCSI devcies: target 1 is sd2, target 2 is sd4, etc. + +It might be a good time to run the diagnostics on your Sun3. 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. + +The console location (ttya, ttyb, or keyboard/display) is controlled +by address 0x1F in the EEPROM, which you can examine and change in +the PROM monitor by entering "q1f" followed by a numeric value (or +just a '.' if you don't want to change it). Console values are: + 00: default graphics display + 10: tty a (9600-N-8-1) + 11: tty b (1200-N-8-1) + 20: Color option board on P4 + +NetBSD will use the EEPROM setting to determine which device to +use as the console, so you should make sure it is correct. diff --git a/distrib/notes/sun3/upgrade b/distrib/notes/sun3/upgrade new file mode 100644 index 00000000000..03413985f35 --- /dev/null +++ b/distrib/notes/sun3/upgrade @@ -0,0 +1,70 @@ + +There is no automated upgrade program in this release. +(This is the first official release for the Sun3 anyway.) +However, it is possible to upgrade your system manually. + +Manual upgrade procedure: + + * Place _at least_ the `base' binary set in a filesystem + accessible to the target machine. A local filesystem + is preferred, since there may be incompatibilities + between the NetBSD 1.1 kernel and older route(8) + binaries. + + * Back up your pre-existing kernel and copy the 1.1 + kernel into your root partition. + + * Reboot with the 1.1 kernel into single-user mode. + + * Check all filesystems: + + /sbin/fsck -p + + * Mount all local filesystems: + + /sbin/mount -a -t nonfs + + * If you keep /usr or /usr/share on an NFS server, you + will want to mount those filesystems as well. To do + this, you will need to enable the network: + + sh /etc/netstart + + NOTE: the route(8) commands may fail due to potential + incompatibilities between route(8) and the NetBSD 1.1 + kernel. Once you have enabled the network, mount the + NFS filesystems. If you use amd(8), you may or may not + have to mount these filesystems manually. Your mileage + may vary. + + * Make sure you are in the root filesystem and extract + the `base' binary set: + + cd / + tar --unlink -zxvpf /path/to/base11.tar.gz + + NOTE: the `--unlink' option is _very_ important! + + * Install a new boot block: + + cd /usr/mdec + cp -p ./ufsboot /mnt/ufsboot + sync ; sleep 1 ; sync + ./installboot /mnt/ufsboot bootxx /dev/rsd0a + # Substitute your root partition here -^ + + * Sync the filesystems: + + sync + + * At this point you may extract any other binary sets + you may have placed on local filesystems, or you may + wish to extract additional sets at a later time. + To extract these sets, use the following commands: + + cd / + tar --unlink -zxvpf <path to set> + +NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, +you should extract that set into another area and carefully merge +the changes by hand. diff --git a/distrib/notes/sun3/whatis b/distrib/notes/sun3/whatis new file mode 100644 index 00000000000..6c55986da91 --- /dev/null +++ b/distrib/notes/sun3/whatis @@ -0,0 +1,22 @@ + +NetBSD 1.1 is the first "full" release of NetBSD for the sun3, +including a full set of binaries. This binary distribution is +referred to elsewhere in this document by the name NetBSD/sun3. +This release offers improved stability and many new features. + +New features added since the 1.0 release include: +* Native boot programs for disk, network, and tape +* Automated installation tools (using a "miniroot") +* New SCSI driver supporting DMA, interrupts, and + disconnect/reselect with SCSI-2 devices (optional) +* Frame buffer drivers for bwtwo, cgtwo, and cgthree, + all compatible with SunOS and the X Window System +* Support for the Virtually Addressed Cache (VAC) on + Sun3/260 models (and vastly improved performance) +* SMD disk drivers -- almost (still need testing) + +Old features (from 1.0 and earier) worth mentioning: +* SunOS 4.1 compatibility (runs most Sun3 applications) +* Supports most SCSI devices (CD-ROM, etc) +* Diskless boot capability +* Built-in kernel debugger diff --git a/distrib/notes/sun3/xfer b/distrib/notes/sun3/xfer new file mode 100644 index 00000000000..c6fdf1ad225 --- /dev/null +++ b/distrib/notes/sun3/xfer @@ -0,0 +1,125 @@ + +Installation is supported from several media types, including: + * Tape + * NFS + * CD-ROM + * FTP + +Note that installing on a "bare" machine requires some bootable +device; either a tape drive or Sun-compatible NFS server. + +The procedure for transferring the distribution sets onto +installation media depends on the type of media. Instructions +for each type of media are given below. + +In order to create installation media, you will need all the +files in these two directories: + .../NetBSD-1.1/sun3/install + .../NetBSD-1-1/sun3/binary + +* Creating boot/install tapes: + +Installing from tape is the simplest method of all. +This method uses two tapes; one called the "boot" +tape, and another called the "install" tape. + +The boot tape is created as follows: + + cd .../NetBSD-1.1/sun3/install + set T = /dev/nrst0 + mt -f $T rewind + dd if=tapeboot of=$T bs=8k conv=sync + dd if=netbsd-rd of=$T bs=8k conv=sync + gzip -d < miniroot.gz | dd of=$T bs=8k + mt -f $T rewind + +The install tape is created as follows: + + cd .../NetBSD-1.1/sun3/install + set T = /dev/nrst0 + mt -f $T rewind + foreach f (base etc comp games man misc text) + gzip -d < $f.gz | dd of=$T bs=8k + end + mt -f $T rewind + +If the tapes do not work as expected, you may need to explicitly +set the EOF mark at the end of each tape segment. It may also be +necessary to use the `conv=osync' argument to dd(1). Note that +this argument is incompatible with the `bs=' argument. Consult +the tape-related manual pages on the system where the tapes are +created for more details. + +* Boot/Install from NFS server: + +If your machine has a disk and network connection, but no tape drive, +it may be convenient for you to install NetBSD over the network. This +involves temporarily booting your machine over NFS, just long enough +so you can initialize its disk. This method requires that you have +access to an NFS server on your network so you can configure it to +support diskless boot for your machine. Configuring the NFS server +is normally a task for a system administrator, and is not trivial. + +If you are using a NetBSD system as the boot-server, have a look at +the diskless(8) manual page for guidelines on how to proceed with +this. If the server runs another operating system, consult the +documentation that came with it (i.e. add_client(8) on SunOS). + +Your Sun3 expects to be able to download a second stage bootstrap +program via TFTP after having acquired its IP address through RARP +when instructed to boot "over the net". It will look for a filename +derived from the machine's IP address expressed in hexadecimal. For +example, a sun3 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 the NetBSD/sun3 "netboot" 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). The netboot program +may be found in the install directory of this distribution. + +The netboot program will query a bootparamd server to find the +NFS server address and path name for its root, and then load a +kernel from that location. The server should have a copy of the +netbsd-rd kernel in the root area for your client (no other files +are needed in the client root) and /etc/bootparams on the server +should have an entry for your client and its root directory. +The client will need access to the miniroot image, which can be +provided using NFS or remote shell. If using NFS, miniroot.gz +must be expanded on the server, because there is no gzip program +in the RAMDISK image. The unzipped miniroot takes 8MB of space. + +If you will be installing NetBSD on several clients, it may be useful +to know that you can use a single NFS root for all the clients as long +as they only use the netbsd-rd kernel. There will be no conflict +between clients because the RAM-disk kernel will not use the NFS root. +No swap file is needed; the RAM-disk kernel does not use that either. + +* Install/Upgrade from CD-ROM: + +This method requires that you boot from another device (i.e. tape +or network, as described above). You may need to make a boot tape +on another machine using the files provided on the CD-ROM. Once +you have booted netbsd-rd (the RAM-disk kernel) and loaded the +miniroot, you can load any of the distribution sets directly from +the CD-ROM. The "install" program in the miniroot automates the +work required to mount the CD-ROM and extract the files. + +* Install/Upgrade via FTP: + +This method requires that you boot from another device (i.e. tape +or network, as described above). You may need to make a boot tape +on another machine using the files in .../install (which you get +via FTP). Once you have booted netbsd-rd (the RAM-disk kernel) +and loaded the miniroot, you can load any of the distribution sets +over the net using FTP. The "install" program in the miniroot +automates the work required to configure the network interface and +transfer the files. + +This method, of course, requires network access to an FTP server. +This might be a local system, or it might even be ftp.NetBSD.ORG +itself. If you wish to use ftp.NetBSD.ORG as your FTP file +server, you may want to keep the following information handy: + + IP Address: 205.149.163.23 + Login: anonymous + Password: <your e-mail address> + Server path: /pub/NetBSD/NetBSD-1.1/sun3/binary |