INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/mac68k. CCOONNTTEENNTTSS About this Document............................................2 What is NetBSD?................................................2 Upgrade path to NetBSD 1.6.....................................2 Changes Between The NetBSD 1.5 and 1.6 Releases................3 Kernel......................................................3 Networking..................................................3 File system.................................................4 Security....................................................4 System administration and user tools........................5 Miscellaneous...............................................5 mac68k specific.............................................6 The Future of NetBSD...........................................6 Sources of NetBSD..............................................7 NetBSD 1.6 Release Contents....................................7 NetBSD/mac68k subdirectory structure........................8 Binary distribution sets....................................9 NetBSD/mac68k System Requirements and Supported Devices.......11 Supported models...........................................11 Supported devices..........................................11 Unsupported models.........................................12 Known hardware issues with this release....................12 Getting the NetBSD System on to Useful Media..................13 Preparing your System for NetBSD installation.................14 Installing the NetBSD System (Sysinst Method).................15 Running the sysinst installation program...................15 Introduction............................................15 Possible hardware-specific issues.......................15 General.................................................16 Quick install...........................................16 Booting NetBSD..........................................18 Network configuration...................................19 Preparing a disk for Mac OS and NetBSD..................19 Installation drive selection and parameters.............19 Partitioning the disk...................................19 Preparing your hard disk................................21 Getting the distribution sets...........................22 Installation using ftp..................................22 Installation using NFS..................................22 Installation from CD-ROM................................22 Installation from Mac OS file systems...................23 Installation from an unmounted file system..............23 Installation from a local directory.....................23 Extracting the distribution sets........................23 Finalizing your installation............................23 Installing the NetBSD System (Traditional Method).............23 Preparing the file system(s)...............................23 Installing the files.......................................24 Installation of base files.................................25 Booting the system.........................................25 Post installation steps.......................................26 Upgrading a previously-installed NetBSD System................28 Compatibility Issues With Previous NetBSD Releases............29 Issues affecting an upgrade from NetBSD 1.5................29 Issues affecting an upgrade from NetBSD 1.4 or prior.......30 Using online NetBSD documentation.............................31 Administrivia.................................................32 Thanks go to..................................................32 We are........................................................34 Legal Mumbo-Jumbo.............................................39 The End.......................................................41 DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.6 on the _m_a_c_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 fifty three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD 1.6 release contains complete binary releases for thirty eight different system architectures. (The fifteen 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..66 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.6. NetBSD 1.6 is an upgrade of NetBSD 1.5.3 and earlier major and patch re- leases 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.6 was started are designated by ver- sion identifiers such as 1.6A, 1.6B, etc. These identifiers do not des- ignate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can _n_o_t be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system _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.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 11..55 aanndd 11..66 RReelleeaasseess The NetBSD 1.6 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over eighteen months of develop- ment that went into the NetBSD 1.6 release. Some highlights include: _K_e_r_n_e_l ++oo Ports to new platforms including: algor, dreamcast, evbarm, hpcarm, hpcsh, newsmips, sandpoint, sgimips, sun2, and walnut. ++oo Unified Buffer Cache (UBC) removes size restriction of the file sys- tem's buffer cache to use all available RAM (if not otherwise used!) and improves overall system performance. ++oo Round-robin page colouring implemented for various ports for better cache utilisation, more deterministic run-time behaviour, and faster program execution. ++oo A rewritten SCSI middle layer to provide a cleaner interface between the different kernel layers, including a kernel thread to handle er- ror recovery outside of the interrupt context. See scsipi(9). ++oo A new pipe implementation with significantly higher performance due to lower overheads, which uses the UVM Page Loan facility. ++oo A work-in-progress snapshot of ACPI support, based on the 20010831 snapshot of the Intel ACPICA reference implementation. ++oo USB 2.0 support, in the form of a preliminary driver for the ehci(4) host controller. ++oo Basic kernel support for IrDA in the form of the irframe(4) IrDA frame level driver. Serial dongles and the oboe(4) driver are cur- rently supported. ++oo Kernel configuration files can be embedded into the kernel for later retrieval. Refer to INCLUDE_CONFIG_FILE in options(4) for more in- formation. ++oo Many more kernel tunable variables added to sysctl(8). ++oo Linux binary emulation has been greatly improved, and now supports Linux kernel version 2.4.18. _N_e_t_w_o_r_k_i_n_g ++oo Hardware assisted IPv4 TCP and UDP checksumming and caching of the IPv6 TCP pseudo header. Support for checksum offloading on the DP83820 Gigabit Ethernet, 3Com 3c90xB, 3Com 3c90xC, and Alteon Tigon/Tigon2 Gigabit Ethernet cards. ++oo Zero-Copy for TCP and UDP transmit path achieved through page loaning code for ssoosseenndd(). ++oo In-kernel ISDN support, from the ISDN4BSD project. ++oo 802.1Q VLAN (virtual LAN) support. See vlan(4). ++oo IPFilter now supports IPv6 filtering. ++oo ndbootd(8) added; used to netboot NetBSD/sun2 machines. ++oo racoon(8) added; IKE key management daemon for IPsec key negotiation, from the KAME project. ++oo WEP encryption supported in ifconfig(8) and awi(4) driver. ++oo wi(4) and wiconfig(8) now support scanning for access points, and de- faults to BSS instead of ad-hoc mode. ++oo Bridging support; currently only for ethernet. See bridge(4). ++oo In-kernel PPP over Ethernet (PPPoE) - RFC 2516, with much lower over- head than user-land PPPoE clients. See pppoe(4). ++oo ifwatchd(8) added; invokes up-script and down-script when a network interface goes up and down. Used by pppoe(4). _F_i_l_e _s_y_s_t_e_m ++oo Enhanced stability of LFS version 2, the BSD log-structured file sys- tem. ++oo dump(8), dumpfs(8), fsck_ffs(8), fsirand(8), newfs(8), and tunefs(8) support a --FF option to manipulate file system images in regular files. ++oo makefs(8) added; creates file system images from a directory tree. (Currently ffs only.) ++oo Enhanced ffffss__ddiirrpprreeff() by Grigoriy Orlov, which noticeably improves performance on FFS file systems when creating directories, and subse- quently manipulating them. ++oo Fixes for free block tracking and directory block allocation in FFS softdeps. ++oo Correctly support FFS file systems with a large number of cylinder groups. ++oo Fix the endian independant FFS (FFS_EI) support. ++oo newfs(8) calculates default block size from the file system size, and uses the largest possible cylinders/group (cpg) value if --cc isn't given. ++oo dpti(4) driver added; an implementation of the DPT/Adaptec SCSI/I2O RAID management interface. Allows the use of the Linux versions of ddppttmmggrr, rraaiidduuttiill, ddpptteelloogg, (etc). ++oo Support for Windows 2000 `NTFS' (NTFS5). ++oo Tagged queueing support for SCSI drivers based on the ncr53c9x con- troller. _S_e_c_u_r_i_t_y ++oo Addition of a chroot(8) hierarchy for services including named(8), ntpd(8), and sshd(8). ++oo Additional passwd(5) ciphers: MD5, and DES with more encryption rounds. See passwd.conf(5). ++oo Several more code audits were performed. ++oo _/_e_t_c_/_s_e_c_u_r_i_t_y performs many more checks and is far more flexible in how it monitors changes. See security.conf(5). _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 sushi(8) added; a menu based system administration tool. ++oo pgrep(1) and pkill(1) added; find or signal processes by name or oth- er attributes. ++oo System upgrades are made easier through the etcupdate(8) script which helps updating the _/_e_t_c config files interactively, and the _/_e_t_c_/_p_o_s_t_i_n_s_t_a_l_l script which is provided to check for or fix config- uration changes that have occurred in NetBSD. ++oo stat(1) added; a user interface to the information returned by the stat(2) system call. ++oo BSD sort(1) replaces GNU sort(1). ++oo The ``stop'' operation for rc.d(8) scripts waits until the service terminates before returning. This improves the reliability of ``restart'' operations as well. ++oo Swap devices can be removed at system shutdown by enabling swapoff in rc.conf(5). ++oo An optional watchdog timer which will terminate rc.shutdown(8) after the number of seconds provided in rcshutdown_timeout from rc.conf(5). _M_i_s_c_e_l_l_a_n_e_o_u_s ++oo Support for multibyte LC_CTYPE locales has been integrated from the Citrus project. Many Chinese, Japanese, Korean, and other encodings are now available. ++oo Full support for cross-compilation of the base system, even as a non- root user! _s_r_c_/_b_u_i_l_d_._s_h is available for doing arbitrary cross- builds; see _s_r_c_/_B_U_I_L_D_I_N_G for more information. At least 38 ports for the NetBSD 1.6 release were cross-built on a NetBSD/i386 system using this mechanism. ++oo Migrated the following CPU platforms to ELF: arm, and m68k (including amiga, hp300, mac68k, mvme68k, sun2, and x68k). ++oo Updates of most third party packages that are shipped in the base system to the following latest stable releases: -- amd 6.0.6 -- BIND 8.3.3 -- binutils 2.11.2 -- bzip2 1.0.2 -- cvs 1.11 -- dhcp 3.0.1rc9 -- file 3.38 -- gcc 2.95.3 -- groff 1.16.1 -- Heimdal 0.4e -- IPfilter 3.4.27 -- kerberos4 1.1 -- ksh from pdksh 5.2.14p2 -- less 374 -- nvi 1.79 -- OpenSSH 3.4 -- OpenSSL 0.9.6g -- Postfix 1.1.11 -- ppp 2.4.0 -- routed 2.24 -- sendmail 8.11.6 -- tcpdump 3.7.1 ++oo Many new packages in the _p_k_g_s_r_c system, including the latest open source desktop KDE3, OpenOffice, perl, Apache and many more. At the time of writing, there are over 3000 third party packages available in pkgsrc. ++oo Added AGP GART driver agp(4) for faster access to graphics boards. ++oo init(8) will create an mfs (memory based file system) _/_d_e_v if _/_d_e_v_/_c_o_n_s_o_l_e is missing. ++oo vmstat(8) displays kernel hash statistics with --HH and --hh _h_a_s_h. ++oo wscons(4) supports blanking of VGA consoles. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. _m_a_c_6_8_k _s_p_e_c_i_f_i_c NetBSD 1.6 is the seventh major release of NetBSD for the m68k-based Mac- intosh. For the mac68k port, NetBSD 1.6 offers improved support for a variety of PowerBook models, many of which now support the built-in keyboard and display as a console. Please see the _N_e_t_B_S_D_/_m_a_c_6_8_k _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 section for de- tails. There is still a lot of work to be done and help is welcomed. NetBSD 1.6 on the mac68k platform is, as usual, also fully backward compatible with old NetBSD/mac68k binaries, so you don't need to recompile all of your local programs. 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..66 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.6 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._6_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.6 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.6 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. _5_5 _M_B _g_z_i_p_p_e_d_, _2_4_7 _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. _1_2 _M_B _g_z_i_p_p_e_d_, _9_4 _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. _4 _M_B _g_z_i_p_p_e_d_, _1_6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssrrcc This set contains all of the base NetBSD 1.6 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. _2_7 _M_B _g_z_i_p_p_e_d_, _1_3_6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssyyssssrrcc This set contains the sources to the NetBSD 1.6 kernel for all architectures; config(8); and dbsym(8). _2_2 _M_B _g_z_i_p_p_e_d_, _1_1_4 _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 _M_B _g_z_i_p_p_e_d_, _3_9_4 _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. Except for the ppkkggssrrcc set, which is traditionally unpacked into _/_u_s_r_/_p_k_g_s_r_c, all sets may be unpacked 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 distribution 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_a_c_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 mac68k-specific portion of the NetBSD 1.6 release is found in the _m_a_c_6_8_k subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._6_/_m_a_c_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 kernel containing code for everything supported in this release using the standard SCSI driver. _n_e_t_b_s_d_-_G_E_N_E_R_I_C_S_B_C_._g_z A kernel containing code for everything supported in this release using the SBC variant of the SCSI driver. _s_e_t_s_/ mac68k binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _i_n_s_t_k_e_r_n_e_l_/ mac68k boot and installation kernels; see instal- lation section (Sysinst Method), below. _m_i_s_c_/ Miscellaneous mac68k installation utilities; see the Traditional method installation section, be- low. _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD mac68k binary distribution sets contain the binaries which comprise the NetBSD 1.6 release for the mac68k. There are eight binary distribution sets. The binary distribution sets can be found in the _m_a_c_6_8_k_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.6 distribution tree, and are as follows: bbaassee The NetBSD 1.6 mac68k bbaassee binary distribution. You _m_u_s_t in- stall this distribution set. It contains the base NetBSD util- ities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. _1_7 _M_B _g_z_i_p_p_e_d_, _4_1 _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_4 _M_B _g_z_i_p_p_e_d_, _5_3 _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. _1 _M_B _g_z_i_p_p_e_d_, _1 _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 _M_B _g_z_i_p_p_e_d_, _7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn--GGEENNEERRIICC This set contains a NetBSD/mac68k 1.6 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install either this distribution set or kern-GENERICSBC. _1 _M_B _g_z_i_p_p_e_d_, _3 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn--GGEENNEERRIICCSSBBCC This set contains a NetBSD/mac68k 1.6 GENERICSBC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install either this distribution set or kern-GENERIC. _1 _M_B _g_z_i_p_p_e_d_, _3 _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. _7 _M_B _g_z_i_p_p_e_d_, _2_7 _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. _3 _M_B _g_z_i_p_p_e_d_, _8 _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. _2 _M_B _g_z_i_p_p_e_d_, _6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window System are distributed with NetBSD. The sets are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. _3 _M_B _g_z_i_p_p_e_d_, _7 _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. _2 _M_B _g_z_i_p_p_e_d_, _8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoonnttrriibb Programs that were contributed to X. _1 _M_B _g_z_i_p_p_e_d_, _1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxffoonntt Fonts needed by X. _6 _M_B _g_z_i_p_p_e_d_, _7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxmmiisscc Miscellaneous X programs. _1 _M_B _g_z_i_p_p_e_d_, _1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxsseerrvveerr The Xmac68k _m_o_n_o_c_h_r_o_m_e server with man pages. _2 _M_B _g_z_i_p_p_e_d_, _4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d The mac68k 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 filenames stored in the sets are relative and therefore the files are extracted _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y. Therefore, 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 root directory ( _/ ) of your system. Kernels suitable for booting from an AppleShare server may be found in the _m_a_c_6_8_k_/_b_i_n_a_r_y_/_k_e_r_n_e_l_s subdirectory of the NetBSD 1.6 distribution tree. These kernels are generally named something like _n_e_t_b_s_d_-_G_E_N_E_R_I_C_._g_z and can be booted as-is by the NetBSD/mac68k Booter utility, if desired. Please note that these kernels are simply gzipped and are not in tar archives. The Mac OS based utilities necessary for installing and running NetBSD can be found in the _m_a_c_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c subdirectory of the NetBSD 1.6 distribution tree. The important files in this directory are as follows: _B_o_o_t_e_r_._s_e_a_._h_q_x The NetBSD/mac68k Booter utility. This program is used to boot the NetBSD kernel from within Mac OS. _1_4_1 _K_B _a_r_c_h_i_v_e_d _I_n_s_t_a_l_l_e_r_._s_e_a_._h_q_x The NetBSD/mac68k Installer utility. This program is used to install the distribution sets onto your NetBSD partition(s). This utility is used only in a Tradi- tional method installation; it is not used or required for an installation using the ssyyssiinnsstt method. _1_4_7 _K_B _a_r_c_h_i_v_e_d _M_k_f_s_._s_e_a_._h_q_x The Mkfs utility. This program is used to format your chosen partitions so that they can be used with NetBSD. This utility is used only in a Traditional method installation; it is not used or required for an installation using the ssyyssiinnsstt method. _7_6 _K_B _a_r_c_h_i_v_e_d These files are all BinHexed, self-extracting archives. If you need them, the sources for these utilities are in the _s_r_c subdirectory. This utility is used only in a Traditional method installation. _N_o_t_e_: Each directory in the mac68k binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//mmaacc6688kk SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess NetBSD/mac68k 1.6 runs on several of the older Macintosh computers. About 4 MB of RAM is sufficient to boot a stripped-down custom kernel, and a subset of the system can be squeezed onto a 40 MB hard disk with considerable creativity and persistence. However, an 80 MB disk should be considered a practical minimum, and to do anything more interesting than booting at least 8 MB of RAM and more disk space is recommended. About 180 MB will be necessary to install all of the NetBSD/mac68k 1.6 binary system distribution sets (note that this does not count swap space!). You can drop this to 150 MB if you choose not to install the binary X11 dis- tribution sets. Much more disk space is required to install the source and objects as well; a complete source distribution, including X11, con- sumes nearly 1 GB of storage. Please note that to install NetBSD/mac68k 1.6 using the ssyyssiinnsstt method, your system must have a minimum of 6 MB of RAM and 60 MB of available disk space (i.e. not part of an in-use HFS partition). _S_u_p_p_o_r_t_e_d _m_o_d_e_l_s ++oo Mac II, IIx, IIcx, SE/30, IIci, IIsi, IIvx, IIvi ++oo Performa 400/405/410/430, Performa 450, Performa 460/466/467 ++oo Performa 520, Performa 550/560, Performa 600/600CD ++oo LC II, LC III, LC III+, LC 520, LC 550 ++oo MacTV ++oo Classic II, Color Classic ++oo Centris 650 ++oo Quadra 610, Quadra 630, Quadra 650, Quadra 700, Quadra 800 ++oo Quadra/Centris 660AV, Quadra 840AV ++oo PowerBook 140, PowerBook 145/145B, PowerBook 170 ++oo PowerBook 160, PowerBook 165, PowerBook 180 ++oo PowerBook 165c, PowerBook 180c, PowerBook 550c _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo Onboard SCSI bus and most SCSI tapes, hard drives, and CD-ROMs ++oo Internal sound -- enough to beep on some machines, anyway ++oo Most basic NuBus video cards (there have been some problems with some 24-bit color cards and with most QuickDraw acclera- tors) ++oo Both internal serial ports ++oo ADB keyboards and mice (both Apple and a number of third party multi-button mice and trackballs are supported) ++oo Ethernet cards based on the National Semiconductor 8390 and the SONIC (DP83932) chips (Asante, Apple, and a few others -- prob- lems still with Ethernet and many NuBus video cards) ++oo Ethernet cards based on the SMC 91c92 and 91c100 (FEAST) chips. This includes the AsanteFAST 10/100 cards ++oo Onboard Ethernet based on the SONIC chip for Quadra-series Macs ++oo Onboard Ethernet based on the MACE (Am79C940) chip for the Quadra AV-series Macs ++oo Ethernet port on Asante NetDock and Newer Ether MicroDock, for PowerBook Duo series ++oo Comm-slot Ethernet should be working for most machines/cards If your 68030 system is not listed above, it may be because of a problem with accessing onboard video, and it may still work with a serial con- sole. Some of the known ones in this category: ++oo Mac Classic series ++oo PowerBook Duo series If your 68LC040 system is not listed above, it is due to a problem with floating point emulation (FPE) for this type of processor. Machines in this category include: ++oo Newer LC-series machines (47x, 57x) ++oo Newer Performa-series machines (47x, 57x, 58x, 63x, 640) ++oo Some PowerBook 500-series Macs _U_n_s_u_p_p_o_r_t_e_d _m_o_d_e_l_s ++oo Macintosh IIfx This machine has unusual custom chips for the ADB and serial interfaces which make support for it difficult. Work is in progress on this, though. ++oo Quadra 900/950 These machines have I/O processor chips for their ADB inter- faces similar to those used in the IIfx and thus face similar support problems. Note that you can use a serial console on these systems. ++oo PowerPC-based Macs This is a separate effort from the mac68k port. PowerMacs use hardware that is often fairly different from that of the mac68k port. If you are interested in this, you might want to take a look at the new NetBSD/macppc port: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//iinnddeexx..hhttmmll _K_n_o_w_n _h_a_r_d_w_a_r_e _i_s_s_u_e_s _w_i_t_h _t_h_i_s _r_e_l_e_a_s_e ++oo Real Time Clock Due to oddities of the Macintosh hardware interrupt priority scheme, NetBSD/mac68k keeps very poor time. Under a high inter- rupt load (e.g. SCSI or serial port activity) , a machine can lose several minutes per hour. A consequence of this problem is that attempting to run nnttppdd is generally rather pointless. ++oo SCSI difficulties The NetBSD/mac68k SCSI drivers are not quite as robust as their Mac OS counterparts. Symptoms of these problems are that some SCSI disks will not work under NetBSD that work fine under Mac OS. Other problems include occasional file system corruption with some types of drives and the general unreliability of re- movable SCSI media. Keep in mind that there are no clear pat- terns with these problems, and they do not appear to affect the majority of users. GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa There are currently two installation methods available for initial in- stallation of NetBSD on Apple Macintosh 68000-based systems. Neither sup- ports all installation media types at this time, so the one you select must be compatible with the media you have available on your system. ++oo The ssyyssiinnsstt method of installation uses an Installation Kernel which is a minimal NetBSD system with a memory resident set of utilities that are capable of partitioning the disk, initializing the file sys- tems, and loading them from the archive files. Since the installa- tion kernel does not currently support access to Mac OS HFS file sys- tems this method requires that the Binary Distribution Sets be acces- sible from CD-ROM, remote NFS partition, or via FTP access. ++oo The Traditional method of installation uses Mac OS hosted utilities to partition your disk, initialize the partitions for use by NetBSD, and load the file systems from archive files stored on the Mac OS HFS file system. This method requires that the Binary Distribution Sets reside on a local Macintosh hard drive, a CD-ROM, or an AppleShare volume. The Traditional method of installation is currently supported from the local Macintosh hard drive, from a CD-ROM, or from an AppleShare volume (however, you may ugrade a system from within NetBSD; see the _U_p_g_r_a_d_i_n_g _a _p_r_e_v_i_o_u_s_l_y_-_i_n_s_t_a_l_l_e_d _N_e_t_B_S_D _S_y_s_t_e_m section for more details). If you are installing from a local hard drive, this means that you'll need at least enough room for the largest file that you will have to in- stall. This is the 15.2 MB _b_a_s_e_._t_g_z file. There has been talk of allow- ing an install from split files. If you have the time, desire, and knowl- edge, please feel free to add that functionality. If the install is being done from an AppleShare-mounted volume, the NetBSD/mac68k Installer must be in the same folder as the binary distri- bution sets. Each distribution file is in _r_a_w archive format. ++oo Distribution files must be downloaded in binary mode. Common web browsers may not be suitable for this task; FTP clients such as Fetch and Anarchie work fine, but be sure to specify a binary file trans- fer. ++oo The files should not be unpacked. If you have the Internet Config extension installed, you can disable this in the ``Helpers'' dialog by removing the entry associated with ``.tgz'' files. Other FTP clients may require separate changes; consult your package's documen- tation. ++oo If you are installing from a CD-ROM, the distribution sets are al- ready in the proper format. No special handling is required. You will also need to collect the Mac OS installation tools from the _m_a_c_6_8_k_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c subdirectory of the NetBSD 1.6 distribution: Mk- fs, NetBSD/mac68k Installer, and NetBSD/mac68k Booter. These three are in BinHexed, self-extracting archives as Mkfs.sea.hqx, Installer.sea.hqx, and Booter.sea.hqx, respectively. Extract them as you would any other Macintosh application. _N_o_t_e_: The Booter is the only Mac OS application needed if the ssyyssiinnsstt method of installation is used. The Traditional method of instal- lation is deprecated and will be removed in a future release, and the Mkfs and Installer tools will be retired. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn No matter which installation method you use, there is some planning and preparation that is required beforehand. First and foremost, before be- ginning the installation process, make sure you have a reliable backup of any data on your hard disk that you wish to keep. _M_i_s_t_a_k_e_s _i_n _p_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _m_a_y _l_e_a_d _t_o _d_a_t_a _l_o_s_s_. NetBSD/mac68k uses the same disk mapping scheme as Mac OS: the Apple Disk Partition Map. This permits both systems to reside on the same disk, but introduces some installation problems unique to the Macintosh. There are very few, if any, reliable ways to reduce the size of an existing Mac OS disk partition, so partitioning a disk that currently contains Mac OS will almost always require a backup and reload step under Mac OS. If you are using the ssyyssiinnsstt method of installation you will be able to do most, if not all, of your disk partitioning during the install pro- cess. Partitioning the disk with ssyyssiinnsstt will destroy any partition that is resized, deleted, converted, or designated for use by NetBSD. All space not planned to be used for Mac OS HFS partitions may be used by NetBSD and can be sub-divided by the ssyyssiinnsstt process. This space may be defined within one or more existing disk partitions of any type, includ- ing HFS partitions that are no longer needed for Mac OS. However it is best if this space is physically contiguous on the disk as ssyyssiinnsstt is not capable of merging non-contiguous disk partitions. If you are using the ssyyssiinnsstt method and have sufficient disk space in one or more disk parti- tions you should skip forward to the section labeled _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m _(_S_y_s_i_n_s_t _M_e_t_h_o_d_) in this document. If you are using the Traditional method of installation you must use a disk partitioning utility to designate the different partitions you will want in your final NetBSD configuration. It is not necessary to create NetBSD (or AU/X) type partitions at this stage; the Mkfs utility can con- vert a partition of any type to one usable for NetBSD. If disk partitioning is required because you've selected the Traditional method of installation, or because disk space needs to be freed up for use for the ssyyssiinnsstt method of installation, follow the directions in the remainder of this section. Find your favorite disk partitioning utility. Any formatter capable of partitioning a SCSI disk should work. Some of the ones that have been tried and seem to work are: ++oo Apple HD SC Setup ++oo Hard Disk ToolKit from FWB ++oo SCSI Director Lite ++oo Disk Manager Mac from OnTrack ++oo Silverlining from LaCie ++oo APS Disk Tools Apple's HD SC Setup is probably the easiest to use and the most commonly available. Instructions for patching HD SC Setup so that it will recog- nize non-Apple drives is available at: hhttttpp::////wwwwww..eeuurroonneett..nnll//uusseerrss//eerrnnssttoouudd//ppaattcchh..hhttmmll First, you need to choose a drive on which to install NetBSD. Try to pick a drive with a low SCSI target number (or "SCSI ID"), especially if you are likely to add or remove drives to your SCSI chain in the future. _N_o_t_e_: Be certain you have a reliable backup of any data that you may want to keep. Repartitioning your hard drive is an excellent way to destroy important data. Second, decide how you want to set up your partitions. At minimum, you need a partition to hold the NetBSD installation (the root partition -- _/) and a partition to serve as swap space. You may choose to use more than one partition to hold the installation. This allows you to separate the more vital portions of the file system (such as the kernel and the _/_e_t_c directory) from the more volatile parts of the file system. Typical setups place the _/_u_s_r directory on a separate partition from the root partition (_/). Generally, _/ can be fairly small while the _/_u_s_r partition should be fairly large. If you plan to use this machine as a server, you may also want a separate _/_v_a_r partition. Once you have decided how to lay out your partitions, you need to calcu- late how much space to allocate to each partition. A minimal install of NetBSD (i.e. _b_a_s_e_._t_g_z, _e_t_c_._t_g_z_, and either _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z or _k_e_r_n_- _G_E_N_E_R_I_C_S_B_C_._t_g_z) should just fit in a 56 MB partition. For a full instal- lation, you should allocate at least 180 MB (150 MB if you do not wish to install the X sets). A general rule of thumb for sizing the swap parti- tion is to allocate twice as much swap space as you have real memory. Having your swap + real memory total at least 20 MB is also a good idea. Systems that will be heavily used or that are low on real memory should have more swap space allocated. Systems that will be only lightly used or have a very large amount of real memory can get away with less. Keep in mind that NetBSD currently requires Mac OS in order to boot, so it is likely that you will want to keep at least a minimal install of Mac OS around on an HFS partition for this purpose. The size of this parti- tion may vary depending on the size requirements for the version of Mac OS you are using. Of course, if you have Mac OS on another hard drive or can boot from a floppy, feel free to dedicate the entire drive to NetBSD. Next, use your favorite partitioning utility to make partitions of the necessary sizes. You can use any type of partition, but partitions of type Apple_Free might save you some confusion in the future. You are now set to install NetBSD on your hard drive. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm ((SSyyssiinnsstt MMeetthhoodd)) _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 for the sake of completeness. Do not let this discourage you; the install program is not hard to use. 2. _P_o_s_s_i_b_l_e _h_a_r_d_w_a_r_e_-_s_p_e_c_i_f_i_c _i_s_s_u_e_s ++oo _S_C_S_I _d_r_i_v_e_r _p_r_o_b_l_e_m_s The SCSI driver used in the kernel on many older Macintosh sys- tems is, by default, the ncrscsi driver. It contains a recog- nized but as yet unfixed bug that affects some disk drive/con- troller combinations, usually Quantum disks. Under heavy load these systems may hang or corrupt the file system; or, you may experience frequent _S_e_g_m_e_n_t_a_t_i_o_n _f_a_u_l_t and _I_l_l_e_g_a_l _i_n_s_t_r_u_c_t_i_o_n errors that may or may not be consistently repeatable. This latter condition is particularly prevalent on systems with mini- mal RAM installed. If either of these problems occur on your system you are advised to use the SBC variants of the Kernel and Installation Kernel. However, be aware that this issue does not affect e.g. Centris or Quadra systems. ++oo _T_h_e _6_8_L_C_0_4_0 _p_r_o_c_e_s_s_o_r NetBSD has known but unresolved problems running on the 68LC040 processor, the variant of the 68040 that does not contain the floating point unit (FPU). The kernel is thus forced to emulate the missing operations in software. Unfortunately the 68LC040 processor has a design problem that causes the emulation to fail intermittently. We hope to provide a solution for this issue in a future NetBSD release. Software emulation of floating point operations is not a problem on the 68020 and 68030 processors. 3. _G_e_n_e_r_a_l The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. ssyyssiinnsstt is a menu driv- en installation system that allows for some freedom in doing the in- stallation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the in- stallation process again from scratch by running the _/_s_y_s_i_n_s_t pro- gram from the command prompt. It is not necessary to reboot. 4. _Q_u_i_c_k _i_n_s_t_a_l_l First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to the next section. This section describes a basic in- stallation, using a CD-ROM install as an example. ++oo What you need. -- The distribution sets (in this example, they are on CD). -- The Mac OS Booter application and an Installation Kernel -- A Macintosh with a 68020 and MMU, 68030 or 68RC040 proces- sor. An FPU is not required but will be used if present (but see the note above regarding the 68LC040). -- A CD-ROM drive (SCSI), a harddisk and a minimum of 8 MB of memory installed. -- The harddisk should have at least 120 + _n megabytes of space free, where _n is the number of megabytes of main memory in your system. If you wish to install the X Window System as well, you will need at least 60 MB more. ++oo The NetBSD Boot Tools folder. -- Create a Folder on your Mac OS disk for the NetBSD/mac68k components. -- Copy the Booter application into the newly created Folder. Expand the file if necessary to create the Mac OS exe- cutable. -- Copy the Installation Kernels into the newly created Folder. It is not necessary to gguunnzziipp compressed kernel files. -- Single-click on the Booter application icon then select the "Get Info" from the File Menu list. Increase the memory al- location for the Booter to as much as possible for your sys- tem. Having a large number of fonts, extensions or sounds installed on your system can cause memory exhaustion prob- lems for the Booter if you don't do this. Also, the extra memory is needed by the Booter to expand compressed kernels while booting. ++oo The Quick Installation -- Double-click on the Booter application icon to start execut- ing it. From the OOppttiioonnss pull-down menu, select MMoonniittoorrss, then select CChhaannggee MMoonniittoorr DDeepptthh and make sure B&W is high- lighted. Close the window using the CClloossee button. -- From the OOppttiioonnss pull-down menu select BBoooott OOppttiioonnss. This will bring up an option panel. Set the AAuuttoo--sseett GGMMTT BBiiaass checkbox in the lower left and then select the BBoooott ffrroomm MMaacc OOSS option at the top of the window. The SSeett button on the right will become active. Use it to locate and select the Installation Kernel file appropiate for your hardware. This will be either _n_e_t_b_s_d_-_I_N_S_T_A_L_L_._g_z or _n_e_t_b_s_d_-_I_N_S_T_A_L_L_S_B_C_._g_z. Close the window using the CClloossee button. -- From the OOppttiioonnss pull-down menu select the BBoooott NNooww, or use the Apple-B (Command-B) key combination to start the NetBSD boot process. Do not move the mouse while the boot opera- tion is in progress as this may leave the keyboard locked to NetBSD. The main menu will be displayed. .***********************************************. * NetBSD-1.6 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * x: Exit Install System * .***********************************************. -- If you wish, you can configure some network settings immedi- ately by choosing the UUttiilliittyy mmeennuu and then CCoonnffiigguurree nneettwwoorrkk. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. -- Choose iinnssttaallll. -- You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. -- After your disk has been prepared, choose CCDD--RROOMM as the medium. The default values for the path and device should be ok. -- After all the files have been unpacked, go back to the main menu and select rreebboooott.. -- NetBSD will now boot. If you haven't already done so in ssyyssiinnsstt, you should log in as root, and set a password for that account. You are also advised to edit the file _/_e_t_c_/_r_c_._c_o_n_f to match your system needs. -- Your installation is now complete. -- For configuring the X window system, if installed, see the files in _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c. Further information can be found on hhttttpp::////wwwwww..xxffrreeee8866..oorrgg//. 5. _B_o_o_t_i_n_g _N_e_t_B_S_D Prior to attempting to boot NetBSD/mac68k verify that all the fol- lowing are done: ++oo Enable 32-bit addressing in the Memory Control Panel [1]. ++oo Disable all forms of virtual memory (the Memory Control Panel, RAM Doubler, or other software-based memory enhancement prod- ucts). ++oo Place the system in B&W Mode (1-bit color or grayscale) as shown in the Monitors Control Panel or in the Monitors options dialog of the Booter. You may choose to have the Booter do this for you automatically by selecting the appropiate check box and ra- dio button in the MMoonniittoorrss dialog on the OOppttiioonnss menu. It is probably best to boot your machine with all extensions turned off [1]. You can do this by booting into Mac OS with the SHIFT key held down. You may have to restart your Macintosh for changes to take effect before proceeding. [1] If your version of the Memory control panel does not have a 32-bit addressing mode radio button, this means that your sys- tem is already 32-bit clean and is running in 32-bit addressing mode by default. If the Booter complains that your are not in 32-bit mode, it may be necessary for you to press the "Use De- faults" button in the Memory control panel to restore 32-bit addressing. You should probably reboot after doing so. If you have an older II-class system (including the II, IIx, IIcx, and SE/30), it is necessary to install Connectix's MODE32 to work around ROM issues which prevent you from enabling 32-bit ad- dressing. Please see the NetBSD/mac68k FAQ at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaacc6688kk//ffaaqq// for more information. Double-click on the NetBSD/mac68k Booter icon to start the applica- tion. Select BBoooottiinngg from the OOppttiioonnss menu. Select the Kernel Lo- cation to be from Mac OS with the filename corresponding to the name of the Installation Kernel you are using. Typically this will be netbsd-INSTALL.gz. If you haven't already put your Macintosh into B&W mode, select the MMoonniittoorr OOppttiioonnss from the OOppttiioonnss menu and check the box for B&W mode. Try booting NetBSD by selecting BBoooott NNooww from the OOppttiioonnss menu. If the system does not come up, send mail to _p_o_r_t_-_m_a_c_6_8_k_@_n_e_t_b_s_d_._o_r_g describing your software, your hardware, and as complete a descrip- tion of the problem as you can. As an alternative, try using the Traditional method of installation described in the next section. 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 If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the UUttiilliittyy mmeennuu, and select the CCoonnffiigguurree nneettwwoorrkk option. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this. 7. _P_r_e_p_a_r_i_n_g _a _d_i_s_k _f_o_r Mac OS _a_n_d _N_e_t_B_S_D ssyyssiinnsstt can manipulate the Apple Disk Partition Map allowing you to partition your disk for use with NetBSD. It does not support resiz- ing existing Mac OS HFS disk partitions. If there is insufficient Free space on the disk to support an installation of NetBSD you will need to backup, repartition and restore your existing Mac OS parti- tions before proceeding. You may choose to use a Traditional method of creating disk partitions for NetBSD if you wish. They can still be used by ssyyssiinnsstt for a NetBSD installation. 8. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s To start the installation, select IInnssttaallll NNeettBBSSDD ttoo hhaarrdd ddiisskk from the main menu. To start the installation, select the menu option in 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. ssyyssiinnsstt next tries to figure out how the selected volume has been partitioned. It does this by reading the Apple Disk Partition Map from the disk. If the disk does not have a Partition Map, ssyyssiinnsstt will give you the option of writing one, but doing so will not make the disk a Mac OS bootable volume. You will have the option of cre- ating HFS partitions that may be subsequentially initialized and used under Mac OS though. 9. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k ++oo Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. ++oo Definition of the NetBSD disklabel. The Apple Disk Partition Map is used to create an in-core map of the disk called the disklabel. A minimum of two NetBSD parti- tions will be required, one for root and one for swap. Up to eight partitions may be used by NetBSD. Up to 32 partitions may exist on the disk which can be any combination of Mac OS HFS, Free, Scratch and NetBSD partitions, although only the first eight which meet the needs of NetBSD will be seen and mapped to the NetBSD disklabel. Some partitions in the disklabel have a fixed purpose. Parti- tion 'a' is always the root partition, 'b' is the swap partition and 'c' is the entire disk. Partitions 'd' through 'h' are available for other use. Traditionally, 'g' is the partition mounted on the /usr directory, but this is historical practice, not a fixed value. ++oo Editing the NetBSD Disklabel (and the underlying Apple Disk Par- tition Map). You will be presented with the current layout of the disk as seen by NetBSD, and given a change to change it. (Even though NetBSD can only use the first eight qualified partitions, all partitions found on the disk will be displayed.) The partitions found on the disk will be shown in the top section of the dis- play. Each will be identified with the name assigned by NetBSD, the current size, offset, type, use and mount point. The parti- tion currently being modified will be highlighted in inverse video. The bottom part of the display will list the operations which may be performed on the selected (highlighted) partition. The options are: -- Select next partition This highlights the next partition in the upper display list and makes it the current one selected for manipulation. -- Change selected partition This changes the type assigned to the partition. A parti- tion may be assigned for use as a NetBSD Root, SWAP, Usr, or Root&Usr; it may be assigned for use as a Mac OS HFS parti- tion; a Scratch (for later reassignment); or a Free parti- tion. Free partitions which are physically adjacent to each other will be collapsed into a single Free partition. -- Set mount point for partition This designates the NetBSD file system mount point for the partition, and gets transferred into the /etc/fstab defini- tion so NetBSD knows where to mount the file system on sub- sequent boots. The option only applies to NetBSD Root, Usr, Root&Usr or Mac OS HFS partitions, although currently HFS access is not supported without optional software compo- nents. A common set of predefined mount points (/usr, /home, /var, /tmp or None) will be presented to you to as- sist you in defining the most commonly used, but you may en- ter you own names if you choose. Selecting "None" will clear the mount point name and keep the partition from being defined in the resulting _/_e_t_c_/_f_s_t_a_b file. -- Split selected partition This option divides the selected partition into two separate partitions if there is space available in the Disk Partition Map. You will be prompted for the size of the first segment and the remaining portion will be allocated to the second segment. The first segment will be designated as a Scratch type, and the second will be designated as a Free type. To clear a split, or remerge two adjacent partitions into a single one, change both to be Free types. ssyyssiinnsstt will merge them and update the display. This is the primary option used to partition the disk since it allows you to sub-divide the selected partition into two partitions. Changing the types associated with the result- ing two parts, or splitting the second part further sub-di- vides the original partition. -- Page Up, Page Down These entries allow you to scroll the upper display if more than eight partitions currently exist on the disk. -- Fix selected partition This option reviews the partition's size and starting ad- dress and fixes the values if they overlap any adjacent par- tition. This is primarily a debugging option and shouldn't be necesary during a normal installation. However, some 3rd party disk formatters have been known to create bogus en- tries in the Apple Disk Partition Map, and this option can aid is repairing these entries. -- Exit This option completes the disk partitioning and returns you to the previous installation menu. At that point you will be given one last opportunity to bail out before committing the changes to the Disk Partition Map recorded on the disk. ++oo Recommended approach to partitioning The simplest method of approaching disk partitioning with ssyyssiinnsstt is to convert everything that can be used for NetBSD in- to a Free type partition. This will allow ssyyssiinnsstt to collapse and merge all the available space. Then cycle through the Se- lect, Split, Select, Change, and Set Mount Point options for each of the NetBSD partitions that are desired. Since NetBSD/mac68k has a very specific mount order for partitions during system boot, it is best to create your NetBSD partitions in the following order: Root, SWAP, Usr where the partitions will be mounted in order on 'a', 'b', 'g', 'd', 'e', 'f', and 'h'. At least one Root or Root&Usr is required, and a SWAP partition is highly desirable. As a general rule you will need twice as much swap space as you have RAM, more if you plan on running X, Web applications or doing heavy development in a multi-user en- vironment. The Root partition, if it is separate from your Usr, usually requires about 24 MB. If multiple Root partitions are defined, the second is usually mounted on /altusr by default. NetBSD/mac68k automatically mounts all Root partitions after the first as Usr type parti- tions. However, it is best to be very specific about mount points and partition type and use. You will then be asked to name your disk's disklabel. The default response is ``mmyyddiisskk''. For most purposes this will be OK. If you choose to name it something different, make sure the name is a sin- gle word and contains no special characters. You don't need to re- member this name. 10. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to pro- ceed, enter yes at the prompt. The install program will now label your disk and make the file sys- tems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installa- tion program after pressing the return key. 11. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD distribution consists of a number of _s_e_t_s, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installa- tion, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to section labeled `Extracting the distribution sets'. 12. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _f_t_p To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server. ssyyssiinnsstt will proceed to transfer all the default set files from the remote site to your hard disk. 13. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server. 14. _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. 15. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _M_a_c _O_S _f_i_l_e _s_y_s_t_e_m_s NetBSD/mac68k does not currently have in-kernel support for Mac OS HFS/HFS+ or AppleShare filesystems. ssyyssiinnsstt therefore can not ac- cess the file sets if they are on these filesystems. 16. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m In order to install from a local file system, you will need to spec- ify the device that the file system resides on (for example sd1e) the type of the file system, and the directory on the specified file system where the sets are located. ssyyssiinnsstt will then check if it can indeed access the sets at that location. 17. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file sys- tem that is already accessible. ssyyssiinnsstt will ask you for the name of this directory. 18. _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 se- lection menu. Before extraction begins, you can elect to watch the files being ex- tracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles. After all the files have been extracted, all the necessary device node files will be created. If you have already configured network- ing, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the net- work configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password en- cryption algorithm and can than set a password for the "root" ac- count, to prevent the machine coming up without access restrictions. 19. _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.6. You can now reboot the machine, and boot NetBSD from harddisk. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm ((TTrraaddiittiioonnaall MMeetthhoodd)) The Traditional method of installation can be broken down into three ba- sic steps: ++oo Run Mkfs to build a file system or file systems. ++oo Run the Installer to load the files onto your file systems. ++oo Run the Booter to boot the system. _P_r_e_p_a_r_i_n_g _t_h_e _f_i_l_e _s_y_s_t_e_m_(_s_) Double-click on the Mkfs application icon to start it up. It will ask you for the SCSI-ID (SCSI target number) of the drive that you are installing NetBSD on. Once this is selected, it will present a list of the parti- tions on that disk. You must first convert the partitions to a type which NetBSD can understand. Select each partition on which you wish to build a file system and click on the CChhaannggee button. If you are placing the entire installation on a single partition, select the NNeettBBSSDD RRoooott&&UUssrr radio but- ton. If you are using multiple partitions, select NNeettBBSSDD RRoooott for the root partition (_/) and NNeettBBSSDD UUssrr for all the other partitions. You should select NNeettBBSSDD SSwwaapp for the swap partition. When you have finished converting each partition, select each partition and click on the FFoorrmmaatt button. You will now be asked for a bunch of pa- rameters for the hard drive and the file system. Usually, you can just take the defaults. If you are installing onto removable media (e.g. a Zip, Jaz, or Syquest), please see the FAQ. Note that although this dialog only has the OOKK button, you are not committed, yet. Once you get the val- ues you want, press the OOKK button. A dialog will be presented at this point with two options: FFoorrmmaatt and CCaanncceell. If you choose CCaanncceell, nothing will be written to your drive. If you choose FFoorrmmaatt, the program will proceed to make a file system. Mkfs is not a well-behaved Macintosh application. It will not allow any other tasks to run while it does (cooperative multitasking at its best). When it's finished, the program will put up a dialog to ask if you have scanned the output for any error messages. Usually there won't have been any errors, but do scan the output to make sure. Simply click on the II RReeaadd IItt button and the program will quit. Repeat as necessary for any extra partitions that you wish to make file systems on. Note that you do _n_o_t need a file system on your swap parti- tion. When you are finished, click on the DDoonnee button and choose QQuuiitt from the FFiillee menu to exit Mkfs. _I_n_s_t_a_l_l_i_n_g _t_h_e _f_i_l_e_s Before using the Installer, it is probably a good idea to increase its memory allocation. Select the Installer icon by clicking on it and choose GGeett IInnffoo from the File menu. Increase both the Minimum and Preferred sizes to as much as you can spare. Double-click on the Installer icon to start it up. The Installer will present the same SCSI-ID menu that Mkfs did. Select the same SCSI-ID (SC- SI target number) that you did for Mkfs - i.e., the one you are in- stalling NetBSD on. If you are installing onto a single root partition (_/), proceed to the _I_n_s_t_a_l_l_a_t_i_o_n _o_f _b_a_s_e _f_i_l_e_s section, below. If you have not created file systems for _/ (root), _u_s_r, and any other file systems, go back to _P_r_e_p_a_r_i_n_g _t_h_e _f_i_l_e _s_y_s_t_e_m_(_s_) above. When you started the Installer, it mounted your root partition (_/). Just before it printed Mounting partition 'A' as / it printed lines like: sd1 at scsi ID 5 This means that the device for SCSI target 5 ("SCSI ID 5") is sd1. The partitions are signified by a trailing letter. For instance, sd1a would be the root partition (_/) of the second SCSI disk in the chain, and sd0g would be the first Usr partition on the first SCSI disk. You will need to know the proper device to mount the remaining parti- tion(s) by hand: 1. Select BBuuiilldd DDeevviicceess from the FFiillee menu. 2. Select MMiinnii SShheellll from the FFiillee menu. 3. You can use the ddiisskkllaabbeell command to get a listing of the available partitions and their types and sizes. 4. Create the directory mount point(s) with the command: # mmkkddiirr ppaatthh E.g. for the _/_u_s_r partition type: # mmkkddiirr //uussrr 5. Mount the file systems you wish with the command: # mmoouunntt ddeevviiccee ppaatthh For example, if you wish to mount a _/_u_s_r partition from the first SCSI disk sd0, on _/_u_s_r, you would type: # mmoouunntt //ddeevv//ssdd00gg //uussrr 6. Type # ffssttaabb ffoorrccee to create a proper _/_e_t_c_/_f_s_t_a_b file. 7. Type qquuiitt after you have mounted all the file systems. _I_n_s_t_a_l_l_a_t_i_o_n _o_f _b_a_s_e _f_i_l_e_s Select the IInnssttaallll menu item from the FFiillee menu and install _b_a_s_e_._t_g_z, _e_t_c_._t_g_z, _e_i_t_h_e_r _k_e_r_n_-_G_E_N_E_R_I_C_._t_g_z _o_r _k_e_r_n_-_G_E_N_E_R_I_C_S_B_C_._t_g_z, and any other sets you wish to install at this time (see the _N_e_t_B_S_D _1_._6 _R_e_l_e_a_s_e _C_o_n_t_e_n_t_s for information about what's in each set). The Installer will print out the filename of each file as it is in- stalled, and will take quite some time to install everything (the base package alone can take over two hours on a slow hard drive). As is the case with Mkfs, this is not a particularly well-behaved Macin- tosh application and the machine will be completely tied up while the in- stallation takes place. At some point after installing the base set, select the BBuuiilldd DDeevviicceess op- tion from the FFiillee menu if you have not already done so. This will create a bunch of device nodes for you and will create your initial _/_e_t_c_/_f_s_t_a_b. The Installer program also has an option to give you a mini-shell. Do not use this unless you are sure know what you are doing. When you are finished installing all of the sets you wish to install, ex- it the Installer by choosing QQuuiitt from the FFiillee menu. _B_o_o_t_i_n_g _t_h_e _s_y_s_t_e_m Prior to attempting to boot NetBSD/mac68k, please verify that all of the following are true: 1. 32-bit addressing is enabled [2] in the Memory control panel; 2. All forms of virtual memory are disabled (the Memory control panel, RAM Doubler, or other software-based memory enhancement products); and 3. Your system is in B&W mode (1-bit color or grayscale) as shown by the Monitors control panel. You may choose to have the Booter do this for you automatically by selecting the appropriate check box and radio button in the MMoonniittoorrss dialog on the OOppttiioonnss menu. It is probably best to boot your machine with all extensions turned off [2]. You can do this by booting into Mac OS with the SHIFT key held down. You may have to restart your Macintosh for changes to take effect before proceeding. [2] If your version of the Memory control panel does not have a 32-bit addressing mode radio button, this means that your system is already 32-bit clean and is running in 32-bit addressing mode by default. If the Booter complains that you are not in 32-bit mode, it may be necessary for you to press the UUssee DDeeffaauullttss button in the Memory control panel to restore 32-bit addressing. You should probably re- boot after doing so. If you have an older II-class system (includ- ing the II, IIx, IIcx, and SE/30), it is necessary to install Con- nectix's MODE32 to work around ROM issues which prevent you from en- abling 32-bit addressing. Please see the NetBSD/mac68k FAQ at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaacc6688kk//ffaaqq// for more information. Double-click on the NetBSD/mac68k Booter icon to start the application. Select BBoooottiinngg from the OOppttiioonnss menu. Check that all of the items in the resulting dialog look sane - especially the SCSI target number. If not, correct them to your preference (the SCSI target number, or "SCSI ID", should be the only thing you need to change). When you are satisfied with your choices, try booting NetBSD by selecting BBoooott NNooww from the OOppttiioonnss menu. If you wish to save your preferences, choose SSaavvee OOppttiioonnss from the FFiillee menu before Booting (your preferences will not be saved if you forget to do this). If the system does not come up, send mail to _p_o_r_t_-_m_a_c_6_8_k_@_n_e_t_b_s_d_._o_r_g de- scribing your software, your hardware, and as complete a description of the problem as you can. If the system does come up, congratulations, you have successfully in- stalled NetBSD 1.6. 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-only. 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 file system 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, where your on-board, NuBus or PDS interface may be ae0, mc0 or sn0. For example: ifconfig_sn0="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_sn0="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. -- More information on the package system is at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll -- A list of available packages suitable for browsing is at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//RREEAADDMMEE..hhttmmll -- Precompiled binaries can be found at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess, usually in the _1_._6_/_m_a_c_6_8_k_/_A_l_l subdir. You can install them with the following commands: ## PPKKGG__PPAATTHH==ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..66//mmaacc6688kk//AAllll ## eexxppoorrtt PPKKGG__PPAATTHH ## ppkkgg__aadddd --vv ttccsshh ## ppkkgg__aadddd --vv aappaacchhee ## ppkkgg__aadddd --vv ppeerrll ... The above commands will install the tcsh shell, the Apache web server and the perl programming language as well as all the packages they depend on. -- 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 -- 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. -- 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. -- Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use. -- Many of the _/_e_t_c files are documented in section 5 of the manu- al; so just invoking # mmaann 55 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm The upgrade to NetBSD 1.6 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components. To do the upgrade, you must boot from the installer kernel using one of the methods described above. You must also have at least the bbaassee and kkeerrnn binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously in- stalled or to account for growth of the sets between releases. If you have a few megabytes free on each of your root (_/) and _/_u_s_r partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your NetBSD parti- tion, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to _b_a_c_k _u_p any important data on your disk, whether on the NetBSD partition or on another operat- ing system's partition, before beginning the upgrade process. The upgrade procedure using the ssyyssiinnsstt tool is similar to an installa- tion, but without the hard disk partitioning. The original _/_e_t_c directo- ry is renamed to _/_e_t_c_._o_l_d, and no attempt is made to merge any of the previous configuration into the new system except that the previous _/_e_t_c_/_f_s_t_a_b file is copied into the new configuration. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some sanity checks are done, i.e. file systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.6 system. However, that doesn't mean that you're fin- ished with the upgrade process. You will probably want to update the set of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v by hand, you will need to be careful about this, but if not, you can just cd into _/_d_e_v, and run the command: # sshh MMAAKKEEDDEEVV aallll Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. NetBSD/mac68k has switched its executable format from the old a.out for- mat to ELF, the now more commonly used and supported format. Your old bi- naries will continue to work just fine. The installation procedure will try to take the necessary steps to accomplish this. The most important step is to move the old a.out shared libraries in _/_u_s_r_/_l_i_b and _/_u_s_r_/_X_1_1_R_6_/_l_i_b (if X was installed) to _/_e_m_u_l_/_a_o_u_t, where they will be au- tomatically found if an older a.out binary is executed. Sysinst will use an existing _/_e_m_u_l and / or _/_e_m_u_l_/_a_o_u_t directory if available, and will create it (as a symbolic link to _/_u_s_r_/_a_o_u_t) if necessary. If you already had a _/_e_m_u_l directory, or a symbolic link by that name, sysinst should rename it and tell you about it. CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.6. _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_._5 The following issues can generally be resolved by extracting the eettcc set into a temporary directory and running _p_o_s_t_i_n_s_t_a_l_l: mkdir /tmp/upgrade cd /tmp/upgrade pax -zrpe -f /path/to/etc.tgz ./etc/postinstall -s `pwd` check ./etc/postinstall -s `pwd` fix Issues fixed by _p_o_s_t_i_n_s_t_a_l_l: -- Various files in _/_e_t_c need upgrading. These include: ++oo _/_e_t_c_/_d_e_f_a_u_l_t_s_/_* ++oo _/_e_t_c_/_m_t_r_e_e_/_* ++oo _/_e_t_c_/_d_a_i_l_y ++oo _/_e_t_c_/_w_e_e_k_l_y ++oo _/_e_t_c_/_m_o_n_t_h_l_y ++oo _/_e_t_c_/_s_e_c_u_r_i_t_y ++oo _/_e_t_c_/_r_c_._s_u_b_r ++oo _/_e_t_c_/_r_c ++oo _/_e_t_c_/_r_c_._s_h_u_t_d_o_w_n ++oo _/_e_t_c_/_r_c_._d_/_* -- The following files are now obsolete: _/_e_t_c_/_r_c_._d_/_N_E_T_W_O_R_K and _/_e_t_c_/_r_c_._d_/_g_a_t_e_d. -- The following rc.conf(5) entries are now obsolete: amd_master, ip6forwarding, defcorename, and nfsiod_flags. critical_filesystems_beforenet has been replaced by critical_filesystems_local. critical_filesystems has been re- placed by critical_filesystems_remote. -- The users and groups `named', `ntpd', and `sshd' need to be created. -- The configuration files for ssh(1) and sshd(8) were moved from _/_e_t_c to _/_e_t_c_/_s_s_h, including _s_s_h___k_n_o_w_n___h_o_s_t_s_* files and the host key files _s_s_h___h_o_s_t_*___k_e_y_*. _/_e_t_c_/_s_s_h_._c_o_n_f was renamed to _/_e_t_c_/_s_s_h_/_s_s_h___c_o_n_f_i_g, and _/_e_t_c_/_s_s_h_d_._c_o_n_f was renamed to _/_e_t_c_/_s_s_h_/_s_s_h_d___c_o_n_f_i_g. -- The mmuuxx entries in wscons.conf(5) are now obsolete. The following issues need to be resolved manually: -- postfix(8) configuration files require upgrading. cd /usr/share/examples/postfix cp post-install postfix-files postfix-script /etc/postfix postfix check -- The _d_e ethernet driver was replaced with the _t_l_p driver. This may require the renaming of the files _/_e_t_c_/_i_f_c_o_n_f_i_g_._d_e_* to _/_e_t_c_/_i_f_c_o_n_f_i_g_._t_l_p_*, renaming of rc.conf(5) entries ifconfig_de* to ifconfig_tlp*, and the reconfiguration of files such as _/_e_t_c_/_d_h_c_l_i_e_n_t_._c_o_n_f and _/_e_t_c_/_i_p_f_._c_o_n_f. _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 -- _/_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. -- 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"; }; -- sysctl(8) was 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. -- 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 -- intro(1), -- man(1), -- apropros(1), -- passwd(1), and -- 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 include 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 -- 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. -- 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. -- 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. -- Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers. -- Redback Networks, Inc. for hosting the NetBSD mail and GNATS server. -- The Helsinki University of Technology in Finland for hosting the NetBSD CVS server. -- The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. -- The many organisations that provide NetBSD mirror sites. -- 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. -- 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. -- 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 Luke Mewburn Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Rob Windsor Jim Wise Reinoud Zandijk Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) -- 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_: 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_)_: Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ssbbmmiippss 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 Chris Gilbert _c_h_r_i_s_@_n_e_t_b_s_d_._o_r_g ccaattss 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 aaccoorrnn2266 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 Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g ii338866 Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g vvaaxx Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g ppcc553322 NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g xx6688kk 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 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 Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmeeppppcc Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g aaccoorrnn3322 _T_h_e _N_e_t_B_S_D _1_._6 _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_: Erik Berls _c_y_b_e_r_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_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 Luke Mewburn _l_u_k_e_m_@_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 _N_e_t_B_S_D _D_e_v_e_l_o_p_e_r_s_: Nathan Ahlstrom _n_r_a_@_n_e_t_b_s_d_._o_r_g Steve Allen _w_o_r_m_e_y_@_n_e_t_b_s_d_._o_r_g Julian Assange _p_r_o_f_f_@_n_e_t_b_s_d_._o_r_g Lennart Augustsson _a_u_g_u_s_t_s_s_@_n_e_t_b_s_d_._o_r_g Christoph Badura _b_a_d_@_n_e_t_b_s_d_._o_r_g Bang Jun-Young _j_u_n_y_o_u_n_g_@_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 Hiroyuki Bessho _b_s_h_@_n_e_t_b_s_d_._o_r_g John Birrell _j_b_@_n_e_t_b_s_d_._o_r_g Mason Loring Bliss _m_a_s_o_n_@_n_e_t_b_s_d_._o_r_g Rafal Boni _r_a_f_a_l_@_n_e_t_b_s_d_._o_r_g Manuel Bouyer _b_o_u_y_e_r_@_n_e_t_b_s_d_._o_r_g John Brezak _b_r_e_z_a_k_@_n_e_t_b_s_d_._o_r_g Allen Briggs _b_r_i_g_g_s_@_n_e_t_b_s_d_._o_r_g Mark Brinicombe _m_a_r_k_@_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 Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g 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 Jeremy Cooper _j_e_r_e_m_y_@_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 Alistair Crooks _a_g_c_@_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 Tracy Di Marco White _g_e_n_d_a_l_i_a_@_n_e_t_b_s_d_._o_r_g Jarom'ir Dolecek _j_d_o_l_e_c_e_k_@_n_e_t_b_s_d_._o_r_g Andy Doran _a_d_@_n_e_t_b_s_d_._o_r_g Roland Dowdeswell _e_l_r_i_c_@_n_e_t_b_s_d_._o_r_g Emmanuel Dreyfus _m_a_n_u_@_n_e_t_b_s_d_._o_r_g Matthias Drochner _d_r_o_c_h_n_e_r_@_n_e_t_b_s_d_._o_r_g Jun Ebihara _j_u_n_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Stoned Elipot _s_e_b_@_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 Gavan Fantom _g_a_v_a_n_@_n_e_t_b_s_d_._o_r_g Hubert Feyrer _h_u_b_e_r_t_f_@_n_e_t_b_s_d_._o_r_g Jason R. Fink _j_r_f_@_n_e_t_b_s_d_._o_r_g Matt Fredette _f_r_e_d_e_t_t_e_@_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 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 Chris Gilbert _c_h_r_i_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 Matthew Green _m_r_g_@_n_e_t_b_s_d_._o_r_g Andreas Gustafsson _g_s_o_n_@_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 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 Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g Ross Harvey _r_o_s_s_@_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 Eduardo Horvath _e_e_h_@_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 Shell Hung _s_h_e_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 Tetsuya Isaki _i_s_a_k_i_@_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 Darrin Jewell _d_b_j_@_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 S/oren J/orvang _s_o_r_e_n_@_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 Mattias Karlsson _k_e_i_h_a_n_@_n_e_t_b_s_d_._o_r_g KAWAMOTO Yosihisa _k_a_w_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g Mario Kemper _m_a_g_i_c_k_@_n_e_t_b_s_d_._o_r_g 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 Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g Martti Kuparinen _m_a_r_t_t_i_@_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 Frank van der Linden _f_v_d_l_@_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 Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g MAEKAWA Masahide _g_e_h_e_n_n_a_@_n_e_t_b_s_d_._o_r_g David Maxwell _d_a_v_i_d_@_n_e_t_b_s_d_._o_r_g Dan McMahill _d_m_c_m_a_h_i_l_l_@_n_e_t_b_s_d_._o_r_g Gregory McGarry _g_m_c_g_a_r_r_y_@_n_e_t_b_s_d_._o_r_g Jared D. McNeill _j_m_c_n_e_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 Minoura Makoto _m_i_n_o_u_r_a_@_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 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 Phil Nelson _p_h_i_l_@_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 Tohru Nishimura _n_i_s_i_m_u_r_a_@_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 Chris Pinnock _c_j_e_p_@_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 Darren Reed _d_a_r_r_e_n_r_@_n_e_t_b_s_d_._o_r_g Scott Reynolds _s_c_o_t_t_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 David Sainty _d_s_a_i_n_t_y_@_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 Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_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 Jan Schaumann _j_s_c_h_a_u_m_a_@_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 Amitai Schlair _s_c_h_m_o_n_z_@_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 Takeshi Shibagaki _s_h_i_b_a_@_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 Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g SOMEYA Yoshihiko _s_o_m_e_y_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 Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g Bill Squier _g_r_o_o_@_n_e_t_b_s_d_._o_r_g Jonathan Stone _j_o_n_a_t_h_a_n_@_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 Shin Takemura _t_a_k_e_m_u_r_a_@_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 Jason Thorpe _t_h_o_r_p_e_j_@_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 Tsubai Masanari _t_s_u_b_a_i_@_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 Masao Uebayashi _u_e_b_a_y_a_s_i_@_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 Leo Weppelman _l_e_o_@_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 Nathan Williams _n_a_t_h_a_n_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 Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g Colin Wood _e_n_d_e_r_@_n_e_t_b_s_d_._o_r_g YAMAMOTO Takashi _y_a_m_t_@_n_e_t_b_s_d_._o_r_g Yuji Yamano _y_y_a_m_a_n_o_@_n_e_t_b_s_d_._o_r_g Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g Maria Zevenhoven _m_a_r_i_a_7_@_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 _O_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_: 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 Brian R. Gaeke _b_r_g_@_d_g_a_t_e_._o_r_g Brad Grantham _g_r_a_n_t_h_a_m_@_t_e_n_o_n_._c_o_m Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t LLeeggaall MMuummbboo--JJuummbboo All product names mentioned herein are trademarks or registered trade- marks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by The NetBSD Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Han- num. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Alistair G. Crooks. This product includes software developed by Amancio Hasty and Roger Hardiman. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch. This product includes software developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe for the NetB- SD Project. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael L. Hitch. This product includes software developed by Niels Provos. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by Tohru Nishimura for the NetB- SD Project. This product includes software developed by TooLs GmbH. This product includes software designed by William Allen Simpson. This product includes software developed by Winning Strategies, Inc. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the Computer Systems Labora- tory at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@min- com.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by Reinoud Zandijk. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by the Alice Group. This product includes software developed by Allen Briggs. This product includes software developed by Bradley A. Grantham. This product includes softwarre developed by Daishi Kato. This product includes software developed by Takashi Hamada. This product includes software developed by Scott Reynolds. This product includes software developed by John P. Wittkoski. This product includes software developed by Colin Wood. TThhee EEnndd CCoonnttrriibbuuttiioonnss The following people have made contributions of various sorts specifical- ly for the Macintosh port (in alphabetical order): ++oo All of the users who have supplied us with good bug reports and moral support. ++oo The Alice Group (Allen K. Briggs, Chris P. Caputo, Michael L. Finch, Bradley A. Grantham, and Lawrence A. Kesteloot), without whom there would be no NetBSD port for the Macintosh. ++oo Steven R. Allen for keeping our snapshot distributions up-to-date. ++oo Stephen C. Brown for maintaining the Installer application. ++oo Denton Gentry and Yanagisawa Takeshi for their work on the SONIC Eth- ernet driver. ++oo Paul Goyette, Taras Ivanenko, Ken Nakata, and Michael R. Zucca for invaluable work towards supporting color X. ++oo Takashi Hamada and John Wittkoski beating the direct ADB hardware driver into submission. ++oo David Huang for getting MACE Ethernet and basic DMA working on the AV Macs. ++oo Scott Jann for acquiring a IIx and a IIci, used for building and testing release sets. ++oo Scott Kaplan for lending his IIci and Kensington Turbo Mouse for IIci/IIsi banked memory and internal video as well as non-Apple ADB devices. ++oo Noah M. Kieserman for lending a PowerBook 520C for tracking down sev- eral bugs on that platform. ++oo Markus Krummenacker for monetary donations. ++oo Glan Lalonde for an invaluable IIci page table dump. ++oo Dan McMahill for lending a PowerBook 165 to tweak ADB support on the PowerBook 160 and 180 family laptops. ++oo Bob Nestor for (unofficially) maintaining the Mkfs utility, and pro- viding a lot of useful information about the ROM vectors used by dif- ferent systems. ++oo Brad Parker for serial and Ethernet drivers/improvements. ++oo Brian R. Gaeke and Nigel Pearson for tweaking, polishing, and per- forming the occasional major refit on the Booter application. ++oo Scott Redman for lending Brad Grantham a PowerBook 160. ++oo Craig Ruff for assembling an '030 pmove ttx instruction. ++oo Brad Salai for lending an Ethernet card to help resolve interrupt conflicts. ++oo Larry Samuels for monetary donations. ++oo Peter Siebold for lending his IIvx in support of ADB and IIvx inter- nal video. ++oo Glen Stewart for lending a Carrera040 accelerator which, while still unsupported, helped to track down memory management bugs for '030-based machines. ++oo Bill Studenmund for providing a stable front end to the machine- in- dependent serial driver. ++oo Schuyler Stultz for the loan of his Macintosh II when we desperately needed another machine on which to compile and test during the '93 Xmas vacation. ++oo Tenon Intersystems for monetary donations, MachTen, and Brad's access to several machines and documentation after hours. ++oo Virginia Tech English Department for loan of a IIci w/ NuBus video and 32 MB of RAM -- the first IIci to run NetBSD/mac68k. ++oo Rob Windsor for donating a variety of Macintosh II-family systems, a Centris 650, a Quadra 700, and several boxes full of miscellaneous peripherals and parts in the interest of ensuring adequate testing and working out minor (and not-so-minor) problems. ++oo Colin Wood for maintaining a host of NetBSD/mac68k documentation, in- cluding the FAQ, Meta-FAQ, and OS Info documents. NetBSD September 7, 2002 43