INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NNAAMMEE IINNSSTTAALLLL - Installation procedure for NetBSD/macppc. CCOONNTTEENNTTSS About this Document............................................2 Quick install notes for the impatient..........................3 What is NetBSD?................................................4 Upgrade path to NetBSD 1.6.....................................4 Changes Between The NetBSD 1.5 and 1.6 Releases................5 Kernel......................................................5 Networking..................................................5 File system.................................................6 Security....................................................6 System administration and user tools........................7 Miscellaneous...............................................7 macppc specific.............................................8 The Future of NetBSD...........................................8 Sources of NetBSD..............................................9 NetBSD 1.6.1 Release Contents..................................9 NetBSD/macppc subdirectory structure.......................11 Binary distribution sets...................................11 NetBSD/macppc System Requirements and Supported Devices.......13 Supported models...........................................13 Unsupported models.........................................14 Supported devices..........................................15 Unsupported devices........................................17 Supported boot devices and media...........................17 Getting the NetBSD System on to Useful Media..................17 Preparing your System for NetBSD installation.................19 Prepare yourself...........................................19 Updating your BootROM......................................20 Getting to the Open Firmware Prompt on Newer Models........20 Getting to the Open Firmware Prompt on Apple Network.......21 Getting to the Open Firmware Prompt on Older Models........21 Older Open Firmware System Preparation.....................22 Getting to the Open Firmware Prompt (Recommended method using22 Getting to the Open Firmware Prompt (Harder method using...23 Getting to the Open Firmware Prompt (Without using MacOS)..24 Setting up pre-Open Firmware 3 to boot NetBSD..............25 Setting up Open Firmware 3 to boot NetBSD..................26 Available Boot Media.......................................27 Description of bootable media..............................28 Partitioning your hard drive for NetBSD....................29 Preparing the Bootable Media...............................31 Booting off an MS-DOS floppy............................32 Booting off the NetBSD install floppy...................32 Booting off an HFS or HFS+ partition....................33 Booting off the NetBSD/macppc CD-R image................33 Booting off an ISO9660 CD-ROM...........................33 Booting off a hybrid HFS/ISO9660 CD-ROM.................34 Booting over the ethernet...............................35 Booting the floppy image off a SCSI or IDE drive........39 Installing the NetBSD System..................................40 Open Firmware boot syntax..................................40 Examples of Open Firmware boot commands....................43 Booting off an MS-DOS floppy............................43 Booting off the NetBSD install floppy...................43 Booting off the NetBSD/macppc install CD-R..............44 Booting off the NetBSD/macppc install CD-R..............44 Booting off a home-made CD-ROM ISO9660 or Hybrid........44 Booting off an IDE or SCSI drive with 'partition zero'..45 Booting off an IDE or SCSI drive with an HFS partition..45 Example of a normal boot...................................46 Common Problems and Error Messages.........................46 Black screen............................................47 Grey screen with flashing question mark.................47 Information on your screen seems garbled or out of sync.47 DEFAULT CATCH!..........................................47 CLAIM failed............................................47 can't OPEN..............................................48 unrecognized Client Program formatstate not valid.......48 bad partition number, using 0no bootable HFS partition..48 TFTP timeout............................................48 Bootloader hangs before the copyright notice............48 Hang after configuring devices..........................49 Milestone..................................................49 Running the sysinst installation program...................49 Introduction............................................49 General.................................................49 Quick install...........................................49 Booting NetBSD..........................................51 Network configuration...................................51 Preparing a disk which will be used for Mac OS and NetBSD51 Installation drive selection and parameters.............52 Partitioning the disk...................................53 Preparing your hard disk................................53 Getting the distribution sets...........................54 Installation using ftp..................................54 Installation using NFS..................................54 Installation from CD-ROM................................54 Installation from an unmounted file system..............55 Installation from a local directory.....................55 Extracting the distribution sets........................55 Making the device nodes.................................55 Finalizing your installation............................56 Post installation steps.......................................56 Upgrading a previously-installed NetBSD System................58 Compatibility Issues With Previous NetBSD Releases............59 Issues affecting an upgrade from NetBSD 1.5................59 Issues affecting an upgrade from NetBSD 1.4 or prior.......60 Using online NetBSD documentation.............................61 Administrivia.................................................61 Thanks go to..................................................62 We are........................................................64 Legal Mumbo-Jumbo.............................................68 The End.......................................................71 DDEESSCCRRIIPPTTIIOONN AAbboouutt tthhiiss DDooccuummeenntt This document describes the installation procedure for NetBSD 1.6.1 on the _m_a_c_p_p_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.6.1 on a machine of the macppc architecture. ++oo Fetch the files necessary to boot your system. The files depend on what model you are using and how you plan to boot your machine. For systems with built-in floppy drives, fetch the bootloader _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f and the installation kernel _b_i_n_a_r_y_/_k_e_r_n_e_l_/_n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z. For systems without floppy drives, fetch the bootloader _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f and the installation kernel _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___M_D_._g_z. Alternatively, you can fetch the CD image, _m_a_c_p_p_c___b_o_o_t_a_b_l_e_._i_s_o or the boot floppy image _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_._f_s which include the bootloader and instal- lation kernel. Alternatively, you may netboot the installation ker- nel, 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 kernel from floppy, hard drive, or CD-ROM, the installation program can fetch these files for you (using e.g. ftp), if you have a network connection. There are several other methods to get the binary sets onto your machine. You will at a minimum need the following sets: _k_e_r_n_-_G_E_N_E_R_I_C_._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 If your mac has a floppy drive, copy _o_f_w_b_o_o_t_._x_c_f and _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z to an MS-DOS formatted floppy disk and rename _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z to _n_e_t_b_s_d_._g_z. Otherwise, drag _o_f_w_b_o_o_t_._x_c_f and _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z to your hard drive icon (the top level of the drive, not the desktop). If you are making a CD, burn it now. The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD. ++oo Determine your machine's model, quirks, and Open Firmware version from the NetBSD/macppc Model Support webpage. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll At present, NetBSD/macppc cannot exist on the same hard drive as Mac OS unless you partition your disk using a Mac OS partitioning utili- ty. Open Firmware versions prior to 3 cannot boot into NetBSD on a drive partitioned this way -- you must use the entire disk, parti- tioned with the installation tools. Open Firmware version 3 cannot boot into NetBSD on a drive partitioned with the installation tools, you must use a Mac OS partitioning utility and the ``RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss'' option in the installer (selecting the ``IInnssttaallll NNeettBBSSDD ttoo hhaarrdd ddiisskk'' or ``UUppggrraaddee NNeettBBSSDD oonn aa hhaarrdd ddiisskk'' options will render your drive unbootable). If you are unsure, you may want to read the section below on _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D ++oo For systems with Open Firmware versions prior to 3, you may need to use Apple's System Disk utility to enter Open Firmware and use your screen and keyboard. To enter Open Firmware, hold down the COMMAND- OPTION-O-F keys after the boot chime starts, but before it ends. En- tering Open Firmware versions prior to 3 is usually the most frus- trating part of installation -- you may want to read the section be- low on _O_l_d_e_r _O_p_e_n _F_i_r_m_w_a_r_e _S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n You should have the Open Firmware ``_0 _>'' prompt on your screen be- fore attempting to boot NetBSD/macppc. ++oo At the Open Firmware prompt, type the command to boot. To boot from a floppy, the command is ``bboooott ffdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..ggzz''. For the install kernel and bootloader on your hard drive (Open Firmware 3), the command is ``bboooott hhdd::\\,,ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz''. For boot CDs, the command is something like ``bboooott ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..mmaaccppppcc'' (for Open Firmware 3) or ``bboooott ssccssii--iinntt//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC'' (for earlier Open Firmware versions). You will need to use the correct case for OOFFWWBBOOOOTT..XXCCFF and NNEETTBBSSDD..MMAACCPPPPCC depending on how your version of Open Firmware interprets the ISO file system. You may need to replace ccdd with ssccssii//ssdd@@33, ssccssii--iinntt//ssdd@@33, ssccssii-- eexxtt//ssdd@@33, aattaa//aattaappii--ddiisskk, or some other device alias. You should al- so use the Open Firmware ddiirr command to confirm that the NetBSD/macppc kernel is called _N_E_T_B_S_D_._M_A_C_P_P_C. ++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 3000 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 fifty three different system architectures (ports), featuring seventeen machine architectures across eleven distinct CPU families, and is being ported to more. The NetBSD 1.6.1 release contains complete bi- nary releases for thirty eight different system architectures. (The fif- teen remaining are not fully supported at this time and are thus not part of the binary distribution. For information on them, please see the NetBSD web site at hhttttpp::////wwwwww..nneettbbssdd..oorrgg//.) NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, the X Window System, firewall software and numerous other tools, all accompanied by full source code. NetBSD is a creation of the members of the Internet community. Without the unique cooperation and coordination the net makes possible, it's likely that NetBSD wouldn't exist. UUppggrraaddee ppaatthh ttoo NNeettBBSSDD 11..66 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.6. NetBSD 1.6 is an upgrade of NetBSD 1.5.3 and earlier major and patch re- leases of NetBSD. The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from _a_f_t_e_r the point where the release cycle for 1.6 was started are designated by ver- sion identifiers such as 1.6A, 1.6B, etc. These identifiers do not des- ignate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.6 can _n_o_t be used to upgrade a system running one of those intermediate development versions. Trying to use the NetBSD 1.6 kernel on such a system _w_i_l_l probably result in problems. Please also note that it is not possible to do a direct ``version'' com- parison between any of the intermediate development versions mentioned above and 1.6 to determine if a given feature is present or absent in 1.6. The development of 1.6 and the subsequent ``point'' releases is done on a separate branch in the CVS repository. The branch was created when the release cycle for 1.6 was started, and during the release cycle of 1.6 and its patch releases selected fixes and enhancements have been imported from the main development trunk. CChhaannggeess BBeettwweeeenn TThhee NNeettBBSSDD 11..55 aanndd 11..66 RReelleeaasseess The NetBSD 1.6 release provides numerous significant functional enhance- ments, including support for many new devices, integration of hundreds of bug fixes, new and updated kernel subsystems, and many user-land enhance- ments. The result of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize over eighteen months of develop- ment that went into the NetBSD 1.6.1 release. Some highlights include: _K_e_r_n_e_l ++oo Ports to new platforms including: algor, dreamcast, evbarm, hpcarm, hpcsh, newsmips, sandpoint, sgimips, sun2, and walnut. ++oo Unified Buffer Cache (UBC) removes size restriction of the file sys- tem's buffer cache to use all available RAM (if not otherwise used!) and improves overall system performance. ++oo Round-robin page colouring implemented for various ports for better cache utilisation, more deterministic run-time behaviour, and faster program execution. ++oo A rewritten SCSI middle layer to provide a cleaner interface between the different kernel layers, including a kernel thread to handle er- ror recovery outside of the interrupt context. See scsipi(9). ++oo A new pipe implementation with significantly higher performance due to lower overheads, which uses the UVM Page Loan facility. ++oo New boot loader flags --vv (_b_o_o_t_v_e_r_b_o_s_e) and --qq (_b_o_o_t_q_u_i_e_t), to be used by kernel code to optionally print information during boot. ++oo An in-kernel boot time device configuration manager userconf(4), ac- tivated with the --cc boot loader flag. ++oo A work-in-progress snapshot of ACPI support, based on the 20010831 snapshot of the Intel ACPICA reference implementation. ++oo USB 2.0 support, in the form of a preliminary driver for the ehci(4) host controller. ++oo Basic kernel support for IrDA in the form of the irframe(4) IrDA frame level driver. Serial dongles and the oboe(4) driver are cur- rently supported. ++oo Kernel configuration files can be embedded into the kernel for later retrieval. Refer to INCLUDE_CONFIG_FILE in options(4) for more in- formation. ++oo Many more kernel tunable variables added to sysctl(8). ++oo Linux binary emulation has been greatly improved, and now supports Linux kernel version 2.4.18. _N_e_t_w_o_r_k_i_n_g ++oo Hardware assisted IPv4 TCP and UDP checksumming and caching of the IPv6 TCP pseudo header. Support for checksum offloading on the DP83820 Gigabit Ethernet, 3Com 3c90xB, 3Com 3c90xC, and Alteon Tigon/Tigon2 Gigabit Ethernet cards. ++oo Zero-Copy for TCP and UDP transmit path achieved through page loaning code for ssoosseenndd(). ++oo In-kernel ISDN support, from the ISDN4BSD project. ++oo 802.1Q VLAN (virtual LAN) support. See vlan(4). ++oo IPFilter now supports IPv6 filtering. ++oo ndbootd(8) added; used to netboot NetBSD/sun2 machines. ++oo racoon(8) added; IKE key management daemon for IPsec key negotiation, from the KAME project. ++oo WEP encryption supported in ifconfig(8) and awi(4) driver. ++oo wi(4) and wiconfig(8) now support scanning for access points, and de- faults to BSS instead of ad-hoc mode. ++oo Bridging support; currently only for ethernet. See bridge(4). ++oo In-kernel PPP over Ethernet (PPPoE) - RFC 2516, with much lower over- head than user-land PPPoE clients. See pppoe(4). ++oo ifwatchd(8) added; invokes up-script and down-script when a network interface goes up and down. Used by pppoe(4). _F_i_l_e _s_y_s_t_e_m ++oo Enhanced stability of LFS version 2, the BSD log-structured file sys- tem. ++oo dump(8), dumpfs(8), fsck_ffs(8), fsirand(8), newfs(8), and tunefs(8) support a --FF option to manipulate file system images in regular files. ++oo makefs(8) added; creates file system images from a directory tree. (Currently ffs only.) ++oo Enhanced ffffss__ddiirrpprreeff() by Grigoriy Orlov, which noticeably improves performance on FFS file systems when creating directories, and subse- quently manipulating them. ++oo Fixes for free block tracking and directory block allocation in FFS softdeps. ++oo Correctly support FFS file systems with a large number of cylinder groups. ++oo Fix the endian independant FFS (FFS_EI) support. ++oo newfs(8) calculates default block size from the file system size, and uses the largest possible cylinders/group (cpg) value if --cc isn't given. ++oo dpti(4) driver added; an implementation of the DPT/Adaptec SCSI/I2O RAID management interface. Allows the use of the Linux versions of ddppttmmggrr, rraaiidduuttiill, ddpptteelloogg, (etc). ++oo Support for Windows 2000 `NTFS' (NTFS5). ++oo Tagged queueing support for SCSI drivers based on the ncr53c9x con- troller. _S_e_c_u_r_i_t_y ++oo Addition of a chroot(8) hierarchy for services including named(8), ntpd(8), and sshd(8). ++oo Additional passwd(5) ciphers: MD5, and DES with more encryption rounds. See passwd.conf(5). ++oo Several more code audits were performed. ++oo _/_e_t_c_/_s_e_c_u_r_i_t_y performs many more checks and is far more flexible in how it monitors changes. See security.conf(5). _S_y_s_t_e_m _a_d_m_i_n_i_s_t_r_a_t_i_o_n _a_n_d _u_s_e_r _t_o_o_l_s ++oo sushi(8) added; a menu based system administration tool. ++oo pgrep(1) and pkill(1) added; find or signal processes by name or oth- er attributes. ++oo System upgrades are made easier through the etcupdate(8) script which helps updating the _/_e_t_c config files interactively, and the _/_e_t_c_/_p_o_s_t_i_n_s_t_a_l_l script which is provided to check for or fix config- uration changes that have occurred in NetBSD. ++oo stat(1) added; a user interface to the information returned by the stat(2) system call. ++oo BSD sort(1) replaces GNU sort(1). ++oo The ``stop'' operation for rc.d(8) scripts waits until the service terminates before returning. This improves the reliability of ``restart'' operations as well. ++oo Swap devices can be removed at system shutdown by enabling swapoff in rc.conf(5). ++oo An optional watchdog timer which will terminate rc.shutdown(8) after the number of seconds provided in rcshutdown_timeout from rc.conf(5). _M_i_s_c_e_l_l_a_n_e_o_u_s ++oo Support for multibyte LC_CTYPE locales has been integrated from the Citrus project. Many Chinese, Japanese, Korean, and other encodings are now available. ++oo Full support for cross-compilation of the base system, even as a non- root user! _s_r_c_/_b_u_i_l_d_._s_h is available for doing arbitrary cross- builds; see _s_r_c_/_B_U_I_L_D_I_N_G for more information. At least 38 ports for the NetBSD 1.6.1 release were cross-built on a NetBSD/i386 system us- ing this mechanism. ++oo Migrated the following CPU platforms to ELF: arm, and m68k (including amiga, hp300, mac68k, mvme68k, sun2, and x68k). ++oo Updates of most third party packages that are shipped in the base system to the following latest stable releases: -- amd 6.0.6 -- BIND 8.3.3 -- binutils 2.11.2 -- bzip2 1.0.2 -- cvs 1.11 -- dhcp 3.0.1rc9 -- file 3.38 -- gcc 2.95.3 -- groff 1.16.1 -- Heimdal 0.4e -- IPfilter 3.4.27 -- kerberos4 1.1 -- ksh from pdksh 5.2.14p2 -- less 374 -- nvi 1.79 -- OpenSSH 3.4 -- OpenSSL 0.9.6g -- Postfix 1.1.11 -- ppp 2.4.0 -- routed 2.24 -- sendmail 8.11.6 -- tcpdump 3.7.1 ++oo Many new packages in the _p_k_g_s_r_c system, including the latest open source desktop KDE3, OpenOffice, perl, Apache and many more. At the time of writing, there are over 3000 third party packages available in pkgsrc. ++oo Added AGP GART driver agp(4) for faster access to graphics boards. ++oo init(8) will create an mfs (memory based file system) _/_d_e_v if _/_d_e_v_/_c_o_n_s_o_l_e is missing. ++oo vmstat(8) displays kernel hash statistics with --HH and --hh _h_a_s_h. ++oo wscons(4) supports blanking of VGA consoles. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. _m_a_c_p_p_c _s_p_e_c_i_f_i_c This is the third major release of NetBSD for the macppc platform, in- cluding the Apple iBook, iMac, PowerMacintosh, and PowerBook models, as well as clones. As is usual between releases, the macppc port has had many improvements made to it -- too many to detail all of them here. Numerous new drivers have been added. See the supported hardware list for details. Some (but not all!) notable macppc-specific improvements include: ++oo Support for the some of the latest models. ++oo Support for the built-in AirPort/AirMac interface. ++oo Experimental support for the built-in audio on most models. NetBSD 1.6.1 on macppc is, as usual, also fully backward compatible with old NetBSD/macppc 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..66..11 RReelleeaassee CCoonntteennttss The root directory of the NetBSD 1.6.1 release is organized as follows: _._._._/_N_e_t_B_S_D_-_1_._6_._1_/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.6.1 distribution. README.files README describing the distribution's contents. TODO NetBSD 's todo list (also somewhat incomplete and out of date). _p_a_t_c_h_e_s_/ Post-release source code patches. _s_o_u_r_c_e_/ Source distribution sets; see below. In addition to the files and directories listed above, there is one di- rectory per architecture, for each of the architectures for which NetBSD 1.6.1 has a binary distribution. There are also _R_E_A_D_M_E_._e_x_p_o_r_t_- _c_o_n_t_r_o_l files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution that may be subject to export regulations of the United States, e.g. code under _s_r_c_/_c_r_y_p_t_o and _s_r_c_/_s_y_s_/_c_r_y_p_t_o. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The source distribution sets can be found in subdirectories of the _s_o_u_r_c_e subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: ggnnuussrrcc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. _5_5 _M_B _g_z_i_p_p_e_d_, _2_4_7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ppkkggssrrcc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. _1_2 _M_B _g_z_i_p_p_e_d_, _9_4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d sshhaarreessrrcc This set contains the ``share'' sources, which include the sources for the man pages not associated with any particular program; the sources for the typesettable document set; the dictionaries; and more. _4 _M_B _g_z_i_p_p_e_d_, _1_6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssrrcc This set contains all of the base NetBSD 1.6.1 sources which are not in ggnnuussrrcc, sshhaarreessrrcc, or ssyyssssrrcc. _2_7 _M_B _g_z_i_p_p_e_d_, _1_3_6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ssyyssssrrcc This set contains the sources to the NetBSD 1.6.1 kernel for all architectures; config(8); and dbsym(8). _2_2 _M_B _g_z_i_p_p_e_d_, _1_1_4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxssrrcc This set contains the sources to the X Window System. _7_8 _M_B _g_z_i_p_p_e_d_, _3_9_4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d All the above source sets are located in the _s_o_u_r_c_e_/_s_e_t_s subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the ppkkggssrrcc set, which is traditionally unpacked into _/_u_s_r_/_p_k_g_s_r_c, all sets may be unpacked into _/_u_s_r_/_s_r_c with the command: # (( ccdd // ;; ttaarr --zzxxppff -- )) << sseett__nnaammee..ttggzz The _s_e_t_s_/_S_p_l_i_t_/ subdirectory contains split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are named _s_e_t___n_a_m_e_._x_x where _s_e_t___n_a_m_e is the distribution set name, and _x_x is the sequence number of the file, starting with ``aa'' for the first file in the distribution set, then ``ab'' for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) The split distributions may be reassembled and extracted with ccaatt as fol- lows: # ccaatt sseett__nnaammee..???? || (( ccdd // ;; ttaarr --zzxxppff -- )) In each of the source distribution set directories, there are files which contain the checksums of the files in the directory: BSDSUM Historic BSD checksums for the various files in that di- rectory, in the format produced by the command: cckkssuumm --oo 11 _f_i_l_e. CKSUM POSIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm _f_i_l_e. MD5 MD5 digests for the various files in that directory, in the format produced by the command: cckkssuumm --mm _f_i_l_e. SYSVSUM Historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cckkssuumm --oo 22 _f_i_l_e. The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest pos- sible range of system can check the integrity of the release files. _N_e_t_B_S_D_/_m_a_c_p_p_c _s_u_b_d_i_r_e_c_t_o_r_y _s_t_r_u_c_t_u_r_e The macppc-specific portion of the NetBSD 1.6.1 release is found in the _m_a_c_p_p_c subdirectory of the distribution: _._._._/_N_e_t_B_S_D_-_1_._6_._1_/_m_a_c_p_p_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 re- lease. _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z A gzipped NetBSD kernel containing code for everything supported in this re- lease. It also has a RAM-disk in- staller. This is the kernel you should use when you want to install via from an HFS partition on Open Firmware 3 systems, netboot, or from a CD-R. _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z A gzipped NetBSD kernelcontaining code only for Open Firmware 1.0.5, 1.1.22, and 2.4 systems (i.e. those that have floppy drives). It has a RAM-disk in- staller. This is the kernel you should use when you want to install on one of these systems from a floppy disk. _s_e_t_s_/ macppc binary distribution sets; see below. _i_n_s_t_a_l_l_a_t_i_o_n_/ _f_l_o_p_p_y_/_b_o_o_t_._f_s macppc boot and installation floppy image. Only usable on models that ship with a floppy drive (pre-Open Firmware 3); see below. _o_f_w_b_o_o_t_._x_c_f macppc bootloader; see below. _B_i_n_a_r_y _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD macppc binary distribution sets contain the binaries which comprise the NetBSD 1.6.1 release for the macppc. There are eight binary distribution sets. The binary distribution sets can be found in the _m_a_c_p_p_c_/_b_i_n_a_r_y_/_s_e_t_s subdirectory of the NetBSD 1.6.1 distribution tree, and are as follows: bbaassee The NetBSD 1.6.1 macppc bbaassee binary distribution. You _m_u_s_t in- stall this distribution set. It contains the base NetBSD util- ities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. _2_0 _M_B _g_z_i_p_p_e_d_, _5_3 _M_B _u_n_c_o_m_p_r_e_s_s_e_d 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_7 _M_B _g_z_i_p_p_e_d_, _6_4 _M_B _u_n_c_o_m_p_r_e_s_s_e_d eettcc This distribution set contains the system configuration files that reside in _/_e_t_c and in several other places. This set _m_u_s_t be installed if you are installing the system from scratch, but should _n_o_t be used if you are upgrading. _1 _M_B _g_z_i_p_p_e_d_, _1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d ggaammeess This set includes the games and their manual pages. _3 _M_B _g_z_i_p_p_e_d_, _7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d kkeerrnn--GGEENNEERRIICC This set contains a NetBSD/macppc 1.6.1 GENERIC kernel, named _/_n_e_t_b_s_d. You _m_u_s_t install this distribution set. _2 _M_B _g_z_i_p_p_e_d_, _5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d mmaann This set includes all of the manual pages for the binaries and other software contained in the bbaassee set. Note that it does not include any of the manual pages that are included in the other sets. _7 _M_B _g_z_i_p_p_e_d_, _2_7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d mmiisscc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from _/_u_s_r_/_s_h_a_r_e. _3 _M_B _g_z_i_p_p_e_d_, _8 _M_B _u_n_c_o_m_p_r_e_s_s_e_d tteexxtt This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. _2 _M_B _g_z_i_p_p_e_d_, _6 _M_B _u_n_c_o_m_p_r_e_s_s_e_d NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window System are distributed with NetBSD. The sets are: xxbbaassee The basic files needed for a complete X client environment. This does not include the X servers. _3 _M_B _g_z_i_p_p_e_d_, _9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoommpp The extra libraries and include files needed to compile X source code. _2 _M_B _g_z_i_p_p_e_d_, _9 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxccoonnttrriibb Programs that were contributed to X. _1 _M_B _g_z_i_p_p_e_d_, _1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxffoonntt Fonts needed by X. _6 _M_B _g_z_i_p_p_e_d_, _7 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxmmiisscc Miscellaneous X programs. _1 _M_B _g_z_i_p_p_e_d_, _1 _M_B _u_n_c_o_m_p_r_e_s_s_e_d xxsseerrvveerr The Xmacppc server which supports 256 colors with man pages. _2 _M_B _g_z_i_p_p_e_d_, _5 _M_B _u_n_c_o_m_p_r_e_s_s_e_d The macppc binary distribution sets are distributed as gzipped tar files named with the extension ..ttggzz, e.g. _b_a_s_e_._t_g_z. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted _b_e_l_o_w _t_h_e _c_u_r_r_e_n_t _d_i_r_e_c_t_o_r_y. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the ttaarr --xxppff command from the root directory ( _/ ) of your system. This utility is used only in a Traditional method in- stallation. _N_o_t_e_: Each directory in the macppc binary distribution also has its own checksum files, just as the source distribution does. NNeettBBSSDD//mmaaccppppcc SSyysstteemm RReeqquuiirreemmeennttss aanndd SSuuppppoorrtteedd DDeevviicceess Currently, NetBSD/macppc requires the use of Open Firmware to boot. Open Firmware is a command environment using the FORTH language which the NetBSD kernel uses to gether information about your system, and to con- trol some of your devices. It is part of the boot ROMs in most PowerPC- based Macintosh systems. Until late 1996, Apple never intended to use Open Firmware for anything other than internal debugging and hardware support. It was not intended to be used to boot an operating system. This is why earlier machines have so much trouble with Open Firmware. This also means that PowerMacs and clones that lack Open Firmware cannot boot NetBSD on the macppc platform. Most machines introduced by Apple and the clone-makers after August 17, 1995 have Open Firmware and are supported. Apple made several revisions of this Open Firmware environment, and each has various quirks and problems that we must work around. The single hardest step of installing NetBSD/macppc is to set up Open Firmware prop- erly. Open Firmware versions 1.0.5 and 2.0.x act similarly and the same set of instructions applies to them Open Firmware version 2.4 is slightly different with regards to booting. Open Firmware version 3 is altogether different. At present, NetBSD/macppc does not support the PPC 601 microprocessor, which means that the PowerMacintosh 7200 and 7500 models are not support- ed. The PowerMacintosh 7500 may be upgraded to a PPC 604, G3 or G4 mi- croprocessor via a daughtercard replacement, in which case NetBSD will run on this system. The minimal configuration requires 16 MB of RAM and ~80 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 16 MB of RAM is very slow. Note that until you have around 32 MB of RAM, getting more RAM is more important than getting a faster CPU. _S_u_p_p_o_r_t_e_d _m_o_d_e_l_s Find your model from the list below and take note of its Open Firmware version: _O_p_e_n _F_i_r_m_w_a_r_e _1_._0_._5 ++oo Apple PowerMacintosh (7300, 7500 (with CPU upgrade), 7600, 8500, 8600, 9500, and 9600) ++oo Apple Workgroup Server 8550 ++oo Power Computing (PowerBase, PowerCenter, PowerCenter Pro, PowerCurve, PowerTower, PowerTower Pro, and PowerWave) ++oo UMAX (J700, S900) _O_p_e_n _F_i_r_m_w_a_r_e _1_._1_._2_2 ++oo Apple Network Server (500 and 700) _N_o_t_e_: Users have reported that the NetBSD kernel does not work well with the on-board MACE-based ethernet (the one that requires an Apple AAUI dongle). If your system does not have the Apple PCI Ethernet Card, you may need to purchase and install another ether- net card in your Apple Network Server. _O_p_e_n _F_i_r_m_w_a_r_e _2_._0_._x ++oo Apple PowerBook (2400, 3400, G3, and G3 Series) ++oo Apple PowerMacintosh/Performa (4400, 54xx, 5500, 6300/160, 6360, 6400, and 6500) ++oo Apple PowerMacintosh (G3 ``Beige'' models with ATI RageII+: Desktop, Mini Tower, and All-in-One) ++oo APS Tech (M*Power 604e/200) ++oo Motorola StarMax (3000, 4000, 5000, and 5500) ++oo UMAX (Apus 2000, Apus 3000, C500, and C600) _O_p_e_n _F_i_r_m_w_a_r_e _2_._4 ++oo Apple PowerMacintosh (G3 ``Beige'' models with ATI Rage Pro: Desktop, Mini Tower, and All-in-One) _O_p_e_n _F_i_r_m_w_a_r_e _3 ++oo Apple original iBook, iBook SE, iBook (Dual USB), iBook (Late 2001), and iBook (Summer 2002) ++oo Apple iMac; Bondi Blue (Rev A and Rev B, 233 MHz), 5 Fla- vors (Rev C and Rev D, 266 MHz and 333 MHz), iMac (Slot Loading), iMac (Summer 2000), iMac (Early 2001), and iMac (Summer 2001) ++oo Apple original eMac ++oo Apple PowerBook (G3 Series (bronze keyboard) and G3 (FireWire)) ++oo Apple PowerBook G4 (Titanium), PowerBook G4 (Gigabit Ether- net), and PowerBook G4 (DVI) ++oo Apple PowerMacintosh G3 (Blue and White) ++oo Apple PowerMacintosh (G4 (PCI), G4 (AGP), G4 (Gigabit Eth- ernet), G4 (Digital Audio), G4 (Quicksilver), G4 (Quicksil- ver 2002), and G4 Cube) ++oo Apple Xserve _N_o_t_e_: Some iMac (Bondi Blue) and PowerMacintosh G3 (Blue and White) machines have keyboard problems. There is a workaround for the PowerMacintosh described in the NetBSD/macppc FAQ. There is no known workaround for the iMac machines encountering this problem. See hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##uussbb-- kkeeyybbooaarrdd--pprroobblleemmss _U_n_s_u_p_p_o_r_t_e_d _m_o_d_e_l_s ++oo Systems with Open Firmware, but using a PPC 601 microprocessor (PowerMacintosh 7200 and 7500 (without CPU upgrade)) ++oo Systems with a PowerPC microprocessor, but lacking Open Firmware -- Apple PowerBook (1400, 2300, and 5300) -- Apple PowerMacintosh/Performa (52xx, 53xx, 62xx, and 63xx (except 6300/160 and 6360 which are supported)) -- Apple PowerMacintosh/Performa (61xx, 71xx, and 81xx) -- PowerComputing (Power 100 and Power 120) ++oo Systems with broken Open Firmware (Twentieth Anniversary Macin- tosh) ++oo Systems with a Motorola 68k microprocessor (these systems are supported by NetBSD/mac68k) ++oo Systems upgraded from any of the above (unless the motherboard is replaced as part of the upgrade) ++oo Systems released in the second half of 2002 and later (future releases of NetBSD/macppc will support these systems) ++oo Systems released before the second half of 2002, but not listed above. These models might work, but have not been tested as of the release of NetBSD 1.6.1. _S_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo CPU upgrades -- Most CPU upgrades are supported. Some older models will not automatically enable the L2 cache on a G3 or G4 proces- sor. See the FAQ entry hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ccppuu-- uuppggrraaddee ++oo Ethernet -- On-board 79C950-based MACE Ethernet interface (_m_c_0) -- On-board bmac Ethernet interface (_b_m_0) -- On-board gmac Ethernet interface (_g_m_0) -- Apple PCI Ethernet Card (option for Apple Network Server) (_d_e) -- Asante Mac 10/100 PCI Rev A, part number 09-00169-01 (_d_e) -- Farallon Fast EtherTX 10/100, part number PN996L-TX (_d_e) -- SMC Etherpower II (9432TX) (_e_p_i_c) -- SMC 83c170 (_e_p_i_c) -- 3Com 3c905 (_e_x) -- Intel EtherExpress PRO/10+ PCI LAN Adapter (_f_x_p) -- RealTek 8029 Ethernet (_n_e) -- VIA Technologies VT86C926 (_n_e) -- D-Link DFE-530TX+ (_r_t_k) -- RealTek 8139 (_r_t_k) -- Netgear FA-311 (_s_i_p) -- Lite-On PNIC (_t_l_p) -- D-Link DFE-530TX (_v_r) -- Many other PCI and Cardbus Ethernet interfaces, such as Tulip-compatible (_d_e and _t_l_p), 3Com (_e_p), SMC (_e_p_i_c), Intel (_f_x_p), NE2000-compatible (_n_e), and RealTek (_r_t_k) -- Many USB Ethernet interfaces (_a_u_e, _c_u_e, and _k_u_e) ++oo Wireless -- On-board AirPort or AirMac 802.11b (_w_i) -- AT&T/Lucent WaveLan IEEE PCMCIA card (_w_i) ++oo SCSI -- On-board NCR 53c94 SCSI controller (_e_s_p) -- On-board MESH SCSI controller (_m_e_s_h) -- Adaptec PCI controllers 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160 and AIC-78xx (_a_h_c) _N_o_t_e_: The 294x models are not bootable in Open Firmware, even though they can boot MacOS . -- AdvanSys 1200[A,B], 9xx[U,UA] SCSI controller (_a_d_v) -- AMD 53c974 (_p_c_s_c_p) -- Apple 53c875 Ultra Wide SCSI (shipped in some Beige G3 mod- els) (_n_c_r or _s_i_o_p) _N_o_t_e_: This card may need a firmware update to boot NetBSD. Use the Mac OS X SCSI Card Updater from hhttttpp::////ddooccss..iinnffoo..aappppllee..ccoomm//aarrttiiccllee..hhttmmll??aarrttnnuumm==2255117766 -- NCR/Symbios 53C8xx (_s_i_o_p or _e_s_i_o_p) -- Many other PCI SCSI controllers should work, but no one has tried them -- Most SCSI disk/tape/CD-ROM devices should work ++oo IDE -- On-board IDE controlers -- Promise Ultra66 (_p_c_i_i_d_e) (this, and other PC-based cards are not bootable on macppc) -- Acard ATP-850/860 based IDE controlers (_p_c_i_i_d_e) (including the Acard AEC-6210/6260 and the Sonnet Tempo ATA/66 cards) -- Some other PCI IDE controllers should work, although no one has had much success -- Most IDE disk/CD-ROM/ATAPI devices should work ++oo Input devices -- Most ADB keyboards, mice, trackballs, and trackpads -- Most USB keyboards, mice, trackballs, and trackpads -- Most PS/2 keyboards, mice, and trackballs (middle button on 3-button mice may not work) ++oo Video -- On-board video on most models (_o_f_b) _N_o_t_e_: Several models have been reported to not work with NetBSD if the on-board video is in use, such as the Performa 54xx, 6360, 6400, PowerComputing Power- Center and PowerTower, and UMAX C600 and Apus 3000. Also, the video card that shipped with the PowerMac- intosh 9500/150, 9500/180, and 9500/200 systems is reported to have the same problem. -- PCI frame buffers which have Open Firmware support (ATI, IMS, Matrox, and NVIDIA have several models which work) ++oo Audio -- On-board audio on most models (_a_w_a_c_s) _N_o_t_e_: This driver has only recently been introduced and is considered ``experimental'' meaning that it may cause your system to crash and/or is lacking some features you may expect. Due to interrupt conflicts with some G4 models, this driver is disabled by de- fault and you will need to build a kernel with it enabled. -- USB audio devices (_u_a_u_d_i_o) -- PCI audio cards, although only the Ensoniq AudioPCI (_e_a_p) has been thoroughly tested ++oo Serial ports -- On-board serial ports (the modem and printer ports) (_t_t_y_a and _t_t_y_b) _t_t_y_a is the mini-DIN 8 serial port with the `Modem' icon, and _t_t_y_b is has the `Printer' icon. Some models with in- ternal modems have the serial port with the `Modem' icon covered over, and the modem is _t_t_y_a. _N_o_t_e_: The on-board serial ports can be used for console (38400 bps, 8 bits, no parity, 1 stop bit, no hand- shaking), although many users have reported problems trying to run ppp or other high speed serial appli- cations -- The Gee Three Stealth Serial Port, possibly the Griffin Technology gPort _N_o_t_e_: These serial ports can be used for console (57600 bps, 8 bits, no parity, 1 stop bit, no handshaking). Use (_s_c_c_a) for the Open Firmware `input-device' and `output-device' variables. -- Some USB, PCI, and Cardbus serial ports should work, but no one has tried them ++oo USB devices -- Most MI USB devices should work (such as disks, printers, input devices, SCSI adapters, and ethernet interfaces) hhttttpp::////wwwwww..nneettbbssdd..oorrgg//HHaarrddwwaarree//uussbb..hhttmmll ++oo PCMCIA and Cardbus cards -- Most MI PCMCIA and Cardbus cards should work, although very few have been tested with NetBSD/macppc hhttttpp::////wwwwww..nneettbbssdd..oorrgg//HHaarrddwwaarree//ccaarrddbbuuss..hhttmmll hhttttpp::////wwwwww..nneettbbssdd..oorrgg//HHaarrddwwaarree//ppccmmcciiaa..hhttmmll ++oo PCI cards -- Most MI PCI cards should work, although very few have been tested with NetBSD/macppc hhttttpp::////wwwwww..nneettbbssdd..oorrgg//HHaarrddwwaarree//ppccii..hhttmmll _N_o_t_e_: While the NetBSD kernel may support the various Cardbus, PCI, PCMCIA, and USB devices you may have, Open Firmware does _n_o_t unless it has a specific Open Firmware ROM. This means you cannot boot from these devices. Some Adaptec SCSI controllers have bootable Open Firmware ROMs. _U_n_s_u_p_p_o_r_t_e_d _d_e_v_i_c_e_s ++oo Floppy disk _N_o_t_e_: Though NetBSD/macppc can boot from a floppy, there is no kernel support yet ++oo FireWire (IEEE 1394) ++oo Advanced power management (cannot put system to `sleep') ++oo Multiple processors _N_o_t_e_: Although NetBSD/macppc can boot with more than one pro- cessor present, it will not use the additional CPUs ++oo On-board video capture _S_u_p_p_o_r_t_e_d _b_o_o_t _d_e_v_i_c_e_s _a_n_d _m_e_d_i_a Each version of Open Firmware supports different devices and media that you may boot from. We define the terms ``bootable media'' as the media (hard drive, floppy, CD-R, ethernet) that will be used to bootstrap your macppc system into NetBSD, and ``distribution sets'' or ``distribution media'' as the media (hard drive, CD-R, ethernet) that contains the files that will be installed to generate a working NetBSD system onto your des- tination media. Go to the NetBSD/macppc Model Support webpage and look up your system. Take note of the comments about your model and keep these in mind during the rest of this installation procedure. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll GGeettttiinngg tthhee NNeettBBSSDD SSyysstteemm oonn ttoo UUsseeffuull MMeeddiiaa You should wait to decide where to put the NetBSD distribution sets until you have figured out how you are going to boot your system. Refer back to this section after you have done so. _N_o_t_e_: Some Mac OS ffttpp clients default to downloading files in `ASCII' mode. This will render the NetBSD files useless. Make sure to set your ftp program to download in `binary' mode. Installation is supported from several media types, including: ++oo CD-ROM ++oo FTP ++oo Remote NFS partition The steps necessary to prepare the distribution sets for installation de- pend upon which installation medium you choose. The steps for the vari- ous media are outlined below. _C_D_-_R_O_M Find out where the distribution set files are on the CD- ROM. Proceed to the instruction on installation. _F_T_P The preparations for this installation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the nu- meric IP address of the router closest to the NetBSD ma- chine. Finally, you need to know the numeric IP address of the NetBSD machine itself. If you don't have access to a functioning nameserver during installation, the IP ad- dress of ffttpp..nneettbbssdd..oorrgg is 204.152.184.75 (as of June, 2002). Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. _N_F_S Place the NetBSD distribution sets you wish to install in- to a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the _/_e_t_c_/_e_x_p_o_r_t_s file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine it- self. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on up- grading. _N_o_t_e_: This method of installation is recommended only for those already familiar with using BSD network con- figuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. PPrreeppaarriinngg yyoouurr SSyysstteemm ffoorr NNeettBBSSDD iinnssttaallllaattiioonn _P_r_e_p_a_r_e _y_o_u_r_s_e_l_f Take a deep breath. Good. Now, make sure you are reading the PDF (if available), PostScript, or HTML version of this document, as the _._t_x_t and _._m_o_r_e versions lack im- portant formatting information that will prevent you from following the twisted path you must follow. OK, good. Now, print out this document. While it's printing, get some coffee, relax a bit, and mentally prepare yourself for something that promises to be confusing, frustrating, and annoying. If you assume the worst, you'll be pleasantly surprised when everything works easier than you expected. Also, forget everything you've been told about installing NetBSD/macppc. That's right, flush your knowledge cache -- some of it is almost certainly dirty. Some of this document assumes familiarity with MacOS, e.g. how to down- load BinHex files and extract things with StuffIt Expander. If you've never heard of those terms before, it is possible to install NetBSD/macppc without booting or knowing how to use MacOS, but depending on your model it may be almost as painful as learning a little MacOS. See the FAQ for more help: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##mmaaccooss--nneewwbbiiee It's done printing? Fine, now get a dark writing implement. The recommended installation procedure is as follows: 1. Go to the NetBSD/macppc model support page and look up your model information and issues (I can't stress this enough times). hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll 2. Spend about 15 minutes and read through this document from this point onward. While you're reading, use the writing implement to cross out the sections that do not apply to your model (or hilight the sections that do depending on your preferences). 3. Now spend another 5 minutes and re-read this document, and mentally piece together how you think you'll be installing onto your machine. It may help to take a blank piece of paper and write out an outline of the procedure you think you'll be going through. 4. Now create your bootable media and media for the distribution sets. 5. Prepare your machine, depending on the instructions for your model (for example: partition your drive, download and run System Disk, or hook up a serial console). 6. Boot into Open Firmware, and verify that it has the version of Open Firmware you think it does. Also make sure that the other variables are set correctly. 7. Figure out the correct boot command, and boot your machine from the bootable media you just created. If you're having trouble, be sure to read the section on _C_o_m_m_o_n _P_r_o_b_l_e_m_s _a_n_d _E_r_r_o_r _M_e_s_s_a_g_e_s 8. Celebrate! The worst is over, but you've still got some work to do. Take a break, maybe more coffee, maybe a quick walk around the block, whatever turns your fancy. 9. Now use the installer to install the distribution sets onto your system and do some initial configurations. 10. Figure out how to boot from the installed partition. Boot into NetBSD for the first time. 11. Configure to your preferences, install your favorite packages, and have fun with your new NetBSD/macppc machine! _N_o_t_e_: You really actually truly do need to follow the procedure listed in this document in the order that we describe. These systems are rather tricky to boot for the novice and expert alike. Once you cross off the sections that don't apply to you, it will make more sense. _N_o_t_e_: If the instructions in a subsection below do not apply to _a_l_l ver- sions of Open Firmware, there will be a line listing which ver- sions of Open Firmware they apply to, such as: (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4, Open Firmware 3) _U_p_d_a_t_i_n_g _y_o_u_r _B_o_o_t_R_O_M (Open Firmware 3) Open Firmware 3 systems have a rewritable ``firmware'', also called the BootROM. When you use an Apple firmware updater, it updates the BootROM. This will _n_o_t change the version of Open Firmware in your machine -- it will still be Open Firmware 3. The BootROM is what is first executed when you power on or reset your system. The BootROM then loads Open Firmware, which boots your operating system. Go to the `Apple Software Updates' web site at hhttttpp::////aassuu..iinnffoo..aappppllee..ccoomm// and search for `firmware' and install the most recent version for your model. You will need to run the FirmWare updater from MacOS 9. _N_o_t_e_: If you accidentally set the llooaadd--bbaassee or rreeaall--bbaassee Open Firmware variables and reset your machine you will, in effect, rewrite the BootROM with garbage, rendering your machine unbootable. We rec- ommend not doing this. _N_o_t_e_: The most recent BootROMs available (4.1.7 and later) are known to have some problems. Some PowerMacintosh users find that their third-party RAM has been disabled. See the discussion at hhttttpp::////wwwwww..mmaaccffiixxiitt..ccoomm//aarrcchhiivveess//aapprriill..0011..aa..sshhttmmll##ffiirrmm--0044--0077 There are reports that FirmWare Update 4.1.9 on iMac (Summer 2000) will prevent the CD-ROM and the hard drive from operating togeth- er. You may get _w_d_c_0_:_0_:_1_: _l_o_s_t _i_n_t_e_r_r_u_p_t problems. _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _o_n _N_e_w_e_r _M_o_d_e_l_s (Open Firmware 3) Hold down a special four-key combination when your system boots. After the chime starts, but before it stops, hold down the four COMMAND- OPTION-O-F keys (the COMMAND key looks like a four-leaf clover or an open apple, and the OPTION key may look like a two-way switch with four straight line segments or say ALT) until you see the Open Firmware com- mand prompt on your screen: Apple PowerBook3,1 2.1f1 BootROM built on 01/29/00 at 22:38:07 Copyright 1994-2000 Apple Computer, Inc. All Rights Reserved Welcome to Open Firmware. To continue booting, type "mac-boot" and press return. To shut down, type "shut-down" and press return. ok 0 > Now, set your system to always stop at the Open Firmware prompt. 0 > sseetteennvv aauuttoo--bboooott?? ffaallssee Skip down to the section on _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D since the next several pages are instructions for older models. _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _o_n _A_p_p_l_e _N_e_t_w_o_r_k _S_e_r_v_e_r_s (Open Firmware 1.1.22) The version of Open Firmware in the Apple Network Servers can only use a serial console. You must first hook up a serial console (38400 bps, 8 bits, no parity, 1 stop bit, no handshaking) to `Port 2' (the `ttya' de- vice in Open Firmware). Hold down a special four-key combination on the keyboard attached to the ADB port on your system (not the serial console) when your system boots. After the chime starts, but before it stops, hold down the four COMMAND- OPTION-O-F keys (the COMMAND key looks like a four-leaf clover or an open apple, and the OPTION key may look like a two-way switch with four straight line segments or say ALT) until you see some introductory text and the Open Firmware command prompt on your serial terminal: 0 > Your Apple Network Server's screen will remain black. Now, set your system to always stop at the Open Firmware prompt. 0 > sseetteennvv aauuttoo--bboooott?? ffaallssee Skip down to the section on _S_e_t_t_i_n_g _u_p _p_r_e_-_O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D since the next several pages are instructions for MacOS models. _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _o_n _O_l_d_e_r _M_o_d_e_l_s (Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4) These models are significantly trickier than the newer machines. Open Firmware has two variables, `input-device' and `output-device ', which specify which devices to use for input and output. All Open Firmware 1.0.5 and most Open Firmware 2.0.x systems will default to using the `Modem' serial port for the console instead of the ADB keyboard and the monitor attached to the on-board video. Unless you use a MacOS-based utility to set these variables correctly, you _w_i_l_l need to hook up a serial console temporarily to configure Open Firmware to use your keyboard and screen. Some models (such as the Per- forma 54xx, 6360, 6400, and 6500) have the `Modem' serial port covered with a piece of plastic since the internal modem usurps that serial port. You will either need to use Boot Variables to set the `input-device' and `output-device' variables to `ttyb' (which is the Printer serial port) or remove the internal modem. Open Firmware seems to ignore the settings on most DB15 to VGA adapters. Depending on your model, it will default to either 640 x 480 at 60 Hz or to the resolution previously selected in MacOS. Make sure that your mon- itor can handle these resolutions. Now would be a good time to look at the NetBSD/macppc Model Support web- page to determine the issues with your model. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll In particular, some models _m_u_s_t use a serial console, or they will be un- able to boot NetBSD at all. All models can be set to use a serial con- sole, if you desire to bypass the keyboard and screen. If, after re-reading the next several sections, you still need help fig- uring out your `input-device' and `output-device' settings, see the FAQ: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--iinnppuutt--oouuttppuutt-- ddeevviicceess If you need to use a serial console, you can use a normal `printer' cable (mini-DIN 8 to mini-DIN 8) and a MacOS tool, such as ZTerm to connect a MacOS system to your NetBSD/macppc system. hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccoommmm//tteerrmm//zztteerrmm--110011..hhqqxx See the NetBSD Serial Port Primer for additional help and references: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//HHaarrddwwaarree//MMiisscc//sseerriiaall..hhttmmll _O_l_d_e_r _O_p_e_n _F_i_r_m_w_a_r_e _S_y_s_t_e_m _P_r_e_p_a_r_a_t_i_o_n (Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4) All pre-Open Firmware 3 macppc systems have Open Firmware bugs. Luckily, Open Firmware has a small Non-Volatile RAM variable (NVRAM) which is re- served for FORTH commands which will be run before booting an operating system. Apple has released a freeware MacOS tool called System Disk, which patches most of these bugs. We _s_t_r_o_n_g_l_y recommend that you use this tool to patch your Open Firmware, as several systems cannot boot without these patches. Instructions for using System Disk are covered in the next section. Unfortunately, some models are broken by or are unsupported by System Disk. If you have one of the following models, then skip down to the section on _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _(_H_a_r_d_e_r _m_e_t_h_o_d _u_s_i_n_g Apple Performa 4400, 5500, 6500, 54xx, 6400, and 6360, Motorola Starmax 3000, 4000, 5000, and 5500, APS Tech M*Power 604e/200, PowerComputing PowerBase, Umax Apus 2000, Apus 3000, C500, and C600 Umax S900 _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _(_R_e_c_o_m_m_e_n_d_e_d _m_e_t_h_o_d _u_s_i_n_g _M_a_c_O_S_) (Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4) Download System Disk: ffttpp::////ffttpp..aappppllee..ccoomm//ddeevveellooppeerr//mmaaccoossxxsseerrvveerr//uuttiilliittiieess//SSyysstteemmDDiisskk22..33..11..ssmmii..bbiinn For a brief tutorial on how to use System Disk, see: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk--ttuuttoorriiaall// Launch the MacOS System Disk tool. Click on ``Power User (Open Firmware)'' then click on the ``Advanced Options'' button. Now, click on the checkbox that says ``Stop Boot at Open Firmware prompt'' and select ``OK''. Click the ``Save'' button and reboot your system. _N_o_t_e_: NVRAM patches and Open Firmware settings will be erased if you `zap your PRAM' by holding down COMMAND-OPTION-P-R keys during the boot chimes, or if you accidentally boot into MacOS . If your `output-device' is `/chaos/control' (i.e. you have a PowerMacin- tosh 7300 -- 8600 system), there is a chance that your monitor will not sync. See hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk-- ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll You should now see the Open Firmware command prompt on your screen: Open Firmware, 1.0.5 To continue booting the MacOS type: BYE To continue booting from the default boot device type: BOOT ok 0 > If your screen is black, then your model does not support using the on- board video in Open Firmware. You will need to connect a serial console to the `Modem' port of your system (38400 bps, 8 bits, no parity, 1 stop bit, no handshaking). _N_o_t_e_: The ``Stop Boot at Open Firmware prompt'' setting is persistent. It is equivalent to the Open Firmware command 0 > sseetteennvv aauuttoo--bboooott?? ffaallssee _N_o_t_e_: Unfortunately, there are a few models that are better off without the System Disk patches. If you find that your machine doesn't boot, then try: 0 > sseetteennvv uussee--nnvvrraammrrcc?? ffaallssee 0 > rreesseett--aallll _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _(_H_a_r_d_e_r _m_e_t_h_o_d _u_s_i_n_g _M_a_c_O_S_) (Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4) If System Disk doesn't work because your version of MacOS is too old or because System Disk says that it doesn't support your model, then you may try using the MacOS BootVars tool. ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//mmaaccooss-- uuttiillss//bboooottvvaarrss//bboooottvvaarrss..ssiitt..hhqqxx _N_o_t_e_: BootVars does _n_o_t apply the (possibly critical) NVRAM patches that System Disk does. Expect some devices to not work (such as boot- ing from hard drives and CD-Rs). Look up the proper `output-device' for your model on the NetBSD/macppc Model Support webpage. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll If the NetBSD/macppc Model support webpage does not list an `output- device' for your model, then your system will default to using the on- board video. You needn't fill in the `output-device' and `input-device' variables. Launch the MacOS BootVars tool. Uncheck the ``auto-boot?'' checkbox, then check on the ``All Variables'' checkbox and type kkbbdd into the `input-device' box, and the proper device name into the `output-device' box. Click on the ``write'' button, and then reboot your system. If your `output-device' is `/chaos/control' (i.e. you have a PowerMacin- tosh 7300 -- 8600 system), there is a chance that your monitor will not sync. See hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk-- ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll If you have a Performa 5500 or 6500, you may need to apply NVRAMRC patch- es to use your built-in video. See the information in the NetBSD/macppc Model Support webpage. You should now see the Open Firmware command prompt on your screen: Open Firmware, 1.0.5 To continue booting the MacOS type: BYE To continue booting from the default boot device type: BOOT ok 0 > If your screen is black, then your model has defaulted to using a serial console. This is fairly common on Open Firmware 1 and 2 models if you do not use the System Disk tool to set up Open Firmware. You must hook up a serial console (38400 bps, 8 bits, no parity, 1 stop bit, no handshak- ing). _N_o_t_e_: The ``auto-boot?'' setting is persistent. Your system will always stop at the Open Firmware prompt. It is equivalent to the Open Firmware command 0 > sseetteennvv aauuttoo--bboooott?? ffaallssee _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _(_W_i_t_h_o_u_t _u_s_i_n_g _M_a_c_O_S_) (Open Firmware 1.0.5, Open Firmware 2.0.x, Open Firmware 2.4) If you don't have MacOS, then you need to hold down a special four-key combination when your system boots. Do this on the keyboard attached to the ADB port on your system (not the serial console or PS/2 port) when your system boots. _N_o_t_e_: Your system will _n_o_t have the (possibly critical) NVRAM patches that System Disk applies. Expect some devices to not work (such as booting from hard drives and CD-Rs). After the chime starts, but before it stops, hold down the four COMMAND- OPTION-O-F keys (the COMMAND key looks like a four-leaf clover or an open apple, and the OPTION key may look like a two-way switch with four straight line segments or say ALT) until you see the Open Firmware com- mand prompt on your screen or serial console: Open Firmware, 1.0.5 To continue booting the MacOS type: BYE To continue booting from the default boot device type: BOOT ok 0 > If your screen is black, then your system has defaulted to using a serial console. This is fairly common on Open Firmware 1 and 2 models if you do not use the System Disk tool to set up Open Firmware. You must hook up a serial console (38400 bps, 8 bits, no parity, 1 stop bit, no handshak- ing). Now, set your system to always stop at the Open Firmware prompt. 0 > sseetteennvv aauuttoo--bboooott?? ffaallssee To use your on-board video and keyboard, look up the proper `output- device' for your model on the NetBSD/macppc webpage hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//mmooddeellss..hhttmmll Run the following commands to use your screen instead of a serial console (replace `screen' with the correct `output-device' for your model): 0 > sseetteennvv oouuttppuutt--ddeevviiccee ssccrreeeenn 0 > sseetteennvv iinnppuutt--ddeevviiccee kkbbdd 0 > rreesseett--aallll Now you should see the Open Firmware prompt on your screen. If your `output-device' is `/chaos/control' (i.e. you have a PowerMacin- tosh 7300 -- 8600 system), there is a chance that your monitor will not sync. See hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//SSyysstteemmDDiisskk-- ttuuttoorriiaall//ooff110055ppaattcchh..hhttmmll _S_e_t_t_i_n_g _u_p _p_r_e_-_O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) This section describes some steps you must take to prepare Open Firmware to boot NetBSD. Additional resources are available in the FAQ regarding how to use the Open Firmware command environment, and the Open Firmware variables you may be using: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--aacccceessss hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--vvaarriiaabblleess Double-check your Open Firmware version: 0 > ddeevv //ooppeennpprroomm 0 > ..pprrooppeerrttiieess name openprom model Open Firmware, 1.0.5 relative-addressing ok If your system has Open Firmware prior to version 3, then you must set some Open Firmware variables before NetBSD can boot. Do _n_o_t run these commands on Open Firmware 3 machines, as you may overwrite your firmware requiring a trip to Apple for repairs. 0 > sseetteennvv llooaadd--bbaassee 660000000000 0 > sseetteennvv rreeaall--bbaassee FF0000000000 0 > rreesseett--aallll The last command reboots your machine so that the settings are stored. If you will be netbooting your system, you can look up your MAC address. 0 > ddeevv eenneett 0 > ..pprrooppeerrttiieess [...] local-mac-address CCCCCCCC CCCC [...] ok _N_o_t_e_: Some early Open Firmware 1.0.5 machines had their MAC address stored incorrectly on the motherboard (little- vs. big-endian problems). The patches the System Disk installs will correct this. Without the patch, the machine will still work, but its MAC address may conflict with another ethernet device on your network. You can check your Open Firmware settings with the _p_r_i_n_t_e_n_v command: 0 > pprriinntteennvv little-endian? false false real-mode? false false auto-boot? false true diag-switch? false false [...] use-nvramrc? true false real-base F00000 -1 [...] load-base 600000 4000 [...] input-device kbd ttya output-device /chaos/control ttya _N_o_t_e_: Open Firmware 1.0.5 settings and nvram patches will be erased if you boot into MacOS . You will need to re-enter them before boot- ing NetBSD again. _N_o_t_e_: Open Firmware 2.0.x and Open Firmware 2.4 systems will set the real-base environment variable to its default value (which pre- vents NetBSD frombooting) if you boot into MacOS . _S_e_t_t_i_n_g _u_p _O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D (Open Firmware 3) This section describes some steps you must take to prepare Open Firmware to boot NetBSD. Additional resources are available in the FAQ regarding how to use the Open Firmware command environment, and the Open Firmware variables you may be using: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--aacccceessss hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--vvaarriiaabblleess Double-check your Open Firmware version: 0 > ddeevv //ooppeennpprroomm 0 > ..pprrooppeerrttiieess name openprom device_type BootROM model OpenFirmware 3 relative-addressing supports-bootinfo ok If you will be netbooting your system, you can look up your MAC address. 0 > ddeevv eenneett 0 > ..pprrooppeerrttiieess [...] local-mac-address CCCCCCCC CCCC [...] _N_o_t_e_: Some Open Firmware 3 machines have their MAC address stored incor- rectly (little- vs. big-endian problem). If you look up your MAC address in MacOS, it will be different than what Open Firmware 3 uses to contact your netboot server. Your machine will still work, but its MAC address may conflict with another ethernet de- vice on your network. You can check your Open Firmware settings with the _p_r_i_n_t_e_n_v command: 0 > pprriinntteennvv -------------- Partition: common -------- Signature: 0x70 --------------- little-endian? false false real-mode? false false auto-boot? false true diag-switch? false false [...] use-nvramrc? true false real-base -1 -1 [...] input-device keyboard keyboard output-device screen screen _A_v_a_i_l_a_b_l_e _B_o_o_t _M_e_d_i_a (All Open Firmware versions) Each version of Open Firmware is capable of booting from a variety of me- dia (such as hard drives, floppy disks, CD-ROMs, and ethernet). Open Firmware is able to boot files from a variety of file systems (such as ISO9660, MS-DOS, and on some models HFS and HFS+). Unfortunately, Open Firmware is _n_o_t able to use the NetBSD file system (FFS), so we must put the bootloader in a location that Open Firmware is capable of using. Therefore, to boot the NetBSD kernel, Open Firmware must first open a `bootloader' which knows how to load the NetBSD kernel. There are two approaches, the _o_f_w_b_o_o_t_._x_c_f bootloader and the `partition zero' bootload- er. In the former case, the user tells Open Firmware to load _o_f_w_b_o_o_t_._x_c_f and it will load the kernel. In the latter case, the user tells Open Firmware to boot from a particular device, and a primary bootloader _b_o_o_t_x_x is loaded, which then loads the secondary bootloader _o_f_w_b_o_o_t which then loads the kernel. _N_o_t_e_: _o_f_w_b_o_o_t_._e_l_f is obsoleted. All users should be using _o_f_w_b_o_o_t_._x_c_f instead of _o_f_w_b_o_o_t_._e_l_f now. The following bootable media are available for loading the bootloader (_o_f_w_b_o_o_t or _o_f_w_b_o_o_t_._x_c_f) (see below for descriptions): ++oo _O_p_e_n _F_i_r_m_w_a_r_e _1_._0_._5_, _O_p_e_n _F_i_r_m_w_a_r_e _1_._1_._2_2_, _O_p_e_n _F_i_r_m_w_a_r_e _2_._0_._x -- Partition zero -- Ethernet (netboot) -- ISO9660 CD-ROM file system -- MS-DOS file system ++oo _O_p_e_n _F_i_r_m_w_a_r_e _2_._4 -- Partition zero -- Ethernet (netboot) -- ISO9660 CD-ROM file system -- HFS or HFS+ file systems -- Hybrid (both ISO9660 and HFS) file system -- MS-DOS file system ++oo _O_p_e_n _F_i_r_m_w_a_r_e _3 -- HFS, HFS+, or Hybrid (ISO9660 and HFS) file system -- Ethernet (netboot) -- Partition zero (not supported by NetBSD) -- MS-DOS file system Once _o_f_w_b_o_o_t or _o_f_w_b_o_o_t_._x_c_f is loaded, it can open the kernel from one of the following sources: ++oo _E_t_h_e_r_n_e_t _(_N_F_S_) ++oo _N_e_t_B_S_D _F_F_S _f_i_l_e _s_y_s_t_e_m Such as the boot floppy, or an installed NetBSD partition. ++oo _H_F_S _o_r _H_F_S_+ _f_i_l_e _s_y_s_t_e_m Only on Open Firmware 2.4 or Open Firmware 3 systems. ++oo _I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m The boot floppy image provided with the distribution sets has a `partition zero' bootloader and a NetBSD file system with an installation kernel. The boot CD-R images provided with the distribution sets has both a `partition zero' bootloader and _o_f_w_b_o_o_t_._x_c_f on a hybrid partition so it can be booted on all Open Firmware versions. The boot CD-R image also has an ISO9660 file system with an installation kernel and the dis- tribution sets. _D_e_s_c_r_i_p_t_i_o_n _o_f _b_o_o_t_a_b_l_e _m_e_d_i_a (All Open Firmware versions) This section gives a quick description of the various media that can be used by Open Firmware to load the bootloader. ++oo _P_a_r_t_i_t_i_o_n _z_e_r_o (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) This method loads a primary bootloader called _b_o_o_t_x_x located in the Apple Partition Map, which then loads the secondary boot- loader _o_f_w_b_o_o_t (functionally identical to _o_f_w_b_o_o_t_._x_c_f (q.v.)) which then loads the kernel. This is what ssyyssiinnsstt will place on your hard drive during the installation procedure. Addi- tionally, the NetBSD/macppc CD-R images and boot floppies use this method to load a kernel from the floppy's FFS partition or the CD-R's ISO9660 partition. ++oo _P_a_r_t_i_t_i_o_n _z_e_r_o (Open Firmware 3) While Open Firmware 3 supports this boot method, NetBSD/macppc does not yet support it on these systems. ++oo _H_F_S _o_r _H_F_S_+ _f_i_l_e _s_y_s_t_e_m (Open Firmware 2.4, Open Firmware 3) This method loads _o_f_w_b_o_o_t_._x_c_f from an HFS or HFS+ partition which then loads the kernel from an acceptable source (such as an FFS partition or an HFS or HFS+ partition). The FFS-based kernel may be on a previously installed NetBSD file system. Alternatively, the kernel (compressed or non-compressed) may be on an HFS or HFS+ partition. Due to Open Firmware pickiness, it must be on the same partition as _o_f_w_b_o_o_t_._x_c_f. ++oo _M_S_-_D_O_S _f_i_l_e _s_y_s_t_e_m (All Open Firmware versions) Load the _o_f_w_b_o_o_t_._x_c_f bootloader from an MS-DOS file system (such as a floppy or Zip disk). It can then load a NetBSD ker- nel from the same MS-DOS file system or elsewhere. This has only been thoroughly tested on floppy disks, but may work on FDISK-formatted hard drives. This does not work for MS-DOS partitions on a hard drive with an Apple Partition Map. ++oo _E_t_h_e_r_n_e_t _(_n_e_t_w_o_r_k _b_o_o_t_) (All Open Firmware versions) You can run your entire system diskless or netboot only the files necessary to boot (i.e. the bootloader and the installa- tion kernel), but you must have root access on another UNIX ma- chine on your subnet. _N_o_t_e_: You must use your on-board ethernet device for netboot- ing. While there may be some PCI or Cardbus ethernet interfaces with Open Firmware ROMs, no one has reported success netbooting using these devices ++oo _I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) Load the _o_f_w_b_o_o_t_._x_c_f bootloader from an ISO9660 CD-ROM. It can then load a NetBSD kernel from the ISO9660 CD-ROM. Open Firmware 1.0.5 and 2.0.x machines will _n_o_t boot from the ISO9660 file system if you create a hybrid HFS/ISO format CD-R. Make sure that the CD _o_n_l_y has ISO9660 data and does not have an Apple Partition Map. _N_o_t_e_: Open Firmware can only open files on the first session of a multi-session CD-R ++oo _H_y_b_r_i_d _H_F_S_/_I_S_O_9_6_6_0 _C_D_-_R_O_M _f_i_l_e _s_y_s_t_e_m (Open Firmware 2.4, Open Firmware 3) Load the _o_f_w_b_o_o_t_._x_c_f bootloader from the CD-ROM's HFS file sys- tem. It can then load a NetBSD kernel from the HFS or ISO9660 file system. Make sure that the CD has an Apple Partition Map. _N_o_t_e_: Open Firmware can only open files on the first session of a multi-session CD-R _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D (All Open Firmware versions) ++oo _O_p_e_n _F_i_r_m_w_a_r_e _1_._0_._5_, _O_p_e_n _F_i_r_m_w_a_r_e _1_._1_._2_2_, _O_p_e_n _F_i_r_m_w_a_r_e _2_._0_._x You must use the NetBSD installer to partition your disk if you want it to be bootable. With this release of NetBSD, there is no way to dual-boot MacOS and NetBSD on one hard drive. You can use the instructions in this section to partition a disk that may also be used with MacOS , although a disk pre- pared in this way _w_i_l_l _n_o_t _b_o_o_t NetBSD. That means, your root partition (_/ ) must be on a drive prepared with the NetBSD in- staller, but the partitions not necessary to boot (for example _/_u_s_r , _/_h_o_m_e , or _/_e_x_p_o_r_t ) may be on the same disk as MacOS . Unless you are planning to use partitions on the same disk as MacOS , skip forward to _P_r_e_p_a_r_i_n_g _t_h_e _B_o_o_t_a_b_l_e _M_e_d_i_a ++oo _O_p_e_n _F_i_r_m_w_a_r_e _2_._4 We recommend using the NetBSD installer to partition your disk, but you will not be able to use partitions on this drive with MacOS. If you'd like to have MacOS and NetBSD partitions on one hard drive (and for both to be bootable), then read the rest of this section. ++oo _O_p_e_n _F_i_r_m_w_a_r_e _3 You must have at least one disk that was partitioned using a MacOS tool before installing NetBSD on your system. This is the drive that will be holding the bootloader, _o_f_w_b_o_o_t_._x_c_f . Your NetBSD partitions may either be on this same disk (using the method described in the rest of this sec- tion), or on a separate disk accessible only to NetBSD. If you are dedicating an entire disk to NetBSD, then your MacOS parti- tioned disk only needs HFS or HFS+ partitions. The rest of this section describes how to make a single disk dual-bootable which is necessary for machines which have only one hard drive (such as the iBook, iMac, PowerBook, and Power- Macintosh Cube systems). Using the NetBSD installer to install a disklabel or bootloader will ren- der your disk unusable by MacOS. Either will also prevent Open Firmware 3 machines from booting. You will need to use the installer's ``Re- install sets'' option. More information is provided below on this pro- cess. There are several contradictory partition numbering schemes. You may want to look at the explanation in the FAQ. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ppaarrttiittiioonnss Unfortunately, the partitioning tools for NetBSD are not advanced enough to create HFS or HFS+ file systems or a partition map that can be shared with MacOS. You will need to use the MacOS Drive Setup tool (versions 1.8.1 and later are known to work) to partition the hard drive you will be using for NetBSD. Drive Setup will erase the contents of your drive -- it does not preserve data from any of your partitions. Make the fol- lowing partitions: _H_F_S or _H_F_S_+ Must be large enough to hold the boot- loader, over 100 KB. May be as large as you desire for MacOS usage. _A_/_U_X _R_o_o_t Must be at least 20 MB. Alternatively, you may decide to use one partition for your entire NetBSD installation, in which case it should be at least 200 MB without X, or 250 MB with X. NetBSD interprets an _A_/_U_X _R_o_o_t partition as the first par- tition (_a ) on the disk. This partition is not readable from MacOS . _A_/_U_X _S_w_a_p Any size. The recommendation is 1.5 times your RAM, although this is not strictly necessary for machines with a lot of RAM. NetBSD interprets an _A_/_U_X _S_w_a_p partition as the second partition (_b ) on the disk. This partition is not readable from MacOS . _A_/_U_X _U_s_e_r and _A_/_U_X _F_r_e_e_1 Use these for any additional partitions you may want to use under NetBSD, such as interprets these partitions as normal partitions. These partitions are not readable from Em Any size. You may want to leave an additional partition available to transfer files between MacOS and NetBSD. If you think you'll be doing this often, then see the FAQ entry on sharing files: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ddiisskk-- sshhaarriinngg _U_F_S Any size. This file system type is not currently supported by NetBSD/macppc al- though it might be in the future. _U_F_S partitions are not readable from MacOS versions prior to X 10.0.0. If you need further help, there is a partitioning HOW-TO on the NetBSD website: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ppaarrttiittiioonniinngg..hhttmmll _P_r_e_p_a_r_i_n_g _t_h_e _B_o_o_t_a_b_l_e _M_e_d_i_a The purpose of this section is to prepare the media from which your sys- tem will boot the installer. We'll describe how to put the files in the right places on your disk(s) or netboot server and prepare it for use on your system. If you will be running your system diskless (i.e. entirely over NFS, not using any local hard drives), then you do not need to run the installer, you only need to extract the distribution sets on the diskless server. To get the distribution sets (which will be placed on your hard drive) onto appropriate media, see the above section entitled _G_e_t_t_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m _o_n _t_o _U_s_e_f_u_l _M_e_d_i_a . You may wish to do this at the same time you create the bootable media (such as netbooting and placing distribution sets on the netboot server, or booting from CD-R and placing distribution sets on the same disk) _N_o_t_e_: Some MacOS ffttpp clients default to downloading files in `ASCII' mode. This will render the NetBSD files useless. Make sure to set your ftp program to download in `binary' mode. These are the recommended techniques for booting the NetBSD install ker- nel: ++oo _O_p_e_n _F_i_r_m_w_a_r_e _1_._0_._5_, _O_p_e_n _F_i_r_m_w_a_r_e _1_._1_._2_2_, _O_p_e_n _F_i_r_m_w_a_r_e _2_._0_._x -- Booting off an MS-DOS floppy -- Booting off the NetBSD install floppy -- Booting off the NetBSD/macppc install CD-R image -- Booting off an ISO9660 CD-ROM -- Booting over the ethernet -- Booting the floppy image off a SCSI or IDE drive (not rec- ommended) ++oo _O_p_e_n _F_i_r_m_w_a_r_e _2_._4 -- Booting off an MS-DOS floppy (may not be supported by Open Firmware 2.4) -- Booting off the NetBSD install floppy -- Booting off the NetBSD/macppc install CD-R image -- Booting off an HFS or HFS+ partition -- Booting off an ISO9660 CD-ROM -- Booting off a Hybrid HFS/ISO9660 CD-ROM -- Booting over the ethernet -- Booting the floppy image off a SCSI or IDE drive (not rec- ommended) ++oo _O_p_e_n _F_i_r_m_w_a_r_e _3 -- Booting off an HFS or HFS+ partition -- Booting off the NetBSD/macppc install CD-R image -- Booting off a Hybrid HFS/ISO9660 CD-ROM -- Booting over the ethernet What follows are the steps to create different types of bootable media. You should only need to create one of these to get your system to boot the installer ++oo _B_o_o_t_i_n_g _o_f_f _a_n _M_S_-_D_O_S _f_l_o_p_p_y (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) 1. First, make sure you have done a low-level format on the disk. A bad floppy can produce Open Firmware errors similar to other problems. 2. Mount the floppy on your computer. -- Insert it into a Windows or DOS machine. -- Use `File Exchange or `PC Exchange'' with MacOS versions prior to X 10.0.0 -- Use mount_msdos(8) on any unix-like machine. 3. Copy _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z and _o_f_w_b_o_o_t_._x_c_f to the floppy. 4. Rename _n_e_t_b_s_d_._I_N_S_T_A_L_L_._g_z to _n_e_t_b_s_d_._g_z, since OpenFirmware can't deal with MS-DOS filenames longer than eight characters. Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_f_f _t_h_e NetBSD_i_n_s_t_a_l_l _f_l_o_p_p_y (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) 1. First, make sure you have done a low-level format on the disk. A bad floppy can produce Open Firmware errors similar to other problems. 2. If the boot floppy image is compressed, then you will need to uncompress it first. 3. Use a tool to write the boot floppy image _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_._f_s to a floppy disk -- _F_r_o_m _a _U_N_I_X _m_a_c_h_i_n_e # dddd iiff==bboooott..ffss ooff==//ddeevv//rrffdd00aa bbss==3366kk -- _F_r_o_m _a _W_i_n_d_o_w_s _m_a_c_h_i_n_e Get either the rraawwrriittee..eexxee program from the NetBSD/i386 dis- tribution or rraawwrriittee3322..eexxee from hhttttpp::////wwwwww..dduusskkwwaarree..ccoomm//rraawwrriittee3322// -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e Get DDiisskkCCooppyy 6.3.3 from hhttttpp::////ddoowwnnllooAAdd..iinnffoo..aappppllee..ccoomm//AAppppllee__SSuuppppoorrtt__AArreeaa//AAppppllee__SSooffttwwaarree__UUppddaatteess//EEnngglliisshh-- NNoorrtthh__AAmmeerriiccaann//MMaacciinnttoosshh//UUttiilliittiieess//DDiisskk__CCooppyy//DDiisskk__CCooppyy__66..33..33..ssmmii..bbiinn If you are running a MacOS version prior to 9.0, get ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//aarrcchh//mmaaccppppcc//mmaaccooss-- uuttiillss//MMaakkeeDDiisskkCCooppyyFFllooppppyyTTyyppee..hhqqxx and un-BinHex it. Then, drag the _b_o_o_t_._f_s file onto this ap- plication, which will change the type and creator to _d_i_m_g and _d_d_s_k, which is necessary for DiskCopy to work. 4. Open the `Utilities' menu and pick `Make Floppy' 5. In the dialog box, select _b_o_o_t_._f_s 6. At the prompt, insert a blank floppy disk -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_A_l_t_e_r_n_a_t_e_) Get ssuunnttaarr from hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccmmpp//ssuunnttaarr--222222..hhqqxx 1. Open the `Preferences' menu and pick `Expert Mode' 2. Open the `Special' menu and pick `Overwrite Sectors ...' 3. Insert a floppy disk 4. Hit return (i.e. start at sector number zero) 5. Select _b_o_o_t_._f_s and click ``Open'' 6. Open the `File' menu and pick `Eject' Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_f_f _a_n _H_F_S _o_r _H_F_S_+ _p_a_r_t_i_t_i_o_n (Open Firmware 2.4, Open Firmware 3) Place _o_f_w_b_o_o_t_._x_c_f and the installation kernel _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z at the top level of your Macintosh file system. That is, drag the two icons onto your hard drive icon (not the desktop). Make sure they're both on the same partition. Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_f_f _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _C_D_-_R _i_m_a_g_e (All Open Firmware versions) Go to one of the NetBSD mirror sites and download CD-R image from the _p_u_b_/_N_e_t_B_S_D_/_i_s_o directory. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//mmiirrrroorrss//##iissoo -- _F_r_o_m _a _U_N_I_X _m_a_c_h_i_n_e Get and install cdrecord. NetBSD users should install it from the package collection. Other unix systems should get it from the official website: ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrreeccoorrdd//RREEAADDMMEE..hhttmmll hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc oouuttppuutt..iissoo You will need to substitute the correct name of the disk image file, speed for your CD writer, and the correct device for your system (for i386 it would be _/_d_e_v_/_c_d_1_d ). -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_) 1. Open the `Format' menu and pick `Disk Image' 2. Click the ``Data...'' button and select the disk image you downloaded. 3. Click the ``Write CD...'' button Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_f_f _a_n _I_S_O_9_6_6_0 _C_D_-_R_O_M (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) This section describes how to create your own bootable NetBSD/macppc CD-R. We recommend that you use the official NetBSD/macppc-1.6.1 CD- R image, as described in the section above. Place _o_f_w_b_o_o_t_._x_c_f and the installation kernel _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z at the top level of the CD. Due to restrictions in the way that Open Firmware deals with ISO filenames, you may wish to name your kernel _n_e_t_b_s_d_._g_z. You may also place the NetBSD 1.6.1 distribution sets on the disk. -- _F_r_o_m _a _U_N_I_X _m_a_c_h_i_n_e Get and install mkhybrid. This is now part of the cdrecord pack- age. NetBSD users should install it from the package collection. Other unix systems should get it from the official website: ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrreeccoorrdd//RREEAADDMMEE..hhttmmll hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll # mmkkhhyybbrriidd --oo oouuttppuutt..iissoo --aa --ll --JJ --rr # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc oouuttppuutt..iissoo You will need to substitute the correct speed for your CD writer, and the correct device for your system (for i386 it would be _/_d_e_v_/_c_d_1_d ). See the NetBSD Bootable CD-ROM HOW-TO for more detail: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//bboooottccdd..hhttmmll -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_) 1. Open the `Format' menu and pick `ISO 9660' 2. Click the ``Data...'' button and drag _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f and _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___M_D_._g_z into the window 3. Click the ``Settings'' tab, open the ``Naming'' popup menu, and pick ``Macintosh Names'' 4. Click the ``Done'' button 5. Click the ``Write CD...'' button Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_f_f _a _h_y_b_r_i_d _H_F_S_/_I_S_O_9_6_6_0 _C_D_-_R_O_M (Open Firmware 2.4, Open Firmware 3) This section describes how to create your own bootable NetBSD/macppc CD-R. We recommend that you use the official NetBSD/macppc-1.6.1 CD- R image, as described two sections above. Place _o_f_w_b_o_o_t_._x_c_f and the installation kernel _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z at the top level of the CD. Make sure that the bootloader is present on the HFS partition, and the kernel is on both the ISO9660 and HFS par- titions. Due to restrictions in the way that Open Firmware deals with ISO filenames, you may wish to name your kernel _n_e_t_b_s_d_._g_z. You may also place the NetBSD 1.6.1 distribution sets on the ISO9660 par- tition (_n_o_t only on the HFS partition). -- _F_r_o_m _a _U_N_I_X _m_a_c_h_i_n_e Get and install mkhybrid. This is now part of the cdrecord pack- age. NetBSD users should install it from the package collection. Other unix systems should get it from the official website: ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//ppkkggssrrcc//ssyyssuuttiillss//ccddrreeccoorrdd//RREEAADDMMEE..hhttmmll hhttttpp::////wwwwww..ffookkuuss..ggmmdd..ddee//rreesseeaarrcchh//cccc//gglloonnee//eemmppllooyyeeeess//jjooeerrgg..sscchhiilllliinngg//pprriivvaattee//ccddrreeccoorrdd..hhttmmll # mmkkhhyybbrriidd --oo oouuttppuutt..iissoo --hhffss --ppaarrtt --aa --ll # ccddrreeccoorrdd --vv ssppeeeedd==44 ddeevv==//ddeevv//ccdd11cc oouuttppuutt..iissoo You will need to substitute the correct speed for your CD writer, and the correct device for your system (for i386 it would be _/_d_e_v_/_c_d_1_d ). See the NetBSD Bootable CD-ROM HOW-TO for more detail: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//bboooottccdd..hhttmmll -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e _(_u_s_i_n_g _T_o_a_s_t_) 1. Open the `Format' menu and pick `Mac/ISO Hybrid' 2. Open the `Utilities' menu and pick `Create Temporary Partition...' 3. Make this temporary partition large enough for all of the files you will be placing on the HFS portion of the CD (only _o_f_w_b_o_o_t_._x_c_f is necessary). 4. Copy _i_n_s_t_a_l_l_a_t_i_o_n_/_o_f_w_b_o_o_t_._x_c_f to the temporary partition 5. Click the ``Data...'' button and select the temporary parti- tion you just created 6. Click the ``ISO...'' button and drag _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___M_D_._g_z into the window. You may also want to drag the NetBSD 1.6.1 distribution sets to this window as well. 7. Click the ``Settings'' tab, open the ``Naming'' popup menu, and pick ``Macintosh Names'' 8. Click the ``Done'' button 9. Click the ``Write CD...'' button Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _o_v_e_r _t_h_e _e_t_h_e_r_n_e_t (All Open Firmware versions) 1. Introduction To netboot a macppc, you must configure one or more servers to provide information and files to your macppc (the `client ).' If you are using NetBSD (any architecture) on your netboot serv- er(s), the information provided here should be sufficient to configure everything. Additionally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configuring. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary to configure the net- boot services on a variety of platforms. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//nneettwwoorrkk//nneettbboooott// You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network. Briefly, the netboot process involves discovery, bootstrap, ker- nel and file system stages. In the first stage, the client dis- covers information about where to find the bootstrap program. Next, it downloads and executes the bootstrap program. The bootstrap program goes through another discovery phase to deter- mine where the kernel is located. The bootstrap program tries to mount the NFS share containing the kernel. Once the kernel is loaded, it starts executing. For RAM disk kernels, it mounts the RAM disk file system and begins executing the installer from the RAM disk. For normal (non-RAM disk) kernels, the kernel tries to mount the NFS share that had the kernel and starts exe- cuting the installation tools or init(8). All macppc systems use BOOTP for the discovery stage. TFTP is used in the boot- strap phase to download the bootstrap program, _o_f_w_b_o_o_t_._x_c_f. NFS is used in both the kernel and file system stages to download the kernel, and to access files on the file server. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hardware address) of your netboot client machine. You should have determined this address in an earlier stage. In this exam- ple, we will use `192.168.1.10' as the IP address of your client and `client.test.net' as its name. We will assume you're pro- viding all of your netboot services on one machine called `server.test.net' with the client's files exported from the di- rectory _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environment. You should set up each netboot stage in order (i.e. discovery, bootstrap, kernel, and then file system) so that you can test them as you proceed. 2. dhcpd(8) in bootpd(8) compatible mode Put the following lines in your _/_e_t_c_/_d_h_c_p_d_._c_o_n_f (see dhcpd.conf(5) and dhcp-options(5) for more information): ddns-update-style none; # Do not use any dynamic DNS features # allow bootp; # Allow bootp requests, thus the dhcp server # will act as a bootp server. # authoritative; # This is the authoritative DHCP server for this subnet # subnet 192.168.1.0 netmask 255.255.255.0 { # Which network interface the server will listen on. # The zeros indicate which range of addresses are # allowed to connect. } group { # Set of parameters common to all clients # in this "group". # option broadcast-address 192.168.1.255; option domain-name "test.net"; option domain-name-servers dns.test.net; option routers router.test.net; option subnet-mask 255.255.255.0; # # An individual client. # host client.test.net { hardware ethernet CC:CC:CC:CC:CC:CC; fixed-address 192.168.1.10; # # Name of the host (if the fixed address # doesn't resolve to a simple name). # option host-name "client"; # # Name of the bootloader or kernel # to download via tftp. # filename "ofwboot.xcf"; # # The path on the NFS server. # option root-path "/export/client/root"; } #you may paste another "host" entry here for additional clients on this network } You will need to make sure that the _d_h_c_p_d_._l_e_a_s_e_s file exists. # ttoouucchh //vvaarr//ddbb//ddhhccppdd..lleeaasseess You will need to start the ddhhccppdd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD 1.5 or later, you can achieve this with: # //eettcc//rrcc..dd//ddhhccppdd rreessttaarrtt 3. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) environment in the _/_t_f_t_p_b_o_o_t directory. Thus, the first order of business is to create this directory: # mmkkddiirr --pp //ttffttppbboooott Next, edit _/_e_t_c_/_i_n_e_t_d_._c_o_n_f and uncomment the line with the TFTP daemon: tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot Now, restart inetd(8). If the server is running NetBSD 1.5 or later, you can achieve this with: # //eettcc//rrcc..dd//iinneettdd rreessttaarrtt Now, you need to copy the bootloader for your macppc machine to _/_t_f_t_p_b_o_o_t. Get ofwboot.xcf(8) from the _i_n_s_t_a_l_l_a_t_i_o_n directory of the distribution. # ccpp ooffwwbboooott..xxccff //ttffttppbboooott Just to be sure, let's make everything readable. # cchhmmoodd --RR aa++rrXX //ttffttppbboooott Sometimes, the arp(8) table gets messed up, and the TFTP server can't communicate with the client. In this case, it will write a log message (via syslogd(8)) to _/_v_a_r_/_l_o_g_/_m_e_s_s_a_g_e_s saying: `tftpd: write: Host is down'. If this is the case, you may need to force the server to map your client's ethernet address to its IP address: # aarrpp --ss cclliieenntt CCCC::CCCC::CCCC::CCCC::CCCC::CCCC 4. nfsd(8), mountd(8), and rpcbind(8) Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. 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 an NFS server, you only need to restart mountd(8). Otherwise, you need to start rpcbind(8) and nfsd(8). If the server is running NetBSD 1.5 or later, you can achieve this with: # //eettcc//rrcc..dd//rrppccbbiinndd ssttaarrtt # //eettcc//rrcc..dd//nnffssdd ssttaarrtt # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt 5. NetBSD kernel and installation tools Now, if you place a kernel named _n_e_t_b_s_d in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t your client should boot the kernel. If you are netbooting the installer, 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___M_D_._g_z (this has the installation tools in a RAM disk). Also, copy the distribution files to the client's root directory. # ccpp **ttggzz //eexxppoorrtt//cclliieenntt//rroooott # gguunnzziipp nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz # mmvv nneettbbssdd..GGEENNEERRIICC__MMDD //eexxppoorrtt//cclliieenntt//rroooott//nneettbbssdd If you are running your macppc diskless, simply 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. 6. Client file system You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//DDooccuummeennttaattiioonn//nneettwwoorrkk//nneettbboooott//nnffss..hhttmmll -- Extracting distribution sets # ccdd //eexxppoorrtt//cclliieenntt//rroooott # ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//bbaassee..ttggzz # ttaarr --xxppzzff //ppaatthh//ttoo//ffiilleess//eettcc..ttggzz Continue with the other non-essential distribution sets if desired. -- Set up swap # mmkkddiirr //eexxppoorrtt//cclliieenntt//rroooott//sswwaapp # dddd iiff==//ddeevv//zzeerroo ooff==//eexxppoorrtt//cclliieenntt//sswwaapp bbss==44kk ccoouunntt==44kk # eecchhoo ''//eexxppoorrtt//cclliieenntt//sswwaapp --mmaapprroooott==rroooott::wwhheeeell cclliieenntt..tteesstt..nneett'' ccaatt >>>> # //eettcc//rrcc..dd//mmoouunnttdd rreessttaarrtt This creates a 16 MB swap file and exports it to the client. -- Create device nodes # ccdd //eexxppoorrtt//cclliieenntt//rroooott//ddeevv # ..//MMAAKKEEDDEEVV aallll This procedure only works on NetBSD hosts. -- Set up the client's fstab(5) Create a file in _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_f_s_t_a_b with the fol- lowing lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 -- Set up the client's rc.conf(5) Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_r_c_._c_o_n_f rc_configured=YES hostname="client" defaultroute="192.168.1.1" nfs_client=YES auto_ifconfig=NO net_interfaces="" Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system. -- Set up the client's hosts(5) file. Edit _/_e_x_p_o_r_t_/_c_l_i_e_n_t_/_r_o_o_t_/_e_t_c_/_h_o_s_t_s ::1 localhost 127.0.0.1 localhost 192.168.1.10 client.test.net client 192.168.1.5 server.test.net server 7. Setting up the server daemons If you want these services to start up every time you boot your server, make sure the following lines are present in your _/_e_t_c_/_r_c_._c_o_n_f: dhcpd=YES dhcpd_flags="-q" nfs_server=YES # enable server daemons mountd=YES rpcbind=YES rpcbind_flags="-l" # -l logs libwrap Also, you'll need to make sure the _t_f_t_p_d line in _/_e_t_c_/_i_n_e_t_d_._c_o_n_f remains uncommented. Skip forward to _I_n_s_t_a_l_l_i_n_g _t_h_e _N_e_t_B_S_D _S_y_s_t_e_m ++oo _B_o_o_t_i_n_g _t_h_e _f_l_o_p_p_y _i_m_a_g_e _o_f_f _a _S_C_S_I _o_r _I_D_E _d_r_i_v_e (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) If the boot floppy image is compressed, then you will need to uncom- press it first. Find a spare bootable drive (i.e. SCSI or IDE), and use some tool to write the floppy disk image _i_n_s_t_a_l_l_a_t_i_o_n_/_f_l_o_p_p_y_/_b_o_o_t_._f_s to your spare drive, and boot from that drive. For example, you could use a Zip drive, a Jaz drive, a Compact Flash drive, or even a spare hard drive. The floppy image has a `partition zero' bootloader which ul- timately loads the installation kernel from the FFS file system from the disk image. -- _F_r_o_m _a _U_N_I_X _m_a_c_h_i_n_e # dddd iiff==bboooott..ffss ooff==//ddeevv//rrssdd00cc where _/_d_e_v_/_r_s_d_0_c is the `whole disk' partition for the drive you will be using. Be certain you have typed this correctly, as it will erase the disk. -- _F_r_o_m _a _W_i_n_d_o_w_s _m_a_c_h_i_n_e Get rraawwrriittee3322..eexxee from hhttttpp::////wwwwww..dduusskkwwaarree..ccoomm//rraawwrriittee3322// Be certain you have selected the correct disk, as it will erase the contents. -- _F_r_o_m _a _M_a_c_O_S _m_a_c_h_i_n_e Get ssuunnttaarr from hhttttpp::////hhyyppeerraarrcchhiivvee..llccss..mmiitt..eedduu//HHyyppeerrAArrcchhiivvee//AArrcchhiivvee//ccmmpp//ssuunnttaarr--222222..hhqqxx 1. Open the `Preferences' menu and pick `Expert Mode' 2. Open the `File' menu and pick `Open Device ...' 3. Click on the ``scan SCSI'' button to get a list of which drives are attached. 4. Pick the correct drive. Be certain you have selected the correct disk, as it will erase the contents. 5. Open the `Special' menu and pick `Overwrite Sectors ...' 6. Hit return (i.e. start at sector number zero) 7. Select _b_o_o_t_._f_s and click ``Open'' 8. Open the `File' menu and pick `Close Device' IInnssttaalllliinngg tthhee NNeettBBSSDD SSyysstteemm _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t _s_y_n_t_a_x The syntax of the Open Firmware bboooott command is: boot boot-device [boot-file] [-as] where the boot-device describes where to find the bootloader, boot-file describes where to find the NetBSD kernel, and the options specify how you want to boot. You use the boot-device to tell Open Firmware where to find ofwboot(7) by listing the device, the partition (if it's a disk), and the filename of the bootloader (if using _o_f_w_b_o_o_t_._x_c_f ). If the boot-file is on the same device and (if it's a disk) partition as the boot-device then you can just specify the kernel filename. Other- wise, you need to specify the full Open Firmware path to the kernel. The --aa flag will ask you for the location of the next item to load (i.e. the bootloader will ask where the kernel is (if unspecified), or the ker- nel will ask where the root file system is). The --ss flag will boot into `single-user' mode. The exact command you will be using depends on which version of Open Firmware your machine has and which device you will be booting from. Sometimes you may have to guess as we don't know all of the combinations of models, device names, and file names. In general the format is: device:[partition][,\filename]. Keep in mind for the future that you may be able to have your boot-device and boot-file on entirely different de- vices (such as the bootloader netbooted from enet and the kernel loaded from a hard drive on the ultra0 ATA/IDE bus). We'll try to walk you through the process of figuring out what Open Firmware calls your device, partition, and file names. To start with, Open Firmware keeps a ``device tree'' with all of the devices it finds in your system. You can get a listing of the nodes in this device tree with the ddeevv and llss commands. ddeevv is similar to the unix ccdd command and is used to change between the nodes in the Open Firmware device tree (simi- lar to a file system). llss of course is similar to the unix llss command and is used to list the contents of the current device node. To get a listing of all the devices available in your system, use the following commands: 0 > ddeevv // 0 > llss Open Firmware has device aliases which are simple names for the full hardware path to a device (similar to aalliiaass in csh(1)). You can find out what device aliases Apple created on your machine with the ddeevvaalliiaass com- mand. For example, here are the devaliases on a PowerMacintosh 7300: 0 > ddeevvaalliiaass vci0 /chaos@F0000000 pci1 /bandit@F2000000 pci2 /bandit@F4000000 fd /bandit/gc/swim3 kbd /bandit/gc/via-cuda/adb/keyboard ttya /bandit/gc/escc/ch-a ttyb /bandit/gc/escc/ch-b enet /bandit/gc/mace scsi /bandit/gc/53c94 scsi-int /bandit/gc/mesh ok On most systems, you'll find the devices you're looking for. Typical aliases are: Dl hd internal hard drive Dl cd CD-ROM drive Dl zip internal Zip drive Dl enet ethernet Dl fd floppy drive Dl scsi SCSI bus Dl scsi-int internal SCSI bus (on systems with multiple SCSI busses) Dl scsi-ext external SCSI bus (on systems with multiple SCSI busses) Dl ata ATA/IDE bus Dl ideN ATA/IDE bus number N Dl ultraN Ultra/66 or Ultra/100 IDE bus number N Note that some of these items are the device itself, and some are a bus. When you only have the devalias to a bus, you need to specify which de- vice on that bus you want to use. You can use the Open Firmware ddeevv and llss commands. For example, here are the devices on the internal SCSI bus of a PowerMacintosh 7300: 0 > ddeevv ssccssii--iinntt 0 > llss FF83C850: /sd@0,0 FF83D480: /st@0,0 ok In this case, Open Firmware seems to be saying there are two devices, both at address zero (one is a SCSI disk `sd@0,0' and the other is a SCSI tape `st@0,0 ).' Unfortunately, older systems will only list the naming convention and not the actual devices currently connected, but that's OK -- we've got more tricks up our sleeve. If you've got ATA/IDE drives, you have all the device information you need (since Apple only ever ships drives as ``master'' which is typically something like ata-disk@0, ATA-Disk@0, atapi-disk, or ata-disk@000ata- disk@011ata-disk@02 You can find out the devices on your SCSI bus with the sshhooww--cchhiillddrreenn com- mand: 0 > ddeevv ssccssii--iinntt 0 > sshhooww--cchhiillddrreenn Target 0 Unit 0 Disk IBM DCAS-32160 S65A Target 3 Unit 0 Removable Read Only device SONY CD-ROM CDU-8005 1.0j ok Open Firmware calls SCSI IDs ``Target''. The ``Unit'' number is the Log- ical Unit Number (LUN). This is almost always zero. Thus, this PowerMa- cintosh system has an IBM hard drive (DCAS-32160) at SCSI ID 0, and a Sony CD-ROM drive (CDU-8005) at SCSI ID 3. Now, we've got enough information to construct the device name for Open Firmware. Just stick everything together to describe to Open Firmware what you want. For example, Open Firmware calls the CD-ROM drive in this system scsi-int/sd@3. To determine if a device is bootable, type: 0 > ddeevv ssccssii--iinntt//ssdd@@33 0 > wwoorrddss load write read seek close open write-blocks read-blocks max-transfer block-size dma-sync dma-map-out dma-map-in dma-free dma-alloc ok If the wwoorrdd ``open'' is present in the list, then the device is almost certainly bootable. Next, you need to figure out what partition Open Firmware thinks your bootloader is located on if you're going to boot from a disk. If you're using a ``partition zero'' bootloader, the answer is obvious: 0. Thus, your boot-device for the NetBSD/macppc CD-R image on an Open Firmware 1.0.5 system would be scsi-int/sd@3:0 since the image has a `partition zero' bootloader. Other situations get a little trickier, as we know of no way to get a partition map from within Open Firmware, and it uses a different number- ing scheme than either NetBSD or MacOS 9.x and earlier. See the FAQ for an explanation: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ppaarrttiittiioonnss Typically, MS-DOS and ISO9660 formatted disks have their file systems at partition 1. Typically, Drive Setup formatted disks have their file sys- tems starting at partition number 9. Often, if you omit the partition number, Open Firmware looks in the first partition it understands holding a valid file system. Open Firmware uses a comma (,) to separate the partition number from the filename. It uses a backslash (the _\ character) to separate directories. The bootloader uses forward slashes (the _/ character) to separate direc- tories when specifying the boot-file. Thus, to specify the top of the file system on a CD-ROM in the example PowerMacintosh 7300 system, you'd use: scsi-int/sd@3:,\ Now, to confirm that you and Open Firmware are looking at the same files, you can get a directory listing of the file system on your device with the ddiirr command. This command is only useful with file systems that Open Firmware understands and is able to boot from. On Open Firmware 1.0.5, 1.1.22, and 2.0.x systems, you can use ddiirr on ISO9660 (not hybrid) and MS-DOS file systems. On Open Firmware 2.4, you can use it on HFS, HFS+, hybrid, ISO9960, and MS-DOS file systems. On Open Firmware 3, you can use it on HFS, HFS+, hybrid (not pure ISO9660), and MS-DOS file systems. 0 > ddiirr ffdd::,,\\ FINDER .DAT 022 2 2B8 DESKTOP . 022 0 0 RESOURCE.FRK 012 3 0 NETBSD~1.GZ 020 5 1FDFCA TRASH . 010 B00 0 OFWBOOT .XCF 020 A75 D8F4 ok You can see that this MacOS formatted floppy has a bunch of stuff, as well as the two important files: _N_E_T_B_S_D_~_1_._G_Z and _O_F_W_B_O_O_T_._X_C_F. Note that MacOS shortened _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z to _N_E_T_B_S_D_~_1_._G_Z since MS-DOS file systems can only natively hold 8 characters for the filename. Keep in mind that Open Firmware is often case-sensitive when it comes to file- names. If the ddiirr command showed you the files you're looking for, then you've figure out how to tell Open Firmware to look for your bootloader! In this case, your boot-device is fd:,\OFWBOOT.XCF and your boot-file is fd:,/NETBSD~1.GZ. For additional help, see ofwboot(7) and the FAQ on topics like how to use the Open Firmware command environment and how to boot from a device at- tached to a PCI card which has Open Firmware support: hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ooffww--uussee hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##bboooott--ppccii _E_x_a_m_p_l_e_s _o_f _O_p_e_n _F_i_r_m_w_a_r_e _b_o_o_t _c_o_m_m_a_n_d_s Here are some examples of the commands you might use to boot your system: ++oo _B_o_o_t_i_n_g _o_f_f _a_n _M_S_-_D_O_S _f_l_o_p_p_y (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) _N_o_t_e_: This is not a normal MacOS boot floppy -- you must enter Open Firmware and type a boot command. Use the Open Firmware ddiirr command to get a listing of the files on the floppy. Typically you'll find filenames like OFWBOOT.XCF and NETBSD~1.GZ. 0 > bboooott ffdd::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD~~11..GGZZ You can eject a floppy by typing: 0 > eejjeecctt ffdd ++oo _B_o_o_t_i_n_g _o_f_f _t_h_e _N_e_t_B_S_D _i_n_s_t_a_l_l _f_l_o_p_p_y (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) The floppy disk has a `partition zero' bootloader. _N_o_t_e_: This is not a normal MacOS boot floppy -- you must enter Open Firmware and type a boot command. All you need to do is: 0 > bboooott ffdd::00 You can eject a floppy by typing: 0 > eejjeecctt ffdd ++oo _B_o_o_t _o_v_e_r _t_h_e _e_t_h_e_r_n_e_t (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) You can try the simple form (i.e. that you are booting from ether- net): 0 > bboooott eenneett::,,ooffwwbboooott..xxccff Or you may be more specific, specifying the bootloader filename and the kernel name: 0 > bboooott eenneett::,,ooffwwbboooott..xxccff eenneett::,,//nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz _N_o_t_e_: Some Open Firmware 1.0.5 machines have their MAC address stored incorrectly. Make sure that your netboot server is us- ing the same MAC address that your macppc client is using. See the section on _S_e_t_t_i_n_g _u_p _p_r_e_-_O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D to figure out your MAC address. _N_o_t_e_: Some Open Firmware 1.0.5 machines, using ofwboot.xcf version 1.2 cannot load compressed kernels. Uncompress them first. ++oo _B_o_o_t _o_v_e_r _t_h_e _e_t_h_e_r_n_e_t (Open Firmware 3) You can try the simple form (i.e. that you are booting from ether- net): 0 > bboooott eenneett::00 Or you may be more specific, specifying the bootloader filename and the kernel name: 0 > bboooott eenneett::00,,ooffwwbboooott..xxccff eenneett::00,,//nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz ++oo _B_o_o_t_i_n_g _o_f_f _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _i_n_s_t_a_l_l _C_D_-_R (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) Here are some examples of what you might use to boot from CD-ROM (Ap- ple usually sets their CD-ROM drives to SCSI ID 3): 0 > bboooott ssccssii--iinntt//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC 0 > bboooott ssccssii//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC 0 > bboooott ssccssii--eexxtt//ssdd@@33::00 NNEETTBBSSDD..MMAACCPPPPCC 0 > bboooott aattaa//aattaappii--ddiisskk::00 NNEETTBBSSDD..MMAACCPPPPCC 0 > bboooott iiddee11//ddiisskk@@00::00 NNEETTBBSSDD..MMAACCPPPPCC 0 > bboooott ccdd::00 NNEETTBBSSDD..MMAACCPPPPCC ++oo _B_o_o_t_i_n_g _o_f_f _t_h_e _N_e_t_B_S_D_/_m_a_c_p_p_c _i_n_s_t_a_l_l _C_D_-_R (Open Firmware 3) 0 > bboooott ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..mmaaccppppcc ++oo _B_o_o_t_i_n_g _o_f_f _a _h_o_m_e_-_m_a_d_e _C_D_-_R_O_M _I_S_O_9_6_6_0 _o_r _H_y_b_r_i_d (All Open Firmware versions) Open Firmware doesn't understand long filenames (created with the RockRidge and Joliet extensions), so you may need to figure out what your file is called. You should use the Open Firmware ddiirr command to get a listing of the files on your CD. For instance, TTooaasstt for MacOS creates CDs with long filenames, but uses MS-DOS style short names as well. Instead of referencing _n_e_t_b_s_d_-_G_E_N_E_R_I_C you would need to open _N_E_T_B_S_D_-_G_._E_N_E The mmkkiissooffss and mmkkhhyybbrriidd programs have a similar problem. For them, _n_e_t_b_s_d_._G_E_N_E_R_I_C___M_D_._g_z becomes _N_E_T_B_S_D___G_E_N_E_R_I_C___M_D_._G_Z. Another thing to note is that you _m_u_s_t use the same case when speci- fying the filename to load that Open Firmware uses. Also, keep in mind what format your CD-R has to be for your version of Open Firmware (pure ISO versus hybrid ISO/HFS). We'll assume that you've wisely renamed your kernel to _n_e_t_b_s_d_._g_z to avoid many of these name issues. Here are some examples of what you might use to boot from CD-ROM (Apple usually sets their CD-ROM drives to SCSI ID 3): 0 > bboooott ssccssii--iinntt//ssdd@@33::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ 0 > bboooott ssccssii//ssdd@@33::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ 0 > bboooott ssccssii--eexxtt//ssdd@@33::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ 0 > bboooott aattaa//aattaappii--ddiisskk::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ 0 > bboooott iiddee11//ddiisskk@@00::,,\\OOFFWWBBOOOOTT..XXCCFF NNEETTBBSSDD..GGZZ 0 > bboooott ccdd::,,\\ooffwwbboooott..xxccff nneettbbssdd..ggzz ++oo _B_o_o_t_i_n_g _o_f_f _a_n _I_D_E _o_r _S_C_S_I _d_r_i_v_e _w_i_t_h _a `partition zero _b_o_o_t_l_o_a_d_e_r' (Open Firmware 1.0.5, Open Firmware 1.1.22, Open Firmware 2.0.x, Open Firmware 2.4) You do not specify a file to load, since the `partition zero' booloader knows what to do. You would boot such a system if you have dumped the boot floppy image to your drive, or if you have an al- ready-installed NetBSD/macppc system Remember, that SCSI Zip disks are usually ID 5 or 6. Internal hard drives are usually SCSI ID 0. Here are some examples of what you might use to boot from such a drive: 0 > bboooott ssccssii--iinntt//ssdd@@00::00 0 > bboooott ssccssii//ssdd@@00::00 0 > bboooott ssccssii--eexxtt//ssdd@@00::00 0 > bboooott aattaa//aattaa--ddiisskk@@00::00 0 > bboooott aattaa//AATTAA--DDiisskk@@00::00 0 > bboooott iiddee00//ddiisskk@@00::00 0 > bboooott zziipp::00 ++oo _B_o_o_t_i_n_g _o_f_f _a_n _I_D_E _o_r _S_C_S_I _d_r_i_v_e _w_i_t_h _a_n _H_F_S _o_r _H_F_S_+ _p_a_r_t_i_t_i_o_n (Open Firmware 2.4, Open Firmware 3) MacOS drives have several system-level partitions reserved for MacOS drivers. You may find that your first HFS or HFS+ partition might be as high as partition 9. You may need to keep trying higher partition numbers until you find the one that has your bootloader. If you're running MacOS X you can run the following command to print out the partition table on your drive: % ssuuddoo ppddiisskk //ddeevv//ddiisskk00 --dduummpp If you are confused by the various partition numbering schemes, see the explanation in the FAQ hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##ppaarrttiittiioonnss You should use the Open Firmware ddiirr command to get a directory list- ing of the files on your hard drive. If bootloader is on a different partition from the NetBSD kernel, you will need to specify where to find the kernel. Remember, that SCSI Zip disks are usually ID 5 or 6. Internal hard drives are usually SCSI ID 0. Here are some examples of what you might use to boot the installer kernel located on an HFS or HFS+ partition: 0 > bboooott ssccssii//ssdd@@00::99,,\\ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz 0 > bboooott iiddee00//ddiisskk@@00::1100,,\\ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz 0 > bboooott hhdd::99,,\\ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz 0 > bboooott uullttrraa11::99,,ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz _E_x_a_m_p_l_e _o_f _a _n_o_r_m_a_l _b_o_o_t Of course, a lot of the information in this example depends on your model and what your boot method is, but we'll include this anyways just so you get an idea of what to expect (user-typed commands are in bboolldd ). Apple PowerBook3,1 2.1f1 BootROM built on 01/29/00 at 22:38:07 Copyright 1994-2000 Apple Computer, Inc. All Rights Reserved Welcome to Open Firmware. To continue booting, type "mac-boot" and press return. To shut down, type "shut-down" and press return. ok 0 > bboooott eenneett::,,ooffwwbboooott..xxccff nneettbbssdd..GGEENNEERRIICC__MMDD..ggzz loading XCOFF tsize=C280 dsize=14AC bsize=2620 entry=600000 SECTIONS: .text 00600000 00600000 0000C280 000000E0 .data 0060D000 0060D000 000014AC 0000C360 .bss 0060E4B0 0060E4B0 00002620 00000000 loading .text, done.. loading .data, done.. clearing .bss, done.. >> NetBSD/macppc OpenFirmware Boot, Revision 1.3 >> (tsubai@mint.iri.co.jp, Sun Nov 26 01:41:27 JST 2000) 1701508+177748 [100+68176+55886]=0x1e9468 start=0x100000 Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5.1 (INSTALL) #0: Thu Mar 15 00:52:56 PST 2001 mw@al:/usr/src/sys/arch/macppc/compile/INSTALL total memory = 192 MB avail memory = 172 MB using 2483 buffers containing 9932 KB of memory [...] erase ^H, werase ^W, kill ^U, intr ^C, status ^T Terminal type? [vt100] Erase is backspace. (I)nstall, (S)hell or (H)alt ? _C_o_m_m_o_n _P_r_o_b_l_e_m_s _a_n_d _E_r_r_o_r _M_e_s_s_a_g_e_s This is a brief list of some of the Open Firmware problems you may run into. See the NetBSD/macppc FAQ for a thorough list. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##bboooott--ttrroouubbllee _N_o_t_e_: You may find it necessary to remove all non-Apple devices from your machine. Some users have found this necessary. ++oo Black screen If your system is a PowerBook, NetBSD may have turned down the brightness of the backlight. Use the buttons to turn your brightness back up. Otherwise, you need a serial console. See the section entitled _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _o_n _O_l_d_e_r _M_o_d_e_l_s ++oo Grey screen with flashing question mark This means that your system is trying to boot MacOS. You might get to this state if you didn't properly enter Open Firmware, or if your Open Firmware boot command is misformed. If you typed a bad boot command, Open Firmware tries to boot from the value stored in the boot-device variable, whose default value is the MacOS ROM. The grey screen with the icon is generated by the MacOS ROM. A flashing question-mark or broken folder means that your machine is looking for a bootable MacOS file system, but can't find one. A hap- py face means it's trying to boot MacOS. The boot floppy does not have a bootable MacOS file system, it has a bootable NetBSD file system. Reboot, re-enter Open Firmware and check your syntax carefully. _N_o_t_e_: Don't forget to check your Open Firmware environment vari- ables, as they may have been changed by your brief excursion into MacOS . ++oo Information on your screen seems garbled or out of sync If you have a PowerMacintosh 7300 through 8600, then you need to read the section on System Disk and the patches it applies. See the sec- tion entitled _G_e_t_t_i_n_g _t_o _t_h_e _O_p_e_n _F_i_r_m_w_a_r_e _P_r_o_m_p_t _o_n _O_l_d_e_r _M_o_d_e_l_s If you have a Twentieth Anniversary Macintosh, Open Firmware does not work with the internal display, you will need to set up a serial con- sole. ++oo ``DEFAULT CATCH!'' This is a general message from Open Firmware to the effect that it had trouble loading a file. If your machine is Open Firmware version 1.0.5, 2.0.x, or 2.4, this error does sometimes appear randomly. You might try the boot command a second time (this is known to work on some models). It's also an indication that either your floppy disk is bad, or the floppy drive is bad. Try doing a low-level format on the floppy, re-copy the files, and try again. There are several models that cannot be booted while using the on- board video and keyboard. Try using a serial console. ++oo ``CLAIM failed'' This is a general message from Open Firmware to the effect that it failed to allocate some memory or memory is messed up. First, make sure you have the Open Firmware variable load-base set correctly. If your system is Open Firmware version 1.0.5, 1.1.22, 2.0.x, or 2.4, see the section above on _S_e_t_t_i_n_g _u_p _p_r_e_-_O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D Do not change load-base on an Open Firmware 3 system. If you tried one boot command and it failed, then you tried a second and got the CLAIM failed message, then this is an indication that you should reboot between attempts. Use the Open Firmware rreesseett--aallll com- mand. Contradictorily, if your machine is Open Firmware version 1.0.5, 2.0.x or 2.4, this error does sometimes appear randomly. You might try the boot command a second time (this is known to work on some models). There are several models that cannot be booted while using the on- board video and keyboard. Try using a serial console. ++oo ``can't OPEN'' Open Firmware either can't open the device you specified (because it is not present or the device path is mistyped) or the file you speci- fied. Check your typing and check to make sure that the media has the files you think it has. Use the Open Firmware ddiirr command to verify that the file(s) you tried accessing are really there. ++oo ``unrecognized Client Program formatstate not valid'' This is a general Open Firmware error message indicating that the filename you tried to open either doesn't exist or is in the wrong format. For Open Firmware 1 and 2 machines, it must be an XCOFF file (such as _o_f_w_b_o_o_t_._x_c_f) and for Open Firmware 3 machines, it must be either XCOFF or ELF (such as a kernel). Make sure that you have use binary mode to FTP the files, and that they are properly uncom- pressed. ++oo ``bad partition number, using 0no bootable HFS partition'' If you're trying to boot an Open Firmware 1.0.5, 1.1.22, or 2.0.x system, this probably means that your media (i.e. hard drive or CD- ROM) has an HFS file system on it (such as a hybrid CD-R or a hard drive with MacOS partitions). ++oo ``TFTP timeout'' Either the server's TFTP server isn't running, or you're using a mod- el with Open Firmware 1.0.5 and not specifying the location of the bootloader. Unfortunately, on the early models, _o_f_w_b_o_o_t_._x_c_f gets confused and doesn't work right unless you load it explicitly from the boot-device, even if the bootp or DHCP server provides the cor- rect information. You need to boot with a command like: 0 > bboooott eenneett::,,ooffwwbboooott..xxccff ++oo Bootloader hangs before the copyright notice and the kernel configu- ration You forgot to set real-base in Open Firmware or it got erased by your booting into MacOS. Make sure you have the Open Firmware variable real-base set correct- ly. If your system is Open Firmware version 1.0.5, 1.1.22, 2.0.x, or 2.4, see the section above on _S_e_t_t_i_n_g _u_p _p_r_e_-_O_p_e_n _F_i_r_m_w_a_r_e _3 _t_o _b_o_o_t _N_e_t_B_S_D Do not set real-base on an Open Firmware 3 system. ++oo Hang after configuring devices, but before doing anything else Actually, this can have many causes. The most likely is a keyboard problem. First, try plugging the USB keyboard directly into the com- puter (i.e. not through a hub) and unplugging the mouse. This is also a known problem on some PowerMacintosh G3 (Blue and White) and iMac (Bondi Blue) machines. If you have a PowerMacintosh G3 (Blue and White) with this problem, then you can try the following procedure: 1. Unplug the USB keyboard and plug in an ADB keyboard 2. Boot NetBSD with the ADB keyboard 3. Enter root, swap and file system responses on the ADB keyboard 4. When the system gets to the shell prompt (or login if you went multi-user), unplug the ADB and plug in the USB keyboard The USB will be usable at this point and you can use the system. You'll notice that the ADB is dead even before you unplugged it. Al- so you _m_u_s_t boot without the USB installed or this won't work. Alternatively, much as it pains us to say this, NetBSD 1.4.3 works fine on both the iMac (Bondi Blue) and the PowerMacintosh G3 (Blue and White) models and does not have this USB keyboard problem. _M_i_l_e_s_t_o_n_e If you've reached this point, then you must've gotten the NetBSD in- staller to boot. Congratulations! That was the hard part. From now through the rest of this document, there should be no more Open Firmware specific problems, so read everything because it applies to all models. _R_u_n_n_i_n_g _t_h_e _s_y_s_i_n_s_t _i_n_s_t_a_l_l_a_t_i_o_n _p_r_o_g_r_a_m 1. _I_n_t_r_o_d_u_c_t_i_o_n Using ssyyssiinnsstt, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use. 2. _G_e_n_e_r_a_l The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. ssyyssiinnsstt is a menu driv- en installation system that allows for some freedom in doing the in- stallation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the in- stallation process again from scratch by running the _/_s_y_s_i_n_s_t pro- gram from the command prompt. It is not necessary to reboot. 3. _Q_u_i_c_k _i_n_s_t_a_l_l First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to the next section. This section describes a basic in- stallation, using a CD-ROM install as an example. ++oo What you need. -- The distribution sets (in this example, they are on CD). -- Some form of bootable media, described above. -- A CD-ROM drive (SCSI or ATAPI), a harddisk and a minimum of 8 MB of memory installed. -- The harddisk should have at least 200 + _n megabytes of space free, where _n is the number of megabytes of main memory in your system. If you wish to install the X Window System as well, you will need at least 60 MB more. ++oo The Quick Installation -- Boot the system as described above. You should be at the ssyyssiinnsstt main menu. .***********************************************. * NetBSD-1.6 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * x: Exit Install System * .***********************************************. -- If you wish, you can configure some network settings immedi- ately by choosing the UUttiilliittyy mmeennuu and then CCoonnffiigguurree nneettwwoorrkk. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. -- Choose iinnssttaallll. -- You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. -- After your disk has been prepared, choose CCDD--RROOMM as the medium. The default values for the path and device should be ok. -- After all the files have been unpacked, go back to the main menu and select rreebboooott.. -- Once the system reaches the Open Firmware prompt, you will need to type the correct command to boot from your hard drive. NetBSD will now boot. If you haven't already done so in ssyyssiinnsstt, you should log in as root, and set a password for that account. You are also advised to edit the file _/_e_t_c_/_r_c_._c_o_n_f to match your system needs. -- Your installation is now complete. -- For configuring the X window system, if installed, see the files in _/_u_s_r_/_X_1_1_R_6_/_l_i_b_/_X_1_1_/_d_o_c. Further information can be found on hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//xx1111..hhttmmll 4. _B_o_o_t_i_n_g _N_e_t_B_S_D You may want to read the boot messages, to notice your disk's name and capacity. Its name will be something like sd0 or wd0 and the geometry will be printed on a line that begins with its name. As mentioned above, you may need your disk's geometry when creating NetBSD 's partitions. You will also need to know the name, to tell ssyyssiinnsstt on which disk to install. The most important thing to know is that wd0 is NetBSD 's name for your first IDE disk, wd1 the sec- ond, etc. sd0 is your first SCSI disk, sd1 the second, etc. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. _N_e_t_w_o_r_k _c_o_n_f_i_g_u_r_a_t_i_o_n If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the UUttiilliittyy mmeennuu, and select the CCoonnffiigguurree nneettwwoorrkk option. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this. 6. _P_r_e_p_a_r_i_n_g _a _d_i_s_k _w_h_i_c_h _w_i_l_l _b_e _u_s_e_d _f_o_r Mac OS _a_n_d _N_e_t_B_S_D Skip this step if you are installing NetBSD onto a dedicated drive. Go to the UUttiilliittyy MMeennuu, and select the RRuunn //bbiinn//sshh option which will give you a shell prompt. From this shell prompt, you will do some of the steps that the normal install procedure runs automatically. Unfortunately, at the moment, our install tools aren't smart enough to deal with drives shared with Mac OS and will overwrite important information describing your partitions. 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 ''^^??'' Type the following command (replacing _w_d_0 with the name of your des- tination hard drive): # ddiisskkllaabbeell wwdd00 This will print out the partition info that was generated by Drive Setup. Note that, as discussed above in the _P_a_r_t_i_t_i_o_n_i_n_g _y_o_u_r _h_a_r_d _d_r_i_v_e _f_o_r _N_e_t_B_S_D section, your _A_/_U_X _R_o_o_t typically is the first par- tition (_a) and your _A_/_U_X _S_w_a_p typically is the second partition (_b). You may also find that your _A_/_U_X _U_s_e_r partition is the seventh par- tition (_g). For example: # ddiisskkllaabbeell wwdd00 [...] # size offset fstype [fsize bsize cpg/sgs] a: 426613 837432 4.2BSD 0 0 0 # (Cyl. 1622*- 2449*) b: 204800 632632 swap # (Cyl. 1226*- 1622*) c: 2134305 0 unused 0 0 # (Cyl. 0 - 4136*) d: 426616 1216 HFS # (Cyl. 2*- 829*) e: 204800 427832 HFS # (Cyl. 829*- 1226*) f: 21 2134284 unknown # (Cyl. 4136*- 4136*) g: 870239 1264045 4.2BSD 0 0 0 # (Cyl. 2449*- 4136*) disklabel: boot block size 0 disklabel: super block size 0 Now, you need to create file systems on the partitions that NetBSD will be using. _D_o _n_o_t _m_o_d_i_f_y _a_n_y _p_a_r_t_i_t_i_o_n_s _l_a_b_e_l_e_d _H_F_S _o_r _u_n_k_n_o_w_n. The partitions you will be using have their _f_s_t_y_p_e listed as _4_._2_B_S_D. Run the nneewwffss command on the _4_._2_B_S_D partitions: # nneewwffss //ddeevv//wwdd00aa newfs: /dev/sd1a: not a character-special device Warning: 120 sector(s) in last cylinder unallocated /dev/sd1a: 426612 sectors in 827 cylinders of 4 tracks, 129 sectors 208.3MB in 52 cyl groups (16 c/g, 4.03MB/g, 1024 i/g) super-block backups (for fsck -b #) at: 32, 8432, 16832, 25232, 33056, 41456, 49856, 58256, 66080, 74480, 82880, 91280, 99104, 107504, 115904, 124304, 132128, 140528, 148928, 157328, 165152, 173552, 181952, 190352, 198176, 206576, 214976, 223376, 231200, 239600, 248000, 256400, 264224, 272624, 281024, 289424, 297248, 305648, 314048, 322448, 330272, 338672, 347072, 355472, 363296, 371696, 380096, 388496, 396320, 404720, 413120, 421520, newfs: ioctl (WDINFO): Invalid argument newfs: /dev/sd1a: can't rewrite disk label You can ignore the `not a character-special device', `sector(s) in last cylinder unallocated', `ioctl (WDINFO): Invalid argument', and `can't rewrite disk label' warnings. Now you need to mount your destination root partition: # mmoouunntt //ddeevv//wwdd00aa //mmnntt Make an _f_s_t_a_b file for your new system (right now, you only really need to include _/, _/_u_s_r, and _s_w_a_p), for example: # mmkkddiirr //mmnntt//eettcc # ccaatt >> //mmnntt//eettcc//ffssttaabb /dev/wd0a / ffs rw 1 1 /dev/wd0b none swap sw 0 0 /dev/wd0g /usr ffs rw 1 2 If you mess up while typing, you can press CONTROL-U to erase every- thing on the current line, or CONTROL-C to cancel the file creation, so you can start over. Great, now create the mountpoints for the file systems you listed in the _f_s_t_a_b: # mmkkddiirr //mmnntt//uussrr Clean up and return to ssyyssiinnsstt: # ccdd //;;uummoouunntt //mmnntt # eexxiitt 7. _I_n_s_t_a_l_l_a_t_i_o_n _d_r_i_v_e _s_e_l_e_c_t_i_o_n _a_n_d _p_a_r_a_m_e_t_e_r_s To start the installation onto a dedicated NetBSD drive, select IInnssttaallll NNeettBBSSDD ttoo hhaarrdd ddiisskk from the main menu. To start the in- stallation onto a drive which will also be used with Mac OS, select RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss from the main menu. The first thing is to identify the disk on which you want to install NetBSD. ssyyssiinnsstt will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like wd0, wd1, sd0 or sd1. If ssyyssiinnsstt reports I can not find any hard disk for use by NetBSD or the drive you wish to install onto is missing, then you should look at the FAQ entry hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//ffaaqq..hhttmmll##nnooddiisskk 8. _P_a_r_t_i_t_i_o_n_i_n_g _t_h_e _d_i_s_k You can skip a few steps, down to `Getting the distribution sets', if you are installing onto a drive that will be used with Mac OS (i.e. you selected RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss from the main menu). 9. _E_d_i_t_i_n_g _t_h_e _N_e_t_B_S_D _d_i_s_k_l_a_b_e_l The partition table of the NetBSD part of a disk is called a _d_i_s_k_l_a_b_e_l. In actuality, NetBSD/macppc uses an Apple Partition Map. The installer creates something like a real Apple Partition Map, but it is not compatible with Mac OS, which is one of the reasons why you cannot use this installer to partition a disk that can be used with Mac OS. There are 4 layouts for the NetBSD part of the disk that you can pick from: SSttaannddaarrdd,, SSttaannddaarrdd wwiitthh XX,, CCuussttoomm and UUssee EExxiissttiinngg. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the CCuussttoomm option you can specify everything yourself. The last option uses the partition info already present on the disk. You will be presented with the current layout of the NetBSD diskla- bel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 44..22BBSSDD. A swap partition has a special type called sswwaapp. Some partitions in the disklabel have a fixed purpose. a Root partition (_/) b Swap partition. c The NetBSD portion of the disk. d-p Available for other use. Traditionally, g is the par- tition mounted on _/_u_s_r, but this is historical prac- tice and not a fixed value. You will then be asked to name your disk's disklabel. The default response is ``mmyyddiisskk''. For most purposes this will be OK. If you choose to name it something different, make sure the name is a sin- gle word and contains no special characters. You don't need to re- member this name. 10. _P_r_e_p_a_r_i_n_g _y_o_u_r _h_a_r_d _d_i_s_k _Y_o_u _a_r_e _n_o_w _a_t _t_h_e _p_o_i_n_t _o_f _n_o _r_e_t_u_r_n. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to pro- ceed, enter yes at the prompt. The install program will now label your disk and make the file sys- tems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installa- tion program after pressing the return key. _N_o_t_e_: The bootstrapping code installed in this step will _n_o_t boot a machine with Open Firmware 3. You will still need to have _o_f_w_b_o_o_t_._x_c_f on an HFS or HFS+ partition. 11. _G_e_t_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s The NetBSD distribution consists of a number of _s_e_t_s, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installa- tion, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to section labeled `Extracting the distribution sets'. 12. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _f_t_p To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server. ssyyssiinnsstt will proceed to transfer all the default set files from the remote site to your hard disk. 13. _I_n_s_t_a_l_l_a_t_i_o_n _u_s_i_n_g _N_F_S To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. ssyyssiinnsstt will do this for you, asking you to provide some data, like IP address, hostname, etc. If you do not have name ser- vice set up for the machine that you are installing on, you can just press RETURN in answer to these questions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server. 14. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _C_D_-_R_O_M When installing from a CD-ROM, you will be asked to specify the de- vice name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are. ssyyssiinnsstt will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 15. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a_n _u_n_m_o_u_n_t_e_d _f_i_l_e _s_y_s_t_e_m In order to install from a local file system, you will need to spec- ify the device that the file system resides on (for example sd1e) the type of the file system, and the directory on the specified file system where the sets are located. ssyyssiinnsstt will then check if it can indeed access the sets at that location. Remember, NetBSD/macppc doesn't grok HFS or HFS+ partitions 16. _I_n_s_t_a_l_l_a_t_i_o_n _f_r_o_m _a _l_o_c_a_l _d_i_r_e_c_t_o_r_y This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file sys- tem that is already accessible. ssyyssiinnsstt will ask you for the name of this directory. 17. _E_x_t_r_a_c_t_i_n_g _t_h_e _d_i_s_t_r_i_b_u_t_i_o_n _s_e_t_s After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full instal- lation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kkeerrnn,, bbaassee) and eettcc they will not be shown in this se- lection menu. Before extraction begins, you can elect to watch the files being ex- tracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles. If you are installing using the RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss option, then you will need to create the device nodes in _/_d_e_v, otherwise, all the necessary device node files will be created. If you have already configured networking, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the network configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can than set a password for the "root" account, to prevent the machine coming up without access restrictions. 18. _M_a_k_i_n_g _t_h_e _d_e_v_i_c_e _n_o_d_e_s If you are installing using the RRee--iinnssttaallll sseettss oorr iinnssttaallll aaddddiittiioonnaall sseettss option, then you will need to create the device nodes in _/_d_e_v now. Otherwise, skip this step. Go to the main installation menu, and select UUttiilliittyy mmeennuu and then select the RRuunn //bbiinn//sshh option, which will give you a shell prompt. 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 ''^^??'' Type the following command (replacing _w_d_0_a with the partition name of your destination root partition): Now you need to mount your des- tination root partition: # mmoouunntt //ddeevv//wwdd00aa //mmnntt # ccdd //mmnntt//ddeevv # sshh MMAAKKEEDDEEVV aallll # ccdd //;;uummoouunntt //mmnntt # eexxiitt 19. _F_i_n_a_l_i_z_i_n_g _y_o_u_r _i_n_s_t_a_l_l_a_t_i_o_n Congratulations, you have successfully installed NetBSD 1.6.1. Now, you can reboot to get to the Open Firmware prompt. Once there, you can set Open Firmware to always boot into NetBSD from the media of your choice. First, make sure you know what command you need to boot (see above). If you are using a `partition zero' style boot scheme, you would type something like the following: 0 > sseetteennvv aauuttoo--bboooott?? ttrruuee 0 > sseetteennvv bboooott--ddeevviiccee ssccssii//ssdd@@00::00 0 > sseetteennvv bboooott--ffiillee nneettbbssdd 0 > rreesseett--aallll The last command resets the system so that these settings are stored. Replace ssccssii//ssdd@@00::00 with the actual device you will be booting from. If you find that your system tries booting before your hard drive has spun up, you may need to also enter something like: 0 > sseetteennvv bboooott--ccoommmmaanndd bbeeggiinn [['']] bboooott ccaattcchh If you are not using a `partition zero' style boot scheme, then you can still plug in all the information you need: 0 > sseetteennvv aauuttoo--bboooott?? ttrruuee 0 > sseetteennvv bboooott--ddeevviiccee iiddee00//ddiisskk@@00::88,,\\ooffwwbboooott..xxccff 0 > sseetteennvv bboooott--ffiillee iiddee00//ddiisskk@@00::1133,,//nneettbbssdd 0 > rreesseett--aallll PPoosstt iinnssttaallllaattiioonn sstteeppss Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below. 1. Configuring _/_e_t_c_/_r_c_._c_o_n_f If you or the installation software haven't done any configuration of _/_e_t_c_/_r_c_._c_o_n_f (ssyyssiinnsstt usually will), the system will drop you in- to single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (_/) mounted read-only. When the sys- tem asks you to choose a shell, simply press RETURN to get to a _/_b_i_n_/_s_h prompt. If you are asked for a terminal type, respond with vvtt110000 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # ssttttyy eerraassee ''^^hh'' # ssttttyy eerraassee ''^^??'' At this point, you need to configure at least one file in the _/_e_t_c directory. You will need to mount your root file system read/write with: # //ssbbiinn//mmoouunntt --uu --ww // Change to the _/_e_t_c directory and take a look at the _/_e_t_c_/_r_c_._c_o_n_f file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in _/_e_t_c_/_d_e_f_a_u_l_t_s_/_r_c_._c_o_n_f, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). If your _/_u_s_r directory is on a separate partition and you do not know how to use eedd, you will have to mount your _/_u_s_r partition to gain access to eexx or vvii. Do the following: # mmoouunntt //uussrr # eexxppoorrtt TTEERRMM==vvtt110000 If you have _/_v_a_r on a separate partition, you need to repeat that step for it. After that, you can edit _/_e_t_c_/_r_c_._c_o_n_f with vi(1). When you have finished, type eexxiitt at the prompt to leave the single- user shell and continue with the multi-user boot. Other values that need to be set in _/_e_t_c_/_r_c_._c_o_n_f for a networked en- vironment are _h_o_s_t_n_a_m_e and possibly _d_e_f_a_u_l_t_r_o_u_t_e, furthermore add an _i_f_c_o_n_f_i_g___i_n_t for your network interface, where your on-board interfaces may be one of mc0, bm0, de0 or gm0. For example: ifconfig_mc0="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_mc0="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. Also, you may want to read through the NetBSD/macppc X11R6 FAQ. hhttttpp::////wwwwww..nneettbbssdd..oorrgg//PPoorrttss//mmaaccppppcc//xx1111..hhttmmll 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 list of available packages suitable for browsing 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_._6_._1_/_m_a_c_p_p_c_/_A_l_l subdir. You can install them with the following commands: ## PPKKGG__PPAATTHH==ffttpp::////ffttpp..nneettbbssdd..oorrgg//ppuubb//NNeettBBSSDD//ppaacckkaaggeess//11..66..11//mmaaccppppcc//AAllll ## eexxppoorrtt PPKKGG__PPAATTHH ## ppkkgg__aadddd --vv ttccsshh ## ppkkgg__aadddd --vv aappaacchhee ## ppkkgg__aadddd --vv ppeerrll ... The above commands will install the tcsh shell, the Apache web server and the perl programming language as well as all the packages they depend on. ++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.6.1 is a binary upgrade; it can be quite diffi- cult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components. To do the upgrade, you must boot from the installer kernel using one of the methods described above. You must also have at least the bbaassee and kkeerrnn binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previously in- stalled or to account for growth of the sets between releases. If you have a few megabytes free on each of your root (_/) and _/_u_s_r partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your NetBSD parti- tion, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to _b_a_c_k _u_p any important data on your disk, whether on the NetBSD partition or on another operat- ing system's partition, before beginning the upgrade process. Since in- stallation of the bootloader will prevent Mac OS from using the disk and will prevent Open Firmware 3 machines from booting, there is an option to bypass this step. Make sure you know whether or not to install the boot- loader. The upgrade procedure using the ssyyssiinnsstt tool is similar to an installa- tion, but without the hard disk partitioning. The original _/_e_t_c directo- ry is renamed to _/_e_t_c_._o_l_d, and no attempt is made to merge any of the previous configuration into the new system except that the previous _/_e_t_c_/_f_s_t_a_b file is copied into the new configuration. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some sanity checks are done, i.e. file systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.6.1 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in _/_d_e_v. If you've changed the contents of _/_d_e_v by hand, you will need to be careful about this, but if not, you can just cd into _/_d_e_v, and run the command: # sshh MMAAKKEEDDEEVV aallll Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. CCoommppaattiibbiilliittyy IIssssuueess WWiitthh PPrreevviioouuss NNeettBBSSDD RReelleeaasseess Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.6.1. _I_s_s_u_e_s _a_f_f_e_c_t_i_n_g _a_n _u_p_g_r_a_d_e _f_r_o_m _N_e_t_B_S_D _1_._5 The following issues can generally be resolved by extracting the eettcc set into a temporary directory and running _p_o_s_t_i_n_s_t_a_l_l: mkdir /tmp/upgrade cd /tmp/upgrade pax -zrpe -f /path/to/etc.tgz ./etc/postinstall -s `pwd` check ./etc/postinstall -s `pwd` fix Issues fixed by _p_o_s_t_i_n_s_t_a_l_l: ++oo Various files in _/_e_t_c need upgrading. These include: -- _/_e_t_c_/_d_e_f_a_u_l_t_s_/_* -- _/_e_t_c_/_m_t_r_e_e_/_* -- _/_e_t_c_/_d_a_i_l_y -- _/_e_t_c_/_w_e_e_k_l_y -- _/_e_t_c_/_m_o_n_t_h_l_y -- _/_e_t_c_/_s_e_c_u_r_i_t_y -- _/_e_t_c_/_r_c_._s_u_b_r -- _/_e_t_c_/_r_c -- _/_e_t_c_/_r_c_._s_h_u_t_d_o_w_n -- _/_e_t_c_/_r_c_._d_/_* ++oo The following files are now obsolete: _/_e_t_c_/_r_c_._d_/_N_E_T_W_O_R_K and _/_e_t_c_/_r_c_._d_/_g_a_t_e_d. ++oo The following rc.conf(5) entries are now obsolete: amd_master, ip6forwarding, defcorename, and nfsiod_flags. critical_filesystems_beforenet has been replaced by critical_filesystems_local. critical_filesystems has been re- placed by critical_filesystems_remote. ++oo The users and groups `named', `ntpd', and `sshd' need to be created. ++oo The configuration files for ssh(1) and sshd(8) were moved from _/_e_t_c to _/_e_t_c_/_s_s_h, including _s_s_h___k_n_o_w_n___h_o_s_t_s_* files and the host key files _s_s_h___h_o_s_t_*___k_e_y_*. _/_e_t_c_/_s_s_h_._c_o_n_f was renamed to _/_e_t_c_/_s_s_h_/_s_s_h___c_o_n_f_i_g, and _/_e_t_c_/_s_s_h_d_._c_o_n_f was renamed to _/_e_t_c_/_s_s_h_/_s_s_h_d___c_o_n_f_i_g. ++oo The mmuuxx entries in wscons.conf(5) are now obsolete. The following issues need to be resolved manually: ++oo postfix(8) configuration files require upgrading. cd /usr/share/examples/postfix cp post-install postfix-files postfix-script /etc/postfix postfix check ++oo The _d_e ethernet driver was replaced with the _t_l_p driver. This may require the renaming of the files _/_e_t_c_/_i_f_c_o_n_f_i_g_._d_e_* to _/_e_t_c_/_i_f_c_o_n_f_i_g_._t_l_p_*, renaming of rc.conf(5) entries ifconfig_de* to ifconfig_tlp*, and the reconfiguration of files such as _/_e_t_c_/_d_h_c_l_i_e_n_t_._c_o_n_f and _/_e_t_c_/_i_p_f_._c_o_n_f. _I_s_s_u_e_s _a_f_f_e_c_t_i_n_g _a_n _u_p_g_r_a_d_e _f_r_o_m _N_e_t_B_S_D _1_._4 _o_r _p_r_i_o_r ++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. ++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) was moved from _/_u_s_r_/_s_b_i_n_/_s_y_s_c_t_l to _/_s_b_i_n_/_s_y_s_c_t_l. If you have hardcoded references to the full pathname (in shell scripts, for example) please be sure to update those. ++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 include lots of details. Additionally, bug reports can be sent by mail to: _n_e_t_b_s_d_-_b_u_g_s_@_n_e_t_b_s_d_._o_r_g. Use of send-pr(1) is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit hhttttpp::////wwwwww..nneettbbssdd..oorrgg//MMaaiilliinnggLLiissttss//. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed be- low). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: _n_e_t_b_s_d_-_h_e_l_p_@_n_e_t_b_s_d_._o_r_g. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. TThhaannkkss ggoo ttoo ++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 Luke Mewburn Toru Nishimura Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Eric and Rosemary Spahr Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Rob Windsor Jim Wise Reinoud Zandijk Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Distributed Processing Technology Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. Precedence Technologies Ltd Salient Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. Whitecross Database Systems Ltd. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) ++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_)_: Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g ssbbmmiippss Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g ssuunn33xx Matt Fredette _f_r_e_d_e_t_t_e_@_n_e_t_b_s_d_._o_r_g ssuunn22 Chris Gilbert _c_h_r_i_s_@_n_e_t_b_s_d_._o_r_g ccaattss Ross Harvey _r_o_s_s_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g sshh33 Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g aaccoorrnn2266 Eduardo Horvath _e_e_h_@_n_e_t_b_s_d_._o_r_g ssppaarrcc6644 Darrin Jewell _d_b_j_@_n_e_t_b_s_d_._o_r_g nneexxtt6688kk S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ccoobbaalltt S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g ssggiimmiippss Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g mmiippssccoo Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g ssppaarrcc Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g ii338866 Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g vvaaxx Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g ppcc553322 NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g xx6688kk Tohru Nishimura _n_i_s_i_m_u_r_a_@_n_e_t_b_s_d_._o_r_g lluunnaa6688kk NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g pprreepp Scott Reynolds _s_c_o_t_t_r_@_n_e_t_b_s_d_._o_r_g mmaacc6688kk Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g bbeebbooxx Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g aarrcc Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g ooffppppcc Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g aammiiggaa Jonathan Stone _j_o_n_a_t_h_a_n_@_n_e_t_b_s_d_._o_r_g ppmmaaxx Shin Takemura _t_a_k_e_m_u_r_a_@_n_e_t_b_s_d_._o_r_g hhppccmmiippss Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g aallpphhaa Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g hhpp330000 Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g mmaaccppppcc Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g nneewwssmmiippss Izumi Tsutsui _t_s_u_t_s_u_i_@_n_e_t_b_s_d_._o_r_g nneewwss6688kk Leo Weppelman _l_e_o_@_n_e_t_b_s_d_._o_r_g aattaarrii Nathan Williams _n_a_t_h_a_n_w_@_n_e_t_b_s_d_._o_r_g ssuunn33 Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmee6688kk Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g mmvvmmeeppppcc Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g aaccoorrnn3322 _T_h_e _N_e_t_B_S_D _1_._6_._1 _R_e_l_e_a_s_e _E_n_g_i_n_e_e_r_i_n_g _t_e_a_m_: Erik Berls _c_y_b_e_r_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g Luke Mewburn _l_u_k_e_m_@_n_e_t_b_s_d_._o_r_g Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g _N_e_t_B_S_D _D_e_v_e_l_o_p_e_r_s_: Nathan Ahlstrom _n_r_a_@_n_e_t_b_s_d_._o_r_g Steve Allen _w_o_r_m_e_y_@_n_e_t_b_s_d_._o_r_g Julian Assange _p_r_o_f_f_@_n_e_t_b_s_d_._o_r_g Lennart Augustsson _a_u_g_u_s_t_s_s_@_n_e_t_b_s_d_._o_r_g Christoph Badura _b_a_d_@_n_e_t_b_s_d_._o_r_g Bang Jun-Young _j_u_n_y_o_u_n_g_@_n_e_t_b_s_d_._o_r_g Dieter Baron _d_i_l_l_o_@_n_e_t_b_s_d_._o_r_g Robert V. Baron _r_v_b_@_n_e_t_b_s_d_._o_r_g Jason Beegan _j_t_b_@_n_e_t_b_s_d_._o_r_g Erik Berls _c_y_b_e_r_@_n_e_t_b_s_d_._o_r_g Hiroyuki Bessho _b_s_h_@_n_e_t_b_s_d_._o_r_g John Birrell _j_b_@_n_e_t_b_s_d_._o_r_g Mason Loring Bliss _m_a_s_o_n_@_n_e_t_b_s_d_._o_r_g Rafal Boni _r_a_f_a_l_@_n_e_t_b_s_d_._o_r_g Manuel Bouyer _b_o_u_y_e_r_@_n_e_t_b_s_d_._o_r_g John Brezak _b_r_e_z_a_k_@_n_e_t_b_s_d_._o_r_g Allen Briggs _b_r_i_g_g_s_@_n_e_t_b_s_d_._o_r_g Mark Brinicombe _m_a_r_k_@_n_e_t_b_s_d_._o_r_g Aaron Brown _a_b_r_o_w_n_@_n_e_t_b_s_d_._o_r_g Andrew Brown _a_t_a_t_a_t_@_n_e_t_b_s_d_._o_r_g David Brownlee _a_b_s_@_n_e_t_b_s_d_._o_r_g Frederick Bruckman _f_r_e_d_b_@_n_e_t_b_s_d_._o_r_g Jon Buller _j_o_n_b_@_n_e_t_b_s_d_._o_r_g Simon Burge _s_i_m_o_n_b_@_n_e_t_b_s_d_._o_r_g Robert Byrnes _b_y_r_n_e_s_@_n_e_t_b_s_d_._o_r_g D'Arcy J.M. Cain _d_a_r_c_y_@_n_e_t_b_s_d_._o_r_g Dave Carrel _c_a_r_r_e_l_@_n_e_t_b_s_d_._o_r_g James Chacon _j_m_c_@_n_e_t_b_s_d_._o_r_g Bill Coldwell _b_i_l_l_c_@_n_e_t_b_s_d_._o_r_g Julian Coleman _j_d_c_@_n_e_t_b_s_d_._o_r_g Jeremy Cooper _j_e_r_e_m_y_@_n_e_t_b_s_d_._o_r_g Chuck Cranor _c_h_u_c_k_@_n_e_t_b_s_d_._o_r_g Alistair Crooks _a_g_c_@_n_e_t_b_s_d_._o_r_g Aidan Cully _a_i_d_a_n_@_n_e_t_b_s_d_._o_r_g Johan Danielsson _j_o_d_a_@_n_e_t_b_s_d_._o_r_g Matt DeBergalis _d_e_b_e_r_g_@_n_e_t_b_s_d_._o_r_g Rob Deker _d_e_k_e_r_@_n_e_t_b_s_d_._o_r_g Chris G. Demetriou _c_g_d_@_n_e_t_b_s_d_._o_r_g Tracy Di Marco White _g_e_n_d_a_l_i_a_@_n_e_t_b_s_d_._o_r_g Jarom'ir Dolecek _j_d_o_l_e_c_e_k_@_n_e_t_b_s_d_._o_r_g Andy Doran _a_d_@_n_e_t_b_s_d_._o_r_g Roland Dowdeswell _e_l_r_i_c_@_n_e_t_b_s_d_._o_r_g Emmanuel Dreyfus _m_a_n_u_@_n_e_t_b_s_d_._o_r_g Matthias Drochner _d_r_o_c_h_n_e_r_@_n_e_t_b_s_d_._o_r_g Jun Ebihara _j_u_n_@_n_e_t_b_s_d_._o_r_g Hoavard Eidnes _h_e_@_n_e_t_b_s_d_._o_r_g Stoned Elipot _s_e_b_@_n_e_t_b_s_d_._o_r_g Enami Tsugutomo _e_n_a_m_i_@_n_e_t_b_s_d_._o_r_g Bernd Ernesti _v_e_e_g_o_@_n_e_t_b_s_d_._o_r_g Erik Fair _f_a_i_r_@_n_e_t_b_s_d_._o_r_g Gavan Fantom _g_a_v_a_n_@_n_e_t_b_s_d_._o_r_g Hubert Feyrer _h_u_b_e_r_t_f_@_n_e_t_b_s_d_._o_r_g Jason R. Fink _j_r_f_@_n_e_t_b_s_d_._o_r_g Matt Fredette _f_r_e_d_e_t_t_e_@_n_e_t_b_s_d_._o_r_g Thorsten Frueauf _f_r_u_e_a_u_f_@_n_e_t_b_s_d_._o_r_g Castor Fu _c_a_s_t_o_r_@_n_e_t_b_s_d_._o_r_g Ichiro Fukuhara _i_c_h_i_r_o_@_n_e_t_b_s_d_._o_r_g Thomas Gerner _t_h_o_m_a_s_@_n_e_t_b_s_d_._o_r_g Simon J. Gerraty _s_j_g_@_n_e_t_b_s_d_._o_r_g Justin Gibbs _g_i_b_b_s_@_n_e_t_b_s_d_._o_r_g Chris Gilbert _c_h_r_i_s_@_n_e_t_b_s_d_._o_r_g Adam Glass _g_l_a_s_s_@_n_e_t_b_s_d_._o_r_g Michael Graff _e_x_p_l_o_r_e_r_@_n_e_t_b_s_d_._o_r_g Brian C. Grayson _b_g_r_a_y_s_o_n_@_n_e_t_b_s_d_._o_r_g Matthew Green _m_r_g_@_n_e_t_b_s_d_._o_r_g Andreas Gustafsson _g_s_o_n_@_n_e_t_b_s_d_._o_r_g Jun-ichiro itojun Hagino _i_t_o_j_u_n_@_n_e_t_b_s_d_._o_r_g Juergen Hannken-Illjes _h_a_n_n_k_e_n_@_n_e_t_b_s_d_._o_r_g Charles M. Hannum _m_y_c_r_o_f_t_@_n_e_t_b_s_d_._o_r_g Ben Harris _b_j_h_2_1_@_n_e_t_b_s_d_._o_r_g Ross Harvey _r_o_s_s_@_n_e_t_b_s_d_._o_r_g Eric Haszlakiewicz _e_r_h_@_n_e_t_b_s_d_._o_r_g John Hawkinson _j_h_a_w_k_@_n_e_t_b_s_d_._o_r_g HAYAKAWA Koichi _h_a_y_a_@_n_e_t_b_s_d_._o_r_g Ren'e Hexel _r_h_@_n_e_t_b_s_d_._o_r_g Michael L. Hitch _m_h_i_t_c_h_@_n_e_t_b_s_d_._o_r_g Christian E. Hopps _c_h_o_p_p_s_@_n_e_t_b_s_d_._o_r_g Ken Hornstein _k_e_n_h_@_n_e_t_b_s_d_._o_r_g Marc Horowitz _m_a_r_c_@_n_e_t_b_s_d_._o_r_g Eduardo Horvath _e_e_h_@_n_e_t_b_s_d_._o_r_g Nick Hudson _s_k_r_l_l_@_n_e_t_b_s_d_._o_r_g Shell Hung _s_h_e_l_l_@_n_e_t_b_s_d_._o_r_g Martin Husemann _m_a_r_t_i_n_@_n_e_t_b_s_d_._o_r_g Dean Huxley _d_e_a_n_@_n_e_t_b_s_d_._o_r_g Bernardo Innocenti _b_e_r_n_i_e_@_n_e_t_b_s_d_._o_r_g Tetsuya Isaki _i_s_a_k_i_@_n_e_t_b_s_d_._o_r_g ITOH Yasufumi _i_t_o_h_y_@_n_e_t_b_s_d_._o_r_g IWAMOTO Toshihiro _t_o_s_h_i_i_@_n_e_t_b_s_d_._o_r_g Matthew Jacob _m_j_a_c_o_b_@_n_e_t_b_s_d_._o_r_g Lonhyn T. Jasinskyj _l_o_n_h_y_n_@_n_e_t_b_s_d_._o_r_g Darrin Jewell _d_b_j_@_n_e_t_b_s_d_._o_r_g Chris Jones _c_j_o_n_e_s_@_n_e_t_b_s_d_._o_r_g S/oren J/orvang _s_o_r_e_n_@_n_e_t_b_s_d_._o_r_g Takahiro Kambe _t_a_c_a_@_n_e_t_b_s_d_._o_r_g Antti Kantee _p_o_o_k_a_@_n_e_t_b_s_d_._o_r_g Masanori Kanaoka _k_a_n_a_o_k_a_@_n_e_t_b_s_d_._o_r_g Mattias Karlsson _k_e_i_h_a_n_@_n_e_t_b_s_d_._o_r_g KAWAMOTO Yosihisa _k_a_w_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g Mario Kemper _m_a_g_i_c_k_@_n_e_t_b_s_d_._o_r_g Thomas Klausner _w_i_z_@_n_e_t_b_s_d_._o_r_g Klaus Klein _k_l_e_i_n_k_@_n_e_t_b_s_d_._o_r_g Wayne Knowles _w_d_k_@_n_e_t_b_s_d_._o_r_g John Kohl _j_t_k_@_n_e_t_b_s_d_._o_r_g Paul Kranenburg _p_k_@_n_e_t_b_s_d_._o_r_g Martti Kuparinen _m_a_r_t_t_i_@_n_e_t_b_s_d_._o_r_g Kevin Lahey _k_m_l_@_n_e_t_b_s_d_._o_r_g Johnny C. Lam _j_l_a_m_@_n_e_t_b_s_d_._o_r_g Martin J. Laubach _m_j_l_@_n_e_t_b_s_d_._o_r_g Ted Lemon _m_e_l_l_o_n_@_n_e_t_b_s_d_._o_r_g Frank van der Linden _f_v_d_l_@_n_e_t_b_s_d_._o_r_g Joel Lindholm _j_o_e_l_@_n_e_t_b_s_d_._o_r_g Mike Long _m_i_k_e_l_@_n_e_t_b_s_d_._o_r_g Warner Losh _i_m_p_@_n_e_t_b_s_d_._o_r_g Tomasz Luchowski _z_u_n_t_u_m_@_n_e_t_b_s_d_._o_r_g Federico Lupi _f_e_d_e_r_i_c_o_@_n_e_t_b_s_d_._o_r_g Brett Lymn _b_l_y_m_n_@_n_e_t_b_s_d_._o_r_g Paul Mackerras _p_a_u_l_u_s_@_n_e_t_b_s_d_._o_r_g Anders Magnusson _r_a_g_g_e_@_n_e_t_b_s_d_._o_r_g MAEKAWA Masahide _g_e_h_e_n_n_a_@_n_e_t_b_s_d_._o_r_g David Maxwell _d_a_v_i_d_@_n_e_t_b_s_d_._o_r_g Dan McMahill _d_m_c_m_a_h_i_l_l_@_n_e_t_b_s_d_._o_r_g Gregory McGarry _g_m_c_g_a_r_r_y_@_n_e_t_b_s_d_._o_r_g Jared D. McNeill _j_m_c_n_e_i_l_l_@_n_e_t_b_s_d_._o_r_g Neil J. McRae _n_e_i_l_@_n_e_t_b_s_d_._o_r_g Perry Metzger _p_e_r_r_y_@_n_e_t_b_s_d_._o_r_g Minoura Makoto _m_i_n_o_u_r_a_@_n_e_t_b_s_d_._o_r_g Luke Mewburn _l_u_k_e_m_@_n_e_t_b_s_d_._o_r_g der Mouse _m_o_u_s_e_@_n_e_t_b_s_d_._o_r_g Joseph Myers _j_s_m_@_n_e_t_b_s_d_._o_r_g Ken Nakata _k_e_n_n_@_n_e_t_b_s_d_._o_r_g Phil Nelson _p_h_i_l_@_n_e_t_b_s_d_._o_r_g Bob Nestor _r_n_e_s_t_o_r_@_n_e_t_b_s_d_._o_r_g NISHIMURA Takeshi _n_s_m_r_t_k_s_@_n_e_t_b_s_d_._o_r_g Tohru Nishimura _n_i_s_i_m_u_r_a_@_n_e_t_b_s_d_._o_r_g NONAKA Kimihiro _n_o_n_a_k_a_@_n_e_t_b_s_d_._o_r_g Jesse Off _j_o_f_f_@_n_e_t_b_s_d_._o_r_g Tatoku Ogaito _t_a_c_h_a_@_n_e_t_b_s_d_._o_r_g Masaru Oki _o_k_i_@_n_e_t_b_s_d_._o_r_g Atsushi Onoe _o_n_o_e_@_n_e_t_b_s_d_._o_r_g Greg Oster _o_s_t_e_r_@_n_e_t_b_s_d_._o_r_g Herb Peyerl _h_p_e_y_e_r_l_@_n_e_t_b_s_d_._o_r_g Matthias Pfaller _m_a_t_t_h_i_a_s_@_n_e_t_b_s_d_._o_r_g Chris Pinnock _c_j_e_p_@_n_e_t_b_s_d_._o_r_g Dante Profeta _d_a_n_t_e_@_n_e_t_b_s_d_._o_r_g Chris Provenzano _p_r_o_v_e_n_@_n_e_t_b_s_d_._o_r_g Michael Rauch _m_r_a_u_c_h_@_n_e_t_b_s_d_._o_r_g Darren Reed _d_a_r_r_e_n_r_@_n_e_t_b_s_d_._o_r_g Scott Reynolds _s_c_o_t_t_r_@_n_e_t_b_s_d_._o_r_g Michael Richardson _m_c_r_@_n_e_t_b_s_d_._o_r_g Tim Rightnour _g_a_r_b_l_e_d_@_n_e_t_b_s_d_._o_r_g Gordon Ross _g_w_r_@_n_e_t_b_s_d_._o_r_g Heiko W. Rupp _h_w_r_@_n_e_t_b_s_d_._o_r_g David Sainty _d_s_a_i_n_t_y_@_n_e_t_b_s_d_._o_r_g SAITOH Masanobu _m_s_a_i_t_o_h_@_n_e_t_b_s_d_._o_r_g Kazuki Sakamoto _s_a_k_a_m_o_t_o_@_n_e_t_b_s_d_._o_r_g Curt Sampson _c_j_s_@_n_e_t_b_s_d_._o_r_g Wilfredo Sanchez _w_s_a_n_c_h_e_z_@_n_e_t_b_s_d_._o_r_g Ty Sarna _t_s_a_r_n_a_@_n_e_t_b_s_d_._o_r_g SATO Kazumi _s_a_t_o_@_n_e_t_b_s_d_._o_r_g Jan Schaumann _j_s_c_h_a_u_m_a_@_n_e_t_b_s_d_._o_r_g Matthias Scheler _t_r_o_n_@_n_e_t_b_s_d_._o_r_g Karl Schilke (rAT) _r_a_t_@_n_e_t_b_s_d_._o_r_g Amitai Schlair _s_c_h_m_o_n_z_@_n_e_t_b_s_d_._o_r_g Konrad Schroder _p_e_r_s_e_a_n_t_@_n_e_t_b_s_d_._o_r_g Reed Shadgett _d_e_n_t_@_n_e_t_b_s_d_._o_r_g Tim Shepard _s_h_e_p_@_n_e_t_b_s_d_._o_r_g Takeshi Shibagaki _s_h_i_b_a_@_n_e_t_b_s_d_._o_r_g Takao Shinohara _s_h_i_n_@_n_e_t_b_s_d_._o_r_g Takuya SHIOZAKI _t_s_h_i_o_z_a_k_@_n_e_t_b_s_d_._o_r_g Chuck Silvers _c_h_s_@_n_e_t_b_s_d_._o_r_g Thor Lancelot Simon _t_l_s_@_n_e_t_b_s_d_._o_r_g Jeff Smith _j_e_f_f_s_@_n_e_t_b_s_d_._o_r_g Noriyuki Soda _s_o_d_a_@_n_e_t_b_s_d_._o_r_g Wolfgang Solfrank _w_s_@_n_e_t_b_s_d_._o_r_g SOMEYA Yoshihiko _s_o_m_e_y_a_@_n_e_t_b_s_d_._o_r_g Bill Sommerfeld _s_o_m_m_e_r_f_e_l_d_@_n_e_t_b_s_d_._o_r_g Ignatios Souvatzis _i_s_@_n_e_t_b_s_d_._o_r_g Bill Squier _g_r_o_o_@_n_e_t_b_s_d_._o_r_g Jonathan Stone _j_o_n_a_t_h_a_n_@_n_e_t_b_s_d_._o_r_g Bill Studenmund _w_r_s_t_u_d_e_n_@_n_e_t_b_s_d_._o_r_g Kevin Sullivan _s_u_l_l_i_v_a_n_@_n_e_t_b_s_d_._o_r_g SUNAGAWA Keiki _k_e_i_@_n_e_t_b_s_d_._o_r_g Kimmo Suominen _k_i_m_@_n_e_t_b_s_d_._o_r_g Shin Takemura _t_a_k_e_m_u_r_a_@_n_e_t_b_s_d_._o_r_g TAMURA Kent _k_e_n_t_@_n_e_t_b_s_d_._o_r_g Shin'ichiro TAYA _t_a_y_a_@_n_e_t_b_s_d_._o_r_g Matt Thomas _m_a_t_t_@_n_e_t_b_s_d_._o_r_g Jason Thorpe _t_h_o_r_p_e_j_@_n_e_t_b_s_d_._o_r_g Christoph Toshok _t_o_s_h_o_k_@_n_e_t_b_s_d_._o_r_g Tsubai Masanari _t_s_u_b_a_i_@_n_e_t_b_s_d_._o_r_g Izumi Tsutsui _t_s_u_t_s_u_i_@_n_e_t_b_s_d_._o_r_g UCHIYAMA Yasushi _u_c_h_@_n_e_t_b_s_d_._o_r_g Masao Uebayashi _u_e_b_a_y_a_s_i_@_n_e_t_b_s_d_._o_r_g Shuichiro URATA _u_r_@_n_e_t_b_s_d_._o_r_g Todd Vierling _t_v_@_n_e_t_b_s_d_._o_r_g Aymeric Vincent _a_y_m_e_r_i_c_@_n_e_t_b_s_d_._o_r_g Paul Vixie _v_i_x_i_e_@_n_e_t_b_s_d_._o_r_g Krister Walfridsson _k_r_i_s_t_e_r_w_@_n_e_t_b_s_d_._o_r_g Lex Wennmacher _w_e_n_n_m_a_c_h_@_n_e_t_b_s_d_._o_r_g Leo Weppelman _l_e_o_@_n_e_t_b_s_d_._o_r_g Assar Westerlund _a_s_s_a_r_@_n_e_t_b_s_d_._o_r_g Todd Whitesel _t_o_d_d_p_w_@_n_e_t_b_s_d_._o_r_g Nathan Williams _n_a_t_h_a_n_w_@_n_e_t_b_s_d_._o_r_g Rob Windsor _w_i_n_d_s_o_r_@_n_e_t_b_s_d_._o_r_g Dan Winship _d_a_n_w_@_n_e_t_b_s_d_._o_r_g Jim Wise _j_w_i_s_e_@_n_e_t_b_s_d_._o_r_g Michael Wolfson _m_b_w_@_n_e_t_b_s_d_._o_r_g Steve Woodford _s_c_w_@_n_e_t_b_s_d_._o_r_g Colin Wood _e_n_d_e_r_@_n_e_t_b_s_d_._o_r_g YAMAMOTO Takashi _y_a_m_t_@_n_e_t_b_s_d_._o_r_g Yuji Yamano _y_y_a_m_a_n_o_@_n_e_t_b_s_d_._o_r_g Reinoud Zandijk _r_e_i_n_o_u_d_@_n_e_t_b_s_d_._o_r_g Maria Zevenhoven _m_a_r_i_a_7_@_n_e_t_b_s_d_._o_r_g Christos Zoulas _c_h_r_i_s_t_o_s_@_n_e_t_b_s_d_._o_r_g _O_t_h_e_r _c_o_n_t_r_i_b_u_t_o_r_s_: Dave Burgess _b_u_r_g_e_s_s_@_c_y_n_j_u_t_._i_n_f_o_n_e_t_._n_e_t Brian R. Gaeke _b_r_g_@_d_g_a_t_e_._o_r_g Brad Grantham _g_r_a_n_t_h_a_m_@_t_e_n_o_n_._c_o_m Lawrence Kesteloot _k_e_s_t_e_l_o_o_@_c_s_._u_n_c_._e_d_u Waldi Ravens _w_a_l_d_i_@_m_o_a_c_s_._i_n_d_i_v_._n_l_._n_e_t LLeeggaall MMuummbboo--JJuummbboo All product names mentioned herein are trademarks or registered trade- marks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by The NetBSD Foundation, Inc. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by Adam Glass and Charles Han- num. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Alistair G. Crooks. This product includes software developed by Amancio Hasty and Roger Hardiman. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gardner Buchanan. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Hauke Fath. This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch. This product includes software developed by Herb Peyerl. This product includes software developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Mark Brinicombe for the NetB- SD Project. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Tinguely and Jim Lowe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael L. Hitch. This product includes software developed by Niels Provos. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by Tohru Nishimura for the NetB- SD Project. This product includes software developed by TooLs GmbH. This product includes software designed by William Allen Simpson. This product includes software developed by Winning Strategies, Inc. This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the Computer Systems Labora- tory at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Eric Young (eay@min- com.oz.au). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/). This product includes software developed by the University of Oregon. This product includes software developed by the University of Southern California and/or Information Sciences Institute. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by Reinoud Zandijk. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by Allen K. Briggs. This product includes software developed by Apple Computer, Inc. This product includes software developed by Bill Studenmund. This product includes software developed by Bradley A. Grantham. This product includes software developed by Carnegie-Mellon University. This product includes software developed by Chris P. Cputo. This product includes software developed by Colin Wood. This product includes software developed by David Huang. This product includes software developed by Internet Research Institute, Inc. This product includes software developed by John P. Wittkoski. This product includes software developed by Open Software Foundation, Inc. This product includes software developed by Per Fogelstrom, Opsycon AB and RTMX Inc, USA. This product includes software developed by Takashi Hamada. This product includes software developed by Tsubai Masanari. This product includes software developed by University of Utah. This product includes software developed by Wolfgang Solfrank. TThhee EEnndd NetBSD September 7, 2002 71