INSTALLATION NOTES for OpenBSD/pmax 2.8 What is OpenBSD? ---------------- OpenBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. Continuing the multi-platform tradition, OpenBSD has added ports to mvme68k, powerpc and arc machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. You can look for this trend to continue. Security of the system as a whole has been significantly improved. Source code for all critical system components has been checked for remote-access, local-access, denial-of-service, data destruction, or information-gathering problems. Tools like ssh, ipf, ipnat, and nc have been added to the tree because security conscious people often need them. OpenBSD 2.8 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. Cryptography components are part of OpenBSD. OpenBSD is from Canada, and export of these pieces (such as kerberosIV) to the world is not restricted. Note that it can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distrib- ution from an FTP server in the US if you are outside of Canada and the US. Many new user programs have been added in OpenBSD 2.8, as well, bringing it closer to our goal of supplying a complete and modern UN*X-like environment. Tools like perl and ksh are standard, as are numerous other useful tools. OpenBSD 2.8 is the first public release of OpenBSD for the DECstation and DECsystem family of computers. This release includes kernel support for ELF shared libraries and uses them throughout the userland. Sources of OpenBSD: ------------------- This is a list of currently known ftp servers: Australia: ftp://ftp.aba.net.au/pub/OpenBSD == ftp://ftp.au.openbsd.org/pub/OpenBSD France: ftp://ftp.lip6.fr/pub/OpenBSD == ftp://ftp.fr.openbsd.org/pub/OpenBSD ftp://frp.univ-evry.fr/pub/OpenBSD Germany: ftp://ftp.fu-berlin.de/unix/OpenBSD == ftp://ftp.de.openbsd.org/pub/unix/openbsd/mirrors/OpenBSD Japan: ftp://ftp.tut.ac.jp/OpenBSD == ftp://ftp.jp.openbsd.org/OpenBSD ftp://ftp.dti.ad.jp/pub/OpenBSD Korea: ftp://ftp.snu.ac.kr/pub/OpenBSD/ Sweden: ftp://ftp.stacken.kth.se/pub/OpenBSD == ftp://ftp.se.openbsd.org/pub/OpenBSD ftp://ftp1.se.openbsd.org/pub/OpenBSD Switzerland: ftp://web.eunet.ch/pub/OpenBSD == ftp://ftp.eu.openbsd.org/pub/OpenBSD Taiwan: ftp://openbsd.csie.nctu.edu.tw/pub/OpenBSD Thailand: ftp://ftp.ruibon.ac.th/pup/OpenBSD == ftp://ftp.th.openbsd.org/pub/OpenBSD United Kingdom: ftp://ftp.demon.co.uk/pub/OpenBSD USA: ftp://freestuff.cs.colorado.edu/pub/OpenBSD == ftp://ftp3.usa.openbsd.org/pub/OpenBSD ftp://openbsd.eecs.umich.edu/pub/OpenBSD == ftp://ftp1.usa.openbsd.org/pub/OpenBSD ftp://ftp4.usa.openbsd.org/pub/OpenBSD ftp://ftp.geek-girl.com/pub/OpenBSD == ftp://ftp.usa.openbsd.org/pub/OpenBSD ftp://ftp6.usa.openbsd.org/pub/OpenBSD ftp://ftp.op.net/pub/OpenBSD Canada: ftp://lager.ucs.ualberta.ca/pub/OpenBSD == ftp://ftp.openbsd.org/pub/OpenBSD ftp://ftp.ca.openbsd.org/pub/OpenBSD ftp://ftp1.ca.openbsd.org/pub/OpenBSD ftp://obsd.compmore.net/pub/OpenBSD == ftp://ftp2.ca.openbsd.org/pub/OpenBSD As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.8/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact deraadt@cvs.openbsd.org. OpenBSD 2.8 Release Contents: ----------------------------- The OpenBSD 2.8 release is organized in the following way. In the .../2.8 directory, for each of the architectures having an OpenBSD 2.8 binary distribution, there is a sub-directory. The pmax-specific portion of the OpenBSD 2.8 release is found in the "pmax" subdirectory of the distribution. That subdirectory is laid out as follows: .../2.8/pmax/ INSTALL.pmax Installation notes; this file. CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. *.tgz pmax binary distribution sets; see below. simpleroot* pmax boot and installation simpleroot files; see below. There is a pmax simpleroot image named simpleroot28.fs (it is usually compressed using gzip - simpleroot28.fs.gz - so you need gunzip first to uncompress it) subdirectory of the OpenBSD 2.8 distribution. This file you can dump onto a disk and boot from it to start the installation of OpenBSD/pmax. Also there is a simpleroot28.tgz file there. It can be used as root area on the NFS server if you plan to install via network. The OpenBSD/pmax binary distribution sets contain the binaries which comprise the OpenBSD 2.8 release for pmax systems. There are ten binary distribution sets. The binary distribution sets can be found in the "pmax" subdirectory of the OpenBSD 2.8 distribution tree, and are as follows: base28 The OpenBSD/pmax 2.8 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. [ 20.9M gzipped, 69.6M uncompressed ] comp28 The OpenBSD/pmax Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!) are supported. 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. [ 17.6M gzipped, 69.2M uncompressed ] etc28 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.) [ 162.4K gzipped, 730.0K uncompressed ] game28 This set includes the games and their manual pages. [ 2.7M gzipped, 7.0M uncompressed ] man28 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. [ 3.4M gzipped, 13.1M uncompressed ] misc28 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.6M gzipped, 5.4M uncompressed ] xbase28 This set includes the base X distribution. This includes programs, headers, libraries, configuration files. xfont28 This set includes all of the X fonts. xserv28 This set includes all of the X servers. OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/pmax 28 runs on the following classes of machines: - Decstation 2100 and 3100, also known as "pmin" and "pmax" - Personal Decstations (5000/20, and /25) also known as "MAXINE" - Decstation 5000/120, /125, and /133, also known as "3MIN" - Decstation 5000/200, also known as "3MAX" - Decstation 5000/240, also known as "3MAXPLUS" OpenBSD/pmax 28 does *not* (yet) run on these machines: - Decstation 5100 (an r2000-based cousin of the Decstation 3100) - Decsystem 5400 and 5500 (Qbus-based systems, similar to a Vax 'Mayfair' and 'Mayfair II', but with an r2000a or r3000 cpu instead of a CVAX cpu.) - Decsystem 5800 (xbi-based multiprocessor, a Vax 8800 with Vax CPU boards replaced with Mips cpu boards) The minimal configuration requires 8M of RAM and ~60M of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (OpenBSD with 8M of RAM feels like Ultrix with 8M of RAM.) Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU. Supported devices include: Decstation 2100 and 3100 baseboard video: pm one-bit mono or 8-bit pseudocolor frame buffers. Decstation 5000 series TurboChannel video: PMAG-DV Personal Decstation baseboard 1024x768 frame buffer. PMAG-BA 1024x768 8-bit color frame buffer. PMAGB-BA 1024x768 8-bit color frame buffer. PMAG-AA 1280x1024 four-bit greyscale frame buffer. NOTE: All supported DECstation video produces sync-on-green. Be sure to use either a DEC-compatible fixed-sync monitor or a multisync monitor that supports sync-on-green. serial ports: ttya and ttyb (can be used as console if needed) ethernet: on-board AMD Lance ethernet ("le0"), TURBOchannel AMD Lance ethernet cards. SCSI: on-board DEC "sii" SCSI controller (2100 and 3100) on-board "asc" SCSI controller (5000 series machines) TurboChannel "asc" SCSI controller, NOTE: If you want to connect a tape to the machine which you plan to use under OpenBSD/pmax make shure that the scsi id of the tape is either 5 or 6 because tape support is hardcoded to those ids in the kernel. DEC (LK-201 or compatible) keyboard DEC ("hockey puck" or compatible) mouse. Hardware that we do NOT currently support: Q-bus Decsystem machines Decstation 5100 machines PrestoServe NVRAM on Decstation 5100 machines audio drivers for Personal Decstation machines floppy driver for Personal Decstation machines TurboChannel audio hardware (LoFi) PMAG-C 2-D accelerated framebuffers with onboard i860 processors Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: NFS partitions FTP Tape The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. Those are only the preparations required before you start the installation. 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. If you are using a diskless setup to install OpenBSD on your machine, you can take advantage of the fact that the above has already been done on your machine's server. So, you can conveniently put the OpenBSD filesets in your machine's root filesystem on the server where the install program can find them. 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: 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 tape: To install OpenBSD from a tape, 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 where "" 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. "" 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. Preparing your System for OpenBSD Installation: ----------------------------------------------- Before you start you should familiarize yourself with the boot PROM of your machine. The older Decstation 2100 and 3100 cannot select a kernel from the command line. You need to set the bootpath environment variable to point to the disk and kernel you intend to boot. You should also examine the guide on the OpenBSD/pmax web site, which will hopefully soon have more complete and more up-to-date instructions than are given in the install document. I will try to put there all the corrections to this document in the future. If you're installing OpenBSD/pmax 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. But if you don't have a second disk or plan to do an installation via netbooting you don't have any choice about the partition sizes (at least not for the root and the swap partitions) because they are set in the simpleroot image to 40M for root and 64M for swap. About the rest of your disk you can still decide yourself. Assuming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the OpenBSD root filesystem partition is about 32M; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike Ultrix, there are no restrictions on the size of the swap partition that would render part of your memory unusable). A full binary installation, without X11 or other additional software, takes about 130MB in `/usr'. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. Also i wanted to note that the installation procedure via install script is new for the pmax and i had only the chance of limited testing for it - so if you run into any problems with it or if this documentation is somehow unclear - please send me a mail and I'll try to help you or to fix the problem. 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 another convenient way to install OpenBSD/pmax. Installing using the OpenBSD simpleroot. The simpleroot is a self-contained OpenBSD filesystem holding a complete OpenBSD/pmax root filesystem 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 from which it can be booted using the appropriate PROM command. Loading the simpleroot onto your raw partition is simple. You can do this on any machine you can hang on the disk which you plan to put onto the pmax which allows you to write to the raw disk - i.e. on all UN*X like operating systems it should work using "dd". On OpenBSD as well as SunOS you use a command like: # dd if=simpleroot28.fs of=/dev/rsd0c bs=20b 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 and hang the disk onto the pmax you want to install OpenBSD/pmax on. Then boot the simpleroot by typing the appropriate command at the PROM: >> boot rz(0,0,0)/bsd # for Decstation 2100/3100 >> boot 5/rz0a/bsd # for Decstation 5000/2xx >> boot 3/rz0a/bsd # for Decstation 5000/1xx 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. For further instructions please read on in the "Continuing the installation from single user mode" below. If the boot hangs without loading the kernel on a Decstation 5000, the SCSI controller may be in a strange state. This can happen if you interrupt the self-test during boot or after hitting the reset button. To fix this, hit ^C to get back to the ROM monitor and enter "init". You should now be able to boot as described above. Note: if booting the kernel in the miniroot should not work - there are two kernels part of the distribution - look at the place you got the distribution from - the kernels are there also - so you can see which kernels there are - usually there should be 3 of them * bsd - a generic kernel which should ask for the root device * bsd.rz0 - generic kernel with root and swap fixed to rz0 don't ask me why - but this should be usable then installing from a simpleroot on a zip disk (which is usually rz5 or rz6 - bsd crashes here :-) * bsd.nfs - a generic kernel with root and swap configured to be on nfs (also this kernel is in ecoff and not in a.out format so that it can be netbooted with a pmax) 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). One part of the distribution of OpenBSD/pmax is a file called simpleroot28.tgz which is a good start for the root filesystem area on the NFS server then you want to install via network. A few configuration files need to be edited: /etc/hosts Add the IP addresses of both server and client. /etc/myname This file contains the client's hostname; use the same name as in /etc/hosts. /etc/fstab Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 Now you must populate the the `/dev' directory for your client. If you have an intelligent tar command on the NFS server the /dev directory inside the simpleroot28.tgz should be usable (i.e. containing special devices and not only files) - else you'll have to remake the devices on the server using cd /export/root/client/dev mv MAKEDEV* .. rm -rf * mkdir fd mv ../MAKEDEV* . ./MAKEDEV all This may not not work correctly on some operating systems. Ok here is in short form what you have to do on the Server to prepare a diskless installation of OpenBSD/pmax assuming the Server is an OpenBSD machine (for instance a PC running OpenBSD/i386). As said above for other systems you'll have to look into the supplied documentation for that systems. All the following should apply also without any major changes to an FreeBSD or NetBSD server. If the following instructions are not enough - you may look at the man pages for the following commands: * tftpd * rarpd * bootpd * rpc.bootparamd Ok - now let's see what to do to set up the server: * set up a file /etc/ethers containing the ethernet hardware address of the pmax you want to boot via net and its hostname (the hardware address you should get via PROM commands) example: --- snip --- 08:00:2b:1a:4b:41 summer --- snip --- * add an entry to /etc/bootptab which looks like the following: --- snip --- .ris.dec:hn:vm=rfc1048 summer:ht=ethernet:ha=08002b1c4d51:ip=10.0.0.5:bf=/bsd --- snip --- * make sure that the following line in /etc/inetd.conf is not commented out: --- snip --- tftp dgram udp wait root /usr/libexec/tftpd tftpd -s /tftpboot --- snip --- if it is commented out (which is the default on OpenBSD for security reasons) - uncomment it and send the inetd process and HUP signal kill -HUP `cat /var/run/inetd.pid` so that it rereads the /etc/inetd.conf file * untar the simpleroot28.tgz on the server in an nfs exported directory - for instance /export/root - so /etc/exports should contain a line like (OpenBSD syntax !) --- snip --- /export -alldirs -root=0:0 summer --- snip --- for the example above - on OpenBSD the tar should be intelligent enough to unpack the /dev directory correctly - on other systems you may look at the comment about /dev above. So what you have to do in this example you have to do: mkdir /export/root cd /export/root tar xvpzf /some_path/simpleroot28.tgz vi /etc/exports (to add the above line) kill -HUP `cat /var/run/mountd.pid` (so that mountd rereads exports) Note: also make sure that the server is configured as nfs server - i.e. for OpenBSD "option NFSSERVER" for the kernel and the following set in /etc/netstart: --- snip --- nfs_server="YES" nfs_client="YES" --- snip --- * create an swapfile using (example 16 mbytes): cd /exports dd if=/dev/zero of=swap bs=1024k count=16 * copy the kernel from the /export/root area to the tftp area: mkdir /tftpboot cp /export/root/bsd_nfs /tftpboot * create a /etc/bootparams file - for example: --- snip --- summer root=prospero:/export/root \ swap=prospero:/export/swap --- snip --- prospero is the hostname of the server in this example * start the required daemons on the server: /usr/sbin/rpc.bootparamd /usr/sbin/rarpd -a and bootpd - either by uncommenting the entry in /etc/inetd.conf and sending inetd an HUP signal like above or by starting it explicitly /usr/sbin/bootpd * now you should be able to boot the pmax using: >> boot -f tftp()/bsd_nfs for 2100/3100 systems or >> boot 6/tftp for a 5000/200 - look into the manual of your pmax for details how to boot via tftp If you plan to use OpenBSD/pmax on a diskless system in the future - keep in mind that the Decstations can only boot ecoff format kernels via net - so you have to convert them explicitly after the kernel compilation to ecoff - therefor in the kernel compile dir you can do the following after the kernel compile has finished elf2ecoff bsd.elf bsd.ecoff then you can use the bsd.ecoff for netbooting - as a starting point for the kernel config file you may choose GENERIC_NFS. After you have set up everything correctly you can boot your system over the network into singleuser mode and continue the installation. Continuing the installation from single user mode If you have reached single user mode either via booting the simpleroot image or via booting over the network you will have to relabel/label your disk and put filesystems on the partitions. So here's what you have to do after going into single user mode: - simpleroot image (assuming you have the simpleroot on rz0 and want to install on that disk too - everything behind the ";" is comment) # fsck /dev/rrz0a ; check the filesystem # mount /dev/rz0a / ; mount / read write # mount -t kernfs /kern /kern # ./install - network boot # mount -t kernfs /kern /kern # ./install This script should bring you to a completely installed OpenBSD/pmax system (in theory :-) - if you should run into any problems while installing - please first look at http://www.OpenBSD.org/pmax.html I'll try to collect there any hints, fixes and so on. If your problem can't be solved that way just send me a mail to graichen@OpenBSD.org and I'll try to help you fixing it. If you should somehow fail using the install script and want to restart - you may have to umount any filesystems mounted while running the install script (so all except /) and clean /tmp using: rm /tmp/.??* /tmp/??* then it should be possible to rerun it again. Now some more notes about labeling the disk - which you will have to do in the process of running the install script. Here follows an example of what you'll see while in the disklabel 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:', ...). If you are using the simpleroot image and want to install onto the same disk you put the simpleroot on you'll also have to change the sector, track, cylinder, etc. entries to match the values for your disk. The Problem is to get those values for your disk :-) - you can either look into the /etc/disktab file for an matching entry or boot another verbose system like OpenBSD/i386 with your disk attached an see what it prints out about the geometry of the disk. Also you can get the total size of your disk from the bootup output of the Decstation - look for lines like: rz0 at sii0 drive 0 slave 0 SEAGATE ST1480 rev 7336, 832527 512 byte blocks here 832527 is the number of total sectors on that disk. 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:'. Ok - now lets see how the default disklabel of the simpleroot image looks like: OpenBSD# disklabel rz0 # /dev/rrz0c: type: SCSI disk: simpleroot label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 64 sectors/cylinder: 2048 cylinders: 96 total sectors: 196608 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: 65536 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 32*) b: 131072 65536 swap # (Cyl. 32*- 96*) c: 196608 0 unused 1024 8192 # (Cyl. 0 - 96*) ok - and now let's see how it looks like if it is adapted for the rz0 disk above (SEAGATE ST1480). OpenBSD# disklabel rz0 # /dev/rrz0c: type: SCSI disk: SEAGATE ST1480 r label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 11 sectors/cylinder: 693 cylinders: 832527 total sectors: 832527 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: 65536 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 94*) b: 131072 65536 swap # (Cyl. 94*- 283*) c: 832527 0 unused 1024 8192 # (Cyl. 0 - 1201*) d: 635919 196608 4.2BSD 1024 8192 16 # (Cyl. 283*- 1201*) I hope you got the idea now - maybe it'll take some experiments until you get it right :-). One thing to note here is that you can't change the a and b partitions if you are relabeling the disk you are running the simpleroot on - you'll have to accept the simpleroot values here for those 2 partitions. Note: if you have finished the disklabeling and exited the editor for editing the label in the process of the installation and if you then get a message like: "no disklabel on disk - use the -r option to write one" you should ignore it and answer no to the question if you want to re-edit the disklabel - this is due to a problem with the pmax disklabel code and it should be worked around by the install script. So what does the install script explicitly do ? These script 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. 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 If the installation worked fine we can go on. 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 incarnation to make the root filesystem writable is OpenBSD# fsck -p OpenBSD# mount -u /dev/rz0a / assuming your rootdisk is rz0. Congratulations, you have successfully installed OpenBSD 2.8. When you reboot into OpenBSD, you should log in as "root" at the login prompt. You should create yourself an account and protect it and the "root" account with good passwords. You should have got a mail from the install program we recommend you to read, it contains answers to basic questions you might have about OpenBSD (like setting up your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more). This you can do by running mail and then just enter "1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 2.8 distribution might need to be tailored for your site. We recommend you run: man afterboot which will tell you about a bunch of the files needing to be reviewed. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed OpenBSD System: ------------------------------------------------ Because this is the first release of OpenBSD for the pmax - there is no upgrade option in this release. Getting source code for your OpenBSD System: -------------------------------------------- Now that your OpenBSD system is up and running, you probably want to get access to source code so that you can recompile pieces of the system. A few methods are provided. If you have an OpenBSD CD, the source code is provided. Otherwise, you can get the pieces over the Internet using ANONCVS, CTM or FTP. For more information, see http://www.openbsd.org/anoncvs.html http://www.openbsd.org/ctm.html http://www.openbsd.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual distribution set. Traditionally, the UN*X "man pages" (documentation) are denoted by 'name(section)'. Some examples of this are intro(1), man(1), apropos(1), passwd(1), and passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the least-numbered section name will be displayed. For instance, after logging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where "subject-word" is your topic of interest; a list of possibly related man pages will be displayed. Adding third party software; ``packages'' and ``ports'': ------------------------------------------------------- As complete as your OpenBSD system is, you may want to add any of several excellent third party software applications. There are several ways to do this. You can: 1) Obtain the source code and build the application based upon whatever installation procedures are provided with the application. 2) Use the OpenBSD ``ports'' collection to automatically get any needed source file, apply any required patches, create the application, and install it for you. 3) Use the OpenBSD ``package'' collection to grab a pre-compiled and tested version of the application for your hardware. If you purchased the OpenBSD CD-ROM you already have several popular ``packages'', and the ``ports'' collection. NOTE: Some important packages which are not permitted on the CD (due to patents) are available on our FTP servers. In particular, we provide the USA and international versions of both SSH and PGP. The filenames are: ssh-usa-1.2.27.tgz ssh-intl-1.2.27.tgz pgp-usa-2.6.3.tgz pgp-intl-2.6.3.tgz Instructions for installing applications from the various sources using the different installation methods follow. If emacs is to be installed it should be installed first as it creates the ``info'' directory file that may be modified by other applications. You should also refer to the packages(7) manual page. Installing applications from the CD-ROM package collection: The OpenBSD CD-ROM ships with several applications pre-built for various hardware architectures. The number of applications vary according to available disk space. Check the directory 2.8/packages/pmax to see which packages are available for your hardware architecture. That directory will be on the same CD-ROM containing the OS installation files for your architecture. To install one or more of these packages you must 1) become the superuser (root) 2) mount the appropriage CD-ROM 3) use the ``pkg_add'' command to install the software Example (in which we use su(1) to get superuser privileges, thus you have to be in group "wheel", see the manual page for su(1)). $ su Password: # mkdir -p /cdrom # mount /dev/cd0a /cdrom # pkg_add /cdrom/2.8/packages/pmax/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-20.3.tgz Installing applications from the ftp.openbsd.org package collection: All available packages for your architecture have been placed on ftp.openbsd.org in the directory pub/OpenBSD/2.8/packages/pmax/ You may want to peruse this to see what packages are available. The packages are also on the OpenBSD FTP mirror sites. See http://www.openbsd.org/ftp.html for a list of current ftp mirror sites. Installation of a package is very easy. 1) become the superuser (root) 2) use the ``pkg_add'' command to install the software ``pkg_add'' is smart enough to know how to download the software from the OpenBSD ftp server. Example: $ su Password: # pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/2.8/packages/pmax/emacs-20.3.tgz Note: there are both USA and INTERNATIONAL versions of ssh and pgp on the ftp server. Be sure to grab the correct version. The USA versions, ssh-usa-1.2.26.tgz and pgp-usa-2.6.3.tgz, use RSAREF, a legal requirement for use within the United States due to patent issues. Packages available include (at least): ImageMagick-4.2.0.tgz m4-1.4.tgz Xaw3d-1.3.tgz mm-2.7.tgz aalib-1.2.tgz mpeg_lib-1.2.1.tgz afm-1.0.tgz mpeg_play-2.4.tgz autoconf-2.13.tgz netpbm-19940301.tgz bash-2.03.tgz netpipes-4.1.1-export.tgz bison-1.25.tgz nmh-1.0.tgz bzip2-0.9.0c.tgz pgp-2.6.3-intl.tgz compface-1.0.tgz pgp-2.6.3-usa.tgz cucipop-1.31.tgz pine-4.10.tgz dejagnu-1.3.tgz png-1.0.3.tgz egcs-1.1.2.tgz psutils-1.17-a4.tgz emacs-20.3.tgz psutils-1.17-letter.tgz enscript-1.6.1.tgz screen-3.7.6.tgz ethereal-0.5.1.tgz sharutils-4.2.tgz expect-5.28.tgz sniffit-0.3.5.tgz fetchmail-4.7.9.tgz ssh-1.2.27-intl.tgz freetype-1.2.tgz ssh-1.2.27-usa.tgz gettext-0.10.35.tgz tar-1.12.tgz ghostscript-5.10.tgz tcl-8.0.5.tgz gimp-1.1.4.tgz tcsh-6.08.00.tgz glib-1.2.1.tgz teTeX-0.4.tgz glimpse-4.1.tgz tiff-3.4.tgz gmake-3.77.tgz tk-8.0.5.tgz gnuplot-3.7.tgz transfig-3.2.1.tgz gtk+-1.2.1.tgz unzip-5.40.tgz gv-3.5.8.tgz viewfax-2.3.tgz id-utils-3.2.tgz wget-1.5.3.tgz idled-1.16.tgz xcolors-1.3.tgz iozone-2.01.tgz xfig-3.2.2.tgz ircii-2.8.2-epic3.004.tgz xntp3-5.93e-export.tgz ispell-3.1.20.tgz xpaint-2.5.5.tgz jove-4.16.tgz xpdf-0.80.tgz jpeg-6b.tgz xphoon-91.9.18.tgz lesstif-0.88.0.tgz xspread-2.1.tgz libslang-1.2.2.tgz xv-3.10a.tgz Note: these packages may not exist for all architectures; other packages may be added. Some packages are only available via ftp. Installing applications from the CD-ROM ports collection: The CD-ROM ``ports'' collection is a set of Makefiles, patches, and other files used to control the building and installation of an application from source files. Creating an application from sources can require a lot of disk space, sometimes 50 megabytes or more. The first step is to determine which of your disks has enough room. Once you've made this determination read the file README.ports on CD-ROM 2 to see how to copy or mount the ports directory. To build an application you must: 1) become the superuser (root) 2) have network access, or obtain the actual source files by some other means. 3) cd to the ports directory containing the port you wish to build. To build samba, for example, where you'd previously copied the ports files into the /usr/ports directory: cd /usr/ports/net/samba 4) make 5) make install 6) make clean Installing applications from the OpenBSD ports collection: See http://www.openbsd.org/ports.html for current instructions on obtaining and installing OpenBSD ports. You should also refer to the ports(7) manual page. Installing other applications: If an OpenBSD package or port does not exist for an application you're pretty much on your own. The first thing to do is ask ports@openbsd.org if anyone is working on a port -- there may be one in progress. If no luck there you may try the FreeBSD ports or NetBSD package collection. If you are on an i386 based machine it is quite possible that the FreeBSD port, if one exists, will work for you. If you can't find an existing port try to make your own and feed it back to OpenBSD. That's how our ports collection grows. Some details can be found at http://www.openbsd.org/porting.html with more help coming from the mailing list, ports@openbsd.org. Administrivia: -------------- There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are also two OpenBSD Usenet newsgroups, comp.unix.bsd.openbsd.announce for important announcements and comp.unix.bsd.openbsd.misc for general OpenBSD discussion. To report bugs, use the 'sendbug' command shipped with OpenBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: bugs@OpenBSD.ORG Use of 'sendbug' is encouraged, however, because bugs reported with it are entered into the OpenBSD bugs database, and thus can't slip through the cracks. As a favor, please avoid mailing huge documents or files to the mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it.