INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/sparc. CCOONNTTEENNTTSS About this Document............................................1 Quick install notes for the impatient..........................2 What is NetBSD?................................................2 Upgrade path to NetBSD 1.5.3...................................3 Major Changes Between 1.5.2 and 1.5.3..........................3 Known Caveats with 1.5.3.......................................4 Major Changes Between 1.5.1 and 1.5.2..........................5 Major Changes Between 1.5 and 1.5.1............................5 Changes Between The NetBSD 1.4 and 1.5 Releases................7 Kernel......................................................7 Networking..................................................8 File system.................................................8 Security....................................................8 System administration and user tools........................9 Miscellaneous...............................................9 The Future of NetBSD..........................................10 Sources of NetBSD.............................................10 NetBSD 1.5.3 Release Contents.................................10 NetBSD/sparc subdirectory structure........................12 Binary distribution sets...................................12 NetBSD/sparc System Requirements and Supported Devices........14 Supported machines.........................................14 Machines not supported by NetBSD/sparc.....................15 Supported devices..........................................15 Unsupported devices........................................17 Getting the NetBSD System on to Useful Media..................17 Preparing your System for NetBSD installation.................19 Configuring your PROM......................................19 Determining how to access your SCSI disk from the..........21 Deciding on partition sizes................................22 Configuration of network interfaces........................22 Installing the NetBSD System..................................22 Installing NetBSD by placing a bootable filesystem on a....22 Installing NetBSD by using a bootable CD-ROM...............23 Installing NetBSD by using the bootable floppies...........23 Installing NetBSD by using a netboot setup.................24 Configuring your netboot server............................25 Installing NetBSD by using a bootable tape.................26 Running the installation scripts...........................27 Post installation steps.......................................28 Upgrading a previously-installed NetBSD System................30 Compatibility Issues With Previous NetBSD Releases............31 General issues.............................................31 Issues affecting an upgrade from NetBSD 1.4 or prior.......31 Using online NetBSD documentation.............................32 Administrivia.................................................32 Thanks go to..................................................33 We are........................................................35 Legal Mumbo-Jumbo.............................................39 The End.......................................................41 DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.5.3 on the _s_p_a_r_c platform. It is available in four different formats titled _I_N_S_T_A_L_L_._e_x_t, where _._e_x_t is one of _._p_s, _._h_t_m_l, _._m_o_r_e, or _._t_x_t: _._p_s PostScript. _._h_t_m_l Standard Internet HTML. _._m_o_r_e The enhanced text format used on UNIX-like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line _m_a_n pages are generally pre- sented. _._t_x_t Plain old ASCII. You are reading the _m_o_r_e version. QQuuiicckk iinnssttaallll nnootteess ffoorr tthhee iimmppaattiieenntt This section contains some brief notes describing what you need to in- stall NetBSD 1.5.3 on a machine of the sparc architecture. ++oo Fetch the CD image, _s_p_a_r_c___b_o_o_t_a_b_l_e_._i_s_o or the floppy disk images, _i_n_s_t_a_l_l_/_f_l_o_p_p_y_/_d_i_s_k_1_._g_z and _i_n_s_t_a_l_l_/_f_l_o_p_p_y_/_d_i_s_k_2. You need either the pair of floppies or the CD to boot your system. Alternatively, you may netboot the installation kernel, which requires several local netboot services. The details are not covered here, as setting up a netboot server is hardly ``quick''. ++oo The actual binary distribution is in the _b_i_n_a_r_y_/_s_e_t_s_/ directory. When you boot the install floppies or CD-ROM, the installation pro- gram can fetch these files for you (using e.g. ftp), if you have a network connection. There are several other methods to get the bina- ry sets onto your machine. You will at a minimum need the following sets: _k_e_r_n_._t_g_z, _b_a_s_e_._t_g_z and _e_t_c_._t_g_z. In a typical workstation installation you will probably want all the installation sets. ++oo Make sure your sparc's CD-ROM drive is bootable. Burn the CD. Oth- erwise, write the floppy images directly to a pair of floppies (after uncompressing disk1.gz). The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD. ++oo You will need to get to the OpenBoot PROM ``ookk'' prompt. After your system first powers on, and displays some initial information, press the STOP-A keys. At the ``ookk'' prompt, type the command to boot your system into NetBSD. The command to boot from CD is one of the fol- lowing commands (depending on your model): ``bb ssdd((,,3300,,))'', ``bboooott ssdd((,,3300,,))'', or ``bboooott ccddrroomm''. The command to boot from floppy is either ``bboooott ffdd((,,,,11))'' or ``bboooott ffllooppppyy''. The installer will prompt you to insert the second floppy when it is ready for it. ++oo For third-party programs which are not part of the base NetBSD dis- tribution, you will want to explore the ppkkggssrrcc system with its more than 2100 program packages. WWhhaatt iiss NNeettBBSSDD?? The NetBSD Operating System is a fully functional Open Source UNIX-like operating system derived from the University of California, Berkeley Net- working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on thirty-one different system architectures featuring twelve dis- tinct families of CPUs, and is being ported to more. The NetBSD 1.5.3 re- lease contains complete binary releases for fifteen different machine types. (The sixteen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//.) NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist. UUppggrraaddee ppaatthh ttoo NNeettBBSSDD 11..55..33 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.5.3. NetBSD 1.5.3 is an upgrade of NetBSD 1.5, 1.5.1, 1.5.2, and earlier major and maintenance releases of NetBSD. The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from _a_f_t_e_r the point where the release cycle for 1.5 was started are designated by ver- sion identifiers such as 1.5A, 1.5B, etc. These identifiers do not des- ignate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.5.3 can _n_o_t be used to upgrade a sys- tem running one of those intermediate development versions. Trying to use the NetBSD 1.5.3 kernel on such a system _w_i_l_l probably result in problems. Please also note that it is not possible to do a direct ``version'' com- parison between any of the intermediate development versions mentioned above and 1.5.3 to determine if a given feature is present or absent in 1.5.3. The development of 1.5 and the subsequent maintenance releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.5 was started, and during the release cycle of 1.5 and its maintenance releases, selected fixes and enhancements have been imported from the main development trunk. So, there are features in 1.5.3 which were not in, e.g. 1.5B, and vice versa. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55..22 aanndd 11..55..33 Some highlights are: ++oo lpd(8) has been fixed to deal with a security issue (SA2001-018). ++oo Drivers for Mylex DAC960, Compaq EISA array controllers, and I2O block/SCSI devices added. This has caused ca(4) to be replaced by ld(4). Drivers for the Mylex DAC960 management interface and DPT/Adaptec I2O RAID management interface has also been added. See dpti(4) and mlxctl(8). ++oo A driver for the 3ware Escalade 5000 and 6000 series RAID controllers has been added, see twe(4). ++oo Various different fixes have been applied to the network device drivers ep(4), ex(4), rtk(4), sip(4), ti(4), tl(4), and wi(4). ++oo Support for some more variants of rtk(4) on CardBus has been added. ++oo The ne(4) driver has been extended to support some more pcmcia cards. ++oo Support for more pciide(4) controllers added: HPT-370A, Acard ATP-850/860, and AMD-768. Ultra-DMA 100 support added for CMD 0649. ++oo A problem with the NFS server code, exposed on NetBSD/alpha, where use of ``..'' would return info for ``.'' has been fixed. ++oo Support for ``other-endian'' file systems has been improved. ++oo The layout algorithm for FFS file systems has been substantially im- proved, resulting in better performance, both due to improved locali- ty between files and their corresponding directory, and lessened pressure on the buffer cache. ++oo The performance of soft dependencies in FFS has been significantly improved in some circumstances. ++oo Handling of init/fini section support and DWARF2 exception handling has been added to the C runtime startup code. ++oo OpenSSH has been upgraded to version 3.0.2. ++oo A security issue arising from a race between set-uid execution and use of ptrace has been fixed (SA2002-001). ++oo The package tools has been extended to provide for optional digital signatures on binary packages. Additionally, binary package version number handling has been rewritten. ++oo A driver for Creative Labs SBLive! EMU10000 has been added; see emuxki(4). ++oo A driver for ESS Allegro-1 / Maestro-3 has been added; see esa(4). ++oo Support for the 53c1010-33 and 53c1510D has been added to the siop(4) driver. ++oo IPFilter upgraded to 3.4.23. ++oo The boot code on NetBSD/macppc has been improved. ++oo sendmail(8) has been upgraded to version 8.11.6. ++oo A long file name buffer overrun in gzip has been fixed (SA2002-002). ++oo IPSEC policy check has been fixed for forwarded IPv4 packets (SA2002-003). ++oo Two security problems in OpenSSH has been fixed (SA2002-004, SA2002-005). ++oo A buffer overrun in the resolver part of the C library has been fixed (SA2002-006). To fix this problem in the BIND user utilities, BIND has been upgraded to version 8.3.3. ++oo Various other kernel stability and robustness fixes has been applied. In addition, many bugs have been fixed--more than 70 problems reported through our problem tracking system have been fixed, and several other non-reported problems have also been found and fixed. See the CHANGES-1.5.3 file for the complete list. KKnnoowwnn CCaavveeaattss wwiitthh 11..55..33 The following are the major known issues with NetBSD 1.5.3. ++oo The upgrade of IPFilter to version 3.4.23 is not backward compatible. This means that the user-land tools used to manage IPFilter will have to be upgraded when the kernel is upgraded. ++oo Due to xsrc changes which are not backward compatible on the arm32 port, the X bits for arm32 is built from the 1.5.2 sources. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55..11 aanndd 11..55..22 The main purpose of NetBSD 1.5.2 is to fix some problems discovered shortly after the release of NetBSD 1.5.1. Some highlights are: ++oo telnetd(8) has been fixed to deal with a security issue (SA2001-012). ++oo A weakness in the OpenSSL libcrypto's pseudo random number generator has been fixed (SA2001-013). ++oo Floating point emulation on i386 (to run on FPU-less CPUs) which was broken late in 1.5.1's cycle has been restored to working order. ++oo Bugs in the compiler have been worked around to produce a working miniroot image on sparc64. ++oo The script-based installers on amiga, atari and mvme68k have been up- dated to deal with new behaviour from mount(8). ++oo dump(8) has been fixed to deal with a local security issue (SA2001-014). ++oo Several system calls have had defensive length checks applied on their arguments (SA2001-015). ++oo The DHCP software has been upgraded to ISC Version 3, Release Candi- date 10. Additionally, a few more bugs have been fixed. See the CHANGES-1.5.2 file for the complete list of changes. MMaajjoorr CChhaannggeess BBeettwweeeenn 11..55 aanndd 11..55..11 The complete list of changes between NetBSD 1.5 and 1.5.1 can be found in the file CHANGES-1.5.1 in the top directory of the source tree. The fol- lowing are highlights only: ++oo A driver for the Aironet/Cisco wireless PCMCIA cards has been added; see an(4). ++oo NFS client performance has been improved, typically by 40% for writes but possibly up to 100% in certain setups. ++oo The siop(4) driver has improved in performance and robustness. ++oo Support for cloning pseudo-interfaces has been added. See ifconfig(8). ++oo Support for 802.1Q virtual LANs has been added. See vlan(4). ++oo The isp(4) driver has been upgraded to (among other things) work on MacPPC. ++oo BIND has been upgraded to version 8.2.3 (SA2001-001). ++oo Support for booting from RAIDframe RAID1 mirrors on i386 added. ++oo The lfs(4) file system has again been substantially updated, but is still experimental. ++oo Ultra/66 support has been added for capable VIA chipsets, and Ul- tra/100 support has been added for the HPT370, Promise and Intel ICH2 controllers in the pciide(4) driver. Support for Intel 82801BAM con- trollers has also been added, and handling of Ali controllers has been improved. ++oo OpenSSH has been updated to deal with a security issue (SA2001-003). ++oo Sendmail has been upgraded to version 8.11.3. ++oo The ex(4) driver has added support for 3Com 3c555, 3c556 and 3c556B MiniPCI Ethernet cards. ++oo A driver for the on-board audio hardware found on many Apple PowerMa- cs has been added; see awacs(4). ++oo The sip(4) driver has been fixed to properly support the dp83815, as found in current Netgear FA311 10/100 cards. ++oo ftpd(8) has been updated to deal with two security issues (SA2000-018 and SA2001-005). ++oo ntpd(8) has been updated to deal with a security issue (SA2001-004). ++oo telnetd(8) has been updated to deal with a security issue (SA2000-017). ++oo A vulnerability on i386 related to USER_LDT has been fixed (SA2001-002). ++oo The Linux emulation has been enhanced to prepare for the support of using the Linux version of VMware. ++oo IP checksumming speed has been improved on i386 compared to NetBSD 1.5 by about 10%. ++oo Support for the Socket Communications LP-E Type II PCMCIA NE2000 clone card has been added to ne(4). ++oo The DHCP software has been upgraded to ISC version 3, Beta 2, patch- level 24, to fix core dumps in dhclient(8), among other things. Please note that the new dhcpd(8) forces you to configure a "ddns-up- date-style" of either "ad-hoc", "interim" or "none". ++oo Various fixes and enhancements to INET6 and IPSEC code; among them improved interaction between IPF/Nat and IPSEC. ++oo The Heimdal kerberos(8) implementation has been upgraded to version 0.3e. ++oo Support for Accton EN2242 and other AmdTek AN985 cards added to the tlp(4) driver. ++oo Several country-specific keyboard mappings have been added for USB keyboards. ++oo A driver for Yamaha YMF724/740/744/745-based sound cards has been added, see yds(4). ++oo The maximum number of BSD disklabel partitions on the i386 port has been increased from 8 to 16. ++oo Drivers for the AC'97 based audio sound chips ESS Technology Maestro 1, 2, and 2E (see esm(4)), NeoMagic 256 (see neo(4)), and Cirrus Log- ic CrystalClear PCI Audio CS4281 (see clct(4)) have been added. In addition, many bugs have been fixed--more than 95 problems reported through our problem tracking system have been fixed, and some other non- reported problems have also been found and fixed. See the CHANGES-1.5.1 file for the complete list. The NetBSD Packages Collection (pkgsrc) which is used to maintain, build, track dependencies, and maintain NetBSD-specific fixes to third-party programs, has received a major overhaul for NetBSD 1.5.1. Some high- lights are: ++oo Many new packages were added to the collection, which now includes about 2100 packages. Many of them are also available as pre-compiled binaries on ftp.netbsd.org and its mirrors. Many packages have been modified and enhanced to compile and function properly on big-endian (m68k, sparc), and LP64 architectures (alpha, sparc64). ++oo KDE2 and KOffice together consitutes a fully integrated office envi- ronment with no license problems, available for i386, alpha and many other architectures. ++oo Mozilla 0.9, KDE2's Konqueror, and Links 0.95 are just a few examples of the web browsers available. ++oo A support package for running VMware on NetBSD/i386 was added, it's called suse_vmware. The official VMware code, a valid license, and Wasabi Systems' compatibility package are all needed to run VMware. ++oo Internal changes of the pkgsrc system include strong checksums to prevent malicious distribution files, as well as restructuring of the package structure in pkgsrc for faster extraction of pkgsrc tar files and upgrades via SUP and CVS. Please note that at the moment, ssyyssiinnsstt will not assist you in installing pre-built third-party binary packages or the pkgsrc system itself, so you will have to manually install packages using ppkkgg__iinnssttaallll or fetch and ex- tract the pkgsrc.tgz tar file to get started. Lastly, it should be noted that the X11 binaries shipped in NetBSD 1.5.3 is still based on XFree86 version 3.3.6. Several newer graphics cards are inadequately supported by that code base, but on the other hand sup- port for several older graphics cards is not available in newer XFree86 code. NetBSD is in the process of moving to XFree86 version 4, and is currently maintaining both the XFree86 3.3.6 and the XFree86 version 4 code in the xxssrrcc source set, and you may at compile time pick which sources to build and install. To ease installation, testing and use of the XFree86 version 4 code, a binary snapshot based on XFree86 version 4.0.3 will be made available for at least the i386 architecture shortly after the release of NetBSD 1.5.3. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 11..44 aanndd 11..55 RReelleeaasseess The NetBSD 1.5 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many userland enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over one year of development that went into the NetBSD 1.5.3 release. Some highlights include: _K_e_r_n_e_l ++oo Ports to new platforms including: arc, cobalt, hpcmips, news68k, sgimips, and sparc64. ++oo Improved performance and stability of the UVM virtual memory subsys- tem. ++oo Implementation of generic kernel locking code, as well as a restruc- ture and re-tuning of the scheduler, to be used by the future symmet- ric multi-processing (SMP) implementation. ++oo Improved compatibility support for Linux, OSF1, and SVR4 programs. ++oo New compatibility support for Win32 programs. ++oo Support for dynamically loaded ELF kernel modules. ++oo Kernel process tracing using ktruss(1). ++oo Deletion of swap devices using swapctl(8). ++oo Easier hot-pluggability of keyboards and mice using a new wscons de- vice--wsmux. ++oo Improved PCMCIA and CardBus support, including support for detaching of devices and cards, resulting in better support for notebooks and PDA devices. ++oo Numerous hardware improvements, including areas such as: audio, UD- MA/66 support for ATA drives, USB, and wireless networking. _N_e_t_w_o_r_k_i_n_g ++oo Addition of IP version 6 (IPv6) and IPsec to the networking stack, from the KAME project. This includes addition of kernel code for IPv6/IPsec, IPv4/v6 dual-stack user applications and supporting li- braries. Due to this, the shlib major version for pcap(3) is incre- mented and you may need to recompile userland tools. The KAME IPv6 part includes results from the unified-IPv6 effort. _F_i_l_e _s_y_s_t_e_m ++oo Significant Fast file system (FFS) performance enhancements via inte- gration of Kirk McKusick's soft updates and trickle sync code. ++oo Support for the Windows NT `NTFS' file system (read-only at this stage). ++oo Support for revision 1 of the Linux `ext2fs' file system. ++oo Enhanced stability and usability of LFS (the BSD log-structured file system). ++oo Various RAIDframe enhancements including: auto-detection of RAID com- ponents and auto-configuration of RAID sets, and the ability to con- figure the root file system (_/) on a RAID set. ++oo Support for Microsoft Joliet extensions to the ISO9660 CD file sys- tem. ++oo Improved file system vnode locking mechanisms, thus resolving a source of several panics in the past. ++oo Support for NFS and RPC over IPv6. ++oo The server part of NFS locking (implemented by rpc.lockd(8)) now works. _S_e_c_u_r_i_t_y ++oo Strong cryptographic libraries and applications integrated, including the AES cipher Rijndael, the OpenSSL library, more complete Kerberos IV and Kerberos V support, and an SSH server and client. ++oo sysctl(3) interfaces to various elements of process and system infor- mation, allowing programs such as ps(1), dmesg(1) and the like to op- erate without recompilation after kernel upgrades, and remove the ne- cessity to run setgid kmem (thus improving system security). ++oo Disable various services by default, and set the default options for disabled daemons to a higher level of logging. ++oo Several code audits were performed. One audit replaced string rou- tines that were used without bounds checking, and another one identi- fied and disabled places where format strings were used in unsafe ways, allowing arbitrary data to be entered by (possibly) malicious users to overwrite application code, and leading from Denial of Ser- vice attacks to compromised systems. ++oo sshd(8) and ssh(1) now require rnd(4) kernel random number devices. _S_y_s_t_e_m _a_d_m_i_n_i_s_t_r_a_t_i_o_n _a_n_d _u_s_e_r _t_o_o_l_s ++oo Conversion of the rc(8) system startup and shutdown scripts to an `rc.d' mechanism, with separate control scripts for each service, and appropriate dependency ordering provided by rcorder(8). ++oo postfix(1) provided as alternative mail transport agent to sendmail(8). ++oo User management tools useradd(8), usermod(8), userdel(8), groupadd(8), groupmod(8), and groupdel(8) added to the system. ++oo Incorporation of a login class capability database (_/_e_t_c_/_l_o_g_i_n_._c_o_n_f) from BSD/OS. ++oo Improved support for usernames longer than eight characters in pro- grams such as at(1) and w(1). ++oo Many enhancements to ftpd(8) providing features found in larger and less secure FTP daemons, such as user classes, connection limits, im- proved support for virtual hosting, transfer statistics, transfer rate throttling, and support for various IETF ftpext working group extensions. ++oo The ftp(1) client has been improved even further, including transfer rate throttling, improved URL support, command line uploads. See the man page for details. _M_i_s_c_e_l_l_a_n_e_o_u_s ++oo Updates to the NetBSD source code style code (located in _/_u_s_r_/_s_h_a_r_e_/_m_i_s_c_/_s_t_y_l_e) to use ANSI C only (instead of K&R) and re- flect current (best) practice, and begin migrating the NetBSD source code to follow it. ++oo Implementation of many SUSv2 features to the curses(3) library, in- cluding support for color. ++oo Updates of most third party packages that are shipped in the base system, including file(1), ipfilter(4), ppp(4), and sendmail(8) to the latest stable release. ++oo Many new packages in the _p_k_g_s_r_c system, including standard desktops like KDE and GNOME as well as latest Tcl/Tk and perl and many of the components of the Java Enterprise platform. The package framework itself now has full wildcard dependency support. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.5.3 is the sixth release for the sparc. Some (but not all!) notable sparc-specific improvements include: ++oo Migration to the ELF binary format from a.out. ++oo Support for the JavaStation 1. ++oo HyperSPARCs now run reliably. ++oo Tadpole console and mouse now work. ++oo Support for the sun4/400 class of machines. NetBSD 1.5.3 on sparc is, as usual, also fully backward compatible with old NetBSD/sparc binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration. TThhee FFuuttuurree ooff NNeettBBSSDD The NetBSD Foundation has been incorporated as a non-profit organization. Its purpose is to encourage, foster and promote the free exchange of com- puter software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. The NetBSD Foundation will help improve the quality of NetBSD by: ++oo providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. ++oo providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. ++oo providing a better position from which to undertake promotional ac- tivities. ++oo periodically organizing workshops for developers and other interested people to discuss ongoing work. We intend to begin narrowing the time delay between releases. Our ambi- tion is to provide a full release every six to eight months. We hope to support even _m_o_r_e hardware in the future, and we have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily basis. We intend to integrate free, positive changes from whatever sources sub- mit them, providing that they are well thought-out and increase the us- ability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. SSoouurrcceess ooff NNeettBBSSDD Refer to hhttttpp::////wwwwww..nneettbbssdd..oorrgg//SSiitteess//nneett..hhttmmll. NNeettBBSSDD 11..55..33 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.5.3 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._5_._3_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.5.3 distribution. README.files README describing the distribution's contents. TODO NetBSD 's todo list (also somewhat incomplete and out of date). _p_a_t_c_h_e_s_/ Post-release source code patches. _s_o_u_r_c_e_/ Source distribution sets; see below. In addition to the files and directories listed above, there is one di- rectory per architecture, for each of the architectures for which NetBSD 1.5.3 has a binary distribution. There are also _R_E_A_D_M_E_._e_x_p_o_r_t_- _c_o_n_t_r_o_l files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution that may be subject to export regulations of the United States, e.g. code under _s_r_c_/_c_r_y_p_t_o and _s_r_c_/_s_y_s_/_c_r_y_p_t_o. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The source distribution sets can be found in subdirectories of the _s_o_u_r_c_e subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: ggnnuussrrcc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. _2_2_._3 _M_B _g_z_i_p_p_e_d_, _9_8_._8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ppkkggssrrcc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. _7_._4 _M_B _g_z_i_p_p_e_d_, _7_3_._0 _M_B _u_n_c_o_m_p_r_e_s_s_e_d sshhaarreessrrcc This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more. _3_._3 _M_B _g_z_i_p_p_e_d_, _1_3_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssrrcc This set contains all of the base NetBSD 1.5.3 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. _2_4_._8 _M_B _g_z_i_p_p_e_d_, _1_2_3_._1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssyyssssrrcc This set contains the sources to the NetBSD 1.5.3 kernel for all architectures; config(8); and dbsym(8). _1_8_._0 _M_B _g_z_i_p_p_e_d_, _9_0_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxssrrcc This set contains the sources to the X Window System. _7_8_._1 _M_B _g_z_i_p_p_e_d_, _3_9_3_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The source sets are distributed as compressed tar files. They may be un- packed into _/_u_s_r_/_s_r_c with the command: # (( ccdd // ;; ttaarr --zzxxppff -- )) << sseett__nnaammee..ttggzz The _s_e_t_s_/_S_p_l_i_t_/ subdirectory contains split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are named _s_e_t___n_a_m_e_._x_x where _s_e_t___n_a_m_e is the distribution set name, and _x_x is the sequence number of the file, starting with ``aa'' for the first file in the distribution set, then ``ab'' for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distri- bution set.) The split distributions may be reassembled and extracted with ccaatt as fol- lows: # ccaatt sseett__nnaammee..???? || (( ccdd // ;; ttaarr --zzxxppff -- )) In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: BSDSUM Historic BSD checksums for the various files in that di- rectory, in the format produced by the command: cckkssuumm --oo 11 _f_i_l_e. CKSUM POSIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm _f_i_l_e. MD5 MD5 digests for the various files in that directory, in the format produced by the command: cckkssuumm --mm _f_i_l_e. SYSVSUM Historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm --oo --22 _f_i_l_e. The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest pos- sible range of system can check the integrity of the release files. _N_e_t_B_S_D_/_s_p_a_r_c _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The sparc-specific portion of the NetBSD 1.5.3 release is found in the _s_p_a_r_c subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._5_._3_/_s_p_a_r_c_/ _I_N_S_T_A_L_L_._h_t_m_l _I_N_S_T_A_L_L_._p_s _I_N_S_T_A_L_L_._t_x_t _I_N_S_T_A_L_L_._m_o_r_e Installation notes in various file formats, including this file. The _._m_o_r_e file contains underlined text using the more(1) conventions for indicating italic and bold display. _b_i_n_a_r_y_/ _k_e_r_n_e_l_/ _n_e_t_b_s_d_._G_E_N_E_R_I_C_._g_z A gzipped NetBSD kernel containing code for everything supported in this release. _s_e_t_s_/ sparc binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _f_l_o_p_p_y_/ sparc boot and installation floppies; see be- low. _m_i_n_i_r_o_o_t_/ sparc miniroot file system image; see below. _m_i_s_c_/ Statically-linked versions of ggzziipp (GNU gzip) and ggttaarr (GNU tar). _n_e_t_b_o_o_t_/ Server boot-file image for diskless machines. _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD sparc binary distribution sets contain the binaries which com- prise the NetBSD 1.5.3 release for the sparc. There are eight binary dis- tribution sets. The binary distribution sets can be found in the _s_p_a_r_c_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.5.3 distribution tree, and are as follows: bbaassee The NetBSD 1.5.3 sparc bbaassee binary distribution. You _m_u_s_t in- stall this distribution set. It contains the base NetBSD utili- ties that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. _1_7_._5 _M_B _g_z_i_p_p_e_d_, _4_3_._7 _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_._1 _M_B _g_z_i_p_p_e_d_, _5_1_._9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d eettcc This distribution set contains the system configuration files that reside in _/_e_t_c and in several other places. This set _m_u_s_t be installed if you are installing the system from scratch, but should _n_o_t be used if you are upgrading. _0_._1 _M_B _g_z_i_p_p_e_d_, _0_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ggaammeess This set includes the games and their manual pages. _3_._0 _M_B _g_z_i_p_p_e_d_, _7_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn This set contains a NetBSD/sparc 1.5.3 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _1_._2 _M_B _g_z_i_p_p_e_d_, _2_._8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d mmaann This set includes all of the manual pages for the binaries and other software contained in the bbaassee set. Note that it does not include any of the manual pages that are included in the other sets. _5_._6 _M_B _g_z_i_p_p_e_d_, _2_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. _2_._2 _M_B _g_z_i_p_p_e_d_, _7_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d tteexxtt This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. _1_._3 _M_B _g_z_i_p_p_e_d_, _4_._4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. The binaries shipped with NetBSD 1.5.3 are based on XFree86 version 3.3.6. NetBSD is in the process of moving to XFree86 version 4, and the X source set actually contains source for both XFree86 3.3.6 and XFree86 4, and the ability to decide at compile-time which one to build and install. The X Window Sys- tem binary sets distributed with NetBSD are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. _2_._8 _M_B _g_z_i_p_p_e_d_, _8_._2 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoommpp The extra libraries and include files needed to compile X source code. _1_._8 _M_B _g_z_i_p_p_e_d_, _8_._3 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoonnttrriibb Programs that were contributed to X. _0_._2 _M_B _g_z_i_p_p_e_d_, _0_._6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxffoonntt Fonts needed by X. _6_._2 _M_B _g_z_i_p_p_e_d_, _7_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxsseerrvveerr The Xsun, Xsun24, XsunMono and Xprt servers with man pages. _3_._3 _M_B _g_z_i_p_p_e_d_, _8_._5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d The sparc binary distribution sets are distributed as gzipped tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are _/-relative and therefore are extracted _b_e_l_o_w the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the ttaarr --xxppff command from _/. _N_o_t_e_: The distribution cannot be extracted using the SunOS ttaarr program so statically-linked SunOS versions of ggzziipp (GNU gzip) and ggttaarr (GNU tar) are provided in _s_p_a_r_c_/_i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_s_c. _N_o_t_e_: Each directory in the sparc binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//ssppaarrcc SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess _S_u_p_p_o_r_t_e_d _m_a_c_h_i_n_e_s ++oo sun4 -- 4/100 -- 4/200 -- 4/300 -- 4/400 ++oo sun4c -- SPARCstation/server 1 -- SPARCstation/server 1+ -- SPARCstation/server 2 -- IPC -- ELC -- IPX -- SLC ++oo sun4c clones -- Aries Parrot II -- Opus/5000 -- Opus/5250 -- FORCE Sparc CPU1e/4 -- FORCE Sparc CPU2e/4 (and possibly more) _N_o_t_e_: NetBSD doesn't support the VME interface on the FORCE models ++oo sun4m -- 4/600 -- SPARC Classic -- SPARC LX -- SPARCstation 4 -- SPARCstation/server 5 -- SPARCstation/server 10 -- SPARCstation/server 20 -- Voyager -- JavaStation 1 _N_o_t_e_: All known MBus modules are supported ++oo sun4m clones -- Axil 245 -- Axil 311 -- Axil 320 -- Cycle C C Cycle 5-IP -- DTKstation/Classic+ -- RDI PowerLite-85 -- RDI PowerLite-110 -- RDI BriteLite -- Ross sparc 20 -- Transtec SS5/170 -- Tatung microCOMPstation 5 -- TWS SuperCOMPstation-20S -- Tadpole SPARCbook 3 series (and possibly more) _M_a_c_h_i_n_e_s _n_o_t _s_u_p_p_o_r_t_e_d _b_y _N_e_t_B_S_D_/_s_p_a_r_c ++oo sun4d -- SPARCcenter 1000 -- SPARCcenter 2000 ++oo sun4u and other UltraSPARC based machines These are supported by the NetBSD sparc64 port. Refer to hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//ssppaarrcc6644//iinnddeexx..hhttmmll ++oo Solbourne machines ++oo Other JavaStation models The minimal configuration requires 4 MB of RAM and ~60 MB of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended, as NetBSD with 4 MB of RAM feels like Solaris with 4 MB of RAM - slow. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU. _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo sun4c and sun4m video; Sbus card, on-board, or optional -- _b_w_t_w_o; 1 bpp framebuffer. On-board and Sbus card (MG1 and MG2) -- _c_g_t_h_r_e_e; 8 bpp framebuffer. On-board and Sbus card -- _c_g_s_i_x; 8 bpp accelerated framebuffer. On-board and Sbus card (GX, GX+, TGX, and TGX+) -- _c_g_f_o_u_r_t_e_e_n; SX 24 bpp accelerated framebuffer. On-board SPARCstation 10SX and SPARCstation 20, requires optional 4 or 8 MB VSIMM, limited to _c_g_t_h_r_e_e emulation -- _t_c_x; S24 accelerated color framebuffer. On-board SPARCsta- tion 4 (8 bpp) and optional on SPARCstation 5 (24 bpp), limited to _c_g_t_h_r_e_e emulation -- _p_n_o_z_z; Weitek p9100 24 bpp accelerated framebuffer. On- board Tadpole SPARCbook 3GS and 3GX, limited to _c_g_t_h_r_e_e em- ulation ++oo sun4 video; VME card, on-board, or P4 (supported only on 4/100 and 4/300 series machines) -- _b_w_t_w_o; 1 bpp framebuffer. On-board and P4 -- _c_g_t_w_o; 8 bpp framebuffer. VME card -- _c_g_f_o_u_r; 8 bpp framebuffer with overlay. P4 -- _c_g_s_i_x; LEGO 8 bpp accelerated framebuffer. P4 -- _c_g_e_i_g_h_t; 24 bpp framebuffer with overlay. P4 (not well tested) ++oo Network interfaces -- _b_e; 100 Mbps half-duplex ``Big Mac'' ethernet. Sbus card -- _e_n; Efficient Networks, Inc. ATM interface. Sbus card -- _h_m_e; 100 Mbps full-duplex ``Happy Meal'' ethernet. Sbus card (not well tested) -- _i_e; 10 Mbps Intel 82586 ethernet. On-board (4/100 and 4/200, may not be working properly on 4/400) and VME card -- _l_e; 10 Mbps AMD 9790 Lance ethernet. On-board (4/300, sun4c, and sun4m) and Sbus card -- _q_e_c; One 100 Mbps be interface and four 10 Mbps Mace ether- net interfaces. Sbus card -- _q_f_e; quad 100 Mbps full-duplex ``Happy Meal'' ethernet (four ethernet interfaces). Sbus card (not well tested) -- misc: various ethernet interfaces are found on multi-func- tion Sbus cards (e.g. along with SCSI), the ethernet inter- faces work even if the other functions do not ++oo SCSI interfaces -- _e_s_p; 5 MB/s and 10 MB/s (Fast) NCR 53C9x SCSI controller. On-board (sun4c, sun4m, and 4/300) and Sbus card -- _i_s_p; 10 MB/s (Fast) and 20 MB/s (Fast+Wide) Qlogic ISP 10x0 family. Sbus card -- _s_i; 5 MB/s NCR 5380 SCSI controller. VME card (Interrupt driven and polled DMA) -- _s_w; 5 MB/s NCR 5380 ``SCSI Weird'' controller. Onboard 4/110 (polled DMA only) -- misc: SCSI functionality is sometimes found on multi-func- tion Sbus cards (e.g. along with ethernet), the SCSI _e_s_p and _i_s_p portions of those cards should work, even if the other functions do not. _N_o_t_e_: See hhttttpp::////ssaattuurrnn..ttlluugg..oorrgg//ssuunnccddffaaqq// for information on bootable CD-ROMs ++oo VME disk interfaces -- _x_d; Xylogics 7053 VME/SMD disk controller -- _x_y; Xylogics 450/451 VME disk controller _N_o_t_e_: VME/IPI disks are not supported ++oo Floppy drives -- _f_d; floppy disk drive. On-board sun4c and sun4m -- _s_d; SCSI floppy drive, acts as a SCSI drive to kernel. found with some SPARCBook 3 machines ++oo Serial interfaces -- On-board serial ports based on Zilog 8530 and Zilog 85C30 (can be used as console if needed) ++oo Input devices -- Sun keyboard and mouse -- SPARCBook 3 keyboard and joystick -- Third-party keyboards, mice, and trackballs ++oo Audio -- _a_u_d_i_o_a_m_d; AMD 7930-based 8000 Hz, 8 bit, mono, mu-law. On- board sun4c and SPARC Classic -- _a_u_d_i_o_c_s; CS4231-based 44 KHz, 16 bit, stereo, PCM. On- board SPARCStation 5 and optional on SPARCStation 4 (does not support audio input) ++oo Misc cards -- _m_t_t_y _/ _m_b_p_p; Magma Serial/Parallel ports. Sbus card -- _x_b_o_x; Sun Sbus expander device _U_n_s_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo Use of more than one processor in sun4m machines (it boots, but only uses one processor) ++oo DBRIe-based audio and ISDN. On-board some sun4m machines (such as SS10, SS20, SPARC LX, and Tadpole SPARCbook) ++oo _s_c; Sun SCSI. VME card ++oo _b_p_p; Bi-directional parallel port. On-board and Sbus card ++oo _c_g_t_w_e_l_v_e; I.e. GS, 24 bpp framebuffer. Sbus card ++oo _l_e_o; I.e. ZX and TZX, 24 bpp accelerated framebuffer. Sbus card ++oo _n_e_l_l; Sbus-to-PCMCIA bridge GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa Installation is supported from several media types, including: ++oo CD-ROM ++oo MS-DOS floppy ++oo FTP ++oo Remote NFS partition ++oo Tape ++oo Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation de- pend upon which installation medium you choose. The steps for the vari- ous media are outlined below. _C_D_-_R_O_M Find out where the distribution set files are on the CD- ROM. Proceed to the instruction on installation. _M_S_-_D_O_S _f_l_o_p_p_y Count the number of _s_e_t___n_a_m_e_._x_x files that make up the distribution sets you want to install or upgrade. You will need one sixth that number of 1.44 MB floppies. Format all of the floppies with MS-DOS. Do _n_o_t make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distribution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box. Place all of the _s_e_t___n_a_m_e_._x_x files on the MS-DOS disks. Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the sec- tion on preparing your hard disk, below. If you're up- grading an existing installation, go directly to the sec- tion on upgrading. _F_T_P The preparations for this installation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the nu- meric IP address of the router closest to the NetBSD ma- chine. Finally, you need to know the numeric IP address of the NetBSD machine itself. If you don't have access to a functioning nameserver during installation, the IP ad- dress of ffttpp..nneettbbssdd..oorrgg is 204.152.184.75 (as of April, 2001). Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. _N_F_S Place the NetBSD distribution sets you wish to install in- to a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the _/_e_t_c_/_e_x_p_o_r_t_s file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine it- self. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on up- grading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. _T_a_p_e To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX-like system, the easi- est way to do so is probably something like: # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e _d_i_s_t___d_i_r_e_c_t_o_r_i_e_s where _t_a_p_e___d_e_v_i_c_e is the name of the tape device that de- scribes the tape drive you're using; possibly _/_d_e_v_/_r_s_t_0, or something similar, but it will vary from system to sys- tem. (If you can't figure it out, ask your system admin- istrator.) In the above example, _d_i_s_t___d_i_r_e_c_t_o_r_i_e_s are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the mmiisscc,, bbaassee,, and eettcc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: # ccdd ......//NNeettBBSSDD--11..55..33 # ccdd ssppaarrcc//bbiinnaarryy # ttaarr --ccff _t_a_p_e___d_e_v_i_c_e mmiisscc eettcc kkeerrnn _N_o_t_e_: You still need to fill in _t_a_p_e___d_e_v_i_c_e in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. _U_p_g_r_a_d_e If you are upgrading NetBSD, you also have the option of installing NetBSD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: Place the distribution sets you wish to upgrade somewhere in your current file system tree. Please note that the _/_d_e_v on the floppy used for upgrades only knows about wd0, wd1, sd0, sd1, and sd2. If you have more than two IDE drives or more than three SCSI drives, you should take care not to place the sets on the high-numbered drives. At a bare minimum, you must upgrade the bbaassee and kkeerrnn bi- nary distributions, and so must put the bbaassee and kkeerrnn sets somewhere in your file system. If you wish, you can do the other sets, as well, but you should _n_o_t upgrade the eettcc distribution; it contains contains system configura- tion files that you should review and update by hand. Once you have done this, you can proceed to the next step in the upgrade process, actually upgrading your system. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn _C_o_n_f_i_g_u_r_i_n_g _y_o_u_r _P_R_O_M Before you start, you should configure your PROM. There are three cate- gories of PROM: ``sunmon'' (sometimes called Restricted Prompt, sun moni- tor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2. The sun4 machines only have sunmon. Some of the early sun4c models default to sunmon but have OpenBoot PROM 1. The later sun4c models and all sun4m models have OpenBoot PROM 2. First, you need to stop your system from automatically booting when pow- ered on. Pressing the STOP key (sometimes called the L1 key, found on the left side of your keyboard) and the a key will halt your system and give you a PROM prompt. If you are using a Tadpole SPARCbook, you press the Pause and a keys. If you are using a serial console, send a ``BREAK'' signal from your terminal (the method of sending ``BREAK'' varies from terminal to terminal). Next, you should set your system to always use the OpenBoot PROM (some- times called ``new command mode'') if it defaults to sunmon. The NetBSD kernel relies on some of the functionality provided by the OpenBoot PROM. If your machine gives you a `>' prompt instead of an `ok' prompt, type: > nn ok sseetteennvv ssuunnmmoonn--ccoommppaatt?? ffaallssee ok Next, if you are using any security features of OpenBoot PROM, you should turn them off - NetBSD can't deal well with this. ok sseetteennvv sseeccuurriittyy--mmooddee nnoonnee The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCstation/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. There are three SCSI addressing schemes used by your system: SCSI target ID (set by physical jumpers on the device), PROM `unit' number (set by Open- Boot PROM 1, based on its SCSI target ID), and the name you reference within an operating system (set by the kernel, based on the PROM `unit' number). Sun shipped these systems with the internal drives set to SCSI target IDs 3 and 1. The default value of the OpenBoot PROM variable `sd-targets' is `31204567.' This variable maps how the OpenBoot PROM 1 assigns `unit' numbers based on the SCSI target ID. Thus the device at SCSI target ID 3 is considered `unit' 0, and the SCSI device at target ID 0 is `unit' 3. When you type ``bboooott ssccssii((00,,00,,00))'', the OpenBoot PROM will boot from `unit' 0 (which is SCSI target ID 3, the internal hard drive). The SunOS kernel is hard-wired to map sd0 to SCSI target 3, and sd3 to SCSI target 0. _P_R_O_M _U_n_i_t_# _S_C_S_I _T_a_r_g_e_t _S_u_n_O_S _n_a_m_e 0 3 sd0 1 1 sd1 2 2 sd2 3 0 sd3 4 4 st0 5 5 st1 6 6 cdrom The NetBSD/sparc GENERIC kernel does not wire things down as does SunOS. It names the disks in the order that the SCSI targets are probed (01234567). If you only have one disk, it is always sd0 regardless of its SCSI target ID or its PROM `unit' number, and there are no problems. If you have two disks, one at SCSI ID 2 ( `unit' 2) and SCSI ID 3 ( `unit' 0), then they are recognized as sd0 and sd1 respectively. This can be a problem if you are not aware of it, particularly when creating an fstab. There are two approaches to fixing this problem: changing the mapping that OpenBoot PROM 1 does, and changing the NetBSD kernel configuration. To get OpenBoot PROM 1 to number the SCSI `unit' numbers the same as the SCSI target IDs, you need to run this command: ok sseetteennvv ssdd--ttaarrggeettss 0011223344556677 This may, however, cause problems if you were to later attempt to use SunOS on this machine or if you reset the OpenBoot PROM variables. The other approach is to use a NetBSD kernel that matches the PROM's odd target mapping by treating `unit' 0 (i.e. SCSI target ID 3) as sd0 and `unit' 3 (i.e. SCSI target ID 0) as sd3. The GENERIC_SCSI3 kernel per- forms this target mapping, but the GENERIC and INSTALL kernels do not. _N_o_t_e_: This is also a concern when you start building your own customised kernels. The machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) have s similar SCSI target mapping in the form of a ddeevvaalliiaass entry. That is, the device alias ddiisskk is shorthand for the disk at SCSI ID 3 on the internal SCSI controller. Normally, the ddiisskk device alias is what the PROM uses as the default boot device, i.e. in the ab- sence of a _d_e_v_i_c_e argument to the bboooott command. Note that there are also pre-configured device alias entries for ddiisskk00,, ddiisskk11,, ddiisskk22 and ddiisskk33, which are in fact a one-to-one mapping to the SCSI targets 00 to 33 (all on the internal SCSI controller). Again, it may be advantageous to use a fixed ``SCSI target'' to ``NetBSD disk unit'' mapping in your kernel configuration file (such as is done in the GENERIC_SCSI3 kernel) to ensure that your disks remain showing up at the same NetBSD device unit numbers even if you add disks to your system at a later time. _D_e_t_e_r_m_i_n_i_n_g _h_o_w _t_o _a_c_c_e_s_s _y_o_u_r _S_C_S_I _d_i_s_k _f_r_o_m _t_h_e _P_R_O_M sunmon and OpenBoot PROM 1 use an archaic sd(_c_,_u_,_p)) syntax to address SC- SI devices. OpenBoot PROM 2 uses a more intuitive syntax using device aliases. To calculate the parameters for sunmon and OpenBoot PROM 1: _c specifies the SCSI controller number (first is 0, second is 1, ...) _u the hexadecimal number obtained from evaluating the expression _(_8 _* _T_A_R_G_E_T_) _+ _L_U_N _p the partition number from which to boot (`0' = `a', `1' = `b', etc.) Therefore, to boot from the swap partition on the internal hard drive (first SCSI bus, target 0, lun 0, partition 1), one would use: ok bboooott ssdd((00,,00,,11)) To boot from a CD-ROM (first SCSI bus, target 6, lun 0, partition dynami- cally determined), one would use: ok bboooott ssdd((00,,3300,,)) And, to boot from a kernel named netbsd-GENERIC on the fourth partition ( `d', often the _/_u_s_r partition) on an external hard drive (first SCSI bus, target 2, lun 0, partition 3), one would use: ok bboooott ssdd((00,,1100,,33))nneettbbssdd--GGEENNEERRIICC Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT ddeevvaalliiaass which provides simple mnemonics for the full path to the device. Type ddeevvaalliiaass in OpenBoot PROM 2 to get a list of all of the available aliases. Just the alias and partition are necessary when booting. Therefore, to boot from the swap partition on the internal hard drive (OpenBoot PROM 2 assumes the internal hard drive is at target 3), one would use: ok bboooott ddiisskk::bb To boot from a CD-ROM (OpenBoot PROM 2 assumes the CD-ROM is at target 6), one would use: ok bboooott ccddrroomm And, to boot from a kernel named netbsd-GENERIC on the fourth partition ( `d', often the _/_u_s_r partition) on an external hard drive (target 2, par- tition 3), one would use: ok bboooott ddiisskk22::dd nneettbbssdd--GGEENNEERRIICC The full device path specifier for OpenBoot PROM 2 depends on how Open- Boot PROM 2 recognizes your SCSI controller. Typically, one would use something like: _/_s_b_u_s_/_e_s_p_/_s_d_@_t_,_p where t is the SCSI target and p is the partition number. _D_e_c_i_d_i_n_g _o_n _p_a_r_t_i_t_i_o_n _s_i_z_e_s If you're installing NetBSD/sparc for the first time it's a good idea to look at the partition sizes of disk you intend installing NetBSD on. Asumming a classic partition scheme with _/ (root) and _/_u_s_r filesystems, a comfortable size for the NetBSD root filesystem partition is about 20 MB; a good initial size for the swap partition is twice the amount of physi- cal memory in your machine (though, unlike SunOS 4.x, there are no re- strictions on the size of the swap partition that would render part of your memory unusable). A full binary installation takes about 60 MB in _/_u_s_r. Most sparc systems have trouble booting if the root partition extends be- yond the first 2 GB of your disk. _C_o_n_f_i_g_u_r_a_t_i_o_n _o_f _n_e_t_w_o_r_k _i_n_t_e_r_f_a_c_e_s Some network devices (i.e. the built-in _l_e interface on sun4m machines) allow a choice between operating on a UTP or a AUI port. The _l_e driver supports automatic detection of the port which is actually connected to the wire. Additionally, some of the Fast ethernet devices (such as _b_e, _h_m_e, _q_e_c, and _q_f_e) support selection of various speeds and options. The default is to attempt to automatically detect the speed. If automatic detection is not available or not working properly in your environment, you may have to specify the type connection using the mmeeddiiaa parameter of ifconfig(8). During installation, you'll get the opportuni- ty to specify the appropriate medium. Use 10base5 or AUI to select the AUI connector, or 10baseT or UTP to select the UTP connector. Fast eth- ernet interfaces default to auto, which usually does not detect properly and runs at `10BaseT' speed. The options are 10baseT, 10baseTX, and auto. The _h_m_e and _q_f_e interfaces also allow 10baseT-FDX and 100baseT- FDX. IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm Installing NetBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. There are several ways to install NetBSD onto your system. The easiest way is to use the _m_i_n_i_r_o_o_t_._f_s image copied to your local disk's swap par- tition or a scratch drive. If your Sparc is hooked up in a network, you may configure another UNIX-like machine as a netboot server for your Sparc. Alternatively, there is a pair of floppy images that will boot your system and run the installer. For more information on the commands and variables available in the Open- Boot PROM (present in all sun4c and sun4m machines), go to hhttttpp::////ddooccss..ssuunn..ccoomm and search for ``openboot reference'' (without quotes). _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _p_l_a_c_i_n_g _a _b_o_o_t_a_b_l_e _f_i_l_e_s_y_s_t_e_m _o_n _a _p_a_r_t_i_t_i_o_n_e_d _h_a_r_d _d_r_i_v_e _i_n_s_t_a_l_l_a_t_i_o_n_/_m_i_n_i_r_o_o_t_/_m_i_n_i_r_o_o_t_._f_s_._g_z is a compressed, self-contained NetBSD filesystem holding all utilities necessary to install NetBSD onto a disk attached to your system. It is distributed as a compressed plain file you will transfer to a raw disk partition. You will then boot this installer using the appropriate PROM command. The simplest case is where you place the _m_i_n_i_r_o_o_t_._f_s filesystem on the swap partition of your disk. Alternatively, you can place it on any other unused partition on any disk (such as a Zip disk). Be forewarned that you will not be able to install NetBSD onto the partition that contains the _m_i_n_i_r_o_o_t_._f_s as this partition is needed during the install process. Loading the filesystem onto a raw partition is straightforward. First, download _m_i_n_i_r_o_o_t_._f_s to your system. Next, reboot in single-user mode (i.e. bboooott --ss) to ensure that your system will not be swapping. Final- ly, place the _m_i_n_i_r_o_o_t_._f_s on your partition of choice. On NetBSD or SunOS the commands are: # gguunnzziipp mmiinniirroooott..ffss..ggzz # dddd iiff==mmiinniirroooott..ffss ooff==//ddeevv//rrssdd00bb bbss==44kk ccoonnvv==ssyynncc Here, /dev/rsd0b is assumed to be your swap partition. If you decide to place _m_i_n_i_r_o_o_t_._f_s on a non-swap partition, it will overwrite all of the contents of that partition, but you will not need to reboot into single- user mode to write it. After transferring the filesystem to disk, bring the system down by: # hhaalltt Then boot the installer by typing the appropriate command at the PROM prompt (this example is for the swap partition): sunmon > bb ssdd((,,,,11))nneettbbssdd --ss OpenBoot PROM 1 ok bboooott ssdd((,,,,11))nneettbbssdd --ss OpenBoot PROM 2 ok bboooott ddiisskk::bb nneettbbssdd --ss The monitor boot command will load the NetBSD kernel contained in the filesystem image. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s_. below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _b_o_o_t_a_b_l_e _C_D_-_R_O_M If you wish to burn a CD-R containing a bootable NetBSD installation, then you can either burn the prepared disk image in _i_n_s_t_a_l_l_a_t_i_o_n_/_c_d_r_o_m_/_n_e_t_b_s_d_-_s_p_a_r_c_._i_s_o or create your own. If you wish to create your own, you should follow the directions on the NetBSD Bootable CD-ROM HOW-TO at: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//bboooottccdd..hhttmmll##ssppaarrcciimmaaggee Once you have downloaded _n_e_t_b_s_d_-_s_p_a_r_c_._i_s_o or created your own disk image, then you need to burn it to a CD-R. The CD-ROM attached to your Sparc must support 512 byte sectors to be bootable. All Sun brand CD-ROMs will work, as well as many other manu- facturers. See the Sun CD-ROM FAQ: hhttttpp::////ssaattuurrnn..ttlluugg..oorrgg//ssuunnccddffaaqq// Sun sets their CD-ROM drives to SCSI ID 6. We recommend you do the same. Boot the installer by typing the appropriate command at the PROM prompt: sunmon > bb ssdd((,,3300,,)) OpenBoot PROM 1 ok bboooott ssdd((,,3300,,)) OpenBoot PROM 2 ok bboooott ccddrroomm After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s_. below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _t_h_e _b_o_o_t_a_b_l_e _f_l_o_p_p_i_e_s The NetBSD install floppies only work on the sun4c and sun4m machines. Making the install floppies is fairly straightforward. NetBSD and SunOS use the same commands. First, get two 1.44 MB floppy disks and format them either using the fdformat(8) command or a PC. # ffddffoorrmmaatt Be sure that the `fdformat' command completes successfully before pro- ceeding; on NetBSD success is a string of all `V 's', and on SunOS suc- cess is a string of `. 's'. Next, transfer the two floppy images (_i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_d_i_s_k_1_._g_z and _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_d_i_s_k_2) to the disks you just formatted. You can do this step from NetBSD, SunOS, or a Windows machine using rraawwrriittee..eexxee (available in the NetBSD/i386 distribution). Insert the first floppy and run the following commands: # gguunnzziipp ddiisskk11..ggzz # dddd iiff==ddiisskk11 ooff==//ddeevv//rrffdd00aa bbss==3366kk # eejjeecctt ffllooppppyy Insert the second floppy and run the following commands: # dddd iiff==ddiisskk22 ooff==//ddeevv//rrffdd00aa bbss==3366kk ccoonnvv==ssyynncc # eejjeecctt ffllooppppyy Be sure to label your floppies so you can later identify them. Insert the floppy made from _d_i_s_k_1 into your Sparc. From the OpenBoot prompt, boot the floppy with the following command: OpenBoot PROM 1 ok bboooott ffdd((,,,,11)) OpenBoot PROM 1 (alternate) ok bboooott //ffdd OpenBoot PROM 2 ok bboooott ffllooppppyy After the initial probe messages you'll be asked to insert the floppy la- beled ``NetBSD disk2''. If the floppy is not automatically ejected, you can either use a straightened paperclip to eject the disk or do the fol- lowing: Press the STOP key (sometimes called the L1 key, found on the left side of your keyboard) and the a key, which will halt your system and give you a PROM prompt. ok eejjeecctt ok ggoo Now, insert the floppy labeled disk2. After the installation tools have been loaded, you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s_. below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _n_e_t_b_o_o_t _s_e_t_u_p First, you must setup a netboot server to provide the services and files your client needs. If you are using a NetBSD system as the netboot serv- er, have a look at the diskless(8) manual page for a more detailed guide on how to proceed with this. If the server runs another operating sys- tem, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary to configure a netboot server on a variety of platforms. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//nneettwwoorrkk//nneettbboooott// This section will briefly describe what happens during a Sparc netboot, and the next section will give a brief set of directions on how to set up your server. Your Sparc initially broadcasts a RARP request, and expects a server to reply with your client's IP address. Next, it downloads a second stage bootstrap program via TFTP from the server that responded to the RARP request. It will look for a filename composed of the machine's IP address followed by the machine's architecture, separated by a period. For example, a sun4c machine which has been assigned IP address 130.115.144.11, will make an TFTP request for _8_2_7_3_9_0_0_B_._S_U_N_4_C. This file is a symbolic link to the second-stage boot program, which should be lo- cated in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). The boot program to use is _i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t_/_b_o_o_t_._n_e_t Alternatively, you can find the bootstrap program in _/_u_s_r_/_m_d_e_c_/_b_o_o_t_._n_e_t in the NetBSD/sparc distribution. _N_o_t_e_: The only difference between _/_u_s_r_/_m_d_e_c_/_b_o_o_t_._n_e_t and _/_u_s_r_/_m_d_e_c_/_b_o_o_t is in the a.out header, which has been magically transformed in a way that makes it usable on all versions of Sparc PROMs. After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request should contain the client's name. This name is used in next step, a BOOTPARAM GETFILE request - sent to the server that responded to the WHOAMI request - requesting the name and address of the machine that will serve the client's root directory, as well as the path of the client's root on that server. Finally, this information is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corre- sponding to the root filesystem. Once the NFS mount is complete, the boot program starts reading from the remote root filesystem in search of the kernel which is then read into memory. _C_o_n_f_i_g_u_r_i_n_g _y_o_u_r _n_e_t_b_o_o_t _s_e_r_v_e_r Follow this section to configure a NetBSD machine as your netboot server. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hardware ad- dress) of your netboot client machine that you wish to install NetBSD on. We use `192.168.1.10' as the IP address of your client, and `client.test.net' as the name. The server name is `server.test.net', and the path on the server to the NFS exported directory is _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t although you may choose to use a different path. Create an _/_e_t_c_/_e_t_h_e_r_s file with the following line: CC:CC:CC:CC:CC:CC client Add your client to the server's _/_e_t_c_/_h_o_s_t_s file: 192.168.1.10 client If rraarrppdd is currently running, restart it (kill -HUP), otherwise start rraarrppdd: # //uussrr//ssbbiinn//rraarrppdd --aa Next, create _/_e_t_c_/_b_o_o_t_p_a_r_a_m_s with the following line: client root=server:/export/client/root If rrppcc..bboooottppaarraammdd is currently running, restart it (kkiillll --HHUUPP), otherwise start rrppcc..bboooottppaarraammdd: # //uussrr//ssbbiinn//rrppcc..bboooottppaarraammdd Now, make sure the bootloader in _/_t_f_t_p_b_o_o_t is linked to, or a copy of, _b_o_o_t_._n_e_t and is named appropriately for your client (in this case, it would be _C_0_A_8_0_1_0_A_._S_U_N_4_C), E.g.: # ccpp bboooott..nneett //ttffttppbboooott # ccdd //ttffttppbboooott # llnn --ss bboooott..nneett CC00AA88001100AA..SSUUNN44CC Now, you should edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f and make sure that the line starting with tftp is uncommented. You will need to kkiillll --HHUUPP the iinneettdd process to enable tftp if this line was previously commented out. The next step is to set up NFS exports. Create the directory you are exporting for the netboot client: # mmkkddiirr --pp //eexxppoorrtt//cclliieenntt//rroooott Put the following line in _/_e_t_c_/_e_x_p_o_r_t_s to enable NFS sharing: /export/client/root -maproot=root client.test.net If your server is currently running NFS services, you only need to kkiillll --HHUUPP the mmoouunnttdd process. Otherwise, you need to run: # //uussrr//ssbbiinn//mmoouunnttdd # //uussrr//ssbbiinn//nnffssdd --ttuunn 44 Now, you need to place the files your netboot client will need. As noted above in the section _P_r_e_p_a_r_i_n_g _y_o_u_r _S_y_s_t_e_m _f_o_r _N_e_t_B_S_D _I_n_s_t_a_l_l_a_t_i_o_n you have several options when choosing a location to store the distribution filesets. However, the easiest way is to put the distribution files into the exported directory for your client on the server. # mmvv **..ttggzz //eexxppoorrtt//cclliieenntt//rroooott Your client will need a kernel to boot (use _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). # gguunnzziipp nneettbbssdd..GGEENNEERRIICC..ggzz # mmvv nneettbbssdd..GGEENNEERRIICC //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd Your client will need installation tools (use _i_n_s_t_a_l_l_a_t_i_o_n_/_n_e_t_b_o_o_t_/_r_o_o_t_f_s_._t_g_z). # gguunnzziipp << rroooottffss..ttggzz || ((ccdd //eexxppoorrtt//cclliieenntt//rroooott &&&& ttaarr --xxppff --)) Now, netboot your Sparc from the server by entering the appropriate bboooott ccoommmmaanndd aatt tthhee mmoonniittoorr pprroommpptt.. Depending on the PROM version in your ma- chine, this command takes one of the following forms: sunmon > bb llee(())nneettbbssdd OpenBoot PROM 1 ok bb llee(())nneettbbssdd OpenBoot PROM 2 ok bb nneett nneettbbssdd After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s_. below. _I_n_s_t_a_l_l_i_n_g _N_e_t_B_S_D _b_y _u_s_i_n_g _a _b_o_o_t_a_b_l_e _t_a_p_e Sun sets their tape drives to SCSI ID 4. We recommend you do the same. Get the tape images (_i_n_s_t_a_l_l_a_t_i_o_n_/_t_a_p_e_/_t_a_p_e_f_i_l_e_1_._g_z and _i_n_s_t_a_l_l_a_t_i_o_n_/_t_a_p_e_/_t_a_p_e_f_i_l_e_2) and transfer them to a tape. Make sure you use the `no rewind scsi tape' device. Run the following commands: # gguunnzziipp ttaappeeffiillee11..ggzz # mmtt --ff //ddeevv//nnrrsstt00 rreeww # dddd iiff==ttaappeeffiillee11 ooff==//ddeevv//nnrrsstt00 bbss==44kk # dddd iiff==ttaappeeffiillee22 ooff==//ddeevv//nnrrsstt00 bbss==44kk Now you can transfer the NetBSD 1.5.3. distribution sets from (_b_i_n_a_r_y_/_s_e_t_s) to the tape by using a series of additional # dddd iiff==<>..ttggzz ooff==//ddeevv//nnrrsstt00 bbss==44kk commands. See also the section _G_e_t_t_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m _o_n _t_o _U_s_e_f_u_l _M_e_d_i_a_. Be sure to mark the location of these files on the tape; you'll need them during the installation procedure. Insert the tape into your Sparc's tapestation. Boot the installer by typing the appropriate command at the PROM prompt: sunmon > bb sstt(()) OpenBoot PROM 1 ok bboooott sstt(()) OpenBoot PROM 2 ok bboooott ttaappee After the initial probe messages you'll be asked to confirm the tape de- vice and tape file number containing the installation tools. Then, pro- ceed to the section _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s_. below. _R_u_n_n_i_n_g _t_h_e _i_n_s_t_a_l_l_a_t_i_o_n _s_c_r_i_p_t_s The first thing that the installation scripts will inquire about is the type of console you're using on your machine. If you're using a Sun frame buffer display, choose the terminal type ssuunn (this is presented as the default). _N_o_t_e_: if your frame buffer device is a cgsix Sbus board, you should change the terminal type to ssuunn--ccggssiixx to avoid triggering a bug in the board's firmware code that can garble your screen. If you're using a terminal device connected to a serial port, choose a terminal type appropriate for that device, e.g. vvtt110000 or vvtt220000. Next, you will be presented with a choice of two installation methods: a new full-screen ssyyssiinnsstt program, or the traditional script-based mmiinniirroooott program. The ssyyssiinnsstt program is easier to use, but the mmiinniirroooott program is more flexible. Both of these installation methods will follow the same set of procedures and will fully install NetBSD on your Sparc. You will frequently be asked for confirmation before the system proceeds with each phase of the installation process. Occasionally, you will have to provide a piece of information such as the name of the disk you want to install on, partitioning information, or IP addresses and domain names you want to assign. If your system has more than one disk, you may want to look at the output of the dmesg(8) command to see how your disks have been identified by the kernel. _N_o_t_e_: If you repartition a hard drive, be certain that every partition starts on a cylinder boundary for compatability with the Sparc ROM. The installation script goes through the following phases: ++oo determination of the disk on which to install NetBSD ++oo checking/creation of the partition information on the disk ++oo creating and mounting the NetBSD filesystems ++oo setup of network configuration ++oo extraction of the distribution tar files ++oo installation of bootstrap programs Now try a reboot. Initially we'd suggest you bboooott ssdd(())nneettbbssdd --bbss, then try multiuser after that. If you boot single-user the NetBSD incantation to make the root filesystem writable is # mmoouunntt --uu //ddeevv//ssdd00aa // Your PROM might have been setup to instruct the boot program to load a file called _v_m_u_n_i_x. On OpenBoot PROM systems you can change it to load _n_e_t_b_s_d instead using the following commands: OpenBoot PROM 1 ok sseetteennvv bboooott--ffrroomm ssdd((00,,00,,00))nneettbbssdd OpenBoot PROM 2 ok sseetteennvv bboooott--ffiillee nneettbbssdd ok sseetteennvv bboooott--ddeevviiccee ddiisskk::aa _C_o_n_g_r_a_t_u_l_a_t_i_o_n_s, you have successfully installed NetBSD 1.5.3. PPoosstt iinnssttaallllaattiioonn sstteeppss Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below. 1. Configuring _/_e_t_c_/_r_c_._c_o_n_f If you or the installation software haven't done any configuration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt usually will), the system will drop you in- to single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (_/) mounted read-write. When the sys- tem asks you to choose a shell, simply press RETURN to get to a _/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with ssuunn for a local console, or whatever is appropriate for your serial console (some systems display garbage with a ssuunn terminal type, you may need to use ssuunn--ssss55) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # ssttttyy eerraassee ''^^hh'' # ssttttyy eerraassee ''^^??'' At this point, you need to configure at least one file in the _/_e_t_c directory. You will need to mount your root filesystem read/write with: # //ssbbiinn//mmoouunntt --uu --ww // Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). If your _/_u_s_r directory is on a separate partition and you do not know how to use eedd, you will have to mount your _/_u_s_r partition to gain access to eexx or vvii. Do the following: # mmoouunntt //uussrr # eexxppoorrtt TTEERRMM==ssuunn If you have _/_v_a_r on a separate partition, you need to repeat that step for it. After that, you can edit _/_e_t_c_/_r_c_._c_o_n_f with vi(1). When you have finished, type eexxiitt at the prompt to leave the single-user shell and continue with the multi-user boot. Other values that need to be set in _/_e_t_c_/_r_c_._c_o_n_f for a networked en- vironment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e, furthermore add an _i_f_c_o_n_f_i_g___i_n_t for your network interface, along the lines of ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0" ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have _m_y_n_a_m_e_._m_y_._d_o_m in _/_e_t_c_/_h_o_s_t_s: ifconfig_le0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an _/_e_t_c_/_r_e_s_o_l_v_._c_o_n_f file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Other files in _/_e_t_c that may require modification or setting up in- clude _/_e_t_c_/_m_a_i_l_e_r_._c_o_n_f, _/_e_t_c_/_n_s_s_w_i_t_c_h_._c_o_n_f, and _/_e_t_c_/_w_s_c_o_n_s_._c_o_n_f. 2. Logging in After reboot, you can log in as root at the login prompt. Unless you've set a password in ssyyssiinnsstt, there is no initial password. If you're using the machine in a networked environment, you should cre- ate an account for yourself (see below) and protect it and the ``root'' account with good passwords. Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...]. 3. Adding accounts Use the useradd(8) command to add accounts to your system, _d_o _n_o_t edit _/_e_t_c_/_p_a_s_s_w_d directly. See useradd(8) for more information on how to add a new user to the system. 4. The X Window System If you have installed the X Window System, look at the files in _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c for information. Don't forget to add _/_u_s_r_/_X_1_1_R_6_/_b_i_n to your path in your shell's dot file so that you have access to the X binaries. 5. Installing third party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies in- stallation (and deinstallation), both from source and precompiled binaries. ++oo More information on the package system is at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//ssooffttwwaarree//ppaacckkaaggeess..hhttmmll ++oo A browsable listing of available packages is at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//RREEAADDMMEE..hhttmmll ++oo Precompiled binaries can be found at ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess, usually in the _1_._5_._3_/_s_p_a_r_c_/_A_l_l subdir. You can install them with the following commands: ## eexxppoorrtt PPKKGG__PPAATTHH==\\ ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..55..33//ssppaarrcc//AAllll\\;;\\ ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..55//ssppaarrcc//AAllll ## ppkkgg__aadddd --vv ttccsshh ## ppkkgg__aadddd --vv ccvvss ## ppkkgg__aadddd --vv aappaacchhee ## ppkkgg__aadddd --vv ppeerrll ... The above commands will install the tcsh shell, the CVS source code management system, the Apache web server and the perl pro- gramming language as well as all the packages they depend on. ++oo Package sources for compiling packages on your own can be ob- tained by retrieving the file ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//NNeettBBSSDD-- ccuurrrreenntt//ttaarr__ffiilleess//ppkkggssrrcc..ttaarr..ggzz They are typically extracted into _/_u_s_r_/_p_k_g_s_r_c (though other lo- cations work fine), with the commands: # mmkkddiirr //uussrr//ppkkggssrrcc # (( ccdd //uussrr//ppkkggssrrcc ;; ttaarr --zzxxppff -- )) << ppkkggssrrcc..ttaarr..ggzz After extracting, then see the _R_E_A_D_M_E file in the extraction di- rectory (e.g. _/_u_s_r_/_p_k_g_s_r_c_/_R_E_A_D_M_E) for more information. 6. Misc ++oo Edit _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. ++oo The _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f file will almost definitely need to be adjusted; files aiding in this can be found in _/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l. See the README file there for more infor- mation. ++oo Edit _/_e_t_c_/_r_c_._l_o_c_a_l to run any local daemons you use. ++oo Many of the _/_e_t_c files are documented in section 5 of the manu- al; so just invoking # mmaann 55 _f_i_l_e_n_a_m_e is likely to give you more information on these files. UUppggrraaddiinngg aa pprreevviioouussllyy--iinnssttaalllleedd NNeettBBSSDD SSyysstteemm The upgrade to NetBSD 1.5.3 is a binary upgrade; it can be quite diffi- cult to advance to a later version by recompiling from source due primar- ily to interdependencies in the various components. To do the upgrade, you must boot from the installer kernel using one of the methods described above. To do the upgrade, you must have the boot floppy available. 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 the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. If you have a few megabytes free on each of your root (_/) and _/_u_s_r partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your NetBSD parti- tion, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to _b_a_c_k _u_p _a_n_y _i_m_p_o_r_t_a_n_t _d_a_t_a _o_n _y_o_u_r _d_i_s_k, whether on the NetBSD partition or on another operat- ing system's partition, before beginning the upgrade process. The upgrade procedure using the ssyyssiinnsstt tool is similar to an installa- tion, but without the hard disk partitioning. The original _/_e_t_c directo- ry is renamed to _/_e_t_c_._o_l_d, and no attempt is made to merge any of the previous configuration into the new system except that the previous _/_e_t_c_/_f_s_t_a_b file is copied into the new configuration. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some san- ity checks are done, i.e. file systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.5.3 system. However, that doesn't mean that you're fin- ished with the upgrade process. You will probably want to update the set of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v by hand, you will need to be careful about this, but if not, you can just cd into _/_d_e_v, and run the command: # sshh MMAAKKEEDDEEVV aallll You must also deal with certain changes in the formats of some of the configuration files. The most notable change is that the options given to many of the file systems in _/_e_t_c_/_f_s_t_a_b have changed, and some of the file systems have changed names. To find out what the new options are, it's suggested that you read the manual page for the file system's mount com- mands, for example mount_nfs(8) for NFS. Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. NetBSD/sparc has switched its executable format from the old a.out format to ELF, the now more commonly used and supported format. Your old bina- ries will continue to work just fine. The installation procedure will try to take the necessary steps to accomplish this. The most important step is to move the old a.out shared libraries in _/_u_s_r_/_l_i_b and _/_u_s_r_/_X_1_1_R_6_/_l_i_b (if X was installed) to _/_e_m_u_l_/_a_o_u_t, where they will be automatically found if an older a.out binary is executed. Sysinst will use an existing _/_e_m_u_l and / or _/_e_m_u_l_/_a_o_u_t directory if available, and will create it (as a symbolic link to _/_u_s_r_/_a_o_u_t) if necessary. If you already had a _/_e_m_u_l directory, or a symbolic link by that name, sysinst should rename it and tell you about it. CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.5.3. _G_e_n_e_r_a_l _i_s_s_u_e_s ++oo _/_e_t_c_/_r_c modified to use _/_e_t_c_/_r_c_._d_/_* Prior to NetBSD 1.5, _/_e_t_c_/_r_c was a traditional BSD style monolithic file; each discrete program or substem from _/_e_t_c_/_r_c and _/_e_t_c_/_n_e_t_s_t_a_r_t has been moved into separate scripts in _/_e_t_c_/_r_c_._d_/. At system startup, _/_e_t_c_/_r_c uses rcorder(8) to build a dependency list of the files in _/_e_t_c_/_r_c_._d and then executes each script in turn with an argument of `start'. Many _r_c_._d scripts won't start unless the ap- propriate rc.conf(5) entry in _/_e_t_c_/_r_c_._c_o_n_f is set to `YES.' At system shutdown, _/_e_t_c_/_r_c_._s_h_u_t_d_o_w_n uses rcorder(8) to build a de- pendency list of the files in _/_e_t_c_/_r_c_._d that have a ``KEYWORD: shutdown'' line, reverses the resulting list, and then executes each script in turn with an argument of `stop'. The following scripts support a specific shutdown method: _c_r_o_n, _i_n_e_t_d, _l_o_c_a_l, and _x_d_m. Local and third-party scripts may be installed into _/_e_t_c_/_r_c_._d as nec- essary. Refer to the other scripts in that directory and rc(8) for more information on implementing _r_c_._d scripts. _I_s_s_u_e_s _a_f_f_e_c_t_i_n_g _a_n _u_p_g_r_a_d_e _f_r_o_m _N_e_t_B_S_D _1_._4 _o_r _p_r_i_o_r ++oo named(8) leaks version information Previous releases of NetBSD disabled a feature of named(8) where the version number of the server could be determined by remote clients. This feature has not been disabled in NetBSD 1.5, because there is a named.conf(5) option to change the version string: option { version "newstring"; }; ++oo sysctl(8) pathname changed sysctl(8) is moved from _/_u_s_r_/_s_b_i_n_/_s_y_s_c_t_l to _/_s_b_i_n_/_s_y_s_c_t_l. If you have hardcoded references to the full pathname (in shell scripts, for example) please be sure to update those. ++oo sendmail(8) configuration file pathname changed Due to sendmail(8) upgrade from 8.9.x to 8.10.x, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_f is moved to _/_e_t_c_/_m_a_i_l_/_s_e_n_d_m_a_i_l_._c_f. Also, the default sendmail.cf(5) refers different pathnames than before. For example, _/_e_t_c_/_a_l_i_a_s_e_s is now located at _/_e_t_c_/_m_a_i_l_/_a_l_i_a_s_e_s, _/_e_t_c_/_s_e_n_d_m_a_i_l_._c_w is now called _/_e_t_c_/_m_a_i_l_/_l_o_c_a_l_-_h_o_s_t_-_n_a_m_e_s, and so forth. If you have customized sendmail.cf(5) and friends, you will need to move the files to the new locations. See _/_u_s_r_/_s_h_a_r_e_/_s_e_n_d_m_a_i_l_/_R_E_A_D_M_E for more information. UUssiinngg oonnlliinnee NNeettBBSSDD ddooccuummeennttaattiioonn Documentation is available if you first install the manual distribution set. Traditionally, the ``man pages'' (documentation) are denoted by `name(section)'. Some examples of this are ++oo intro(1), ++oo man(1), ++oo apropros(1), ++oo passwd(1), and ++oo passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The _m_a_n command is used to view the documentation on a topic, and is started by entering mmaann [_s_e_c_t_i_o_n] _t_o_p_i_c. The brackets [] around the sec- tion should not be entered, but rather indicate that the section is op- tional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after log- ging in, enter # mmaann ppaasssswwdd to read the documentation for passwd(1). To view the documentation for passwd(5), enter # mmaann 55 ppaasssswwdd instead. If you are unsure of what man page you are looking for, enter aapprrooppooss _s_u_b_j_e_c_t_-_w_o_r_d where _s_u_b_j_e_c_t_-_w_o_r_d is your topic of interest; a list of possibly related man pages will be displayed. AAddmmiinniissttrriivviiaa If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at _m_a_j_o_r_d_o_m_o_@_n_e_t_b_s_d_._o_r_g. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instruc- tions. There are various mailing lists set up to deal with comments and ques- tions about this release. Please send comments to: _n_e_t_b_s_d_- _c_o_m_m_e_n_t_s_@_n_e_t_b_s_d_._o_r_g. To report bugs, use the send-pr(1) command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports in- clude lots of details. Additionally, bug reports can be sent by mail to: _n_e_t_b_s_d_-_b_u_g_s_@_n_e_t_b_s_d_._o_r_g. Use of send-pr(1) is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit hhttttpp::////wwwwww..nneettbbssdd..oorrgg//MMaaiilliinnggLLiissttss//. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed be- low). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: _n_e_t_b_s_d_-_h_e_l_p_@_n_e_t_b_s_d_._o_r_g. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. TThhaannkkss ggoo ttoo ++oo The former members of UCB's Computer Systems Research Group, includ- ing (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. ++oo Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. ++oo UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. ++oo Vixie Enterprises for hosting the NetBSD FTP, SUP, and WWW servers. ++oo Redback Networks, Inc. for hosting the NetBSD mail and GNATS server. ++oo The Helsinki University of Technology in Finland for hosting the NetBSD CVS server. ++oo The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. ++oo The many organisations that provide NetBSD mirror sites. ++oo Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. ++oo Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. ++oo The following individuals and organizations (each in alphabetical or- der) have made donations or loans of hardware and/or money, to sup- port NetBSD development, and deserve credit for it: Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard S/oren J/orvang Scott Kaplan Noah M. Keiserman Harald Koerfgen John Kohl Chris Legrow Ted Lemon Norman R. McBride Neil J. McRae Perry E. Metzger Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Reinoud Zandijk Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) ++oo Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) WWee aarree...... (in alphabetical order) _T_h_e _N_e_t_B_S_D _c_o_r_e _g_r_o_u_p_: Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g Luke Mewburn _l_u_k_e_m_@_n_e_t_b_s_d_._o_r_g Christos Zoulas _c_h_r_i_s_t_o_s_@_n_e_t_b_s_d_._o_r_g _T_h_e _p_o_r_t_m_a_s_t_e_r_s _(_a_n_d _t_h_e_i_r _p_o_r_t_s_)_: Mark Brinicombe _m_a_r_k_@_n_e_t_b_s_d_._o_r_g aarrmm3322 Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g ssuunn33xx Matt Fredette _f_r_e_d_e_t_t_e_@_n_e_t_b_s_d_._o_r_g ssuunn22 Ross Harvey _r_o_s_s_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g sshh33 Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g aarrmm2266 Eduardo Horvath _e_e_h_@_n_e_t_b_s_d_._o_r_g ssppaarrcc6644 Darrin Jewell _d_b_j_@_n_e_t_b_s_d_._o_r_g nneexxtt6688kk S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ccoobbaalltt S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ssggiimmiippss Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g mmiippssccoo Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g ssppaarrcc Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g vvaaxx Minoura Makoto _m_i_n_o_u_r_a_@_n_e_t_b_s_d_._o_r_g xx6688kk Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g ppcc553322 Tohru Nishimura _n_i_s_i_m_u_r_a_@_n_e_t_b_s_d_._o_r_g lluunnaa6688kk NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g pprreepp Scott Reynolds _s_c_o_t_t_r_@_n_e_t_b_s_d_._o_r_g mmaacc6688kk Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g bbeebbooxx Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g aarrcc Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g ooffppppcc Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g aammiiggaa Jonathan Stone _j_o_n_a_t_h_a_n_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Shin Takemura _t_a_k_e_m_u_r_a_@_n_e_t_b_s_d_._o_r_g hhppccmmiippss Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g hhpp330000 Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g mmaaccppppcc Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g nneewwssmmiippss Izumi Tsutsui _t_s_u_t_s_u_i_@_n_e_t_b_s_d_._o_r_g nneewwss6688kk Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g ii338866 Leo Weppelman _l_e_o_@_n_e_t_b_s_d_._o_r_g aattaarrii Nathan Williams _n_a_t_h_a_n_w_@_n_e_t_b_s_d_._o_r_g ssuunn33 Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmee6688kk _T_h_e _N_e_t_B_S_D _1_._5_._3 _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_: Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g _D_e_v_e_l_o_p_e_r_s _a_n_d _o_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_: Nathan Ahlstrom _n_r_a_@_N_e_t_B_S_D_._o_r_g Steve Allen _w_o_r_m_e_y_@_n_e_t_b_s_d_._o_r_g Julian Assange _p_r_o_f_f_@_n_e_t_b_s_d_._o_r_g Lennart Augustsson _a_u_g_u_s_t_s_s_@_n_e_t_b_s_d_._o_r_g Christoph Badura _b_a_d_@_n_e_t_b_s_d_._o_r_g 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 John Birrell _j_b_@_n_e_t_b_s_d_._o_r_g Mason Loring Bliss _m_a_s_o_n_@_n_e_t_b_s_d_._o_r_g Rafal Boni _r_a_f_a_l_@_n_e_t_b_s_d_._o_r_g Manuel Bouyer _b_o_u_y_e_r_@_n_e_t_b_s_d_._o_r_g John Brezak _b_r_e_z_a_k_@_n_e_t_b_s_d_._o_r_g Allen Briggs _b_r_i_g_g_s_@_n_e_t_b_s_d_._o_r_g Aaron Brown _a_b_r_o_w_n_@_n_e_t_b_s_d_._o_r_g Andrew Brown _a_t_a_t_a_t_@_n_e_t_b_s_d_._o_r_g David Brownlee _a_b_s_@_n_e_t_b_s_d_._o_r_g Frederick Bruckman _f_r_e_d_b_@_n_e_t_b_s_d_._o_r_g Jon Buller _j_o_n_b_@_n_e_t_b_s_d_._o_r_g Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t Robert Byrnes _b_y_r_n_e_s_@_n_e_t_b_s_d_._o_r_g D'Arcy J.M. Cain _d_a_r_c_y_@_n_e_t_b_s_d_._o_r_g Dave Carrel _c_a_r_r_e_l_@_n_e_t_b_s_d_._o_r_g James Chacon _j_m_c_@_n_e_t_b_s_d_._o_r_g Bill Coldwell _b_i_l_l_c_@_n_e_t_b_s_d_._o_r_g Julian Coleman _j_d_c_@_n_e_t_b_s_d_._o_r_g Chuck Cranor _c_h_u_c_k_@_n_e_t_b_s_d_._o_r_g 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 Hubert Feyrer _h_u_b_e_r_t_f_@_n_e_t_b_s_d_._o_r_g Jason R. Fink _j_r_f_@_n_e_t_b_s_d_._o_r_g Thorsten Frueauf _f_r_u_e_a_u_f_@_n_e_t_b_s_d_._o_r_g Castor Fu _c_a_s_t_o_r_@_n_e_t_b_s_d_._o_r_g Ichiro Fukuhara _i_c_h_i_r_o_@_n_e_t_b_s_d_._o_r_g Brian R. Gaeke _b_r_g_@_d_g_a_t_e_._o_r_g Thomas Gerner _t_h_o_m_a_s_@_n_e_t_b_s_d_._o_r_g Simon J. Gerraty _s_j_g_@_n_e_t_b_s_d_._o_r_g Justin Gibbs _g_i_b_b_s_@_n_e_t_b_s_d_._o_r_g Adam Glass _g_l_a_s_s_@_n_e_t_b_s_d_._o_r_g Michael Graff _e_x_p_l_o_r_e_r_@_n_e_t_b_s_d_._o_r_g Brad Grantham _g_r_a_n_t_h_a_m_@_t_e_n_o_n_._c_o_m Brian C. Grayson _b_g_r_a_y_s_o_n_@_n_e_t_b_s_d_._o_r_g Matthew Green _m_r_g_@_n_e_t_b_s_d_._o_r_g Juergen Hannken-Illjes _h_a_n_n_k_e_n_@_n_e_t_b_s_d_._o_r_g Charles M. Hannum _m_y_c_r_o_f_t_@_n_e_t_b_s_d_._o_r_g Eric Haszlakiewicz _e_r_h_@_n_e_t_b_s_d_._o_r_g John Hawkinson _j_h_a_w_k_@_n_e_t_b_s_d_._o_r_g HAYAKAWA Koichi _h_a_y_a_@_n_e_t_b_s_d_._o_r_g Ren'e Hexel _r_h_@_n_e_t_b_s_d_._o_r_g Michael L. Hitch _m_h_i_t_c_h_@_n_e_t_b_s_d_._o_r_g Christian E. Hopps _c_h_o_p_p_s_@_n_e_t_b_s_d_._o_r_g Ken Hornstein _k_e_n_h_@_n_e_t_b_s_d_._o_r_g Marc Horowitz _m_a_r_c_@_n_e_t_b_s_d_._o_r_g Nick Hudson _s_k_r_l_l_@_n_e_t_b_s_d_._o_r_g Martin Husemann _m_a_r_t_i_n_@_n_e_t_b_s_d_._o_r_g Dean Huxley _d_e_a_n_@_n_e_t_b_s_d_._o_r_g Bernardo Innocenti _b_e_r_n_i_e_@_n_e_t_b_s_d_._o_r_g 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 Chris Jones _c_j_o_n_e_s_@_n_e_t_b_s_d_._o_r_g Takahiro Kambe _t_a_c_a_@_n_e_t_b_s_d_._o_r_g Antti Kantee _p_o_o_k_a_@_n_e_t_b_s_d_._o_r_g Masanori Kanaoka _k_a_n_a_o_k_a_@_n_e_t_b_s_d_._o_r_g KAWAMOTO Yosihisa _k_a_w_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g Mario Kemper _m_a_g_i_c_k_@_n_e_t_b_s_d_._o_r_g Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u Thomas Klausner _w_i_z_@_n_e_t_b_s_d_._o_r_g Klaus Klein _k_l_e_i_n_k_@_n_e_t_b_s_d_._o_r_g Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g John Kohl _j_t_k_@_n_e_t_b_s_d_._o_r_g 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 Joel Lindholm _j_o_e_l_@_n_e_t_b_s_d_._o_r_g Mike Long _m_i_k_e_l_@_n_e_t_b_s_d_._o_r_g Warner Losh _i_m_p_@_n_e_t_b_s_d_._o_r_g Tomasz Luchowski _z_u_n_t_u_m_@_n_e_t_b_s_d_._o_r_g Federico Lupi _f_e_d_e_r_i_c_o_@_n_e_t_b_s_d_._o_r_g Brett Lymn _b_l_y_m_n_@_n_e_t_b_s_d_._o_r_g Paul Mackerras _p_a_u_l_u_s_@_n_e_t_b_s_d_._o_r_g MAEKAWA Masahide _g_e_h_e_n_n_a_@_n_e_t_b_s_d_._o_r_g David Maxwell _d_a_v_i_d_@_n_e_t_b_s_d_._o_r_g Dan McMahill _d_m_c_m_a_h_i_l_l_@_n_e_t_b_s_d_._o_r_g Gregory McGarry _g_m_c_g_a_r_r_y_@_n_e_t_b_s_d_._o_r_g 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 der Mouse _m_o_u_s_e_@_n_e_t_b_s_d_._o_r_g Joseph Myers _j_s_m_@_n_e_t_b_s_d_._o_r_g Ken Nakata _k_e_n_n_@_n_e_t_b_s_d_._o_r_g Bob Nestor _r_n_e_s_t_o_r_@_n_e_t_b_s_d_._o_r_g NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g Jesse Off _j_o_f_f_@_n_e_t_b_s_d_._o_r_g Tatoku Ogaito _t_a_c_h_a_@_n_e_t_b_s_d_._o_r_g Masaru Oki _o_k_i_@_n_e_t_b_s_d_._o_r_g Atsushi Onoe _o_n_o_e_@_n_e_t_b_s_d_._o_r_g Greg Oster _o_s_t_e_r_@_n_e_t_b_s_d_._o_r_g Herb Peyerl _h_p_e_y_e_r_l_@_n_e_t_b_s_d_._o_r_g Matthias Pfaller _m_a_t_t_h_i_a_s_@_n_e_t_b_s_d_._o_r_g 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 Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t Darren Reed _d_a_r_r_e_n_r_@_n_e_t_b_s_d_._o_r_g Michael Richardson _m_c_r_@_n_e_t_b_s_d_._o_r_g Tim Rightnour _g_a_r_b_l_e_d_@_n_e_t_b_s_d_._o_r_g Gordon Ross _g_w_r_@_n_e_t_b_s_d_._o_r_g Heiko W. Rupp _h_w_r_@_n_e_t_b_s_d_._o_r_g SAITOH Masanobu _m_s_a_i_t_o_h_@_n_e_t_b_s_d_._o_r_g Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g Wilfredo Sanchez _w_s_a_n_c_h_e_z_@_n_e_t_b_s_d_._o_r_g Ty Sarna _t_s_a_r_n_a_@_n_e_t_b_s_d_._o_r_g SATO Kazumi _s_a_t_o_@_n_e_t_b_s_d_._o_r_g Matthias Scheler _t_r_o_n_@_n_e_t_b_s_d_._o_r_g Karl Schilke (rAT) _r_a_t_@_n_e_t_b_s_d_._o_r_g Konrad Schroder _p_e_r_s_e_a_n_t_@_n_e_t_b_s_d_._o_r_g Reed Shadgett _d_e_n_t_@_n_e_t_b_s_d_._o_r_g Tim Shepard _s_h_e_p_@_n_e_t_b_s_d_._o_r_g Takao Shinohara _s_h_i_n_@_n_e_t_b_s_d_._o_r_g Takuya SHIOZAKI _t_s_h_i_o_z_a_k_@_n_e_t_b_s_d_._o_r_g Chuck Silvers _c_h_s_@_n_e_t_b_s_d_._o_r_g Thor Lancelot Simon _t_l_s_@_n_e_t_b_s_d_._o_r_g Jeff Smith _j_e_f_f_s_@_n_e_t_b_s_d_._o_r_g 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 Bill Squier _g_r_o_o_@_n_e_t_b_s_d_._o_r_g Bill Studenmund _w_r_s_t_u_d_e_n_@_n_e_t_b_s_d_._o_r_g Kevin Sullivan _s_u_l_l_i_v_a_n_@_n_e_t_b_s_d_._o_r_g SUNAGAWA Keiki _k_e_i_@_n_e_t_b_s_d_._o_r_g Kimmo Suominen _k_i_m_@_n_e_t_b_s_d_._o_r_g TAMURA Kent _k_e_n_t_@_n_e_t_b_s_d_._o_r_g Shin'ichiro TAYA _t_a_y_a_@_n_e_t_b_s_d_._o_r_g Matt Thomas _m_a_t_t_@_n_e_t_b_s_d_._o_r_g Christoph Toshok _t_o_s_h_o_k_@_n_e_t_b_s_d_._o_r_g UCHIYAMA Yasushi _u_c_h_@_n_e_t_b_s_d_._o_r_g Shuichiro URATA _u_r_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g Aymeric Vincent _a_y_m_e_r_i_c_@_n_e_t_b_s_d_._o_r_g Paul Vixie _v_i_x_i_e_@_n_e_t_b_s_d_._o_r_g Krister Walfridsson _k_r_i_s_t_e_r_w_@_n_e_t_b_s_d_._o_r_g Lex Wennmacher _w_e_n_n_m_a_c_h_@_n_e_t_b_s_d_._o_r_g Assar Westerlund _a_s_s_a_r_@_n_e_t_b_s_d_._o_r_g Todd Whitesel _t_o_d_d_p_w_@_n_e_t_b_s_d_._o_r_g Rob Windsor _w_i_n_d_s_o_r_@_n_e_t_b_s_d_._o_r_g Dan Winship _d_a_n_w_@_n_e_t_b_s_d_._o_r_g Jim Wise _j_w_i_s_e_@_n_e_t_b_s_d_._o_r_g Michael Wolfson _m_b_w_@_n_e_t_b_s_d_._o_r_g Colin Wood _e_n_d_e_r_@_n_e_t_b_s_d_._o_r_g YAMAMOTO Takashi _y_a_m_t_@_n_e_t_b_s_d_._o_r_g Yuji Yamano _y_y_a_m_a_n_o_@_n_e_t_b_s_d_._o_r_g Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g LLeeggaall MMuummbboo--JJuummbboo All product names mentioned herein are trademarks or registered trade- marks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by The NetBSD Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product in- cludes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Hannum. This product includes software devel- oped by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Al- istair G. Crooks. This product includes software developed by Amancio Hasty and Roger Hardiman. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Charles D. Cranor and Washington University. This product includes software devel- oped by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural Col- lege and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contribu- tors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This prod- uct includes software developed by Christopher G. Demetriou. This prod- uct includes software developed by Christos Zoulas. This product in- cludes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes soft- ware developed by Eric S. Hvozda. This product includes software devel- oped by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes soft- ware developed by HAYAKAWA Koichi. This product includes software devel- oped by Hellmuth Michaelis and Joerg Wunsch. This product includes soft- ware developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operat- ing systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software de- veloped by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software de- veloped by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This prod- uct includes software developed by Kenneth Stailey. This product in- cludes software developed by Leo Weppelman. This product includes soft- ware developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This prod- uct includes software developed by Michael L. Hitch. This product in- cludes software developed by Niels Provos. This product includes soft- ware developed by Paul Kranenburg. This product includes software devel- oped by Paul Mackerras. This product includes software developed by Pe- ter Galbavy. This product includes software developed by Philip A. Nel- son. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This prod- uct includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software de- veloped by SigmaSoft, Th. Lockert. This product includes software devel- oped by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes soft- ware developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software de- veloped by Tohru Nishimura for the NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software devel- oped by Winning Strategies, Inc. This product includes software devel- oped by Zembu Labs, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product in- cludes software developed by the Computer Systems Laboratory at the Uni- versity of Utah. This product includes software developed by the Univer- sity of Calgary Department of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes soft- ware developed for the Internet Software Consortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Pro- ject by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product in- cludes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software de- veloped for the NetBSD Project by Ted Lemon. This product includes soft- ware developed by LAN Media Corporation and its contributors. This prod- uct includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@mincom.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product in- cludes software developed by Reinoud Zandijk. This product includes software developed by the Alice Group. This product includes software developed by David Miller. TThhee EEnndd NetBSD September 10, 2001 41