INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL - Installation procedure for NetBSD/walnut. CONTENTS About this Document............................................2 Dedication.....................................................2 What is NetBSD?................................................2 Upgrade path to NetBSD 1.6.2...................................2 Changes Between The NetBSD 1.6.1 and 1.6.2 Releases............3 Kernel......................................................3 Networking..................................................4 Security....................................................4 System administration and user tools........................4 Miscellaneous...............................................4 walnut specific.............................................5 Changes Between The NetBSD 1.6 and 1.6.1 Releases..............5 Kernel......................................................5 Networking..................................................5 File system.................................................6 Security....................................................6 System administration and user tools........................6 Miscellaneous...............................................7 Changes Between The NetBSD 1.5 and 1.6 Releases................7 Kernel......................................................7 Networking..................................................8 File system.................................................8 Security....................................................9 System administration and user tools........................9 Miscellaneous...............................................9 The Future of NetBSD..........................................10 Sources of NetBSD.............................................11 NetBSD 1.6.2 Release Contents.................................11 NetBSD/walnut subdirectory structure.......................13 Binary distribution sets...................................13 NetBSD/walnut System Requirements and Supported Devices.......14 Supported devices..........................................15 Unsupported devices........................................15 Supported boot devices and media...........................15 Getting the NetBSD System on to Useful Media..................16 Preparing your System for NetBSD installation.................18 Booting over a serial line.................................18 Booting from the network...................................18 Installing the NetBSD System..................................22 Booting the installer......................................22 Example of a normal boot...................................22 Common Problems and Error Messages.........................22 Running the sysinst installation program...................22 Introduction............................................22 General.................................................22 Quick install...........................................22 Booting NetBSD..........................................23 Network configuration...................................23 Installation drive selection and parameters.............24 Partitioning the disk...................................24 Preparing your hard disk................................24 Getting the distribution sets...........................25 Installation using ftp..................................25 Installation using NFS..................................25 Installation from CD-ROM................................25 Installation from an unmounted file system..............25 Installation from a local directory.....................26 Extracting the distribution sets........................26 Finalizing your installation............................26 Post installation steps.......................................26 Upgrading a previously-installed NetBSD System................28 Compatibility Issues With Previous NetBSD Releases............28 Issues affecting an upgrade from NetBSD 1.5................29 Issues affecting an upgrade from NetBSD 1.4 or prior.......29 Using online NetBSD documentation.............................30 Administrivia.................................................31 Thanks go to..................................................31 We are........................................................33 Legal Mumbo-Jumbo.............................................38 The End.......................................................40 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 1.6.2 on the walnut 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. Dedication The NetBSD Foundation would like to dedicate the NetBSD 1.6.2 release to the memory of Erik Reid, who went missing and is presumed dead in a sail- ing accident on 18 February 2004. Erik's contributions to NetBSD includ- ed work on support for SGI MIPS R4000, integrating XFree86 Direct Render- ing Interface (DRI), and managing the build lab. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace. 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 three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD 1.6.2 release contains complete bi- nary releases for thirty eight different system architectures. (The fif- teen 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. Upgrade path to NetBSD 1.6.2 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.6.2. NetBSD 1.6.2 is an upgrade of NetBSD 1.6.1 and earlier major and patch releases of NetBSD. The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.6 was started are designated by ver- sion identifiers such as 1.6A, 1.6B, etc. These identifiers do not des- ignate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can not be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system will probably result in problems. Please also note that it is not possible to do a direct ``version'' com- parison between any of the intermediate development versions mentioned above and 1.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk. Changes Between The NetBSD 1.6.1 and 1.6.2 Releases The NetBSD 1.6.2 release provides numerous significant functional en- hancements, including support for many new devices, integration of hun- dreds of bug fixes, patches and updates to kernel subsystems, and many user-land enhancements. The result of these improvements is a stable op- erating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over nine months of development that went into the NetBSD 1.6.2 release. Some highlights include: Kernel o With pciide(4), make Promise controllers do DMA with large disks re- quiring 48-bit LBA drives. o Add error detection when running low on swap, to improve stability in low-memory situations. o Support for more SiS controllers were added to pciide(4). o Support for the new PowerBook G4 12-inch added. o mlx(4) stability improved. o Support for ICH5 added to pciide(4). o A long-standing stability problem with the original Sun4c sparc sys- tems (SS1, SS1+, and IPC) has been found and fixed. Some optimiza- tions done for these systems as well. o Sun3, Sun3x, and Sun2 may now boot from tape files, through addition of seek support for tape files. o The USERCONF option has been added to the i386 kernels; see userconf(4) for more information. o Hardware random number generator support for Intel 865 and 875P chipsets added. o Fix wdc(4) to work with pre-ATA drives. o Shared libraries and other files mapped executable now count as TEXT pages for vm-usage purposes. This should allow for more appropriate handling of these pages compared to other normal file buffer pages. o General support for multi-function pcmcia cards has been fixed. o Various fixes to linux emulation have been added. Networking o rtk(4) multicast problem fixed. o fxp(4) support yet a few more chip variants. o tulip(4) driver fixed so that the DEC Alpha PWS no longer panics. o Path MTU discovery black-hole detection has been added. o bce(4) driver added for Broadcom BCM4401 chipset, as seen in recent Dell laptops. o A workaround has been added for a race condition in the networking code which could corrupt the callout data structure. o Various networking stack fixes for IPv4, IPv6 and IPSEC. Security o NetBSD-SA2003-018 DNS negative cache poisoning o NetBSD-SA2003-017 OpenSSL multiple vulnerability o NetBSD-SA2003-016 Sendmail - another prescan() bug CAN-2003-0694 o NetBSD-SA2003-015 Remote and local vulnerabilities in XFree86 font libraries o NetBSD-SA2003-014 Insufficient argument checking in sysctl(2) o NetBSD-SA2003-012 Out of bounds memset(0) in sshd o NetBSD-SA2003-011 off-by-one error in realpath(3) o NetBSD-SA2003-010 remote panic in OSI networking code System administration and user tools o Possible crash in vi(1) triggered by an error was fixed. o XFree86 upgraded to version 4.3.0 for those architectures which use XFree86 version 4. o scsictl(8) now supports a few new commands. o BIND has been upgraded to version 8.3.7. o DHCP has been upgraded to version 3.0.1rc11 with various fixes. o CVS has been upgraded to version 1.11.10. Miscellaneous o At least one problem causing sysinst to crash has been fixed, and a progress bar has been added as an option to monitor the progress of the extraction of the install sets. o Package tools upgraded to version 20030918. And of course there have also been innumerable bug fixes and other mis- cellaneous enhancements. You can look for this trend to continue. walnut specific Changes Between The NetBSD 1.6 and 1.6.1 Releases The NetBSD 1.6.1 release provides numerous significant functional en- hancements, including support for many new devices, integration of hun- dreds of bug fixes, patches and updates to kernel subsystems, and many user-land enhancements. The result of these improvements is a stable op- erating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over seven months of development that went into the NetBSD 1.6.1 release. Some highlights include: Kernel o Hardware random number support for some Intel chipsets has been added. o Support for additional Adaptec RAID controllers has been added to aac(4). o A number of bugs in the VM system have been fixed. o Bug fixes to audio(4), dpt(4), eap(4), emuxki(4), iop(4), siop(4) and umass(4). o Some Linux compatibility bugs have been fixed. o A number of USB bugs have been fixed. o acorn32 and acorn26 module recognition overhauled; APDL IDE should now work. o pciide(4) support has been extended to support Promise Ultra133TX2, Promise Ultra133TX2v2, HighPoint HPT372, Ultra/133 on VIA VT8233A, and the VIA VT8235. o Many changes to the arm architecture support, mostly triggered by evbarm port infrastructure changes. o Amiga boot handling has been modified to better handle certain ma- chine configurations. Networking o IPv6 fixes to various tools. o Bug fixes to the tlp(4) and xi(4) drivers. o Enhancements to the pcn(4) driver. o rtk(4) now supports Planex FNW-3603 cardbus ethernet card. o ex(4) multicast handling has been fixed. o wi(4) now supports Netgear MA401RA card. o wm(4) now supports more chip variants. o aue(4) now supports SMC 2206USB/ETH EZ Connect adapter. o sip(4) now has some Tx interrupt mitigation code, and improved sup- port for 64-bit DP83820 cards. o The fxp(4) driver has been improved for better support of certain i82558 revisions, and has been fixed to recognize some more chips. o IPFilter has been upgraded to version 3.4.29. Please note that this requires a synchronized upgrade of kernel and the ipf user programs to work properly. o Support for Broadcom Gigabit Ethernet devices has been added by the addition of the bge(4) driver. o Some IPsec bugs have been fixed (from KAME). o Some ftpd(8) interoperability bugs have been fixed. o mopd(8) fixes to make the program load correctly. o A number of pppoe(4) bugs have been fixed. File system o A number of FFS and NFS bugs have been fixed. o Several fixes to ffs(4) soft dependencies handling have been incorpo- rated. o Some NFSv3 fixes have been applied to amd(8). o Some fsck(8) bugs have been fixed. Security o BIND has been updated to 8.3.4 and security patches applied to named(8) and the libc resolver. o Various security patches have been applied to sendmail. o Padding has been added to minimum-sized IP packets in several ether- net drivers to prevent unintented information leakage. o OpenSSL has been updated to 0.9.6g and a number of security patches applied. o A potential buffer overflow in zlib has been fixed. o Buffer overflow bugs in file(1) have been fixed. o Some Kerberos 4 security bugs have been addressed. o A umask security problem in GNU tar(1) has been fixed. System administration and user tools o user(8) has seen several fixes, some of them related to MD5 and blow- fish password encryption support. o Changes to gcc for the arm architecture introduces a minor flag day: new and old object files can not be mixed. Required for proper soft- VFP support. o MDC2 build has been made optional, as the algorithm is patended. o The package tools have been updated to the 20030202 version. Miscellaneous o Bug fixes to sysinst, the NetBSD installer. o Various cross-build fixes have been incorporated. o Various fixes to the toolchain and build process. o Various fixes to the rc.d subsystem. o A large number of sparc64 fixes have been applied. o Timezone files have been updated to tz2002d. o Many new packages have been added to The NetBSD packages collection, including the latest open source desktop KDE3, OpenOffice.org, as well as a large number of bugs fixed, many addressing security is- sues. And of course there have also been innumerable bug fixes and other mis- cellaneous enhancements. You can look for this trend to continue. Changes Between The NetBSD 1.5 and 1.6 Releases The NetBSD 1.6 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 user-land 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 eighteen months of develop- ment that went into the NetBSD 1.6.2 release. Some highlights include: Kernel o Ports to new platforms including: algor, dreamcast, evbarm, hpcarm, hpcsh, newsmips, sandpoint, sgimips, sun2, and walnut. o Unified Buffer Cache (UBC) removes size restriction of the file sys- tem's buffer cache to use all available RAM (if not otherwise used!) and improves overall system performance. o Round-robin page colouring implemented for various ports for better cache utilisation, more deterministic run-time behaviour, and faster program execution. o A rewritten SCSI middle layer to provide a cleaner interface between the different kernel layers, including a kernel thread to handle er- ror recovery outside of the interrupt context. See scsipi(9). o A new pipe implementation with significantly higher performance due to lower overheads, which uses the UVM Page Loan facility. o New boot loader flags -v (bootverbose) and -q (bootquiet), to be used by kernel code to optionally print information during boot. o An in-kernel boot time device configuration manager userconf(4), ac- tivated with the -c boot loader flag. o A work-in-progress snapshot of ACPI support, based on the 20010831 snapshot of the Intel ACPICA reference implementation. o USB 2.0 support, in the form of a preliminary driver for the ehci(4) host controller. o Basic kernel support for IrDA in the form of the irframe(4) IrDA frame level driver. Serial dongles and the oboe(4) driver are cur- rently supported. o Kernel configuration files can be embedded into the kernel for later retrieval. Refer to INCLUDE_CONFIG_FILE in options(4) for more in- formation. o Many more kernel tunable variables added to sysctl(8). o Linux binary emulation has been greatly improved, and now supports Linux kernel version 2.4.18. Networking o Hardware assisted IPv4 TCP and UDP checksumming and caching of the IPv6 TCP pseudo header. Support for checksum offloading on the DP83820 Gigabit Ethernet, 3Com 3c90xB, 3Com 3c90xC, and Alteon Tigon/Tigon2 Gigabit Ethernet cards. o Zero-Copy for TCP and UDP transmit path achieved through page loaning code for sosend(). o In-kernel ISDN support, from the ISDN4BSD project. o 802.1Q VLAN (virtual LAN) support. See vlan(4). o IPFilter now supports IPv6 filtering. o ndbootd(8) added; used to netboot NetBSD/sun2 machines. o racoon(8) added; IKE key management daemon for IPsec key negotiation, from the KAME project. o WEP encryption supported in ifconfig(8) and awi(4) driver. o wi(4) and wiconfig(8) now support scanning for access points, and de- faults to BSS instead of ad-hoc mode. o Bridging support; currently only for ethernet. See bridge(4). o In-kernel PPP over Ethernet (PPPoE) - RFC 2516, with much lower over- head than user-land PPPoE clients. See pppoe(4). o ifwatchd(8) added; invokes up-script and down-script when a network interface goes up and down. Used by pppoe(4). File system o Enhanced stability of LFS version 2, the BSD log-structured file sys- tem. o dump(8), dumpfs(8), fsck_ffs(8), fsirand(8), newfs(8), and tunefs(8) support a -F option to manipulate file system images in regular files. o makefs(8) added; creates file system images from a directory tree. (Currently ffs only.) o Enhanced ffs_dirpref() by Grigoriy Orlov, which noticeably improves performance on FFS file systems when creating directories, and subse- quently manipulating them. o Fixes for free block tracking and directory block allocation in FFS softdeps. o Correctly support FFS file systems with a large number of cylinder groups. o Fix the endian independant FFS (FFS_EI) support. o newfs(8) calculates default block size from the file system size, and uses the largest possible cylinders/group (cpg) value if -c isn't given. o dpti(4) driver added; an implementation of the DPT/Adaptec SCSI/I2O RAID management interface. Allows the use of the Linux versions of dptmgr, raidutil, dptelog, (etc). o Support for Windows 2000 `NTFS' (NTFS5). o Tagged queueing support for SCSI drivers based on the ncr53c9x con- troller. Security o Addition of a chroot(8) hierarchy for services including named(8), ntpd(8), and sshd(8). o Additional passwd(5) ciphers: MD5, and DES with more encryption rounds. See passwd.conf(5). o Several more code audits were performed. o /etc/security performs many more checks and is far more flexible in how it monitors changes. See security.conf(5). System administration and user tools o sushi(8) added; a menu based system administration tool. o pgrep(1) and pkill(1) added; find or signal processes by name or oth- er attributes. o System upgrades are made easier through the etcupdate(8) script which helps updating the /etc config files interactively, and the /etc/postinstall script which is provided to check for or fix config- uration changes that have occurred in NetBSD. o stat(1) added; a user interface to the information returned by the stat(2) system call. o BSD sort(1) replaces GNU sort(1). o The ``stop'' operation for rc.d(8) scripts waits until the service terminates before returning. This improves the reliability of ``restart'' operations as well. o Swap devices can be removed at system shutdown by enabling swapoff in rc.conf(5). o An optional watchdog timer which will terminate rc.shutdown(8) after the number of seconds provided in rcshutdown_timeout from rc.conf(5). Miscellaneous o Support for multibyte LC_CTYPE locales has been integrated from the Citrus project. Many Chinese, Japanese, Korean, and other encodings are now available. o Full support for cross-compilation of the base system, even as a non- root user! src/build.sh is available for doing arbitrary cross- builds; see src/BUILDING for more information. At least 38 ports for the NetBSD 1.6.2 release were cross-built on a NetBSD/i386 system us- ing this mechanism. o Migrated the following CPU platforms to ELF: arm, and m68k (including amiga, hp300, mac68k, mvme68k, sun2, and x68k). o Updates of most third party packages that are shipped in the base system to the following latest stable releases: - amd 6.0.6 - BIND 8.3.3 - binutils 2.11.2 - bzip2 1.0.2 - cvs 1.11 - dhcp 3.0.1rc9 - file 3.38 - gcc 2.95.3 - groff 1.16.1 - Heimdal 0.4e - IPfilter 3.4.27 - kerberos4 1.1 - ksh from pdksh 5.2.14p2 - less 374 - nvi 1.79 - OpenSSH 3.4 - OpenSSL 0.9.6g - Postfix 1.1.11 - ppp 2.4.0 - routed 2.24 - sendmail 8.11.6 - tcpdump 3.7.1 o Many new packages in the pkgsrc system, including the latest open source desktop KDE3, OpenOffice, perl, Apache and many more. At the time of writing, there are over 3000 third party packages available in pkgsrc. o Added AGP GART driver agp(4) for faster access to graphics boards. o init(8) will create an mfs (memory based file system) /dev if /dev/console is missing. o vmstat(8) displays kernel hash statistics with -H and -h hash. o wscons(4) supports blanking of VGA consoles. 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 first major release of NetBSD/walnut. 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.6.2 Release Contents The root directory of the NetBSD 1.6.2 release is organized as follows: .../NetBSD-1.6.2/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.6.2 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.6.2 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. 55 MB gzipped, 247 MB uncompressed pkgsrc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. 12 MB gzipped, 94 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. 4 MB gzipped, 16 MB uncompressed src This set contains all of the base NetBSD 1.6.2 sources which are not in gnusrc, sharesrc, or syssrc. 27 MB gzipped, 136 MB uncompressed syssrc This set contains the sources to the NetBSD 1.6.2 kernel for all architectures; config(8); and dbsym(8). 22 MB gzipped, 114 MB uncompressed xsrc This set contains the sources to the X Window System. 78 MB gzipped, 394 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 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 distribution 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/walnut subdirectory structure The walnut-specific portion of the NetBSD 1.6.2 release is found in the walnut subdirectory of the distribution: .../NetBSD-1.6.2/walnut/ 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-WALNUT.gz A gzipped NetBSD kernel (in ELF format) containing code for everything support- ed in this release. netbsd.img-WALNUT.gz Same as the above, but in the format expected by the firmware. netbsd.INSTALL.gz A gzipped NetBSD kernel (ELF format) containing code for everything support- ed in this release. It also includes a RAM-disk installer with sysinst. netbsd.INSTALL.img.gz Same as the above, but in the format expected by the firmware. sets/ walnut binary distribution sets; see below. installation/ Binary distribution sets The NetBSD walnut binary distribution sets contain the binaries which comprise the NetBSD 1.6.2 release for the walnut. There are eight binary distribution sets. The binary distribution sets can be found in the walnut/binary/sets subdirectory of the NetBSD 1.6.2 distribution tree, and are as follows: base The NetBSD 1.6.2 walnut 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 functional. It includes shared library support, and excludes everything described below. 20 MB gzipped, 53 MB uncompressed comp Things needed for compiling programs. This set includes the system include files (/usr/include) and the various system libraries (ex- cept the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utili- ties it contains, as well as the system call and library manual pages. 17 MB gzipped, 64 MB uncompressed etc This distribution set contains the system configuration files that reside in /etc and in several other places. This set must be in- stalled 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-WALNUT This set contains a NetBSD/walnut 1.6.2 kernel in ELF format named /netbsd and the same kernel in the format needed by the bootloader as /netbsd.img. You must install this distribution set. 4 MB gzipped, 8 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. 7 MB gzipped, 27 MB uncompressed misc This set includes the (rather large) system dictionaries, the type- settable document set, and other files from /usr/share. 3 MB gzipped, 8 MB uncompressed text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. 2 MB gzipped, 6 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. 3 MB gzipped, 9 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 2 MB gzipped, 9 MB uncompressed xcontrib Programs that were contributed to X. 1 MB gzipped, 1 MB uncompressed xfont Fonts needed by X. 6 MB gzipped, 7 MB uncompressed xmisc Miscellaneous X programs. 1 MB gzipped, 1 MB uncompressed The walnut 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 file- names 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 util- ity is used only in a Traditional method installation. Note: Each directory in the walnut binary distribution also has its own checksum files, just as the source distribution does. NetBSD/walnut System Requirements and Supported Devices NetBSD/walnut is a port of NetBSD to the IBM PowerPC 405GP based walnut evalu- ation board. Supported devices o Ethernet: The built-in Ethernet card is not supported, so another PCI Ethernet card supported by NetBSD must be provided if you want to use NetBSD/walnut on a network. Any PCI Ethernet card supported by NetBSD should work. o SCSI: Any PCI SCSI card supported by NetBSD should work, as should most SCSI disk/tape/CD-ROM devices. o IDE: - Promise Ultra66 (pciide) - Other PCI IDE controllers should work, but there are no reports. - Most IDE disk/CD-ROM/ATAPI devices should work. o Audio - PCI audio cards, although none have been tested. o Serial ports - On-board serial ports (com0) and (com1) - Some PCI serial ports should work, but no one has tried them o PCI cards - Most MI PCI cards should work, although very few have been test- ed with NetBSD/walnut http://www.netbsd.org/Hardware/pci.html Unsupported devices o On-board Ethernet Note: This does not concern booting the kernel itself, since that is done by the firmware. For using an NFS root you will have to pro- vide a supported network card, though. Supported boot devices and media The firmware only supports booting from network or the serial port, so you cannot boot from disk even if you install a disk controller. Instructions for booting from serial port are not provided; in the following we will describe how to setup netbooting. The first step is setting the IP addresses of both the walnut itself and the host that will be serving the kernel image. From the main menu, choose 3 to set the IP address of the machine: 1 - Enable/disable tests 2 - Enable/disable boot devices 3 - Change IP addresses 4 - Ping test 5 - Toggle ROM monitor debugger 6 - Toggle automatic menu 7 - Display configuration 8 - Save changes to configuration 9 - Set baud rate for s1 boot A - Enable/disable I cache (Enabled ) B - Enable/disable D cache (Enabled ) 0 - Exit menu and continue -> 3 Set the IP address for the local Ethernet with 1: --- CHANGE IP ADDRESS --- Device List: 001 Enabled Ethernet [ENET] local=0.0.0.0 remote=0.0.0.0 hwaddr=0004ace312bd 004 Disabled Serial Port 2 [S2] local=8.1.1.2 remote=255.255.255.255 hwaddr=ffffffffffff ---------------------------- select device to change ->1 1 - Change local address 2 - Change remote address 0 - Return to main menu ->1 Current IP address = (0.0.0.0) Enter new IP address ->Enter IP address in dot notation, (eg. 8.1.1.2) Here you enter the machine's IP address, e.g. 10.0.0.1. Now you need to do the same thing to set the host IP address (choice 2 from the menu above). Once both the local and remote addresses are set, you can use the ping test to make sure the ethernet is working; or you can simply use option 0, "Exit menu and continue" to try to boot the machine, if you already set up the remote ma- chine to provide a kernel image. For details on how to do that, see the Booting from the network section below. You should now be able to boot the operating system. Getting the NetBSD System on to Useful Media Installation is supported from several media types, including: o CD-ROM 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 various media are outlined below. CD-ROM Find out where the distribution set files are on the CD-ROM. 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. You 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 upgrad- ing 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 in- stallation, the IP address of ftp.netbsd.org is 204.152.184.75 (as of June, 2002). Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're in- stalling NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing instal- lation, go directly to the section on upgrading. Note: This method of installation is recommended only for those already familiar with using BSD network configura- tion and management commands. If you aren't, this docu- mentation should help, but is not intended to be all-en- compassing. 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 privi- leges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the ma- chine 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 ad- dress of the NetBSD machine itself. Once the NFS server is set up properly and you have the infor- mation 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 preparing your hard disk, below. If you're upgrading an existing installation, go di- rectly to the section on upgrading. Note: This method of installation is recommended only for those already familiar with using BSD network configura- tion and management commands. If you aren't, this docu- mentation should help, but is not intended to be all-en- compassing. 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 easiest 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 system. (If you can't figure it out, ask your system administrator.) In the above example, dist_directories are the distribution sets' directo- ries, 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-1.6.2 # cd walnut/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 instal- lation, go directly to the section on upgrading. Upgrade If you are upgrading NetBSD, you also have the option of in- stalling NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the base and kern binary distributions, and so must put the base and kern sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should not upgrade the etc distribution; it contains contains system configuration files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. Preparing your System for NetBSD installation When installing NetBSD for your NetBSD/walnut system, you have two options: Via serial port or via network. The firmware does not support loading the kernel from a disk. Booting over a serial line This is not currently documented or supported. If you would like to attempt this and supply documentation, please do! Booting from the network 1. Introduction To netboot a walnut, you must configure one or more servers to provide information and files to your walnut (the `client ).' If you are using NetBSD (any architecture) on your netboot server(s), the information pro- vided here should be sufficient to configure everything. 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 op- erating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary 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, kernel and file system stages. In the first stage, the client discovers information about where to find the kernel image. Once the kernel is loaded, it starts execut- ing. 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 walnut systems use BOOTP for the discovery stage. TFTP is used in the bootstrap phase to download the kernel via the on-board Ethernet card by the firmware. Thus, NetBSD support for the on-board card is not needed in this step. For NFS mounting a file system on the other hand, NetBSD support for the Ethernet card is needed, and the on-board one will not suffice; you have to provide a second Ethernet card supported by NetBSD. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hardware ad- dress) 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 direc- tory /export/client/root. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environment. You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed. 2. dhcpd(8) in bootpd(8) compatible mode 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"; # # Name of the kernel image to download via tftp. # Note: Plain (ELF) kernels won't work, you # have to use the corresponding *.img file. # filename "netbsd.INSTALL.img" # # The path on the NFS server. # option root-path "/export/client/root"; } #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 1.5 or later, you can achieve this with: # /etc/rc.d/dhcpd restart 3. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) en- vironment in the /tftpboot directory. Thus, the first order of business is to create this directory: # mkdir -p /tftpboot Next, edit /etc/inetd.conf and uncomment the line with the TFTP daemon: tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot Now, restart inetd(8). If the server is running NetBSD 1.5 or later, you can achieve this with: # /etc/rc.d/inetd restart Now, you need to copy the kernel for your walnut machine to /tftpboot. Just to be sure, let's make everything readable. # chmod -R a+rX /tftpboot Sometimes, the arp(8) table gets messed up, and the TFTP server can't communicate with the client. In this case, it will write a log message (via syslogd(8)) to /var/log/messages saying: `tftpd: write: Host is down'. If this is the case, you may need to force the server to map your client's ethernet address to its IP address: # arp -s client CC:CC:CC:CC:CC:CC 4. nfsd(8), mountd(8), and rpcbind(8) You can either boot a kernel, or the RAM disk-based installer binary/kernel/netbsd.INSTALL.img.gz. In the first case you'll also need an NFS-mounted userland. Let's set up the NFS server. Create the direc- tory 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 1.5 or later, 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 If you are netbooting the installer, use binary/kernel/netbsd.INSTALL.img.gz (this has the installation tools in a RAM disk). Also, copy the distribution files to the client's root direc- tory. # cp *tgz /export/client/root # gunzip netbsd.INSTALL.img.gz # mv netbsd.INSTALL.img /export/client/root/netbsd If you are running your walnut diskless, simply use binary/kernel/netbsd.img-WALNUT.gz. 6. Client file system You can skip this step if you do not plan to run your client diskless af- ter 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 list- ed 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/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 following 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: nfs_server=YES # enable server daemons mountd=YES rpcbind=YES rpcbind_flags="-l" # -l logs libwrap Also, you'll need to make sure the tftpd line in /etc/inetd.conf remains uncommented. Installing the NetBSD System Booting the installer The kernel starts automatically once it is loaded. Example of a normal boot If you already configured the network settings, just press `0' from the boot menu to boot. Common Problems and Error Messages Do not use the plain ELF kernel as the file provided to the firmware, use the ``netbsd.img'' file (which is in the format the firmware expects). Of course, you should put the matching ``netbsd'' as /netbsd on your root file system, otherwise some kernel grovellers won't work. Running the sysinst installation program 1. Introduction Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use. 2. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installa- tion system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch by running the /sysinst program from the command prompt. It is not neces- sary to reboot. 3. Quick install First, let's describe a quick install. The other sections of this docu- ment go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instructions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example. o What you need. - The distribution sets (in this example, they are on CD). - Some form of bootable media, described above. - A CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of of memory installed. - The harddisk should have at least + n megabytes of space free, where n is the number of megabytes of main memory in your system. If you wish to install the X Window System as well, you will need at least 60 MB more. o The Quick Installation - Boot the system as described above. You should be at the sysinst main menu. .***********************************************. * NetBSD-1.6 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * x: Exit Install System * .***********************************************. - If you wish, you can configure some network settings immediately by choosing the Utility menu and then Configure network. It isn't actually required at this point, but it may be more conve- nient. Go back to the main menu. - Choose install. - You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. - After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok. - After all the files have been unpacked, go back to the main menu and select reboot, after you have removed the bootfloppy from the drive. - NetBSD will now boot. If you haven't already done so in sysinst, you should log in as root, and set a password for that account. You are also advised to edit the file /etc/rc.conf to match your system needs. - Your installation is now complete. - For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on http://www.xfree86.org/. 4. Booting NetBSD You may want to read the boot messages, to notice your disk's name and capacity. Its name will be something like sd0 or wd0 and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD 's partitions. You will also need to know the name, to tell sysinst on which disk to in- stall. The most important thing to know is that wd0 is NetBSD 's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. Network configuration If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu, and select the Configure network option. If you only want to temporarily use networking during the in- stallation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this. 6. Installation drive selection and parameters To start the installation, select Install NetBSD to hard disk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like sd0 or sd1. 7. Partitioning the disk o Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. 8. Editing the NetBSD disklabel The partition table of the NetBSD part of a disk is called a disklabel. There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can spec- ify everything yourself. The last option uses the partition info already present on the disk. You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the diskla- bel have a fixed purpose. a Root partition (/) b Swap partition. c The NetBSD portion of the disk. d-p Available for other use. Traditionally, e is the partition mounted on /usr, but this is historical practice and not a fixed value. You will then be asked to name your disk's disklabel. The default re- sponse is ``mydisk''. For most purposes this will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. 9. Preparing your hard disk You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to proceed, enter yes at the prompt. The install program will now label your disk and make the file systems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are run- ning. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Oth- erwise, you can continue the installation program after pressing the re- turn key. 10. Getting the distribution sets The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installation, you will be presented with a menu which enables you to choose from one of the fol- lowing methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be us- ing, you can continue to section labeled `Extracting the distribution sets'. 11. Installation using ftp To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure net- working, you will need to specify an IP address instead of a hostname for the ftp server. sysinst will proceed to transfer all the default set files from the re- mote site to your hard disk. 12. Installation using NFS To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure net- working, you will need to specify an IP address instead of a hostname for the NFS server. 13. Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are. sysinst will then check if the files are indeed available in the speci- fied location, and proceed to the actual extraction of the sets. 14. Installation from an unmounted file system In order to install from a local file system, you will need to specify the device that the file system resides on (for example sd1e) the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location. 15. Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file system that is al- ready accessible. sysinst will ask you for the name of this directory. 16. Extracting the distribution sets After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full installation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base) and etc they will not be shown in this selection menu. Before extraction begins, you can elect to watch the files being extract- ed; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles. After all the files have been extracted, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can than set a pass- word for the "root" account, to prevent the machine coming up without ac- cess restrictions. 17. Finalizing your installation Congratulations, you have successfully installed NetBSD 1.6.2. You can now reboot the machine, and boot NetBSD from harddisk. 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 system 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 vt220 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # stty erase '^h' # stty erase '^?' At this point, you need to configure at least one file in the /etc direc- tory. 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. De- fault 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=vt220 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 con- tinue with the multi-user boot. Other values that need to be set in /etc/rc.conf for a networked environ- ment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your network interface, along the lines of ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_de0="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 adventurous) run named(8). See resolv.conf(5) or named(8) for more information. 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 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 sys- tem. This automatically handles any changes necessary to make the soft- ware run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstal- lation), 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 1.6.2/walnut/All subdir. You can install them with the following commands: # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/1.6.2/walnut/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v apache # pkg_add -v perl ... The above commands will install the tcsh shell, the Apache web server and the perl programming language 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, then see the README file in the extraction directo- ry (e.g. /usr/pkgsrc/README) for more information. 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 ad- justed; files aiding in this can be found in /usr/share/sendmail. See the README file there for more information. 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 manual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System This is the first release of NetBSD/walnut, and as such, there is no ability to upgrade from a prior release. Compatibility Issues With Previous NetBSD Releases Users upgrading from previous versions of NetBSD may wish to bear the follow- ing problems and compatibility issues in mind when upgrading to NetBSD 1.6.2. Issues affecting an upgrade from NetBSD 1.5 The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall: mkdir /tmp/upgrade cd /tmp/upgrade pax -zrpe -f /path/to/etc.tgz ./etc/postinstall -s `pwd` check ./etc/postinstall -s `pwd` fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* o The following files are now obsolete: /etc/rc.d/NETWORK and /etc/rc.d/gated. o The following rc.conf(5) entries are now obsolete: amd_master, ip6forwarding, defcorename, and nfsiod_flags. critical_filesystems_beforenet has been replaced by critical_filesystems_local. critical_filesystems has been replaced by critical_filesystems_remote. o The users and groups `named', `ntpd', and `sshd' need to be created. o The configuration files for ssh(1) and sshd(8) were moved from /etc to /etc/ssh, including ssh_known_hosts* files and the host key files ssh_host*_key*. /etc/ssh.conf was renamed to /etc/ssh/ssh_config, and /etc/sshd.conf was renamed to /etc/ssh/sshd_config. o The mux entries in wscons.conf(5) are now obsolete. The following issues need to be resolved manually: o postfix(8) configuration files require upgrading. cd /usr/share/examples/postfix cp post-install postfix-files postfix-script /etc/postfix postfix check o The de ethernet driver was replaced with the tlp driver. This may require the renaming of the files /etc/ifconfig.de* to /etc/ifconfig.tlp*, renaming of rc.conf(5) entries ifconfig_de* to ifconfig_tlp*, and the reconfiguration of files such as /etc/dhclient.conf and /etc/ipf.conf. Issues affecting an upgrade from NetBSD 1.4 or prior o /etc/rc modified to use /etc/rc.d/* Prior to NetBSD 1.5, /etc/rc was a traditional BSD style monolithic file; 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 argu- ment of `start'. Many rc.d scripts won't start unless the appropriate rc.conf(5) entry in /etc/rc.conf is set to `YES.' At system shutdown, /etc/rc.shutdown uses rcorder(8) to build a dependency list of the files in /etc/rc.d that have a ``KEYWORD: shutdown'' line, re- verses 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 neces- sary. Refer to the other scripts in that directory and rc(8) for more in- formation on implementing rc.d scripts. o named(8) leaks version information. Previous releases of NetBSD disabled a feature of named(8) where the ver- sion 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) was 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 differ- ent 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 section should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the 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 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 vari- ous 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 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 some- where, 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, including (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 Robert- son, 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 recog- nized for it. o The following individuals and organizations (each in alphabetical order) have made donations or loans of hardware and/or money, to support 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 Luke Mewburn 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 Rob Windsor Jim Wise Reinoud Zandijk 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. Precedence Technologies Ltd 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 devel- oping 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: 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): Simon Burge simonb@netbsd.org pmax Simon Burge simonb@netbsd.org sbmips Jeremy Cooper jeremy@netbsd.org sun3x Matt Fredette fredette@netbsd.org sun2 Chris Gilbert chris@netbsd.org cats Ross Harvey ross@netbsd.org alpha Jun-ichiro itojun Hagino itojun@netbsd.org sh3 Ben Harris bjh21@netbsd.org acorn26 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 Frank van der Linden fvdl@netbsd.org i386 Anders Magnusson ragge@netbsd.org vax Phil Nelson phil@netbsd.org pc532 NISHIMURA Takeshi nsmrtks@netbsd.org x68k 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 Leo Weppelman leo@netbsd.org atari Nathan Williams nathanw@netbsd.org sun3 Steve Woodford scw@netbsd.org mvme68k Steve Woodford scw@netbsd.org mvmeppc Reinoud Zandijk reinoud@netbsd.org acorn32 The NetBSD 1.6.2 Release Engineering team: Erik Berls cyber@netbsd.org Havard Eidnes he@netbsd.org Perry Metzger perry@netbsd.org Luke Mewburn lukem@netbsd.org Jason Thorpe thorpej@netbsd.org Todd Vierling tv@netbsd.org NetBSD Developers: Nathan Ahlstrom nra@netbsd.org Steve Allen wormey@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 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 Rafal Boni rafal@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 James Chacon jmc@netbsd.org Bill Coldwell billc@netbsd.org Julian Coleman jdc@netbsd.org Jeremy Cooper jeremy@netbsd.org Chuck Cranor chuck@netbsd.org Alistair Crooks agc@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 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 Havard Eidnes he@netbsd.org Stoned Elipot seb@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 Matt Fredette fredette@netbsd.org Thorsten Frueauf frueauf@netbsd.org Castor Fu castor@netbsd.org Ichiro Fukuhara ichiro@netbsd.org Thomas Gerner thomas@netbsd.org Simon J. Gerraty sjg@netbsd.org Justin Gibbs gibbs@netbsd.org Chris Gilbert chris@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 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 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 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 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 Mattias Karlsson keihan@netbsd.org KAWAMOTO Yosihisa kawamoto@netbsd.org Mario Kemper magick@netbsd.org Thomas Klausner wiz@netbsd.org Klaus Klein kleink@netbsd.org Wayne Knowles wdk@netbsd.org John Kohl jtk@netbsd.org Paul Kranenburg pk@netbsd.org Martti Kuparinen martti@netbsd.org Kevin Lahey kml@netbsd.org Johnny C. Lam jlam@netbsd.org Martin J. Laubach mjl@netbsd.org Ted Lemon mellon@netbsd.org Frank van der Linden fvdl@netbsd.org Joel Lindholm joel@netbsd.org Mike Long mikel@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 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 Phil Nelson phil@netbsd.org Bob Nestor rnestor@netbsd.org NISHIMURA Takeshi nsmrtks@netbsd.org Tohru Nishimura nisimura@netbsd.org NONAKA Kimihiro nonaka@netbsd.org Jesse Off joff@netbsd.org Tatoku Ogaito tacha@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 Chris Pinnock cjep@netbsd.org Dante Profeta dante@netbsd.org Chris Provenzano proven@netbsd.org Michael Rauch mrauch@netbsd.org Darren Reed darrenr@netbsd.org Scott Reynolds scottr@netbsd.org Michael Richardson mcr@netbsd.org Tim Rightnour garbled@netbsd.org Gordon Ross gwr@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 Reed Shadgett dent@netbsd.org Tim Shepard shep@netbsd.org Takeshi Shibagaki shiba@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 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 Matt Thomas matt@netbsd.org Jason Thorpe thorpej@netbsd.org Christoph Toshok toshok@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 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 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 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 soft- ware 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 Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Hannum. 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 Washington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, 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 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 Weppelman. 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 Wun- sch. 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 Pro- ject. 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 Communica- tions, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Pro- ject. 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 Pro- ject. 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 for the NetBSD Project. 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 Sol- frank. This product includes software developed by Mats O Jansson and Charles D. Cra- nor. 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 Pro- ject. 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 NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software designed by William Allen Simpson. 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 Science at the University of Utah. This product includes software developed by the Computer Systems Laboratory at the University of Utah. This product includes software developed by the University of Calgary Depart- ment 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 Consortium 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 Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed for the NetBSD Project by Wasabi Sys- tems, Inc. This product includes software developed by LAN Media Corporation and its con- tributors. This product includes software developed by Michael Graff for the NetBSD Pro- ject. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@mincom.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 Cali- fornia and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by Reinoud Zandijk. This product includes software developed at the Information Technology Divi- sion, US Naval Research Laboratory. This product includes software developed by Brini. 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 Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Charles M. Hannum. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by TooLs GmbH. This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed for the NetBSD Project by Wasabi Sys- tems, Inc. The End NetBSD September 7, 2002 40