INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL - Installation procedure for NetBSD/hp300. DESCRIPTION About this Document This document describes the installation procedure for NetBSD 1.5 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 thirty-one different system architectures featuring twelve dis- tinct families of CPUs, and is being ported to more. The NetBSD 1.5 re- lease contains complete binary releases for fifteen different machine types. (The sixteen remaining are not fully supported at this time and are thus not part of the binary distribution. 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 portable, 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 Since The Last Release The NetBSD 1.5 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many userland enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over one year of development that went into the NetBSD 1.5 release. Some highlights include: Kernel o Ports to new platforms including: arc, cobalt, hpcmips, news68k, sgimips, and sparc64. o Improved performance and stability of the UVM virtual memory subsys- tem. o Implementation of generic kernel locking code, as well as a restruc- ture and re-tuning of the scheduler, to be used by the future symmet- ric multi-processing (SMP) implementation. o Improved compatibility support for Linux, OSF1, and SVR4 programs. o New compatibility support for Win32 programs. o Support for dynamically loaded ELF kernel modules. o Kernel process tracing using ktruss(1). o Deletion of swap devices using swapctl(8). o Easier hot-pluggability of keyboards and mice using a new wscons de- vice - wsmux. o Improved PCMCIA and Cardbus support, including support for detaching of devices and cards, resulting in better support for notebooks and PDA devices. o Numerous hardware improvements, including areas such as: audio, UD- MA/66 support for ATA drives, USB, and wireless networking. Networking o Addition of IP version 6 (IPv6) and IPsec to the networking stack, from the KAME project. This includes addition of kernel code for IPv6/IPsec, IPv4/v6 dual-stack user applications and supporting li- braries. Due to this, the shlib major version for pcap(3) is incre- mented and you may need to recompile userland tools. The KAME IPv6 part includes results from the unified-ipv6 effort. File system o Significant Fast file system (FFS) performance enhancements via inte- gration of Kirk McKusick's soft updates and trickle sync code. o Support for the Windows NT `NTFS' file system (read-only at this stage). o Support for revision 1 of the Linux `ext2fs' file system. o Enhanced stability and usability of LFS (the BSD log-structured file system). o Various RAIDframe enhancements including: auto-detection of RAID com- ponents and auto-configuration of RAID sets, and the ability to con- figure the root file system (/) on a RAID set. o Support for Microsoft Joliet extensions to the ISO9660 CD file sys- tem. o Improved file system vnode locking mechanisms, thus resolving a source of several panics in the past. o Support for NFS and RPC over IPv6. o Server part of NFS locking (implemented by rpc.lockd(8)) now works. Security o Strong cryptographic libraries and applications integrated, including the AES cipher Rijndael, the OpenSSL library, more complete Kerberos IV and Kerberos V support, and an SSH server and client. o sysctl(3) interfaces to various elements of process and system infor- mation, allowing programs such as ps(1), dmesg(1) and the like to op- erate without recompilation after kernel upgrades, and remove the ne- cessity to run setgid kmem (thus improving system security). o Disable various services by default, and set the default options for disabled daemons to a higher level of logging. o Several code audits were performed. One audit replaced string rou- tines that were used without bound checking, and another one to iden- tify and disable places where format strings were used in an unsafe way, allowing arbitrary data entered by (possibly) malicious users to overwrite application code, and leading from Denial of Service at- tacks to compromised system. System administration and user tools o Conversion of the rc(8) system startup and shutdown scripts to an `rc.d' mechanism, with separate control scripts for each service, and appropriate dependency ordering provided by rcorder(8). o postfix(1) provided as alternative mail transport agent to sendmail(8). o User management tools useradd(8), usermod(8), userdel(8), groupadd(8), groupmod(8), and groupdel(8) added to the system. o Incorporation of a login class capability database (/etc/login.conf) from BSD/OS. o Improved support for usernames longer than eight characters in pro- grams such as at(1) and w(1). o Many enhancements to ftpd(8) providing features found in larger and less secure FTP daemons, such as user classes, connection limits, im- proved support for virtual hosting, transfer statistics, transfer rate throttling, and support for various IETF ftpext working group extensions. o The ftp(1) client has been improved even further, including transfer rate throttling, improved URL support, command line uploads. See the man page for details. Miscellaneous o Updates to the NetBSD source code style code (located in /usr/share/misc/style) to use ANSI C only (instead of K&R) and re- flect current (best) practice, and begin migrating the NetBSD source code to follow it. o Implementation of many SUSv2 features to the curses(3) library, in- cluding support for color. o Updates of most third party packages that are shipped in the base system, including file(1), ipfilter(4), ppp(4), and sendmail(8) to the latest stable release. o Many new packages in the pkgsrc system, including standard desktops like KDE and GNOME as well as latest Tcl/Tk and perl and many of the components of the Java Enterprise platform. The package framework itself now has full wildcard dependency support. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. This is the sixth major release of NetBSD for the HP 9000/300 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 ac- tivities. 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 us- ability 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/Sites/net.html. NetBSD 1.5 Release Contents The root directory of the NetBSD 1.5 release is organized as follows: .../NetBSD-1.5/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.5 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 di- rectory per architecture, for each of the architectures for which NetBSD 1.5 has a binary distribution. There are also README.export- control files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution that may be subject to export regulations of the United States, e.g. code under src/crypto and src/sys/crypto. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. 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. 22.3 MB gzipped, 98.8 MB uncompressed pkgsrc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. 5.6 MB gzipped, 57.0 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. 3.3 MB gzipped, 13.2 MB uncompressed src This set contains all of the base NetBSD 1.5 sources which are not in gnusrc, sharesrc, or syssrc. 24.2 MB gzipped, 120.6 MB uncompressed syssrc This set contains the sources to the NetBSD 1.5 kernel for all architectures, config(8), and dbsym(8). 17.6 MB gzipped, 88.6 MB uncompressed xsrc This set contains the sources to the X Window System. 35.2 MB gzipped, 176.8 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. They may be un- packed into /usr/src with the command: # ( cd / ; tar -zxpf - ) < set_name.tgz The sets/Split/ subdirectory contains split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are named set_name.xx where set_name is the distribution set name, and xx is the sequence number of the file, starting with ``aa'' for the first file in the distribution set, then ``ab'' for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distri- bution set.) The split distributions may be reassembled and extracted with cat as fol- lows: # cat set_name.?? | ( cd / ; tar -zxpf - ) 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 di- rectory, 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 AT&T 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 1.5 release is found in the hp300 subdirectory of the distribution: .../NetBSD-1.5/hp300/ 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. sets/ hp300 binary distribution sets; see below. installation/ floppy/ hp300 boot and installation floppies; see be- low. miniroot/ hp300 miniroot file system image; see below. misc/ Miscellaneous hp300 installation utilities; see installation section, below. Binary distribution sets The NetBSD hp300 binary distribution sets contain the binaries which com- prise the NetBSD 1.5 release for the hp300. There are eight binary dis- tribution sets. The binary distribution sets can be found in the hp300/binary/sets subdirectory of the NetBSD 1.5 distribution tree, and are as follows: base The NetBSD 1.5 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 minimally func- tional. It includes shared library support, and excludes every- thing described below. 15.7 MB gzipped, 41.5 MB uncompressed comp Things needed for compiling programs. This set includes the system include files (/usr/include) and the various system li- braries (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. 11.8 MB gzipped, 39.5 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. (If you are upgrading, it's recommended that you get a copy of this set and carefully upgrade your configuration files by hand.) 0.1 MB gzipped, 0.6 MB uncompressed games This set includes the games and their manual pages. 3.0 MB gzipped, 7.4 MB uncompressed kern This set contains a NetBSD/hp300 1.5 GENERIC kernel, named /netbsd. You must install this distribution set. 0.7 MB gzipped, 1.6 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. 5.0 MB gzipped, 19.9 MB uncompressed misc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share. 2.6 MB gzipped, 10.1 MB uncompressed text This set includes NetBSD 's text processing tools, including groff(1), all related programs, and their manual pages. 1.3 MB gzipped, 4.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 3.3.6. 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. 2.6 MB gzipped, 8.2 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 1.7 MB gzipped, 7.2 MB uncompressed xcontrib Programs that were contributed to X. 0.2 MB gzipped, 0.7 MB uncompressed xfont Fonts needed by X. 6.2 MB gzipped, 7.5 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 files are /-relative and therefore are extracted below the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xpf command from /. The following are included in the hp300/installation directory: miniroot/ miniroot.fs.gz A copy of the miniroot file system. 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 in- stallation program. 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. rbootd.tgz Source code for the rbootd program included with NetBSD. It requires that the server has a Berkeley Packet Filter (bpf). You will need to compile this version of rbootd if server system does not have this utility already. The following are included in the hp300/binary/kernel directory: netbsd.gdb.gz A gzipped GENERIC kernel with debugging symbols. netbsd.gz A gzipped GENERIC kernel. 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 1.5 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. Here is a table of recommended HD 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 Anything else is up to you! Note: The hp300 installation procedure uses a miniroot file system which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image. Supported hardware o CPUs - 68020-based: 318, 319, 320, 330, and 350. - 68030-based: 340, 345, 360, 370, 375, and 400 [1]. - 68040-based: 380, 425 [1], and 433 [1]. o Disks - HP-IB/CS80: 7912, 7914, 7933, 7936, 7937, 7945, 7957, 7958, 7959, 2200, and 2203. - SCSI-I [2], including magneto-optical and CD-ROM. o Tape drives - Low-density HP-IB/CS80 cartridge: 7914, 7946, and 9144. - High-density HP-IB/CS80 cartridge: 9145. - HP-IB/CS80 1/2": 7974A, 7978A/B, 7979A, 7980A, and 7980XC. - SCSI: HP DAT, Exabyte, and SCSI QIC drives such as the Archive Viper. o RS232 interfaces - 98644 built-in single port (dca). - 98642 4-port (dcm). - 98638 8-port (dcm). o Network interfaces - 98643 built-in and add-on LAN cards. o Displays - 98544, 98545, and 98547 color and monochrome Topcat. - 98548, 98549, and 98550 color and monochrome Catseye. - 98700 and 98710 Gatorbox. - 98720 and 98721 Renaissance. - 98730 and 98731 DaVinci. - A1096A monochrome Hyperion. o Input devices - General interface supporting all HIL devices: keyboard, 2 and 3 button mice [3], and ID module. o Miscellaneous - Battery-backed real-time clock. - 98624 built-in HP-IB interface. - 98625A and 98625B `fast' HP-IB interface. - 98658A built-in and add-on SCSI interface. - Printers and plotters on RS232 and HP-IB. - SCSI autochanger. [1] 400-series machines configured for Domain/OS are not fully supported. Notably, the keyboard doesn't work and the ROMs must be in ``HP-UX mode''. [2] SCSI-II drives are known to work, though this may require changing a jumper on some drives. See your disk's documenta- tion for details. [3] Serial mice connected to a `HIL to quad' converter are also known to work. If it's not on this list, there is no official support for it in this re- lease. Getting the NetBSD System on to Useful Media Installation is supported from several media types, including: o FTP o NFS o Tape The steps necessary to prepare the distribution sets for installation de- pend on which method of installation you choose. The various methods are explained below. FTP It is possible, using the install and upgrade programs in the mini- root, to extract the binary sets directly onto disk from an FTP server. This is by far the easiest installation method, as you may specify to have all sets extracted at once, providing that they are located in the same directory on the server. All that is required in this case is that you have network access to an FTP server. This may be your account on another system, or may even be ftp.netbsd.org itself. If you wish to use ftp.netb- sd.org as your FTP file server, you may want to keep the following information handy: IP Address: ftp.netbsd.org Login: anonymous Password: Server path: /pub/NetBSD/NetBSD-1.5/hp300/binary/sets Note: If you're not using a nameserver during installation, you might find 204.152.184.75 handy; it's the IP address of ftp.netbsd.org as of October, 2000. NFS SYS_INST currently requires an NFS server from which to copy the miniroot. o This file system must be exported with root permissions, but may be exported read-only. o The miniroot image must reside in the `root' of the mounted file system. For example, if the client system mounts server:/u, then the miniroot image must reside in /u on the server. This is due to limitations in the file lookup code used in SYS_INST, and may be fixed in a future release. o If you also wish to install the binary sets from the NFS serv- er, place them in a properly exported file system on the serv- er. Note that these files do not suffer from the same placement restrictions as the miniroot. Tape If you wish to load SYS_INST from tape, it must appear on the tape before any other files. To copy this onto tape, use a command like the following: dd if=SYS_INST of= obs=20b conv=osync Note that not all HP BOOTROMs support booting from SCSI tapes. Copying the miniroot to disk from tape is not currently supported. However, it is planned for a future release. If you wish to extract binary sets onto your disk from tape, you must first place them on the tape. The easiest way to do this is with the dd(1) command. Make sure you use a `no-rewind-on-close' tape device. For example: # for file in base.tgz etc.tgz; do dd if=${file} of=/dev/nrst0 # done Note that depending on your tape drive, you may need to explicitly set the EOF marker at the end of each file. It may also be neces- sary to use the conv=osync argument to dd(1). Note that this argu- ment is incompatible with the bs= argument. Consult the tape-relat- ed manual pages on the system where the tapes are created for more details. Preparing your System for NetBSD installation Currently, only installing the miniroot from the network is supported. This may change in a future release. You will need information about your disk's geometry, based on 512-byte sectors. You must have this information before proceeding. The file .../installation/misc/HP-IB.geometry has geometry inforomation for sever- al 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 sectors. 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 `a' partition one cylinder from the begin- ning of the disk. Later, the `c' partition will be marked with the type FS_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'.) 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) + slave Controllers are numbered 0, 1, ... starting with the lowest select code. SCSI controllers and HP-IB controllers are counted separately. Therefore, 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 numers might be something like the following: Location Unit HP-IB at 7, slave 2 2 (disk: rd2) HP-IB at 14, slave 5 13 (disk: rd13) SCSI at 16, slave 0 0 (disk: sd0) Miniroot installation via network Note: Booting sys_inst via the network on early hp300 models is only possible if your bootrom is rev. c or later. When checking the revision of your BOOTROM, use what it printed on the console dur- ing the self-test, not what may be printed on a sticker on the chip itself. In order to complete this process, you will need the following from the .../installation/misc directory of the distribution: SYS_INST.gz The standalone disklabel and miniroot installation tool. This file must be un-gzipped before using. And you will need the following from the .../installation/miniroot direc- tory of of the distribution: miniroot.fs.gz A miniroot file system image. To boot SYS_INST via the network, you will need a system capable of han- dling boot requests for an HP workstation. If you will use this method, see the special note below. To boot SYS_INST from tape, you need only place SYS_INST on the tape as the first file. Loading SYS_INST via the network If you wish to load the SYS_INST program via the network, you may need the following from the .../installation/misc directory in addition to the items listed above: rbootd.tgz Source code for the rbootd program included with NetBSD. It requires that the server has a Berkeley Packet Filter (bpf). You will need to compile this version of rbootd if your serv- er system does not have this utility already. First of all, configure your rbootd to handle boot requests from the client. Note: NetBSD 's rbootd is slightly different from HP-UX's. To configure NetBSD 's rbootd, create a file called /etc/rbootd.conf and place in it an entry like the following: 08:00:09:04:AA:33 SYS_INST # thunder-egg The first column is the ethernet address of the client's network interface. The second column is the program to send to the client, and anything after the `#' is a comment. Once you have rbootd running, copy the SYS_INST program to the /usr/mdec/rbootd directory on your server. If this directory doesn't exist already, you will need to create it. For information on configuring rbootd under HP-UX, see the rbootd(1M) manual page on your server system. Once rbootd is configured and running, you will be ready to continue. Make sure that the miniroot file system image has been un-gzipped, and that it resides in a file system what is exported to the client. See the manual pages on your server system if you need more information about ex- porting file systems. You are now ready to SYS_INST. During the client's self-test cycle, press SPACE a few times. Shortly, you should see a menu of possible boot op- tions appear. Select the option corresponding to SYS_INST. SYS_INST will load and prompt you for a command. If this is a new NetBSD installation, 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 allocate at least 6 MB for the `b' partition, or else the miniroot will not fit. 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 necessary, 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. The next step is to copy the miniroot image onto the target disk. sys_inst> miniroot You will be prompted for the target disk and the source of the miniroot filesytem image. Enter the filename of the miniroot image. Note that this file must reside in the server directory being mounted. Next you will be asked for the client's IP address, netmask, and default router, the server's IP ad- dress, and the directory on the server to mount. Once you have entered this information, SYS_INST will attempt to mount the NFS server and begin copying the miniroot file system to the `b' partition of the target disk. Is is worth noting that this copy may take a while. It might be worth grabbing a cup of coffee at this point. Once the miniroot file system image has been copied onto the target disk, you may boot from the miniroot file system. sys_inst> boot Enter the disk from which to boot. The kernel in the miniroot file system will be booted into single-user mode. 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. Additional improve- ments are planned for future releases. 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. If the disk is the boot disk, you must offset the root partition (/) (`a') one cylinder, as the hp300 boot code if large enough to spill past the label area. In this case, the `c' partition must be fstype boot. 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 man- ually edit the resulting /etc/fstab. 5. Extract binary sets from the media of your choice. 6. Copy configuration information gathered during the installation pro- cess 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 in- stallation 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, 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-write. When the sys- tem asks you to choose a shell, simply press RETURN to get to a prompt. If you are asked for a terminal type, respond with hp300h for a local console, or whatever is appropriate for your serial con- sole. and press RETURN. At this point, you need to configure at least one file in the /etc directory. 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 documenta- tion 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 en- vironment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your 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. Other files in /etc that may require modification or setting up in- clude /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. There is no initial password, but if you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. 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 useradd(8) for more information on how to add a new user to the system. 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. 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 in- stallation (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 browsable listing of available packages 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/ o Package sources for compiling packages can be obtained by re- trieving the file ftp://ftp.netbsd.org/pub/NetBSD/NetBSD- current/tar_files/pkgsrc.tar.gz They are typically extracted into /usr/pkgsrc (though other lo- cations work fine), as with the command: # mkdir /usr/pkgsrc; tar -C /usr/pkgsrc -zxpf pkgsrc.tar.gz After extracting, then see the README file in the extraction di- rectory (e.g. /usr/pkgsrc/README) for more information. 6. Misc o Edit /etc/mail/aliases to forward root mail to the right place (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. 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 manu- al; 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. 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. 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 1.5executables. 7. Install a new boot block. 8. Check your file systems for integrity. While using the miniroot's upgrade program is the preferred method of up- grading 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 1.5 kernel may be incompatible with your old binaries. 2. Back up your pre-existing kernel and copy the 1.5 kernel into your root partition (/). 3. Reboot with the 1.5 kernel into single-user mode. 4. Check all file systems: # /sbin/fsck -pf 5. Mount all local file systems: # /sbin/mount -a -t nonfs 6. 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 en- able the network: # sh /etc/rc.d/network start 7. Make sure you are in the root file system (/) and extract the base binary set: # cd / # pax -zrvpe -f /path/to/base.tgz 8. Install a new boot block: # cd /usr/mdec # disklabel -B root-disk E.g.: root-disk could be sd0. 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 1.5. General issues o /etc/rc modified to use /etc/rc.d/* In previous releases of NetBSD, /etc/rc was a traditional BSD style monolithic file. As of NetBSD 1.5, each discrete program or substem from /etc/rc and /etc/netstart has been moved into separate scripts in /etc/rc.d/. At system startup, /etc/rc uses rcorder(8) to build a dependency list of the files in /etc/rc.d and then executes each script in turn with an argument of `start'. Many rc.d scripts won't start unless the ap- propriate rc.conf(5) entry in /etc/rc.conf is set to `YES.' At system shutdown, /etc/rc.shutdown uses rcorder(8) to build a de- pendency list of the files in /etc/rc.d that have a ``KEYWORD: shutdown'' line, reverses the resulting list, and then executes each script in turn with an argument of `stop'. The following scripts support a specific shutdown method: cron, inetd, local, and xdm. Local and third-party scripts may be installed into /etc/rc.d as nec- essary. Refer to the other scripts in that directory and rc(8) for more information on implementing rc.d scripts. Issues affecting an upgrading from NetBSD 1.4 or later o named(8) leaks version information Previous releases of NetBSD disabled a feature of named(8) where the version number of the server could be determined by remote clients. This feature has not been disabled in NetBSD 1.5, because there is a named.conf(5) option to change the version string: option { version "newstring"; }; o sysctl(8) pathname changed sysctl(8) is moved from /usr/sbin/sysctl to /sbin/sysctl. If you have hardcoded references to the full pathname (in shell scripts, for example) please be sure to update those. o sendmail(8) configuration file pathname changed Due to sendmail(8) upgrade from 8.9.x to 8.10.x, /etc/sendmail.cf is moved to /etc/mail/sendmail.cf. Also, the default sendmail.cf(5) refers different pathnames than before. For example, /etc/aliases is now located at /etc/mail/aliases, /etc/sendmail.cw is now called /etc/mail/local-host-names, and so forth. If you have customized sendmail.cf(5) and friends, you will need to move the files to the new locations. See /usr/share/sendmail/README for more information. Using online NetBSD documentation Documentation is available if you first install the manual distribution set. Traditionally, the ``man pages'' (documentation) are denoted by `name(section)'. Some examples of this are o intro(1), o man(1), o apropros(1), o passwd(1), and o passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The man command is used to view the documentation on a topic, and is started by entering man [section] topic. The brackets [] around the sec- tion should not be entered, but rather indicate that the section is op- tional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after log- ging in, enter # man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter # man 5 passwd instead. If you are unsure of what man page you are looking for, enter apropos subject-word where subject-word is your topic of interest; a list of possibly related man pages will be displayed. 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 mailing list server, send mail to that address with an empty body, and it will reply with instruc- tions. There are various mailing lists set up to deal with comments and ques- tions 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 in- clude 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 be- low). 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 o The former members of UCB's Computer Systems Research Group, includ- ing (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. o Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. o UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. o Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers. o Redback Networks, Inc. for hosting the NetBSD mail and GNATS server. o The Helsinki University of Technology in Finland for hosting the NetBSD CVS server. o The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. o The many organisations that provide NetBSD mirror sites. o Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. o Dave Burgess burgess@cynjut.infonet.net has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. o The following individuals and organizations (each in alphabetical or- der) have made donations or loans of hardware and/or money, to sup- port NetBSD development, and deserve credit for it: Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Soren Jorvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd. (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.) o Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 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: Alistair Crooks agc@netbsd.org Jun-ichiro itojun Hagino itojun@netbsd.org Frank van der Linden fvdl@netbsd.org Luke Mewburn lukem@netbsd.org Christos Zoulas christos@netbsd.org The portmasters (and their ports): Mark Brinicombe mark@netbsd.org arm32 Jeremy Cooper jeremy@netbsd.org sun3x Ross Harvey ross@netbsd.org alpha Jun-ichiro itojun Hagino itojun@netbsd.org sh3 Ben Harris bjh21@netbsd.org arm26 Eduardo Horvath eeh@netbsd.org sparc64 Darrin Jewell dbj@netbsd.org next68k Soren Jorvang soren@netbsd.org cobalt Soren Jorvang soren@netbsd.org sgimips Wayne Knowles wdk@netbsd.org mipsco Paul Kranenburg pk@netbsd.org sparc Anders Magnusson ragge@netbsd.org vax Minoura Makoto minoura@netbsd.org x68k Phil Nelson phil@netbsd.org pc532 Tohru Nishimura nisimura@netbsd.org luna68k NONAKA Kimihiro nonaka@netbsd.org prep Scott Reynolds scottr@netbsd.org mac68k Kazuki Sakamoto sakamoto@netbsd.org bebox Noriyuki Soda soda@netbsd.org arc Wolfgang Solfrank ws@netbsd.org ofppc Ignatios Souvatzis is@netbsd.org amiga Jonathan Stone jonathan@netbsd.org pmax Shin Takemura takemura@netbsd.org hpcmips Jason Thorpe thorpej@netbsd.org alpha Jason Thorpe thorpej@netbsd.org hp300 Tsubai Masanari tsubai@netbsd.org macppc Tsubai Masanari tsubai@netbsd.org newsmips Izumi Tsutsui tsutsui@netbsd.org news68k Frank van der Linden fvdl@netbsd.org i386 Leo Weppelman leo@netbsd.org atari Nathan Williams nathanw@netbsd.org sun3 Steve Woodford scw@netbsd.org mvme68k The NetBSD 1.5 Release Engineering team: Chris G. Demetriou cgd@netbsd.org Havard Eidnes he@netbsd.org Ted Lemon mellon@netbsd.org John Hawkinson jhawk@netbsd.org Perry Metzger perry@netbsd.org Curt Sampson cjs@netbsd.org Jason Thorpe thorpej@netbsd.org Todd Vierling tv@netbsd.org Developers and other contributors: Steve Allen wormey@netbsd.org Julian Assange proff@netbsd.org Lennart Augustsson augustss@netbsd.org Christoph Badura bad@netbsd.org Robert V. Baron rvb@netbsd.org Erik Berls cyber@netbsd.org John Birrell jb@netbsd.org Mason Loring Bliss mason@netbsd.org Manuel Bouyer bouyer@netbsd.org John Brezak brezak@netbsd.org Allen Briggs briggs@netbsd.org Aaron Brown abrown@netbsd.org David Brownlee abs@netbsd.org Frederick Bruckman fredb@netbsd.org Jon Buller jonb@netbsd.org Simon Burge simonb@netbsd.org Dave Burgess burgess@cynjut.infonet.net Robert Byrnes byrnes@netbsd.org D'Arcy J.M. Cain darcy@netbsd.org Dave Carrel carrel@netbsd.org James Chacon jmc@netbsd.org Bill Coldwell billc@netbsd.org Julian Coleman jdc@netbsd.org Chuck Cranor chuck@netbsd.org Aidan Cully aidan@netbsd.org Johan Danielsson joda@netbsd.org Matt DeBergalis deberg@netbsd.org Rob Deker deker@netbsd.org Chris G. Demetriou cgd@netbsd.org Jaromir Dolecek jdolecek@netbsd.org Andy Doran ad@netbsd.org Roland Dowdeswell elric@netbsd.org Matthias Drochner drochner@netbsd.org Jun Ebihara jun@netbsd.org Havard Eidnes he@netbsd.org Enami Tsugutomo enami@netbsd.org Bernd Ernesti veego@netbsd.org Erik Fair fair@netbsd.org Hubert Feyrer hubertf@netbsd.org Thorsten Frueauf frueauf@netbsd.org Castor Fu castor@netbsd.org Ichiro Fukuhara ichiro@netbsd.org Brian R. Gaeke brg@dgate.org Thomas Gerner thomas@netbsd.org Simon J. Gerraty sjg@netbsd.org Justin Gibbs gibbs@netbsd.org Adam Glass glass@netbsd.org Michael Graff explorer@netbsd.org Brad Grantham grantham@tenon.com Brian C. Grayson bgrayson@netbsd.org Matthew Green mrg@netbsd.org Juergen Hannken-Illjes hannken@netbsd.org Charles M. Hannum mycroft@netbsd.org Eric Haszlakiewicz erh@netbsd.org John Hawkinson jhawk@netbsd.org HAYAKAWA Koichi haya@netbsd.org Rene Hexel rh@netbsd.org Michael L. Hitch mhitch@netbsd.org Christian E. Hopps chopps@netbsd.org Ken Hornstein kenh@netbsd.org Marc Horowitz marc@netbsd.org Nick Hudson skrll@netbsd.org Martin Husemann martin@netbsd.org Dean Huxley dean@netbsd.org Bernardo Innocenti bernie@netbsd.org ITOH Yasufumi itohy@netbsd.org IWAMOTO Toshihiro toshii@netbsd.org Matthew Jacob mjacob@netbsd.org Lonhyn T. Jasinskyj lonhyn@netbsd.org Chris Jones cjones@netbsd.org Takahiro Kambe taca@netbsd.org Antti Kantee pooka@netbsd.org Lawrence Kesteloot kesteloo@cs.unc.edu Thomas Klausner wiz@netbsd.org Klaus Klein kleink@netbsd.org Wayne Knowles wdk@netbsd.org John Kohl jtk@netbsd.org Kevin Lahey kml@netbsd.org Johnny C. Lam jlam@netbsd.org Martin J. Laubach mjl@netbsd.org Ted Lemon mellon@netbsd.org Joel Lindholm joel@netbsd.org Mike Long mikel@netbsd.org Warner Losh imp@netbsd.org Federico Lupi federico@netbsd.org Brett Lymn blymn@netbsd.org Paul Mackerras paulus@netbsd.org David Maxwell david@netbsd.org Dan McMahill dmcmahill@netbsd.org Gregory McGarry gmcgarry@netbsd.org Neil J. McRae neil@netbsd.org Perry Metzger perry@netbsd.org der Mouse mouse@netbsd.org Joseph Myers jsm@netbsd.org Ken Nakata kenn@netbsd.org Bob Nestor rnestor@netbsd.org NONAKA Kimihiro nonaka@netbsd.org Masaru Oki oki@netbsd.org Atsushi Onoe onoe@netbsd.org Greg Oster oster@netbsd.org Herb Peyerl hpeyerl@netbsd.org Matthias Pfaller matthias@netbsd.org Dante Profeta dante@netbsd.org Chris Provenzano proven@netbsd.org Waldi Ravens waldi@moacs.indiv.nl.net Darren Reed darrenr@netbsd.org Michael Richardson mcr@netbsd.org Tim Rightnour garbled@netbsd.org Gordon Ross gwr@netbsd.org Heiko W. Rupp hwr@netbsd.org SAITOH Masanobu msaitoh@netbsd.org Curt Sampson cjs@netbsd.org Wilfredo Sanchez wsanchez@netbsd.org Ty Sarna tsarna@netbsd.org SATO Kazumi sato@netbsd.org Matthias Scheler tron@netbsd.org Karl Schilke (rAT) rat@netbsd.org Konrad Schroder perseant@netbsd.org Reed Shadgett dent@netbsd.org Tim Shepard shep@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 Bill Sommerfeld sommerfeld@netbsd.org Bill Squier groo@netbsd.org Bill Studenmund wrstuden@netbsd.org Kevin Sullivan sullivan@netbsd.org SUNAGAWA Keiki kei@netbsd.org Kimmo Suominen kim@netbsd.org Matt Thomas matt@netbsd.org Christoph Toshok toshok@netbsd.org UCHIYAMA Yasushi uch@netbsd.org Shuichiro URATA ur@netbsd.org Todd Vierling tv@netbsd.org Aymeric Vincent aymeric@netbsd.org Paul Vixie vixie@netbsd.org Krister Walfridsson kristerw@netbsd.org Lex Wennmacher wennmach@netbsd.org Assar Westerlund assar@netbsd.org Todd Whitesel toddpw@netbsd.org Rob Windsor windsor@netbsd.org Dan Winship danw@netbsd.org Jim Wise jwise@netbsd.org Michael Wolfson mbw@netbsd.org Colin Wood ender@netbsd.org Legal Mumbo-Jumbo All product names mentioned herein are trademarks or registered trade- marks 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 Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Han- num. 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 Alistair G. Crooks. 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 Bill Paul. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity 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 by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. 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 David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch. This product includes software developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. 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 W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, 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 John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe. 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 Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael L. Hitch. This product includes software developed by Niels Provos. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by Tohru Nishimura for the NetB- SD Project. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the Computer Systems Labora- tory at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. 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 Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@min- com.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed at Ludd, University of Lule}, Sweden and its contributors. NetBSD October 29, 2000 29