INSTALLATION NOTES for OpenBSD/i386 2.4 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 ipf, ipnat, and nc have been added to the tree because security conscious people often need them. OpenBSD 2.4 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.4, 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. For the i386, OpenBSD 2.4 brings greater stability and security. As a side effect of the full security audit, many userland programs have been significantly cleaned up and debugged. Sources of OpenBSD: ------------------- This is a list of currently known ftp servers: Korea: ftp://ftp1.kr.openbsd.org/pub/OpenBSD == ftp://sunsite.kren.ne.kr/pub/OpenBSD Australia: ftp://ftp.aba.net.su/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 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 Thailand: ftp://ftp.ruibon.ac.th/pup/OpenBSD == ftp://ftp.th.openbsd.org/pub/OpenBSD Korea: ftp://sunsite.kren.ne.kr/pup/OpenBSD == ftp://ftp.kr.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 ftp://freon.republic.k12.mo.us/pub/OpenBSD frp://ftp.msoe.edu/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 ftp://ftp.styx.org/pub/OpenBSD As well, the file ftp://ftp.openbsd.org/pub/OpenBSD/2.4/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.4 Release Contents: ----------------------------- The OpenBSD 2.4 release is organized in the following way. In the .../2.4 directory, for each of the architectures having an OpenBSD 2.4 binary distribution, there is a sub-directory. The i386-specific portion of the OpenBSD 2.4 release is found in the "i386" subdirectory of the distribution. That subdirectory is laid out as follows: .../2.4/i386/ INSTALL.i386 Installation notes; this file. CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. floppy24.fs The i386 boot and installation floppy; see below. *.tar.gz i386 binary distribution sets; see below. bsd A stock GENERIC i386 kernel which will be installed on your system during the install. As well you may be interested in .../2.4/tools/ miscellaneous i386 installation utilities like rawrite.exe, gzip.exe, and pfdisk.exe; see installation section, below. In summary, there is one i386 floppy image called "floppy24.fs" (which you can copy to a floppy using rawrite.exe or `dd'; as described later in this document). This is a bootable install floppy which can be used both to install and to upgrade OpenBSD to the current version. It is also useful for maintenance and disaster recovery. In addition, the "tools/" directory contains some utilities that might be useful for the installation. Bootable installation/upgrade floppy: This disk contains a file system, is bootable, and has enough utilities on board to prepare your hard disk drive for OpenBSD and to install the OpenBSD distribution. It also holds the utilities needed in order to upgrade a system to the current version of OpenBSD. The OpenBSD/i386 binary distribution sets contain the binaries which comprise the OpenBSD 2.4 release for i386 systems. There are ten binary distribution sets. The binary distribution sets can be found in the "i386" subdirectory of the OpenBSD 2.4 distribution tree, and are as follows: base24 The OpenBSD/i386 2.4 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. [ 11.9M gzipped, 33.3M uncompressed ] comp24 The OpenBSD/i386 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. [ 7.3M gzipped, 23.0M uncompressed ] etc24 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, 490K uncompressed ] game24 This set includes the games and their manual pages. [ 2.7M gzipped, 6.4M uncompressed ] man24 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 ] misc24 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.7M gzipped, 5.8M uncompressed ] text24 This set includes OpenBSD's text processing tools, including groff, all related programs, and their manual pages. [ 944K gzipped, 3.3M uncompressed ] xbase24 This set includes the base X distribution. This includes programs, headers, libraries, configuration files. xfont24 This set includes all of the X fonts. xserv24 This set includes all of the X servers. xlink24 This set includes the X server link kit. OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/i386 2.4 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems with 386-family processors, with or without math coprocessors. It does NOT support MCA systems, such as some IBM PS/2 systems. The minimal configuration is said to require 4M of RAM and 50M of disk space, though we do not know of anyone running with a system quite this minimal today. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (4M of RAM will actually allow you to run X and/or compile, but it won't be speedy. Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) Supported devices include: Floppy controllers. MFM, ESDI, IDE, and RLL hard disk controllers. SCSI host adapters: Adaptec AHA-154xA, -B, -C, and -CF Adaptec AHA-174x Adaptec AIC-6260 and AIC-6360 based boards, including the Adaptec AHA-152x and the SoundBlaster SCSI host adapter. (Note that you cannot boot from these boards if they do not have a boot ROM; only the AHA-152x and motherboards using this chip are likely to be bootable, consequently.) Adaptec AHA-294x[W] cards and some onboard PCI designs using the AIC7870 chip. The 2940AU is known not to perform very well with this driver. Adaptec AHA-394x[W] cards; two AIC7870 chips with an on-board PCI to PCI bridge. Adaptec AIC-7770-based SCSI host adapters (including the Adaptec AHA-274x, AHA-284x families). WD-7000 SCSI host adapters. Buslogic 54x (Adaptec AHA-154x clones; driver on kcadp floppy) BusLogic 445, 74x, 9xx (But not the new "FlashPoint" series of BusLogic SCSI adapters) Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters Ultrastor 14f, 34f, and (possibly) 24f Seagate/Future Domain ISA SCSI adapter cards, including ST01/02 Future Domain TMC-885 Future Domain TMC-950 MDA, CGA, VGA, SVGA, and HGC Display Adapters. (Note that not all of the display adapters OpenBSD/i386 can work with are supported by X. See the XFree86 FAQ for more information.) Serial ports: 8250/16450-based ports 16550-based ports ST16660-base ports XR16850-based ports (only in the pccom driver) AST-style 4-port serial boards [*] BOCA 8-port serial cards [*] Cyclades Cyclom-{4, 8, 16}Y serial boards [*] IBM PC-RT 4-port serial boards [*] Parallel ports. Ethernet adapters: AMD LANCE and PCnet-based ISA Ethernet adapters [*], including: Novell NE1500T Novell NE2100 Kingston 21xx AMD PCnet-based PCI Ethernet adapters, including: BOCALANcard/PCI AT&T StarLAN 10, EN100, and StarLAN Fiber 3COM 3c501 3COM 3c503 3COM 3c505 [*] 3COM 3c507 3COM 3c509, 3c579, 3c589, 3c59x 3COM 3c900, 3c900b, 3c905, and 3c905b Digital DC21x4x-based PCI Ethernet adapters, including: SMC EtherPower 10, 10/100 (PCI only!) Znyx ZX34X Cogent EM100 Digital DE450 Digital DE500 Netgear FA310TX rev D1 Lite-On PNIC BICC Isolan [* and not recently tested] Intel EtherExpress 16 SMC/WD 8003, 8013, and the SMC "Elite16" ISA boards SMC/WD 8216 (the SMC "Elite16 Ultra" ISA boards) [X SEE BELOW] SMC EtherPower II (EPIC 10/100) Novell NE1000, NE2000 Digital DEFPA PCI FDDI adapters Intel EtherExpress 100 Fast Ethernet adapters. Texas Instruments ThunderLAN PCI Ethernet adapters, including: Compaq Netelligent PCI Adapters Compaq NetFlex 3/P Compaq Deskpro integrated adapter Compaq Prosignia integrated adapter Olicom OC2183, OC2325, OC2326 TI ThunderLAN adapters Tape drives: Most SCSI tape drives QIC-02 and QIC-36 format (Archive- and Wangtek- compatible) tape drives [*] [+] CD-ROM drives: Mitsumi CD-ROM drives [*] [+] [Note: The Mitsumi driver device probe is known to cause trouble with several devices!] Most SCSI CD-ROM drives Most ATAPI CD-ROM drives [Note: With single ATAPI device IDE busses, the ATAPI device should be set to SLAVE.] Mice: "Logitech"-style bus mice [*] [+] "Microsoft"-style bus mice [*] [+] "PS/2"-style mice [*] [+] Serial mice (uses serial port driver) Sound Cards: SoundBlaster [*] [+] Gravis Ulrasound and Ultrasound Max [*] [+] [The following drivers are not extensively tested] Personal Sound System [*] [+] Windows Sound System [*] [+] ProAudio Spectrum [*] [+] Miscellaneous: OPTi(82C929) chipset for multi-interface CD-ROM, and sound ISA cards. PCI-PCI bridges and cards which include them, such as the AHA-394x SCSI host adapter and some DC21x4x-based multi-Ethernet cards. APM power management. Drivers for hardware marked with "[*]" are NOT included on the distribution floppies. Except as noted above, all other drivers are present on install floppy. Also, at the present time, the distributed kernels support only one SCSI host adapter per machine. OpenBSD normally allows more, though, so if you have more than one, you can use all of them by compiling a custom kernel once OpenBSD is installed. Support for devices marked with "[+]" IS included in the "generic" kernels, although it is not in the kernel on the installation floppy. Hardware the we do NOT currently support, but get many questions about: NCR 5380-based SCSI host adapters. QIC-40 and QIC-80 tape drives. (Those are the tape drives that connect to the floppy disk controller.) Multiprocessor Pentium and Pentium Pro systems. (Though they should run fine using one processor only.) We are planning future support for many of these devices. To be detected by the distributed kernels, the devices must be configured as follows: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports pccom0 0x3f8 4 [8250/16450/16550/clones] pccom1 0x2f8 3 [8250/16450/16550/clones] pccom2 0x3e8 5 [8250/16450/16550/clones] pccom3 0x2e8 3 [PCMCIA modem cards] ast0 0x1a0 5 [AST 4-port serial card] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] lpt2 0x3bc [polling only] MFM/ESDI/IDE/RLL hard disk controllers wdc0 0x1f0 14 [supports two disks or atapi] wdc1 0x170 15 [supports two disks or atapi] Floppy controller fdc0 0x3f0 6 2 [supports two disks] AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters aha0 0x330 any any aha1 0x334 any any AHA-174x SCSI host adapters (in enhanced mode) ahb0 any any any AHA-284x,274x,2940, aic7770 SCSI host adapters ahc0 any any BT445, BT74x, or BT9xx SCSI host adapters bt0 0x330 any any bt1 0x334 any any Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha0 0x330 any any uha1 0x334 any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters aic0 0x340 11 6 Seagate ST0[12], Future Domain TMC-8xx based SCSI controllers sea0 5 iomem 0xc8000 Symbios Logic/NCR 53C8xx based PCI SCSI host adapters ncr0 any any any WD7000 and TMC-7000 SCSI host adapters wds0 0x350 15 6 wds1 0x358 11 5 SCSI disks sd0 first SCSI disk (by SCSI id) sd1 second SCSI disk (by SCSI id) sd2 third SCSI disk (by SCSI id) sd3 fourth SCSI disk (by SCSI id) SCSI tapes st0 first SCSI tape (by SCSI id) st1 second SCSI tape (by SCSI id) SCSI CD-ROMs cd0 first SCSI CD-ROM (by SCSI id) cd1 second SCSI CD-ROM (by SCSI id) SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards, 3c503, Novell NE1000, or NE2000 Ethernet boards ed0 0x280 9 iomem 0xd0000 ed1 0x250 9 iomem 0xd8000 ed2 0x300 10 iomem 0xcc000 [X SEE BELOW] ed3 0x240 9 iomem 0xd8000 3COM 3c501 Ethernet boards el0 0x300 9 3COM 3c505/Etherlink+ Ethernet boards eg0 0x310 5 3COM 3c509, 3c579, 3c595 Ethernet boards ep0 any any 3COM 3c900, 3c900b, 3c905, 3c905b Ethernet boards xl0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] AT&T StarLAN 10, EN100, or StarLAN Fiber, or 3COM 3c507 Ethernet boards ie0 0x360 7 iomem 0xd0000 EtherExpress boards ie1 0x300 10 PCNet-PCI based Ethernet boards; see above for partial list le0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] DC21x4x based Ethernet boards; see above for partial list de0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] Intel EtherExpress 100 Ethernet boards fxp0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] SMC EtherPower II (EPIC) 10/100 Ethernet boards tx0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] SPECIAL CARE FOR SMC ULTRA ELITE -------------------------------- Note for SMC Elite Ultra ethernet card users: The Elite Ultra is very sensitive to how its I/O port is treated. Mistreating it can cause a number of effects -- everything from the card not responding when the kernel probes, or the soft configuration being corrupted or wiped completely. By default, the kernel ships with device ed2 configured for the 'default' Elite Ultra locations, comprising of port 0x300, irq 10, and memory location 0xcc000. This matches a hard coded jumper on the board as well a common soft config setting. Unfortunately, the kernel's autconfiguration process (specifically, some of the devices it probes for) cause conflicts with the SMC Elite Ultra, and very often cause it to lose its configuration and fail its own probe. If this happens, you must boot the computer into DOS, and run the EzSetup program from SMC (if you do not have a copy on the floppy accompanying your board, the complete URL to download the program is ftp://ftp.smc.com/pub/nics/ethernet/elite_ultra/gez122.exe). This program will allow you to reconfigure and recover a card that has lost its configuration with a minimum of hassle. In order to avoid blowing away the card, one *must* use the run-time kernel configuration system when booting the Install kernel. This is done by giving the -c flag to the initial boot request. Following the loading of the kernel, the user is presented with a UKC> prompt. At this prompt, as variety of commands may be issued, but the relevant one to getting the SMC Elite Ultra running is 'disable'. The wt0, el0, and ie1 devices all need to be disabled. This is done by typing 'disable' followed by the name of the device, i.e., 'disable wt0', and pressing return. If, for some reason, your Elite Ultra is not configured at the 'default' location the kernel is expecting it, you may also use the 'change' command in the UKC system to modify where the kernel will look for it. Typing 'change ed2' will allow you to modify those settings. Note that running the card at an i/o port of anything other then 0x300 at this point is not recommended, and is beyond the scope of this document-- by doing so you risk other device probes wreaking the havoc we are trying to avoid. When all three extra devices are disabled and any changes made, the 'quit' command will exit the UKC. The kernel should then boot, and find your Elite Ultra on device ed2. SPECIAL CARE FOR NEWER NOTEBOOK COMPUTERS AND PCMCIA There is a problem on some newer notebooks with OpenBSD's autoconfiguration not YET finding the PCI<-->PCMCIA bridge, and therefore not finding any of the PCMCIA cards, which can be a nuisance if you're trying to install over an Ethernet LAN. The symptoms: 1) No probe messages indicating any PCMCIA response or any probe response for any PCMCIA cards, and 2) A probe message like this: Cirrus Logic CL-GD6729 (class bridge, subclass PCMCIA, revision 0xfe) at pci0 dev 4 function 0 not configured The details will vary; the important parts are class bridge, subclass PCMCIA, ... at pci* ... not configured Finding the Bridge Address Bear in mind that both ISA and PCI are just different ways of electrically connecting an adaptor into the PC's memory space. PCI merely provides convenient iterators for finding everything on it, which is easier than it is on ISA. This is why you get the "not configured" message above. But once a device is connected in there, the driver only needs to know its memory mapped address. Now we don't know its address on YOUR brand of PC, but we can help you find it out. Someday our software will do this for you, of course, but it doesn't as of today. Your first try should be 0x3000, which seems to be used on several notebooks. If this fails, you need to do some nosing around. The easiest way is to boot up Windows '95, if you have it on a hard disk. Right-click on the "My Computer" Icon, select Properties, select the Device Manager tab, and double click on PCMCIA Socket, then on the Bridge that is listed under this heading. Select Properties at the bottom of the window, and click on Resources. Finally you will see an address range, in Hex. On my Dell Latitude LM, for example, the range was FCFC-FCFF. If you don't have Windows '95 on a hard disk, there are several possibilities: 1) But you do have Windows'95 setup floppies? Then look through them for the ".INF" files, and rummage around in them until you find it. 2) You have a friend, or the dealer, who has a similar Notebook PC with Windows '95 installed? Proceed as above. 3) Call Customer Support at the manufacturer, tell them you're having a setup problem, and need to know the memory address to set for the PCI to PCMCIA bridge. Oh, take a few cans of Jolt and a good book to read while waiting on the line. Fixing it - temporarily OK, now you have the address and size of the memory window for the PCMCIA bridge. Or so you think. To try it out, use the UKC, as described earlier (under SMC Elite, above). Basically you use "boot -c" to get into UKC. Give the command "change pcicmaster0", and to set the address and iosize to the values you found above. Then type "quit", and the boot should continue, and you should find your PCMCIA cards. Note that if the card is an "ep0" (3c589 on PCMCIA) AND you are using UTP, you must give the arguments "link0 link1" on the ifconfig command. The autoconfig message ep0 at pcmcia0 port 0x300-0x30f irq 10: ep0: address nn:nn:nn:nn:nn:nn, utp/aui/bnc (default utp) implies that the default is UTP and you can omit the link* arguments, but in fact you cannot! Fixing it - configuring a new kernel Follow the normal steps for building a new kernel documented elsewhere. For my system I changed the original pcicmaster0 line as follows: #pcicmaster0 at isa? port 0x3E0 size 2 #hack for CL PCIC on Dell Lattitude LM; really on PCI, but... pcicmaster0 at isa? port 0xFCFC size 4 IRQ's: You probably do NOT have to worry about the IRQ's appearing different than what Windows'95 claims. Trust me, and try it. Fixing it for good OK, this is the tough part. Somebody has to wade in and rewrite the OpenBSD PCMCIA subsystem to support multiple adapters on multiple busses. Nobody's done this yet. You have the source, so you truly can "Use The Source, Luke." Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: DOS partitions FFS partitions Tape Remote NFS partition FTP HTTP rsh & restore No matter which installation medium you choose, you'll need to have a floppy disk (1.44Mb required). If you are using a UN*X-like system to write the floppy image to disk, you should use the "dd" command to copy the file system image (floppy24.fs) directly to the raw floppy disks. It is suggested that you read the dd(1) manual page or ask your system administrator to determine the correct set of arguments to use; it will be slightly different from system to system, and a comprehensive list of the possibilities is beyond the scope of this document. If you are using DOS to write the floppy image to disk, you should use the "rawrite" utility, provided in the "2.4/tools" directory of the OpenBSD distribution. It will write the file system image (floppy24.fs) to a disk. Note that when installing, the floppy can be write-protected (i.e. read-only). Obviously, the steps necessary to prepare the distribution sets for installation or upgrade depend on which installation medium you choose. The steps for the various media types are outlined below. To install or upgrade OpenBSD using a tape, you need to do the following: To install OpenBSD from a tape, you need to make a tape that contains the distribution set files, in "tar" format. If you're making the tape on a UN*X-like system, the easiest way to do so is probably something like: tar cf where "" is the name of the tape device that describes the tape drive you're using (possibly /dev/rst0, or something similar, but it will vary from system to system. (If you can't figure it out, ask your system administrator.) In the above example, "" are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the "base24", "etc24", and "bsd" distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: cd .../2.4 # the top of the tree cd i386/ tar cf base24 etc24 bsd (Note that you still need to fill in "" in the example.) Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing OpenBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. To install or upgrade OpenBSD using a remote partition, mounted via NFS, you must do the following: NOTE: This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the OpenBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading OpenBSD. This will probably require modifying the /etc/exports file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading OpenBSD, you need to know the numeric IP address of the router closest to the OpenBSD machine. Finally, you need to know the numeric IP address of the OpenBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing OpenBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. If you are upgrading OpenBSD, you also have the option of installing OpenBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base24" set somewhere in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for OpenBSD Installation: ----------------------------------------------- NOTE: If you wish to install OpenBSD on your whole disk, i.e. you do not want DOS or any other operating system to reside on your hard disk, you can skip this section and go on to the section that describes installation, below. If you're upgrading your system from a previous release of OpenBSD, you should have proceeded directly to the section about upgrading; you need none of the information presented here. First and foremost, before beginning the installation process, MAKE SURE YOU HAVE A RELIABLE BACKUP of any data on your hard disk that you wish to keep. Repartitioning your hard disk is an excellent way to destroy important data. Second, if you are using a disk controller which supports disk geometry translation, be sure to use the same parameters for OpenBSD as for DOS or the other operating systems installed on your disk. If you do not, it will be much harder to make OpenBSD properly coexist with them. Utilities exist which will print out the disk geometry which DOS sees; some versions of DOS "fdisk" also do this. If you have an "EIDE" hard disk, DOS and OpenBSD probably won't see the same geometry, and you must be careful to find out the DOS geometry and tell OpenBSD about it during the installation. Third (but related to the second point above), if you are using a hard disk with more sectors than DOS or your controller's BIOS supports without some kind of software translation utility or other kludge, you MUST BE SURE that all partitions which you want to boot from must start and end below cylinder 1024 by the BIOS's idea of the disk, and that all DOS partitions MUST EXIST ENTIRELY BELOW cylinder 1024, or you will either not be able to boot OpenBSD, not be able to boot DOS, or you may experience data loss or filesystem corruption. Be sure you aren't using geometry translation that you don't know about, but that the DOS "fdisk" program does! Fourth, use the other operating system's "fdisk" program or partition editor to create at least one of the partitions to be used for that operating system. If that operating system is already set up to use the entire disk, you will have to back it up, remove and recreate a smaller partition for it, and then restore the data from that partition. You do not have to create an OpenBSD partition at this time, the OpenBSD install- ation will give you an opportunity to create the partition needed for OpenBSD. Finally, do whatever is necessary to restore order to the partition you took space away from. If it was a DOS partition, you probably will need to use "format" to create a new file system on it, and then restore your important files from your backups. Other operating systems will have different needs; most will need to reformat the partition, and if it was their "main" partition, will probably need to be reinstalled. Once you've backed all your data up, there is a tool called fips 2.0 that can shrink your DOS/Windows/Windows95 partition to make room for OpenBSD. It is included in the i386 tools area of this distribution as a convenience. It is strongly advised that you read its documentation and understand the consequences of your actions before using it. In some cases, defragmenting your disk and running fips may be much faster than reinstalling your DOS partitition from the backup. Your hard disk is now prepared to have OpenBSD installed on it, and you should proceed with the installation instructions. Installing the OpenBSD System: ------------------------------ Installing OpenBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not currently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The OpenBSD kernel will try to discover these parameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) If OpenBSD will be sharing the disk with DOS or another operating system, you should have already completed the section of these notes that instructed you on how to prepare your hard disk. You should know the size of the OpenBSD area of the disk and its offset from the beginning of the disk. You will need this information when setting up your OpenBSD partitions. If you BIOS uses translated geometry, you should use this geometry for the remainder of the install. This is only necessary if you are sharing the disk with other operating systems that use the translated geometry. You should now be ready to install OpenBSD. The following is a walk-through of the steps you will take while getting OpenBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. Boot your machine using the floppy24.fs floppy. When presented with the boot prompt hit return. If the boot prompt does not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the floppy24.fs floppy image to a different disk, and using that. If that doesn't work, try booting after disabling your CPU's internal and external caches (if any). If it still doesn't work, OpenBSD probably can't be run on your hardware. This can probably be considered a bug, so you might want to report it. If you do, please include as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, most likely more than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has happened, either your boot floppy is bad or you are having hardware problems, and should proceed as outlined above. Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disk's name and geometry. Its name will be something like "sd0" or "wd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating OpenBSD partitions. You will also need to know the device name to tell the install tools what disk to install on. If you cannot read the messages as they scroll by, do not worry -- you can get at this information later inside the install program. While booting, you will probably see several warnings. You should be warned that no swap space is present, and that init(8) cannot find /etc/rc. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. Now you will be asked whether you wish to do an "install" or an "upgrade". Enter 'i' for a fresh install or 'u' to upgrade an existing installation. You will be presented with a welcome message and asked if you really wish to install (or upgrade). Assuming you answered yes, you will be asked which terminal type to use. You should just hit return to select the default (pcvt25). The install program will then tell you which disks of that type it can install on, and ask you which it should use. The name of the disk is typically "wd0" for IDE/RLL/ESDI/ST506 drives or "sd0" for SCSI drives. Reply with the name of your disk. Next you will have to edit or create a disk label for the disk OpenBSD is being installed on. If there are any existing partitions defined (for any operating system), and a disk label is not found, you will first be given an opportunity to run fdisk and create an OpenBSD partition. If fdisk is being invoked on your behalf, it will start by displaying the current partitions defined and then allow you to modify this information, add new partitions and change which partition to boot from by default. If you make a mistake, you will be allowed to repeat this procedure as necessary to correct this. Note that you should make OpenBSD be the active partition at least until the install has been completed. Next the disk label which defines the layout of the OpenBSD file systems must be set up. The installation script will invoke an interactive editor allowing you to do this. Note that partition 'c' inside this disk label should ALWAYS reflect the entire disk, including any non-OpenBSD portions. If you are labeling a new disk, you will probably start out with an 'a' partition that spans the disk. In this case You should delete 'a' before adding new partitions. The root file system should be in partition 'a', and swap is usually in partition 'b'. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'h', 'i' and so on. It is recommended that you create separate partitions for /usr, /tmp, and /var, and if you have room for it, one for /home. In doing this, remember to skip 'c', leaving it as type "unused". Create your next partition as 'd' and continue from there with any additional partitions. If you have DOS or Linux partitions defined on the disk, these will usually show up as partition 'h', 'i', and so on. When you are finished with disklabel you will be prompted for the mount points for the partitions in the current label. For help in the disk label editor, enter '?' or 'M' to view the manual page (see the info on the ``-E'' flag). Note that all OpenBSD partitions in the disk label must have an offset that makes it start within the OpenBSD part of the disk, and a size that keeps it inside of that portion of the disk. This is within the bounds of the 'c' partition if the disk is not being shared with other operating systems, and within the OpenBSD fdisk partition if the disk is being shared. The swap partition (usually 'b') should have a type of "swap", all other native OpenBSD partitions should have a type of "4.2BSD". Block and fragment sizes are usually 8192 and 1024 bytes, but can also be 4096 and 512 or even 16384 and 2048 bytes. The install program will now label your disk and ask which file systems should be created on which partitions. It will auto- matically select the 'a' partition to be the root file system. Next it will ask for which disk and partition you want a file system created on. This will be the same as the disk name (eg. "wd0") with the letter identifying the partition (eg. "d") appended (eg. "wd0d"). Then it will ask where this partition is to be mounted, eg. /usr. This process will be repeated until you enter "done". At this point you will be asked to confirm that the file system information you have entered is correct, and given an opportunity to change the file system table. Next it will create the new file systems as specified, OVERWRITING ANY EXISTING DATA. This is the point of no return. After all your file systems have been created, the install program will give you an opportunity to configure the network. The network configuration you enter (if any) can then be used to do the install from another system using NFS, HTTP or FTP, and will also be the configuration used by the system after the installation is complete. If you select to configure the network, the install program will ask you for a name of your system and the DNS domain name to use. Note that the host name should be without the domain part, and that the domain name should NOT include the host name part. Next the system will give you a list of network interfaces you can configure. For each network interface you select to configure, it will ask for the IP address to use, the symbolic host name to use, 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. The flags usually carry the following meaning: -link0 -link1 Use BNC (coaxial) port [default] link0 -link1 Use AUI port link0 link1 Use UTP (twisted pair) port After all network interfaces has been configured the install pro- gram will ask for a default route and IP address of the primary name server to use. You will also be presented with an opportunity to edit the host table. At this point you will be allowed to edit the file system table that will be used for the remainder of the installation and that will be used by the finished system, following which the new file systems will be mounted to complete the installation. After these preparatory steps has been completed, you will be able to extract the distribution sets onto your system. There are several install methods supported; FTP, HTTP, tape, CD-ROM, NFS or a local disk partition. To install from a tape, the distrib- ution sets must have been written to tape prior to running the installation program, either as tar images or as gzipped tar images. Note that installation from floppies is not currently supported. To install via FTP: To begin an FTP install you will need the following pieces of information. Don't be daunted by this list; the defaults are sufficient for most people. 1) Proxy server URL if you are using a URL-based ftp proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing ftp (assuming you have a proxy available to use). 2) Do you need to use active mode ftp? By default, ftp will attempt to use passive mode and fall back to an active connection if the server does not support passive mode. You only need to enable this option if you are connecting to a buggy ftp daemon that implements passive ftp incorrectly. Note that you will not be asked about active ftp if you are using a proxy. 3) The IP address (or hostname if you enabled DNS earlier in the install) of an ftp server carrying the OpenBSD 2.4 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The ftp directory holding the distribution sets. The default value of pub/OpenBSD/2.4/i386 is almost always correct. 5) The login and password for the ftp account. You will only be asked for a password for non-anonymous ftp. For instructions on how to complete the installation via ftp, see the section named "Common URL installations" below. To install via HTTP: To begin an HTTP install you will need the following pieces of information: 1) Proxy server URL if you are using a URL-based http proxy (squid, CERN ftp, Apache 1.2 or higher). You need to define a proxy if you are behind a firewall that blocks outgoing http connections (assuming you have a proxy available to use). 3) The IP address (or hostname if you enabled DNS earlier in the install) of an http server carrying the OpenBSD 2.4 distribution. If you don't know, just hit return when asked if you want to see a list of such hosts. 4) The directory holding the distribution sets. There is no standard location for this; You should use the directory specified along with the server in the list of official http mirror sites that you received in step 3. For instructions on how to complete the installation via http, see the section named "Common URL installations" below. To install from tape: In order to install from tape, the distribution sets to be installed must have been written to tape previously, either in tar format or gzip-compressed tar format. You will also have to identify the tape device where the distribution sets are to be extracted from. This will typically be "nrst0" (no-rewind, raw interface). Next you will have to provide the file number of the set that is to be extracted. Note that the file number starts at 1, which is the first file written to the tape. The install program will not automatically detect whether an image has been compressed, so it will ask for that information before starting the extraction. To install from CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be either "cd0" or "acd0". Next you will be asked which partition on the CD-ROM the distribution is to be loaded from. This is normally partition "a". Next you will have to identify the file system type that has been used to create the distribution on the CD-ROM, this can be either FFS or ISO CD9660. The OpenBSD CD distribution uses the CD9660 format. You will also have to provide the relative path to the directory on the CD which holds the distribution, for the i386 this is "2.4/i386". For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a NFS mounted directory: When installing from a NFS-mounted directory, you must have completed network configuration above, and also set up the exported file system on the NFS server in advance. First you must identify the IP address of the NFS server to load the distribution from, and the file system the server expects you to mount. The install program will also ask whether or not TCP should be used for transport (the default is UDP). Note that TCP only works with newer NFS servers. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. For instructions on how to complete the installation from the CD-ROM distribution, see the section named "Common file system installations" below. To install from a local disk partition: When installing from a local disk partition, you will first have to identify which disk holds the distribution sets. This is normally "wdN" or "sdN" where N is a number 0 through 9. Next you will have to identify the partition within that disk that holds the distribution, this is a single letter between 'a' and 'p'. You will also have to identify the type of file system residing in the partition identified. Currently, you can install from partitions that has been formatted as the Berkeley fast file system (ffs) or MS-DOS. You will also have to provide the relative path to the directory on the file system where the distribution sets are located. Note that this path should not be prefixed with a '/'. For instructions on how to complete the installation from the a local disk partition, see the next section. Common file system installations: The following instructions are common to installations from local disk partitions, NFS mounted directories and CD-ROMs. A list of available distribution sets will be listed. You may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, eg `*.tar.gz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to extract file sets. Assuming you acquiesce, the files will begin to extract. If not, you will be given the option of installing sets via one of the other install methods. Common URL installations: Once you have entered the required information, the install program will fetch a file list and present a list of all the distribution sets that were found in the specified directory. (If no valid sets were found, you will be notified and given the option of unpacking any gzipped tar files found or getting a file list if none were found.) At this point you may individually select distribution sets to install or enter `all' to install all of the sets (which is what most users will want to do). You may also enter `list' to get a file list or `done' when you are done selecting distribution sets. You may also use wildcards in place of a file name, eg `*.tar.gz' or even `base*|comp*'. It is also possible to enter an arbitrary filename and have it treated as a file set. Once you have selected the file sets you want to install and entered `done' you will be prompted to verify that you really do want to download and install the files. Assuming you acquiesce, the files will begin to download and unpack. If not, you will be given the option of installing sets via one of the other install methods. When all the selected distribution sets has been extracted, you will be allowed to select which time zone your system will be using, all the device nodes needed by the installed system will be created for you and the file systems will be unmounted. For this to work properly, it is expected that you have installed at least the "base24", "etc24", and "bsd" distribution sets. Congratulations, you have successfully installed OpenBSD 2.4. 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. You should have got a mail from the install program we recommend you to read. 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.4 distribution might need to be tailored for your site. We recommend you run: man afterboot which wilk 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: ------------------------------------------------ NOTE! If you are going to do the upgrade manually, you MUST use the "-r" flag when invoking disklabel(8). You MUST also change the partition table such that partition 'c' encompasses the entire drive, and not only the OpenBSD partition. Finally, partition 'd' is no longer special and can be used for any purpose whatsoever. Also, OpenBSD now uses partition ID 0xA6 (166 decimal), but will continue to work with 0xA5 for compatibility reasons. However, if you change the partition ID to 0xA6, you will be able to share the disk with 386BSD, FreeBSD or NetBSD. Note that the latter three can NOT easily share the disk with each other. To do the upgrade, you must have the floppy24.fs floppy image on a disk. You must also have at least the "base24" and "bsd" binary distribution set available, so that you can upgrade with it, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. If you have a few megabytes free on each of your root and /usr partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your OpenBSD partition, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the OpenBSD partition or on another operating system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: Boot your machine using of the floppy24.fs floppy. When presented with the boot prompt (the "boot>" prompt), hit return. While booting, you will probably see several warnings. You should be warned that no swap space is present, and that init(8) cannot find /etc/rc. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a shell name, just hit return. You will be presented with a welcome message and a prompt. If you are upgrading from a pre-OpenBSD 1.0 release, you should upgrade your file systems manually now, using "fsck -c 2". Read the fsck(8) manual page for more details. Now you will be asked whether you wish to do an "install" or an "upgrade". Enter 'u' to upgrade your existing installation. You will be presented with some information about the upgrade process and a warning message, and will be asked if you wish to proceed with the upgrade process. If you answer negatively, the upgrade process will stop, and your disk will not be modified. If you answer affirmatively, the upgrade process will begin, and your disk will be modified. You may hit Control-C to stop the upgrade process at any time. However, if you hit it at an inopportune moment, your system may be left in an inconsistent (and possibly unusable) state. You will be asked which terminal type to use, you should just hit return to select the default (pcvt25). The upgrade program will then tell you which disks of that type it can upgrade, and ask you which it should use. The name of the disk is typically "wd0" for IDE/RLL/ESDI/ST506 drives or "sd0" for SCSI drives. Reply with the name of your disk. The upgrade program will then ask you for the partition which contains the root file system and proceed with checking it. It will then mount your root file system on /mnt. After all your root file system has been mounted, the upgrade program will ask you if you want to enable the network. If you answer affirmatively, the configuration stored on the root file system will be used. After this you will be given the opportunity to escape to the command shell to do any additional network configuration. This may include adding or altering routes, if needed. At the next point you can edit the fstab, which is used for the upgrade process. You may need to resolve dependencies in the order in which the file systems are mounted. All partitions will be checked and mounted under /mnt. In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, etc. You will be asked if the upgrade sets are already on the mounted file systems. If you answer with yes, you can type in the path where the sets are stored. The upgrade then continues with the procedure described in the paragraph "Common file system installations" in the install section of this document. If you don't already have the OpenBSD distribution sets on your disk, look at the installation section of this document for information on how to go on. Your options are to install via FTP, via HTTP, via nfs, from tape, from CD-ROM or, again, from local disk. But remember to not install the "etc24" distribution file! Your system has now been upgraded to OpenBSD 2.4. After rebooting your machine is a complete OpenBSD 2.4 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly. First, you will probably want to get the etc24 distribution, extract it to a temporary location, and compare its contents with those in your /etc/ directory. You will probably want to replace some of your system configuration files, or incorporate some of the changes in the new versions into yours. Second, you will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this. A "MAKEDEV all" was already run during the upgrade procedure, so you will have to take care about those devices, that are not remade by "MAKEDEV all". Third, you must deal with certain changes in the formats of some of the configuration files. The most notable change is that the "options" given to many of the file systems in /etc/fstab or by hand have changed, and some of the file systems have changed names. *IMPORTANT*: ANY INSTANCES OF "ufs" IN /etc/fstab ARE CHANGED TO "ffs" BY THE UPGRADE PROGRAM. To find out what the new options are, it's suggested that you read the manual page for the file systems' mount commands, for example mount_nfs(8) for NFS. (Note that the information for mounts of type "ffs", i.e. Fast File Systems, are contained in the mount(8) man page.) Finally, you will want to delete old binaries that were part of the version of OpenBSD that you upgraded from and have since been removed from the OpenBSD distribution. If you are upgrading from a pre-1.0 OpenBSD, you might also want to recompile any locally-built binaries, to take advantage of the shared libraries. (Note that any new binaries that you build will be dynamically linked, and therefore take advantage of the shared libraries, by default. For information on how to make statically linked binaries, see the cc(1) and ld(1) manual pages.) 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'', the ``ports'' collection, and some of the ``ports'' source file releases. 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.26.tgz ssh-intl-1.2.26.tgz pgp-usa-2.6.3.tgz pgp-intl-2.6.3.tgz You are STRONGLY urged to install one of the above ssh packages and use ssh instead of telnet, rlogin, or rsh. See below for instructions on installing packages using ftp. 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. 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.4/packages/i386 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.4/packages/i386/ # # 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.4/packages/i386/ 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.4/packages/i386/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.0.6.tgz mpeg_lib-1.2.1.tgz Xaw3d-1.3.tgz netpipes-4.1.1-export.tgz afm-1.0.tgz nmh-0.27.tgz bash-2.02.tgz pgp-intl-2.6.3.tgz bison-1.25.tgz pgp-usa-2.6.3.tgz bzip2-0.9.0b.tgz pine-4.03.tgz dejagnu-1.3.tgz png-1.0.2.tgz emacs-20.3.tgz psutils-a4-1.17.tgz enscript-1.6.1.tgz psutils-letter-1.17.tgz expect-5.26.tgz screen-3.7.4.tgz fetchmail-4.5.4.tgz sharutils-4.2.tgz ghostscript-5.10.tgz ssh-intl-1.2.26.tgz gimp-1.0.0.tgz ssh-usa-1.2.26.tgz glimpse-4.1.tgz tar-1.12.tgz gmake-3.76.1.tgz tcl-8.0.2.tgz gnuplot-3.5.tgz tcsh-6.07.02.tgz gtk+-1.0.5.tgz teTeX-0.4.tgz gv-3.5.8.tgz tiff-3.4.tgz id-utils-3.2.tgz tk-8.0.2.tgz idled-1.16.tgz transfig-3.2.1.tgz iozone-2.01.tgz unzip-5.3.2.tgz ircii-2.8.2-epic3.004.tgz xcolors-1.3.tgz ispell-3.1.20.tgz xfig-3.2.2.tgz jove-4.16.tgz xntp3-5.93-export.tgz jpeg-6b.tgz xpaint-2.5.5.tgz lesstif-0.86.0.tgz xphoon-91.9.18.tgz m4-1.4.tgz xv-3.10a.tgz mm-2.7.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. The source files come from archives which are also, for the most part, on the OpenBSD CD-ROM. 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) mount CD-ROM number 2 on the directory /cdrom. This is necessary to find the application source files. 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 FETCH_SYMLINK_DISTFILES=YES 5) make FETCH_SYMLINK_DISTFILES=YES install 6) make FETCH_SYMLINK_DISTFILES=YES clean The FETCH_SYMLINK_DISTFILES=YES parameter tells make not to copy the application's distribution sources from the cdrom to your hard disk, but instead create a symbolic link pointing to the CD-ROM. This is done to conserve disk space. Installing applications from the OpenBSD ports collection: See http://www.openbsd.org/ports.html for current instructions on obtaining and installing OpenBSD ports. 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.