INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/vax DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.4.2 on the _v_a_x 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 UN*X-like operating system derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on twenty different system architectures featuring eight distinct families of CPUs, and is being ported to more. The NetBSD 1.4.2 release contains complete binary releases for fifteen different machine types. (The remaining ones are not fully supported at this time and are thus not part of the binary distri- bution. 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, and nu- merous 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..44..22 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.4.2. NetBSD 1.4.2 is an upgrade of NetBSD 1.4.1, NetBSD 1.4 and earlier re- leases of NetBSD such as versions 1.3.3, 1.2 etc. 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.4 was started are designated by ver- sion identifiers such as 1.4A, 1.4B, 1.4P etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.4.2 can _n_o_t be used to upgrade a sys- tem running one of those intermediate development versions. Trying to use the NetBSD 1.4.2 kernel on such a system _w_i_l_l in all probability re- sult 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.4.2 to determine if a given feature is present or absent in 1.4.2. The development of 1.4, 1.4.1 and 1.4.2 is done on a separate branch in the CVS repository which was created when the release cylcle for 1.4 was started, and during the release cycles for all these versions selective fixes (with minor impact on the stability of the code on the release branch) have been imported from the main development trunk. So, there are features in 1.4.2 which were not in e.g. 1.4H, but the reverse is also true. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..44..11 aanndd 11..44..22 The complete list of changes between NetBSD 1.4.1 and 1.4.2 can be found in the file CHANGES-1.4.2 in the top directory of the source tree. The following are the highlights only. ++oo A driver for the Alteon Gigabit Ethernet cards has been added, see ti(4). ++oo A driver for the Realtek 8129/8239 Fast Ethernet PCI cards have been added, see rl(4). ++oo A driver for the DPT SmartCache and SmartRAID III or IV SCSI adapters has been added, see dpt(4). ++oo A driver for the BOCA IOAT66 6-port ISA serial adapter has been added, see ioat(4). ++oo Support for the X-surf Amiga board has been added. ++oo Support has been added for ext2fs revision 1, with read-only support for the ``sparse super'' and the ``filetype'' options. ++oo BIND has been upgraded to version 8.2.2-P5. ++oo The IPF packet filtering software has been updated to version 3.3.5. ++oo Tcpdump now does hex/ascii dumps of packet contents if asked to do so. ++oo An implementation of the System V user management utilities has been added. ++oo The name ``errno'' is now always a macro which expands to a function call. This is done to ease the integration of thread libraries with the code in both system and third-party libraries. Please include to access the correct definition of ``errno''. ++oo A utility for making temporary files for shell scripts has been added, see mktemp(1). ++oo The automounter utility amd(8) has been updated to fix a security problem. ++oo A security problem in procfs has been fixed. Procfs is not used by default in NetBSD. ++oo The floating point emulation on the ports using the m68k CPU has been reverted to the version in NetBSD 1.4 (the version in 1.4.1 had prob- lems). ++oo Several subsystems have received substantial work, such as RAIDframe, LFS, and the package tools. In addition, many, many bugs have been fixed -- more than 100 problems reported through our problem tracking system have been fixed, and many other non-reported problems have also been found and fixed. See the CHANGES-1.4.2 file for the complete list. KKnnoowwnn ccaavveeaattss wwiitthh 11..44..22 The following are the major known issues with NetBSD 1.4.2. ++oo The upgrade of ipf(8) caused a change of the kernel API. Thus, if you are using ipf(8) you need to upgrade both the kernel and the us- er-land utilities to control that feature in order for it to work. ++oo As part of fixing a kernel bug, ``struct vfsnode'' needed to change size. This will unfortunately, and contrary to tradition for patch releases, cause incompatibilities for users of file system LKMs com- piled for 1.4 and 1.4.1. ++oo Although LFS has been improved between 1.4.1 and 1.4.2, it can proba- bly still be characterized as being of ``beta test'' quality, e.g. filling the file system still gives ``interesting'' effects. It should probably not be used to store critical data quite yet. ++oo The version of the IPF packet filtering software in NetBSD 1.4.2 must be enabled with ``ipf -E'' before filtering or NAT rules can be set. Failure to do so may result in a panic. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..44 aanndd 11..44..11 The complete list of changes between NetBSD 1.4 and 1.4.1 can be found in the file CHANGES-1.4.1 in the top directory of the source tree. ++oo The NetBSD/alpha port's compatibility for Digital UNIX executables has been greatly improved. ++oo Many bug fixes and improvements of the installation tools and utili- ties. ++oo Support for more PCI serial/parallel cards has been added. ++oo It is now possible to boot NetBSD/i386 on systems with 1GB of RAM. ++oo The floating point emulation on the ports using the m68k CPU has been upgraded. ++oo A fatal problem with /dev/random has been found and fixed. ++oo Support for Alpha 21264 ev6 based systems has been added to NetB- SD/alpha. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..33 aanndd 11..44 The NetBSD 1.4 release is a substantial improvement over its predeces- sors. We have provided numerous significant functional enhancements, in- cluding support for many new devices, integration of hundreds of bug fix- es, new and updated kernel subsystems, and many userland enhancements. The results of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize the nearly two years of develop- ment that went into the NetBSD 1.4 release. Some highlights include: ++oo Substantial improvements in the TCP/IP implementation, including nu- merous performance enhancements and bug fixes by Jason Thorpe and others. ++oo A new, high efficiency kernel memory pool allocator by Paul Kranen- burg. This has been integrated into most kernel subsystems. ++oo A new, totally rewritten virtual memory subsystem, UVM, created by Chuck Cranor, which is substantially cleaner and better performing than the old Mach derived VM subsystem. ++oo Improved POSIX and XPG standards compliance. ++oo Completion of the integration of all remaining 4.4BSD Lite-2 kernel improvements and bug fixes that had not been previously integrated. (Integration of all userland components was completed before NetBSD 1.3) ++oo Several new ports, including macppc, bebox, sparc64, next68k, and others, have been integrated into the source tree. ++oo The system compilers have been upgraded to egcs 1.1.1, and the system compiler toolchain now (mostly) uses the latest versions of GNU binu- tils instead of the obsolete versions left over from 4.4BSD Lite. ++oo Everyone's favorite ftp(1) client has been improved even further. See the man page for details. ++oo A new architecture independent console driver, wscons(4), has been integrated into many ports. ++oo Numerous improvements have been made to the audio subsystem support, including support for MIDI device drivers. ++oo Linux compatibility support has been improved. ++oo A number of scheduler enhancements have yielded dramatic improvements in interactive performance and better control of background tasks. ++oo Several network tunneling protocols, including GRE and IP in IP, have been implemented. ++oo Kernel support for the CODA distributed file system has been added. ++oo Manuel Bouyer completed major changes to the IDE support. It is now architecture independent. Major changes have been made to the IDE code for better error handling, improved ATAPI support, 32 bit data I/O support and bus-master DMA support on PCI IDE controllers. ++oo Lennart Augustsson has added full USB support, permitting the use of a wide variety of Universal Serial Bus peripherals. The drivers should easily port to any future platforms that support the PCI bus. See usb(4) for an overview. ++oo RAIDframe, version 1.1, from the Parallel Data Laboratory at Carnegie Mellon University, has been integrated. Supports RAID levels 0, 1, 4, 5, and more. ++oo Luke Mewburn added nsswitch.conf(5) functionality to the system to specify the search order for system databases. ++oo syslogd(8) now supports listening on multiple sockets, to make the chrooting of servers easier. ++oo Most third party packages have been updated to the latest stable re- lease. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. This is the third public release of NetBSD for the VAX. 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. In addition, Anonymous CVS access to the NetBSD source tree has been added since NetBSD 1.4.1; see hhttttpp::////wwwwww..nneettbbssdd..oorrgg//CChhaannggeess//##aannoonnccvvss--aavvaaiillaabbllee We have also added a browsable CVS repository on the web at hhttttpp::////ccvvsswweebb..nneettbbssdd..oorrgg//ccggii--bbiinn//ccvvsswweebb..ccggii// 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 Please refer to hhttttpp::////wwwwww..nneettbbssdd..oorrgg//SSiitteess//nneett..hhttmmll. NNeettBBSSDD 11..44..22 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.4.2 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._4_._2_/ BUGS Known bugs list (somewhat incomplete and out of date). CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.4.2 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (also somewhat incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one di- rectory per architecture, for each of the architectures for which NetBSD 1.4.2 has a binary distribution. There are also 'README.export- control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The NetBSD project maintains a web page at hhttttpp::////wwwwww..NNeettBBSSDD..OORRGG//MMiisscc//ccrryyppttoo--eexxppoorrtt..hhttmmll which should contain up-to-date information on this issue. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: secrsrc.tgz: This set contains the "domestic" sources. These sources may be subject to United States export regulations. _4_2_1_K _g_z_i_p_p_e_d_, _2_M _u_n_c_o_m_p_r_e_s_s_e_d gnusrc.tgz: This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. _1_9_M _g_z_i_p_p_e_d_, _8_4_._3_M _u_n_c_o_m_p_r_e_s_s_e_d syssrc.tgz: This set contains the sources to the NetBSD 1.4.2 ker- nel, config(8), and dbsym(8). _1_3_._9_M _g_z_i_p_p_e_d_, _6_8_._3_M _u_n_c_o_m_p_r_e_s_s_e_d sharesrc.tgz: This set contains the "share" sources, which include the sources for the man pages not associated with any par- ticular program, the sources for the typesettable docu- ment set, the dictionaries, and more. _3_M _g_z_i_p_p_e_d_, _1_1_._9_M _u_n_c_o_m_p_r_e_s_s_e_d src.tgz: This set contains all of the NetBSD 1.4.2 sources which are not mentioned above. _1_4_._4_M _g_z_i_p_p_e_d_, _6_7_._4_M _u_n_c_o_m_p_r_e_s_s_e_d Most of the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The secrsrc.tgz set is contained in the _s_o_u_r_c_e_/_s_e_c_u_r_i_t_y subdirectory. This set, which may only be available to users in the United States and Canada, contains the sources normally found in _/_u_s_r_/_s_r_c_/_d_o_m_e_s_t_i_c - primarily Kerberos and other cryptographic security related software. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the Unit- ed States and Canada. Again, see hhttttpp::////wwwwww..NNeettBBSSDD..OORRGG//MMiisscc//ccrryyppttoo--eexxppoorrtt..hhttmmll for updated information on this issue.) The source sets are distributed as compressed tar files. They may be un- packed into _/_u_s_r_/_s_r_c with the command: ccaatt sseett__nnaammee..ttggzz || gguunnzziipp || ((ccdd //;; ttaarr xxppff -- )) The _s_e_t_s_/_S_p_l_i_t_/ and _s_e_c_u_r_i_t_y_/_S_p_l_i_t_/ subdirectories contain 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 are named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) The split distributions may be reassembled and extracted with ccaatt as follows: ccaatt sseett__nnaammee..???? || gguunnzziipp || ((ccdd //;; ttaarr xxppff -- )) In each of the source distribution set directories, there is a file named _C_K_S_U_M_S which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the in- tegrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. Checksums based on other algorithms may also be present - see the release(7) man page for details. _N_e_t_B_S_D_/_v_a_x _S_u_b_d_i_r_e_c_t_o_r_y _S_t_r_u_c_t_u_r_e The vax-specific portion of the NetBSD 1.4.2 release is found in the _v_a_x subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._4_._2_/_v_a_x_/ _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; this file. The _._m_o_r_e file contains underlined text using the more(1) conventions for indicat- ing italic and bold display. _b_i_n_a_r_y_/ _s_e_t_s_/ vax binary distribution sets; see below. _s_e_c_u_r_i_t_y_/ vax security distribution; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _B_i_n_a_r_y _D_i_s_t_r_i_b_u_t_i_o_n _S_e_t_s The NetBSD vax binary distribution sets contain the binaries which com- prise the NetBSD 1.4.2 release for the vax. There are eight binary dis- tribution sets and the _s_e_c_u_r_i_t_y distribution set. The binary distribu- tion sets can be found in the _v_a_x_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.4.2 distribution tree, and are as follows: bbaassee The NetBSD 1.4.2 vax bbaassee binary distribution. You _m_u_s_t in- stall this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. _1_0_._1_M _g_z_i_p_p_e_d_, _2_4_._8_M _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 libraries (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. _8_._1_M _g_z_i_p_p_e_d_, _2_7_._3_M _u_n_c_o_m_p_r_e_s_s_e_d eettcc This distribution set contains the system configuration files that reside in _/_e_t_c and in several other places. This set _m_u_s_t be installed if you are installing the system from scratch, but should _n_o_t be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and _c_a_r_e_f_u_l_l_y upgrade your configuration files by hand.) _6_0_K _g_z_i_p_p_e_d_, _3_5_0_K _u_n_c_o_m_p_r_e_s_s_e_d ggaammeess This set includes the games and their manual pages. _2_._8_M _g_z_i_p_p_e_d_, _6_._8_M _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn This set contains a NetBSD/vax 1.4.2 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _5_1_7_k _g_z_i_p_p_e_d_, _1_M _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. _4_._2_M _g_z_i_p_p_e_d_, _1_7_._2_M _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_._1_M _g_z_i_p_p_e_d_, _8_._1_M _u_n_c_o_m_p_r_e_s_s_e_d tteexxtt This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. _1_._2_M _g_z_i_p_p_e_d_, _4_._3_M _u_n_c_o_m_p_r_e_s_s_e_d The vax security distribution set is named sseeccrr and can be found in the _v_a_x_/_b_i_n_a_r_y_/_s_e_c_u_r_i_t_y subdirectory of the NetBSD 1.4.2 distribution tree. It contains security- related binaries which depend on cryptographic source code. You do not need this distribution set to use encrypted passwords in your password file; the bbaassee distribution includes a crypt library which can perform only the one-way encryption function. The security distribution includes a version of the Kerberos IV network security system, and a Kerberized version of telnet(1) program. The sseeccrr distribution set can be found only on those sites which carry the complete NetBSD distribution and which can legally obtain it. Because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada. See hhttttpp::////wwwwww..NNeettBBSSDD..OORRGG//MMiisscc//ccrryyppttoo--eexxppoorrtt..hhttmmll for updated information on this issue. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window system are distributed with NetBSD. The sets are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. xxccoommpp The extra libraries and include files needed to compile X source code. xxccoonnttrriibb Programs that were contributed to X. xxffoonntt Fonts needed by X. The vax 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 xxffpp command from /. _N_o_t_e Each directory in the vax binary distribution also has its own checksum files, just as the source distribution does: All BSDSUM files are historic BSD checksums for the various files in that directory, in the format produced by the command: cckkssuumm --oo 11 _f_i_l_e All CKSUM files are POSIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm _f_i_l_e. All MD5 files are MD5 digests for the various files in that direc- tory, in the format produced by the command: cckkssuumm --mm _f_i_l_e. All SYSVSUM files are 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 possible range of system can check the integrity of the release files. NNeettBBSSDD//vvaaxx SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess Hardware supported by NetBSD/vax 1.4.2 includes (but may not be limited to): _C_P_U _t_y_p_e_s_: VAX 11/750, VAX 11/78{0,5}, VAX 8200/8250/8300/8350, VAX 8600/8650, MicroVAX II/VAXstation II, MicroVAX III, Mi- croVAX 3300/3400, MicroVAX 3500/3600, MicroVAX 3800/3900, MicroVAX 2000/VAXstation 2000, VAXstation 3100 model 30,38,40,48,76, VAXstation 3200/3500 and VAXstation 4000/60. _N_e_t_w_o_r_k_i_n_g_: DEUNA/DELUA Unibus ethernet, DEQNA/DELQA Q22 bus ethernet, and LANCE chip where available. _S_e_r_i_a_l _l_i_n_e_s_: DHU11/DHV11/DL11/DLV11/DZ11/DZQ11/DZV11 Unibus/Q22 bus asynchronous lines and DZ11-compatible lines on VAXsta- tions. _D_i_s_k_s_: UDA50 Unibus MSCP controller, KDA50/RQDX1/2/3 Q22 bus MSCP controller, KDB50 BI-bus MSCP controller, MFM and SCSI con- trollers on VAXstations, RP04/05/06/07 and RM02/03/05/80 Massbus disks, and Console RL02 on VAX 8600. Some third-party controllers are also known to work, other do not. _T_a_p_e_s_: TMSCP on Q22 bus (TK50/70, TU81), TMSCP on BI bus and SCSI tapes on VAXstations. _F_l_o_p_p_y_: RX33/RX50 on RQDX controllers. RX50 on VAX 8200. The minimal configuration requires 2M of RAM and ~40MB of disk space, but the installation really requires 6MB RAM unless you plan on using Jedi powers. Here is a table of recommended HD partition sizes for a full install: Partition Advised Needed root (/) 32M 16M user (/usr) 110M 45M swap 2 or 3 * RAM Anything else is up to you! GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa Installation is supported from several media types, including: ++oo Floppy ++oo FTP ++oo Tape ++oo NFS _N_o_t_e Installing on a "bare" machine requires some bootable device; ei- ther a tape or floppy drive or a NFS server together with a ma- chine that can act as a MOP loader, such as another machine run- ning NetBSD. NetBSD/vax can use both BOOTP/DHCP and BOOTPARAMS for netboot installations. The procedure for transferring the distribution sets onto installation media depends on the type of media. most of it is up to you, depending what you want to install, but preferred are to do the installation over network as soon as the install kernel is booted. _C_r_e_a_t_i_n_g _b_o_o_t _t_a_p_e_s Fetch the bootable bootfs image from .../NetBSD-1.4.2/vax/installation/bootfs/boot.fs.gz Gunzip boot.fs.gz and write it on the beginning of the tape. Under NetB- SD this is done via: gguunnzziipp bboooott..ffss..ggzz mmtt --ff //ddeevv//nnrrmmtt00 rreewwiinndd dddd iiff==bboooott..ffss ooff==//ddeevv//nnrrmmtt00 mmtt --ff //ddeevv//nnrrmmtt00 rreewwooffffll Under Ultrix the tape name is different: gguunnzziipp bboooott..ffss..ggzz mmtt --ff //ddeevv//rrmmtt00hh rreewwiinndd dddd iiff==bboooott..ffss ooff==//ddeevv//rrmmtt00hh mmtt --ff //ddeevv//rrmmtt00hh rreewwooffffll Of course, if you have a tape unit other than unit 0 you have to use the corresponding unit number. If you wish to install the sets from tape then stage you will need to download the *.tgz files from .../NetBSD-1.4.2/vax/binary/sets_{_5_0_,_3_3_} (if your disk is less than 200MB you will probably want to exclude the X sets) and then before the 'mt ... rewoffl' run ttaarr ccvvff //ddeevv//nnrrmmtt00 **..ttggzz When you have booted the bootfs and completed the disk partitioning you will be prompted to 'select medium' for install. At this point you will need to press ^Z (Ctrl+Z) to suspend the install tool, then ccdd //mmnntt mmtt --ff //ddeevv//nnrrmmtt00 rreewwiinndd mmtt --ff //ddeevv//nnrrmmtt00 ffssff ttaarr xxvvff //ddeevv//nnrrmmtt00 ffgg then select "install from local dir" and give "/mnt". Note: If your disk is small you will need to be careful about filling it up. If you are using any other OS to create bootable tapes, remember that the blocksize _m_u_s_t be 512 for the file to be bootable! Otherwise it just won't work. _C_r_e_a_t_i_n_g _b_o_o_t _f_l_o_p_p_i_e_s Fetch the bootable bootfs image from .../NetBSD-1.4.2/vax/installation/bootfs/boot.fs.gz and gunzip it. It is a 1MB bootable image that will boot from any floppy of size 1MB and bigger. Note that you _c_a_n_n_o_t install from RX50 floppies due to the small size. This may change in the future. All floppies except RX50 use a standardized format for storing data so writing the bootfs to the floppy can be done on any PC. From DOS the pre- ferred way to do this is using RAWRITE.EXE. _B_o_o_t_i_n_g _f_r_o_m _N_F_S _s_e_r_v_e_r All VAXen that can boot over network uses MOP, a DEC protocol. To be able to use MOP, a MOP daemon must be present on one of the machines on the local network. The boot principle is: ++oo The VAX broadcast a wish to load an image. ++oo A mopd answers and send the boot program to the VAX. ++oo The boot program does rarp/bootp requests, mounts the root filesystem and loads the kernel. ++oo The kernel is loaded and starts executing. If your machine has a disk and network connection, it may be convenient for you to install NetBSD over the network. This involves 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 ma- chine. Configuring the NFS server is normally a task for a system admin- istrator, 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.) There is also very useful documentation at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//nneettwwoorrkk//nneettbboooott// You also must install a MOP loader. If you are booting from another NetB- SD machine, the MOP daemons are included in the distribution, otherwise you may have to install a MOP loader. A loader can be found at ffttpp..ssttaacckkeenn..kktthh..ssee:://ppuubb//OOSS//NNeettBBSSDD//mmooppdd Fetch the latest and read the installation instructions. The file that should be loaded is called boot.mop and is located in .../NetBSD-1.4.2/vax/installation/netboot/boot.mop The kernel to load is the same kernel as the bootfs uses and can be found in .../NetBSD-1.4.2/vax/installation/netboot/netbsd.ram.gz From the install program started in the kernel the rest of the system can be installed. There is also a very good (if somewhat out of date) FAQ for netbooting VAXen at hhttttpp::////wwoorrlldd..ssttdd..ccoomm//~~bbddcc//pprroojjeeccttss//vvaaxxeenn//VVAAXX--nneettbboooott--HHOOWWTTOO..hhttmmll that describes netbooting of VAXen from many different OS'es. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD IInnssttaallllaattiioonn VAX machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of BACKING UP ALL DATA on any attached storage devices. If you are on a Qbus or Unibus system the disk controller(s) need be at the standard CSR addresses for DUA (772150) or DUB (760334) to be recog- nized by the kernel and boot programs. If you are installing on a VAXstation you _m_a_y require a serial console. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm Installation of NetBSD/vax is now easier than ever! For the latest news, problem reports, and discussion, join the port-vax mainlist by mailing a line saying subscribe port-vax to _m_a_j_o_r_d_o_m_o_@_n_e_t_s_b_d_._o_r_g. Also, see hhttttpp::////wwwwww..nneettbbssdd..oorrgg for more infor- mation. If you encounter any problems, please report them via the mailing list or the send-pr(1) program so that they can be fixed for the next release. To install or upgrade NetBSD, you need to first boot the installation program and then interact with the screen-menu program ssyyssiinnsstt. The in- stallation program actually consists of the NetBSD kernel plus an in-mem- ory file system of utility programs. The usual procedure is to write the installation system to the install media, as described earlier. Booting from install media The built-in console monitor understands a bunch of commands, dependent of which VAX you have. To just boot from a device, type 'B' at the '>>>' prompt. Device naming in the console monitor differs a lot from the Unix counterparts. A device looks like "ddcu", where dd is the device type, c is the controller number and u is the device unit. Many console monitors also support the 'SHOW DEV' command, which shows available units to boot from. A summary of the most common boot devices and their name: BB DDUUAA00 -- ffiirrsstt MMSSCCPP ccoonnttrroolllleerr,, uunniitt 00.. BB MMUUAA00 -- ffiirrsstt TTMMSSCCPP ttaappee ccoonnttrroolllleerr,, uunniitt 00.. BB DDKKBB00 -- sseeccoonndd SSCCSSII bbuuss,, uunniitt 00.. BB XXQQAA00 -- ffiirrsstt QQ2222 bbuuss EEtthheerrnneett ccoonnttrroolllleerr.. BB EESSAA00 -- ffiirrsstt LLAANNCCEE EEtthheerrnneett ccoonnttrroolllleerr oonn VVAAXXssttaattiioonnss.. Other devices may be appropriate for your configuration. Then just proceed with the program sysinst. The install descriptions for sysinst that follows can be easily adopted to vax. _R_u_n_n_i_n_g _t_h_e _S_y_s_i_n_s_t _I_n_s_t_a_l_l_a_t_i_o_n _P_r_o_g_r_a_m 1. _I_n_t_r_o_d_u_c_t_i_o_n Using ssyyssiinnsstt, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details to be completed. Do not let this discourage you, the install program is not hard to use. 2. _P_o_s_s_i_b_l_e PCMCIA _i_s_s_u_e_s There is a serious bug that may make installation of NetBSD on PCMCIA machines difficult. This bug does not make _u_s_e of PCMCIA dif- ficult once a machine is installed. If you do not have PCMCIA on your machine ( PCMCIA is only really used on laptop machines), you can skip this section, and ignore the ``[PCMCIA]'' notes. This will explain how to work around the installation problem. What is the bug: The kernel keeps careful track of what interrupts and i/o ports are in use during autoconfiguration. It then allows the PCMCIA devices to pick unused interrupts and ports. Unfortu- nately, not all devices are included in the INSTALL kernels in order to save space. Let's say your laptop has a soundblaster device built in. The INSTALL kernel has no sound support. The PCMCIA code might allocate your soundblaster's IRQ and I/O ports to PCMCIA devices, causing them not to work. This is especially bad if one of the de- vices in question is your ethernet card. This problem will impact some, but not all, users of PCMCIA. If this bug is affecting you, watch the [PCMCIA] notes that will appear in this document. 3. _G_e_n_e_r_a_l The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. ssyyssiinnsstt is a menu driv- en installation system that allows for some freedom in doing the in- stallation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may hit Control- C at any time, but if you do, you'll have to begin the installation process again from scratch. 4. _Q_u_i_c_k _i_n_s_t_a_l_l First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to section 3. This section describes a basic installa- tion, using a CD-ROM install as an example. ++oo What you need. -- The distribution sets (in this example, they are on CD). -- One 1.44M 3.5" floppy. -- A CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of of memory installed. -- The harddisk should have at least + _n megabytes of space free, where _n is the number of megabytes of main memory in your system. If you wish to install the X window system as well, you will need at least 60Mb more. ++oo The Quick Installation -- Insert the boot floppy you just created. Boot the computer. The main menu will be displayed. -- If you wish, you can configure some network settings immedi- ately by choosing the uuttiilliittiieess menu and then ccoonnffiigguurree nneettwwoorrkk. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. -- Choose iinnssttaallll -- You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. -- After your disk has been prepared, choose CCDD--RROOMM as the medium. The default values for the path and device should be ok. -- After all the files have been unpacked, go back to the main menu and select rreebboooott, after you have removed the bootflop- py from the drive. -- NetBSD will now boot. You should log in as root, and set a password for that account. You are also advised to edit the file _/_e_t_c_/_r_c_._c_o_n_f to match your system needs. -- Your installation is now complete. -- For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on hhttttpp::////wwwwww..xxffrreeee8866..oorrgg// 5. _B_o_o_t_i_n_g NetBSD [PCMCIA] Unplug your PCMCIA devices, so that they won't be found by NetBSD. Boot your machine using the boot floppy. The boot loader will start, and will print a countdown and begin booting. If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that. It will take a while to load the kernel from the floppy, probably around a minute or so, then, the kernel boot messages will be dis- played. This may take a little while also, as NetBSD will be probing your system to discover which hardware devices are installed. The most important thing to know is that wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Note that, once the system has finished booting, you need not leave the floppy in the disk drive. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 6. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n [PCMCIA] You can skip this section, as you will only get data from floppy in the first part of the install. If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the utilities menu, and select CCoonnffiigguurree nneettwwoorrkk ooppttiioonn. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using Domain Name Service (DNS), you can give an empty response in reply to answers relating to this. 7. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s To start the installation, select the menu option to install NetBSD from the main menu. The first thing is to identify the disk on which you want to install NetBSD. ssyyssiinnsstt will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like wd0, wd1, sd0, or sd1. Next, depending on whether you are using a wd_x or wd_x disk, you will either be asked for the type of disk (wd_x) you are using or you will be asked if you want to specify a fake geometry for your SCSI disk (sd_x). The types of disk are be IDE, ST-506 or ESDI. If you're in- stalling on an ST-506 or ESDI drive, you'll be asked if your disk supports automatic sector forwarding. If you are _s_u_r_e that it does, reply affirmatively. Otherwise, the install program will automati- cally reserve space for bad144 tables. 8. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k_. ++oo Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. If you want to use the entire disk for NetBSD, you can skip the following section and go to _E_d_i_t_i_n_g _t_h_e NetBSD _d_i_s_k_l_a_b_e_l. ++oo _E_d_i_t_i_n_g _t_h_e NetBSD _d_i_s_k_l_a_b_e_l. The partition table of the NetBSD part of a disk is called a _d_i_s_k_l_a_b_e_l. There are 3 layouts for the NetBSD part of the disk that you can pick from: SSttaannddaarrdd,, SSttaannddaarrdd wwiitthh XX and CCuussttoomm. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. The last option lets you specify everything yourself. You will be presented with the current layout of the NetBSD disklabel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 44..22BBSSDD. A swap partition has a special type called sswwaapp. Some partitions in the disklabel have a fixed purpose. Partition aa is always the root partition, bb is the swap partition, and cc is the whole disk. Partitions ee--hh are available for other use. Traditionally, dd is the partition mounted on the _/_u_s_r directory, but this is historical practice, not a fixed value. You will then be asked to name your disk's disklabel. The de- fault response is mmyyddiisskk. For most purposes this will be OK. If you choose to name it something different, make sure the name is a single word and contains no special characters. You don't need to remember this name. 9. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to pro- ceed, enter yes at the prompt. The install program will now label your disk and make the file sys- tems you specified. The filesystems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installation program after pressing the return key. 10. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s_. The NetBSD distribution consists of a number of _s_e_t_s, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installa- tion, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to section 9 11. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _f_t_p To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press return in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, and the account name and password used to log into that host using ftp. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a hostname for the ftp serv- er. ssyyssiinnsstt will proceed to transfer all the default set files from the remote site to your hard disk. 12. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP number, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press return in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP number instead of a host- name for the NFS server. 13. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M When installing from a CD-ROM, you will be asked to specify the de- vice name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are. ssyyssiinnsstt will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 14. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e_s_y_s_t_e_m In order to install from a local filesystem, you will need to speci- fy the device that the filesystem resides on (for example wd1e) the type of the filesystem, and the directory on the specified filesys- tem where the sets are located. ssyyssiinnsstt will then check if it can indeed access the sets at that location. 15. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a filesystem that is already accessible. ssyyssiinnsstt will ask you for the name of this directory. 16. _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full instal- lation), or only extract sets that you have selected. In the latter case you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kkeerrnn,, bbaassee and eettcc) they will not be shown in this selec- tion menu. Before extraction begins, you can elect to watch the files being ex- tracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles. After all the files have been extracted, all the necessary device node files will be created. If you have already configured network- ing, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the net- work configuration files. 17. _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n_. Congratulations, you have successfully installed NetBSD 1.4.2. You can now reboot the machine, and boot from harddisk. PPoosstt iinnssttaallllaattiioonn sstteeppss Once you've got the operating system running, there are a few things you need to do in order to bring the system into a propperly configured state, with the most important ones described below. 1. Configuring _/_e_t_c_/_r_c_._c_o_n_f If you haven't done any configuration of _/_e_t_c_/_r_c_._c_o_n_f, the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root filesystem mounted read-write. When the system asks you to choose a shell, simply hit return to get to a prompt. If you are asked for a terminal type, respond with vvtt222200 (or whatever is appropriate for your terminal type) and hit return. At this point, you need to configure at least one file in the _/_e_t_c directory. Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi-user boot can proceed. If your _/_u_s_r directory is on a separate partition and you do not know how to use 'ed' or 'ex', you will have to mount your _/_u_s_r partition to gain access to 'vi'. Do the follow- ing: mmoouunntt //uussrr eexxppoorrtt TTEERRMM==vvtt222200 If you have _/_v_a_r on a seperate partition, you need to repeat that step for it. After that, you can edit _/_e_t_c_/_r_c_._c_o_n_f with vi(1). When you have finished, type eexxiitt at the prompt to leave the single-user shell and continue with the multi-user boot. Other values that need to be set in _/_e_t_c_/_r_c_._c_o_n_f for a networked en- vironment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e, furthermore add an _i_f_c_o_n_f_i_g___i_n_t for your interface , along the lines of ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s: ifconfig_de0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Other files in _/_e_t_c that are new to NetBSD 1.4 and may require modi- fication or setting up include _/_e_t_c_/_m_a_i_l_e_r_._c_o_n_f, _/_e_t_c_/_n_s_s_w_i_t_c_h_._c_o_n_f and _/_e_t_c_/_w_s_c_o_n_s_._c_o_n_f. 2. Logging in After reboot, you can log in as root at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the "root" account with good passwords. 3. Adding accounts Use the vipw(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 adduser(8) for more information on the process of 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 3rd party packages There is a lot of software freely available for Unix-based systems, almost all of which can run on NetBSD. Modifications are usually needed to when transferring programs between different Unix-like systems, so the NetBSD packages collection incorporates any such changes necessary to make that software run on NetBSD, and makes the installation (and deinstallation) of the software packages easy. There's also the option of building a package from source, in case there's no precompiled binary available. Precompiled binaries can be found at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess// Package sources for compiling packages can be obtained by retrieving the file ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD-- ccuurrrreenntt//ttaarr__ffiilleess//ppkkggssrrcc..ttaarr..ggzz and extracting it into _/_u_s_r_/_p_k_g_s_r_c. See _/_u_s_r_/_p_k_g_s_r_c_/_R_E_A_D_M_E then for more information. 6. Misc ++oo To adjust the system to your local timezone, point the _/_e_t_c_/_l_o_c_a_l_t_i_m_e symlink to the appropriate file under _/_u_s_r_/_s_h_a_r_e_/_z_o_n_e_i_n_f_o. ++oo Edit _/_e_t_c_/_a_l_i_a_s_e_s to forward root mail to the right place (run newaliases(1) afterwards.) ++oo The _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_f file will almost definitely need to be ad- justed; 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 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm There is no upgrade program for NetBSD/vax; you will have to upgrade your system by hand. Here are some hints about how to do it: ++oo First replace the kernel, /boot and the boot blocks with new ones. The boot system has changed since 1.3. ++oo Reboot the system so you are running with the new kernel. ++oo Untar the wanted distributions. Remember to use the ----uunnlliinnkk flag to tar(1), otherwise you will run into trouble. ++oo Reboot the system once again. ++oo Now you will (hopefully) be up and running in the new world. _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.4.2 _N_o_t_e Only issues effecting an upgrade from NetBSD 1.3 or NetBSD 1.3.x are decribed here. ++oo "machine" directory/link in "/usr/include" Description Some architecture may fail to install the ccoommpp set because the /usr/include/machine directory changed to a symbolic link in NetBSD 1.4. Fix If this happens, you can use the command # rrmm --rr //uussrr//iinncclluuddee//mmaacchhiinnee to remove the old directory and it contents and reinstall the ccoommpp set. 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)m 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. If you're inter- ested in doing a serious amount of work on a specific port, you probably should contact the "owner" of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: _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 some- where, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. 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, WWW and SUP server. ++oo Redback Networks, Inc. for hosting the NetBSD Mail server. ++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 organiztions (each in alphabetical or- der) have made donations or loans of hardware and/or money, to sup- port NetBSD development, and deserve credit for it: Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Soren Jorvang Scott Kaplan Noah M. Keiserman John Kohl Chris Legrow Ted Lemon Neil J. McRae Perry E. Metzger Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation 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. VMC Harald Frank, Germany Warped Communications, Inc. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) ++oo Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) WWee aarree...... (in alphabetical order) _T_h_e _N_e_t_B_S_D _c_o_r_e _g_r_o_u_p_: Alistair Crooks _a_g_c_@_N_e_t_B_S_D_._O_R_G Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_N_e_t_B_S_D_._O_R_G Frank van der Linden _f_v_d_l_@_N_e_t_B_S_D_._O_R_G Luke Mewburn _l_u_k_e_m_@_N_e_t_B_S_D_._O_R_G Christos Zoulas _c_h_r_i_s_t_o_s_@_N_e_t_B_S_D_._O_R_G _T_h_e _p_o_r_t_m_a_s_t_e_r_s _(_a_n_d _t_h_e_i_r _p_o_r_t_s_)_: Mark Brinicombe _m_a_r_k_@_N_e_t_B_S_D_._O_R_G aarrmm3322 Jeremy Cooper _j_e_r_e_m_y_@_N_e_t_B_S_D_._O_R_G ssuunn33xx Ross Harvey _r_o_s_s_@_N_e_t_B_S_D_._O_R_G aallpphhaa Ignatios Souvatzis _i_s_@_N_e_t_B_S_D_._O_R_G aammiiggaa Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_N_e_t_B_S_D_._O_R_G sshh33 Eduardo Horvath _e_e_h_@_N_e_t_B_S_D_._O_R_G ssppaarrcc6644 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 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 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 Scott Reynolds _s_c_o_t_t_r_@_N_e_t_B_S_D_._O_R_G mmaacc6688kk Darrin Jewell _d_b_j_@_N_e_t_B_S_D_._O_R_G nneexxtt6688kk Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_N_e_t_B_S_D_._O_R_G bbeebbooxx Wolfgang Solfrank _w_s_@_N_e_t_B_S_D_._O_R_G ooffppppcc 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 hhpp330000 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_._4_._2 _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_: Chris G. Demetriou _c_g_d_@_N_e_t_B_S_D_._O_R_G Havard Eidnes _h_e_@_N_e_t_B_S_D_._O_R_G Ted Lemon _m_e_l_l_o_n_@_N_e_t_B_S_D_._O_R_G 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 _D_e_v_e_l_o_p_e_r_s _a_n_d _o_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_: Steve Allen _w_o_r_m_e_y_@_N_e_t_B_S_D_._O_R_G Julian Assange _p_r_o_f_f_@_N_e_t_B_S_D_._O_R_G Lennart Augustsson _a_u_g_u_s_t_s_s_@_N_e_t_B_S_D_._O_R_G Christoph Badura _b_a_d_@_N_e_t_B_S_D_._O_R_G Robert V. Baron _r_v_b_@_N_e_t_B_S_D_._O_R_G Erik Berls _c_y_b_e_r_@_N_e_t_B_S_D_._O_R_G John Birrell _j_b_@_N_e_t_B_S_D_._O_R_G Mason Loring Bliss _m_a_s_o_n_@_N_e_t_B_S_D_._O_R_G Manuel Bouyer _b_o_u_y_e_r_@_N_e_t_B_S_D_._O_R_G John Brezak _b_r_e_z_a_k_@_N_e_t_B_S_D_._O_R_G Allen Briggs _b_r_i_g_g_s_@_N_e_t_B_S_D_._O_R_G Aaron Brown _a_b_r_o_w_n_@_N_e_t_B_S_D_._O_R_G David Brownlee _a_b_s_@_N_e_t_B_S_D_._O_R_G Frederick Bruckman _f_r_e_d_b_@_N_e_t_B_S_D_._O_R_G Jon Buller _j_o_n_b_@_N_e_t_B_S_D_._O_R_G Simon Burge _s_i_m_o_n_b_@_N_e_t_B_S_D_._O_R_G Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t Robert Byrnes _b_y_r_n_e_s_@_N_e_t_B_S_D_._o_r_g D'Arcy J.M. Cain _d_a_r_c_y_@_N_e_t_B_S_D_._O_R_G Dave Carrel _c_a_r_r_e_l_@_N_e_t_B_S_D_._O_R_G Bill Coldwell _b_i_l_l_c_@_N_e_t_B_S_D_._O_R_G Julian Coleman _j_d_c_@_N_e_t_B_S_D_._O_R_G Chuck Cranor _c_h_u_c_k_@_N_e_t_B_S_D_._O_R_G Aidan Cully _a_i_d_a_n_@_N_e_t_B_S_D_._O_R_G Johan Danielsson _j_o_d_a_@_N_e_t_B_S_D_._O_R_G Matt DeBergalis _d_e_b_e_r_g_@_N_e_t_B_S_D_._O_R_G Rob Deker _d_e_k_e_r_@_N_e_t_B_S_D_._O_R_G Chris G. Demetriou _c_g_d_@_N_e_t_B_S_D_._O_R_G Jaromir Dolecek _j_d_o_l_e_c_e_k_@_N_e_t_B_S_D_._O_R_G Andy Doran _a_d_@_N_e_t_B_S_D_._O_R_G Roland Dowdeswell _e_l_r_i_c_@_N_e_t_B_S_D_._O_R_G Matthias Drochner _d_r_o_c_h_n_e_r_@_N_e_t_B_S_D_._O_R_G Jun Ebihara _j_u_n_@_N_e_t_B_S_D_._O_R_G Havard Eidnes _h_e_@_N_e_t_B_S_D_._O_R_G Enami Tsugutomo _e_n_a_m_i_@_N_e_t_B_S_D_._O_R_G Bernd Ernesti _v_e_e_g_o_@_N_e_t_B_S_D_._O_R_G Erik Fair _f_a_i_r_@_N_e_t_B_S_D_._O_R_G Hubert Feyrer _h_u_b_e_r_t_f_@_N_e_t_B_S_D_._O_R_G Thorsten Frueauf _f_r_u_e_a_u_f_@_N_e_t_B_S_D_._O_R_G Castor Fu _c_a_s_t_o_r_@_N_e_t_B_S_D_._O_R_G 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 Brian C. Grayson _b_g_r_a_y_s_o_n_@_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 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 HAYAKAWA Koichi _h_a_y_a_@_N_e_t_B_S_D_._O_R_G Rene 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 Dean Huxley _d_e_a_n_@_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 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 Soren Jorvang _s_o_r_e_n_@_N_e_t_B_S_D_._O_R_G Antti Kantee _p_o_o_k_a_@_N_e_t_B_S_D_._O_R_G Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u Thomas Klausner _w_i_z_@_N_e_t_B_S_D_._O_R_G Klaus Klein _k_l_e_i_n_k_@_N_e_t_B_S_D_._O_R_G 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 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 Dan McMahill _d_m_c_m_a_h_i_l_l_@_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 Tohru Nishimura _n_i_s_i_m_u_r_a_@_N_e_t_B_S_D_._O_R_G Masaru Oki _o_k_i_@_N_e_t_B_S_D_._O_R_G Greg Oster _o_s_t_e_r_@_N_e_t_B_S_D_._O_R_G Herb Peyerl _h_p_e_y_e_r_l_@_N_e_t_B_S_D_._O_R_G Matthias Pfaller _m_a_t_t_h_i_a_s_@_N_e_t_B_S_D_._O_R_G Dante Profeta _d_a_n_t_e_@_N_e_t_B_S_D_._O_R_G Chris Provenzano _p_r_o_v_e_n_@_N_e_t_B_S_D_._O_R_G Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t Darren Reed _d_a_r_r_e_n_r_@_N_e_t_B_S_D_._O_R_G Michael Richardson _m_c_r_@_N_e_t_B_S_D_._O_R_G Tim Rightnour _g_a_r_b_l_e_d_@_N_e_t_B_S_D_._O_R_G Gordon Ross _g_w_r_@_N_e_t_B_S_D_._O_R_G Heiko W. Rupp _h_w_r_@_N_e_t_B_S_D_._O_R_G SAITOH Masanobu _m_s_a_i_t_o_h_@_N_e_t_B_S_D_._O_R_G Curt Sampson _c_j_s_@_N_e_t_B_S_D_._O_R_G Wilfredo Sanchez _w_s_a_n_c_h_e_z_@_N_e_t_B_S_D_._O_R_G Ty Sarna _t_s_a_r_n_a_@_N_e_t_B_S_D_._O_R_G SATO Kazumi _s_a_t_o_@_N_e_t_B_S_D_._O_R_G Matthias Scheler _t_r_o_n_@_N_e_t_B_S_D_._O_R_G Karl Schilke (rAT) _r_a_t_@_N_e_t_B_S_D_._O_R_G Konrad Schroder _p_e_r_s_e_a_n_t_@_N_e_t_B_S_D_._O_R_G 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 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 Noriyuki Soda _s_o_d_a_@_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 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 Kimmo Suominen _k_i_m_@_N_e_t_B_S_D_._O_R_G Matt Thomas _m_a_t_t_@_N_e_t_B_S_D_._O_R_G Christoph Toshok _t_o_s_h_o_k_@_N_e_t_B_S_D_._O_R_G Izumi Tsutsui _t_s_u_t_s_u_i_@_N_e_t_B_S_D_._O_R_G UCHIYAMA Yasushi _u_c_h_@_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 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 Colin Wood _e_n_d_e_r_@_N_e_t_B_S_D_._O_R_G LLeeggaall MMuummbboo--JJuummbboo 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 Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Adam Glass and Charles Han- num. This product includes software developed by Adam Glass. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Herb Peyerl. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Mark Brinicombe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed at Ludd, University of Lule}, Sweden. This product includes software developed by Gordon W. Ross. This product includes software developed by Ben Harris. This product includes software developed by Adam Glass, David Jones, and Gordon Ross. NetBSD 23 March 1999 28