INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/hp300. CONTENTS About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 3.1 release and 3.1.1 update........3 Supported devices...........................................3 Kernel......................................................3 Networking..................................................3 File system.................................................3 Security....................................................3 Miscellaneous...............................................4 alpha specific..............................................4 mac68k specific.............................................4 sparc specific..............................................4 xen specific................................................4 The Future of NetBSD...........................................4 Sources of NetBSD..............................................5 NetBSD 3.1.1 Release Contents..................................5 NetBSD/hp300 subdirectory structure.........................6 Binary distribution sets....................................7 NetBSD/hp300 System Requirements and Supported Devices.........8 Supported hardware..........................................8 Unsupported hardware.......................................11 Getting the NetBSD System on to Useful Media..................11 Preparing your System for NetBSD installation.................13 Formatting your hard drives................................13 Designing your disk's partition table......................14 Installing the bootstrap program locally...................15 Installing the miniroot file system locally................15 Configuring the netboot server.............................16 Put Series 400 systems in HP-UX Compatible Boot Mode.......20 Searching for a bootable system............................21 Selecting ethernet port on Series 400......................22 Running SYS_INST...........................................22 Chosing a kernel location..................................23 Installing the NetBSD System..................................23 Post installation steps.......................................25 Upgrading a previously-installed NetBSD System................27 Upgrading using the miniroot...............................27 Manual upgrade.............................................28 Compatibility Issues With Previous NetBSD Releases............29 Issues affecting an upgrade from NetBSD 3.1 and older......29 Using online NetBSD documentation.............................30 Administrivia.................................................31 Thanks go to..................................................31 We are........................................................36 Legal Mumbo-Jumbo.............................................42 The End.......................................................48 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 3.1.1 on the hp300 platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt: .ps PostScript. .html Standard Internet HTML. .more The enhanced text format used on UNIX -like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line man pages are generally pre- sented. .txt Plain old ASCII. You are reading the ASCII version. What is NetBSD? The NetBSD Operating System is a fully functional Open Source UNIX -like operating system derived from the University of California, Berkeley Net- working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring sev- enteen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD 3.1.1 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distri- bution. For information on them, please see the NetBSD web site at .: http://www.NetBSD.org/) NetBSD is a completely integrated system. In addition to its highly por- table, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist. Changes Between The NetBSD 3.1 release and 3.1.1 update The NetBSD 3.1.1 update is the first security/critical update of the NetBSD 3.1 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. These fixes will also appear in future releases (NetBSD 3.2 etc), together with other less-critical fixes and feature enhancements. Specific updates are as follows: Supported devices o wd(4): fix broken Seagate drive ST3160811A. Kernel o Don't accept a compressed vnd(4) image with block size 0 to avoid a kernel panic. Networking o Fix get-lease-hostnames option in dhcpd.conf(5) to make dhcpd(8) use the DNS hostname as the DHCP hostname given to the client. o Fix TCP window scaling in ipfilter(4). File system o Prevent a kernel panic when creating snapshots on filesystems which use quota's. o Fix a coredump in dump(8) when using -X (filesystem internal snap- shots). o Fix a panic when one user has 65536 active vnodes on a quota-enabled file system. Security o Fix a buffer overflow in glob(3), which affected ftpd(8) and possibly other programs (SA2006-027). o X11: fix an integer overflow in the Render and DBE extensions (SA2007-002). o BIND: fix multiple Denial of Service vulnerabilities (SA2007-003). o Fix a buffer overflow in iso(4) which could potentially lead to a local root compromise (SA2007-004). o Fix an integer underflow in file(1) which could lead to an exploitable heap overflow. o X11: fix a number of possible memory corruptions due to integer over- flows (CVE 2007-1003, 1351, 1352, 1667). o Fix a denial of service vulnerability in racoon(8) which could allow an attacker to disrupt a connection between IPSec peers. o Disable processing or routing header type 0 (RH0) IPv6 packets since they can be used for DoS attacks (CVE-2007-2242). Provide a sysctl (net.inet6.ip6.rht0) to re-enable them. Note: the sysctl may be removed completely in future NetBSD releases. o Two veriexec(4) flaws have been fixed: users can no longer rename a file to a veriexec protected file or run unfingerprinted files at strict level two or above. o file(1) has been updated to version 4.21, including and integer underflow and an integer overflow fix (CVE-2007-1536 and CVE-2007-2799). Miscellaneous o Fix some problems with etcupdate(8) for upgrading. o Update time zoneinfo to tzdata2007f. o Set /etc/postfix/post-install mode 555 (executable) instead of 444. o passwd(1): display a message indicating who's password is being changed, to avoid confusion after su(1). o The /etc/daily, weekly, monthly and security scripts now use $TMPDIR instead of /tmp. alpha specific o Fix alignment problems causing regular panics on NetBSD/alpha and NetBSD/sparc. mac68k specific o Avoid a kernel panic before reboot. sparc specific o Fix alignment problems causing regular panics on NetBSD/alpha and NetBSD/sparc. xen specific o Prevent xennet from occasionally becoming unable to receive packets for several minutes when under certain types of load. o Don't try to handle xbd interrupts if the device is not yet con- nected, to fix a Xen3 xbd panic at boot when more than one xbd device is configured. o Fix Xen console hangs. o Fix occasional panics in NetBSD domU's caused by a race condition. o Avoid block I/O stalls in Xen 3 guests on SMP systems. This is the tenth major release of NetBSD for the HP 9000/300 and 9000/400 series of computers. The Future of NetBSD The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of com- puter software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. The NetBSD Foundation will help improve the quality of NetBSD by: o providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. o providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. o providing a better position from which to undertake promotional activities. o periodically organizing workshops for developers and other interested people to discuss ongoing work. We intend to begin narrowing the time delay between releases. Our ambi- tion is to provide a full release every six to eight months. We hope to support even more hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. We intend to integrate free, positive changes from whatever sources sub- mit them, providing that they are well thought-out and increase the usability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD Refer to .: http://www.NetBSD.org/mirrors/ NetBSD 3.1.1 Release Contents The root directory of the NetBSD 3.1.1 release is organized as follows: .../NetBSD-3.1.1/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 3.1.1 distribution. README.files README describing the distribution's contents. TODO NetBSD 's todo list (also somewhat incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 3.1.1 has a binary distribution. The source distribution sets can be found in subdirectories of the source subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: gnusrc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. 79 MB gzipped, 367 MB uncompressed pkgsrc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. 24 MB gzipped, 200 MB uncompressed sharesrc This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more. 5 MB gzipped, 20 MB uncompressed src This set contains all of the base NetBSD 3.1.1 sources which are not in gnusrc, sharesrc, or syssrc. 37 MB gzipped, 176 MB uncompressed syssrc This set contains the sources to the NetBSD 3.1.1 kernel for all architectures; config(8); and dbsym(8). 26 MB gzipped, 140 MB uncompressed xsrc This set contains the sources to the X Window System. 84 MB gzipped, 450 MB uncompressed All the above source sets are located in the source/sets subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the pkgsrc set, which is traditionally unpacked into /usr/pkgsrc, all sets may be unpacked into /usr/src with the command: # ( cd / ; tar -zxpf - ) set_name.tgz In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: BSDSUM Historic BSD checksums for the various files in that directory, in the format produced by the command: cksum -o 1 file. CKSUM POSIX checksums for the various files in that directory, in the format produced by the command: cksum file. MD5 MD5 digests for the various files in that directory, in the format produced by the command: cksum -m file. SYSVSUM Historic ATT System V UNIX checksums for the various files in that directory, in the format produced by the command: cksum -o 2 file. The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest pos- sible range of system can check the integrity of the release files. NetBSD/hp300 subdirectory structure The hp300-specific portion of the NetBSD 3.1.1 release is found in the hp300 subdirectory of the distribution: .../NetBSD-3.1.1/hp300/. It con- tains the following files and directories: INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display. binary/ kernel/ netbsd-GENERIC.gz A gzipped NetBSD kernel containing code for everything supported in this release. netbsd-RAMDISK.gz A gzipped NetBSD kernel containing code for all of the hardware supported in this release with an embedded ramdisk- based installer. This is the same ker- nel that is present on the miniroot filesystem, but uses a newer more user- friendly installation program. netbsd-RAMDISK.symbols.gz Symbols for netbsd-RAMDISK.gz. sets/ hp300 binary distribution sets; see below. installation/ miniroot/ hp300 miniroot file system image; see below. misc/ HP-IB.geometry A file containing geometry for some HB-IB disk drives. SYS_INST.gz A gzipped copy of the SYS_INST miniroot installation program. This is only necessary if you can't use the RAMDISK based installer. SYS_UBOOT.gz A gzipped copy of the universal boot block. Supports Network, tape and disk booting. This is useful if you are installing a diskless NetBSD/hp300 system. Binary distribution sets The NetBSD hp300 binary distribution sets contain the binaries which com- prise the NetBSD 3.1.1 release for the hp300. The binary distribution sets can be found in the hp300/binary/sets subdirectory of the NetBSD 3.1.1 distribution tree, and are as follows: base The NetBSD 3.1.1 hp300 base binary distribution. You must install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be mini- mally functional. It includes shared library support, and excludes everything described below. 16 MB gzipped, 46 MB uncompressed comp Things needed for compiling programs. This set includes the system include files (/usr/include) 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. 18 MB gzipped, 69 MB uncompressed etc 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. 1 MB gzipped, 1 MB uncompressed games This set includes the games and their manual pages. 3 MB gzipped, 7 MB uncompressed kern-GENERIC This set contains a NetBSD/hp300 3.1.1 GENERIC kernel, named /netbsd. You must install this distribution set. 2 MB gzipped, 3 MB uncompressed man 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. 8 MB gzipped, 30 MB uncompressed misc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share. 3 MB gzipped, 9 MB uncompressed text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. 2 MB gzipped, 7 MB uncompressed NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. Binary sets for the X Window System are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. 6 MB gzipped, 17 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 10 MB gzipped, 37 MB uncompressed xfont Fonts needed by X. 31 MB gzipped, 39 MB uncompressed xetc Configuration files for X which could be locally modified. 0.03 MB gzipped, 0.17 MB uncompressed xserver The X server. 3 MB gzipped, 7 MB uncompressed The hp300 binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xpf command from the root directory ( / ) of your system. This utility is used only in a Traditional method installation. Note: Each directory in the hp300 binary distribution also has its own checksum files, just as the source distribution does. NetBSD/hp300 System Requirements and Supported Devices NetBSD/hp300 3.1.1 will run on most HP 9000/300- and 400-series machines. The smallest amount of RAM that has been tested is 4 MB. If you wish to run X, more RAM is recommended. Supported hardware o CPUs - 318 (16 MHz 68020, with built-in monochrome framebuffer, no expansion) - 319 (16 MHz 68020, with built-in 6 bit color framebuffer, no expansion) - 320 (16 MHz 68020, 16 KB L2 cache, up to 7.5 MB RAM) Requires Human Interface board - 330 (16 MHz 68020, 4 MB on motherboard, up to 8 MB RAM) Requires Human Interface board - 340 (16 MHz 68030, up to 16 MB RAM) - 345 (50 MHz 68030 with 32 KB L2 cache, up to 128 MB RAM, built-in SCSI) - 350 (25 MHz 68020, 32 KB L2 cache, up to 48 MB RAM) Requires Human Interface board - 360 (25 MHz 68030, with 4 MB RAM built-in, up to 48 MB RAM) Requires System Interface board - 362 (25 MHz 68030, up to 16 MB RAM, built-in SCSI) Framebuffer is unsupported, you must use a serial console - 370 (33 MHz 68030, 64 KB L2 cache, up to 48 MB RAM) Requires System Interface board - 375 (50 MHz 68030 with 32 KB L2 cache, up to 128 MB RAM, built-in SCSI) - 380 (25 MHz 68040, up to 128 MB RAM, built-in SCSI) - 382 (25 MHz 68040, up to 32 MB RAM, built-in SCSI) Framebuffer is unsupported, you must use a serial console - 385 (33 MHz 68040, up to 128 MB RAM, built-in SCSI) - 400s, 400t, 400dl (50 MHz 68030 with 32 KB L2 cache, built- in SCSI, up to 128 MB RAM) - 425s, 425t, 425dl (25 MHz 68040 with built-in SCSI, up to 128 MB RAM) - 425e (25 MHz 68040, built-in SCSI) The BootROM does not support serial console and NetBSD/hp300 does not support the 425e framebuffer. When the NetBSD kernel begins to boot it will default to using the serial port for console - 433s, 433t, 433dl (33 MHz 68040 with built-in SCSI, up to 128 MB RAM) o HP-IB devices - rd; CS80 disks: 2200, 2203, 7912, 7914, 7933, 7936, 7937, 7945, 7946, 7957, 7958, and 7959 - rd; CS80 floppy disks: 9122, 9134 (possibly others) Requires use of HP-UX LIF utilities via HP-UX emulation - ct; CS80 Low-density 16 track cartridge (67 MB): 7912, 7914, 7946, and 9144 Cannot read or write to 32 track tapes - ct; CS80 High-density 32 track cartridge (134 MB): 9145 Cannot write to 16 track tapes (read only) - mt; CS80 Half-inch tape: 7974A, 7978A/B, 7979A, 7980A, and 7980XC. Note: You should connect HP-IB tape drives and printers to the slow HP-IB interface and hard drives to the fast HP-IB interface (if present). o SCSI devices - sd; SCSI hard drives Some SCSI II drives may have problems (not very common) - sd; SCSI CD-ROM drives Support for data only (no audio CDs) - sd; SCSI Magneto-optical drives - st; SCSI tape drives: HP 35450A (DDS-1 DAT), Exabyte EXB-8200 (8mm), Archive (QIC-24), Archive Viper (QIC-60), Archive Viper (QIC-150), Archive Python 25501 (DAT), and Archive Python 28849 (DAT) - ac; SCSI autochangers o Serial interfaces - com; Built-in single serial port on System Interface board and Human Interface board - com; Built-in Apollo 4-port on Series 400 workstations - dcm; 98638 8-port (DIO-II board, appears to kernel as two 98642 devices) - dcm; 98642 4-port (DIO-I board) - com; 98626, 98644 built-in or add-on (DIO-I board) single serial port Note: See the FAQ for more detailed specs and information on configuring: http://www.NetBSD.org/Ports/hp300/faq.html#serialinfo o Network interfaces - le; 98643 built-in and add-on (DIO-I board) ethernet cards. o Graphics Devices - 98544 monochrome Topcat (1024x768, 1 bit, DIO-II) - 98545A color Topcat (1024x768, 4 bits, DIO-II) - 98547 color Topcat (1024x768, 6 bits) - 98548A monochrome Catseye (1024x768, 1 bit) - 98549A color Catseye (1024x768, 6 bits) - 98550A Catseye Hi-Res Color (a.k.a. CH) (1280x1024 @ 60 Hz, 8 bits, DIO-II) - 98700 and 98710 Gatorbox (1280x1024 @ 60 Hz, 4 or 8 bits) Requires 98287 (DIO-I board) to connect to workstation - 98720 and 98721 color Renaissance SRX (1280x1024 @ 60 Hz, 8, 12 or 24 bits) Requires 98724 (DIO-I board) or 98725 (DIO-II board) to connect to workstation - 98730 and 98731 DaVinci TurboSRX (1280x1024 @ 60 Hz, 8, 16, or 24 bits) Requires 98726A (DIO-II board) to connect to workstation - A1096A monochrome Hyperion (1280x1024, 1 bit) - A1416A Kathmandu (a.k.a. Color VRX) (1280x1024 @ 60 hz, 8 bits, DIO-II) o HP-HIL devices - Keyboards - Two and three button mice - 46094 Quadrature Port (supports normal serial mice) - Graphics tablets - Dial boxes - ID modules o Miscellaneous boards/interfaces - 98265A SCSI interface (DIO-I board, daughtercard for 98562, or built-in) - 98561 Human Interface board (DIO-I board with serial port, HP-HIL, and HP-IB) - 98562 System Interface board (DIO-II board with serial port, HP-HIL, HP-IB, DMA, and ethernet, has optional fast HP-IB or SCSI daughterboard) - 98620 DMA card (DIO-I board, for use with 98561) - 98624 HP-IB interface (DIO-I board or built-in) - 98625A and 98625B 'fast' HP-IB interface (DIO-I board or daughtercard for 98562) Each serial interface has its own quirks, and some of them use non-stan- dard pins. The FAQ describes how to configure and connect serial con- soles to hp300 systems. http://www.NetBSD.org/Ports/hp300/faq.html#serialconsole When you try booting from a system with a framebuffer that is not sup- ported by NetBSD/hp300, the screen will turn black, and it will try using the serial port for the console. Unsupported hardware o CPUs - 310 (10 MHz 68010, with built-in monochrome framebuffer, rs232 (25 pin), hil, and slow hpib) - 332 (16? MHz 68030, with no floating point unit) o Graphics Devices - SGC support (for 425e built-in EVRX framebuffer) - SGC support (for some rare configurations of 4XXt and 4XXdl workstations) - 98702 TurboVRX DIO-II graphics device - 98705 Tigershark PersonalVRX DIO-II graphics device - internal video on models 362/382 o Miscellaneous boards/interfaces - domain keyboard and mouse, on Series 400 workstations. Needs wscons - parallel port, on 345, 362, 375, 380, 382, 382, and Series 400 workstations - EISA support, on Series 400 workstations - Token Ring cards (a.k.a. ATR) - VME bus adapter, on Series 300 workstations - 98628A single port dcl (DIO-I board) - 98625C fast HP-IB option on models 345 and 375 - internal SCSI floppy drive on 362, 382, and 425e Getting the NetBSD System on to Useful Media You should wait to decide where to put the NetBSD distribution sets until you have figured out how you are going to boot your system. Refer back to this section after you have done so. Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted. Installation is supported from several media types, including: o CD-ROM / DVD o FTP o Remote NFS partition o Tape o Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the var- ious media are outlined below. CD-ROM / DVD Find out where the distribution set files are on the CD- ROM or DVD. Likely locations are binary/sets and hp300/binary/sets. Proceed to the instruction on installation. FTP The preparations for this installation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. If you don't have DHCP available on your network, you will need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. If you don't have access to a functioning nameserver during installation, the IPv4 address of ftp.NetBSD.org is 204.152.184.75 and the IPv6 address is 2001:4f8:4:7:2e0:81ff:fe21:6563 (as of June, 2004). Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD 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. Note: This method of installation is recommended for those familiar with using BSD network configuration and management commands. If you aren't, this docu- mentation should help, but is not intended to be all-encompassing. NFS Place the NetBSD 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 NetBSD. 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 numeric IP address of the NFS server, and, if you don't have DHCP available on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD 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 NetBSD from scratch, go to the section on pre- paring your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Note: This method of installation is recommended for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Tape To install NetBSD 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 UNIX -like system, the eas- iest way to do so is probably something like: # tar -cf tape_device dist_directories where tape_device 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 sys- tem. (If you can't figure it out, ask your system admin- istrator.) In the above example, dist_directories are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the misc, base, and etc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: # cd .../NetBSD-3.1.1 # cd hp300/binary # tar -cf tape_device misc etc kern Note: You still need to fill in tape_device 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 NetBSD 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. Preparing your System for NetBSD installation There are two installation tools available. The traditional miniroot installer is script-based and may be netbooted or may be dumped to a disk and run locally. The ramdisk kernel with the sysinst installation util- ity is more flexible, but can only be netbooted and has not been exten- sively tested. There are several possible installation configurations described in this document. Other configurations are possible, but less common. If you are unable to install based on the information in this document, post a message to port-hp300@NetBSD.org asking for help. The configurations described in this document are as follows: o hp300 netboots SYS_UBOOT and then runs the miniroot installation tools or a purely diskless installation from a NetBSD server on the same subnet (you must have root access). Other server platforms will work, but are described in the NetBSD Diskless HOW-TO. http://www.NetBSD.org/Documentation/network/netboot/ o hp300 loads SYS_UBOOT from a local disk, tape, or floppy and then runs the miniroot installation tools or a purely diskless installa- tion from a NetBSD server on the same subnet (you must have root access). Other server platforms will work, but are described in the NetBSD Diskless HOW-TO. http://www.NetBSD.org/Documentation/network/netboot/ You will need HP-UX on your hp300 if it does not have a SCSI inter- face or a floppy drive. o hp300 loads SYS_INST from a local disk. You partition the drive and then run the miniroot installation tools from that drive. You will need HP-UX on your hp300 if it does not have a SCSI interface. The preferred method is to use another NetBSD server to netboot the hp300 client. This procedure will not work on the handful of models which are incapable of netbooting. In particular, the 320, 350, 330, 318, and 319 might not have a recent enough BootROM. The BootROM revision is printed when your workstation is first powered on (or rebooted). Revision B or later will definitely work. BootROMs with numeric revisions such as 1.1 (on a 400s) will netboot without any problems. You can netboot from any built-in or add-on ethernet board on a model with a supported BootROM. If you have access to a NetBSD/hp300 system, it is much easier to simply upgrade than to install from scratch. Skip down to the section on Upgrading a previously-installed NetBSD System Formatting your hard drives NetBSD/hp300 does not have the capability to perform a low-level format of hard drives. SCSI disks can be formatted on any platform with SCSI support and then used on NetBSD/hp300. HP-IB disks can only be formatted by the HP-UX mediainit(1) command. You may need to first create the device nodes for your disk, as HP-UX was never very good about populating /dev/rdsk propertly. # mknod /dev/dsk/IDs0 b 0 0xSCID00 # mknod /dev/rdsk/IDs0 c 4 0xSCID00 # mediainit -v /dev/rdsk/IDs0 ID is the HP-IB address (a.k.a. slave) of the disk in hexadecimal. This is usually between 00 and 07, but possibly up to 1F (31 decimal) . SC is the Select Code of the disk controller. This is usually 07 for slow (i.e. built-in) HP-IB or 0E (14 decimal) for SCSI or fast HP-IB. Designing your disk's partition table This step can sometimes be a real pain, especially when using SYS_INST. It's best to calculate it ahead of time. If you are installing to an HP-IB disk, you will need information about your disk's geometry, based on 512-byte sectors. The file installation/misc/HP-IB.geometry in the distribution has geometry infor- mation for several HP-IB disks, but may be incomplete. Geometry may be calculated from an HP-UX /etc/disktab entry, but note that HP-UX geometry is based on 1024 byte sectors, while NetBSD 's is based on 512 byte sec- tors. You should have all partitions start on cylinder boundaries. If you are installing to a SCSI disk, you don't need to worry about the details of the geometry. Just create a disklabel based on the total num- ber of sectors available on the disk. A quick note about partitions: Since the target disk will become the boot disk for your new NetBSD/hp300 installation, you will need to treat the `a' and `c' partitions in a special manner. Due to the size of the NetBSD/hp300 boot program (it spills into the area after the disklabel), it is necessary to offset the beginning of the `a' partition. For HP-IB disks, it is best to offset it by one cylinder from the beginning of the disk. For SCSI disks, just offset it by 100 KB (200 sectors). Later, the `c' partition will be marked with the type `boot' and may not be used for a file system. (For those unfamiliar with historic BSD partition conventions, the `c' partition is defined as the `entire disk', or the `raw partition'.) Here is a table of recommended partition sizes for a full install: Partition Suggested Needed / (root) 25 MB 15 MB /usr 150 MB 100 MB /var 20 MB 5 MB swap 2-3 *RAM 6 MB Note: You will need at least a 6 MB swap partition if you are unable to netboot the installer, as the miniroot is temporarily placed in this partition. Here is an example disklabel from a 7959B HP-IB hard drive: # /dev/rrd0a: type: HP-IB disk: rd7959B label: flags: bytes/sector: 512 sectors/track: 42 tracks/cylinder: 9 sectors/cylinder: 378 cylinders: 1572 total sectors: 594216 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize cpg] a: 37800 378 4.2BSD 1024 8192 16 # b: 66150 38178 swap 1024 8192 16 # c: 594216 0 boot # (Cyl. 0 - 1571) d: 489888 104328 4.2BSD 1024 8192 16 # Installing the bootstrap program locally For earlier models incapable of netbooting, you need to install the boot- strap program on a bootable local device, such as a hard disk, floppy disk, or tape drive. If you will be booting the miniroot over the net- work, then you will be installing installation/misc/SYS_UBOOT. If you do not have access to a netboot server to serve the miniroot installer, you can use a primitive bootstrap program installation/misc/SYS_INST to load the miniroot from a locally attached device (such as a disk, tape or CD-R). This is not recommended, as SYS_INST is difficult to use, buggy, and provides no error checking when partitioning your disk. If your system has SCSI, this is easy. Just take a scratch SCSI disk (hard disk, zip disk, or CD-R) and use any computer to dump the bootstrap program to it. For example, to dump it to the sd1 disk on a non-i386 platform: # dd if=SYS_UBOOT of=/dev/sd1c If your system has a floppy drive, you can write the bootstrap program to it using any computer with a floppy drive. You will need to dump it using a utility like rawrite or dd(1). Make sure to read back from the floppy to verify that the file has been written correctly. If your system does not have SCSI or a floppy drive, you will need a bootable operating system on your hp300 so you can write files to the HP- IB device. You should probably write the bootstrap program to the disk you will be installing NetBSD onto. Using HP-UX to write to an HP-IB disk: # dd if=SYS_UBOOT of=/dev/rdsk/IDs0 ID is the HP-IB address (a.k.a. slave) of the disk in hexadecimal. This is usually between 00 and 07, but possibly up to 1F (31 decimal) . Using HP-UX to write to an HP-IB tape: # dd if=SYS_UBOOT of=/dev/rmt/0mnb obs=20b conv=sync Installing the miniroot file system locally This step is only necessary if you are not loading the miniroot installer from a netboot server. Follow the same procedure for the bootstrap pro- gram, except use the uncompressed miniroot file system (installation/miniroot/miniroot.fs.gz ) instead of the bootstrap program. The only quirk is that you should place it at the offset of the swap par- tition you calculated above in the disklabel. In the example disklabel above, the offset is 38178 sectors of 512 bytes. Therfore, the dd(1) command would be something like: # gunzip miniroot.fs.gz # dd if=miniroot.fs of=/dev/rdsk/IDs0 seek=38178b Note the `b' after the offset, which specifies blocks of 512 bytes. By dumping the miniroot to disk where the swap partition will be, you're saving a step later where SYS_INST tries to download the miniroot over NFS. Just make sure that when you enter the partition table into SYS_INST you use the same block offset for the swap partition as you dumped the miniroot. Configuring the netboot server This step will configure your netboot server to provide SYS_UBOOT and the miniroot installer to your hp300. 1. Introduction To netboot a hp300, you must configure one or more servers to pro- vide information and files to your hp300 (the `client ).' If you are using NetBSD (any architecture) on your netboot server(s), the information provided here should be sufficient to configure every- thing. Additionally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configuring. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps neces- sary to configure the netboot services on a variety of platforms. http://www.NetBSD.org/Documentation/network/netboot/ You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network. Briefly, the netboot process involves discovery, bootstrap, kernel and file system stages. In the first stage, the client discovers information about where to find the bootstrap program. Next, it downloads and executes the bootstrap program. The bootstrap program goes through another discovery phase to determine where the kernel is located. The bootstrap program tries to mount the NFS share con- taining the kernel. Once the kernel is loaded, it starts executing. For RAM disk kernels, it mounts the RAM disk file system and begins executing the installer from the RAM disk. For normal (non-RAM disk) kernels, the kernel tries to mount the NFS share that had the kernel and starts executing the installation tools or init(8). All supported hp300 systems use HP's proprietary RMP (the rbootd(8) dae- mon) for the first discovery stage and bootstrap download stages. The bootstrap program uses DHCP for its discovery stage. NFS is used in both the kernel and file system stages to download the ker- nel, and to access files on the file server. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hard- ware address) of your netboot client machine. You should have determined this address in an earlier stage. In this example, we will use `192.168.1.10' as the IP address of your client and `client.test.net' as its name. We will assume you're providing all of your netboot services on one machine called `server.test.net' with the client's files exported from the directory /export/client/root. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environ- ment. You should set up each netboot stage in order (i.e. discovery, boot- strap, kernel, and then file system) so that you can test them as you proceed. 2. rbootd(8) Get SYS_UBOOT from the installation/misc directory of the distribu- tion. # mkdir -p /usr/mdec/rbootd # cp SYS_UBOOT /usr/mdec/rbootd # chmod -R a+rX /usr/mdec/rbootd Create /etc/rbootd.conf with the following line: CC:CC:CC:CC:CC:CC SYS_UBOOT You will need to start the rbootd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with: # /etc/rc.d/rbootd restart 3. dhcpd(8) The bootstrap program uses DHCP to discover the location of the ker- nel. Put the following lines in your /etc/dhcpd.conf (see dhcpd.conf(5) and dhcp-options(5) for more information): ddns-update-style none; # Do not use any dynamic DNS features # allow bootp; # Allow bootp requests, thus the dhcp server # will act as a bootp server. # authoritative; # master DHCP server for this subnet # subnet 192.168.1.0 netmask 255.255.255.0 { # Which network interface to listen on. # The zeros indicate the range of addresses # that are allowed to connect. } group { # Set of parameters common to all clients # in this "group". # option broadcast-address 192.168.1.255; option domain-name "test.net"; option domain-name-servers dns.test.net; option routers router.test.net; option subnet-mask 255.255.255.0; # # An individual client. # host client.test.net { hardware ethernet CC:CC:CC:CC:CC:CC; fixed-address 192.168.1.10; # # Name of the host (if the fixed address # doesn't resolve to a simple name). # option host-name "client"; # # The path on the NFS server. # option root-path "/export/client/root"; # # If your DHCP server is not your NFS server, supply the # address of the NFS server. Since we assume you run everything # on one server, this is not needed. # # next-server server.test.net; } #you may paste another "host" entry here for additional #clients on this network } You will need to make sure that the dhcpd.leases file exists. # touch /var/db/dhcpd.leases You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with: # /etc/rc.d/dhcpd restart 4. nfsd(8), mountd(8), and rpcbind(8) Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client: # mkdir -p /export/client/root Put the following line in /etc/exports to enable NFS sharing: /export/client/root -maproot=root client.test.net If your server is currently running an NFS server, you only need to restart mountd(8). Otherwise, you need to start rpcbind(8) and nfsd(8). If the server is running NetBSD, you can achieve this with: # /etc/rc.d/rpcbind start # /etc/rc.d/nfsd start # /etc/rc.d/mountd restart 5. NetBSD kernel and installation tools Now, if you place a kernel named netbsd in /export/client/root your client should boot the kernel. If you are netbooting the installer, you can use either the traditional miniroot-based installer installation/miniroot/miniroot.fs.gz or the experimental RAM disk- based installer binary/kernel/netbsd-RAMDISK.gz. To use the miniroot-based installer, mount the miniroot file system on your netboot server. This procedure does not work on any operat- ing system other than NetBSD. You'll also need to either set up a new NFS share point or an FTP server for the distribution files, as they won't fit inside the miniroot file system. # gunzip miniroot.fs.gz # vnconfig -c /dev/vnd0c /path/to/miniroot.fs # mount -o ro /dev/vnd0c /export/client/root # ls /export/client/root .profile dist/ install.md mnt/ sbin/ usr/ bin/ etc/ install.sub mnt2/ tmp/ var/ dev/ install* kern/ netbsd* upgrade* If there are no files present in your exported directory, then some- thing is wrong. To use the RAM disk-based installer, uncompress and rename the ker- nel. Also, copy the distribution files to the client's root direc- tory. # cp *tgz /export/client/root # gunzip netbsd-RAMDISK.gz # mv netbsd-RAMDISK /export/client/root/netbsd If you are running your hp300 diskless, simply use binary/kernel/netbsd-GENERIC.gz. 6. Client file system You can skip this step if you do not plan to run your client disk- less after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/Documentation/network/netboot/nfs.html o Extracting distribution sets # cd /export/client/root # tar -xpzf /path/to/files/base.tgz # tar -xpzf /path/to/files/etc.tgz Continue with the other non-essential distribution sets if desired. o Set up swap # mkdir /export/client/root/swap # dd if=/dev/zero of=/export/client/swap bs=4k count=4k # echo '/export/client/swap -maproot=root:wheel client.test.net' | cat /etc/exports # /etc/rc.d/mountd restart This creates a 16 MB swap file and exports it to the client. o Create device nodes # cd /export/client/root/dev # ./MAKEDEV all This procedure only works on NetBSD hosts. o Set up the client's fstab(5) Create a file in /export/client/root/etc/fstab with the follow- ing lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 o Set up the client's rc.conf(5) Edit /export/client/root/etc/rc.conf rc_configured=YES hostname="client" defaultroute="192.168.1.1" nfs_client=YES auto_ifconfig=NO net_interfaces="" Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system. o Set up the client's hosts(5) file. Edit /export/client/root/etc/hosts ::1 localhost 127.0.0.1 localhost 192.168.1.10 client.test.net client 192.168.1.5 server.test.net server 7. Setting up the server daemons If you want these services to start up every time you boot your server, make sure the following lines are present in your /etc/rc.conf: rbootd=YES rbootd_flags="" dhcpd=YES dhcpd_flags="-q" nfs_server=YES # enable server daemons mountd=YES rpcbind=YES rpcbind_flags="-l" # -l logs libwrap Put Series 400 systems in HP-UX Compatible Boot Mode Series 400 systems can be configured to boot either HP-UX or DomainOS. To boot NetBSD/hp300 you must have your system configured in `HP-UX Compatible Boot Mode'. If, when you power on your machine, it does not present a menu like the following, then you need to change your configu- ration. Copyright 1990, Hewlett-Packard Company. All Rights Reserved. BOOTROM Series 400 Rev. 1.1 MD12 REV 1.2 1990/08/07.14:27:08 [...] 1. Attach a Domain keyboard or an HIL keyboard. The BootROM knows how to use either, even if NetBSD doesn't yet. 2. Put your system into `service mode'. For a 4XXs, there's a toggle switch on the back of the machine (near the top). For a 4XXt or 4XXdl, press the green button on the front, behind the silly door. For a 425e, there's a toggle switch on the back of the machine (in the middle). The second green LED should light up. 3. Reset the machine. Press the reset button. For a 4XXs, ther's a small plunger on the back of the machine (near the top). For a 4XXt or 4XXdl, there's a white button on the front, behind the silly door. For a 425e, there's a button on the back of the machine. 4. Press RETURN to get the Domain boot prompt (). You can type H to get a list of available commands. 5. Type the following sequence of commands to convert to `HP-UX Compatible Boot Mode'. CF Type [key] RETURN ? 2 Type [key] RETURN ? 2 Type T or P RETURN ? P Type [key] RETURN ? E 6. Be sure to turn `service mode' off when you're done. It may prevent you from selecting which device to boot from. See the FAQ for additional help. http://www.NetBSD.org/Ports/hp300/faq.html#domain Searching for a bootable system All the early hp300 Boot ROMs are very primitive and only allow a few simple operations. You can only interact with it after it is first pow- ered on. If you reboot the machine, it will ignore anything you type and start loading the same OS you previously booted. At any time after it recognizes the keyboard, while it is doing its self test or searching for a bootable system, you can hit reset to return it to a cold-boot configuration. On HIL keybaords, this is control-shift-break, where break is the key in the upper left (where escape is on sane keyboards). There is no equivalent over serial termi- nal, you'll need to power-cycle your machine. After it beeps (i.e. recognizes the HIL keyboard), press RETURN twice to get the list of bootable devices. SEARCHING FOR A SYSTEM (RETURN To Pause) The newer HP Boot ROM, present on Series 400 machines and some of the later 300s (345, 375, 380, 382, 385) is capable of a little bit more. To select which device to boot from, press RETURN once after it beeps twice (i.e. recognizes the HIL keyboard) to get the list of bootable devices. RESET To Power-Up, SPACE clears input Select System, type RETURN ? The FAQ lists additional things you can do with the BootROM and describes the order the BootROM looks for bootable devices. http://www.NetBSD.org/Ports/hp300/faq.html A normal power-on sequence (from a 400s) looks something like this: Copyright 1990, Hewlett-Packard Company. All Rights Reserved. BOOTROM Series 400 Rev. 1.1 MD12 REV 1.2 1990/08/07.14:27:08 MC68030 Processor MC68882 Coprocessor Configuration EEPROM Utility Chip at 41 HP-HIL.Keyboard RESET To Power-Up Loading Memory Self-Test Mode RESET To Power-Up, SPACE clears input Select System, type RETURN HP-IB DMA-C0 Self-Test Mode RAM 33554158 Bytes HP98644 (RS-232) at 9 HP PARALLEL at 12 HP98265 (SCSI S 32) at 14 HP98643 (LAN) at 21, AUI, 080009115DB3 Bit Mapped Video at 133 (Console) System Search Mode :RODIME RO3000T, 1406, 0 1Z SYS_UBOOT :LAN080009115DB3, 2100, 0 2Z SYS_UBOOT :HP7959, 702, 0, 0 1H SYSHPUX 1D SYSDEBUG 1B SYSBCKUP :HP9122, 0700, 0, 0 3Z SYS_INST You should see your bootstrap program somewhere in this list. If it's not here, then your hp300 can't boot it and there's a problem somewhere. To boot from a particular device, type in the two character name for it and press RETURN. In this example, you'd type 2Z to boot from the net- work. Selecting ethernet port on Series 400 Series 400 machines have two ethernet media types built into the mother- board. You may only use one at a time. When your Series 400 workstation goes through the self-test when powered on or rebooted, it will say one of the following: HP98643 (LAN) at 21, AUI HP98643 (LAN) at 21, Thin If the wrong type of network is selected, you will need to change the ethernet port. You will need to open the case (4XXt, 4XXdl, 4XXe) or remove the motherboard (4XXs) to access the jumper. Be sure to use static-prevention measures, as you could easily fry your motherboard from carelessness. If you are uncomfortable with this, ask a friend who is aware of these issues. There is a block of 8 jumpers at the rear of the motherboard, labeled AUI/Thin. You will need to put the jumpers in the position necessary for your type of ethernet. Running SYS_INST This step is necessary only if you cannot netboot. Chose SYS_INST from the list of bootable devices that the BootROM found. SYS_INST will load and prompt you for a command. A quick note about disk numbers: While in the SYS_INST program, you may use different unit numbers for the disks than when the NetBSD kernel is running. The unit number for a disk while in SYS_INST is calculated with the following formula: unit = (controller * 8) + slaveID Controllers are numbered 0, 1, ... starting with the lowest select code. SCSI controllers and HP-IB controllers are counted separately. There- fore, if you had a system with an internal HP-IB interface at select code 7, a fast HP-IB interface at select code 14, and a SCSI interface at select code 16, unit numbers might be something like the following: Location Unit HP-IB at 7, slaveID 2 2 (disk: rd2) HP-IB at 14, slaveID 5 13 (disk: rd13) SCSI at 16, slaveID 0 0 (disk: sd0) You will need to place a disklabel on the disk. sys_inst disklabel Note: It may be worth selecting the zap option initially to ensure that the disklabel area is clear. This may be especially important if an HP-UX boot block had been previously installed on the disk. Select the edit option, and answer the questions about your disk. There may be several questions which you may not be sure of the answers to. Listed below are guidelines for SCSI and HP-IB disks: Bad sectoring? NO Ecc? NO Interleave? 1 Trackskew? 0 Cylinderskew? 0 Headswitch? 0 Track-to-track? 0 Drivedata 0-4? 0 (for all Drivedata values) Next, you will be asked to fill out the partition map. You must provide responses for all 8 partitions. Remember, you must have the sector off- set for the `b' partition match the location you dumped the miniroot file system image. Set the size and offset of any unused partition to 0. Note that sizes and offsets are expressed in `n sectors', assuming 512 byte sectors. Care should be taken to ensure that partitions begin and end on cylinder boundaries (i.e. size and offset is an even multiple of the number of sectors per cylinder). While this is not technically nec- essary, it is generally encouraged. Note: When setting the partition type of the `b' partition, make sure to specify it as an ffs partition so that the miniroot can be mounted (even if this will be a swap partition). You will be given a chance to clean this up later in the installation process. Once you have edited the label, select the show option to verify that it is correct. If so, select write and done. Otherwise, you may re-edit the label. In an earlier step, we already copied the miniroot image to the target disk. Boot from the miniroot file system. sys_inst boot Enter the disk from which to boot. The kernel in the miniroot file sys- tem will be booted into single-user mode. Chosing a kernel location Once the bootstrap program SYS_UBOOT has started, it will pause and let you chose a kernel location, name, and options: NetBSD/hp300 Primary Boot, Revision 1.13 (gregm@mcgarry, Mon Apr 15 08:46:32 NZST 2002) HP 9000/425e SPU Enter "reset" to reset system. Boot: [[[le0a:]netbsd][-a][-c][-d][-s][-v][-q]] :- If your kernel is on a different device than SYS_UBOOT then you will need to type in where to find it. This is the case, for example, if your model is incapable of netbooting and you started SYS_UBOOT from a floppy, and the miniroot installer is on a netboot server. In this case, you'd type in `le0' at the prompt. If you've installed the miniroot on your disk, you can always boot from that by using partition `b' when prompted by SYS_UBOOT. For example, to boot the miniroot from an HP-IB disk on controller 0 at slave ID 2, you'd type: Boot: [[[rd0a:]netbsd][-a][-c][-d][-s][-v][-q]] :- rd2b:netbsd Installing the NetBSD System The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. If you need to restart the installer, hit Control-C which will return you to a shell prompt. From there, just start it over: # ./install The experimental RAM disk-based installer is not described here, but is very self-explanatory. The miniroot's install program will: 1. Allow you to place disklabels on additional disks. Note that parti- tion sizes and offsets are expressed in sectors. When you fill out the disklabel, you will need to specify partition types and file system parameters. If you're unsure what these values should be, use the following: fstype: 4.2BSD fsize: 1024 bsize: 4096 cpg: 16 If the partition will be a swap partition, use the following: fstype: swap fsize: 0 (or blank) bsize: 0 (or blank) cpg: 0 (or blank) You will also need to specify the number of partitions. The number of partitions is determined by the `index' of the last partition letter, where a = 1, b = 2, etc. Therefore, if the last filled par- tition is partition `g', there are 7 partitions. Any partitions with size of 0 may be removed from the list. Anything after a `#' is a comment. The following is an example disklabel partition map: 7 partitions: # size offset fstype [fsize bsize cpg] a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69) b: 130816 31360 swap # (Cyl. 70 - 361) c: 1296512 0 boot # (Cyl. 0 - 2893) e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544) f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773) g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893) 2. Create file systems on target partitions. 3. Allow you to set up your system's network configuration. Remember to specify host names without the domain name appended to the end. For example use foo instead of foo.bar.org. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for configuration again. 4. Mount target file systems. You will be given the opportunity to manually edit the resulting /etc/fstab. 5. Extract binary sets from the media of your choice. 6. Copy configuration information gathered during the installation process to your root file system (/). 7. Make device nodes in your root file system under /dev. 8. Copy a new kernel onto your root partition (/). 9. Install a new boot block. 10. Check your file systems for integrity. First-time installation on a system through a method other than the installation program is possible, but strongly discouraged. Post installation steps Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below. 1. Configuring /etc/rc.conf If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst usually will), the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (/) mounted read-only. When the sys- tem asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a terminal type, respond with hp300h for a local console, or whatever is appropriate for your serial console. and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depend- ing on your keyboard: # stty erase '^h' # stty erase '^?' At this point, you need to configure at least one file in the /etc directory. You will need to mount your root file system read/write with: # /sbin/mount -u -w / Change to the /etc directory and take a look at the /etc/rc.conf file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). If your /usr directory is on a separate partition and you do not know how to use ed, you will have to mount your /usr partition to gain access to ex or vi. Do the following: # mount /usr # export TERM=hp300h If you have /var on a separate partition, you need to repeat that step for it. After that, you can edit /etc/rc.conf with vi(1). When you have finished, type exit at the prompt to leave the single- user shell and continue with the multi-user boot. Other values that need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your network interface, along the lines of ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_le0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an /etc/resolv.conf file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Instead of manually configuring network and naming service, DHCP can be used by setting dhclient=YES in /etc/rc.conf. Other files in /etc that may require modification or setting up include /etc/mailer.conf, /etc/nsswitch.conf, and /etc/wscons.conf. 2. Logging in After reboot, you can log in as root at the login prompt. Unless you've set a password in sysinst, there is no initial password. If you're using the machine in a networked environment, you should cre- ate an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is disabled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...]. 3. Adding accounts Use the useradd(8) command to add accounts to your system. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 4. The X Window System If you have installed the X Window System, look at the files in /usr/X11R6/lib/X11/doc for information. Also, you may want to read through the NetBSD/hp300 FAQ entry on X11. http://www.NetBSD.org/Ports/faq.html#x11 Don't forget to add /usr/X11R6/bin to your path in your shell's dot file so that you have access to the X binaries. 5. Installing third party packages If you wish to install any of the software freely available for UNIX -like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries. o More information on the package system is at http://www.NetBSD.org/Documentation/software/packages.html o A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/README.html o Precompiled binaries can be found at ,: ftp://ftp.NetBSD.org/pub/NetBSD/packages/ usually in the 3.1.1/hp300/All subdir. You can install them with the following commands under sh(1): # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/hp300/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v mozilla ... If you are using csh(1) then replace the first two lines with the following: # setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.1.1/hp300/All ... The above commands will install the Tenex-csh and Bourne Again shell, the Perl programming language, Apache web server, KDE desktop environment and the Mozilla web browser as well as all the packages they depend on. o Package sources for compiling packages on your own can be obtained by retrieving the file ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/tar_files/pkgsrc.tar.gz They are typically extracted into /usr/pkgsrc (though other locations work fine), with the commands: # mkdir /usr/pkgsrc # ( cd /usr/pkgsrc ; tar -zxpf - ) pkgsrc.tar.gz After extracting, see the README and doc/pkgsrc.txt files in the extraction directory (e.g. /usr/pkgsrc/README) for more infor- mation. 6. Misc o Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. o The /etc/mail/sendmail.cf file will almost definitely need to be adjusted; files aiding in this can be found in /usr/share/sendmail. See the README file there for more infor- mation. If you prefer postfix as MTA, adjust /etc/mailer.conf. o Edit /etc/rc.local to run any local daemons you use. o Many of the /etc files are documented in section 5 of the man- ual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System It is possible to easily upgrade your existing NetBSD/hp300 system using the upgrade program in the miniroot or by manually performing the same steps as the miniroot upgrade program. Upgrading using the miniroot If you wish to upgrade your system by this method, simply select the upgrade option once the miniroot has booted. The upgrade program with then guide you through the procedure. While you can boot the miniroot using the same methods described above for a fresh install of NetBSD/hp300 there are easier and less intrusive options since your disk is already labeled and bootable. The easiest is to dump the miniroot to your swap partition and boot from that. 1. Download the files you'll need to upgrade In particular, make sure you have on your locally mounted file sys- tems base.tgz and miniroot.fs.gz 2. Boot your hp300 into `single-user mode': Follow the instructions in the section above on Chosing a kernel location and type -s at the prompt. 3. Extract and install a new boot block: Make sure you install the bootstrap program distributed with this version of NetBSD/hp300. # tar -xpvzf base.tgz ./usr/mdec # disklabel -B -b ./usr/mdec/uboot.lif root-disk E.g.: root-disk could be sd0 or rd0. We'll assume rd0 for now. 4. Install the miniroot file system: First make sure that your `b' partition has enough room for the uncompressed miniroot (otherwise it might overwrite another parti- tion or the end of the disk). # gunzip miniroot.fs.gz # dd if=miniroot.fs of=/dev/rd0b 5. Boot the miniroot: Follow the instructions in the section above on Chosing a kernel location and type rd0b:netbsd at the prompt. The upgrade program will: 1. Enable the network based on your system's current network configura- tion. 2. Mount your existing file systems. 3. Extract binary sets from the media of your choice. 4. Fixup your system's existing /etc/fstab, changing the occurrences of ufs to ffs and let you edit the resulting file. 5. Make new device nodes in your root file system under /dev. 6. Don't forget to extract the kern set from the distribution. Note: The existing kernel will not be backed up; doing so would be pointless, since older kernels may not be capable of running NetBSD 3.1.1 executables. 7. Install a new boot block. 8. Check your file systems for integrity. 9. You'll have to reboot your system manually Manual upgrade While using the miniroot's upgrade program is the preferred method of upgrading your system, it is possible to upgrade your system manually. To do this, follow the following procedure: 1. Place at least the base binary set in a file system accessible to the target machine. A local file system is preferred, since the NFS subsystem in the NetBSD 3.1.1 kernel may be incompatible with your old binaries. 2. Back up your pre-existing kernel and copy the 3.1.1 kernel into your root partition (/). 3. Extract and install a new boot block: Make sure you install the bootstrap program distributed with this version of NetBSD/hp300. # tar -xpvzf base.tgz ./usr/mdec # disklabel -B -b ./usr/mdec/uboot.lif root-disk E.g.: root-disk could be sd0 or rd0. 4. Reboot with the 3.1.1 kernel into single-user mode. 5. Check all file systems: # /sbin/fsck -pf 6. Mount all local file systems: # /sbin/mount -a -t nonfs 7. If you keep /usr or /usr/share on an NFS server, you will want to mount those file systems as well. To do this, you will need to enable the network: # sh /etc/rc.d/network start 8. Make sure you are in the root file system (/) and extract the base binary set: # cd / # pax -zrvpe -f /path/to/base.tgz 9. Sync the file systems: # sync 10. At this point you may extract any other binary sets you may have placed on local file systems, or you may wish to extract additional sets at a later time. To extract these sets, use the following com- mands: # cd / # pax -zrvpe -f path_to_set Note: You should not extract the etc set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand. Compatibility Issues With Previous NetBSD Releases Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 3.1.1. Issues affecting an upgrade from NetBSD 3.1 and older releases. It is very important that you populate the directory /etc/pam.d with appropriate configuration files for the Pluggable Authentication Modules (PAM) because you will not be able to login any more otherwise. Using postinstall as described below will take care of this. Please refer to http://www.netbsd.org/guide/en/chap-pam.html for documentation about PAM. The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall: postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/pam.d/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* The following issues need to be resolved manually: - The user `_pflogd' and the groups `_pflogd' and `authpf' need to be created. Using online NetBSD documentation Documentation is available if you first install the manual dis- tribution set. Traditionally, the ``man pages'' (documenta- tion) are denoted by `name(section)'. Some examples of this are - intro(1), - man(1), - apropros(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 informa- tion 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 indi- cate that the section is optional. If you don't ask for a par- ticular section, the topic with the lowest numbered section name will be displayed. For instance, after logging in, enter # man passwd to read the documentation for passwd(1). To view the documen- tation 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 possi- bly related man pages will be displayed. Administrivia If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mail- ing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.org. To report bugs, use the send-pr(1) command shipped with NetBSD, 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: netbsd-bugs@NetBSD.org. Use of send-pr(1) is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/MailingLists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.org. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW 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. Thanks go to - The former members of UCB's Computer Systems Research Group, including (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encour- agement. - The Internet Systems Consortium, Inc. for hosting the NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS, SUP, Rsync and WWW servers. - The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. - The Helsinki University of Technology in Finland for host- ing the NetBSD backup CVS and backup server. - SSH Communications Security in Finland for operating the backup server. - The many organizations that provide NetBSD mirror sites. - Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the vari- ous other people who've had a hand in making CVS a useful tool. - The following individuals and organizations (each in alpha- betical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: AMD - Advanced Micro Devices, Inc. ASA Computers Aaron Wall ABE Masayuki AboveNet Communications, Inc. Achim Grolms Adam Kasper Adaptec Advanced System Products, Inc. Akihiro IIJIMA Alex Poylisher Algorithmics, Ltd. Alistair Crooks Allegro Networks Aloys Keller Andreas Berg Andreas Jellinghaus Andrew Brown Andrew Gillham Andy Hagans Antonio Larripa Arend Harrewijne Armijn Hemel Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Benoit Lepage Bernhard Moellemann Bill Coldwell Bill Sommerfeld Bill Squier Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Brian Mitchell Canada Connect Corporation Carl Shapiro Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Chris Townsend Christer O. Andersson Christopher G. Demetriou Christos Zoulas Chuck Silvers Cologne Chip AG Computer und Literatur Verlag Computertechnik Krienke & Nolte Computing Services Department, The University of Liverpool Convert Tools Co-operative Research Centre for Enterprise Distributed Curt Sampson DAYOMON from Japan Damicon Kraa, Finland Daniel de Kok Dave Burgess Dave Rand Dave Tyson David Brownlee Dayton Clark Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Distro Jockey Douglas J. Trainor Dr.ir. F.W. Dillema Easynet, UK Ed Braaten Edward Richley emuty Eric and Rosemary Spahr Erik Berls Erik E. Fair Erkki Ruohtula Ernst Lehmann Espen Randen Ewald Kicker Florent Parent Frank Kardel Free Hardware Foundation Front Range *BSD User Group FUKAUMI Naoki Gan Uesli Starling Garth R. Patil Geert Hendrickx (ghen) Geert Jan de Groot GK Meier Gordon Zaft Grant Beattie Greg Gingerich Greg Girczyc Guenther Grau HP Sweden Hanno Wagner Hans Huebner Harald Koerfgen Haroon Khalid Harry McDonald Hauke Fath Heiko W. Rupp Herb Peyerl Hernani Marques Madeira Hidekichi Ookubo Hideyuki Kido Hisashi Fujinaka Holger Weiss Hubert Feyrer IBM Corporation IMAI Kiyoshi Innovation Development Enterprises of America Intel Internet Software Consortium Internet Users Forever IKI Interoute Telecommunications, UK JNUG (raised at JNUG meeting & BOF August 2005) James Bursa James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jeff Rizzo Jeff Woodall - Portland, OR Jens Schoenfeld Jim Wise Joachim Nink Joachim Thiemann Joel CARNAT John Heasley John Kohl John P. Refling Jonathan P. Kay Jordan K. Hubbard Jorgen Lundman Karl Wagner Kenji Hisazumi Kenneth Alan Hornstein Kenneth P. Stox Kevin Keith Woo Kevin Sullivan Klaus Lichti Kimmo Suominen Korea BSD User Forum Krister Waldfridsson Kwok Ng Lars Mathiassen Lehmanns Fachbochhandlung Lex Wennmacher LinuxFest Northwest Luke Maurits Luke Mewburn MS Macro System GmbH, Germany Maki Kato Marc Tooley Marcus Wyremblewski Mark Brinicombe Mark Houde Mark Perkins Mark S. Thomas Mason Loring Bliss Martin Cernohorsky Martin J. Ekendahl Matt Dainty Matt Thomas Matthew Jacob Matthew Sporleder Matthias Scheler Mattias Karlsson Mel Kravitz Michael Graff Michael "Kvedulv" Moll Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Mirko Thiesen (Thiesi) Murphy Software BV, Netherlands Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Olaf "Rhialto" Seibert Oliver Cahagne Oppedahl & Larson LLP Palle Lyckegaard Paul Ripke Paul Southworth Pawel Rogocz Pearson Education Perry E. Metzger Petar Bogdanovic Peter C. Wallace Peter J. Bui Peter Postma Petri T. Koistinen Phil Thomas Piermont Information Systems Inc. Pierre-Philipp Braun Precedence Technologies Ltd Public Access Networks Corporation Ralph Campbell Randy Ray Real Weasel Reinoud Zandijk Renewed Health Company Richard Nelson Rob Windsor Robert Pankratz Robert Thille Roland Lichti Ross Harvey Ryan Campbell SDF Public Access Unix, Inc. 501(c)(7) SMC Networks Inc. Salient Systems Inc. Sander van Dijk Scott Ellis Scott Kaplan Scott Walters Sean Davis Simon Burge Soren Jacobsen Soren Jorvang Stephen Borrill Stephen Early Steve Allen Steve Wadlow Steven M. Bellovin SunROOT# Project Sylvain Schmitz Takahiro Kambe TAKEUCHI Yoji Tamotsu Kanoh Tasis Michalakopoulos (Athens, Greece) Tatoku Ogaito Ted Lemon Ted Spradley The Names Database The NetBSD Mission The People's Republic of Ames Thierry Lacoste Thierry Laronde Thomas Runge Thor Lancelot Simon Tim Law Timo Scholer Tino Hanich Tino Wildenhain Tom Coulter Tom Ivar Helbekkmo Tom Lyon Tomas Dabasinskas Torsten Harenberg Toru Nishimura Toshiba Turbocat's Development Tyler Sarna UTN Web Directory VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems, Inc. Whitecross Database Systems Ltd. William Gnadt Worria Affordable Web Hosting Worria Web Hosting wwwTrace Traceroute Server Directory Yusuke Yokota Zach Metzinger (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) - Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in Jan- uary, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) We are... (in alphabetical order) The NetBSD core group: Allen Briggs briggs@NetBSD.org Matt Thomas matt@NetBSD.org Valeriy E. Ushakov uwe@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Christos Zoulas christos@NetBSD.org The portmasters (and their ports): ~ Allen Briggs briggs@NetBSD.org sandpoint Anders Magnusson ragge@NetBSD.org vax Andrey Petrov petrov@NetBSD.org sparc64 Ben Harris bjh21@NetBSD.org acorn26 Chris Gilbert chris@NetBSD.org cats Christian Limpach cl@NetBSD.org xen Eduardo Horvath eeh@NetBSD.org evbppc Frank van der Linden fvdl@NetBSD.org amd64 Frank van der Linden fvdl@NetBSD.org i386 Gavan Fantom gavan@NetBSD.org iyonix IWAMOTO Toshihiro toshii@NetBSD.org hpcarm Ichiro Fukuhara ichiro@NetBSD.org hpcarm Ignatios Souvatzis is@NetBSD.org amiga Izumi Tsutsui tsutsui@NetBSD.org hp300 Izumi Tsutsui tsutsui@NetBSD.org news68k Jason Thorpe thorpej@NetBSD.org algor Jason Thorpe thorpej@NetBSD.org evbarm Jason Thorpe thorpej@NetBSD.org shark Jeremy Cooper jeremy@NetBSD.org sun3 Jonathan Stone jonathan@NetBSD.org pmax Julian Coleman jdc@NetBSD.org atari Jun-ichiro itojun Hagino itojun@NetBSD.org evbsh3 Jun-ichiro itojun Hagino itojun@NetBSD.org mmeye Kazuki Sakamoto sakamoto@NetBSD.org bebox Lennart Augustsson augustss@NetBSD.org pmppc Marcus Comstedt marcus@NetBSD.org dreamcast Martin Husemann martin@NetBSD.org sparc64 Matt DeBergalis deberg@NetBSD.org next68k Matt Fredette fredette@NetBSD.org hp700 Matt Fredette fredette@NetBSD.org sun2 Matt Thomas matt@NetBSD.org alpha Matt Thomas matt@NetBSD.org netwinder Matthias Drochner drochner@NetBSD.org cesfic NISHIMURA Takeshi nsmrtks@NetBSD.org x68k NONAKA Kimihiro nonaka@NetBSD.org prep Nathan Williams nathanw@NetBSD.org sun3 Noriyuki Soda soda@NetBSD.org arc Paul Kranenburg pk@NetBSD.org sparc Phil Nelson phil@NetBSD.org pc532 Reinoud Zandijk reinoud@NetBSD.org acorn32 Ross Harvey ross@NetBSD.org alpha Soren Jorvang soren@NetBSD.org cobalt Soren Jorvang soren@NetBSD.org sgimips Scott Reynolds scottr@NetBSD.org mac68k Shin Takemura takemura@NetBSD.org hpcmips Simon Burge simonb@NetBSD.org evbmips Simon Burge simonb@NetBSD.org evbppc Simon Burge simonb@NetBSD.org pmax Simon Burge simonb@NetBSD.org sbmips Steve Woodford scw@NetBSD.org evbsh5 Steve Woodford scw@NetBSD.org mvme68k Steve Woodford scw@NetBSD.org mvmeppc Tohru Nishimura nisimura@NetBSD.org luna68k Tsubai Masanari tsubai@NetBSD.org macppc Tsubai Masanari tsubai@NetBSD.org newsmips UCHIYAMA Yasushi uch@NetBSD.org hpcsh UCHIYAMA Yasushi uch@NetBSD.org playstation2 Wayne Knowles wdk@NetBSD.org mipsco Wolfgang Solfrank ws@NetBSD.org ofppc The NetBSD 3.1.1 Release Engineering team: Grant Beattie grant@NetBSD.org Erik Berls cyber@NetBSD.org James Chacon jmc@NetBSD.org Julian Coleman jdc@NetBSD.org Havard Eidnes he@NetBSD.org Jun-ichiro itojun Hagino itojun@NetBSD.org Geert Hendrickx ghen@NetBSD.org Soren Jacobsen snj@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org Luke Mewburn lukem@NetBSD.org Jeff Rizzo riz@NetBSD.org Matthias Scheler tron@NetBSD.org Curt Sampson cjs@NetBSD.org Jim Wise jwise@NetBSD.org NetBSD Developers: Nathan Ahlstrom nra@NetBSD.org Steve Allen wormey@NetBSD.org Jukka Andberg jandberg@NetBSD.org Julian Assange proff@NetBSD.org Lennart Augustsson augustss@NetBSD.org Christoph Badura bad@NetBSD.org Bang Jun-Young junyoung@NetBSD.org Dieter Baron dillo@NetBSD.org Robert V. Baron rvb@NetBSD.org Alan Barrett apb@NetBSD.org Grant Beattie grant@NetBSD.org Jason Beegan jtb@NetBSD.org Erik Berls cyber@NetBSD.org Hiroyuki Bessho bsh@NetBSD.org John Birrell jb@NetBSD.org Mason Loring Bliss mason@NetBSD.org Charles Blundell cb@NetBSD.org Rafal Boni rafal@NetBSD.org Sean Boudreau seanb@NetBSD.org Manuel Bouyer bouyer@NetBSD.org John Brezak brezak@NetBSD.org Allen Briggs briggs@NetBSD.org Mark Brinicombe mark@NetBSD.org Aaron Brown abrown@NetBSD.org Andrew Brown atatat@NetBSD.org David Brownlee abs@NetBSD.org Frederick Bruckman fredb@NetBSD.org Jon Buller jonb@NetBSD.org Simon Burge simonb@NetBSD.org Robert Byrnes byrnes@NetBSD.org D'Arcy J.M. Cain darcy@NetBSD.org Dave Carrel carrel@NetBSD.org Daniel Carosone dan@NetBSD.org James Chacon jmc@NetBSD.org Bill Coldwell billc@NetBSD.org Julian Coleman jdc@NetBSD.org Ben Collver ben@NetBSD.org Jeremy Cooper jeremy@NetBSD.org Chuck Cranor chuck@NetBSD.org Alistair Crooks agc@NetBSD.org Aidan Cully aidan@NetBSD.org Garrett D'Amore gdamore@NetBSD.org Johan Danielsson joda@NetBSD.org John Darrow jdarrow@NetBSD.org Jed Davis jld@NetBSD.org Matt DeBergalis deberg@NetBSD.org Rob Deker deker@NetBSD.org Chris G. Demetriou cgd@NetBSD.org Tracy Di Marco White gendalia@NetBSD.org Jaromir Dolecek jdolecek@NetBSD.org Andy Doran ad@NetBSD.org Roland Dowdeswell elric@NetBSD.org Emmanuel Dreyfus manu@NetBSD.org Matthias Drochner drochner@NetBSD.org Jun Ebihara jun@NetBSD.org Elad Efrat elad@NetBSD.org Havard Eidnes he@NetBSD.org Stoned Elipot seb@NetBSD.org Michael van Elst mlelstv@NetBSD.org Enami Tsugutomo enami@NetBSD.org Bernd Ernesti veego@NetBSD.org Erik Fair fair@NetBSD.org Gavan Fantom gavan@NetBSD.org Hubert Feyrer hubertf@NetBSD.org Jason R. Fink jrf@NetBSD.org Liam J. Foy liamjfoy@NetBSD.org Matt Fredette fredette@NetBSD.org Thorsten Frueauf frueauf@NetBSD.org Castor Fu castor@NetBSD.org Ichiro Fukuhara ichiro@NetBSD.org Quentin Garnier cube@NetBSD.org Thomas Gerner thomas@NetBSD.org Simon J. Gerraty sjg@NetBSD.org Justin Gibbs gibbs@NetBSD.org Chris Gilbert chris@NetBSD.org Eric Gillespie epg@NetBSD.org Adam Glass glass@NetBSD.org Michael Graff explorer@NetBSD.org Brian C. Grayson bgrayson@NetBSD.org Matthew Green mrg@NetBSD.org Andreas Gustafsson gson@NetBSD.org Jun-ichiro itojun Hagino itojun@NetBSD.org Juergen Hannken-Illjes hannken@NetBSD.org Charles M. Hannum mycroft@NetBSD.org Ben Harris bjh21@NetBSD.org Ross Harvey ross@NetBSD.org Eric Haszlakiewicz erh@NetBSD.org John Hawkinson jhawk@NetBSD.org HAMAJIMA Katsuomi hamajima@NetBSD.org HAYAKAWA Koichi haya@NetBSD.org John Heasley heas@NetBSD.org Geert Hendrickx ghen@NetBSD.org Rene Hexel rh@NetBSD.org Iain Hibbert plunky@NetBSD.org Kouichirou Hiratsuka hira@NetBSD.org Michael L. Hitch mhitch@NetBSD.org Jachym Holecek freza@NetBSD.org Christian E. Hopps chopps@NetBSD.org Ken Hornstein kenh@NetBSD.org Marc Horowitz marc@NetBSD.org Eduardo Horvath eeh@NetBSD.org Nick Hudson skrll@NetBSD.org Shell Hung shell@NetBSD.org Martin Husemann martin@NetBSD.org Dean Huxley dean@NetBSD.org Love Hornquist Astrand lha@NetBSD.org Bernardo Innocenti bernie@NetBSD.org Tetsuya Isaki isaki@NetBSD.org ITOH Yasufumi itohy@NetBSD.org IWAMOTO Toshihiro toshii@NetBSD.org Matthew Jacob mjacob@NetBSD.org Soren Jacobsen snj@NetBSD.org Lonhyn T. Jasinskyj lonhyn@NetBSD.org Darrin Jewell dbj@NetBSD.org Chris Jones cjones@NetBSD.org Soren Jorvang soren@NetBSD.org Takahiro Kambe taca@NetBSD.org Antti Kantee pooka@NetBSD.org Masanori Kanaoka kanaoka@NetBSD.org Frank Kardel kardel@NetBSD.org Mattias Karlsson keihan@NetBSD.org KAWAMOTO Yosihisa kawamoto@NetBSD.org Mario Kemper magick@NetBSD.org Min Sik Kim minskim@NetBSD.org Thomas Klausner wiz@NetBSD.org Klaus Klein kleink@NetBSD.org John Klos jklos@NetBSD.org Wayne Knowles wdk@NetBSD.org Takayoshi Kochi kochi@NetBSD.org John Kohl jtk@NetBSD.org Daniel de Kok daniel@NetBSD.org Paul Kranenburg pk@NetBSD.org Martti Kuparinen martti@NetBSD.org Kentaro A. Kurahone kurahone@NetBSD.org Kevin Lahey kml@NetBSD.org Johnny C. Lam jlam@NetBSD.org Martin J. Laubach mjl@NetBSD.org Greg Lehey grog@NetBSD.org Ted Lemon mellon@NetBSD.org Christian Limpach cl@NetBSD.org Frank van der Linden fvdl@NetBSD.org Joel Lindholm joel@NetBSD.org Mike Long mikel@NetBSD.org Michael Lorenz macallan@NetBSD.org Warner Losh imp@NetBSD.org Tomasz Luchowski zuntum@NetBSD.org Federico Lupi federico@NetBSD.org Brett Lymn blymn@NetBSD.org Paul Mackerras paulus@NetBSD.org Anders Magnusson ragge@NetBSD.org MAEKAWA Masahide gehenna@NetBSD.org David Maxwell david@NetBSD.org Dan McMahill dmcmahill@NetBSD.org Gregory McGarry gmcgarry@NetBSD.org Jared D. McNeill jmcneill@NetBSD.org Neil J. McRae neil@NetBSD.org Perry Metzger perry@NetBSD.org Simas Mockevicius symka@NetBSD.org Juan Romero Pardines xtraeme@NetBSD.org Julio M. Merino Vidal jmmv@NetBSD.org Minoura Makoto minoura@NetBSD.org Luke Mewburn lukem@NetBSD.org der Mouse mouse@NetBSD.org Joseph Myers jsm@NetBSD.org Ken Nakata kenn@NetBSD.org Takeshi Nakayama nakayama@NetBSD.org Phil Nelson phil@NetBSD.org John Nemeth jnemeth@NetBSD.org Bob Nestor rnestor@NetBSD.org NISHIMURA Takeshi nsmrtks@NetBSD.org Tohru Nishimura nisimura@NetBSD.org NONAKA Kimihiro nonaka@NetBSD.org Takehiko NOZAKI tnozaki@NetBSD.org Jesse Off joff@NetBSD.org Tatoku Ogaito tacha@NetBSD.org OKANO Takayoshi kano@NetBSD.org Masaru Oki oki@NetBSD.org Atsushi Onoe onoe@NetBSD.org Greg Oster oster@NetBSD.org Jonathan Perkin sketch@NetBSD.org Herb Peyerl hpeyerl@NetBSD.org Matthias Pfaller matthias@NetBSD.org Chris Pinnock cjep@NetBSD.org Adrian Portelli adrianp@NetBSD.org Rui Paulo rpaulo@NetBSD.org Peter Postma peter@NetBSD.org Dante Profeta dante@NetBSD.org Chris Provenzano proven@NetBSD.org Niels Provos provos@NetBSD.org Michael Rauch mrauch@NetBSD.org Marc Recht recht@NetBSD.org Darren Reed darrenr@NetBSD.org Jeremy C. Reed reed@NetBSD.org Antoine Reilles tonio@NetBSD.org Tyler R. Retzlaff rtr@NetBSD.org Scott Reynolds scottr@NetBSD.org Michael Richardson mcr@NetBSD.org Tim Rightnour garbled@NetBSD.org Alan Ritter rittera@NetBSD.org Jeff Rizzo riz@NetBSD.org Gordon Ross gwr@NetBSD.org Steve Rumble rumble@NetBSD.org Ilpo Ruotsalainen lonewolf@NetBSD.org Heiko W. Rupp hwr@NetBSD.org David Sainty dsainty@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org Kazuki Sakamoto sakamoto@NetBSD.org Curt Sampson cjs@NetBSD.org Wilfredo Sanchez wsanchez@NetBSD.org Ty Sarna tsarna@NetBSD.org SATO Kazumi sato@NetBSD.org Jan Schaumann jschauma@NetBSD.org Matthias Scheler tron@NetBSD.org Karl Schilke (rAT) rat@NetBSD.org Amitai Schlair schmonz@NetBSD.org Konrad Schroder perseant@NetBSD.org Georg Schwarz schwarz@NetBSD.org Lubomir Sedlacik salo@NetBSD.org Christopher SEKIYA sekiya@NetBSD.org Reed Shadgett dent@NetBSD.org John Shannon shannonjr@NetBSD.org Tim Shepard shep@NetBSD.org Takeshi Shibagaki shiba@NetBSD.org Naoto Shimazaki igy@NetBSD.org Takao Shinohara shin@NetBSD.org Takuya SHIOZAKI tshiozak@NetBSD.org Chuck Silvers chs@NetBSD.org Thor Lancelot Simon tls@NetBSD.org Jeff Smith jeffs@NetBSD.org Noriyuki Soda soda@NetBSD.org Wolfgang Solfrank ws@NetBSD.org SOMEYA Yoshihiko someya@NetBSD.org Bill Sommerfeld sommerfeld@NetBSD.org Jorg Sonnenberger joerg@NetBSD.org Ignatios Souvatzis is@NetBSD.org Bill Squier groo@NetBSD.org Jonathan Stone jonathan@NetBSD.org Bill Studenmund wrstuden@NetBSD.org Kevin Sullivan sullivan@NetBSD.org SUNAGAWA Keiki kei@NetBSD.org Kimmo Suominen kim@NetBSD.org Shin Takemura takemura@NetBSD.org TAMURA Kent kent@NetBSD.org Shin'ichiro TAYA taya@NetBSD.org Ian Lance Taylor ian@NetBSD.org Matt Thomas matt@NetBSD.org Jason Thorpe thorpej@NetBSD.org Christoph Toshok toshok@NetBSD.org Greg Troxel gdt@NetBSD.org Tsubai Masanari tsubai@NetBSD.org Izumi Tsutsui tsutsui@NetBSD.org UCHIYAMA Yasushi uch@NetBSD.org Masao Uebayashi uebayasi@NetBSD.org Shuichiro URATA ur@NetBSD.org Valeriy E. Ushakov uwe@NetBSD.org Todd Vierling tv@NetBSD.org Aymeric Vincent aymeric@NetBSD.org Paul Vixie vixie@NetBSD.org Mike M. Volokhov mishka@NetBSD.org Krister Walfridsson kristerw@NetBSD.org Lex Wennmacher wennmach@NetBSD.org Leo Weppelman leo@NetBSD.org Assar Westerlund assar@NetBSD.org Todd Whitesel toddpw@NetBSD.org Nathan Williams nathanw@NetBSD.org Rob Windsor windsor@NetBSD.org Dan Winship danw@NetBSD.org Jim Wise jwise@NetBSD.org Michael Wolfson mbw@NetBSD.org Steve Woodford scw@NetBSD.org Colin Wood ender@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Yuji Yamano yyamano@NetBSD.org Reinoud Zandijk reinoud@NetBSD.org S.P.Zeidler spz@NetBSD.org Maria Zevenhoven maria7@NetBSD.org Christos Zoulas christos@NetBSD.org Other contributors: Dave Burgess burgess@cynjut.infonet.net Brian R. Gaeke brg@dgate.org Brad Grantham grantham@tenon.com Lawrence Kesteloot kesteloo@cs.unc.edu Waldi Ravens waldi@moacs.indiv.nl.net Legal Mumbo-Jumbo All product names mentioned herein are trademarks or registered trademarks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the NetBSD Founda- tion. This product includes software developed by The NetBSD Founda- tion, Inc. and its contributors. This product includes software developed for the NetBSD Project. See http://www.netbsd.org/ for information about NetBSD. This product contains software developed by Ignatios Souvatzis for the NetBSD project. This product contains software written by Ignatios Souvatzis and Michael L. Hitch for the NetBSD project. This product contains software written by Michael L. Hitch for the NetBSD project. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) This product includes cryptographic software written by Eric Young (eay@mincom.oz.au) This product includes software designed by William Allen Simp- son. This product includes software developed at Ludd, University of Lulea, Sweden and its contributors. This product includes software developed at Ludd, University of Lulea. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by David Jones and Gordon Ross This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch This product includes software developed by Internet Research Institute, Inc. This product includes software developed by Leo Weppelman and Waldi Ravens. This product includes software developed by Mika Kortelainen This product includes software developed by Aaron Brown and Harvard University. This product includes software developed by Adam Ciarcinski for the NetBSD project. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Advanced Risc Machines Ltd. This product includes software developed by Alex Zepeda, and Colin Wood for the NetBSD Projet. This product includes software developed by Alex Zepeda. This product includes software developed by Alistair G. Crooks. This product includes software developed by Alistair G. Crooks. for the NetBSD project. This product includes software developed by Allen Briggs This product includes software developed by Amancio Hasty and Roger Hardiman This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Bodo Moeller. (If available, substitute umlauted o for oe) This product includes software developed by Boris Popov. This product includes software developed by Brad Pepers This product includes software developed by Bradley A. Grantham. This product includes software developed by Brini. This product includes software developed by Causality Limited. This product includes software developed by Charles D. Cranor and Seth Widoff. This product includes software developed by Charles D. Cranor and Washington University. This product includes software developed by Charles D. Cranor, Washington University, and the University of California, Berke- ley and its contributors. This product includes software developed by Charles D. Cranor, Washington University, the University of California, Berkeley and its contributors. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the Univer- sity of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles M. Hannum. This product includes software developed by Christian E. Hopps, Ezra Story, Kari Mettinen, Markus Wild, Lutz Vieweg and Michael Teske. This product includes software developed by Christian E. Hopps. This product includes software developed by Christian Limpach This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by Chuck Silvers. This product includes software developed by Colin Wood for the NetBSD Project. This product includes software developed by Colin Wood. This product includes software developed by Cybernet Corpora- tion and Nan Yang Computer Services Limited This product includes software developed by Daishi Kato This product includes software developed by Dale Rahn. This product includes software developed by Daniel Widenfalk and Michael L. Hitch. This product includes software developed by Daniel Widenfalk for the NetBSD Project. This product includes software developed by Darrin B. Jewell This product includes software developed by David Miller. This product includes software developed by Dean Huxley. This product includes software developed by Eduardo Horvath. This product includes software developed by Eric S. Hvozda. This product includes software developed by Eric S. Raymond This product includes software developed by Eric Young (eay@@mincom.oz.au) This product includes software developed by Eric Young (eay@cryptsoft.com) This product includes software developed by Eric Young (eay@mincom.oz.au) This product includes software developed by Ezra Story and by Kari Mettinen. This product includes software developed by Ezra Story, by Kari Mettinen and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, Michael Teske and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, and Michael Teske. This product includes software developed by Ezra Story. This product includes software developed by Frank van der Lin- den for the NetBSD Project. This product includes software developed by Gardner Buchanan. This product includes software developed by Gary Thomas. This product includes software developed by Gordon Ross This product includes software developed by Gordon W. Ross This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Harvard University and its contributors. This product includes software developed by Harvard University. This product includes software developed by Herb Peyerl. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert This product includes software developed by Ian F. Darwin and others. This product includes software developed by Ian W. Dall. This product includes software developed by Ichiro FUKUHARA. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by James R. Maynard III. This product includes software developed by Jared D. McNeill. This product includes software developed by Jason L. Wright This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/ This product includes software developed by Joachim Koenig- Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by Joerg Wunsch This product includes software developed by John Birrell. This product includes software developed by John P. Wittkoski. This product includes software developed by John Polstra. This product includes software developed by Jonathan R. Stone for the NetBSD Project. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Jukka Marin. This product includes software developed by Julian Highfield. This product includes software developed by Kazuhisa Shimizu. This product includes software developed by Kazuki Sakamoto. This product includes software developed by Kenneth Stailey. This product includes software developed by Kiyoshi Ikehara. This product includes software developed by Klaus Burkert,by Bernd Ernesti, by Michael van Elst, and by the University of California, Berkeley and its contributors. This product includes software developed by LAN Media Corpora- tion and its contributors. This product includes software developed by Leo Weppelman for the NetBSD Project. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Luke Mewburn. This product includes software developed by Lutz Vieweg. This product includes software developed by MINOURA Makoto, Takuya Harakawa. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Marcus Comstedt. This product includes software developed by Mark Brinicombe for the NetBSD project. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Murray This product includes software developed by Mark Tinguely and Jim Lowe This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Masanobu Saitoh. This product includes software developed by Masaru Oki. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matt DeBergalis This product includes software developed by Matthew Fredette. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Michael Graff. This product includes software developed by Michael L. Hitch. This product includes software developed by Michael Shalayeff. This product includes software developed by Michael Smith. This product includes software developed by Mike Glover and contributors. This product includes software developed by Mike Pritchard. This product includes software developed by Minoura Makoto. This product includes software developed by Nan Yang Computer Services Limited. This product includes software developed by Niels Provos. This product includes software developed by Niklas Hallqvist, Brandon Creighton and Job de Haas. This product includes software developed by Niklas Hallqvist. This product includes software developed by Onno van der Lin- den. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Per Fogelstrom This product includes software developed by Peter Galbavy. This product includes software developed by Phase One, Inc. This product includes software developed by Philip A. Nelson. This product includes software developed by Philip L. Budne. This product includes software developed by RiscBSD. This product includes software developed by Roar Thronaes. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roger Hardiman This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Ross Harvey for the NetBSD Project. This product includes software developed by Ross Harvey. This product includes software developed by Scott Bartram. This product includes software developed by Scott Stevens. This product includes software developed by Shingo WATANABE. This product includes software developed by Softweyr LLC, the University of California, Berkeley, and its contributors. This product includes software developed by Soren S. Jorvang. This product includes software developed by Stephan Thesing. This product includes software developed by Steve Woodford. This product includes software developed by Takashi Hamada This product includes software developed by Takumi Nakamura. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lam- bert. This product includes software developed by Tetsuya Isaki. This product includes software developed by Thomas Gerner This product includes software developed by Thomas Klausner for the NetBSD Project. This product includes software developed by Tobias Weingartner. This product includes software developed by Todd C. Miller. This product includes software developed by Tohru Nishimura and Reinoud Zandijk for the NetBSD Project. This product includes software developed by Tohru Nishimura for the NetBSD Project. This product includes software developed by Tohru Nishimura. for the NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software developed by Toru Nishimura. This product includes software developed by Trimble Navigation, Ltd. This product includes software developed by WIDE Project and its contributors. This product includes software developed by Waldi Ravens. This product includes software developed by Wasabi Systems for Zembu Labs, Inc. http://www.zembu.com/ This product includes software developed by Winning Strategies, Inc. This product includes software developed by Wolfgang Solfrank. This product includes software developed by Yasushi Yamasaki This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Alice Group. This product includes software developed by the Center for Software Science at the University of Utah. This product includes software developed by the Charles D. Cra- nor, Washington University, University of California, Berkeley and its contributors. This product includes software developed by the Computer Sys- tems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the David Muir Sharnoff. This product includes software developed by the Harvard Univer- sity and its contributors. This product includes software developed by the Kungliga Tekniska Hogskolan and its contributors. This product includes software developed by the Network Research Group at Lawrence Berkeley Laboratory. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/) his product includes software developed by the PocketBSD project and its contributors. This product includes software developed by the RiscBSD kernel team This product includes software developed by the RiscBSD team. This product includes software developed by the SMCC Technology Development Group at Sun Microsystems, Inc. This product includes software developed by the University of California, Berkeley and its contributors, as well as the Trustees of Columbia University. This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its contributors. This product includes software developed by the University of California, Lawrence Berkeley Laboratory. This product includes software developed by the University of Illinois at Urbana and their contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed for the FreeBSD project This product includes software developed for the NetBSD Project by Bernd Ernesti. This product includes software developed for the NetBSD Project by Christopher G. Demetriou. This product includes software developed for the NetBSD Project by Christos Zoulas This product includes software developed for the NetBSD Project by Emmanuel Dreyfus. This product includes software developed for the NetBSD Project by Frank van der Linden This product includes software developed for the NetBSD Project by Ignatios Souvatzis. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Michael L. Hitch. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Scott Bartram and Frank van der Linden This product includes software developed for the NetBSD Project by Allegro Networks, Inc., and Wasabi Systems, Inc. This product includes software developed for the NetBSD Project by Genetec Corporation. This product includes software developed for the NetBSD Project by Jonathan Stone. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by SUNET, Swedish University Computer Network. This product includes software developed for the NetBSD Project by Shigeyuki Fukushima. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed under OpenBSD by Per Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA. This product includes software developed under OpenBSD by Per Fogelstrom. This software is a component of "386BSD" developed by William F. Jolitz, TeleMuse. This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Similar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD", "FreeBSD", "Mach" (by CMU). This software includes software developed by the Computer Sys- tems Laboratory at the University of Utah. This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/). This product includes software developed at Ludd, University of Lule}, Sweden and its contributors. The End NetBSD August 22, 2004 NetBSD