INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/mvme68k. DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.5.1 on the _m_v_m_e_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.1 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..11 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.1. NetBSD 1.5.1 is an upgrade of NetBSD 1.5 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.1 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.1 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.1 to determine if a given feature is present or absent in 1.5.1. 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.1 which were not in, e.g. 1.5B, and vice versa. 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. All packages have been verified on a release candidate of 1.5.1/i386, and have been found to compile, install and de-install cleanly. 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.1 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.1. 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.1 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 fifth major release of NetBSD for the mvme68k series of boards. 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..11 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.5.1 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._5_._1_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.5.1 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.1 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.1 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.1 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_/_m_v_m_e_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 mvme68k-specific portion of the NetBSD 1.5.1 release is found in the _m_v_m_e_6_8_k subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._5_._1_/_m_v_m_e_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. _n_e_t_b_s_d_._V_M_E_1_4_7_._g_z A kernel for MVME147 boards. _n_e_t_b_s_d_._V_M_E_1_6_2_._g_z A kernel for MVME162-LX boards. _n_e_t_b_s_d_._V_M_E_1_6_7_._g_z A kernel for MVME167 boards. _s_e_t_s_/ mvme68k binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _m_i_n_i_r_o_o_t_/ mvme68k miniroot file system image; see below. _n_e_t_b_o_o_t_/ Two programs needed to boot mvme68k kernels over the network; see below. _t_a_p_e_i_m_a_g_e_/ Tape boot programs, and a RAMDISK kernel; see 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 mvme68k binary distribution sets contain the binaries which comprise the NetBSD 1.5.1 release for the mvme68k. There are eight binary distribution sets. The binary distribution sets can be found in the _m_v_m_e_6_8_k_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.5.1 distribution tree, and are as follows: bbaassee The NetBSD 1.5.1 mvme68k 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_._5 _M_B _g_z_i_p_p_e_d_, _4_1_._2 _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. _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/mvme68k 1.5.1 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _0_._7 _M_B _g_z_i_p_p_e_d_, _1_._4 _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. The binaries shipped with NetBSD 1.5.1 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_._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 mvme68k 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 _/. The following are included in the _m_v_m_e_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n directory: _m_i_n_i_r_o_o_t_/ _m_i_n_i_r_o_o_t_._g_z A copy of the miniroot file system. This filesystem image is copied into the swap parti- tion of the disk which you intend to boot NetBSD from. Normally, this step will be performed manu- ally from the ramdisk boot environment. _n_e_t_b_o_o_t_/ _s_b_o_o_t An MVME147 bootstrap program in Motorola S-Record for- mat. This is required when you wish to boot an MVME147 over the network since the ROM has no built-in network support. Instructions for getting this program into memory are discussed later. _n_e_t_b_o_o_t A standalone 2nd stage bootstrap program loaded over the network via TFTP. This is responsible for fetch- ing and starting the NetBSD mvme68k kernel from an NFS server. _t_a_p_e_i_m_a_g_e_/ _s_t_b_o_o_t This file contains a boot sector for Motorola MVME boards. It must be the first file written to a tape in order to make the tape bootable. _b_o_o_t_s_t This file contains a bootstrap program which knows how to load the NetBSD mvme68k ramdisk image from tape. This must be the second file written to the tape. _n_e_t_b_s_d_-_r_d_._g_z This is the NetBSD mvme68k ramdisk image. It contains a GENERIC kernel and a built in RAMDISK with just enough tools to partition a disk, dump the miniroot kernel to it and make the disk bootable. This must be the third file written to the tape. _N_o_t_e_: Each directory in the mvme68k binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//mmvvmmee6688kk SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess NetBSD/mvme68k 1.5.1 runs on Motorola MVME147 , MVME162-LX and MVME167 Single Board Computers. The minimal configuration requires 8 MB of RAM and ~200 MB of disk space. To install the entire system requires much more disk space (approx. 600 MB additional space is necessary for full sources. Double that if you want to recompile it all!). To run X (clients only) or compile the sys- tem, more RAM is recommended. Good performance requires 16 MB of RAM, or 32 MB when running the X Window System. Note that you can install NetBSD 1.5.1 on a system with only 4 MB of on- board RAM, but you will need to use a VMEbus RAM card with at least an- other 4 MB to augment the onboard memory in order to actually install the system. Here is a table of recommended HD partition sizes for a full install: Partition Suggested Needed / (root) 32 MB 26 MB /usr 200 MB 150 MB /var 32 MB 6 MB swap _2_-_3 _*_R_A_M 16 MB Anything else is up to you! Note that the NetBSD/mvme68k installation procedure uses a _m_i_n_i_r_o_o_t image which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image (> 7.5 MB). _S_u_p_p_o_r_t_e_d _V_M_E_1_4_7 _h_a_r_d_w_a_r_e ++oo Serial ports (RS232) -- built-in console -- ttyZ1 -- ttyZ2 -- ttyZ3 ++oo Parallel port -- On-board centronics style printer port ++oo Network interfaces: -- On-board Lance Ethernet (le) ++oo SCSI -- Most SCSI disks, tapes, CD-ROMs, etc -- On-board wd33c93 SCSI bus interface chip (async only) ++oo Miscellaneous: -- Battery-backed real-time clock -- VMEbus RAM cards -- Any VMEbus interface cards with Machine Independent drivers _S_u_p_p_o_r_t_e_d _V_M_E_1_6_2_-_L_X _h_a_r_d_w_a_r_e ++oo Serial ports (RS232) -- built-in console -- ttyZ1 -- ttyZ2 -- ttyZ3 ++oo Network interfaces: -- On-board Intel Ethernet (ie) ++oo SCSI -- Most SCSI disks, tapes, CD-ROMs, etc -- On-board ncr53c710 SCSI I/O processor chip ++oo Miscellaneous: -- Battery-backed real-time clock -- VMEbus RAM cards -- Any VMEbus interface cards with Machine Independent drivers _S_u_p_p_o_r_t_e_d _V_M_E_1_6_7 _h_a_r_d_w_a_r_e ++oo Serial ports (RS232) -- built-in console -- ttyZ1 -- ttyZ2 -- ttyZ3 ++oo Parallel port -- On-board centronics style printer port ++oo Network interfaces: -- On-board Intel Ethernet (ie) ++oo SCSI -- Most SCSI disks, tapes, CD-ROMs, etc -- On-board ncr53c710 SCSI I/O Processor chip ++oo Miscellaneous: -- Battery-backed real-time clock -- VMEbus RAM cards -- Any VMEbus interface cards with Machine Independent drivers If it's not on the above lists, there is no support for it in this re- lease. GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa Installation is supported from several media types, including: ++oo Tape ++oo NFS ++oo CD-ROM ++oo FTP Note that installing on a `bare' machine requires either a bootable tape drive or an ethernet to a compatible NFS server. MVME147 may also need to be booted over an RS232 connection. The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below. In order to create installation media, you will need all the files and subdirectories in these two directories: _._._._/_N_e_t_B_S_D_-_1_._5_._1_/_m_v_m_e_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n _._._._/_N_e_t_B_S_D_-_1_._5_._1_/_m_v_m_e_6_8_k_/_b_i_n_a_r_y _C_r_e_a_t_i_n_g _b_o_o_t_/_i_n_s_t_a_l_l _t_a_p_e_s Installing from tape is the simplest method of all. This method uses two tapes, one containing a bootable ramdisk and miniroot, the other contain- ing the installation sets. The boot tape is created as follows: # ccdd ......//NNeettBBSSDD--11..55..11//mmvvmmee6688kk//iinnssttaallllaattiioonn # sseett TT == //ddeevv//nnrrsstt00 # mmtt --ff $$TT rreewwiinndd # dddd iiff==ttaappeeiimmaaggee//ssttbboooott ooff==$$TT # dddd iiff==ttaappeeiimmaaggee//bboooottsstt ooff==$$TT oobbss==88kk ccoonnvv==oossyynncc # ggzziipp --ddcc ttaappeeiimmaaggee//nneettbbssdd--rrdd..ggzz || dddd ooff==$$TT oobbss==88kk ccoonnvv==oossyynncc # ggzziipp --ddcc mmiinniirroooott//mmiinniirroooott..ggzz || dddd ooff==$$TT oobbss==88kk ccoonnvv==oossyynncc # mmtt --ff $$TT rreewwiinndd The installation set tape is created as follows: # ccdd ......//NNeettBBSSDD--11..55..11//mmvvmmee6688kk//bbiinnaarryy//sseettss # sseett TT == //ddeevv//nnrrsstt00 # mmtt --ff $$TT rreewwiinndd # ffoorr ff iinn bbaassee eettcc ccoommpp ggaammeess mmaann mmiisscc tteexxtt;; ddoo ggzziipp --dd << $$ff..ttggzz || dddd ooff==$$TT bbss==88kk # ddoonnee # mmtt --ff $$TT rreewwiinndd If the tape does not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. Consult the tape-related manual pages on the system where the tapes are created for more details. _B_o_o_t_/_I_n_s_t_a_l_l _f_r_o_m _N_F_S _s_e_r_v_e_r If your machine has a disk and network connection, but no tape drive, it may be convenient for you to install NetBSD over the network. This in- volves temporarily booting your machine over NFS, just long enough so you can initialize its disk. This method requires that you have access to an NFS server on your network so you can configure it to support diskless boot for your machine. Configuring the NFS server is normally a task for a system administrator, and is not trivial. If you are using a NetBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, consult the documentation that came with it (i.e. add_client(8) on SunOS). Booting an MVME147 from ethernet is not possible without first download- ing a small bootstrap program (sboot) via RS232. See the section entitled _I_n_s_t_a_l_l_i_n_g _f_r_o_m _N_F_S for details on how to accomplish this. sboot expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RARP It will look for a filename derived from the machine's IP address expressed in hexadecimal, with an extension of `_._1_4_7'. For example, an MVME147 with IP address 130.115.144.11 will make an TFTP request for _8_2_7_3_9_0_0_B_._1_4_7. Normally, this file is just a symbolic link to the NetBSD/mvme68k _n_e_t_b_o_o_t program, which should be located in a place where the TFTP daemon can find it (re- member, many TFTP daemons run in a chroot'ed environment). The netboot program may be found in the install directory of this distribution. The MVME162-LX and MVME167 boot ROMs have code builtin to boot over eth- ernet from a TFTP server. You should configure it to download the same _n_e_t_b_o_o_t program as is used for MVME147. The netboot program will query a bootparamd server to find the NFS server address and path name for its root, and then load a kernel from that lo- cation. The server should have a copy of the netbsd-rd kernel in the root area for your client (no other files are needed in the client root, al- though it might be a convenient place to put the uncompressed miniroot image) and _/_e_t_c_/_b_o_o_t_p_a_r_a_m_s on the server should have an entry for your client and its root directory. Note that you should rename the _n_e_t_b_s_d_-_r_d kernel to just _n_e_t_b_s_d in the client's root directory before trying to netboot the client. The client will need access to the miniroot image, which can be provided using NFS or remote shell. If using NFS, miniroot.gz should be expanded on the server, because doing so from the RAMDISK shell is not so easy. The unzipped miniroot takes about 7.5 MB of space. If you will be installing NetBSD on several clients, it may be useful to know that you can use a single NFS root for all the clients as long as they only use the netbsd-rd kernel. There will be no conflict between clients because the RAM-disk kernel will not use the NFS root. No swap file is needed; the RAM-disk kernel does not use that either. _I_n_s_t_a_l_l_/_U_p_g_r_a_d_e _f_r_o_m _C_D_-_R_O_M This method requires that you boot from another device (i.e. tape or net- work, as described above). You may need to make a boot tape on another machine using the files provided on the CD-ROM. Once you have booted netbsd-rd (the RAMDISK kernel) and loaded the miniroot, you can load any of the distribution sets directly from the CD-ROM. The iinnssttaallll program in the miniroot automates the work required to mount the CD-ROM and extract the files. _I_n_s_t_a_l_l_/_U_p_g_r_a_d_e _v_i_a _F_T_P This method requires that you boot from another device (i.e. tape or net- work, as described above). You may need to make a boot tape on another machine using the files in .../install (which you get via FTP). Once you have booted netbsd-rd (the RAM-disk kernel) and loaded the miniroot, you can load any of the distribution sets over the net using FTP. The iinnssttaallll program in the miniroot automates the work required to configure the net- work interface and transfer the files. This method, of course, requires network access to an FTP server. This might be a local system, or it might even be ftp.netbsd.org itself. If you wish to use ftp.netbsd.org as your FTP file server, you may want to keep the following information handy: No IP Address: ftp.netbsd.org Login: anonymous Password: Server path: /pub/NetBSD/NetBSD-1.5.1/mvme68k/binary _N_o_t_e_: If you're not using a nameserver duing installation, you might find 204.152.184.75 handy; it's the IP address of ftp.netbsd.org as of October, 2000. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn mvme68k machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of _b_a_c_k_i_n_g _u_p _a_l_l _d_a_t_a on any attached storage devices. The exception to the above is that MVME162-LX and MVME167 boards require a jumper to be removed before NetBSD can be installed. On MVME162-LX pins 1-2 of jumper J11 _m_u_s_t be removed. On MVME167 pins 1-2 of jumper J1 _m_u_s_t be removed. Once you've made any necessary jumper changes, the following instructions should make your machine ``NetBSD Ready''. Power-up your MVME147 board. You should have the _b_u_g prompt: COLD Start Onboard RAM start = $00000000, stop = $007FFFFF 147-Bug> Or, if you have an MVME162-LX or MVME167 board (the following boot mes- sage is from MVME167; MVME162-LX is similar): MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94 COLD Start Local Memory Found =02000000 (&33554432) MPU Clock Speed =33Mhz 167-Bug> Make sure the RAM size looks ok (if you've got an 8 MB MVME147 or a 32 MB MVME167 you should have the same value as we do). Also make sure the clock is ticking: 1xx-Bug>ttiimmee Sunday 12/21/31 16:25:14 1xx-Bug>ttiimmee Sunday 12/21/31 16:25:15 1xx-Bug> Note that NetBSD bases its year at 1968, and adds the year offset in the system's real-time clock to get the current year. So the 31 here equates to 1999. You may have to adjust your clock using the sseett command to com- ply with NetBSD 's requirements. Don't worry if the `Day of the week' is not correct, as NetBSD doesn't use it. Motorola has acknowledged a year 2000 bug in some versions of the MVME147 whereby the day of the week doesn't get set correctly by the 147Bug PROM. _I_t _d_o_e_s _n_o_t _a_f_f_e_c_t NetBSD ! Also make sure that your board's ethernet address is initialised to the correct value. You'll find the address on a label on the inside of the MVME147's front panel, and on the VMEbus P2 connector of the MVME162-LX and MVME167. On the MVME147, enter the last five digits of the address using the llssaadd command. On the MVME162-LX and MVME167, you should use the ccnnffgg command. To install successfully to a local SCSI disk, you need to ensure that the system is aware of what targets are connected to the SCSI bus. This can be done by issueing the following command: 1xx-Bug> iioott;;tt At this point, Bug will scan for any attached SCSI devices. After a short delay, a list of SCSI devices will be displayed. 147Bug will ask if LUNs should be assigned from SCSI ids, to which you should answer Y. You should also answer Y when asked if the information is to be saved to NVRAM. 16xBug does not prompt for this information. The following installation instructions will assume that your target SCSI disk drive appears at SCSI-ID 0. If you have a tape drive, the instruc- tions assume is is configured for SCSI-ID 5. When the RAMDISK root boots, NetBSD will refer to these devices as sd0 and rst0 respectively. You may wish to note these down; you'll be using them a lot. :-) IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm Installing NetBSD is a relatively complex process, but if you have this document in hand it should not be too difficult. There are several ways to install NetBSD onto your disk. If your machine has a tape drive the easiest way is _I_n_s_t_a_l_l_i_n_g _f_r_o_m _t_a_p_e (details below). If your machine is on a network with a suitable NFS server, then _I_n_s_t_a_l_l_i_n_g _f_r_o_m _N_F_S is the next best method. Otherwise, if you have an- other mvme68k machine running NetBSD you can initialize the disk on that machine and then move the disk. _I_n_s_t_a_l_l_i_n_g _f_r_o_m _t_a_p_e Create the NetBSD/mvme68k 1.5.1 boot tape as described in the section en- titled _P_r_e_p_a_r_i_n_g _a _b_o_o_t _t_a_p_e. Then, with the tape in the drive, type the following at the Bug prompt: 147-Bug> bboo 55 16x-Bug> bboo 00,,5500 As mentioned earlier, this assumes your tape is jumpered for SCSI-ID 5. As the tape loads (which may take 20 to 30 seconds), you will see a se- ries of status messages. It may be useful if you can capture these mes- sages to a file, or a scrollable xterm window. In particular, you should make a note of the lines which describe the geometry of the SCSI disks detected by NetBSD. They are of the form: sd0 at scsibus0 targ 0 lun 0: SCSI1 0/direct fixed sd0: 800 MB, 800 cyl, 16 head, 128 sec, 512 bytes/sect x 1638400 sectors The information of most interest is the number of sectors; for the ficti- cious disk above, it's 1638400. You will need this number when you come to create a disklabel for that drive. Here is an example of an MVME147 system booting from tape: RAM address from VMEbus = $00000000 Booting from: VME147, Controller 5, Device 0 Loading: Operating System Volume: NBSD IPL loaded at: $003F0000 >> BSD MVME147 tapeboot 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997, 1998, 1999, 2000 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000 steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . _N_o_t_e_: The exact text of the messages will vary depending on which mvme68k variant you're using. Finally, you will see the following "welcome" message: Welcome to the NetBSD/mvme68k RAMDISK root! This environment is designed to do only four things: 1: Partititon your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Make that partition bootable (using 'installboot') 4: Reboot (using the swap partition, i.e. /dev/sd0b). Copying the miniroot can be done several ways, allowing the source of the miniroot image to be on any of these: boot tape, NFS server, TFTP server, rsh server The easiest is loading from tape, which is done as follows: mt -f /dev/nrst0 rewind mt -f /dev/nrst0 fsf 3 dd bs=8k if=/dev/nrst0 of=/dev/rsd0b (For help with other methods, please see the install notes.) To reboot using the swap partition after running installboot, first use hhaalltt, then at the Bug monitor prompt use a command like: 1x7Bug> bo 0,,b: To view this message again, type: cat /.welcome ssh: You must now create a disklabel on the disk you wish to use for the root file system (_/). This will usually be sd0. The disklabel is used by NetBSD to identify the starting block and size of each partition on the disk. Partitions are named sd0a, sd0b, sd0c, etc, up to sd0h. The mvme68k port of NetBSD makes some assumptions about the first three partitions on a boot disk: sd0a The root file system (_/). sd0b The swap partition. sd0c The whole disk. Also known as the _r_a_w _p_a_r_t_i_t_i_o_n. The _r_a_w _p_a_r_t_i_t_i_o_n is special; NetBSD is able to use it even if the disk has no label. You should never create a file system on the Raw Partition, even on a non-boot disk. It is good practice to put _/_u_s_r on a different partition than _/ (root, AKA sd0a). So, the first available partition for _/_u_s_r is sd0d. Refer to the section entitled _N_e_t_B_S_D _S_y_s_t_e_m _R_e_q_u_i_r_e_m_e_n_t_s _a_n_d _S_u_p_p_o_r_t_e_d _D_e_v_i_c_e_s for information on the recommended sizes of the _/ (root), _/_u_s_r and swap par- titions. You are not required to define any partitions beyond sd0d, but if you have a large disk drive, you might want to create several other parti- tions for file systems such as _/_h_o_m_e or _/_u_s_r_/_s_r_c. Note that at this time you are only required to partition the root/boot disk; you will get the opportunity to partition any other disks in your system from the main mmiinniirroooott installation program. To create the disklabel and partitions, use the edlabel program, passing it the name of the Raw Partition of your root/boot disk. ssh: eeddllaabbeell //ddeevv//rrssdd00cc edlabel menu: print - display the current disk label modify - prompt for changes to the label write - write the new label to disk quit - terminate program edlabel> The program shows what commands it recognizes; pprriinntt, mmooddiiffyy, wwrriittee, and qquuiitt. It will accept the first letter of a command if you don't feel like typing each one in full. To start creating the basic partitions, you should enter mm (modify) at the edlabel prompt, then enter the letter corresponding to the first partition, aa. edlabel> mm modify subcommands: @: modify disk parameters a-h: modify partition s: standarize geometry q: quit this subcommand edlabel/modify> aa a (root) 0 (0/00/00) 0 (0/00/00) unused start as or : 00 length as or : 6655553366 type: 44..22BBSSDD edlabel/modify> When you enter the start and length of a partition, you can use either blocks or cylinder/track/sector notation. If this is the first time you've partitioned a disk for NetBSD, it's probably easiest to use block notation. The above example creates partition `a', starting at block zero and with a size of 65536 blocks. Note that the usual size of a block is 512 bytes, so this creates a 32 MB partition. The type of the partition should be 4.2BSD, otherwise you won't be able to create a file system on it. Next, create a swap partition (b). Note that the minimum size of this swap partition should be 8 MB, otherwise you won't be able to use a mini- root to complete the NetBSD installation! edlabel/modify> bb b (swap) 0 (0/00/00) 0 (0/00/00) unused start as or : 6655553366 length as or : 3322776688 type: sswwaapp edlabel/modify> Here, we specify a value for start such that the swap partition follows immediately after partition `a', i.e. 65536. The length of the swap par- tition should be a multiple of the amount of RAM you have in your system. Here, we've chosen 32768, or 16 MB. The next available block on the drive is thus 65536 + 32768. We will use this to create partition `d' for our _/_u_s_r file system. (Note that for a busy system, or a system with more than 8 MB of RAM, you'll be better off with a 32 or 64 MB swap parti- tion.) edlabel/modify> dd d (user) 0 (0/00/00) 0 (0/00/00) unused start as or : 9988330044 length as or : 11554400009966 type: 44..22BBSSDD edlabel/modify> qq edlabel> As you can see, we've chosen to assign the remainder of the disk to _/_u_s_r. Since there are 1638400 sectors on the example disk (did you remember to note down the number of sectors on your disk during boot?), and partition dd starts at sector 98304, a simple bit of arithmetic (1638400 - 98304) gives dd a size of 1540096. Note that the above partition sizes are just guidelines. If your disk is large enough, you should resize the partitions appropriately and perhaps also create a /var partition as well. You now need to write this new disklabel, together with the partition de- tails you've just entered, to disk. You might also try the `pp' command to view the partitions. Once written, you can quit back to ssh using `qq'. edlabel> pp type_num: 4 sub_type: 0 type_name: SCSI disk pack_name: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 16 cylinders: 800 sectors/cylinder: 2048 partition start (c/t/s) nblks (c/t/s) type a (root) 0 (0/00/00) 65536 (32/00/00) 4.2BSD b (swap) 65536 (32/00/00) 32768 (48/00/00) swap c (disk) 0 (0/00/00) 1638400 (800/00/00) unused d (user) 98304 (48/00/00) 1540096 (752/00/00) 4.2BSD edlabel> ww edlabel> qq ssh: Now that your disk's partitioned, you need to get the proper installation miniroot image onto it. The miniroot image is designed to be copied into the swap partition of your disk. This is a safe place which won't be overwritten by the installation procedure. From the ssh prompt, use the following commands to copy the miniroot image from tape to swap (b). ssh: mmtt --ff //ddeevv//nnrrsstt00 rreewwiinndd ssh: mmtt --ff //ddeevv//nnrrsstt00 ffssff 33 ssh: dddd bbss==88kk iiff==//ddeevv//nnrrsstt00 ooff==//ddeevv//rrssdd00bb The disk and the miniroot must now be made bootable using the installboot(8) command. To do this, issue the following commands: ssh: mmoouunntt //ddeevv//ssdd00bb //mmnntt ssh: iinnssttaallllbboooott //mmnntt//uussrr//mmddeecc//bboooottssdd //bboooottxxxx //ddeevv//rrssdd00bb ssh: uummoouunntt //ddeevv//ssdd00bb You can now shutdown the system. ssh: hhaalltt signal 15 ssh: syncing disks... done unmounting / (root_device)... halted 147-Bug> rreesseett Reset Local SCSI Bus [Y,N] N? yy Automatic reset of known SCSI Buses on RESET [Y,N] Automatic0 Cold/Warm Reset flag [C,W] = C? Execute Soft Reset [Y,N] N? yy Resetting the MVME162-LX and MVME167 boards are very similar. You should now reboot from that just installed miniroot. See the section entitled _B_o_o_t_i_n_g _t_h_e _m_i_n_i_r_o_o_t for details. _I_n_s_t_a_l_l_i_n_g _f_r_o_m _N_F_S Before you can install from NFS, you must have already configured your NFS server to support your machine as a bootable client. Instructions for configuring the server are found in the section entitled _G_e_t_t_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m _o_n_t_o _U_s_e_f_u_l _M_e_d_i_a above. To get started on the MVME147, you need to download _s_b_o_o_t into RAM (you will find ssbboooott in the _i_n_s_t_a_l_l directory of the mvme68k distribution). You can either do that through the console line or through a 2nd serial connection. For example, an MVME147 connected to a sun4/110 and accessed via tip(1) can be loaded as follows: lo 0 ~Ccat sboot go 4000 Which will look like this: 147-Bug> lloo 00 ~CLocal command? ccaatt ssbboooott _a_w_a_y _f_o_r _1_1 _s_e_c_o_n_d_s ! 147-Bug> gg 44000000 Effective address: 00004000 sboot: serial line bootstrap program (end = 6018) >>> Now, if you want to do it through serial line 1, then connect serial line one to a machine. At the 147-Bug> prompt type ttmm 11 You should then login to the machine it is connected to. Then press CONTROL-A to escape to Bug. do lloo 11;;xx==ccaatt ssbboooott _._._. then when that is done you can reconnect ttmm 11 and logout. Then do ggoo 44000000 and you've got the >>> prompt of ssbboooott. Once you've got the >>> prompt, you can boot the RAMDISK kernel from the server: >>> bb le0: ethernet address: 8:0:3e:20:cb:87 My ip address is: 192.168.1.4 Server ip address is: 192.168.1.1 4800 Download was a success! See below for the next step in booting MVME147. The MVME162-LX and MVME167 boards are able to download netboot directly using TFTP. To enable this, you must first configure the networking pa- rameters on the board as described in the section entitled "Preparing your System for NetBSD Installation. On a properly configured MVME162-LX or MVME167, all you need to type is: 16x-Bug> nnbboo For all board types, the boot messages are very similar: Start @ 0x8000 ... >> BSD MVME147 netboot (via sboot) device: le0 attached to 08:00:3e:20:cb:87 boot: client IP address: 192.168.1.4 boot: client name: soapy root addr=192.168.1.1 path=/export/soapy 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997, 1998, 1999, 2000 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000 steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . After the boot program loads the RAMDISK kernel, you should see the wel- come screen as shown in the "tape boot" section above. You now need to create a disklabel with partition information on the SCSI disk on which you intend to create your root file system (_/). Follow the instructions in the previous section entitled _I_n_s_t_a_l_l_i_n_g _f_r_o_m _t_a_p_e to do this. (But stop short of the part which describes how to copy the mini- root from tape.) You must now configure the network interface before you can access the NFS server containing the miniroot image. For example the command: ssh: iiffccoonnffiigg llee00 iinneett 119922..116688..11..44 uupp will bring up the MVME147 network interface le0 with that address. The command: ssh: iiffccoonnffiigg iiee00 iinneett 119922..116688..11..44 uupp will bring up the MVME162-LX or MVME167 network interface ie0 with that address. The next step is to copy the miniroot from your server. This can be done using either NFS or remote shell. (In the examples that fol- low, the server has IP address 192.168.1.1) You may then need to add a default route if the server is on a different subnet: ssh: rroouuttee aadddd ddeeffaauulltt 119922..116688..11..22 11 You can look at the route table using: ssh: rroouuttee sshhooww Now mount the NFS file system containing the miniroot image: ssh: mmoouunntt --rr 119922..116688..11..11:://eexxppoorrtt//ssooaappyy //mmnntt The procedure is simpler if you have space for an expanded (not com- pressed) copy of the miniroot image. In that case: ssh: dddd bbss==88kk iiff==//mmnntt//mmiinniirroooott ooff==//ddeevv//rrssdd00bb Otherwise, you will need to use zzccaatt to expand the miniroot image while copying. This is tricky because the sssshh program (small shell) does not handle sh(1) pipeline syntax. Instead, you first run the reader in the background with its input set to _/_d_e_v_/_p_i_p_e and then run the other program in the foreground with its output to _/_d_e_v_/_p_i_p_e. The result looks like this: ssh: rruunn --bbgg dddd oobbss==88kk iiff==//ddeevv//ppiippee ooff==//ddeevv//rrssdd00bb ssh: rruunn --oo //ddeevv//ppiippee zzccaatt //mmnntt//iinnssttaallll//mmiinniirroooott..ggzz To load the miniroot using rsh to the server, you would use a pair of commands similar to the above. Here is another example: ssh: rruunn --bb dddd oobbss==88kk iiff==//ddeevv//ppiippee ooff==//ddeevv//rrssdd00bb ssh: rruunn --oo //ddeevv//ppiippee rrsshh 119922..116688..11..11 zzccaatt mmiinniirroooott..ggzz You must now make the disk bootable. Refer to the previous section on in- stalling from tape, where it describes how to run iinnssttaallllbboooott. This is immediately following the part which explains how to copy the miniroot from tape. _B_o_o_t_i_n_g _t_h_e _m_i_n_i_r_o_o_t Assuming the miniroot is installed on partition `b' of the disk with SC- SI-ID 0, then the 147Bug boot command is: 147-Bug> bboo 00,,,,bb:: The corresponding 162Bug or 167Bug boot command is: 16x-Bug> bboo 00,,,,,,bb:: The command line parameters above are: 00 controller (usually zero) ,,,, oorr ,,,,,, bug argument separators bb:: tell the bootstrap code to boot from partition b You should see a bunch of boot messages, followed by messages from the miniroot kernel just as you did when the RAMDISK kernel booted. You will then be prompted to enter the root device. Since the miniroot was booted from the swap partition, you should enter sd0b. You will then be asked for the swap device and file system type. Just press RETURN twice to accept the defaults. When asked to enter a terminal type, either accept the default, or use whatever the TERM environment variable is set to in the shell of your host system: boot device: sd0 root device (default sd0a): ssdd00bb dump device (default sd0b): _(_r_e_t_u_r_n_) file system (default generic): _(_r_e_t_u_r_n_) root on sd0b dumps on sd0b mountroot: trying ffs... root file system type: ffs init: copying out path `/sbin/init' 11 erase ^H, werase ^W, kill ^U, intr ^C Terminal type? [vt100] _r_e_t_u_r_n Congratulations! The system should now be running the miniroot installa- tion program. _M_i_n_i_r_o_o_t _i_n_s_t_a_l_l _p_r_o_g_r_a_m_: The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. Additional improve- ments are planned for future releases. The miniroot's install program will: ++oo Allow you to place disklabels on additional disks. The disk we are installing on should already have been partitioned using the RAMDISK kernel. Note that partition sizes and offsets are expressed in sectors. When you fill out the disklabel, you will need to specify partition types and file system parameters. If you're unsure what these values should be, use the following defaults: fstype: 4.2BSD fsize: 1024 bsize: 4096 cpg: 16 If the partition will be a swap partition, use the following: fstype: swap fsize: 0 (or blank) bsize: 0 (or blank) cpg: 0 (or blank) Note that partition `c' is special; it covers then entire disk and should not be assigned to a file system. The number of partitions is currently fixed at 8. ++oo Create file systems on target partitions. ++oo Allow you to set up your system's network configuration. Remember to specify host names without the domain name appended to the end. For example use foo instead of foo.bar.org. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for con- figuration again. ++oo Mount target file systems. You will be given the opportunity to manu- ally edit the resulting _/_e_t_c_/_f_s_t_a_b. ++oo Extract binary sets from the media of your choice. ++oo Copy configuration information gathered during the installation pro- cess to your root file system (_/). ++oo Make device nodes in your root file system under _/_d_e_v. ++oo Copy a new kernel onto your root partition (_/). ++oo Install a new boot block. ++oo Check your file systems for integrity. First-time installation on a system through a method other than the in- stallation program is possible, but strongly discouraged. 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. 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_._1_/_m_v_m_e_6_8_k_/_A_l_l subdir. You can install them with the following commands: ## eexxppoorrtt PPKKGG__PPAATTHH==ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..55..11//mmvvmmee6688kk//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 It is possible to easily upgrade your existing NetBSD/mvme68k system us- ing the upgrade program in the miniroot. If you wish to upgrade your sys- tem by this method, simply select the uuppggrraaddee option once the miniroot has booted. The upgrade program with then guide you through the proce- dure. The upgrade program will: 1. Enable the network based on your system's current network configura- tion. 2. Mount your existing file systems. 3. Extract binary sets from the media of your choice. 4. Fixup your system's existing _/_e_t_c_/_f_s_t_a_b, changing the occurrences of uuffss to ffffss and let you edit the resulting file. 5. Make new device nodes in your root file system under _/_d_e_v. 6. Don't forget to extract the kkeerrnn set from the distribution. _N_o_t_e_: The existing kernel _w_i_l_l _n_o_t be backed up; doing so would be pointless, since older kernels may not be capable of running NetBSD 1.5.1executables. 7. Install a new boot block. 8. Check your file systems for integrity. While using the miniroot's upgrade program is the preferred method of up- grading your system, it is possible to upgrade your system manually. To do this, follow the following procedure: 1. Place _a_t _l_e_a_s_t the bbaassee binary set in a file system accessible to the target machine. A local file system is preferred, since the NFS subsystem in the NetBSD 1.5.1 kernel may be incompatible with your old binaries. 2. Back up your pre-existing kernel and copy the 1.5.1 kernel into your root partition (_/). 3. Reboot with the 1.5.1 kernel into single-user mode. 4. Check all file systems: # //ssbbiinn//ffsscckk --ppff 5. Mount all local file systems: # //ssbbiinn//mmoouunntt --aa --tt nnoonnffss 6. If you keep _/_u_s_r or _/_u_s_r_/_s_h_a_r_e on an NFS server, you will want to mount those file systems as well. To do this, you will need to en- able the network: # sshh //eettcc//rrcc..dd//nneettwwoorrkk ssttaarrtt 7. Make sure you are in the root file system (_/) and extract the bbaassee binary set: # ccdd // # ppaaxx --zzrrvvppee --ff _/_p_a_t_h_/_t_o_/bbaassee..ttggzz 8. Install a new boot block: # ccdd //uussrr//mmddeecc # ccpp bboooottssdd //..bboooottssdd # ..//iinnssttaallllbboooott //..bboooottssdd bboooottxxxx << _r_o_o_t_-_d_i_s_k E.g.: _r_o_o_t_-_d_i_s_k could be _/_d_e_v_/_r_s_d_0_a. 9. Sync the file systems: # ssyynncc 10. At this point you may extract any other binary sets you may have placed on local file systems, or you may wish to extract additional sets at a later time. To extract these sets, use the following com- mands: # ccdd // # ppaaxx --zzrrvvppee --ff _p_a_t_h___t_o___s_e_t _N_o_t_e_: You _s_h_o_u_l_d _n_o_t extract the eettcc set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand. 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.1. _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_._1 _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 Emmanuel Dreyfus _m_a_n_u_@_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_: 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 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 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 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 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 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 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. This product includes software developed by David Jones. This product includes software developed by Steve C. Woodford. TThhee EEnndd NetBSD May 21, 2001 37