INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/i386. DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.5.2 on the _i_3_8_6 platform. It is available in four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of _._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t: _._p_s PostScript. _._h_t_m_l Standard Internet HTML. _._m_o_r_e 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 _m_a_n pages are generally pre- sented. _._t_x_t Plain old ASCII. You are reading the _m_o_r_e version. QQuuiicckk iinnssttaallll nnootteess ffoorr tthhee iimmppaattiieenntt This section contains some brief notes describing what you need to in- stall NetBSD 1.5.2 on a machine of the i386 architecture. ++oo Fetch the appropriate pair of boot floppy images from the _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/ directory. Most people will need the _b_o_o_t_1_._f_s and _b_o_o_t_2_._f_s images, or possibly (but not necessarily) _b_o_o_t_l_a_p_1_._f_s and _b_o_o_t_l_a_p_2_._f_s if installing on a laptop. ++oo The actual binary distribution is in the _b_i_n_a_r_y_/_s_e_t_s_/ directory. When you boot the install floppies, the installation program can fetch these files for you (using e.g. ftp), if you have a network connection. There are several other methods to get the binary sets onto the machine you install. You will at a minimum need one of the kernel sets, typically _k_e_r_n_._t_g_z, as well as _b_a_s_e_._t_g_z and _e_t_c_._t_g_z. In a typical workstation installation you will probably want all the installation sets. ++oo Write the floppy images directly to a pair of floppies. If you have problems writing a raw image to a floppy, the rraawwrriittee..eexxee MS-DOS pro- gram or the RRaawwrriittee3322..eexxee Windows32 program (inside _r_a_w_r_i_t_e_3_2_._z_i_p) in the _u_t_i_l_i_t_i_e_s_/ directory may be of help. The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD. ++oo For third-party programs which are not part of the base NetBSD dis- tribution, you will want to explore the ppkkggssrrcc system with its more than 2100 program packages. WWhhaatt iiss NNeettBBSSDD?? The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Net- working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on thirty-one different system architectures featuring twelve dis- tinct families of CPUs, and is being ported to more. The NetBSD 1.5.2 re- lease contains complete binary releases for fifteen different machine types. (The sixteen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//.) 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. UUppggrraaddee ppaatthh ttoo NNeettBBSSDD 11..55..22 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.5.2. NetBSD 1.5.2 is an upgrade of NetBSD 1.5, 1.5.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 _a_f_t_e_r the point where the release cycle for 1.5 was started are designated by ver- sion identifiers such as 1.5A, 1.5B, etc. These identifiers do not des- ignate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.5.2 can _n_o_t be used to upgrade a sys- tem running one of those intermediate development versions. Trying to use the NetBSD 1.5.2 kernel on such a system _w_i_l_l 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.5.2 to determine if a given feature is present or absent in 1.5.2. The development of 1.5 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.5 was started, and during the release cycle of 1.5 and its patch releases, selected fixes and enhancements have been imported from the main development trunk. So, there are features in 1.5.2 which were not in, e.g. 1.5B, and vice versa. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55..11 aanndd 11..55..22 The main purpose of NetBSD 1.5.2 is to fix some problems discovered shortly after the release of NetBSD 1.5.1. Some highlights are: ++oo telnetd(8) has been fixed to deal with a security issue (SA2001-012). ++oo A weakness in the OpenSSL libcrypto's pseudo random number generator has been fixed (SA2001-013). ++oo Floating point emulation on i386 (to run on FPU-less CPUs) which was broken late in 1.5.1's cycle has been restored to working order. ++oo Bugs in the compiler have been worked around to produce a working miniroot image on sparc64. ++oo The script-based installers on amiga, atari and mvme68k have been up- dated to deal with new behaviour from mount(8). ++oo dump(8) has been fixed to deal with a local security issue (SA2001-014). ++oo Several system calls have had defensive length checks applied on their arguments (SA2001-015). ++oo The DHCP software has been upgraded to ISC Version 3, Release Candi- date 10. Additionally, a few more bugs have been fixed. See the CHANGES-1.5.2 file for the complete list of changes. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55 aanndd 11..55..11 The complete list of changes between NetBSD 1.5 and 1.5.1 can be found in the file CHANGES-1.5.1 in the top directory of the source tree. The fol- lowing are highlights only: ++oo A driver for the Aironet/Cisco wireless PCMCIA cards has been added; see an(4). ++oo NFS client performance has been improved, typically by 40% for writes but possibly up to 100% in certain setups. ++oo The siop(4) driver has improved in performance and robustness. ++oo Support for cloning pseudo-interfaces has been added. See ifconfig(8). ++oo Support for 802.1Q virtual LANs has been added. See vlan(4). ++oo The isp(4) driver has been upgraded to (among other things) work on MacPPC. ++oo BIND has been upgraded to version 8.2.3 (SA2001-001). ++oo Support for booting from RAIDframe RAID1 mirrors on i386 added. ++oo The lfs(4) file system has again been substantially updated, but is still experimental. ++oo Ultra/66 support has been added for capable VIA chipsets, and Ul- tra/100 support has been added for the HPT370, Promise and Intel ICH2 controllers in the pciide(4) driver. Support for Intel 82801BAM con- trollers has also been added, and handling of Ali controllers has been improved. ++oo OpenSSH has been updated to deal with a security issue (SA2001-003). ++oo Sendmail has been upgraded to version 8.11.3. ++oo The ex(4) driver has added support for 3Com 3c555, 3c556 and 3c556B MiniPCI Ethernet cards. ++oo A driver for the on-board audio hardware found on many Apple PowerMa- cs has been added; see awacs(4). ++oo The sip(4) driver has been fixed to properly support the dp83815, as found in current Netgear FA311 10/100 cards. ++oo ftpd(8) has been updated to deal with two security issues (SA2000-018 and SA2001-005). ++oo ntpd(8) has been updated to deal with a security issue (SA2001-004). ++oo telnetd(8) has been updated to deal with a security issue (SA2000-017). ++oo A vulnerability on i386 related to USER_LDT has been fixed (SA2001-002). ++oo The Linux emulation has been enhanced to prepare for the support of using the Linux version of VMware. ++oo IP checksumming speed has been improved on i386 compared to NetBSD 1.5 by about 10%. ++oo Support for the Socket Communications LP-E Type II PCMCIA NE2000 clone card has been added to ne(4). ++oo The DHCP software has been upgraded to ISC version 3, Beta 2, patch- level 23, to fix core dumps in dhclient(8), among other things. Please note that the new dhcpd(8) forces you to configure a "ddns-up- date-style" of either "ad-hoc", "interim" or "none". ++oo Various fixes and enhancements to INET6 and IPSEC code; among them improved interaction between IPF/Nat and IPSEC. ++oo The Heimdal kerberos(8) implementation has been upgraded to version 0.3e. ++oo Support for Accton EN2242 and other AmdTek AN985 cards added to the tlp(4) driver. ++oo Several country-specific keyboard mappings have been added for USB keyboards. ++oo A driver for Yamaha YMF724/740/744/745-based sound cards has been added, see yds(4). ++oo The maximum number of BSD disklabel partitions on the i386 port has been increased from 8 to 16. ++oo Drivers for the AC'97 based audio sound chips ESS Technology Maestro 1, 2, and 2E (see esm(4)), NeoMagic 256 (see neo(4)), and Cirrus Log- ic CrystalClear PCI Audio CS4281 (see clct(4)) have been added. In addition, many bugs have been fixed--more than 95 problems reported through our problem tracking system have been fixed, and some other non- reported problems have also been found and fixed. See the CHANGES-1.5.1 file for the complete list. The NetBSD Packages Collection (pkgsrc) which is used to maintain, build, track dependencies, and maintain NetBSD-specific fixes to third-party programs, has received a major overhaul for NetBSD 1.5.1. Some high- lights are: ++oo Many new packages were added to the collection, which now includes about 2100 packages. Many of them are also available as pre-compiled binaries on ftp.netbsd.org and its mirrors. Many packages have been modified and enhanced to compile and function properly on big-endian (m68k, sparc), and LP64 architectures (alpha, sparc64). ++oo KDE2 and KOffice together consitutes a fully integrated office envi- ronment with no license problems, available for i386, alpha and many other architectures. ++oo Mozilla 0.9, KDE2's Konqueror, and Links 0.95 are just a few examples of the web browsers available. ++oo A support package for running VMware on NetBSD/i386 was added, it's called suse_vmware. The official VMware code, a valid license, and Wasabi Systems' compatibility package are all needed to run VMware. ++oo Internal changes of the pkgsrc system include strong checksums to prevent malicious distribution files, as well as restructuring of the package structure in pkgsrc for faster extraction of pkgsrc tar files and upgrades via SUP and CVS. Please note that at the moment, ssyyssiinnsstt will not assist you in installing pre-built third-party binary packages or the pkgsrc system itself, so you will have to manually install packages using ppkkgg__iinnssttaallll or fetch and ex- tract the pkgsrc.tgz tar file to get started. Lastly, it should be noted that the X11 binaries shipped in NetBSD 1.5.2 is still based on XFree86 version 3.3.6. Several newer graphics cards are inadequately supported by that code base, but on the other hand sup- port for several older graphics cards is not available in newer XFree86 code. NetBSD is in the process of moving to XFree86 version 4, and is currently maintaining both the XFree86 3.3.6 and the XFree86 version 4 code in the xxssrrcc source set, and you may at compile time pick which sources to build and install. To ease installation, testing and use of the XFree86 version 4 code, a binary snapshot based on XFree86 version 4.0.3 will be made available for at least the i386 architecture shortly after the release of NetBSD 1.5.2. NNeeww CCoommppaattiibbiilliittyy IIssssuueess IInnttrroodduucceedd WWiitthh NNeettBBSSDD 11..55..11 With the increase of the maximum number of partitions from 8 to 16 on the i386 port, it is worth noting: ++oo Once you start using more than 8 partitions, you can no longer down- grade to a 1.5 kernel. ++oo The user-land tools which handle disklabels in 1.5.1 can not be used under a 1.5 kernel. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 11..44 aanndd 11..55 RReelleeaasseess The NetBSD 1.5 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many userland enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over one year of development that went into the NetBSD 1.5.2 release. Some highlights include: _K_e_r_n_e_l ++oo Ports to new platforms including: arc, cobalt, hpcmips, news68k, sgimips, and sparc64. ++oo Improved performance and stability of the UVM virtual memory subsys- tem. ++oo Implementation of generic kernel locking code, as well as a restruc- ture and re-tuning of the scheduler, to be used by the future symmet- ric multi-processing (SMP) implementation. ++oo Improved compatibility support for Linux, OSF1, and SVR4 programs. ++oo New compatibility support for Win32 programs. ++oo Support for dynamically loaded ELF kernel modules. ++oo Kernel process tracing using ktruss(1). ++oo Deletion of swap devices using swapctl(8). ++oo Easier hot-pluggability of keyboards and mice using a new wscons de- vice--wsmux. ++oo Improved PCMCIA and CardBus support, including support for detaching of devices and cards, resulting in better support for notebooks and PDA devices. ++oo Numerous hardware improvements, including areas such as: audio, UD- MA/66 support for ATA drives, USB, and wireless networking. _N_e_t_w_o_r_k_i_n_g ++oo Addition of IP version 6 (IPv6) and IPsec to the networking stack, from the KAME project. This includes addition of kernel code for IPv6/IPsec, IPv4/v6 dual-stack user applications and supporting li- braries. Due to this, the shlib major version for pcap(3) is incre- mented and you may need to recompile userland tools. The KAME IPv6 part includes results from the unified-IPv6 effort. _F_i_l_e _s_y_s_t_e_m ++oo Significant Fast file system (FFS) performance enhancements via inte- gration of Kirk McKusick's soft updates and trickle sync code. ++oo Support for the Windows NT `NTFS' file system (read-only at this stage). ++oo Support for revision 1 of the Linux `ext2fs' file system. ++oo Enhanced stability and usability of LFS (the BSD log-structured file system). ++oo Various RAIDframe enhancements including: auto-detection of RAID com- ponents and auto-configuration of RAID sets, and the ability to con- figure the root file system (_/) on a RAID set. ++oo Support for Microsoft Joliet extensions to the ISO9660 CD file sys- tem. ++oo Improved file system vnode locking mechanisms, thus resolving a source of several panics in the past. ++oo Support for NFS and RPC over IPv6. ++oo The server part of NFS locking (implemented by rpc.lockd(8)) now works. _S_e_c_u_r_i_t_y ++oo Strong cryptographic libraries and applications integrated, including the AES cipher Rijndael, the OpenSSL library, more complete Kerberos IV and Kerberos V support, and an SSH server and client. ++oo sysctl(3) interfaces to various elements of process and system infor- mation, allowing programs such as ps(1), dmesg(1) and the like to op- erate without recompilation after kernel upgrades, and remove the ne- cessity to run setgid kmem (thus improving system security). ++oo Disable various services by default, and set the default options for disabled daemons to a higher level of logging. ++oo Several code audits were performed. One audit replaced string rou- tines that were used without bounds checking, and another one identi- fied and disabled places where format strings were used in unsafe ways, allowing arbitrary data to be entered by (possibly) malicious users to overwrite application code, and leading from Denial of Ser- vice attacks to compromised systems. ++oo sshd(8) and ssh(1) now require rnd(4) kernel random number devices. _S_y_s_t_e_m _a_d_m_i_n_i_s_t_r_a_t_i_o_n _a_n_d _u_s_e_r _t_o_o_l_s ++oo Conversion of the rc(8) system startup and shutdown scripts to an `rc.d' mechanism, with separate control scripts for each service, and appropriate dependency ordering provided by rcorder(8). ++oo postfix(1) provided as alternative mail transport agent to sendmail(8). ++oo User management tools useradd(8), usermod(8), userdel(8), groupadd(8), groupmod(8), and groupdel(8) added to the system. ++oo Incorporation of a login class capability database (_/_e_t_c_/_l_o_g_i_n_._c_o_n_f) from BSD/OS. ++oo Improved support for usernames longer than eight characters in pro- grams such as at(1) and w(1). ++oo Many enhancements to ftpd(8) providing features found in larger and less secure FTP daemons, such as user classes, connection limits, im- proved support for virtual hosting, transfer statistics, transfer rate throttling, and support for various IETF ftpext working group extensions. ++oo The ftp(1) client has been improved even further, including transfer rate throttling, improved URL support, command line uploads. See the man page for details. _M_i_s_c_e_l_l_a_n_e_o_u_s ++oo Updates to the NetBSD source code style code (located in _/_u_s_r_/_s_h_a_r_e_/_m_i_s_c_/_s_t_y_l_e) to use ANSI C only (instead of K&R) and re- flect current (best) practice, and begin migrating the NetBSD source code to follow it. ++oo Implementation of many SUSv2 features to the curses(3) library, in- cluding support for color. ++oo Updates of most third party packages that are shipped in the base system, including file(1), ipfilter(4), ppp(4), and sendmail(8) to the latest stable release. ++oo Many new packages in the _p_k_g_s_r_c system, including standard desktops like KDE and GNOME as well as latest Tcl/Tk and perl and many of the components of the Java Enterprise platform. The package framework itself now has full wildcard dependency support. 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 eighth major release of NetBSD for the i386. As is usual between releases, the i386 port has had many improvements made to it--too many to detail all of them here. Numerous new drivers have been added. See the supported hardware list for details. Some (but not all!) notable i386-specific improvements include: ++oo Migration to the ELF binary format from a.out. You can still use your pre-1.5 a.out applications, though. ++oo Preliminary support for MCA (MicroChannel Architecture) NetBSD 1.5 on i386 is, as usual, also fully backward compatible with old NetBSD/i386 binaries, so you don't need to recompile all your local pro- grams provided you set the appropriate binary compatibility options in your kernel configuration. TThhee FFuuttuurree ooff NNeettBBSSDD 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: ++oo providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. ++oo providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. ++oo providing a better position from which to undertake promotional ac- tivities. ++oo 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 _m_o_r_e 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. SSoouurrcceess ooff NNeettBBSSDD Refer to hhttttpp::////wwwwww..nneettbbssdd..oorrgg//SSiitteess//nneett..hhttmmll. NNeettBBSSDD 11..55..22 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.5.2 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._5_._2_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.5.2 distribution. README.files README describing the distribution's contents. TODO NetBSD 's todo list (also somewhat incomplete and out of date). _p_a_t_c_h_e_s_/ Post-release source code patches. _s_o_u_r_c_e_/ Source distribution sets; see below. In addition to the files and directories listed above, there is one di- rectory per architecture, for each of the architectures for which NetBSD 1.5.2 has a binary distribution. There are also _R_E_A_D_M_E_._e_x_p_o_r_t_- _c_o_n_t_r_o_l 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 _s_r_c_/_c_r_y_p_t_o and _s_r_c_/_s_y_s_/_c_r_y_p_t_o. 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 _s_o_u_r_c_e subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: ggnnuussrrcc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. _2_2_._3 _M_B _g_z_i_p_p_e_d_, _9_8_._8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ppkkggssrrcc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. _7_._4 _M_B _g_z_i_p_p_e_d_, _7_3_._0 _M_B _u_n_c_o_m_p_r_e_s_s_e_d sshhaarreessrrcc This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more. _3_._3 _M_B _g_z_i_p_p_e_d_, _1_3_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssrrcc This set contains all of the base NetBSD 1.5.2 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. _2_4_._8 _M_B _g_z_i_p_p_e_d_, _1_2_3_._1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssyyssssrrcc This set contains the sources to the NetBSD 1.5.2 kernel for all architectures; config(8); and dbsym(8). _1_8_._0 _M_B _g_z_i_p_p_e_d_, _9_0_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxssrrcc This set contains the sources to the X Window System. _7_8_._1 _M_B _g_z_i_p_p_e_d_, _3_9_3_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The source sets are distributed as compressed tar files. They may be un- packed into _/_u_s_r_/_s_r_c with the command: # (( ccdd // ;; ttaarr --zzxxppff -- )) << sseett__nnaammee..ttggzz The _s_e_t_s_/_S_p_l_i_t_/ 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 _s_e_t___n_a_m_e_._x_x where _s_e_t___n_a_m_e is the distribution set name, and _x_x is the sequence number of the file, starting with ``aa'' for the first file in the distribution set, then ``ab'' for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distri- bution set.) The split distributions may be reassembled and extracted with ccaatt as fol- lows: # ccaatt sseett__nnaammee..???? || (( ccdd // ;; ttaarr --zzxxppff -- )) 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: cckkssuumm --oo 11 _f_i_l_e. CKSUM POSIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm _f_i_l_e. MD5 MD5 digests for the various files in that directory, in the format produced by the command: cckkssuumm --mm _f_i_l_e. SYSVSUM Historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm --oo --22 _f_i_l_e. 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. _N_e_t_B_S_D_/_i_3_8_6 _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The i386-specific portion of the NetBSD 1.5.2 release is found in the _i_3_8_6 subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._5_._2_/_i_3_8_6_/ _I_N_S_T_A_L_L_._h_t_m_l _I_N_S_T_A_L_L_._p_s _I_N_S_T_A_L_L_._t_x_t _I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats, including this file. The _._m_o_r_e file contains underlined text using the more(1) conventions for indicating italic and bold display. _b_i_n_a_r_y_/ _k_e_r_n_e_l_/ _n_e_t_b_s_d_._G_E_N_E_R_I_C_._g_z A gzipped NetBSD kernel containing code for everything supported in this release. _n_e_t_b_s_d_._G_E_N_E_R_I_C___L_A_P_T_O_P_._g_z A version of GENERIC that has USB, PCMCIA and CardBus enabled to allow installing on laptop machines. _n_e_t_b_s_d_._G_E_N_E_R_I_C___T_I_N_Y_._g_z A version of GENERIC intended to run on machines with less than 8 MB. _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z The install kernel. _n_e_t_b_s_d_._I_N_S_T_A_L_L___T_I_N_Y_._g_z A version of INSTALL intended to run on machines with less than 8 MB. _n_e_t_b_s_d_._I_N_S_T_A_L_L___S_M_A_L_L_._g_z A version of INSTALL intended to fit on a 5.25"/1.2 MB diskette. _n_e_t_b_s_d_._I_N_S_T_A_L_L___L_A_P_T_O_P_._g_z A version of INSTALL that has USB, PCMCIA and CardBus enabled to allow installing on laptop machines. _s_e_t_s_/ i386 binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _f_l_o_p_p_y_/ i386 boot and installation floppies; see be- low. _m_i_s_c_/ Miscellaneous i386 installation utilities; see installation section, below. _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD i386 binary distribution sets contain the binaries which com- prise the NetBSD 1.5.2 release for the i386. There are eight binary dis- tribution sets. The binary distribution sets can be found in the _i_3_8_6_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.5.2 distribution tree, and are as follows: bbaassee The NetBSD 1.5.2 i386 bbaassee binary distribution. You _m_u_s_t in- stall this distribution set. It contains the base NetBSD utili- ties that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. _1_6_._4 _M_B _g_z_i_p_p_e_d_, _3_7_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ccoommpp Things needed for compiling programs. This set includes the system include files (_/_u_s_r_/_i_n_c_l_u_d_e) and the various system li- braries (except the shared libraries, which are included as part of the bbaassee set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. _1_2_._4 _M_B _g_z_i_p_p_e_d_, _4_4_._8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d eettcc This distribution set contains the system configuration files that reside in _/_e_t_c and in several other places. This set _m_u_s_t be installed if you are installing the system from scratch, but should _n_o_t be used if you are upgrading. _0_._1 _M_B _g_z_i_p_p_e_d_, _0_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ggaammeess This set includes the games and their manual pages. _2_._9 _M_B _g_z_i_p_p_e_d_, _7_._0 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn This set contains a NetBSD/i386 1.5.2 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _2_._2 _M_B _g_z_i_p_p_e_d_, _4_._7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d mmaann This set includes all of the manual pages for the binaries and other software contained in the bbaassee set. Note that it does not include any of the manual pages that are included in the other sets. _5_._0 _M_B _g_z_i_p_p_e_d_, _1_9_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d mmiisscc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from _/_u_s_r_/_s_h_a_r_e. _2_._6 _M_B _g_z_i_p_p_e_d_, _1_0_._1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d tteexxtt This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. _1_._2 _M_B _g_z_i_p_p_e_d_, _4_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d 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. The binaries shipped with NetBSD 1.5.2 are based on XFree86 version 3.3.6. NetBSD is in the process of moving to XFree86 version 4, and the X source set actually contains source for both XFree86 3.3.6 and XFree86 4, and the ability to decide at compile-time which one to build and install. The X Window Sys- tem binary sets distributed with NetBSD are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. _2_._7 _M_B _g_z_i_p_p_e_d_, _7_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoommpp The extra libraries and include files needed to compile X source code. _1_._8 _M_B _g_z_i_p_p_e_d_, _7_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoonnttrriibb Programs that were contributed to X. _0_._2 _M_B _g_z_i_p_p_e_d_, _0_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxffoonntt Fonts needed by X. _6_._2 _M_B _g_z_i_p_p_e_d_, _7_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxsseerrvveerr All XFree86 X servers. Because all of them are included, this set is large. However, you will only need one of the servers provided in this set. (Typically, XXFF8866__SSVVGGAA.) _1_4_._9 _M_B _g_z_i_p_p_e_d_, _3_5_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d The i386 binary distribution sets are distributed as gzipped tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z. They are also available in split form; catted together, the members of a split set form a gzipped tar file. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are _/-relative and therefore are extracted _b_e_l_o_w the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the ttaarr --xxppff command from _/. _N_o_t_e_: Each directory in the i386 binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//ii338866 SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess NetBSD 1.5.2 runs on ISA (AT-Bus), EISA, PCI, and VL-bus systems with 386-family processors, with or without math coprocessors. Support for MCA systems (such as some IBM PS/2 systems) is present, but still very exper- imental and needs special setup. The minimal configuration is said to re- quire 4 MB of RAM and 50 MB of disk space, though we do not know of any- one running with a system quite this minimal today. To install the entire system requires much more disk space (the unpacked binary distribution, without sources, requires at least 65 MB without counting space needed for swap space, etc), and to run X or compile the system, more RAM is recommended. (4 MB of RAM will actually allow you to run X and/or com- pile, but it won't be speedy. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU.) _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s Explanation of bracketted footnote tags [] follows this listing. ++oo Floppy controllers. ++oo MFM, ESDI, IDE, and RLL hard disk controllers. There is complete support (including IDE DMA or Ultra-DMA) for the following PCI controllers -- Acer labs M5229 IDE Controller -- Advanced Micro Devices AMD-756 and 766 IDE Controllers -- CMD Tech PCI0643, 0646, 0648 and 0649 IDE Controllers -- Contaq Microsystems/Cypress CY82C693 IDE Controller -- HighPoint HPT366 and HPT370 -- Intel PIIX, PIIX3 and PIIX4 IDE Controllers -- Intel 82801 (ICH/ICH0/ICH2) IDE Controllers -- Promise PDC20246 (Ultra/33), PDC20262 (Ultra/66) and PDC20265/PDC20267 (Ultra/100) -- Silicon Integrated System 5597/5598 IDE controller -- VIA Technologies VT82C586, VT82C586A, VT82C596A and VT82C686A IDE Controllers Most of these controllers are only available in multifunction PCI chips. Other PCI IDE controllers are supported, but per- formance may not be optimal. ISA, ISA Plug and Play and PCMCIA IDE controllers are supported as well. ++oo SCSI host adapters -- Adaptec AHA-154xA, -B, -C, and -CF -- Adaptec AHA-1640 cards (MCA variant of AHA-1540) [m] -- Adaptec AHA-174x -- Adaptec AIC-6260 and AIC-6360 based boards, including the Adaptec AHA-152x, Adaptec APA-1460 (PCMCIA) and APA-1480 (CardBus), and the SoundBlaster SCSI host adapter. _N_o_t_e_: You cannot boot from these boards if they do not have a boot ROM; consequently only the AHA-152x and motherboards using this chip are likely to be bootable. -- Adaptec AHA-2910, 2915, 2920, and 2930C adapters. -- Adaptec AHA-2x4x[U][2][W] cards and onboard PCI designs us- ing the AIC-7770, AIC-7850, AIC-7860, AIC-7870, AIC-7880 and AIC-789x chipsets. -- Adaptec AHA-394x[U][W] cards [b] -- Adaptec AHA-3950U2 cards -- Adaptec AHA-3960, 19160 and 29160 Ultra-160 adapters -- AdvanSys ABP-9x0[U][A] cards -- AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 cards -- AMD PCscsi-PCI (Am53c974) based SCSI adapters, including Tekram DC-390 -- BusLogic 54x (Adaptec AHA-154x clones) -- BusLogic 445, 74x, 9xx (but not the new `FlashPoint' series of BusLogic SCSI adapters) -- Qlogic ISP [12]0x0 SCSI/FibreChannel boards -- Seagate/Future Domain ISA SCSI adapter cards ++oo ST01/02 ++oo Future Domain TMC-885 ++oo Future Domain TMC-950 -- Symbios Logic (NCR) 53C8xx-based PCI SCSI host adapters ++oo Acculogic PCIpport ++oo ASUS SC-200 (requires NCR BIOS on motherboard to boot from disks) ++oo ASUS SC-875 ++oo ASUS SP3[G] motherboard onboard SCSI ++oo DEC Celebris XL/590 onboard SCSI ++oo Diamond FirePort 40 ++oo Lomas Data SCSI adapters ++oo NCR/SYM 8125 (and its many clones; be careful, some of these cards have a jumper to set the PCI interrupt; leave it on INT A!) ++oo Promise DC540 (a particularly common OEM model of the SYM 8125) ++oo Tekram DC-390U/F ++oo Tyan Yorktown -- Symbios Logic (NCR) 5380/53C400-based ISA SCSI host adapters [*] -- Ultrastor 14f, 34f, and (possibly) 24f -- Western Digital WD7000 SCSI and TMC-7000 host adapters (ISA cards only) ++oo MDA, CGA, VGA, SVGA, and HGC Display Adapters. _N_o_t_e_: Not all of the display adapters NetBSD/i386 can work with are supported by X. See the XFree86 FAQ for more information. [m] ++oo Serial ports -- 8250/16450-based ports [m] -- 16550/16650/16750-based ports [m] -- AST-style 4-port serial cards [*] -- BOCA 8-port serial cards [*] -- BOCA 6-port (ioat) serial cards [*] -- IBM PC-RT 4-port serial cards [*] -- Single-port Hayes ESP serial cards [*] -- Cyclades Cyclom-Y serial cards [*] -- Addonics FlexPort 8S 8-port serial cards [*] -- Byte Runner Technologies TC-400 and TC-800 serial cards [*] -- PCI universal communication cards ++oo Parallel ports. [*] [+] [m] ++oo Ethernet adapters -- AMD LANCE and PCnet-based ISA Ethernet adapters [*] ++oo Novell NE1500T ++oo Novell NE2100 ++oo Kingston 21xx ++oo Digital EtherWORKS II ISA adapters (DE200/DE201/DE202) -- AMD PCnet-based PCI Ethernet adapters ++oo Addtron AE-350 ++oo BOCALANcard/PCI ++oo SVEC FD0455 ++oo X/Lan Add-On Adapter ++oo IBM #13H9237 PCI Ethernet Adapter -- AT&T StarLAN 10, EN100, and StarLAN Fiber -- 3COM 3c501 -- 3COM 3c503 -- 3COM 3c505 [*] -- 3COM 3c507 -- 3COM 3c509, 3c579, 3c589, and 3c59X -- 3COM 3c90X (including 3c905B), 3c450, 3c55X, 3c575, 3c980, 3cSOHO100 -- Digital DC21x4x-based PCI Ethernet adapters ++oo Accton EN2242 ++oo ASUS PCI-DEC100TX+ ++oo Cogent EM1X0, EM960 (a.k.a. Adaptec ANA-69XX) ++oo Cogent EM964 [b] ++oo Cogent EM4XX [b] ++oo Compex Readylink PCI ++oo DANPEX EN-9400P3 ++oo Digital Celebris GL, GLST on-board ethernet ++oo DEC (Digital) PCI Ethernet/Fast Ethernet adapters (all) ++oo DLINK DFE500-TX ++oo JCIS Condor JC1260 ++oo Linksys PCI Fast Ethernet ++oo SMC EtherPower 10, 10/100 (PCI only!) ++oo SMC EtherPower^2 [b] ++oo SVEC PN0455 ++oo SVEC FD1000-TP ++oo Znyx ZX34X -- Digital EtherWORKS III ISA adapters (DE203/DE204/DE205) [*] -- Digital DEPCM-BA (PCMCIA) and DE305 (ISA) NE2000-compat. cards -- BICC Isolan [* and not recently tested] -- Efficient Networks EN-155 and Adaptec AIC-590x ATM inter- faces -- Essential Communications Hippi (800 Mbit/s) -- Fujitsu MB86960A/MB86965A based cards ++oo Fujitsu FMV-180 series ++oo Allied-Telesis AT1700 series ++oo Allied-Telesis RE2000 series -- Intel EtherExpress 16 -- Intel EtherExpress PRO/10 -- Intel EtherExpress 100 Fast Ethernet adapters -- Novell NE1000, NE2000 (ISA, PCI, PCMCIA, ISA PnP) -- RealTek 8129/8139 based boards -- SMC/WD 8003, 8013, and the SMC `Elite16' ISA boards -- SMC/WD 8216 (the SMC `Elite16 Ultra' ISA boards) -- SMC 91C9x-based boards (ISA and PCMCIA) -- SMC EPIC/100 Fast Ethernet boards ++oo SMC Etherpower-II -- Texas Instruments ThunderLAN based ethernet boards ++oo Compaq Netelligent 10/100 TX ++oo Compaq ProLiant Integrated Netelligent 10/100 TX ++oo Compaq Netelligent 10 T (untested) ++oo Compaq Integrated NetFlex 3/P ++oo Compaq NetFlex 3/P in baseboard variant (the PCI vari- ant doesn't use the same chip!) ++oo Compaq Dual Port Netelligent 10/100 TX ++oo Compaq Deskpro 4000 5233MMX (untested) ++oo Texas Instruments TravelMate 5000 series laptop docking station Ethernet board -- VIA VT3043 (Rhine) and VT86C100A (Rhine-II) based ethernet boards ++oo D-Link DFE530TX ++oo FDDI adapters -- Digital DEFPA PCI FDDI adapters [*] [+] -- Digital DEFEA EISA FDDI adapters [*] [+] ++oo Token-Ring adapters -- IBM Token-Ring Network PC Adapter [+] -- IBM Token-Ring Network PC Adapter II [+] -- IBM Token-Ring Network Adapter/A [+] -- IBM Token-Ring Network 16/4 Adapter [+] -- IBM Token-Ring Network 16/4 Adapter/A [+] [m] -- IBM 16/4 ISA Adapter [+] -- IBM Auto 16/4 Token-Ring ISA Adapter [+] -- 3COM 3C619 TokenLink [+] -- 3COM 3C319 TokenLink Velocity [+] ++oo Wireless network adapters -- 3Com AirConnect Wireless LAN -- AT&T/Lucent/Agere WaveLAN/ORiNOCO IEEE (802.11) PCMCIA cards -- Aironet 4500/4800 and Cisco 340 series PCMCIA cards -- BayStack 650 802.11FH PCMCIA cards -- Corega Wireless LAN PCC-11 cards -- DEC/Cabletron RoamAbout 802.11 DS High Rate cards -- ELSA AirLancer MC-11 card -- Intersil Prism II -- Melco AIR CONNECT WLI-PCM-L11 cards -- NetWave AirSurfer PCMCIA cards ++oo High Speed Serial -- LAN Media Corporation SSI/LMC10000 (up to 10 Mbps) [*] [+] -- LAN Media Corporation HSSI/LMC5200 [*] [+] -- LAN Media Corporation DS3/LMC5245 [*] [+] ++oo Tape drives -- Most SCSI tape drives -- QIC-02 and QIC-36 format (Archive- and Wangtek- compatible) tape drives [*] [+] ++oo CD-ROM drives -- Non-IDE Mitsumi CD-ROM drives [*] [+] _N_o_t_e_: The Mitsumi driver device probe is known to cause trouble with several devices! -- Most SCSI CD-ROM drives -- Most ATAPI CD-ROM drives. _N_o_t_e_: Some low-priced IDE CD-ROM drives are known for be- ing not or not fully ATAPI compliant, and thus re- quire some hack (generally an entry to a quirk table) to work with NetBSD. ++oo Mice -- ``Logitech'' -style bus mice [*] [+] -- Microsoft-style bus mice [*] [+] -- ``PS/2'' -style mice [*] [+] [m] -- Serial mice (no kernel support necessary) ++oo Sound Cards -- Aria based sound cards [*] -- Cirrus Logic CS461x, CS4280 and CS4281 audio [*] [+] -- Ensoniq AudioPCI [*] [+] -- ESS Technology ES1777/1868/1869/1887/1888/888, Maestro 1/2/2E and Solo-1 ES1938/1946 [*] [+] -- Gravis Ultrasound Plug and Play [*] [+] -- Gravis Ultrasound and Ultrasound Max [*] [+] -- NeoMagic MagicMedia 256AV / 256ZX AC'97 audio [*] [+] -- Personal Sound System [*] [+] -- ProAudio Spectrum [*] [+] -- S3 SonicVibes [*] [+] -- SoundBlaster, SoundBlaster Pro, SoundBlaster 16 [*] [+] -- VIA VT82C686A southbridge integrated AC97 audio [*] [+] -- Windows Sound System [*] [+] -- Yamaha YMF724/740/744/754 audio (DS-1 series) [*] [+] -- Yamaha OPL3-SA3 audio [*] [+] ++oo Game Ports (Joysticks) [*] [+] ++oo Miscellaneous -- Advanced power management (APM) [*] ++oo Universal Serial Bus (USB) -- UHCI host controllers [*] [+] -- OHCI host controllers [*] [+] -- Hubs [*] [+] -- Keyboards using the boot protocol [*] [+] -- Mice [*] [+] -- Printers [*] [+] -- Modems using Abstract Control Model [*] [+] -- Generic support for HID devices [*] [+] -- Ethernet adapters [*] [+] -- Audio devices [*] [+] -- driver for FTDI based serial adapters [*] [+] -- Mass storage devices such as disks, ZIP drives and digital cameras [*] [+] -- driver for the Prolific host-to-host adapter [*] [+] -- Handspring Visor driver [*] [+] ++oo PCMCIA Controllers. ISA, PCI, and ISA Plug and Play attachments -- Intel 82365 PCIC, rev 0 and rev 1 -- Cirrus PD6710 -- Cirrus PD672X _N_o_t_e_: This will work with most laptops as well as with ISA cards which provide PCMCIA slots for desktops. ++oo RAID Controllers -- Compaq Integrated Array (PCI) [b] -- Compaq IAES (EISA) -- Compaq IDA, IDA-2 (EISA) -- Compaq Smart Array 221, 3100ES, 3200, 4200, 4250ES (PCI) [b] -- Compaq Smart Array 431, RAID LC2 [b] -- Compaq SMART 2, 2/E (EISA) -- Compaq SMART 2/E, 2/P, 2DH, 2SL (PCI) [b] -- DPT SCSI RAID boards (ISA [*], EISA and PCI) ++oo SmartCache III ++oo SmartCache IV ++oo SmartRAID III ++oo SmartRAID IV Specific driver footnotes: [*] Drivers are _n_o_t present in kernels on the distribution floppies. Except as noted above, all drivers are present on all disks. Also, at the present time, the distributed kernels support only one SCSI host adapter per machine. NetBSD normally allows more, though, so if you have more than one, you can use all of them by compiling a custom kernel once NetBSD is installed. [+] Support _i_s included in the GENERIC kernels, although it is not in the kernels which are on the distribution floppies. [b] Devices require BIOS support for PCI-PCI bridging on your mother- board. Most reasonably modern Pentium motherboards have this sup- port, or can acquire it via a BIOS upgrade. [m] Devices are also supported by MCA-enabled kernels, such as one com- piled from the PS2 configuration file. Support for MCA is _n_o_t in the GENERIC or installation kernels at this moment. Hardware the we do _n_o_t currently support, but get many questions about: ++oo Multiprocessor systems. NetBSD will run, but only use one pro- cessor. ++oo PCI WD-7000 SCSI host adapters. ++oo QIC-40 and QIC-80 tape drives. (Drives that connect to the floppy disk controller.) We are planning future support for many of these devices. To be detected by the distributed kernels, the devices must be configured as follows: Device Name Port IRQ DRQ Misc ------ ---- ---- --- --- ---- Serial ports com0 0x3f8 4 [8250/16450/16550/clones] com1 0x2f8 3 [8250/16450/16550/clones] com2 0x3e8 5 [8250/16450/16550/clones] Parallel ports lpt0 0x378 7 [interrupt-driven or polling] lpt1 0x278 [polling only] lpt2 0x3bc [polling only] Floppy controller fdc0 0x3f0 6 2 [supports two disks] AHA-154x, AHA-174x (in compatibility mode), or BT-54x SCSI host adapters aha0 0x330 any any aha1 0x334 any any AHA-174x SCSI host adapters (in enhanced mode) ahb0 any any any AHA-152x, AIC-6260- or AIC-6360-based SCSI host adapters aic0 0x340 11 6 AHA-2X4X or AIC-7xxx-based SCSI host adapters [precise list: see NetBSD ahc0 any any any System Requirements and Supported Devices] AdvanSys ABP-9x0[U][A] SCSI host adapters adv0 any any any AdvanSys ABP-940UW[68], ABP-970UW[68], ASB3940UW-00 SCSI host adapters adw0 any any any AMD PCscsi-PCI based SCSI host adapters pcscp0 any any any BusLogic BT445, BT74x, or BT9xx SCSI host adapters bha0 0x330 any any bha1 0x334 any any Seagate/Future Domain SCSI sea0 any 5 any iomem 0xd8000 Symbios Logic/NCR 53C8xx based PCI SCSI host adapters ncr0 any any any Ultrastor 14f, 24f (if it works), or 34f SCSI host adapters uha0 0x330 any any uha1 0x340 any any Western Digital WD7000 based ISA SCSI host adapters wds0 0x350 15 6 wds1 0x358 11 5 PCI IDE hard disk controllers pciide0 any any any [supports four devices] MFM/ESDI/IDE/RLL hard disk controllers wdc0 0x1f0 14 [supports two devices] wdc1 0x170 15 [supports two devices] ATA disks wd0, wd1, ... SCSI and ATAPI disks sd0, sd1, ... SCSI tapes st0, st1, ... SCSI and ATAPI CD-ROMs cd0, cd1, ... For each SCSI and IDE controller found, the SCSI or ATA(PI) devices present on the bus are probed in increasing ID order for SCSI and master/slave order for ATA(PI). So the first SCSI drive found will be called sd0, the second sd1, and so on ... StarLAN cards ai0 0x360 7 any iomem 0xd0000 FMV-180 series cards fmv0 0x2a0 any AT1700 cards ate0 0x2a0 any Intel EtherExpress/16 cards ix0 0x300 10 Intel EtherExpress PRO 10 ISA cards iy0 0x360 any CS8900 Ethernet cards cs0 0x300 any any 3Com 3c501 Ethernet cards el0 0x300 9 3Com 3c503 Ethernet cards ec0 0x250 9 iomem 0xd8000 3Com 3c505 Ethernet cards eg0 0x280 9 3Com 3c507 Ethernet cards ef0 0x360 7 iomem 0xd0000 Novell NE1000, or NE2000 Ethernet boards ne0 0x280 9 ne1 0x300 10 Novell NE2100 Ethernet boards ne2 0x320 9 7 BICC IsoLan cards ne3 0x320 10 7 SMC/WD 8003, 8013, Elite16, and Elite16 Ultra Ethernet boards we0 0x280 9 iomem 0xd0000 we1 0x300 10 iomem 0xcc000 3COM 3c509 or 3COM 3c579 Ethernet boards ep0 any any 3COM 3x59X PCI Ethernet boards ep0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] 3COM 3x90X PCI Ethernet boards ex0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] Intel EtherExpress PRO 10 ISA iy0 0x360 any Intel EtherExpress 100 Fast Ethernet adapters fxp0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] SMC91C9x based Ethernet cards sm0 0x300 10 PCnet-PCI based Ethernet boards; see above for partial list le0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] DC21x4x based Ethernet boards; see above for partial list de0 any any [you must assign an interrupt in your PCI BIOS, or let it do so for you] Digital EtherWORKS III (DE203/DE204/DE205) LEMAC lc0 0x320 any Qlogic ISP [12]0x0 SCSI/FibreChannel boards isp0 any any Efficient Networks EN-155 and Adaptec AIC-590x ATM interfaces en0 any any SMC EPIC/100 Fast Ethernet boards epic0 any any Texas Instruments ThunderLAN based ethernet boards tl0 any any VIA VT3043(Rhine) and VT86C100A(Rhine-II) based ethernet boards vr0 any any IBM TROPIC based Token-Ring cards tr0 0xa20 any iomem 0xd8000 tr1 0xa24 any iomem 0xd0000 tr2 any any GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa If you are not booting off a CD-ROM, you will need to have some floppy disks to boot off; either two 1.44 MB floppies or one 1.2 MB floppy. For laptops that have cardbus slots, you should use the _b_o_o_t_l_a_p_1_._f_s and _b_o_o_t_l_a_p_2_._f_s floppy images. For older machines with little RAM, use _b_o_o_t_-_t_i_n_y_._f_s. This image is tai- lored towards old, small-memory systems, and thus does not contain any PCI or SCSI support. It should work on systems with 4M of RAM. Note that this means 4M available to NetBSD; systems that are said to have 4M may have 640k of base memory and 3072k of extended memory, which currently will not work, as this is a total of 3712k. For old machines that may have EISA, SCSI and more RAM, but only have an 1.2M floppy drive, use _b_o_o_t_-_s_m_a_l_l_._f_s. For all other systems, use _b_o_o_t_1_._f_s and _b_o_o_t_2_._f_s For the 2-floppy sets (and the CD boot image), utilities to repair a bad- ly crashed systems are included. The -small and -tiny images have seper- ate rescue floppy images because of lack of space. If you are using a UNIX-like system to write the floppy images to disks, you should use the dd command to copy the file system image(s) (.fs file) directly to the raw floppy disk. It is suggested that you read the dd(1) manual page or ask your system administrator to determine the correct set of arguments to use; it will be slightly different from system to system, and a comprehensive list of the possibilities is beyond the scope of this document. If you are using MS-DOS to write the floppy image(s) to floppy disk, you should use the rraawwrriittee utility, provided in the _i_3_8_6_/_u_t_i_l_i_t_i_e_s directory of the NetBSD distribution. It will write a file system image (.fs file) to a floppy disk. A rraawwrriittee3322 is also available that runs under MS Windows. Installation is supported from several media types, including: ++oo CD-ROM ++oo MS-DOS floppy ++oo FTP ++oo Remote NFS partition ++oo Tape ++oo Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation de- pend upon which installation medium you choose. The steps for the vari- ous media are outlined below. _C_D_-_R_O_M Find out where the distribution set files are on the CD- ROM. Proceed to the instruction on installation. _M_S_-_D_O_S _f_l_o_p_p_y Count the number of _s_e_t___n_a_m_e_._x_x files that make up the distribution sets you want to install or upgrade. You will need one fifth that number of 1.2 MB floppies, or one sixth that number of 1.44 MB floppies. You should only use one size of floppy for the install or upgrade proce- dure; you can't use some 1.2 MB floppies and some 1.44 MB floppies. Format all of the floppies with MS-DOS. Do _n_o_t make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distribution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box. Place all of the _s_e_t___n_a_m_e_._x_x files on the MS-DOS disks. Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the sec- tion on preparing your hard disk, below. If you're up- grading an existing installation, go directly to the sec- tion on upgrading. _F_T_P 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 upgrading NetBSD, you need to know the nu- meric IP address of the router closest to the NetBSD ma- chine. Finally, you need to know the numeric IP address of the NetBSD machine itself. If you don't have access to a functioning nameserver during installation, the IP ad- dress of ffttpp..nneettbbssdd..oorrgg is 204.152.184.75 (as of April, 2001). Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. _N_F_S Place the NetBSD distribution sets you wish to install in- to 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 _/_e_t_c_/_e_x_p_o_r_t_s file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine it- self. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on up- grading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. _U_p_g_r_a_d_e If you are upgrading NetBSD, you also have the option of installing 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. Please note that the _/_d_e_v on the floppy used for upgrades only knows about wd0, wd1, sd0, sd1, and sd2. If you have more than two IDE drives or more than three SCSI drives, you should take care not to place the sets on the high-numbered drives. At a bare minimum, you must upgrade the bbaassee and kkeerrnn bi- nary distributions, and so must put the bbaassee and kkeerrnn sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should _n_o_t upgrade the eettcc distribution; it contains contains system configura- tion 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. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn First and foremost, before beginning the installation process, _m_a_k_e _s_u_r_e _y_o_u _h_a_v_e _a _r_e_l_i_a_b_l_e _b_a_c_k_u_p of any data on your hard disk that you wish to keep. Mistakes in partitioning your hard disk may lead to data loss. Before you begin, you should be aware of the geometry issues that may arise in relation to your hard disk. First of all, you should know about sector size. You can count on this to be 512 bytes; other sizes are rare (and currently not supported). Of particular interest are the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders. Together they describe the disk geometry. The BIOS has a limit of 1024 cylinders and 63 sectors per track for doing BIOS I/O. This is because of the old programming interface to the BIOS that restricts these values. Most of the big disks currently being used have more than 1024 real cylinders. Some have more than 63 sectors per track. Therefore, the BIOS can be instructed to use a fake geometry that accesses most of the disk and the fake geometry has less than or equal to 1024 cylinders and less than or equal to 63 sectors. This is possible be- cause the disks can be addressed in a way that is not restricted to these values, and the BIOS can internally perform a translation. This can be activated in most modern BIOSes by using _L_a_r_g_e or _L_B_A mode for the disk. NetBSD does not have the mentioned limitations with regard to the geome- try. However, since the BIOS has to be used during startup, it is impor- tant to know about the geometry the BIOS uses. The NetBSD kernel should be on a part of the disk where it can be loaded using the BIOS, within the limitations of the BIOS geometry. The install program will check this for you, and will give you a chance to correct this if this is not the case. If you have not yet installed any other systems on the hard disk that you plan to install NetBSD on, or if you plan to use the disk entirely for NetBSD, you may wish to check your BIOS settings for the `Large' or `LBA' modes, and activate them for the hard disk in question. While they are not needed by NetBSD as such, doing so will remove the limitations men- tioned above, and will avoid hassle should you wish to share the disk with other systems. Do _n_o_t change these settings if you already have data on the disk that you want to preserve! In any case, it is wise to check your the BIOS settings for the hard disk geometry before beginning the installation, and write them down. While this should usually not be needed, it enables you to verify that the in- stall program determines these values correctly. The geometry that the BIOS uses will be referred to as the _B_I_O_S _g_e_o_m_e_t_r_y, the geometry that NetBSD uses is the _r_e_a_l _g_e_o_m_e_t_r_y. ssyyssiinnsstt, the NetBSD installation program, will try to discover both the real geometry and BIOS geometry. It is _i_m_p_o_r_t_a_n_t that ssyyssiinnsstt know the proper BIOS geometry to be able to get NetBSD to boot, regardless of where on your disk you put it. It is less of a concern if the disk is going to be used entirely for NetBSD. If you intend to have several OSes on your disk, this becomes a much larger issue. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m 1. _I_n_t_r_o_d_u_c_t_i_o_n Using ssyyssiinnsstt, 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 to be completed. Do not let this discourage you, the install program is not hard to use. 2. _P_o_s_s_i_b_l_e PCMCIA _i_s_s_u_e_s Machines with PCMCIA slots may have problems during installation. With the improvements of the PCMCIA code in this release, this will not happen very frequently. If you do not have PCMCIA on your ma- chine (PCMCIA is only really used on laptop machines), you can skip this section, and ignore the ``[PCMCIA]'' notes. If you do have PCMCIA in your machine, you can safely ignore this section and the ``[PCMCIA]'' the first time, as you are likely to not have problems. Should troubles occur during floppy boot, they may be PCMCIA specif- ic. You should then re-read this section and try again, following the instructions in the ``[PCMCIA]'' notes. This section explains how to work around the installation problem. The kernel keeps careful track of what interrupts and I/O ports are in use during autoconfiguration. It then allows the PCMCIA devices to pick unused interrupts and I/O ports. Unfortunately, the INSTALL kernel may not detect all devices in your system. This may be be- cause the INSTALL kernel only supports the minimum set of devices to install NetBSD on your system, or it may be that NetBSD does not have support for the device causing the conflict. For example, suppose your laptop has a soundblaster device built in; the INSTALL kernel has no sound support. The PCMCIA code might allocate your soundblaster's IRQ and I/O ports to PCMCIA devices, causing them not to work, or to lock up the system. This is espe- cially bad if one of the devices in question is your ethernet card. As of NetBSD 1.5, the kernel attempts to probe for available inter- rupts that are usable by the PCIC (PCMCIA interrupt controller). As- suming that this functions correctly, it should alleviate interrupt conflicts; however, I/O port conflicts are still possible. This problem will impact some, but not all, users of PCMCIA. If this problem is affecting you, watch the ``[PCMCIA]'' notes that will appear in this document. It can be difficult to distinguish an interrupt conflict from an I/O space conflict. There are no hard-and-fast rules, but interrupt con- flicts are more likely to lock up the machine, and I/O space con- flicts are more likely to result in misbehavior (e.g. a network card that cannot send or receive packets). The kernel selects a free interrupt according to a mask of allowable interrupts, stored in the kernel global variable _p_c_i_c___i_s_a___i_n_t_r___a_l_l_o_c___m_a_s_k. This mask is a logical-or of power-of-2s of allowable interrupts: IRQ Val IRQ Val IRQ Val IRQ Val 0 0x0001 4 0x0010 8 0x0100 12 0x1000 1 0x0002 5 0x0020 9 0x0200 13 0x2000 2 0x0004 6 0x0040 10 0x0400 14 0x4000 3 0x0008 7 0x0080 11 0x0800 15 0x8000 For example, 0x0a00 allows both IRQ 9 and IRQ 11. By default, the INSTALL kernel permits all IRQs other than IRQs 5 and 7, so the cor- responding mask is 0xff5f. The GENERIC kernel, however, allows all IRQs. (The presumption here is that IRQ 10 may be assigned to a de- vice that the GENERIC kernel supports, but that the INSTALL does not.) Because of support for interrupt probing, it is no longer nec- essary to exclude IRQs 3 and 5 explicitly; if they are in use, they should not be assigned to PCMCIA. The kernel selects IO space by assigning cards IO space within a predefined range. The range is specified as a base and size, speci- fied by the kernel global variables _p_c_i_c___i_s_a___a_l_l_o_c___i_o_b_a_s_e and _p_c_i_c___i_s_a___a_l_l_o_c___i_o_s_i_z_e. For systems with 12-bit addressing (most systems), the kernel defaults to a base of 0x400 and a size of 0xbff (a range of 0x400-0xfff). For systems with 10-bit addressing, the kernel defaults to a base of 0x300 and a size of 0xff (range of 0x300-0x3ff). Unfortunately, these ranges may conflict with some devices. In the event of a conflict, try a base of 0x330 with a size of 0x0bf (range of 0x330-0x3ff). In order to work around this at installation time, you may boot the INSTALL kernel with bboooott --dd, in order to enter ddb(4) (the in-kernel debugger), and then use the wwrriittee command to alter the variable val- ues: db> wwrriittee ppcciicc__iissaa__iinnttrr__aalllloocc__mmaasskk 00xx00aa0000 pcic_isa_intr_alloc_mask 0xff5f = 0xa00 db> wwrriittee ppcciicc__iissaa__aalllloocc__iioobbaassee 00xx333300 pcic_isa_alloc_iobase 0x400 = 0x330 db> wwrriittee ppcciicc__iissaa__aalllloocc__iioossiizzee 00xx00bbff pcic_isa_alloc_iosize 0xbff = 0xbf db> ccoonnttiinnuuee Note that, since some floppy images may not have symbol information in the kernel, you may have to consult the matching _._s_y_m_b_o_l_s file in the _b_i_n_a_r_y_/_k_e_r_n_e_l directory in the installation tree. Find the pcic_ symbols used above, look at the hexadecimal value in the first col- umn, and write, for example (if _p_c_i_c___i_s_a___i_n_t_r___a_l_l_o_c___m_a_s_k is equal to c0513e3c): db> wwrriittee 00xxcc00551133ee33cc 00xx00aa0000 After installation, this value can be permanently written to the kernel image directly with: # ccpp //nneettbbssdd //nneettbbssdd..bbaakk # ggddbb ----wwrriittee //nneettbbssdd (gdb) sseett ppcciicc__iissaa__iinnttrr__aalllloocc__mmaasskk==00xx00aa0000 (gdb) sseett ppcciicc__iissaa__aalllloocc__iioobbaassee==00xx333300 (gdb) sseett ppcciicc__iissaa__aalllloocc__iioossiizzee==00xx00bbff (gdb) qquuiitt # or you could specify these value when configuring your kernel, e.g.: options PCIC_ISA_INTR_ALLOC_MASK=0x0a00 options PCIC_ISA_ALLOC_IOBASE=0x330 options PCIC_ISA_ALLOC_IOSIZE=0x0bf If you can get your PCMCIA card to work using this hack, you may al- so ignore the [PCMCIA] notes later in this document. We hope to provide a more elegant solution to this problem in a fu- ture NetBSD release. 3. _G_e_n_e_r_a_l The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. ssyyssiinnsstt is a menu driv- en installation system that allows for some freedom in doing the in- stallation. 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 in- stallation process again from scratch, by running the _/_s_y_s_i_n_s_t pro- gram from the command prompt, you do not need to reboot. 4. _Q_u_i_c_k _i_n_s_t_a_l_l First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to section 3. This section describes a basic installa- tion, using a CD-ROM install as an example. ++oo What you need. -- The distribution sets (in this example, they are on CD). -- Two 1.44 MB 3.5" floppy disks. One 1.44 MB 3.5" floppy. -- A PC with a 386 or newer processor. -- A CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of 4 MB of memory installed. -- The harddisk should have at least 70 + _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. ++oo Creating the boot floppies. You can create the floppies needed for installation under MS-DOS or Windows. Supposing your 1.44 MB floppy drive is drive A:, and your CD is drive E: do the fol- lowing from an MS-DOS command prompt: ee:: ccdd \\NNeettBBSSDD--11..55..22\\ii338866\\iinnssttaallllaattiioonn\\mmiisscc rraawwrriittee When asked for a source filename, answer _._._\_f_l_o_p_p_y_\_b_o_o_t_1_._f_s for the first diskette and _._._\_f_l_o_p_p_y_\_b_o_o_t_2_._f_s for the second diskette. When asked for a destination drive answer `aa'. ++oo To create a bootfloppy under NetBSD or other UNIX-like system, you would type something like: # dddd iiff==......//bboooott11..ffss bbss==1188kk ooff==//ddeevv//rrffdd00aa ++oo The Quick Installation -- Insert the first boot floppy you just created. Restart the computer. When prompted, insert the second boot floppy. The main menu will be displayed. .***********************************************. * NetBSD-1.5.2 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 immedi- ately by choosing the UUttiilliittyy mmeennuu and then CCoonnffiigguurree nneettwwoorrkk. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. -- Choose iinnssttaallll. -- 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 CCDD--RROOMM 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 rreebboooott, after you have removed the bootflop- py from the drive. -- NetBSD will now boot. If you haven't already done so in ssyyssiinnsstt, you should log in as root, and set a password for that account. You are also advised to edit the file _/_e_t_c_/_r_c_._c_o_n_f to match your system needs. -- Your installation is now complete. -- For configuring the X window system, if installed, see the files in _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c. Further information can be found on hhttttpp::////wwwwww..xxffrreeee8866..oorrgg//. 5. _B_o_o_t_i_n_g _N_e_t_B_S_D [PCMCIA] Unplug your PCMCIA devices, so that they won't be found by NetBSD. Boot your machine. The boot loader will start, and will print a countdown and begin booting. If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that. If that doesn't work, try booting after disabling your CPU's inter- nal and external caches (if any). If it still doesn't work, NetBSD probably can't be run on your hardware. This can probably be consid- ered a bug, so you might want to report it. If you do, please in- clude as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, probably around a minute or so, then, the kernel boot messages will be dis- played. This may take a little while also, as NetBSD will be probing your system to discover which hardware devices are installed. You may want to read the boot messages, to notice your disk's name and geometry. Its name will be something like sd0 or wd0 and the geome- try will be printed on a line that begins with its name. As men- tioned above, you may need your disk's geometry when creating NetBSD 's partitions. You will also need to know the name, to tell ssyyssiinnsstt on which disk to install. The most important thing to know is that wd0 is NetBSD 's name for your first IDE disk, wd1 the sec- ond, etc. sd0 is your first SCSI disk, sd1 the second, etc. Note that once the system has finished booting, you need not leave the floppy in the disk drive. Earlier version of the NetBSD install floppies mounted the floppy as the system's root partition (_/), but the new installation floppies use a ramdisk file system and are no longer dependent on the floppy once it has booted. 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. 6. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n [PCMCIA] You can skip this section, as you will only get data from floppy in the first part of the install. 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 UUttiilliittyy mmeennuu , and select the CCoonnffiigguurree nneettwwoorrkk option. If you only want to temporarily use net- working during the installation, 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. 7. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s To start the installation, select IInnssttaallll NNeettBBSSDD ttoo hhaarrdd ddiisskk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. ssyyssiinnsstt 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 wd0, wd1, sd0 or sd1. ssyyssiinnsstt next tries to figure out the real and BIOS geometry of your disk. It will present you with the values it found, if any, and will give you a chance to change them. Next, depending on whether you are using a wd_X or sd_X disk, you will either be asked for the type of disk (wd_X) you are using or you will be asked if you want to specify a fake geometry for your SCSI disk (sd_X). The types of disk are be IDE, ST-506 or ESDI. If you're in- stalling on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are _s_u_r_e that it does, reply affirmatively. Otherwise, the install program will automati- cally reserve space for bad144 tables. 8. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k ++oo 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. If you want to use the entire disk for NetBSD, you can skip the following section and go to _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l. ++oo _E_d_i_t_i_n_g _t_h_e _M_a_s_t_e_r _B_o_o_t _R_e_c_o_r_d First, you will be prompted to specify the units of size that you want to express the sizes of the partitions in. You can ei- ther pick megabytes, cylinders or sectors. After this, you will be presented with the current values stored in the MBR, and will be given the opportunity to change, create or delete partitions. For each partition you can set the type, the start and the size. Setting the type to uunnuusseedd will delete a partition. You can also mark a partition as active, meaning that this is the one that the BIOS will start from at boot time. Be sure to mark the partition you want to boot from as active! After you are done editing the MBR, a sanity check will be done, checking for partitions that overlap. Depending on the BIOS ca- pabilities of your machine and the parameters of the NetBSD par- tition you have specified, you may also be asked if you want to install newer bootcode in your MBR. If you have multiple operat- ing systems on the disk that you are installing on, you will al- so be given the option to install a bootselector, that will al- low you to pick the operating system to start up when your com- puter is (re-)started. If everything is ok, you can go on to the next step, editing the NetBSD disklabel. ++oo _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l The partition table of the NetBSD part of a disk is called a _d_i_s_k_l_a_b_e_l. There are 3 layouts for the NetBSD part of the disk that you can pick from: SSttaannddaarrdd,, SSttaannddaarrdd wwiitthh XX and CCuussttoomm. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. The last option lets you specify everything yourself. 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 44..22BBSSDD. A swap partition has a special type called sswwaapp. You can also specify a partition as type MMSSDDOOSS. This is useful if you share the disk with MS-DOS or Windows; NetBSD is able to access the files on these partitions. You can use the values from the MBR for the MS-DOS part of the disk to specify the partition of type MMSSDDOOSS (you don't have to do this now, you can always re-edit the disklabel to add this once you have installed NetBSD ). Some partitions in the disklabel have a fixed purpose. a Root partition. (_/), b Swap partition. c The NetBSD portion of the disk. d The entire disk. d-h Available for other use. Traditionally, d is the partition mounted on _/_u_s_r, but this is historical practice and not a fixed value. You will then be asked to name your disk's disklabel. The de- fault response is mmyyddiisskk. 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. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. 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 pro- ceed, enter yes at the prompt. The install program will now label your disk and make the file sys- tems 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 running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key. _N_o_t_e_: In previous versions of NetBSD, the kernel from the install floppy was copied onto the hard drive in a special step. In the current install system, the kernel on the floppy is un- suited to being copied onto the hard drive. Instead, a new set, kkeerrnn, has been added which contains a generic kernel to be unloaded onto the drive. So, you can not boot from your hard drive yet at this point. 10. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s [PCMCIA] Load a kernel tar file (i.e. the _k_e_r_n_._t_g_z set file) on to your hard disk, for example by mounting the hard disk first, copying the _k_e_r_n_._t_g_z file from floppy and unpack- ing it. Example: # mmoouunntt //ddeevv//wwdd00aa //mmnntt # ccdd //mmnntt _r_e_p_e_a_t _t_h_e _f_o_l_l_o_w_i_n_g _3 _s_t_e_p_s _u_n_t_i_l _a_l_l _k_e_r_n_._* _f_i_l_e_s _a_r_e _t_h_e_r_e # mmoouunntt --tt mmssddooss //ddeevv//ffdd00aa //mmnntt22 # ccpp //mmnntt22//kkeerrnn..** .. # uummoouunntt //mmnntt22 # ccaatt kkeerrnn..** || ttaarr zzxxppvvff -- Then halt the machine using the hhaalltt command. Power the machine down, and re-insert all the PCMCIA devices. Re- move any floppy from the floppy drive. Start the ma- chine up. After booting NetBSD, you will be presented with the main ssyyssiinnsstt menu. Choose the option to re-in- stall sets. Wait for the file system checks that it will do to finish, and then proceed as described below. The NetBSD distribution consists of a number of _s_e_t_s, 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 installa- tion, you will be presented with a menu which enables you to choose from one of the following 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 using, you can continue to section labeled `Extracting the distribution sets'. 11. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _f_t_p 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. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice 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, and the account name and password used to log into that host using ftp. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server. ssyyssiinnsstt will proceed to transfer all the default set files from the remote site to your hard disk. 12. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S 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. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice 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 networking, you will need to specify an IP address instead of a hostname for the NFS server. 13. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M When installing from a CD-ROM, you will be asked to specify the de- vice name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are. ssyyssiinnsstt will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 14. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _f_l_o_p_p_y _s_e_t Because the installation sets are too big to fit on one floppy, the floppies are expected to be filled with the split set files. The floppies are expected to be in MS-DOS format. You will be asked for a directory where the sets should be reassembled. Then you will be prompted to insert the floppies containing the split sets. This pro- cess will continue until all the sets have been loaded from floppy. 15. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m In order to install from a local file system, you will need to spec- ify 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. ssyyssiinnsstt will then check if it can indeed access the sets at that location. 16. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y 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 already accessible. ssyyssiinnsstt will ask you for the name of this directory. 17. _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full instal- lation), 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 (kkeerrnn,, bbaassee and eettcc) they will not be shown in this selec- tion menu. Before extraction begins, you can elect to watch the files being ex- tracted; 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 network- ing, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the net- work 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 can set a password for the "root" ac- count, to prevent the machine coming up without access restrictions. 18. _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n Congratulations, you have successfully installed NetBSD 1.5.2. You can now reboot the machine, and boot NetBSD from harddisk. PPoosstt iinnssttaallllaattiioonn sstteeppss 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 _/_e_t_c_/_r_c_._c_o_n_f If you or the installation software haven't done any configuration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt usually will), the system will drop you in- to single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (_/) mounted read-write. When the sys- tem asks you to choose a shell, simply press RETURN to get to a _/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with vvtt222200 (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: # ssttttyy eerraassee ''^^hh'' # ssttttyy eerraassee ''^^??'' At this point, you need to configure at least one file in the _/_e_t_c directory. You will need to mount your root filesystem read/write with: # //ssbbiinn//mmoouunntt --uu --ww // Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). If your _/_u_s_r directory is on a separate partition and you do not know how to use eedd, you will have to mount your _/_u_s_r partition to gain access to eexx or vvii. Do the following: # mmoouunntt //uussrr # eexxppoorrtt TTEERRMM==vvtt222200 If you have _/_v_a_r on a separate partition, you need to repeat that step for it. After that, you can edit _/_e_t_c_/_r_c_._c_o_n_f with vi(1). When you have finished, type eexxiitt at the prompt to leave the single-user shell and continue with the multi-user boot. Other values that need to be set in _/_e_t_c_/_r_c_._c_o_n_f for a networked en- vironment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e, furthermore add an _i_f_c_o_n_f_i_g___i_n_t for your network interface, along the lines of ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s: ifconfig_de0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Other files in _/_e_t_c that may require modification or setting up in- clude _/_e_t_c_/_m_a_i_l_e_r_._c_o_n_f, _/_e_t_c_/_n_s_s_w_i_t_c_h_._c_o_n_f, and _/_e_t_c_/_w_s_c_o_n_s_._c_o_n_f. 2. Logging in After reboot, you can log in as root at the login prompt. Unless you've set a password in ssyyssiinnsstt, there is no initial password. If you're using the machine in a networked environment, you should cre- ate an account for yourself (see below) and protect it and the ``root'' account with good passwords. 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, _d_o _n_o_t edit _/_e_t_c_/_p_a_s_s_w_d 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 _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c for information. You will need to set up a configuration file, see _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_X_F_8_6_C_o_n_f_i_g_._e_g for an example. The xf86config(1) utility can interactively create a first version of such a configu- ration file for you. See hhttttpp::////wwwwww..xxffrreeee8866..oorrgg// and the XFree86 manual page for more information. Don't forget to add _/_u_s_r_/_X_1_1_R_6_/_b_i_n to your path in your shell's dot file so that you have access to the X binaries. 5. Installing third party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies in- stallation (and deinstallation), both from source and precompiled binaries. ++oo More information on the package system is at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll ++oo A browsable listing of available packages is at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//RREEAADDMMEE..hhttmmll ++oo Precompiled binaries can be found at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess, usually in the _1_._5_._2_/_i_3_8_6_/_A_l_l subdir. You can install them with the following commands: ## eexxppoorrtt PPKKGG__PPAATTHH==ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..55..22//ii338866//AAllll ## ppkkgg__aadddd --vv ttccsshh ## ppkkgg__aadddd --vv ccvvss ## ppkkgg__aadddd --vv aappaacchhee ## ppkkgg__aadddd --vv ppeerrll ... The above commands will install the tcsh shell, the CVS source code management system, the Apache web server and the perl pro- gramming language as well as all the packages they depend on. ++oo Package sources for compiling packages on your own can be ob- tained by retrieving the file ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD-- ccuurrrreenntt//ttaarr__ffiilleess//ppkkggssrrcc..ttaarr..ggzz They are typically extracted into _/_u_s_r_/_p_k_g_s_r_c (though other lo- cations work fine), with the commands: # mmkkddiirr //uussrr//ppkkggssrrcc # (( ccdd //uussrr//ppkkggssrrcc ;; ttaarr --zzxxppff -- )) << ppkkggssrrcc..ttaarr..ggzz After extracting, then see the _R_E_A_D_M_E file in the extraction di- rectory (e.g. _/_u_s_r_/_p_k_g_s_r_c_/_R_E_A_D_M_E) for more information. 6. Misc ++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. ++oo The _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f file will almost definitely need to be adjusted; files aiding in this can be found in _/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l. See the README file there for more infor- mation. ++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use. ++oo Many of the _/_e_t_c files are documented in section 5 of the manu- al; so just invoking # mmaann 55 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm The upgrade to NetBSD 1.5.2 is a binary upgrade; it can be quite diffi- cult to advance to a later version by recompiling from source due primar- ily to interdependencies in the various components. To do the upgrade, you must have the boot floppy available. You must al- so have at least the bbaassee and kkeerrnn binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods de- scribed above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previ- ously on the system. If you have a few megabytes free on each of your root (_/) and _/_u_s_r partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your NetBSD parti- tion, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to _b_a_c_k _u_p _a_n_y _i_m_p_o_r_t_a_n_t _d_a_t_a _o_n _y_o_u_r _d_i_s_k, whether on the NetBSD partition or on another operat- ing system's partition, before beginning the upgrade process. The upgrade procedure using the ssyyssiinnsstt tool is similar to an installa- tion, but without the hard disk partitioning. The original _/_e_t_c directo- ry is renamed to _/_e_t_c_._o_l_d, and no attempt is made to merge any of the previous configuration into the new system except that the previous _/_e_t_c_/_f_s_t_a_b file is copied into the new configuration. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some san- ity checks are done, i.e. file systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.5.2 system. However, that doesn't mean that you're fin- ished with the upgrade process. You will probably want to update the set of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v by hand, you will need to be careful about this, but if not, you can just cd into _/_d_e_v, and run the command: # sshh MMAAKKEEDDEEVV aallll You must also deal with certain changes in the formats of some of the configuration files. The most notable change is that the options given to many of the file systems in _/_e_t_c_/_f_s_t_a_b have changed, and some of the file systems have changed names. To find out what the new options are, it's suggested that you read the manual page for the file system's mount com- mands, for example mount_nfs(8) for NFS. Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. NetBSD/i386 has switched its executable format from the old a.out format to ELF, the now more commonly used and supported format. Your old bina- ries will continue to work just fine. The installation procedure will try to take the necessary steps to accomplish this. The most important step is to move the old a.out shared libraries in _/_u_s_r_/_l_i_b and _/_u_s_r_/_X_1_1_R_6_/_l_i_b (if X was installed) to _/_e_m_u_l_/_a_o_u_t, where they will be automatically found if an older a.out binary is executed. Sysinst will use an existing _/_e_m_u_l and / or _/_e_m_u_l_/_a_o_u_t directory if available, and will create it (as a symbolic link to _/_u_s_r_/_a_o_u_t) if necessary. If you already had a _/_e_m_u_l directory, or a symbolic link by that name, sysinst should rename it and tell you about it. CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.5.2. _G_e_n_e_r_a_l _i_s_s_u_e_s ++oo _/_e_t_c_/_r_c modified to use _/_e_t_c_/_r_c_._d_/_* Prior to NetBSD 1.5, _/_e_t_c_/_r_c was a traditional BSD style monolithic file; each discrete program or substem from _/_e_t_c_/_r_c and _/_e_t_c_/_n_e_t_s_t_a_r_t has been moved into separate scripts in _/_e_t_c_/_r_c_._d_/. At system startup, _/_e_t_c_/_r_c uses rcorder(8) to build a dependency list of the files in _/_e_t_c_/_r_c_._d and then executes each script in turn with an argument of `start'. Many _r_c_._d scripts won't start unless the ap- propriate rc.conf(5) entry in _/_e_t_c_/_r_c_._c_o_n_f is set to `YES.' At system shutdown, _/_e_t_c_/_r_c_._s_h_u_t_d_o_w_n uses rcorder(8) to build a de- pendency list of the files in _/_e_t_c_/_r_c_._d that have a ``KEYWORD: shutdown'' line, reverses the resulting list, and then executes each script in turn with an argument of `stop'. The following scripts support a specific shutdown method: _c_r_o_n, _i_n_e_t_d, _l_o_c_a_l, and _x_d_m. Local and third-party scripts may be installed into _/_e_t_c_/_r_c_._d as nec- essary. Refer to the other scripts in that directory and rc(8) for more information on implementing _r_c_._d scripts. _I_s_s_u_e_s _a_f_f_e_c_t_i_n_g _a_n _u_p_g_r_a_d_e _f_r_o_m _N_e_t_B_S_D _1_._4 _o_r _p_r_i_o_r ++oo named(8) leaks version information Previous releases of NetBSD disabled a feature of named(8) where the version number of the server could be determined by remote clients. This feature has not been disabled in NetBSD 1.5, because there is a named.conf(5) option to change the version string: option { version "newstring"; }; ++oo sysctl(8) pathname changed sysctl(8) is moved from _/_u_s_r_/_s_b_i_n_/_s_y_s_c_t_l to _/_s_b_i_n_/_s_y_s_c_t_l. If you have hardcoded references to the full pathname (in shell scripts, for example) please be sure to update those. ++oo sendmail(8) configuration file pathname changed Due to sendmail(8) upgrade from 8.9.x to 8.10.x, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_f is moved to _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f. Also, the default sendmail.cf(5) refers different pathnames than before. For example, _/_e_t_c_/_a_l_i_a_s_e_s is now located at _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_w is now called _/_e_t_c_/_m_a_i_l_/_l_o_c_a_l_-_h_o_s_t_-_n_a_m_e_s, and so forth. If you have customized sendmail.cf(5) and friends, you will need to move the files to the new locations. See _/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l_/_R_E_A_D_M_E for more information. UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn 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 ++oo intro(1), ++oo man(1), ++oo apropros(1), ++oo passwd(1), and ++oo 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 _m_a_n command is used to view the documentation on a topic, and is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c. The brackets [] around the sec- tion should not be entered, but rather indicate that the section is op- tional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after log- ging in, enter # mmaann ppaasssswwdd to read the documentation for passwd(1). To view the documentation for passwd(5), enter # mmaann 55 ppaasssswwdd instead. If you are unsure of what man page you are looking for, enter aapprrooppooss _s_u_b_j_e_c_t_-_w_o_r_d where _s_u_b_j_e_c_t_-_w_o_r_d is your topic of interest; a list of possibly related man pages will be displayed. AAddmmiinniissttrriivviiaa If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at _m_a_j_o_r_d_o_m_o_@_n_e_t_b_s_d_._o_r_g. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instruc- tions. There are various mailing lists set up to deal with comments and ques- tions about this release. Please send comments to: _n_e_t_b_s_d_- _c_o_m_m_e_n_t_s_@_n_e_t_b_s_d_._o_r_g. To report bugs, use the send-pr(1) command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports in- clude lots of details. Additionally, bug reports can be sent by mail to: _n_e_t_b_s_d_-_b_u_g_s_@_n_e_t_b_s_d_._o_r_g. 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 hhttttpp::////wwwwww..nneettbbssdd..oorrgg//MMaaiilliinnggLLiissttss//. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed be- low). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: _n_e_t_b_s_d_-_h_e_l_p_@_n_e_t_b_s_d_._o_r_g. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. TThhaannkkss ggoo ttoo ++oo The former members of UCB's Computer Systems Research Group, includ- ing (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. ++oo 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. ++oo UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. ++oo Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers. ++oo Redback Networks, Inc. for hosting the NetBSD mail and GNATS server. ++oo The Helsinki University of Technology in Finland for hosting the NetBSD CVS server. ++oo The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. ++oo The many organisations that provide NetBSD mirror sites. ++oo 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. ++oo Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. ++oo The following individuals and organizations (each in alphabetical or- der) have made donations or loans of hardware and/or money, to sup- port NetBSD development, and deserve credit for it: Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard S/oren J/orvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise 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.) ++oo Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) WWee aarree...... (in alphabetical order) _T_h_e _N_e_t_B_S_D _c_o_r_e _g_r_o_u_p_: Alistair Crooks _a_g_c_@_n_e_t_b_s_d_._o_r_g Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g Luke Mewburn _l_u_k_e_m_@_n_e_t_b_s_d_._o_r_g Christos Zoulas _c_h_r_i_s_t_o_s_@_n_e_t_b_s_d_._o_r_g _T_h_e _p_o_r_t_m_a_s_t_e_r_s _(_a_n_d _t_h_e_i_r _p_o_r_t_s_)_: Mark Brinicombe _m_a_r_k_@_n_e_t_b_s_d_._o_r_g aarrmm3322 Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g ssuunn33xx Matt Fredette _f_r_e_d_e_t_t_e_@_n_e_t_b_s_d_._o_r_g ssuunn22 Ross Harvey _r_o_s_s_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g sshh33 Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g aarrmm2266 Eduardo Horvath _e_e_h_@_n_e_t_b_s_d_._o_r_g ssppaarrcc6644 Darrin Jewell _d_b_j_@_n_e_t_b_s_d_._o_r_g nneexxtt6688kk S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ccoobbaalltt S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ssggiimmiippss Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g mmiippssccoo Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g ssppaarrcc Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g vvaaxx Minoura Makoto _m_i_n_o_u_r_a_@_n_e_t_b_s_d_._o_r_g xx6688kk Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g ppcc553322 Tohru Nishimura _n_i_s_i_m_u_r_a_@_n_e_t_b_s_d_._o_r_g lluunnaa6688kk NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g pprreepp Scott Reynolds _s_c_o_t_t_r_@_n_e_t_b_s_d_._o_r_g mmaacc6688kk Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g bbeebbooxx Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g aarrcc Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g ooffppppcc Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g aammiiggaa Jonathan Stone _j_o_n_a_t_h_a_n_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Shin Takemura _t_a_k_e_m_u_r_a_@_n_e_t_b_s_d_._o_r_g hhppccmmiippss Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g hhpp330000 Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g mmaaccppppcc Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g nneewwssmmiippss Izumi Tsutsui _t_s_u_t_s_u_i_@_n_e_t_b_s_d_._o_r_g nneewwss6688kk Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g ii338866 Leo Weppelman _l_e_o_@_n_e_t_b_s_d_._o_r_g aattaarrii Nathan Williams _n_a_t_h_a_n_w_@_n_e_t_b_s_d_._o_r_g ssuunn33 Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmee6688kk _T_h_e _N_e_t_B_S_D _1_._5_._2 _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_: Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g John Hawkinson _j_h_a_w_k_@_n_e_t_b_s_d_._o_r_g Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g _D_e_v_e_l_o_p_e_r_s _a_n_d _o_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_: Nathan Ahlstrom _n_r_a_@_N_e_t_B_S_D_._o_r_g Steve Allen _w_o_r_m_e_y_@_n_e_t_b_s_d_._o_r_g Julian Assange _p_r_o_f_f_@_n_e_t_b_s_d_._o_r_g Lennart Augustsson _a_u_g_u_s_t_s_s_@_n_e_t_b_s_d_._o_r_g Christoph Badura _b_a_d_@_n_e_t_b_s_d_._o_r_g Dieter Baron _d_i_l_l_o_@_n_e_t_b_s_d_._o_r_g Robert V. Baron _r_v_b_@_n_e_t_b_s_d_._o_r_g Jason Beegan _j_t_b_@_n_e_t_b_s_d_._o_r_g Erik Berls _c_y_b_e_r_@_n_e_t_b_s_d_._o_r_g John Birrell _j_b_@_n_e_t_b_s_d_._o_r_g Mason Loring Bliss _m_a_s_o_n_@_n_e_t_b_s_d_._o_r_g Rafal Boni _r_a_f_a_l_@_n_e_t_b_s_d_._o_r_g Manuel Bouyer _b_o_u_y_e_r_@_n_e_t_b_s_d_._o_r_g John Brezak _b_r_e_z_a_k_@_n_e_t_b_s_d_._o_r_g Allen Briggs _b_r_i_g_g_s_@_n_e_t_b_s_d_._o_r_g Aaron Brown _a_b_r_o_w_n_@_n_e_t_b_s_d_._o_r_g Andrew Brown _a_t_a_t_a_t_@_n_e_t_b_s_d_._o_r_g David Brownlee _a_b_s_@_n_e_t_b_s_d_._o_r_g Frederick Bruckman _f_r_e_d_b_@_n_e_t_b_s_d_._o_r_g Jon Buller _j_o_n_b_@_n_e_t_b_s_d_._o_r_g Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t Robert Byrnes _b_y_r_n_e_s_@_n_e_t_b_s_d_._o_r_g D'Arcy J.M. Cain _d_a_r_c_y_@_n_e_t_b_s_d_._o_r_g Dave Carrel _c_a_r_r_e_l_@_n_e_t_b_s_d_._o_r_g James Chacon _j_m_c_@_n_e_t_b_s_d_._o_r_g Bill Coldwell _b_i_l_l_c_@_n_e_t_b_s_d_._o_r_g Julian Coleman _j_d_c_@_n_e_t_b_s_d_._o_r_g Chuck Cranor _c_h_u_c_k_@_n_e_t_b_s_d_._o_r_g Aidan Cully _a_i_d_a_n_@_n_e_t_b_s_d_._o_r_g Johan Danielsson _j_o_d_a_@_n_e_t_b_s_d_._o_r_g Matt DeBergalis _d_e_b_e_r_g_@_n_e_t_b_s_d_._o_r_g Rob Deker _d_e_k_e_r_@_n_e_t_b_s_d_._o_r_g Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g Jarom'ir Dolecek _j_d_o_l_e_c_e_k_@_n_e_t_b_s_d_._o_r_g Andy Doran _a_d_@_n_e_t_b_s_d_._o_r_g Roland Dowdeswell _e_l_r_i_c_@_n_e_t_b_s_d_._o_r_g Emmanuel Dreyfus _m_a_n_u_@_n_e_t_b_s_d_._o_r_g Matthias Drochner _d_r_o_c_h_n_e_r_@_n_e_t_b_s_d_._o_r_g Jun Ebihara _j_u_n_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Enami Tsugutomo _e_n_a_m_i_@_n_e_t_b_s_d_._o_r_g Bernd Ernesti _v_e_e_g_o_@_n_e_t_b_s_d_._o_r_g Erik Fair _f_a_i_r_@_n_e_t_b_s_d_._o_r_g Hubert Feyrer _h_u_b_e_r_t_f_@_n_e_t_b_s_d_._o_r_g Jason R. Fink _j_r_f_@_n_e_t_b_s_d_._o_r_g Thorsten Frueauf _f_r_u_e_a_u_f_@_n_e_t_b_s_d_._o_r_g Castor Fu _c_a_s_t_o_r_@_n_e_t_b_s_d_._o_r_g Ichiro Fukuhara _i_c_h_i_r_o_@_n_e_t_b_s_d_._o_r_g Brian R. Gaeke _b_r_g_@_d_g_a_t_e_._o_r_g Thomas Gerner _t_h_o_m_a_s_@_n_e_t_b_s_d_._o_r_g Simon J. Gerraty _s_j_g_@_n_e_t_b_s_d_._o_r_g Justin Gibbs _g_i_b_b_s_@_n_e_t_b_s_d_._o_r_g Adam Glass _g_l_a_s_s_@_n_e_t_b_s_d_._o_r_g Michael Graff _e_x_p_l_o_r_e_r_@_n_e_t_b_s_d_._o_r_g Brad Grantham _g_r_a_n_t_h_a_m_@_t_e_n_o_n_._c_o_m Brian C. Grayson _b_g_r_a_y_s_o_n_@_n_e_t_b_s_d_._o_r_g Matthew Green _m_r_g_@_n_e_t_b_s_d_._o_r_g Juergen Hannken-Illjes _h_a_n_n_k_e_n_@_n_e_t_b_s_d_._o_r_g Charles M. Hannum _m_y_c_r_o_f_t_@_n_e_t_b_s_d_._o_r_g Eric Haszlakiewicz _e_r_h_@_n_e_t_b_s_d_._o_r_g John Hawkinson _j_h_a_w_k_@_n_e_t_b_s_d_._o_r_g HAYAKAWA Koichi _h_a_y_a_@_n_e_t_b_s_d_._o_r_g Ren'e Hexel _r_h_@_n_e_t_b_s_d_._o_r_g Michael L. Hitch _m_h_i_t_c_h_@_n_e_t_b_s_d_._o_r_g Christian E. Hopps _c_h_o_p_p_s_@_n_e_t_b_s_d_._o_r_g Ken Hornstein _k_e_n_h_@_n_e_t_b_s_d_._o_r_g Marc Horowitz _m_a_r_c_@_n_e_t_b_s_d_._o_r_g Nick Hudson _s_k_r_l_l_@_n_e_t_b_s_d_._o_r_g Martin Husemann _m_a_r_t_i_n_@_n_e_t_b_s_d_._o_r_g Dean Huxley _d_e_a_n_@_n_e_t_b_s_d_._o_r_g Bernardo Innocenti _b_e_r_n_i_e_@_n_e_t_b_s_d_._o_r_g ITOH Yasufumi _i_t_o_h_y_@_n_e_t_b_s_d_._o_r_g IWAMOTO Toshihiro _t_o_s_h_i_i_@_n_e_t_b_s_d_._o_r_g Matthew Jacob _m_j_a_c_o_b_@_n_e_t_b_s_d_._o_r_g Lonhyn T. Jasinskyj _l_o_n_h_y_n_@_n_e_t_b_s_d_._o_r_g Chris Jones _c_j_o_n_e_s_@_n_e_t_b_s_d_._o_r_g Takahiro Kambe _t_a_c_a_@_n_e_t_b_s_d_._o_r_g Antti Kantee _p_o_o_k_a_@_n_e_t_b_s_d_._o_r_g Masanori Kanaoka _k_a_n_a_o_k_a_@_n_e_t_b_s_d_._o_r_g KAWAMOTO Yosihisa _k_a_w_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g Mario Kemper _m_a_g_i_c_k_@_n_e_t_b_s_d_._o_r_g Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u Thomas Klausner _w_i_z_@_n_e_t_b_s_d_._o_r_g Klaus Klein _k_l_e_i_n_k_@_n_e_t_b_s_d_._o_r_g Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g John Kohl _j_t_k_@_n_e_t_b_s_d_._o_r_g Kevin Lahey _k_m_l_@_n_e_t_b_s_d_._o_r_g Johnny C. Lam _j_l_a_m_@_n_e_t_b_s_d_._o_r_g Martin J. Laubach _m_j_l_@_n_e_t_b_s_d_._o_r_g Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g Joel Lindholm _j_o_e_l_@_n_e_t_b_s_d_._o_r_g Mike Long _m_i_k_e_l_@_n_e_t_b_s_d_._o_r_g Warner Losh _i_m_p_@_n_e_t_b_s_d_._o_r_g Tomasz Luchowski _z_u_n_t_u_m_@_n_e_t_b_s_d_._o_r_g Federico Lupi _f_e_d_e_r_i_c_o_@_n_e_t_b_s_d_._o_r_g Brett Lymn _b_l_y_m_n_@_n_e_t_b_s_d_._o_r_g Paul Mackerras _p_a_u_l_u_s_@_n_e_t_b_s_d_._o_r_g MAEKAWA Masahide _g_e_h_e_n_n_a_@_n_e_t_b_s_d_._o_r_g David Maxwell _d_a_v_i_d_@_n_e_t_b_s_d_._o_r_g Dan McMahill _d_m_c_m_a_h_i_l_l_@_n_e_t_b_s_d_._o_r_g Gregory McGarry _g_m_c_g_a_r_r_y_@_n_e_t_b_s_d_._o_r_g Neil J. McRae _n_e_i_l_@_n_e_t_b_s_d_._o_r_g Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g der Mouse _m_o_u_s_e_@_n_e_t_b_s_d_._o_r_g Joseph Myers _j_s_m_@_n_e_t_b_s_d_._o_r_g Ken Nakata _k_e_n_n_@_n_e_t_b_s_d_._o_r_g Bob Nestor _r_n_e_s_t_o_r_@_n_e_t_b_s_d_._o_r_g NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g Jesse Off _j_o_f_f_@_n_e_t_b_s_d_._o_r_g Tatoku Ogaito _t_a_c_h_a_@_n_e_t_b_s_d_._o_r_g Masaru Oki _o_k_i_@_n_e_t_b_s_d_._o_r_g Atsushi Onoe _o_n_o_e_@_n_e_t_b_s_d_._o_r_g Greg Oster _o_s_t_e_r_@_n_e_t_b_s_d_._o_r_g Herb Peyerl _h_p_e_y_e_r_l_@_n_e_t_b_s_d_._o_r_g Matthias Pfaller _m_a_t_t_h_i_a_s_@_n_e_t_b_s_d_._o_r_g Dante Profeta _d_a_n_t_e_@_n_e_t_b_s_d_._o_r_g Chris Provenzano _p_r_o_v_e_n_@_n_e_t_b_s_d_._o_r_g Michael Rauch _m_r_a_u_c_h_@_n_e_t_b_s_d_._o_r_g Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t Darren Reed _d_a_r_r_e_n_r_@_n_e_t_b_s_d_._o_r_g Michael Richardson _m_c_r_@_n_e_t_b_s_d_._o_r_g Tim Rightnour _g_a_r_b_l_e_d_@_n_e_t_b_s_d_._o_r_g Gordon Ross _g_w_r_@_n_e_t_b_s_d_._o_r_g Heiko W. Rupp _h_w_r_@_n_e_t_b_s_d_._o_r_g SAITOH Masanobu _m_s_a_i_t_o_h_@_n_e_t_b_s_d_._o_r_g Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g Wilfredo Sanchez _w_s_a_n_c_h_e_z_@_n_e_t_b_s_d_._o_r_g Ty Sarna _t_s_a_r_n_a_@_n_e_t_b_s_d_._o_r_g SATO Kazumi _s_a_t_o_@_n_e_t_b_s_d_._o_r_g Matthias Scheler _t_r_o_n_@_n_e_t_b_s_d_._o_r_g Karl Schilke (rAT) _r_a_t_@_n_e_t_b_s_d_._o_r_g Konrad Schroder _p_e_r_s_e_a_n_t_@_n_e_t_b_s_d_._o_r_g Reed Shadgett _d_e_n_t_@_n_e_t_b_s_d_._o_r_g Tim Shepard _s_h_e_p_@_n_e_t_b_s_d_._o_r_g Takao Shinohara _s_h_i_n_@_n_e_t_b_s_d_._o_r_g Takuya SHIOZAKI _t_s_h_i_o_z_a_k_@_n_e_t_b_s_d_._o_r_g Chuck Silvers _c_h_s_@_n_e_t_b_s_d_._o_r_g Thor Lancelot Simon _t_l_s_@_n_e_t_b_s_d_._o_r_g Jeff Smith _j_e_f_f_s_@_n_e_t_b_s_d_._o_r_g Bill Sommerfeld _s_o_m_m_e_r_f_e_l_d_@_n_e_t_b_s_d_._o_r_g Bill Squier _g_r_o_o_@_n_e_t_b_s_d_._o_r_g Bill Studenmund _w_r_s_t_u_d_e_n_@_n_e_t_b_s_d_._o_r_g Kevin Sullivan _s_u_l_l_i_v_a_n_@_n_e_t_b_s_d_._o_r_g SUNAGAWA Keiki _k_e_i_@_n_e_t_b_s_d_._o_r_g Kimmo Suominen _k_i_m_@_n_e_t_b_s_d_._o_r_g TAMURA Kent _k_e_n_t_@_n_e_t_b_s_d_._o_r_g Shin'ichiro TAYA _t_a_y_a_@_n_e_t_b_s_d_._o_r_g Matt Thomas _m_a_t_t_@_n_e_t_b_s_d_._o_r_g Christoph Toshok _t_o_s_h_o_k_@_n_e_t_b_s_d_._o_r_g UCHIYAMA Yasushi _u_c_h_@_n_e_t_b_s_d_._o_r_g Shuichiro URATA _u_r_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g Aymeric Vincent _a_y_m_e_r_i_c_@_n_e_t_b_s_d_._o_r_g Paul Vixie _v_i_x_i_e_@_n_e_t_b_s_d_._o_r_g Krister Walfridsson _k_r_i_s_t_e_r_w_@_n_e_t_b_s_d_._o_r_g Lex Wennmacher _w_e_n_n_m_a_c_h_@_n_e_t_b_s_d_._o_r_g Assar Westerlund _a_s_s_a_r_@_n_e_t_b_s_d_._o_r_g Todd Whitesel _t_o_d_d_p_w_@_n_e_t_b_s_d_._o_r_g Rob Windsor _w_i_n_d_s_o_r_@_n_e_t_b_s_d_._o_r_g Dan Winship _d_a_n_w_@_n_e_t_b_s_d_._o_r_g Jim Wise _j_w_i_s_e_@_n_e_t_b_s_d_._o_r_g Michael Wolfson _m_b_w_@_n_e_t_b_s_d_._o_r_g Colin Wood _e_n_d_e_r_@_n_e_t_b_s_d_._o_r_g YAMAMOTO Takashi _y_a_m_t_@_n_e_t_b_s_d_._o_r_g Yuji Yamano _y_y_a_m_a_n_o_@_n_e_t_b_s_d_._o_r_g Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g LLeeggaall MMuummbboo--JJuummbboo All product names mentioned herein are trademarks or registered trade- marks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by The NetBSD Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product in- cludes 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 devel- oped by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Al- istair 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 devel- oped by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural Col- lege and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contribu- tors. 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 prod- uct includes software developed by Christopher G. Demetriou. This prod- uct includes software developed by Christos Zoulas. This product in- cludes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes soft- ware developed by Eric S. Hvozda. This product includes software devel- oped 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 soft- ware developed by HAYAKAWA Koichi. This product includes software devel- oped by Hellmuth Michaelis and Joerg Wunsch. This product includes soft- ware developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operat- ing systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software de- veloped by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software de- veloped by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This prod- uct includes software developed by Kenneth Stailey. This product in- cludes software developed by Leo Weppelman. This product includes soft- ware developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This prod- uct includes software developed by Michael L. Hitch. This product in- cludes software developed by Niels Provos. This product includes soft- ware developed by Paul Kranenburg. This product includes software devel- oped by Paul Mackerras. This product includes software developed by Pe- ter Galbavy. This product includes software developed by Philip A. Nel- son. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This prod- uct includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software de- veloped by SigmaSoft, Th. Lockert. This product includes software devel- oped by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes soft- ware developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software de- veloped by Tohru Nishimura for the NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software devel- oped by Winning Strategies, Inc. This product includes software devel- oped by Zembu Labs, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product in- cludes software developed by the Computer Systems Laboratory at the Uni- versity of Utah. This product includes software developed by the Univer- sity of Calgary Department 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 soft- ware 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 Pro- ject 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 in- cludes 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 de- veloped for the NetBSD Project by Ted Lemon. This product includes soft- ware developed by LAN Media Corporation and its contributors. This prod- uct includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@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 California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product in- cludes software developed by Reinoud Zandijk. In the following statement, "This software" refers to the Mitsumi CD-ROM driver: This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Similar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD" , "FreeBSD" , "Mach" (by CMU). In the following statement, "This software" refers to the parallel port driver: This software is a component of "386BSD" developed by William F. Jolitz, TeleMuse. TThhee EEnndd NetBSD September 10, 2001 45