INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/macppc. CONTENTS About this Document............................................3 Quick install notes for the impatient..........................3 What is NetBSD?................................................5 Changes Between The NetBSD 3.0 and 4.0 Releases................5 Networking..................................................5 File systems................................................6 Drivers.....................................................6 Platforms...................................................9 Kernel subsystems...........................................9 Security...................................................10 Userland...................................................11 Components removed from NetBSD.............................12 The Future of NetBSD..........................................13 Sources of NetBSD.............................................13 NetBSD 4.0 Release Contents...................................13 NetBSD/macppc subdirectory structure.......................15 Binary distribution sets...................................15 NetBSD/macppc System Requirements and Supported Devices.......17 Supported models...........................................18 Unsupported models.........................................19 Supported devices..........................................19 Unsupported devices........................................21 Supported boot devices and media...........................22 Getting the NetBSD System on to Useful Media..................22 Preparing your System for NetBSD installation.................24 Prepare yourself...........................................24 Preparing your Open Firmware 3 System for NetBSD..............26 Updating your BootROM......................................26 Getting to Open Firmware 3.................................26 Setting up Open Firmware 3 to boot NetBSD..................27 Available Boot Media.......................................27 Partitioning your hard drive for NetBSD....................29 Preparing the Open Firmware 3 Bootable Media...............30 Creating the NetBSD/macppc CD-R.........................31 Preparing an HFS or HFS+ partition......................31 Preparing a custom hybrid HFS/ISO9660 CD-R..............31 Creating an MS-DOS disk.................................32 Preparing the netboot server............................32 Preparing a SCSI or IDE drive with the CD-R image.......37 Preparing your Open Firmware 1.x or 2.x System for NetBSD.....37 Getting to Open Firmware on Apple Network Servers..........37 Open Firmware 1 and 2 System Preparation...................38 Getting to Open Firmware (MacOS X or Darwin)...............39 Getting to Open Firmware (Best, MacOS 8 or 9)..............39 Getting to Open Firmware (Harder, MacOS 7, 8, or...........40 Getting to Open Firmware (Without using MacOS).............41 Setting up Open Firmware 1 and 2 to boot...................42 Available Boot Media.......................................43 Partitioning your hard drive for NetBSD....................44 Preparing the Open Firmware 1 or 2 Bootable Media..........45 Creating the NetBSD/macppc CD-R.........................46 Creating the NetBSD install floppies....................46 Creating a custom ISO9660 CD-R..........................47 Creating an MS-DOS disk.................................48 Preparing the netboot server............................48 Preparing a SCSI or IDE drive with the CD-R image.......52 Installing the NetBSD System..................................53 Open Firmware boot syntax..................................53 Examples of Open Firmware boot commands....................56 Booting the NetBSD/macppc install CD-R..................56 Booting the NetBSD install floppies.....................57 Booting an IDE or SCSI drive with an HFS partition......57 Booting a custom CD-ROM.................................57 Booting an MS-DOS floppy................................58 Booting over the ethernet...............................58 Booting an IDE or SCSI drive with 'partition zero'......59 Example of a normal boot...................................59 Common Problems and Error Messages.........................60 Black screen............................................60 Grey screen with flashing question mark.................60 Information on your screen seems garbled or out of sync.60 DEFAULT CATCH!..........................................61 CLAIM failed............................................61 can't OPEN..............................................61 unrecognized Client Program formatstate not valid.......61 bad partition number, using 0no bootable HFS partition..62 READ TIMEOUT@...........................................62 TFTP timeout............................................62 enet:,/netbsd.ram.gz: Inappropriate file type or format.62 Bootloader hangs before the copyright notice............62 Hang after configuring devices..........................62 Milestone..................................................63 Running the sysinst installation program...................63 Introduction............................................63 General.................................................63 Quick install...........................................63 Booting NetBSD..........................................64 Network configuration...................................64 Preparing a disk for Open Firmware 3 systems............64 Installation drive selection and parameters.............66 Partitioning the disk...................................66 Preparing your hard disk................................67 Getting the distribution sets...........................67 Installation using ftp..................................67 Installation using NFS..................................68 Installation from CD-ROM................................68 Installation from an unmounted file system..............68 Installation from a local directory.....................68 Extracting the distribution sets........................68 Making the device nodes.................................69 Finalizing your installation............................69 Finalizing Open Firmware settings..........................69 Booting NetBSD exclusively..............................69 Additional Open Firmware tips...........................70 Booting NetBSD and MacOS X or Darwin....................70 Booting NetBSD and MacOS 9 or earlier...................70 Other boot techniques...................................71 Post installation steps.......................................71 Upgrading a previously-installed NetBSD System................74 Compatibility Issues With Previous NetBSD Releases............74 Issues affecting an upgrade from NetBSD 2.1 and older......75 Issues affecting an upgrade from NetBSD 3.x releases.......75 Issues with GDB 6.5...........................................76 Using online NetBSD documentation.............................76 Administrivia.................................................77 Thanks go to..................................................77 We are........................................................78 Dedication....................................................84 Legal Mumbo-Jumbo.............................................84 The End.......................................................90 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 4.0 on the macppc platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt: .ps PostScript. .html Standard Internet HTML. .more 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 man pages are generally pre- sented. .txt Plain old ASCII. You are reading the ASCII version. Quick install notes for the impatient This section contains some brief notes describing what you need to install NetBSD 4.0 on a machine of the macppc architecture. o 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 (Open Firmware 1 or 2), fetch the pair of boot floppy images macppc/installation/floppy/boot1.fs and macppc/installation/floppy/boot2.fs, which include the bootloader and installation kernel. For systems without floppy drives (most are Open Firmware 3), fetch the bootloader macppc/installation/ofwboot.xcf and the installation kernel macppc/binary/kernel/netbsd-GENERIC_MD.gz. If you have a CD-R, you can fetch the CD image, macppccd-4.0.iso. Alternatively, you may netboot the installation kernel. This process is covered below, in detail. o The actual binary distribution is in the macppc/binary/sets/ direc- tory. When you boot the install kernel from floppies, 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: kern-GENERIC.tgz, base.tgz and etc.tgz. In a typical workstation installation you will probably want all the installation sets. o If your macppc has a floppy drive, create the pair of boot floppies using suntar (MacOS 9), rawrite (Windows), or dd (any UNIX-like sys- tem with floppy support). If your system has Open Firmware 3, drag ofwboot.xcf and netbsd-GENERIC_MD.gz to your hard drive icon (the top level of the drive, not the desktop). If you are using the CD image, 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. o Determine your machine's model, quirks, and Open Firmware version from the NetBSD/macppc Model Support webpage. http://www.NetBSD.org/ports/macppc/models.html At present, NetBSD/macppc cannot exist on the same hard drive as Mac OS unless you partition your disk before running the installer. Open Firmware versions prior to 3 require a dedicated NetBSD drive -- you must use the entire disk, partitioned with the installation tools. Open Firmware version 3 cannot boot into NetBSD on a drive parti- tioned with the installation tools, you must partition your disk before running the installer, then select the ``Re-install sets or install additional sets'' option in the installer (selecting the ``Install NetBSD to hard disk'' or ``Upgrade NetBSD on a hard disk'' options will render your drive unbootable). If you are unsure, you may want to read the section below on Partitioning your hard drive for NetBSD o 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 the chime ends. Entering Open Firmware versions prior to 3 is usually the most frustrating part of installation -- you may want to read the section below on Older Open Firmware System Preparation You should have the Open Firmware ``0 '' prompt on your screen before attempting to boot NetBSD/macppc. o At the Open Firmware prompt, type the command to boot. To boot from the installation floppies, the command is ``boot fd:0''. For the install kernel and bootloader on your hard drive (Open Firmware 3), the command is ``boot hd:,\ofwboot.xcf netbsd-GENERIC_MD.gz''. For boot CDs, the command is something like ``boot cd:,\ofwboot.xcf netbsd.macppc'' (for Open Firmware 3) or ``boot scsi-int/sd@3:0 NETBSD.MACPPC'' (for earlier Open Firmware versions). You will need to use the correct case for OFWBOOT.XCF and NETBSD.MACPPC depending on how your version of Open Firmware interprets the ISO file system. You may need to replace cd with scsi/sd@3 , scsi-int/sd@3 , ata/atapi-disk , or some other device alias. You should also use the Open Firmware dir command to confirm that the NetBSD/macppc kernel is called NETBSD.MACPPC. You may want to read the section below on Open Firmware boot syntax o For third-party programs which are not part of the base NetBSD dis- tribution, you will want to explore the pkgsrc system with its more than 7200 program packages. What is NetBSD? 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 four different system architectures (ports), featuring sev- enteen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD 4.0 release contains complete binary releases for many different system architectures. (A few ports are not fully supported at this time and are thus not part of the binary distri- bution. Please see the NetBSD web site at http://www.NetBSD.org/ for information on them.) NetBSD is a completely integrated system. In addition to its highly por- table, 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. Changes Between The NetBSD 3.0 and 4.0 Releases The NetBSD 4.0 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 more than a year of development that went into the NetBSD 4.0 release. The complete list of changes can be found in the CHANGES: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES and CHANGES-4.0: ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-4.0/CHANGES-4.0 files in the top level directory of the NetBSD 4.0 release tree. Some highlights include: Networking o agr(4): new pseudo-device driver for link level aggregation. o IPv6 support was extended with an RFC 3542-compliant API and added for gre(4) tunnels and the tun(4) device. o A NDIS-wrapper was added to use Windows binary drivers on the i386 platform, see ndiscvt(8). o The IPv4 source-address selection policy can be set from a number of algorithms. See "IPSRCSEL" in options(4) and in_getifa(9). o Imported wpa_supplicant(8) and wpa_cli(8). Utilities to connect and handle aspects of 802.11 WPA networks. o Imported hostapd(8). An authenticator for IEEE 802.11 networks. o carp(4): imported Common Address Redundancy Protocol to allow multi- ple hosts to share a set of IP addresses for high availability / redundancy, from OpenBSD. o ALTQ support for the PF packet filter. o etherip(4): new EtherIP tunneling device. It's able to tunnel Ether- net traffic over IPv4 and IPv6 using the EtherIP protocol specified in RFC 3378. o ftpd(8) can now run in standalone mode, instead of from inetd(8). o tftp(1) now has support for multicast TFTP operation in open-loop mode, server is in progress. o tcp(4): added support for RFC 3465 Appropriate Byte Counting (ABC) and Explicit Congestion Notification as defined in RFC 3168. File systems o scan_ffs(8), scan_lfs(8): utilities to find FFSv1/v2 and LFS parti- tions to recover lost disklabels on disks and image files. o tmpfs: added a new memory-based file system aimed at replacing mfs. Contrary to mfs, it is not based on a disk file system, so it is more efficient both in overall memory consumption and speed. See mount_tmpfs(8). o Added UDF support for optical media and block devices, see mount_udf(8). Read-only for now. o NFS export list handling was changed to be filesystem independent. o LFS: lots of stability improvements and new cleaner daemon. It is now also possible to use LFS as root filesystem. o vnd(4): the vnode disk driver can be used on filesystems such as smbfs and tmpfs. o Support for System V Boot File System was added, see newfs_sysvbfs(8) and mount_sysvbfs(8). Drivers o Audio: - Support for new models on drivers such as Intel ICH8/6300ESB, NVIDIA nForce 3/4, etc. - Added support for AC'97 modems. - auich(4): added support to handle the AC'97 modem as audio device, enabled with the kernel option ``AUICH_ATTACH_MODEM'' - azalia(4): added support for S/PDIF. o Hardware Monitors: - amdpm(4): added support for the i2c bus on the AMD-8111 used on many Opteron motherboards and for the Analog Devices ADT7464 hardware monitor chip. - adt7467c(4): new driver for Analog Devices ADT7467 and ADM1030 hardware monitor chips. - ipmi(4): new driver for motherboards implementing the Intelligent Platform Management Interface 1.5 or 2.0, from OpenBSD. - it(4): new driver for iTE 8705F/8712F and SiS 950 hardware moni- tors. - The lm(4) driver was rewritten and support for more chips was added, for example for Winbond W83627HF, W83627THF, W83627DHG and Asus AS99127F. - owtemp(4): new driver for the 1-Wire temperature sensors. - tmp121temp(4): new driver for the Texas Instruments TMP121 tem- perature sensor. - ug(4): new driver for Abit uGuru hardware monitor found on newer Abit motherboards. o Miscellaneous: - geodewdog(4): new AMD Geode SC1100 Watchdog Timer driver. - gscpcib(4): new AMD Geode SC1100 PCI-ISA bridge that provides support for the GPIO interface. o Networking: - ath(4): updated HALs with support for WiSOC (AR531x) and 32bit SPARC. - bge(4): added support for the following chips: BCM5753, BCM5753M, BCM5715, BCM5754, BCM5755 and BCM5787. Numerous improvements and bugfixes were made too. - kse(4): new driver for Micrel KSZ8842/8841 PCI network cards. - msk(4): new driver for Marvell Yukon 2 GigE PCI network cards, from OpenBSD. - nfe(4): new driver for NVIDIA nForce Ethernet network cards, from OpenBSD. - ral(4): new 802.11 driver for PCI/Cardbus Ralink RT2500, RT2501, RT2600, RT2661 and RT2500 USB chipsets, from OpenBSD. - rum(4): new 802.11 driver for USB Ralink RT2501 and RT2601 chipsets, from OpenBSD. - sip(4): now works on sparc64. - tlp(4): added support for ASIX AX88140A and AX88141. - vr(4): added support for the VIA Rhine III. - wm(4): added support for i8003, ICH8, ICH9 and others. Support for IPv6 Rx TCP/UDP Checksum Offloading and more. - wpi(4): new driver for Intel PRO/Wireless 3945ABG PCI 802.11 net- work cards, from OpenBSD. o Security: - glxsb(4): new driver for the AMD Geode LX AES Security Block that provides random numbers and AES acceleration, from OpenBSD. o Power Management: - Support for Intel Speedstep SMI on PIIX4 PCI-ISA for i386. - Support for AMD PowerNow and Cool'n'Quiet Technology on K7 and K8 CPUs (both in 32 and 64 bit mode), including Athlon Mobile, Athlon64, Opteron or X2. See options(4) for more information. - Support for more Enhanced Speedstep CPUs, including VIA C7/Eden and Intel Core Solo/Duo/Duo2. See options(4) for more informa- tion. - The Enhanced Speedstep and PowerNow drivers were modified to be able to be scaled in all CPUs available, saving power on SMP sys- tems. o Storage: - ahcisata(4): new driver for AHCI 1.0 and 1.1 compliant SATA con- trollers. - ataraid(4): added support to handle Adaptec HostRAID and VIA V- Tech software RAID. - ciss(4): new driver for HP/Compaq 5th+ generation Smart ARRAY controllers, from OpenBSD. - fdc(4): added support for SBus based sparc64 machines and fixed formatting on sparc. - gcscide(4): new driver for the AMD Geode CS5535 Companion Device IDE controller. - jmide(4): new driver for JMicron Technology JMB36x PCIe to SATA II/PATA controllers. - mfi(4): new driver for LSI Logic and Dell MegaRAID SAS con- trollers, from OpenBSD. - mpt(4): added support for newer SAS and similar devices. - njata(4): new driver for Workbit NinjaATA-32 CardBus IDE con- troller. - pdcsata(4): added support for the Promise PDC20775, PDC20771, PDC40518, PDC40718 and some bugfixes. - piixide(4): added support for some ICH8/ICH8-M/ICH9 IDE and SATA controllers. - svwsata(4): new driver for Serverworks K2 SATA controllers, from OpenBSD. - viaide(4) added support for the VIA VT8237A SATA controller and AMD CS5536 Companion Device IDE Controller. o USB: - ucycom(4): new driver for Cypress microcontroller based serial devices. - uipaq(4): new driver for the iPAQ devices. - uslsa(4): new driver for Silicon Labs CP210x series serial adapters. - utoppy(4): new driver for the Topfield TF5000PVR range of digital video recorders. Platforms o i386: - Added support for the for Multiboot specification. This means much improved support for loading the kernel by GRUB, including passing in parameters to the kernel. - Added the unichromefb framebuffer driver that supports the VIA Unichrome Graphics adapter. - vesafb(4): added new framebuffer driver that supports VESA BIOS (VBE) 2.0 extensions and up. - Added cd9660 file system support to the BIOS bootloader. o evbarm: new platform support for Arcom Viper PXA255-based single board, Atmark Techno Armadillo-9 and Armadillo-210, Certance CP-3100, Linksys NSLU2 (a.k.a. "Slug") and I-O DATA HDL-G Giga LANDISK NAS devices. o evbmips: added support for Alchemy Au1550 processors, DBAu1550 boards, Alchemy Au15XX PCI host, (OMS-AL400/128) and Atheros AR5312 SoC. o New port ews4800mips: NEC's MIPS based EWS4800 workstations. o cobalt: added support for booting off raidframe RAID1 mirrors. o hpcmips: added the teliosio(4) driver for the Sharp Telios LCD screen and Battery unit. o New port landisk: port to the SH4 processor based NAS appliances, supporting models by I-O DATA (USL-5P, HDL-U, HDL-AV, HDL-W and HDLM- U series, SuperTank LAN Tank, UHDL-160U and UHDL-300U) and Plextor PX-EH16L, PX-EH25L and PX-EH40L. o macppc: this port has gained support to use accelerated wsdisplay drivers by default (if possible), and uses the appropriate driver rather than the Generic Open Firmware Framebuffer. o prep: this port has been modernized, and support for five additional machines has been added, among them the IBM 7024-E20 and 7025-F30 models and Motorola Powerstack E1. Additionally, sysinst support was added, and the bootloader process was improved, allowing easy instal- lation and upgrade to future releases. o sparc: added support for booting off raidframe RAID1 mirrors. o Xen: support for Xen3 domU and dom0 (Unprivileged domain and domain 0), including support for hardware virtualization on CPUs that sup- port it. Kernel subsystems o Improved Firewire (IEEE1394) support imported from FreeBSD. o The midi(4) framework got a complete overhaul for better support of Active Sensing and improved handling of tempo and timebase changes. o Added a Bluetooth protocol stack including: - hardware drivers: ubt(4) for USB controllers, and bt3c(4) for the 3Com Bluetooth PC-Card. - socket based access to the HCI, L2CAP, RFCOMM and SCO protocols. - pseudo drivers for integrating services on remote Bluetooth devices such as Keyboards, Mice and SCO Audio into the NetBSD device framework. See bluetooth(4), bthset(1) and btpin(1). o Imported the bio(4) framework from OpenBSD, to query/control block hardware RAID device controllers. Currently supporting the mfi(4) driver. o Kernel uses stateful read-ahead algorithm. o dkctl(8) can be used to switch buffer queuing strategies on the fly on wd(4) disks, see also bufq(9). o fileassoc(9) is used by Veriexec, it adds in-kernel and file-system independent file meta-data association interface. o firmload(9): an API for loading firmware images used by various hard- ware devices. o gpio(4): imported General Purpose I/O framework from OpenBSD. o onewire(4): imported Dallas Semiconductor 1-wire bus framework from OpenBSD. o The proplib(3) protocol was added for sending property lists to/from the kernel using ioctls. o spi(4): new SPI (Serial Peripherial Interface) framework. o timecounter(9) adds a new time-keeping infrastructure along with NTP API 4 nanokernel implementation. Almost all platforms were changed to support this API. o Start of 32bit-Linux-emulation for amd64 (COMPAT_LINUX32). o wscons(4) console driver supports splash screens, scrolling, progress bar for kernel and boot messages. 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. Security o The FAST_IPSEC IPsec implementation was extended to use hardware acceleration for IPv6, in addition to the hardware accelerated IPv4 that was available before. See fast_ipsec(4) for more information. o mprotect(2) got restrictions to enforce W^X policies, from PaX. See options(4), sysctl(3), and paxctl(1). o GCC 4's support for stack smashing protection (SSP) was enabled by adding libssp, see security(8). o The kernel authorization framework kauth(9) was added, replacing the traditional BSD credential management and privileged operation access control with an abstract layer, allowing the implementation of vari- ous security models either as part of the NetBSD distribution or as third-party LKMs. NetBSD's kernel authorization is a hybrid clean-room implementation of a similar interface developed by Apple, extending its capabilities and combining concepts of credential inheritance control. Userland o 3rd party software updates: - BIND 9.4.1-P1 - OpenSSL 0.9.8e - CVS 1.11.22 - OpenSSH 4.4 - gettext 0.14.4 - PF from OpenBSD 3.7 - (n)awk 20050424 - Postfix 2.4.5 - am-utils 6.1.3 - file 4.21 - zlib 1.2.3 - GNU binutils 2.16.1 - GNU groff 1.19.2 - IPFilter 4.1.23 - GNU gcc 4.1.2 prerelease - GNU gdb 6.5 (some architectures) - NTP 4.2.4p2 - pppd 2.4.4 o cdplay(1): added digital transfer mode support. o cksum(1) can now verify checksums. o csplit(1): new utility that splits a file into pieces. From FreeBSD/OpenBSD. o identd(1): added support for forwarding ident queries and receiving of proxied ident queries. o getent(1): added support for the ethers database. o gkermit(1): new program for transferring files using the Kermit pro- tocol. o mail(1): added support for Mime and multi-character set handling, command line editing and completion. o utoppya(1): new utility to interface to the utoppy(4) driver. o init(8): added support for running multi-user in a chroot() environ- ment. Allows / file system on e.g., cgd(4), vnd(4) or ccd(4) volumes. o gpt(8): new GUID partition table maintenance utility, from FreeBSD. o iSCSI target (server) code added, see iscsi-target(8); Initiator (client) code is underway. o lockstat(8): new command to display a summary of kernel locking events recorded over the lifetime of a called program. o ofctl(8): new command to display the OpenPROM or OpenFirmware device tree for the macppc, shark and sparc64. o Various utilities to support Bluetooth were added: - btconfig(8) for controller configuration. - btdevctl(8) to manage pseudo devices relating to remote services. - bthcid(8) and btpin(1) for authenticating radio connections. - sdpd(8) for providing service discovery to remote devices. - sdpquery(1) for querying services on remote devices. - rfcomm_sppd(1) to access remote services over RFCOMM via stdio or pty. - bthset(1) for making connections to Bluetooth headsets. Besides this list, there have also been innumerable bug fixes and other miscellaneous enhancements of course. Components removed from NetBSD In this release of NetBSD, some software components known from previous releases were removed from the system. In some cases those were compo- nents that are not useful anymore or their utility does not justify main- tenance overhead. Other components were not working properly and there was lack of interest in fixing them. o Sushi was removed from the base system due to lack of interest and maintenance. If you really want it, it is available in the CVS repos- itory at othersrc/usr.sbin/sushi. However, be warned that it is unmaintained and is most likely out of date. o Vinum was removed due to lack of interest and maintenance. At the time of removal, it had several known serious issues (including not being compilable). RAIDframe provides similar functionality. If you were using Vinum you will need to back up your data, delete the Vinum partitions, create RAIDframe partitions, and restore your data to them. Details about RAIDframe can be found in raid(4), raidctl(8), and the NetBSD Guide: http://www.NetBSD.org/docs/guide/en/chap-rf.html. o Sendmail was removed. Postfix is the MTA and provides the sendmail(1) command line tool. Postfix has been included with NetBSD since NetBSD 1.5 was released in December 2005. Details about Postfix can be found in the NetBSD Guide: http://www.NetBSD.org/docs/guide/en/chap-mail.html. For those who need Sendmail, it is available from pkgsrc in the mail/sendmail and mail/sendmail813 packages. o NETCCITT and NETNS were removed due to lack of interest and mainte- nance. They had known serious issues (including being out of date with respect to other network code) and there were no known users at the time of their removal. Unfortunately, there is no replacement or option for them. o UUCP was removed. The NetBSD improvements were merged into the pkgsrc version. For those who use UUCP tools, they are available from pkgsrc in the net/uucp package. The cu(1) command is available as a frontend to tip(1). o The Fortran 77 compiler ( g77 ) has been removed with the transition from GCC 3 to GCC 4, which does not include it. For those who need it, it is available from pkgsrc in the lang/gcc3-f77 package. o The evbsh5 port has been removed from NetBSD due to lack of interest, compounded by a lack of available SH5 hardware. The Future of NetBSD 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: o providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. o providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. o providing a better position from which to undertake promotional activities. o periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to support even more 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 usability 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. Sources of NetBSD Refer to http://www.NetBSD.org/mirrors/. NetBSD 4.0 Release Contents The root directory of the NetBSD 4.0 release is organized as follows: .../NetBSD-4.0/ CHANGES Changes between NetBSD 3.0 and branching 4.0. CHANGES-4.0 Changes since NetBSD 4.0 was branched. CHANGES.prev Changes in earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 4.0 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (also somewhat incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures for which NetBSD 4.0 has a binary distribution. The source distribution sets can be found in subdirectories of the source subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: gnusrc This set contains the ``gnu'' sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. 95 MB gzipped, 484 MB uncompressed sharesrc 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. 6 MB gzipped, 25 MB uncompressed src This set contains all of the base NetBSD 4.0 sources which are not in gnusrc, sharesrc, or syssrc. 45 MB gzipped, 214 MB uncompressed syssrc This set contains the sources to the NetBSD 4.0 kernel for all architectures; config(1); and dbsym(8). 33 MB gzipped, 165 MB uncompressed xsrc This set contains the sources to the X Window System. 95 MB gzipped, 502 MB uncompressed All the above source sets are located in the source/sets subdirectory of the distribution tree. The source sets are distributed as compressed tar files. Except for the pkgsrc set, which is traditionally unpacked into /usr/pkgsrc, all sets may be unpacked into /usr/src with the command: # cd / ; tar -zxpf set_name.tgz 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 directory, in the format produced by the command: cksum -o 1 file. CKSUM POSIX checksums for the various files in that directory, in the format produced by the command: cksum file. MD5 MD5 digests for the various files in that directory, in the format produced by the command: cksum -a MD5 file. SHA512 SHA512 digests for the various files in that directory, in the format produced by the command: cksum -a SHA512 file. SYSVSUM Historic ATT System V UNIX checksums for the various files in that directory, in the format produced by the command: cksum -o 2 file. The SHA512 digest is the safest checksum, followed by the MD5 digest, and finally the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of systems can check the integrity of the release files. NetBSD/macppc subdirectory structure The macppc-specific portion of the NetBSD 4.0 release is found in the macppc subdirectory of the distribution: .../NetBSD-4.0/macppc/. It con- tains the following files and directories: INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display. binary/ kernel/ netbsd-GENERIC.gz A gzipped NetBSD kernel containing code for everything supported in this release. netbsd-GENERIC.MP.gz A gzipped NetBSD kernel containing code for everything supported in this release. This kernel also supports SMP on systems with more than one CPU. netbsd-GENERIC_MD.gz A gzipped NetBSD kernel containing code for everything supported in this release. It also has a RAM-disk installer. This is the kernel you should use when you want to install via netboot, from a CD-R, or an HFS parti- tion on Open Firmware 3 systems. netbsd-INSTALL.gz A gzipped NetBSD kernel containing code only for Open Firmware 1.0.5, 1.1.22, 2.0.x, and 2.4 systems (i.e. those that have floppy drives). It has a RAM-disk installer. sets/ macppc binary distribution sets; see below. installation/ floppy/boot1.fs floppy/boot2.fs macppc boot and installation floppy images. The first is the bootloader and kernel. The second image has the installation tools. Only usable on models that ship with a floppy drive (pre-Open Firmware 3); see below. ofwboot.xcf macppc bootloader; see below. Binary distribution sets The NetBSD macppc binary distribution sets contain the binaries which comprise the NetBSD 4.0 release for the macppc. The binary distribution sets can be found in the macppc/binary/sets subdirectory of the NetBSD 4.0 distribution tree, and are as follows: base The NetBSD 4.0 macppc base binary distribution. You must install this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be mini- mally functional. It includes shared library support, and excludes everything described below. 27 MB gzipped, 77 MB uncompressed comp Things needed for compiling programs. This set includes the system include files (/usr/include) and the various system libraries (except the shared libraries, which are included as part of the base 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. 31 MB gzipped, 106 MB uncompressed etc This distribution set contains the system configuration files that reside in /etc and in several other places. This set must be installed if you are installing the system from scratch, but should not be used if you are upgrading. 1 MB gzipped, 1 MB uncompressed games This set includes the games and their manual pages. 4 MB gzipped, 8 MB uncompressed kern-GENERIC This set contains a NetBSD/macppc 4.0 GENERIC kernel named /netbsd. You must install this distribution set. 4 MB gzipped, 7 MB uncompressed kern-GENERIC.MP This set contains a NetBSD/macppc 4.0 GENERIC.MP kernel, which will use multiple processors (if present), named /netbsd. 4 MB gzipped, 7 MB uncompressed man This set includes all of the manual pages for the binaries and other software contained in the base set. Note that it does not include any of the manual pages that are included in the other sets. 8 MB gzipped, 33 MB uncompressed misc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share. 4 MB gzipped, 12 MB uncompressed text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. 4 MB gzipped, 11 MB uncompressed 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 4.5.0. Binary sets for the X Window System are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. 7 MB gzipped, 20 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 13 MB gzipped, 45 MB uncompressed xfont Fonts needed by the X server and by X clients. 31 MB gzipped, 39 MB uncompressed xetc Configuration files for X which could be locally modified. 0.03 MB gzipped, 0.17 MB uncompressed xserver The X server. This includes both the XFree86 and Xmacppc servers. The XFree86 server supports acceleration, switchable resolutions and bit-depths. This server supports only known video cards, such as ATI and Nvidia and can be difficult to configure. The Xmacppc server supports all on-board video and Open Firmware-compatible video cards. Acceleration and depths greater than 256 colors are not supported. See the X11 FAQ for help using X on macppc systems. http://www.NetBSD.org/ports/macppc/x11.html 11 MB gzipped, 28 MB uncompressed The macppc binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. 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 below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xpf command from the root directory ( / ) of your system. This utility is used only in a Traditional method installation. Note: Each directory in the macppc binary distribution also has its own checksum files, just as the source distribution does. NetBSD/macppc System Requirements and Supported Devices Currently, NetBSD/macppc requires the use of Open Firmware to boot. Open Firmware is a command environment using the FORTH language. The NetBSD kernel uses Open Firmware to gather information about your system and to control 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 hard- ware support. It was not intended to be used to boot an operating sys- tem. 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 intro- duced 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, but easier to set up for NetBSD. At present, NetBSD/macppc does not support the PPC 601 microprocessor, which means that the PowerMacintosh 7200 and 7500 models are not sup- ported. The PowerMacintosh 7500 may be upgraded to a PPC 604, G3 or G4 microprocessor 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 200 MB plus space for the swap par- tition (usually the RAM size, unless you've got a lot of RAM). To install X, an additional 60 MB disk space is required, as is more RAM (at least 32 MB). NetBSD with 16 MB of RAM is very slow. Until you have around 32 MB of RAM, getting more RAM is more important than getting a faster CPU. Supported models Find your model from the list below and take note of its Open Firmware version: Open Firmware 1.0.5 o Apple PowerMacintosh (7300, 7500 (with CPU upgrade), 7600, 8500, 8600, 9500, and 9600) o Apple Workgroup Server 8550 o Power Computing (PowerCenter, PowerCenter Pro, PowerCurve, PowerTower, PowerTower Pro, and PowerWave) o UMAX (J700, S900) Open Firmware 1.1.22 o Apple Network Server (500 and 700) Note: 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. Open Firmware 2.0.x o Apple PowerBook (2400, 3400, G3, and G3 Series) o Apple PowerMacintosh/Performa (4400, 54xx, 5500, 6300/160, 6360, 6400, and 6500) o Apple PowerMacintosh (G3 ``Beige'' models with ATI RageII+: Desktop, Mini Tower, and All-in-One) o APS Tech (M*Power 604e/200) o Motorola StarMax (3000, 4000, 5000, and 5500) o Power Computing (PowerBase) o UMAX (Apus 2000, Apus 3000, C500, and C600) Open Firmware 2.4 o Apple PowerMacintosh (G3 ``Beige'' models with ATI Rage Pro: Desktop, Mini Tower, and All-in-One) Open Firmware 3 o Apple original iBook, iBook SE, iBook (Dual USB), iBook (Late 2001), iBook (16VRAM), iBook (Opaque 16 VRAM), iBook (32 VRAM), iBook (14.1 LCD 32 VRAM), and iBook G4 o 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), iMac (Sum- mer 2001), and iMac (USB 2.0) o Apple original eMac and eMac (ATI Graphics) o Apple PowerBook (G3 Series (bronze keyboard) and G3 (FireWire)) o Apple PowerBook (G4 (Titanium), G4 (Gigabit Ethernet), G4 (DVI), G4 (12-inch), G4 (17-inch), G4 (12-inch DVI), Power- Book G4 (15-inch FW 800), PowerBook G4 (17-inch 1.33GHz/1.5GHz)) o Apple PowerMacintosh G3 (Blue and White) o Apple PowerMacintosh (G4 (PCI), G4 (AGP), G4 (Gigabit Eth- ernet), G4 (Digital Audio), G4 (Quicksilver), G4 (Quicksil- ver 2002), G4 (Mirrored Drive Doors), G4 (FW 800), and G4 Cube) o Apple Mac Mini G4 (1.25GHz/1.42GHz/1.5GHz) o Apple original Xserve and Xserve (Slot Load) Note: Some newer G4 models may not run at their full CPU speed, due to the fact Open Firmware starts the CPU at a reduced frequency. o Apple iMac G5, PowerMacintosh G5, Xserve G5 Note: G5 models are supported as a 32-bit port in bridge mode only. Unsupported models o Systems with Open Firmware, but using a PPC 601 microprocessor (PowerMacintosh 7200 and 7500 (without CPU upgrade)) o 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) o Systems with broken Open Firmware (Twentieth Anniversary Macin- tosh) o Systems with a Motorola 68k microprocessor (these systems are supported by NetBSD/mac68k) o Systems upgraded from any of the above (unless the motherboard is replaced as part of the upgrade) Supported devices o CPU upgrades - Only one CPU in a multiprocessor system is supported with the GENERIC kernel. All CPUs are supported with the GENERIC.MP kernel. - Most CPU upgrades are supported. Some older models will not automatically enable the L2 and/or L3 caches on a G3 or G4 processor. See the FAQ entry http://www.NetBSD.org/ports/macppc/faq.html#cpu-upgrade o Ethernet - On-board 79C950-based MACE Ethernet interface (mc) - On-board bmac Ethernet interface (bm) - On-board gmac Ethernet interface (gem) - Apple PCI Ethernet Card (option for Apple Network Server) (tlp) - Asante Mac 10/100 PCI Rev A, part number 09-00169-01 (tlp) - Farallon Fast EtherTX 10/100, part number PN996L-TX (tlp) - SMC Etherpower II (9432TX) (epic) - SMC 83c170 (epic) - 3Com 3c905 (ex) - Intel EtherExpress PRO/10+ PCI LAN Adapter (fxp) - Realtek 8029 Ethernet (ne) - VIA Technologies VT86C926 (ne) - D-Link DFE-530TX+ (rtk) - Realtek 8139 (rtk) - Netgear FA-311 (sip) - Lite-On PNIC (tlp) - D-Link DFE-530TX (vr) - Many other PCI and Cardbus Ethernet interfaces, such as Tulip-compatible (tlp), 3Com (ep), SMC (epic), Intel (fxp), NE2000-compatible (ne), and Realtek (rtk) - Many USB Ethernet interfaces (aue, cue, and kue) o Wireless - On-board AirPort or AirMac 802.11b (wi) - AT&T/Lucent WaveLan IEEE PCMCIA card (wi) o SCSI - On-board NCR 53c94 SCSI controller (esp) - On-board MESH SCSI controller (mesh) - Adaptec PCI controllers 291x, 2920, 2930C, 294x, 295x, 39xx, 19160, 29160 and AIC-78xx (ahc) Note: The 294x models are not bootable in Open Firmware, even though they can boot MacOS 9 and earlier. - AdvanSys 1200[A,B], 9xx[U,UA] SCSI controller (adv) - AMD 53c974 (pcscp) - Apple 53c875 Ultra Wide SCSI (shipped in some Beige G3 mod- els) (ncr or siop) Note: This card may need a firmware update to boot NetBSD. Use the Mac OS X SCSI Card Updater from http://docs.info.apple.com/article.html?artnum=25176 - NCR/Symbios 53C8xx (siop or esiop) - Many other PCI SCSI controllers should work, but no one has tried them - Most SCSI disk/tape/CD-ROM devices should work o IDE - On-board IDE controllers - Promise Ultra66 (pciide) (this, and other PC-based cards are not bootable on macppc) - Acard ATP-850/860 based IDE controllers (pciide) (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 o 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) o Video - On-board video on most models (ofb) Note: 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) - Full wscons capabilities, such as virtual terminals and color text are available. (Note however that switching between virtual terminals while running an X session is not supported at present.) o Audio - On-board audio on most models (awacs or snapper) Note: The (awacs) driver 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 default and you will need to build a kernel with it enabled. - USB audio devices (uaudio) - PCI audio cards, although only the Ensoniq AudioPCI (eap) has been thoroughly tested o Serial ports NetBSD/macppc refers to the on-board serial ports as (tty00) and (tty01). Firmware uses the names listed below. - On-board serial ports (the modem and printer ports) (ttya and ttyb) ttya is the mini-DIN 8 serial port with the `Modem' icon, and ttyb is has the `Printer' icon. Some models with internal modems have the serial port with the `Modem' icon covered over, and the modem is ttya. Note: 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 Xserve serial port. Note: This serial port can be used for console (57600 bps, 8 bits, no parity, 1 stop bit, no handshaking). Use (scca) for the Open Firmware `input-device' and `output-device' variables. Alternatively, if you remove your video card, Open Firmware will default to using the serial port for the console. - The Gee Three Stealth Serial Port, possibly the Griffin Technology gPort Note: These serial ports can be used for console (57600 bps, 8 bits, no parity, 1 stop bit, no handshaking). Use (scca) 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 o USB devices - Most MI USB devices should work (such as disks, printers, input devices, SCSI adapters, and ethernet interfaces) http://www.NetBSD.org/support/hardware/usb.html o PCMCIA and Cardbus cards - Most MI PCMCIA and Cardbus cards should work, although very few have been tested with NetBSD/macppc http://www.NetBSD.org/support/hardware/cardbus.html http://www.NetBSD.org/support/hardware/pcmcia.html o PCI cards - Most MI PCI cards should work, although very few have been tested with NetBSD/macppc http://www.NetBSD.org/support/hardware/pci.html Note: While the NetBSD kernel may support the various Cardbus, PCI, PCMCIA, and USB devices you may have, Open Firmware does not 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. Unsupported devices o Floppy disk Note: Though NetBSD/macppc can boot from a floppy, there is no kernel support yet o Advanced power management (cannot put system to `sleep') o On-board video capture o AirPort Extreme o On-board SATA controller on G5 systems (these machines must be netbooted) Supported boot devices and media 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. http://www.NetBSD.org/ports/macppc/models.html Getting the NetBSD System on to Useful Media 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. Note: Some Mac OS ftp 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. Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted. Installation is supported from several media types, including: o CD-ROM / DVD o MS-DOS floppy o FTP o Remote NFS partition o Tape o Existing NetBSD or MacOS X UFS partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the var- ious media are outlined below. CD-ROM / DVD Find out where the distribution set files are on the CD- ROM or DVD. Likely locations are binary/sets and macppc/binary/sets. Proceed to the instruction on installation. MS-DOS floppy NetBSD doesn't include split sets to keep the distribution size down. They can be created on a separate machine using the split(1) command, running e.g. split -b 235k base.tgz base. to split the base.tgz file from macppc/binary/sets into files named base.aa, base.ab, and so on. Repeat this for all set_name.tgz files, splitting them into set_name.xx files. Count the number of set_name.xx files that make up the distribution sets you want to install or upgrade. You will need one sixth that number of 1.44 MB floppies. Format all of the floppies with MS-DOS. Do not make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distribution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box. Place all of the set_name.xx files on the MS-DOS disks. Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the sec- tion on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. FTP 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. If you don't have DHCP available on your network, you will 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 numeric IP address of the router closest to the NetBSD machine. 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 IPv4 address of ftp.NetBSD.org is 204.152.190.13 and the IPv6 address is 2001:4f8:4:7:230:48ff:fe31:43f2 (as of Decem- ber, 2007). 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. Note: This method of installation is recommended for those familiar with using BSD network configuration and management commands. If you aren't, this docu- mentation should help, but is not intended to be all-encompassing. NFS Place the NetBSD distribution sets you wish to install into 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 /etc/exports file on the NFS server and resetting its mount daemon (mountd). (Both of these actions will proba- bly require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if you don't have DHCP available on your network and 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 itself. 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 pre- paring your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Note: This method of installation is recommended 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. Tape To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX-like system, the easi- est way to do so is probably something like: # tar -cf tape_device dist_directories where tape_device is the name of the tape device that describes the tape drive you're using; possibly /dev/rst0, or something similar, but it will vary from system to sys- tem. (If you can't figure it out, ask your system admin- istrator.) In the above example, dist_directories are the distribution sets' directories, for the distribution sets you wish to place on the tape. For instance, to put the kern-GENERIC, base, and etc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: # cd .../NetBSD-4.0 # cd macppc/binary # tar -cf tape_device kern-GENERIC base etc Note: You still need to fill in tape_device in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Preparing your System for NetBSD installation Prepare yourself Take a deep breath. Good. Now, make sure you are reading the PDF (if available), PostScript, or HTML version of this document, as the .txt and .more versions lack important 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: http://www.NetBSD.org/ports/macppc/faq.html#macos-newbie It's done printing? Fine, time to get started. 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). http://www.NetBSD.org/ports/macppc/models.html 2. Spend about 15 minutes and read through this document from this point onward. There will be many pages of instructions that apply to Open Firmware versions that you do not have. Throw them out. Do not read them -- at best you will be confused, at worst you may dam- age your system requiring repairs. 3. Now create your bootable media and media for the distribution sets. 4. 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). 5. 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. 6. 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 Common Problems and Error Messages 7. 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. 8. Now use the installer to install the distribution sets onto your system and do some initial configurations. 9. Figure out how to boot from the installed partition. Boot into NetBSD for the first time. 10. You may then boot into Open Firmware and set it to always boot your favorite operating system. 11. Configure to your preferences, install your favorite packages, and have fun with your new NetBSD/macppc machine! Note: 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. Note: If the instructions in a subsection below do not apply to all 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) If you do not have an Open Firmware 3 system, skip down to Preparing your Open Firmware 1.x or 2.x System for NetBSD Preparing your Open Firmware 3 System for NetBSD Updating your BootROM 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 not 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 Downloads' web site at http://www.info.apple.com/support/downloads.html and search for `firmware' and install the most recent version for your model. For most G3 and G4 models, you will need to run the FirmWare updater from MacOS 9. Note: If you accidentally change the load-base or real-base Open Firmware variables and reset your machine you will, in effect, re- write the BootROM with garbage. This will permanently damage your machine. We recommend not doing this. Note: The most recent BootROMs available (4.1.7 and later) are a little picky about RAM. Initially, some PowerMacintosh G3 users found that their third-party RAM had been disabled, but the RAM vendors brought their RAM up to spec and it hasn't been much of an issue since then. There is one report that FirmWare Update 4.1.9 on iMac (Summer 2000) will prevent the CD-ROM and the hard drive from operating together. You may get wdc0:0:1: lost interrupt problems. Getting to 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 command 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 setenv auto-boot? false Alternatively, if you are currently running MacOS X or Darwin, you can use the nvram command to set this variable before rebooting. # nvram auto-boot\?=false You will need to escape the question-mark or enclose the whole nvram argument in double-quotes to prevent your shell from trying to interpret it. Setting up Open Firmware 3 to boot NetBSD 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: http://www.NetBSD.org/ports/macppc/faq.html#ofw-access http://www.NetBSD.org/ports/macppc/faq.html#ofw-variables Double-check your Open Firmware version: 0 dev /openprom 0 .properties 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 dev enet 0 .properties [...] local-mac-address CCCCCCCC CCCC [...] Note: 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 device on your network. You can check your Open Firmware settings with the printenv command: 0 printenv -------------- 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 Available Boot Media Open Firmware is capable of booting from a variety of media (such as hard drives, CD-ROMs, and ethernet). Open Firmware is able to boot files from a variety of file systems (such as ISO9660, HFS, HFS+, and MS-DOS FAT). Unfortunately, Open Firmware is not able to directly boot from the NetBSD file system (FFS) or Apple's new BSD-based file system (UFS), so we must put the bootloader in a location that Open Firmware is capable of under- standing. Therefore, to boot the NetBSD kernel, Open Firmware must first load a `bootloader' (ofwboot.xcf) which knows how to load the NetBSD kernel. Note: ofwboot.elf is obsoleted. All users should be using ofwboot.xcf instead of ofwboot.elf now. The following bootable media are available for loading the bootloader: o HFS or HFS+ file system This method loads ofwboot.xcf from an HFS or HFS+ partition which then loads the kernel from an acceptable location. 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 ofwboot.xcf. o MS-DOS file system In this method, Open Firmware loads the ofwboot.xcf bootloader from an MS-DOS file system. It may then load a NetBSD kernel from the same MS-DOS file system. This has only been thor- oughly tested on floppy disks, but may work on Zip disks or FDISK-formatted hard drives. This does not work for MS-DOS partitions on a hard drive with an Apple Partition Map. o Ethernet (network boot) You can run your entire system diskless or netboot only the files necessary to boot (i.e. the bootloader and the installa- tion kernel). You must have root access for the UNIX-like net- boot server, which must be on the same subnet as your NetBSD/macppc machine. Note: 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 o Hybrid HFS/ISO9660 CD-ROM file system Load the ofwboot.xcf 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. Note: Open Firmware can only open files on the first session of a multi-session CD-R Once the bootloader is loaded, it can open the kernel from one of the following sources: o Ethernet (NFS) o NetBSD FFS file system o MacOS X UFS file system o HFS or HFS+ file system o ISO9660 CD-ROM file system o MS-DOS file system The boot CD-R images provided with the distribution sets has both a `partition zero' bootloader and ofwboot.xcf on a hybrid partition so it can be booted on all Open Firmware versions. It also has an ISO9660 file system with an installation kernel and the distribution sets. Partitioning your hard drive for NetBSD You must have at least one disk that was partitioned before running the NetBSD installer. This is the drive that will have the bootloader, ofwboot.xcf. Your NetBSD partitions may either be on this same disk (using the method described in the rest of this section), or on a separate disk accessible only to NetBSD. This section describes how to make a single disk usable by both MacOS and NetBSD -- this is necessary for machines which have only one hard drive (such as the eMac, iBook, iMac, PowerBook, and PowerMacintosh Cube sys- tems). If you do not want MacOS you must still follow this procedure, but create only a small HFS+ partition (large enough for the bootloader). There are two partitioning tools available for NetBSD/macppc, disklabel(8) and pdisk(8). The former is used in the NetBSD sysinst installer, and will render your disk unusable by MacOS. It will also prevent Open Firmware 3 machines from booting from that disk. When run- ning the installer, you will need to use the installer's ``Re-install sets'' option to skip the disklabel step. Do not use disklabel or ``Re-install sets'' unless you will use one drive for NetBSD only and have another drive which will have the bootloader. The process is more fully detailed in the Partitioning HOW-TO: http://www.NetBSD.org/ports/macppc/partitioning.html You can create a partition map with pdisk(8), but the disk will not be usable with MacOS 9 and earlier. If this is a concern, you will need to use Apple's Drive Setup or Disk Utility. If you are using Apple's Drive Setup tool, make sure you have version 1.8.1 or later. This tool only runs under MacOS 9 and earlier. Drive Setup will erase the contents of your drive -- it does not preserve data from any of your partitions. Apple's Disk Utility only runs under MacOS X 10.0.0 and later. Make sure you click the ``Install Mac OS 9 Disk Drivers'' checkbox. Also, keep in mind that Disk Utility does not create the partitions that NetBSD/macppc requires. After creating the initial partition map with Disk Utility, you will need to use the NetBSD pdisk to change the partition types. Also, Disk Utility will erase the contents of your drive -- it does not preserve data from any of your partitions. pdisk is the most flexible (and most difficult to use) partitioning tool available. It runs on almost all OSes that macppc machines support. Download it: ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/netbsd-pdisk/ ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/macos-utils/pdisk.sea.hqx There is built-in help describing how it works. When it asks you to enter the ``Type of partition'', use Apple_UNIX_SVR2 for NetBSD parti- tions, Apple_HFS for HFS and HFS+ partitions, and Apple_UFS for UFS par- titions. After you've written the partition map with pdisk, you will need to cre- ate the file systems. Use newfs(8) and mount(8) for NetBSD file systems, and hfstools to create and mount HFS file systems. ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/hfsutils/README.html Make the following partitions: HFS or HFS+ Must be large enough to hold the boot- loader, over 100 KB. May be as large as you desire for MacOS usage. A/UX Root 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 260 MB with X. NetBSD interprets an A/UX Root partition as the first par- tition (a) on the disk. This partition is not readable from MacOS. A/UX Swap Any size. The recommendation is your RAM size, although this is not strictly nec- essary for machines with a lot of RAM. NetBSD interprets an A/UX Swap partition as the second partition (b) on the disk. This partition is not readable from MacOS. A/UX User and A/UX Free1 Use these for any additional partitions you may want to use under NetBSD, such as /usr (at least 200 MB), /home, /usr/local, or /usr/pkg. NetBSD inter- prets these partitions as normal NetBSD -style partitions. These partitions are not readable from MacOS. HFS Any size. You may want to leave an addi- tional partition available to transfer files between MacOS and NetBSD. If would like to create such a partition, then see the Partitioning HOW-TO. http://www.NetBSD.org/ports/macppc/partitioning.html#msdos UFS Any size. UFS partitions are not read- able from MacOS versions prior to X 10.0.0. If you use an UFS partition as your root, then it may not be recognized by the NetBSD kernel as the first parti- tion (a) on the disk. You will need to compile a new kernel with the root parti- tion explicitly defined to be the UFS partition. Now would be a good time to use pdisk to determine the partition numbers for your bootloader and kernel. Preparing the Open Firmware 3 Bootable Media 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 onto appropriate media, see the above sec- tion entitled Getting the NetBSD System on to Useful Media. You may want to get the distribution sets when you create the bootable media. Note: Some MacOS ftp 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. What follows are the steps to create different types of bootable media for the NetBSD install kernel. You should only need to create one of these to get your system to boot the installer o Creating the NetBSD/macppc CD-R Go to one of the NetBSD mirror sites and download the CD-R image macppccd-4.0.iso from the pub/NetBSD/iso directory. http://www.NetBSD.org/mirrors/#iso - From an UNIX-like machine Get and install cdrecord. NetBSD users should install it from the package collection. Other UNIX-like systems should get it from the official website: ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrtools/README.html http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html # cdrecord -v speed=4 dev=/dev/cd1c macppccd-4.0.iso 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 /dev/cd1d). - From a MacOS machine (using Toast) 1. Click the `Other' button in the main window. 2. Open the contextual menu on the `Other' button and select `Disk Image' 3. Click the `Select' button and select the disk image you downloaded. 4. Click the `Record' button Skip forward to Installing the NetBSD System o Preparing an HFS or HFS+ partition Place ofwboot.xcf and the installation kernel netbsd-GENERIC_MD.gz 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 Installing the NetBSD System o Preparing a custom hybrid HFS/ISO9660 CD-R This section describes how to create your own bootable NetBSD/macppc CD-R. We recommend that you use the official NetBSD/macppc-4.0 CD-R image, as described in the section above. Place ofwboot.xcf and the installation kernel netbsd-GENERIC_MD.gz 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 netbsd.gz. You may also place the NetBSD 4.0 distribution sets on the ISO9660 parti- tion (not only on the HFS partition). - From an UNIX-like machine Get and install mkisofs. This is now part of the cdrecord pack- age. NetBSD users should install it from the package collection. Other UNIX-like systems should get it from the official website: ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/sysutils/cdrtools/README.html http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html # mkisofs -o output.iso -hfs -part -l -J -r -L -N /cdsources # cdrecord -v speed=4 dev=/dev/cd1c output.iso You will need to substitute the correct speed for your CD writer, and the correct device for your system (for i386 it would be /dev/cd1d). See the NetBSD Bootable CD-ROM HOW-TO for more detail: http://www.NetBSD.org/docs/bootcd.html - From a MacOS machine (using Toast) 1. Click the `Data' button in the main window 2. Pick `Mac OS and PC (Hybrid) CD' from the popup menu between the four buttons and the file and folder area. 3. Drag installation/ofwboot.xcf and binary/kernel/netbsd-GENERIC_MD.gz into the window. You may also want to drag the NetBSD 4.0 distribution sets to this window as well. 4. Click the `Record' button Skip forward to Installing the NetBSD System o Creating an MS-DOS disk Open Firmware 3 cannot boot from a floppy disk, but you can still create a bootable Zip disk with this method. 1. First, make sure you have done a low-level format on the disk. A bad disk can produce Open Firmware errors similar to other problems. 2. Mount the disk 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 netbsd-INSTALL.gz and ofwboot.xcf to the disk. 4. Rename netbsd-INSTALL.gz to netbsd.gz, since OpenFirmware can't deal with MS-DOS filenames longer than eight characters. Skip forward to Installing the NetBSD System o Preparing the netboot server 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 server(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. http://www.NetBSD.org/docs/network/netboot/ 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, ofwboot.xcf. 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 directory /export/client/root. 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 /etc/dhcpd.conf (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; # master DHCP server for this subnet # subnet 192.168.1.0 netmask 255.255.255.0 { # Which network interface to listen on. # The zeros indicate the range of addresses # that 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"; # # If your DHCP server is not your NFS server, supply the # address of the NFS server. Since we assume you run everything # on one server, this is not needed. # # macppc machines will look for their bootloader, # ofwboot.xcf, on the next-server as well. # # next-server server.test.net; } #you may paste another "host" entry here for additional #clients on this network } You will need to make sure that the dhcpd.leases file exists. # touch /var/db/dhcpd.leases You will need to start the dhcpd. 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, you can achieve this with: # /etc/rc.d/dhcpd restart 3. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) environment in the /tftpboot directory. Thus, the first order of business is to create this directory: # mkdir -p /tftpboot Next, edit /etc/inetd.conf 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, you can achieve this with: # /etc/rc.d/inetd restart Now, you need to copy the bootloader for your macppc machine to /tftpboot. Get ofwboot.xcf(8) from the installation directory of the distribution. # cp ofwboot.xcf /tftpboot Just to be sure, let's make everything readable. # chmod -R a+rX /tftpboot 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 /var/log/messages 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: # arp -s client CC:CC:CC:CC:CC:CC 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: # mkdir -p /export/client/root Put the following line in /etc/exports 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, you can achieve this with: # /etc/rc.d/rpcbind start # /etc/rc.d/nfsd start # /etc/rc.d/mountd restart 5. NetBSD kernel and installation tools Now, if you place a kernel named netbsd in /export/client/root your client should boot the kernel. If you are netbooting the installer, use binary/kernel/netbsd-GENERIC_MD.gz (this has the installation tools in a RAM disk). Also, copy the distribution files to the client's root directory. Note: Some combinations of Open Firmware version and ofwboot.xcf version have trouble loading compressed ker- nels. If you have trouble loading a kernel, try uncom- pressing it with gunzip(1) # cp *tgz /export/client/root # gunzip netbsd-GENERIC_MD.gz # mv netbsd-GENERIC_MD /export/client/root/netbsd If you are running your macppc diskless, simply use binary/kernel/netbsd-GENERIC.gz. 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. http://www.NetBSD.org/docs/network/netboot/nfs.html - Extracting distribution sets # cd /export/client/root # tar -xpzf /path/to/files/base.tgz # tar -xpzf /path/to/files/etc.tgz Continue with the other non-essential distribution sets if desired. - Set up swap # mkdir /export/client/root/swap # dd if=/dev/zero of=/export/client/swap bs=4k count=4k # echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports # /etc/rc.d/mountd restart This creates a 16 MB swap file and exports it to the client. - Create device nodes # cd /export/client/root/dev # ./MAKEDEV all This procedure only works on NetBSD hosts. - Set up the client's fstab(5) Create a file in /export/client/root/etc/fstab 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 /export/client/root/etc/rc.conf 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 /export/client/root/etc/hosts ::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 /etc/rc.conf: 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 tftpd line in /etc/inetd.conf remains uncommented. Skip forward to Installing the NetBSD System o Preparing a SCSI or IDE drive with the CD-R image If the NetBSD/macppc CD-R image is compressed, then you will need to uncompress it first. Find a spare bootable drive (i.e. SCSI or IDE), and use some tool to write the disk image macppccd-4.0.iso 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 disk image has an HFS partition with ofwboot.xcf which loads the installa- tion kernel from the ISO file system on the disk image. - From an UNIX-like machine (including MacOS X) # dd if=macppccd-4.0.iso of=/dev/rsd0c where /dev/rsd0c 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. - From a Windows machine Get rawrite32.exe from http://www.duskware.com/rawrite32/ Be certain you have selected the correct disk, as it will erase the contents. - From a MacOS 9 (or earlier) machine Get suntar from http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/suntar-223.hqx 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 macppccd-4.0.iso and click ``Open'' 8. Open the `File' menu and pick `Close Device' Skip forward to Installing the NetBSD System Preparing your Open Firmware 1.x or 2.x System for NetBSD Getting to Open Firmware on Apple Network Servers (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' device 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 setenv auto-boot? false Skip down to the section on Setting up Open Firmware 1 and 2 to boot NetBSD since the next several pages are instructions for MacOS models. Open Firmware 1 and 2 System Preparation Open Firmware has two variables, `input-device' and `output-device', which specify how it accepts commands and displays 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 will 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. http://www.NetBSD.org/ports/macppc/models.html In particular, some models must use a serial console, or they will be unable 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: http://www.NetBSD.org/ports/macppc/faq.html#ofw-input-output-devices 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. http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/comm/term/zterm-101.hqx http://homepage.mac.com/dalverson/zterm/ See the NetBSD Serial Port Primer for additional help and references: http://www.NetBSD.org/docs/Hardware/Misc/serial.html All Open Firmware 1 and 2 macppc systems have Open Firmware bugs. Luck- ily, Open Firmware has a small Non-Volatile RAM variable (NVRAM) which is reserved for FORTH commands which will be run before booting an operating system. Apple has released a freeware MacOS 9 tool called System Disk, which patches most of these bugs. We strongly 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 Getting to Open Firmware (Harder, MacOS 7 thru 9) 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 Getting to Open Firmware (MacOS X or Darwin) When you install MacOS X or Darwin, it will install the necessary NVRAM bug fixes. Use the nvram command to set your system to always stop at the Open Firmware prompt, then reboot. # nvram auto-boot\?=false You will need to escape the question-mark or enclose the whole nvram argument in double-quotes to prevent your shell from trying to interpret it. You should now see the Open Firmware command prompt on your screen: Open Firmware, 1.0.5 To continue booting the MacOS type: BYEreturn To continue booting from the default boot device type: BOOTreturn ok 0 If your screen is black, then your model has defaulted to using a serial console. You must hook up a serial console (38400 bps, 8 bits, no par- ity, 1 stop bit, no handshaking). Getting to Open Firmware (Best, MacOS 8 or 9) Download System Disk: ftp://ftp.apple.com/developer/macosxserver/utilities/SystemDisk2.3.1.smi.bin For a brief tutorial on how to use System Disk, see: http://www.NetBSD.org/ports/macppc/SystemDisk-tutorial/ 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. Note: 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 9 or earlier. 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 http://www.NetBSD.org/ports/macppc/SystemDisk-tutorial/of105patch.html You should now see the Open Firmware command prompt on your screen: Open Firmware, 1.0.5 To continue booting the MacOS type: BYEreturn To continue booting from the default boot device type: BOOTreturn 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). Note: The ``Stop Boot at Open Firmware prompt'' setting is persistent. It is equivalent to the Open Firmware command 0 setenv auto-boot? false Note: 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 setenv use-nvramrc? false 0 reset-all Getting to Open Firmware (Harder, MacOS 7, 8, or 9) 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. ftp://ftp.NetBSD.org/pub/NetBSD/arch/macppc/macos-utils/bootvars/bootvars.sit.hqx Note: BootVars does not 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-ROMs). Look up the proper `output-device' for your model on the NetBSD/macppc Model Support webpage. http://www.NetBSD.org/ports/macppc/models.html 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 kbd 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 http://www.NetBSD.org/ports/macppc/SystemDisk-tutorial/of105patch.html If you have a Performa 5500 or 6500, you may need to apply NVRAMRC patches 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: BYEreturn To continue booting from the default boot device type: BOOTreturn 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). Note: 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 setenv auto-boot? false Getting to Open Firmware (Without using MacOS) (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. Note: Your system will not have the (possibly critical) NVRAM patches that System Disk applies. Expect some devices to not work (such as booting from hard drives and CD-ROMs). 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 command prompt on your screen or serial console: Open Firmware, 1.0.5 To continue booting the MacOS type: BYEreturn To continue booting from the default boot device type: BOOTreturn 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 setenv auto-boot? false To use your on-board video and keyboard, look up the proper `output-device' for your model on the NetBSD/macppc webpage http://www.NetBSD.org/ports/macppc/models.html Run the following commands to use your screen instead of a serial console (replace `screen' with the correct `output-device' for your model): 0 setenv output-device screen 0 setenv input-device kbd 0 reset-all 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 http://www.NetBSD.org/ports/macppc/SystemDisk-tutorial/of105patch.html Setting up Open Firmware 1 and 2 to boot NetBSD 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: http://www.NetBSD.org/ports/macppc/faq.html#ofw-access http://www.NetBSD.org/ports/macppc/faq.html#ofw-variables Double-check your Open Firmware version: 0 dev /openprom 0 .properties 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 not run these commands on Open Firmware 3 machines, as you may overwrite your firmware requiring a trip to Apple for repairs. 0 setenv load-base 600000 0 setenv real-base F00000 0 reset-all 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 dev enet 0 .properties [...] local-mac-address CCCCCCCC CCCC [...] ok Note: 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 printenv command: 0 printenv 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 Note: All Open Firmware 1.0.5 settings and nvram patches will be erased if you boot into MacOS 9 or earlier. You will need to re-enter them before booting NetBSD again. Note: 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 from booting) if you boot into MacOS 9 or earlier.