INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/news68k. DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.5 on the _n_e_w_s_6_8_k 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. 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 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. CChhaannggeess SSiinnccee TThhee LLaasstt RReelleeaassee The NetBSD 1.5 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many userland enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over one year of development that went into the NetBSD 1.5 release. Some highlights include: _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 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 bound checking, and another one to iden- tify and disable places where format strings were used in an unsafe way, allowing arbitrary data entered by (possibly) malicious users to overwrite application code, and leading from Denial of Service at- tacks to compromised system. _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. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. This is the first major release of NetBSD for the Sony's news68k based ``NET WORK STATION'' series of computers. 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 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.5 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._5_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.5 distribution. README.files README describing the distribution's contents. TODO NetBSD 's todo list (also somewhat incomplete and out of date). _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 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. _5_._6 _M_B _g_z_i_p_p_e_d_, _5_7_._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 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. _2_4_._2 _M_B _g_z_i_p_p_e_d_, _1_2_0_._6 _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 kernel for all architectures, config(8), and dbsym(8). _1_7_._6 _M_B _g_z_i_p_p_e_d_, _8_8_._6 _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. _3_5_._2 _M_B _g_z_i_p_p_e_d_, _1_7_6_._8 _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_/_n_e_w_s_6_8_k _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The news68k-specific portion of the NetBSD 1.5 release is found in the _n_e_w_s_6_8_k subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._5_/_n_e_w_s_6_8_k_/ _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. _s_e_t_s_/ news68k binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _f_l_o_p_p_y_/ news68k boot and installation floppies; see below. _m_i_s_c_/ Miscellaneous news68k 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 news68k binary distribution sets contain the binaries which comprise the NetBSD 1.5 release for the news68k. There are eight binary distribution sets. The binary distribution sets can be found in the _n_e_w_s_6_8_k_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.5 distribution tree, and are as follows: bbaassee The NetBSD 1.5 news68k 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_5_._6 _M_B _g_z_i_p_p_e_d_, _4_1_._3 _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_1_._8 _M_B _g_z_i_p_p_e_d_, _3_9_._5 _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. (If you are upgrading, it's recommended that you get a copy of this set and _c_a_r_e_f_u_l_l_y upgrade your configuration files by hand.) _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. _3_._0 _M_B _g_z_i_p_p_e_d_, _7_._4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn This set contains a NetBSD/news68k 1.5 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _0_._9 _M_B _g_z_i_p_p_e_d_, _1_._9 _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_._3 _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 NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window system are distributed with NetBSD. The sets are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. _2_._6 _M_B _g_z_i_p_p_e_d_, _8_._2 _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_._7 _M_B _g_z_i_p_p_e_d_, _7_._2 _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_._7 _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 The news68k binary distribution sets are distributed as gzipped tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z. 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 news68k binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//nneewwss6688kk SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess NetBSD/news68k 1.5 will run on single m68030-based Sony NEWS worksta- tions. They include the NWS-14x0, NWS-15x0, PWS-15x0, NWS-17x0, and NWS-12x0 machines. NetBSD/news68k does not currently support m68020-based machines (NWS-700, NWS-800) nor I/O processor based machines (NWS-800, NWS-1800). NetBSD/news68k 1.5 does not support any framebuffers so _y_o_u _h_a_v_e _t_o _u_s_e _s_e_r_i_a_l _c_o_n_s_o_l_e to install NetBSD/news68k. NetBSD/news68k 1.5 does not support SCSI on NWS-12x0 machines, so instal- lations on NWS-12x0 must use a remote NFS file system. MIPS based NEWS workstations (NWS-3xxx or NWS-5000) are supported by NetBSD/newsmips. _S_u_p_p_o_r_t_e_d _h_a_r_d_w_a_r_e ++oo CPUs -- 68020-based: none -- 68030-based: NWS-12x0, NWS-14x0, NWS-15x0, PWS-15x0, NWS-17x0 ++oo RS232 interfaces -- built in Zilog 8530 Serial Communication Controllers (zsc) ++oo Network interfaces -- built in LANCE Ethernet (le) ++oo SCSI interfaces -- built in CXD1180 SCSI interface (si) -- most SCSI devices If it's not on this list, there is no official support for it in this re- lease. More information can also be found at the NetBSD/news68k home- page: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//nneewwss6688kk// GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa _N_o_t_e_: NetBSD/news68k 1.5 does not support any framebuffers (yet) so you have to use serial console on installation procedure. You will need to have a 1.44 MB floppy disk to boot off. You must put the boot floppy image onto this disk, which contains software to install NetBSD system. If you are using a UNIX-like system (such as NEWS-OS or other NetBSD ma- chines) to write the floppy images to disks, you should use the dd(1) 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 compre- hensive list of the possibilities is beyond the scope of this document. If you have an i386 machine which runs MS-DOS and use them to write the floppy image(s) to floppy disk, you can use the rraawwrriittee utility, provided in the _i_3_8_6_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c 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. Though NetBSD/news68k uses the floppy disk to boot for the initial in- stallation, the NetBSD/news68k kernel does not support the floppy device. Some other machines or systems are still required to write floppy images even after NetBSD/news68k has been installed. SCSI devices on NWS-12x0 machines are not supported (yet), so they can only run NetBSD/news68k diskless. No file transfer is needed, and all you have to do is to prepare files on the server. More information about diskless setting can be found at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//nneettwwoorrkk//nneettbboooott// The NEWS PROM also supports tape boot and network boot, but NetBSD/news68k does not support them currently. After the boot floppy is prepared, just type bboo ffhh on the PROM prompt to boot it. Installation is supported from several media types, including: ++oo CD-ROM ++oo FTP ++oo Remote NFS partition 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. _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 October, 2000). 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. 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. 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. _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. 3. _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). -- One 1.44 MB 3.5" floppy. -- A CD-ROM drive (SCSI), a harddisk and a minimum of 4 MB of memory installed. -- The harddisk should have at least 100 + _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\\ii338866\\iinnssttaallllaattiioonn\\mmiisscc rraawwrriittee When asked for a source filename, answer _\_N_e_t_B_S_D_-_1_._5_\_n_e_w_s_6_8_k_\_i_n_s_t_a_l_l_a_t_i_o_n_\_f_l_o_p_p_y_\_b_o_o_t_._f_s 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 boot floppy you just created. Boot the computer. Type NEWS> bboo ffhh The main menu will be displayed. -- If you wish, you can configure some network settings immedi- ately by choosing the uuttiilliittiieess menu 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 sysinst, 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// 4. _B_o_o_t_i_n_g _N_e_t_B_S_D 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. 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. The most important thing to know is that wd0 is NetBSD 's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Note that once the system has finished booting, you need not leave the floppy in the disk drive. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n 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 utilities menu, and select CCoonnffiigguurree nneettwwoorrkk ooppttiioonn. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using Domain Name Service (DNS), you can give an empty response in reply to answers relating to this. 6. _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 the menu option to install NetBSD 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 sd0 or sd1. 7. _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. ++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. Some partitions in the disklabel have a fixed pur- pose. a Root partition. (_/), b Swap partition. c 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. 8. _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. 9. _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 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' 10. _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 number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, 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 number instead of a hostname for the ftp serv- er. ssyyssiinnsstt will proceed to transfer all the default set files from the remote site to your hard disk. 11. _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 number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a host- name for the NFS server. 12. _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. 13. _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. 14. _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. 15. _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 GMT. Finally you can set a password for the "root" ac- count, to prevent the machine coming up without access restrictions. 16. _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. 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, the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (_/) mounted read-write. When the sys- tem asks you to choose a shell, simply press RETURN to get to a prompt. If you are asked for a terminal type, respond with vvtt222200 (or whatever is appropriate for your terminal type) and press RETURN. At this point, you need to configure at least one file in the _/_e_t_c directory. 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 pro- grams can be found in /etc/defaults/rc.conf, where some in-line doc- umentation 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 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. There is no initial password, but if you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the ``root'' account with good passwords. Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...] 3. Adding accounts Use the useradd(8) command to add accounts to your system, _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. 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// ++oo Package sources for compiling packages can be obtained by re- trieving 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), as with the command: # mmkkddiirr //uussrr//ppkkggssrrcc;; ttaarr --CC //uussrr//ppkkggssrrcc --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 (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 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily 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. Another difference is that existing configuration files in _/_e_t_c are backed up and merged with the new files. Getting the binary sets is done in the same manner as the in- stallation procedure; refer to the installation part of the document for how to do this. Also, some sanity 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 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. 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. _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_/_* In previous releases of NetBSD, _/_e_t_c_/_r_c was a traditional BSD style monolithic file. As of NetBSD 1.5, 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_i_n_g _f_r_o_m _N_e_t_B_S_D _1_._4 _o_r _l_a_t_e_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 Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) ++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 Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g ssuunn33xx 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 _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 Havard 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_: 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 Robert V. Baron _r_v_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 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 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 Simon Burge _s_i_m_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 Jaromir 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 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 Havard 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 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 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 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 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 NONAKA Kimihiro _n_o_n_a_k_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 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 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 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 includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Han- num. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Alistair G. Crooks. This product includes software developed by Amancio Hasty and Roger Hardiman. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch. This product includes software developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael L. Hitch. This product includes software developed by Niels Provos. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by Tohru Nishimura for the NetB- SD Project. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the Computer Systems Labora- tory at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@min- com.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. NetBSD October 29, 2000 29