diff options
Diffstat (limited to 'distrib/notes')
| -rw-r--r-- | distrib/notes/arc/contents | 85 | ||||
| -rw-r--r-- | distrib/notes/arc/hardware | 48 | ||||
| -rw-r--r-- | distrib/notes/arc/install | 205 | ||||
| -rw-r--r-- | distrib/notes/arc/prep | 21 | ||||
| -rw-r--r-- | distrib/notes/arc/upgrade | 2 | ||||
| -rw-r--r-- | distrib/notes/arc/whatis | 3 | ||||
| -rw-r--r-- | distrib/notes/arc/xfer | 71 |
7 files changed, 435 insertions, 0 deletions
diff --git a/distrib/notes/arc/contents b/distrib/notes/arc/contents new file mode 100644 index 00000000000..21e1d223fcf --- /dev/null +++ b/distrib/notes/arc/contents @@ -0,0 +1,85 @@ +The ARC specific portion of the OpenBSD 2.1 release is found in the +"arc" subdirectory of the distribution. That subdirectory is laid +out as follows: + +.../2.1/arc/ + INSTALL.arc Installation notes; this file. + + bins/ arc binary distribution sets; + see below. + + miniroot/ arc boot and installation + floppies; see below. + +There is a arc miniroot image to be found in the "arc/minroot" +subdirectory of the OpenBSD 2.1 distribution. Also there is a +miniroot tar file there. + +The OpenBSD/arc binary distribution sets contain the binaries which +comprise the OpenBSD 2.1 release for arc systems. There are seven binary +distribution sets. The binary distribution sets can be found in +subdirectories of the "arc/bins" subdirectory of the OpenBSD 2.1 +distribution tree, and are as follows: + + base21 The OpenBSD/arc 2.1 base binary distribution. You + MUST install this distribution set. It contains the + base OpenBSD utilities that are necessary for the + system to run and be minimally functional. It + includes shared library support, and excludes + everything described below. + [ 15.0M gzipped, 50.8M uncompressed ] + + comp21 The OpenBSD/arc Compiler tools. All of the tools + relating to C, C++, and FORTRAN (yes, there are two!). + 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. + [ 16.2M gzipped, 61.1M uncompressed ] + + etc21 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.) + [ 93K gzipped, 450K uncompressed ] + + game21 This set includes the games and their manual pages. + [ 2.9M gzipped, 7.5M uncompressed ] + + man21 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. + [ 2.5M gzipped, 9.4M uncompressed ] + + misc21 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.2M uncompressed ] + + text21 This set includes OpenBSD's text processing tools, + including groff, all related programs, and their + manual pages. + [ 1.0M gzipped, 4.2M uncompressed ] + +The arc binary distribution sets are distributed in the same form as +the source distribution sets; catted together, the members of a set +form a gzipped tar file. Each arc 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 xfp" +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/arc/hardware b/distrib/notes/arc/hardware new file mode 100644 index 00000000000..7f0cf40dce4 --- /dev/null +++ b/distrib/notes/arc/hardware @@ -0,0 +1,48 @@ +OpenBSD/arc 2.1 runs on the following classes of machines: + - Acer PICA61 (RISC-PC) Systems. + - Deskstation rPC44. + - Deskstation Tyne. + +OpenBSD/pmax 2.1 does *not* (yet) run on these machines: + - Mips Magnum + - Olivetti systems. + +The minimal configuration requires 8M of RAM and ~60M of disk space. +To install the entire system requires ~150M of disk space, and to run +X or compile the system, 32Mb of RAM and ~1G of disk is recommended. + +Supported devices include: + graphics: + built-in S3 VGA graphics adatper on PICA. + Standard VGA graphics adapter on rPC44 and Tyne. + + keyboard: + Standard PC compatible keyboard with driver softloaded keymaps. + + mouse: + PS2 mouse on PICA + Serial mouse (with X server) on rPC44 and Tyne. + + serial ports: + on-board tty00 and tty01 (PICA. can not yet be used as console) + ISA tty00 and tty01 on systems without serial ports on + the motherboard (Tyne). + ISA tty02 and tty03 on all ISA capable systems. + + paralell ports: + paralell ports is supported on-board (PICA) or on ISA + (rPC44 and Tyne). + + floppy: + floppy is supported on PICA only. + + ethernet: + on-board SONIC controller (PICA) + 3Com Etherlink boards (All ISA capable systems) + + SCSI: + on-board NCR53C96 SCSI controller (PICA) + VLB "Buslogic BT-440C/445C" SCSI controller. + + + diff --git a/distrib/notes/arc/install b/distrib/notes/arc/install new file mode 100644 index 00000000000..0a49230d456 --- /dev/null +++ b/distrib/notes/arc/install @@ -0,0 +1,205 @@ +Installing OpenBSD is a relatively complex process, but if you have +this document in hand it shouldn't be too much trouble. + +There are several ways to install OpenBSD onto a disk. The easiest way +in terms of preliminary setup is to use the OpenBSD simpleroot that can +be booted off your local disk. Alternatively, if your Decstation is +hooked up in a network you can find a server and 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 (see the +section `Installing using a diskless setup' below). + + +Installing using the OpenBSD simpleroot. + +The miniroot is a self-contained OpenBSD filesystem holding a complete +OpenBSD/pmax rootfilesystem plus all utilities necessary to install +OpenBSD on a local disk. It is distributed as a plain file designed to +be transferred to a raw disk partition from which it can be booted +using the appropriate PROM command. + +Loading the simpleroot onto your raw partition is simple. On OpenBSD +as well as SunOS you use a command like: + + # dd if=simpleroot21.fs of=/dev/rsd0c bs=20b conv=sync + +Especially on OpenBSD/pmax you'll have to use /dev/rrz0c or something +like that instead of /dev/rsd0c. + +Keep in mind that this will overwrite the contents of that disk! + +After transferring the simpleroot to disk, bring the system down by: + + # halt + +Then boot the miniroot by typing the appropriate command at the PROM: + + >> boot rz(0,0,0)/bsd # for Decstation 2100/3100 + +or + + >> boot 5/rz0a/bsd # for Decstation 5000's + +If you've loaded the simpleroot onto some other disk than `rz0' adapt +the boot specifier accordingly. + +This will cause the kernel contained in the simpleroot to be booted. +After the initial probe messages you'll asked to choose a shell with +sh as default. Simply type Return here and you are in single user +mode. + +XXX more to come here + +Installing using a diskless setup. + +First, you must setup a diskless client configuration on a server. If +you are using a OpenBSD 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, you'll have to consult +documentation that came with it (on SunOS systems, add_client(8) is a +good start). + +XXX more to come here + +As noted above in the section `Preparing your System for OpenBSD Installation', +you have several options when choosing a location to store the installation +filesets. However, the easiest way is to put the *.tar.gz files you want +to install into the root directory for your client on the server. + +Next, unpack `base.tar.gz' and `etc.tar.gz' on the server in the root +directory for your machine. If you elect to use a separately NFS-mounted +filesystem for `/usr' with your diskless setup, make sure the "./usr" base +files in base.tar.gz end up in the correct location. One way to do this is +to temporarily use a loopback mount on the server, re-routing <root>/usr to +your server's exported OpenBSD "/usr" directory. Also put the kernel and the +install/upgrade scripts into the root directory. + +A few configuration files need to be edited: + + <root>/etc/hosts + Add the IP addresses of both server and client. + + <root>/etc/myname + This files contains the client's hostname; use the same + name as in <root>/etc/hosts. + + <root>/etc/fstab + Enter the entries for the remotely mounted filesystems. + For example: + server:/export/root/client / nfs rw 0 0 + server:/export/exec/sun4.OpenBSD /usr nfs rw 0 0 + +Now you must populate the the `/dev' directory for your client. If you server +runs SunOS 4.x, you can simply change your working directory to `<root>/dev' +and run the MAKEDEV script: `sh MAKEDEV all'. + +On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error +messages about unknown user and groups. These errors are inconsequential +for the purpose of installing OpenBSD. However, you may want to correct them +if you plan to the diskless setup regularly. In that case, you may re-run +MAKEDEV on your OpenBSD machine once it has booted. + +XXX more to come here + +This will boot the OpenBSD kernel in single-user mode. + +If you use a diskless setup with a separately NFS-mounted /usr filesystem, +mount /usr by hand now: + +OpenBSD# mount /usr + +XXX more to come here + +Here follows an example of what you'll see while in the dislabel editor. +Do not touch any of the parameters except for the `label: ' entry and +the actual partition size information at the bottom (the lines starting +with `a:', `b:', ...). + +The size and offset fields are given in sector units. Partitions on +which you intend to have a mountable filesystem, should be given +fstype `4.2BSD'. Remember, the `c' partition should describe the whole +disk. The `(Cyl. x - y)' info that appears after the hash (`#') +character is treated as a comment and need not be filled in when +altering partitions. + +Special note: the line containing `8 partitions:' is best left alone, +even if you define less then eight partitions. If this line displays +a different number and the program complains about it (after you leave +the editor), then try setting it to `8 partitions:'. + + +<BEGIN SAMPLE DISKLABEL SCREEN> +OpenBSD# disklabel rz0 + # /dev/rrz0c: +type: SCSI +disk: SCSI disk +label: Hold Your Breath +flags: +bytes/sector: 512 +sectors/track: 64 +tracks/cylinder: 7 +sectors/cylinder: 448 +cylinders: 1429 +rpm: 3600 +interleave: 1 +trackskew: 0 +cylinderskew: 0 +headswitch: 0 # milliseconds +track-to-track seek: 0 # milliseconds +drivedata: 0 + +8 partitions: +# size offset fstype [fsize bsize cpg] + a: 50176 0 4.2BSD 0 0 0 # (Cyl. 0 - 111) + b: 64512 50176 swap # (Cyl. 112 - 255) + c: 640192 0 unknown # (Cyl. 0 - 1428) + d: 525504 114688 4.2BSD 0 0 0 # (Cyl. 256 - 1428) +<END SAMPLE DISKLABEL SCREEN> + + +else, start the installation script: + +OpenBSD# sh install.sh + + +These scripts will do most of the work of transferring the system from the +tar files onto your disk. You will frequently be asked for confirmation +before the script proceeds with each phase of the installation process. +Occasionally, you'll have to provide a piece of information such as the +name of the disk you want to install on or IP addresses and domain names +you want to assign. If your system has more than one disk, you may want +to look at the output of the dmesg(8) command to see how your disks +have been identified by the kernel. + +The installation script goes through the following phases: + + - determination of the disk to install OpenBSD on + - checking of the partition information on the disk + - creating and mounting the OpenBSD filesystems + - setup of IP configuration + - extraction of the distribution tar files + - installation of boot programs + + +Now try a reboot. (If needed, swap your scsi id's first). Initially +I'd suggest you "boot" (Decstation 2100/3100) or "boot/rz0a/bsd", then +try multiuser after that. if you boot single-user the OpenBSD +incantation to make the root filesystem writable is + + OpenBSD# mount -u /dev/sd0a / + +XXX more to come about setting defaults on the prom prompt + +Congratulations, you have successfully installed OpenBSD 2.1. When you +reboot into OpenBSD, you should log in as "root" at the login prompt. +There is no initial password, but if you're using the machine in a +networked environment, you should create yourself an account and +protect it and the "root" account with good passwords. + +Some of the files in the OpenBSD 2.1 distribution might need to be +tailored for your site. In particular, the /etc/sendmail.cf file will +almost definitely need to be adjusted, and other files in /etc will +probably need to be modified. If you are unfamiliar with UN*X-like +system administration, it's recommended that you buy a book that +discusses it. + diff --git a/distrib/notes/arc/prep b/distrib/notes/arc/prep new file mode 100644 index 00000000000..ebbf1269ff5 --- /dev/null +++ b/distrib/notes/arc/prep @@ -0,0 +1,21 @@ +Before you start you should familiarize yourself with the BIOS setup +and how to run programs from the BIOS screen. + +You should also examine the guide on the OpenBSD/arc web site, which +will hopefully soon have more complete and more up-to-date +instructions than are given in the install document. + +If you're installing OpenBSD/arc for the first time it's a very good idea +to look at the partition sizes of disk you intend installing OpenBSD on. +Changing the size of partitions after you've installed is difficult. +If you do not have a spare bootable disk, it may be simpler to re-install +OpenBSD again from scratch. + +Asumming a classic partition scheme with root (`/') and /usr filesystems, +a comfortable size for the OpenBSD root filesystem partition is about 32M. +Hovever it has shown that 64M is not a bad choise when more packages are +to be installed. A good initial size for the swap partition is twice the +amount of physical memory in your machine or at least 64M. A minimum /usr +partition is ~150M but with that you will run into trouble later. A minimum +size of 350M is recommended. A full binary installation, without X11 or +other additional software, takes about 130MB in `/usr'. diff --git a/distrib/notes/arc/upgrade b/distrib/notes/arc/upgrade new file mode 100644 index 00000000000..a62194904e2 --- /dev/null +++ b/distrib/notes/arc/upgrade @@ -0,0 +1,2 @@ +Because this is the first release of OpenBSD for the pmax - there is no +upgrade option in this release. diff --git a/distrib/notes/arc/whatis b/distrib/notes/arc/whatis new file mode 100644 index 00000000000..3cbc1648c97 --- /dev/null +++ b/distrib/notes/arc/whatis @@ -0,0 +1,3 @@ +OpenBSD 2.1 is the second release of OpenBSD for MIPS R4K ARC Class +systems. This release has support for R4000PC, R4400PC, R4600PC and +R4700PC processors. diff --git a/distrib/notes/arc/xfer b/distrib/notes/arc/xfer new file mode 100644 index 00000000000..27f47aff13d --- /dev/null +++ b/distrib/notes/arc/xfer @@ -0,0 +1,71 @@ +Installation is supported from several media types, including: + NFS partitions + FTP + CD-ROM + +The steps necessary to prepare the distribution sets +for installation depend on which method of installation +you choose. The various methods are explained below. + +To prepare for installing via an NFS partition: + + Place the OpenBSD software you wish to install into + a directory on an NFS server, and make that directory + mountable by the machine which you will be installing + OpenBSD on. This will probably require modifying the + /etc/exports file of the NFS server and resetting + mountd, acts which will require superuser privileges. + Note the numeric IP address of the NFS server and of + the router closest to the the new OpenBSD machine, + if the NFS server is not on a network which is + directly attached to the OpenBSD machine. + + Once you have done this, you can proceed to the next + step in the installation process, preparing your + system for OpenBSD installation. + +To prepare for installing via FTP: + + NOTE: this method of installation is recommended + only for those already familiar with using + the BSD network-manipulation commands and + interfaces. If you aren't, this documentation + should help, but is not intended to be + all-encompassing. + + The preparations for this method of installation + are easy: all you have to do is make sure that + there's some FTP site from which you can retrieve + the OpenBSD installation when it's time to do + the install. You should know the numeric IP + address of that site, the numeric IP address of + your nearest router if one is necessary + + Once you have done this, you can proceed to the next + step in the installation process, preparing your + system for OpenBSD installation. + +To prepare for installing via a CD-ROM: + + To install OpenBSD from a CD-ROM, you need to somehow + get the OpenBSD filesets you wish to install on + your system on to the appropriate kind of tape, + in tar format. + + If you're making the tape on a UN*X system, the easiest + way to do so is: + + tar cvf <tape_device> <files> + + where "<tape_device>" is the name of the tape device + that describes the tape drive you're using (possibly + something like /dev/nrst0, but we make no guarantees 8-). + Under SunOS 5.x, this would be something like /dev/rmt/0mbn. + Again, your mileage may vary. If you can't figure it out, + ask your system administrator. "<files>" are the names + of the "set_name.nnn" files which you want to be placed + on the tape. + + Once you have done this, you can proceed to the next + step in the installation process, preparing your + system for OpenBSD installation. |