INSTALLATION NOTES for OpenBSD/armish 4.4 What is OpenBSD? ---------------- OpenBSD is a fully functional, multi-platform UN*X-like Operating System based on Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite. There are several operating systems in this family, but OpenBSD differentiates itself by putting security and correctness first. The OpenBSD team strives to achieve what is called a 'secure by default' status. This means that an OpenBSD user should feel safe that their newly installed machine will not be compromised. This 'secure by default' goal is achieved by taking a proactive stance on security. Since security flaws are essentially mistakes in design or implement- ation, the OpenBSD team puts as much importance on finding and fixing existing design flaws and implementation bugs as it does writing new code. This means that an OpenBSD system will not only be more secure, but it will be more stable. The source code for all critical system components has been checked for remote-access, local-access, denial- of-service, data destruction, and information-gathering problems. In addition to bug fixing, OpenBSD has integrated strong cryptography into the base system. A fully functional IPsec implementation is provided as well as support for common protocols such as SSL and SSH. Network filtering and monitoring tools such as packet filtering, NAT, and bridging are also standard, as well as several routing services, such as BGP and OSPF. For high performance demands, support for hardware cryptography has also been added to the base system. Because security is often seen as a tradeoff with usability, OpenBSD provides as many security options as possible to allow the user to enjoy secure computing without feeling burdened by it. To integrate more smoothly in other environments, OpenBSD 4.4 also provides, on some platforms, several binary emulation subsystems (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris, and Ultrix compatibility), aiming at making the emulation as accurate as possible so that it is transparent to the user. Because OpenBSD is from Canada, the export of Cryptography pieces (such as OpenSSH, IPsec, and Kerberos) to the world is not restricted. (NOTE: OpenBSD can not be re-exported from the US once it has entered the US. Because of this, take care NOT to get the distribution from an FTP server in the US if you are outside of Canada and the US.) A comprehensive list of the improvements brought by the 4.4 release is available on the web at http://www.OpenBSD.org/44.html. OpenBSD/armish runs on the Thecus N2100 and IODATA HDL-G ARM-based network disk appliances. Sources of OpenBSD: ------------------- This is a list of currently known FTP servers at the time of the 4.4 release. For a more recent list, please refer to http://www.OpenBSD.org/ftp.html Main server in Canada: ftp://ftp.OpenBSD.org/pub/OpenBSD (Alberta) 2nd level mirrors: ftp://spargel.kd85.com/pub/OpenBSD (Vienna) ftp://openbsd.informatik.uni-erlangen.de/pub/OpenBSD (Erlangen) ftp://ftp.stacken.kth.se/pub/OpenBSD (Stockholm) ftp://ftp5.usa.openbsd.org/pub/OpenBSD (Redwood City, CA) ftp://ftp3.usa.openbsd.org/pub/OpenBSD (Boulder, CO) ftp://rt.fm/pub/OpenBSD (Lake in the Hills, IL) Argentina: ftp://ftp.openbsd.md5.com.ar/pub/OpenBSD (Buenos Aires) Australia: ftp://ftp.it.net.au/mirrors/OpenBSD (Perth) Austria: ftp://playboy.wu-wien.ac.at/pub/OpenBSD (Vienna) Belgium: ftp://ftp.scarlet.be/pub/openbsd (Brussels) ftp://ftp.belnet.be/packages/openbsd (Brussels) Brazil: ftp://ftp.das.ufsc.br/pub/OpenBSD (Florianopolis, Santa Catarina) Bulgaria: ftp://ftp.bg.openbsd.org/pub/OpenBSD (Plovdiv) Canada: ftp://mirror.arcticnetwork.ca/pub/OpenBSD (Calgary) ftp://ftp.ca.openbsd.org/pub/OpenBSD (Edmonton) ftp://gulus.usherbrooke.ca/pub/distro/OpenBSD (Quebec) China: ftp://ftp.freebsdchina.org/pub/OpenBSD (Shanghai) Denmark: ftp://mirrors.dotsrc.org/openbsd (Aalborg) ftp://ftp.dkuug.dk/pub/OpenBSD (Copenhagen) Estonia: ftp://ftp.aso.ee/pub/OpenBSD (Tallinn) Finland: ftp://mirrors.nic.funet.fi/pub/OpenBSD (Espoo) ftp://ftp.jyu.fi/pub/OpenBSD (Jyvaskyla) France: ftp://ftp.arcane-networks.fr/pub/OpenBSD (Paris) ftp://ftp.crans.org/pub/OpenBSD (Paris) ftp://ftp.irisa.fr/pub/OpenBSD (Rennes) Germany: ftp://openbsd.ftp.fu-berlin.de/pub/OpenBSD (Berlin) ftp://ftp.spline.de/pub/OpenBSD (Berlin) ftp://ftp.freenet.de/pub/ftp.openbsd.org/pub/OpenBSD (Duesseldorf) ftp://ftp-stud.fht-esslingen.de/pub/OpenBSD (Esslingen) ftp://mirror.roothell.org/pub/OpenBSD (Nuremberg) ftp://ftp.bytemine.net/pub/OpenBSD (Oldenburg) Greece: ftp://filoktitis.noc.uoa.gr/pub/OpenBSD (Athens) ftp://ftp.physics.auth.gr/pub/mirrors/OpenBSD/OpenBSD (Thessaloniki) ftp://ftp.duth.gr/pub/OpenBSD (Thrace) ftp://ftp.cc.uoc.gr/mirrors/OpenBSD (Heraklion) Hungary: ftp://ftp.fsn.hu/pub/OpenBSD (Budapest) Ireland: ftp://ftp.esat.net/pub/OpenBSD (Dublin) ftp://ftp.heanet.ie/pub/OpenBSD (Dublin) Israel: ftp://mirror.inter.net.il/pub/OpenBSD (Petach Tiqwa) Italy: ftp://ftp.unina.it/pub/OpenBSD (Napoli) Japan: ftp://ftp.jaist.ac.jp/pub/OpenBSD (Ishikawa) ftp://ftp.nara.wide.ad.jp/pub/OpenBSD (Nara) ftp://ftp.jp.openbsd.org/pub/OpenBSD (Tokyo) ftp://ftp.kddlabs.co.jp/OpenBSD (Tokyo) Korea: ftp://ftp.kaist.ac.kr/pub/OpenBSD (Daejeon) Latvia: ftp://ftp.secure.lv/pub/OpenBSD (Riga) ftp://ftp.bsd.lv/pub/OpenBSD (Riga) The Netherlands: ftp://ftp.calyx.nl/pub/OpenBSD (Amsterdam) ftp://ftp.nluug.nl/pub/OpenBSD (Utrecht) ftp://mirror.hostfuss.com/pub/OpenBSD (Amsterdam) Norway: ftp://ftp.inet.no/pub/OpenBSD (Oslo) ftp://ftp.uninett.no/pub/OpenBSD (Oslo) ftp://jane.tihlde.org/pub/OpenBSD (Trondheim) Poland: ftp://ftp.task.gda.pl/pub/OpenBSD (Gdansk) Portugal: ftp://ftp.fmed.uc.pt/pub/OpenBSD (Coimbra) Russia: ftp://ftp.chg.ru/pub/OpenBSD (Chernogolovka-Moscow) ftp://ftp.gamma.ru/pub/OpenBSD (Moscow) Slovenia: ftp://ftp.obsd.si/pub/OpenBSD (Ljubljana) Spain: ftp://ftp.rediris.es/mirror/OpenBSD (Madrid) ftp://ftp.udc.es/pub/OpenBSD (A Coruna) Sweden: ftp://ftp.su.se/pub/OpenBSD (Stockholm) ftp://ftp.btradianz.se/pub/OpenBSD (Stockholm) Switzerland: ftp://mirror.switch.ch/pub/OpenBSD (Zurich) Turkey: ftp://ftp.enderunix.org/pub/OpenBSD (Istanbul) Ukraine: ftp://gaia.colocall.net/pub/OpenBSD (Kiev) United Kingdom: ftp://ftp.public-internet.co.uk/pub/OpenBSD (London) ftp://ftp.mirrorservice.org/pub/OpenBSD (Kent) USA: ftp://mirror.planetunix.net/pub/OpenBSD (Chicago, IL) ftp://osmirrors.cerias.purdue.edu/pub/OpenBSD (West Lafayette, IN) ftp://mirror.iawnet.sandia.gov/pub/OpenBSD (Albuquerque, NM) ftp://ftp.cse.buffalo.edu/pub/OpenBSD (Buffalo, NY) ftp://mirrors.24-7-solutions.net/pub/OpenBSD (New York, NY) ftp://openbsd.mirrors.pair.com (Pittsburgh, PA) ftp://carroll.cac.psu.edu/pub/OpenBSD (PA) ftp://openbsd.mirrors.tds.net/pub/OpenBSD (Madison, WI) Additionally, the file ftp://ftp.OpenBSD.org/pub/OpenBSD/ftplist contains a list which is continually updated. If you wish to become a distribution site for OpenBSD, contact . OpenBSD 4.4 Release Contents: ----------------------------- The OpenBSD 4.4 release is organized in the following way. In the .../4.4 directory, for each of the architectures having an OpenBSD 4.4 binary distribution, there is a sub-directory. The armish-specific portion of the OpenBSD 4.4 release is found in the "armish" subdirectory of the distribution. That subdirectory is laid out as follows: .../4.4/armish/ INSTALL.armish Installation notes; this file. MD5 Output of the md5(1) program, usable for verification of the correctness of downloaded files. *.tgz armish binary distribution sets; see below. bsd A stock GENERIC armish kernel which will be installed on your system during the install. bsd.rd A compressed RAMDISK kernel; the embedded filesystem contains the installation tools. Used for simple installation from a pre-existing system. The OpenBSD/armish binary distribution sets contain the binaries which comprise the OpenBSD 4.4 release for armish systems. There are eleven binary distribution sets. The binary distribution sets can be found in the "armish" subdirectory of the OpenBSD 4.4 distribution tree, and are as follows: base44 The OpenBSD/armish 4.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. [ 47.7 MB gzipped, 137.4 MB uncompressed ] comp44 The OpenBSD/armish Compiler tools. All of the tools relating to C, C++, Objective-C and Fortran 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. [ 73.1 MB gzipped, 211.1 MB uncompressed ] etc44 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; see the section named Upgrading a previously-installed OpenBSD System" below.) [ 635.0 KB gzipped, 1.9 MB uncompressed ] game44 This set includes the games and their manual pages. [ 2.5 MB gzipped, 5.6 MB uncompressed ] man44 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. [ 7.3 MB gzipped, 26.6 MB uncompressed ] misc44 This set includes the system dictionaries (which are rather large), and the typesettable document set. [ 2.7 MB gzipped, 9.4 MB uncompressed ] xbase44 This set includes the base X distribution. This includes programs, headers and libraries. [ 10.1 MB gzipped, 28.8 MB uncompressed ] xetc44 This set includes the X window system configuration files that reside in /etc. It's the equivalent of etc44 for X. [ 74.0 KB gzipped, 281.3 KB uncompressed ] xfont44 This set includes all of the X fonts. [ 33.9 MB gzipped, 41.7 MB uncompressed ] xserv44 This set includes all of the X servers. [ 7.2 MB gzipped, 20.4 MB uncompressed ] xshare44 This set includes all text files equivalent between all architectures. [ 2.6 MB gzipped, 13.9 MB uncompressed ] OpenBSD System Requirements and Supported Devices: -------------------------------------------------- OpenBSD/armish runs on the Thecus N2100 and IOData HDL-G models at the moment. Supported devices include: Ethernet Adapters ADMtek AN986-based USB adapters, including: Abocom UFE1000 Abocom DSB650TX Accton USB320-EC Accton SpeedStream Ethernet Admtek Pegasus, Pegasus II Billionton Systems USB100 Corega FEther USB-TX D-Link DSB-650, 650TX, 650TX-PNA Elecom LD-USB Elsa Microlink USB2Ethernet I/O Data USB ETTX Kingston KNU101TX Linksys USB100TX, USB100H1 and USB10TA Melco Inc. LUA-TX Siemens SpeedStream USB SmartBridges smartNIC 2 SMC 2202USB/ETH SMC 2206USB/ETH SOHOware NUB100 ASIX Electronics AX88172 USB Ethernet adapters, including: ATEN UC210T BAFO BF-320 Billionton Systems USB2AR Buffalo(MELCO) LUA-U2-KTX Corega FEther USB2-TX D-Link DUB-E100 Good Way GWUSB2E Hawking UF200 Intellinet USB 2.0 to Ethernet (rev A) JVC MP-PRX1 Linksys USB200M Netgear FA120 Sitecom LN-029 SMC 2209USB/ETH SnapPort USB 2.0 LAN Adapter ST Lab USB 2.0 Fast Ethernet Surecom EP-1427X-2 System TALKS SGC-X2UL TRENDnet TU2-ET100 Z-TEK ZK-R01-2 CATC USB-EL1210A-based USB adapters, including: CATC Netmate and Netmate II Belkin F5U011/F5U111 Davicom DM9601 based USB adapters, including: Corega FEther USB-TXC HenTong WK-668 ShanTou ST268 Kawasaki LSI KL5KUSB101B-based USB adapters, including: 3Com 3c19250 3Com 3c460 HomeConnect AboCom Systems URE450 Ethernet ADS Technologies USB-10T Aox USB101 Asante USB to Ethernet ATen DSB-650C ATen UC10T Corega USB-T D-Link DSB-650C Entegra NET-USB-E45 I/O Data USB-ET/T Jaton USB XpressNet Kawasaki USB101 Kingston Ethernet Linksys USB10T Mobility Ethernet Netgear EA101 Peracom USB Portgear Ethernet Portsmith Express Ethernet Psion Dacom Gold Port Ethernet Shark Pocket Adapter Silicom U2E SMC 2102/2104USB RealTek RTL8150L based USB adapters, including: Abocom RTL8151 BAFO BF-310 Billionton USBKR-100 Compex UE202-B GreenHouse GH-USB100B GreenHouse GH-USB100B with HomePNA Hawking Technology HUF11 Linksys USB100M Longshine LCS-8138TX Melco Inc. LUA-KTX Micronet SP128AR NetComm NP1010 Repotec RP-USB100-A SMC 2208USB/ETH TRENDnet TU-ET100C Zt USB10/100 Z-TEK ZK-R02 Wireless Ethernet Adapters Atmel AT76C50x based USB IEEE 802.11b adapters 3Com 3CRSHEW696 AboCom BWU613 Accton 2664W Acer Peripherals AWL300 Acer Peripherals AWL400 Actiontec 802UAT1 Addtron AWU120 Aincomm AWU2000B Askey Computer Voyager 1010 Askey Computer WLL013 (Intersil Radio) Askey Computer WLL013 (RFMD Radio) Belkin F5D6050 Bluetake BW002 Compaq iPAQ h54xx/h55xx Internal WLAN Conceptronic C11U Conceptronic WL210 Corega WLAN USB Stick 11 Dick Smith Electronics CHUSB 611G Dick Smith Electronics WL200U Dick Smith Electronics WL240U Dick Smith Electronics XH1153 D-Link DWL-120 rev E Geowave GW-US11S Gigabyte GN-WLBM101 Gigaset WLAN Hewlett-Packard HN210W Intel AP310 AnyPoint II I/O DATA USB WN-B11 Lexar 2662W-AR Linksys WUSB11 Linksys WUSB11 v2.8 MSI WLAN Netgear MA101 Netgear MA101 rev B Ovislink AirLive WL-1120USB OvisLink AirLive WL-1130USB Planex Communications GW-US11S Samsung SWL2100W Siemens WLL013 SMC 2662W-AR SMC 2662W-V4 Tekram U-300C Z-Com M4Y-750 Intersil PRISM 2.5/3 based USB IEEE 802.11b adapters Acer Warplink USB-400 Actiontec HWU01170 AirVast WM168b Ambit WLAN Apacer Wireless Steno MB112 ASUS WL-140 Compaq W100 Corega WLUSB-11 Corega WLUSB-11 Key D-Link DWL-120 (rev F) D-Link DWL-122 I-O DATA WN-B11/USB Intel PRO/Wireless 2011B Intersil Prism 2X JVC MP-XP7250 Linksys WUSB11 v3.0 Linksys WUSB12 Melco WLI-USB-KB11 Melco WLI-USB-KS11G Melco WLI-USB-S11 Microsoft MN510 Netgear MA111 (version 1) Pheenet WL-503IA Planex GW-US11H Siemens SpeedStream SS1022 Sitecom WL-022 Syntax USB-400 US Robotics 1120 ViewSonic Airsync Z-Com XI-725/726 Z-Com XI-735 ZyXEL ZyAIR B-200 Ralink RT2500 based USB 2.0 IEEE 802.11b/g adapters AMIT WL532U ASUS WL-167g Belkin F5D7050 Buffalo WLI-U2-KG54 Buffalo WLI-U2-KG54-AI Buffalo WLI-U2-KG54-YB CNet CWD-854 Compex WLU54G Conceptronic C54RU D-Link DWL-G122 (b1) Dynalink WLG25USB E-Tech WGUS02 Eminent 3035 Gigabyte GN-WBKG Hercules HWGUSB2-54 KCORP LifeStyle KLS-685 Linksys WUSB54G v4 Linksys WUSB54GP v4 MSI MS-6861 MSI MS-6865 MSI MS-6869 SerComm UB801R SparkLAN WL-685R Sphairon UB801R Surecom EP-9001-g rev 3A Tonze UW-6200C Zaapa ZNWUSB-54 Zinwell ZWX-G261 Zonet ZEW2500P Ralink RT2501USB/RT2601USB USB 2.0 IEEE 802.11/a/b/g adapters 3Com Aolynk WUB320g Abocom WUG2700 Airlink101 AWLL5025 Belkin F5D7050 ver 3 Belkin F5D9050 ver 3 Buffalo WLI-U2-SG54HP Buffalo WLI-U2-G54HP CNet CWD-854 ver F Conceptronic C54RU ver 2 Corega CG-WLUSB2GO D-Link DWL-G122 rev C1 D-Link WUA-1340 Digitus DN-7003GR Edimax EW-7318USG Gigabyte GN-WB01GS Hawking HWUG1 Hawking HWU54DM Hercules HWGUSB2-54-LB Hercules HWGUSB2-54V2-AP LevelOne WNC-0301USB v3 Linksys WUSB54G rev C Linksys WUSB54GR Planex GW-US54HP Planex GW-US54Mini2 Planex GW-USMM Senao NUB-3701 Sitecom WL-113 ver 2 Sitecom WL-172 Sweex LW053 TP-LINK TL-WN321G Serial ports On-board serial (com) ports Universal Serial Bus (USB) Devices USB Audio USB Diamond Multimedia Rio MP3 players USB Ethernet adapters, see above USB Generic Human Interface Devices (catch-all) USB Handspring Visor USB Hubs USB Keyboards USB Mass Storage devices, i.e., USB floppy drives and USB memory stick controllers USB Mice USB Modems USB Printers USB Scanners USB-USB cables USB Y@p phone Keyboards USB keyboards Pointing Devices USB mice Getting the OpenBSD System onto Useful Media: --------------------------------------------- Installation is supported from several media types, including: CD-ROM FFS partitions (for upgrades only) DOS (FAT) partitions EXT2 partitions FTP HTTP The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. Some methods require a bit of setup first that is explained below. The installation allows installing OpenBSD directly from FTP mirror sites over the internet, however you must consider the speed and reliability of your internet connection for this option. It may save much time and frustration to use ftp get/reget to transfer the distribution sets to a local server or disk and perform the installation from there, rather than directly from the internet. 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, 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 "base44" set somewhere in your file system. It is recommended that you upgrade the other sets, as well. Preparing your System for OpenBSD Installation: ----------------------------------------------- To be able to boot the OpenBSD/armish installation program, you will need to learn a bit about RedBoot, the low-level process that controls the microprocessor after hardware initialization. The enabled features between IOData HDL-G and Thecus N2100 vary, so different methods will be needed on both machines. All these machines use RedBoot as their firmware and boot loader interface, with varying limitations. Thecus systems cannot load a file from disk, but can load an image from flash or network. IOData systems are more restricted, and can only load an image from ext2fs partitions on disk, while the commands to load from flash are not available and network booting does not appear to work. Talking to the Thecus The Thecus N2100 needs a serial cable. On the back of the disk drive circuit board, there is either a 10-pin header (with one pin removed), or 9 holes for you to solder in your own header. The ribbon cable that connects from there to your serial cable or the serial port on your computer is of the same type as used on older i386 PCs, but be aware that there are two different types of 10-pin IDC to DB-9M ribbon cable in use, which look identical (the differences are hidden inside the DB-9 connector). The cable you need is wired using the "AT-Everex" or "Asus" pinout, as described here: http://www.pccables.com/07120.htm and *not* the more straightforward to solder "crossed" type: http://www.pccables.com/07121.htm. If you wish to check a cable, or make your own, the pinouts are: DB9 IDC10 === ===== 1 2 3 4 5 1 3 5 7 9 6 7 8 9 2 4 6 8 10 Wire pin 1 to 1, 2 to 2 etc, with 10 not connected. On the Thecus N2100, it is necessary to move jumper J3 to J4 to properly route the serial port interrupt to allow serial to work under OpenBSD. This jumper is under the disk drives, so you may wish to ensure its correct setting while you are installing the disk(s). For instructions on assembling/disassembling your N2100, see the N2100 Manual at http://www.thecus.com/download/manual/N2100%20UM%20EN.pdf Booting Thecus N2100 When you have connected your computer, a command like "tip -115200 tty00" (assuming you're using the first serial port on your machine) should connect you to the Thecus console. Now apply power to the Thecus and start it. After some device probe information, you should see this prompt: == Executing boot script in 3.000 seconds - enter ^C to abort To enter interactive RedBoot, it is necessary to press ^C within the given number of seconds of the prompt. It will typically accept the ^C if typed during the diagnostics that precede this prompt. The recommended way to boot OpenBSD on Thecus is to configure networking and load bsd.rd from a tftp server or http server. First networking must be configured using the fconfig or ip_address commands. Update the IP address, netmask and server address with the commands listed below to allow booting from the network. TFTP and HTTP are supported. (BOOTP configuration _may_ not work) Using ip_address only allows you to set the local IP address and the IP address of the server where bsd.rd is located. This command takes effect immediately but will not persist across a reboot. RedBoot> ip_address -l 10.0.0.21 -h 10.0.0.7 IP: 10.0.0.21/255.255.255.0, Gateway: 0.0.0.0 Default server: 10.0.0.7, DNS server IP: 0.0.0.0 Once you have done this, and have set up your TFTP server on the gateway machine (10.0.0.7 in the above example), you can boot manually. RedBoot> load /bsd.rd Using default protocol (TFTP) Entry point: 0x00200000, address range: 0x00200000-0x0066a49c RedBoot> go OpenBSD/armish booting ... initarm: Configuring system ... physmemory: 65536 pages at 0xa0000000 -> 0xafffffff [ no symbol table formats found ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2008 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 4.3 (RAMDISK) #175: Tue Mar 4 21:54:34 MST 2008 deraadt@armish.openbsd.org:/usr/src/sys/arch/armish/compile/RAMDISK real mem = 268435456 (256MB) avail mem = 250630144 (239MB) ... Install(I), Upgrade(U) or Shell(S)? If you then install to your hard disk, in future you can load /boot the same way and just hit "return" to boot OpenBSD. Automatic Booting However, for easier booting, you may wish to modify the flash memory so that the Thecus will boot automatically into OpenBSD when it is powered up. Doing so disables the devices' built-in Linux kernel, however, and makes it difficult or impossible to apply future RedBoot firmware upgrades. There are two general approaches: 1) Just change the boot configuration (using 'fconfig') to automate the above booting (your TFTP or HTTP boot server will still be needed); 2) Remove a file from the flash and replace it with OpenBSD's /boot; this configuration can be booted standalone. Thecus RedBoot provides the 'fconfig' (not ifconfig) command to change the boot configuration of the device. Also 'fis' is provided to perform flash operations. Due to a change made by Thecus to the firmware, fconfig does not work with Thecus firmware version "1.93 (Feb 2007)" or later, and *it is thus not possible to make the Thecus auto-boot into OpenBSD* (worse, it will let you enter the "script" commands below, but ignore them on boot). To correct this, you must "upgrade" your thecus down to version "1.93 Nov 29 2005" using the file n2100-downgrade-reboot.rom *before* you remove any files from flash. You can get this file from Thecus; they have given permission for it to be mirrored at http://www.darwinsys.com/openbsd/. However, if you have removed files from flash before running this downgrade, it is not believed to be possible to get your machine to auto-boot. Once the downgrade is done, if your TFTP machine will always be around, you can autoboot just by changing the boot script with fconfig, as follows: (in this example, 192.168.1.254 is both the default IP gateway and also the TFTP server): RedBoot> fconfig Run script at boot: true Boot script: .. load /boot.armish .. go Enter script, terminate with empty line >> load /boot.armish >> go >> Boot script timeout (1000ms resolution): 3 Use BOOTP for network configuration: false Gateway IP address: 192.168.1.254 Local IP address: 192.168.1.253 Local IP address mask: 255.255.255.0 Default server IP address: 192.168.1.254 Console baud rate: 115200 DNS server IP address: GDB connection port: 9000 HW Status: 0 Force console for special debug messages: false MAC address: 0x00:0x14:0xFD:0x30:0x25:0x14 MAC address 2: 0x00:0x14:0xFD:0x30:0x25:0x15 Network debug at boot time: false Reset default: Normal Serial number: N2100 V2.1.06 ... Unlock from 0xf0fc0000-0xf0fc1000: . ... Erase from 0xf0fc0000-0xf0fc1000: . ... Program from 0x07fd2000-0x07fd3000 at 0xf0fc0000: . ... Lock from 0xf0fc0000-0xf0fc1000: . RedBoot> This configuration can easily be set back to the default, as the Linux system does not get erased from the flash memory. To set it back, just change the boot script with fconfig back to what it was, for example: thecus_setip fis load ramdisk fis load kernel exec -c "console=ttyS0,115200 root=/dev/ram0 initrd=0xa0800000,42M mem=128M@0xa0000000" You could also remove the boot script altogether by not re-entering it, so you would be dropped to the RedBoot shell by default. Recheck the new values and use the 'reset' command. For the standalone booting option, you will have to load /boot into the flash memory... To overwrite the Thecus ROM and boot from the load device, it is necessary to delete a 'rom file' and load the openbsd bootloader image there. With networking configured (as above) remove a region and load the 'boot' program. Initially the machine will contain much like the following: RedBoot> fis list Name FLASH addr Mem addr Length Entry point RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 user 0xF0EA0000 0xF0EA0000 0x00120000 0x00200000 There is no free space in the rom for the 'boot' program, so something must be removed. WARNING: this will make the machine unbootable into the original Thecus server mode and it is quite difficult to restore to the original software. EXTREME WARNING: Do not touch the RedBoot, RedBoot config, or FIS directory regions, as doing so will probably brick the device. Remove (with confirmation) a region to make space, eg 'user' (the non-root files needed to run Linux from Flash Memory). RedBoot> fis delete user Delete image 'user' - continue (y/n)? y ... Erase from 0xf0ea0000-0xf0fc0000: ......... ... Unlock from 0xf0fe0000-0xf1000000: . ... Erase from 0xf0fe0000-0xf1000000: . ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . ... Lock from 0xf0fe0000-0xf1000000: . Load the Armish OpenBSD bootloader 'boot' via tftp or http: RedBoot> load -m http /boot Entry point: 0x00100000, address range: 0x00100000-0x001067e0 Save that loaded file to flash: RedBoot> fis create boot ... Erase from 0xf0ea0000-0xf0ec0000: . ... Program from 0x00100000-0x001067e0 at 0xf0ea0000: . ... Unlock from 0xf0fe0000-0xf1000000: . ... Erase from 0xf0fe0000-0xf1000000: . ... Program from 0x07fdf000-0x07fff000 at 0xf0fe0000: . ... Lock from 0xf0fe0000-0xf1000000: . Confirm its addition: RedBoot> fis list Name FLASH addr Mem addr Length Entry point RedBoot 0xF0000000 0xF0000000 0x00040000 0x00000000 RedBoot config 0xF0FC0000 0xF0FC0000 0x00001000 0x00000000 FIS directory 0xF0FE0000 0xF0FE0000 0x00020000 0x00000000 ramdisk 0xF0040000 0x00800000 0x00D00000 0x00800000 kernel 0xF0D40000 0x00200000 0x00160000 0x00200000 boot 0xF0EA0000 0x00100000 0x00020000 0x00100000 Now that the bootloader is in place, update fconfig to autoboot OpenBSD: RedBoot> fconfig Run script at boot: true Boot script: .. fis load ramdisk .. fis load kernel .. exec ... Enter script, terminate with empty line >> fis load boot >> go >> Boot script timeout (1000ms resolution): 1 ... Update RedBoot non-volatile configuration - continue (y/n)? y ... Unlock from 0xf0fc0000-0xf0fc1000: . ... Erase from 0xf0fc0000-0xf0fc1000: . ... Program from 0x0ffd2000-0x0ffd3000 at 0xf0fc0000: . ... Lock from 0xf0fc0000-0xf0fc1000: . The important part is that 'Run script' is true and that the commands are 'fis load boot' and 'go' ('boot' is the file created by 'fis create boot' earlier). Confirm the update and type 'reset' to auto boot. The bootloader is command driven with timeout like many other OpenBSD architectures. How to boot/install IOData HDL-G: The hda1 partition is the boot partition for Linux; it contains zImage and initrd. Since RedBoot only can boot from the ext2fs partition it is very important that this partition be present and not be reformatted. If this partition is destroyed, it will be necessary to remove the HD and recreate the partition on another machine. Note: RedBoot should be able to boot from the network, however that has been unsuccessful on IODATA HDL-G so far. To install OpenBSD, boot linux, and copy 'boot' and 'bsd.rd' into the partition mounted on /dev/hda1, after that has been done, it is possible to reboot into OpenBSD and install the device. Installation can proceed as on other machines, however care must be take to not remove wd0i/hda1 partition (fdisk partition 0). DO NOT chose the 'full disk installation' option. Unfortunately, since IODATA did not provide the 'fconfig' command it is not possible to change the boot commands run when RedBoot starts, thus it not possible to autoboot OpenBSD; the OpenBSD/armish bootloader is currently unable to work when loaded as `zImage'. Futhermore, to disable autobooting into Linux, at least one of the zImage and initrd files need to be renamed or removed. This can be done from the shell in bsd.rd. To load the ramdisk kernel to install use the commands RedBoot> load -m disk hda1:/bsd.rd RedBoot> go to boot normally, load the bootloader which will give options to boot other kernels. RedBoot> load -m disk hda1:/boot RedBoot> go Since this bootloader is able to boot any kernel from the OpenBSD root partition, it is not necessary to keep bsd.rd on the hda1 partition after OpenBSD is installed. 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. 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. Using Control-Z to suspend the process may be a better option, or at any prompt enter '!' to get a shell, from which 'exit' will return you back to that prompt (no refresh of the prompt though). Once the kernel has loaded, you will be presented with the OpenBSD kernel boot messages. You will want to read them to determine your disks name and geometry. Its name will be something like "wd0". 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. You will next be asked for your terminal type. If you are installing from a non-serial console, the default of "vt220" is correct. If you are installing from a serial console you should choose the terminal type from amongst those listed. (If your terminal type is xterm, just use vt220.) After entering the terminal type you will be asked whether you wish to do an "(I)nstall" or an "(U)pgrade". 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, the install program will then tell you which disks of that type it can install on, and ask you which it should use. 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 Linux partitions defined on the disk, these will usually show up as partition 'i', 'j' 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". 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". 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 (e.g. "wd0") with the letter identifying the partition (e.g. "d") appended (e.g. "wd0d"). Then it will ask where this partition is to be mounted, e.g. /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 prompt you for the system hostname, and 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 HTTP or FTP, and will also be the configuration used by the system after the installation is complete. Note that the system hostname should be without the domain part. If you select to configure the network, the install program will ask you for the 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. If you select to configure the network, the install program 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. If the IP address should be obtained from a DHCP server, simply enter ``dhcp'' when asked for the IP address. The interface-specific flags are usually used to determine which media the network card is to use. Typically no media flags are required as autodetection normally works, but you will be prompted with a list of the acceptable media flags, and asked if you want to provide any. In doubt, do not enter any media flags; or you can refer to the manual page for your interface for the appropriate flags. After all network interfaces have been configured, the install pro- gram will ask for the DNS domain name to use, as well as the IP address of the primary name server to use. Finally, you will be asked for the IP address of the default route. You will also be presented with an opportunity to edit the host table. At this point you will be asked for the initial root password of the system, twice. Although the install program will only check that the two passwords match, you should make sure to use a strong password. As a minimum, the password should be at least six characters long and a mixture of both lower and uppercase letters, numbers and punctuation characters. After these preparatory steps have 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, or a local disk partition. 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 4.4 distribution. If you don't know, answer ``y'' 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/4.4/armish 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). 2) The IP address (or hostname if you enabled DNS earlier in the install) of an HTTP server carrying the OpenBSD 4.4 distribution. If you don't know, answer ``y'' when asked if you want to see a list of such hosts. 3) 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 CD-ROM: When installing from a CD-ROM, you will be asked which device holds the distribution sets. This will typically be "cd0". 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-ROM distribution uses the CD9660 format. You will also have to provide the relative path to the directory on the CD-ROM which holds the distribution, for the armish this is "4.4/armish". 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 have been formatted as the Berkeley fast file system (ffs), Linux (ext2) 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 a local disk partition, see the next section. Common file system installations: The following instructions are common to installations from mounted disk partitions 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, e.g. `*.tgz' 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, e.g. `*.tgz' 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 have been extracted, you will be asked whether you want to start shhd(8) by default, as well as your ntp server (ntpd(8) will not be started by default if you don't provide a server). The last thing you'll need to configure is the time zone your system will be using. For this work properly, it is expected that you have installed at least the "base44", "etc44", and "bsd" distribution sets. The installer program will the proceed to create all the device nodes needed by the installed system, and will unmount the file systems. Congratulations, you have successfully installed OpenBSD 4.4. 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. The install program leaves root an initial mail message. We recommend you read it, as it contains answers to basic questions you might have about OpenBSD, such as configuring your system, installing packages, getting more information about OpenBSD, sending in your dmesg output and more. To do this, run mail and then just enter "more 1" to get the first message. You quit mail by entering "q". Some of the files in the OpenBSD 4.4 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: ------------------------------------------------ Warning! Upgrades to OpenBSD 4.4 are currently only supported from the immediately previous release. The upgrade process will also work with older releases, but might not execute some migration tasks that would be necessary for a proper upgrade. The best solution, whenever possible, is to backup your data and reinstall from scratch. To upgrade OpenBSD 4.4 from a previous version, start with the general instructions in the section "Installing OpenBSD". Boot from your usual boot device. When prompted, select the (U)pgrade option rather than the (I)nstall option at the prompt in the install process. The upgrade script will ask you for the existing root partition, and will use the existing filesystems defined in /etc/fstab to install the new system in. It will also use your existing network parameters. From then, the upgrade procedure is very close to the installation procedure described earlier in this document. Note that the upgrade procedure will not let you pick neither the ``etc44.tgz'' nor the ``xetc44.tgz'' sets, so as to preserve your files in `/etc' which you are likely to have customized since a previous installation. However, it is strongly advised that you unpack the etc44.tgz and xetc44.tgz sets in a temporary directory and merge changes by hand, or with the help of the sysmerge(8) helper script, since all components of your system may not function correctly until your files in `/etc' are updated. 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-ROM, the source code is provided. Otherwise, you can get the pieces over the Internet using anonymous CVS, CTM, CVSync or FTP. For more information, see http://www.OpenBSD.org/anoncvs.html http://www.OpenBSD.org/ctm.html http://www.OpenBSD.org/cvsync.html http://www.OpenBSD.org/ftp.html Using online OpenBSD documentation: ----------------------------------- Documentation is available if you first install the manual pages 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), passwd(5) and afterboot(8). 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 set you already have several popular ``packages'', and the ``ports'' collection. Instructions for installing applications from the various sources using the different installation methods follow. 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 4.4/packages/arm 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 appropriate 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/4.4/packages/arm/ # # umount /cdrom Package names are usually the application name and version with .tgz appended, e.g. emacs-21.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/4.4/packages/arm/ 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/4.4/packages/arm/emacs-21.3.tgz 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 PORTS located on the CD-ROM which contains the ports tree. 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 if anyone is working on a port -- there may be one in progress. If no such port exists, you might want to look at the FreeBSD ports or NetBSD pkgsrc for inspiration. 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, . 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. More information about the various OpenBSD mailing list and proper netiquette is available at http://www.OpenBSD.org/mail.html 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. For more information about reporting bugs, see http://www.OpenBSD.org/report.html