INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/mvme68k. CONTENTS About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 3.0 and 4.0 Releases................3 Networking..................................................3 File systems................................................4 Drivers.....................................................4 Platforms...................................................6 Kernel subsystems...........................................7 Security....................................................8 Userland....................................................8 Components removed from NetBSD.............................10 The Future of NetBSD..........................................11 Sources of NetBSD.............................................11 NetBSD 4.0 Release Contents...................................11 NetBSD/mvme68k subdirectory structure......................13 Binary distribution sets...................................13 NetBSD/mvme68k System Requirements and Supported Devices......16 Supported VME147 hardware..................................16 Supported VME162/VME172 hardware...........................16 Supported VME167/VME177 hardware...........................17 Getting the NetBSD System on to Useful Media..................17 Creating boot/install tapes................................18 Boot/Install from NFS server...............................18 Install/Upgrade from CD-ROM................................19 Install/Upgrade via FTP....................................19 Preparing your System for NetBSD installation.................19 Installing the NetBSD System..................................21 Installing from tape.......................................21 Installing from NFS........................................25 Booting the miniroot.......................................27 Miniroot install program:..................................28 Running the sysinst installation program...................29 Introduction............................................29 General.................................................29 Quick install...........................................29 Booting NetBSD..........................................30 Network configuration...................................31 Installation drive selection and parameters.............31 Partitioning the disk...................................31 Preparing your hard disk................................32 Getting the distribution sets...........................32 Installation using ftp..................................32 Installation using NFS..................................32 Installation from CD-ROM................................33 Installation from an unmounted file system..............33 Installation from a local directory.....................33 Extracting the distribution sets........................33 Finalizing your installation............................33 Post installation steps.......................................34 Upgrading a previously-installed NetBSD System................36 Upgrading using the miniroot...............................36 Manual upgrade.............................................37 Compatibility Issues With Previous NetBSD Releases............38 Issues affecting an upgrade from NetBSD 2.1 and older......38 Issues affecting an upgrade from NetBSD 3.x releases.......38 Issues with GDB 6.5...........................................39 Using online NetBSD documentation.............................39 Administrivia.................................................40 Thanks go to..................................................40 We are........................................................41 Dedication....................................................47 Legal Mumbo-Jumbo.............................................47 The End.......................................................53 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 4.0 on the mvme68k 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. 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/mvme68k subdirectory structure The mvme68k-specific portion of the NetBSD 4.0 release is found in the mvme68k subdirectory of the distribution: .../NetBSD-4.0/mvme68k/. It contains 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-VME147.gz A kernel for MVME147 boards. netbsd-VME162.gz A kernel for MVME162 boards. netbsd-VME167.gz A kernel for MVME167 boards. netbsd-VME172.gz A kernel for MVME172 boards. netbsd-VME177.gz A kernel for MVME177 boards. sets/ mvme68k binary distribution sets; see below. installation/ miniroot/ mvme68k miniroot file system image; see below. netboot/ Two programs needed to boot mvme68k kernels over the network; see below. tapeimage/ Tape boot programs, and a RAMDISK kernel; see below. Binary distribution sets The NetBSD mvme68k binary distribution sets contain the binaries which comprise the NetBSD 4.0 release for the mvme68k. The binary distribution sets can be found in the mvme68k/binary/sets subdirectory of the NetBSD 4.0 distribution tree, and are as follows: base The NetBSD 4.0 mvme68k 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. 24 MB gzipped, 68 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. 23 MB gzipped, 83 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. 3 MB gzipped, 8 MB uncompressed kern-GENERIC This set contains a NetBSD/mvme68k 4.0 GENERIC kernel, named /netbsd. You must install this distribution set. 1 MB gzipped, 3 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. 3 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. 6 MB gzipped, 18 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 11 MB gzipped, 39 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. 4 MB gzipped, 10 MB uncompressed The mvme68k 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. The following are included in the mvme68k/installation directory: miniroot/ Note: The sysinst method of installation is the preferred method for installing NetBSD/mvme68k. The Traditional method of installation is deprecated and will be removed in a future release. Some other important dif- ferences between the two installation methods are: o The Installer and Mkfs utilities are not used if the installation is done using the sysinst method via booting an Installation Kernel. o Mkfs creates a 4.3BSD "old" format file system. This is the only file system format understood by the Installer. The sysinst process creates "new" file systems which can't be processed by Mkfs or the Installer. o The Installer (and probably Mkfs) is known to have problems with BSD file systems that are larger than 1 GB or extend beyond the 1 GB physical limit. Keep this in mind if doing a Traditional method installation with these utilities. o The Booter is known to have problems booting from a NetBSD file system if the inode of the kernel file is to large. For large disks it is advisable to have a small root partition and one or more usr- type partitions for other files. This ensures the inode of the kernel in the root file system will be small. o The Booter is designed to work with 4.3BSD "old" file systems, but there are enough similarities between the "old" and "new" file system formats in the first few hundred blocks that the Booter can usually boot a Kernel from a 4.3BSD new file sys- tem. If you choose to use "new" file system for- mats, it is advisable to use a small root partition and one or more usr-type partitions for other files. This is the default layout used by sysinst. miniroot.gz A copy of the miniroot file system. This file system image is copied into the swap partition of the disk which you intend to boot NetBSD from. Normally, this step will be performed manually from the ramdisk boot environment. netboot/ sboot An MVME147 bootstrap program in Motorola S-Record for- mat. This is required when you wish to boot an MVME147 over the network since the ROM has no built-in network support. Instructions for getting this program into memory are discussed later. netboot A standalone 2nd stage bootstrap program loaded over the network via TFTP. This is responsible for fetch- ing and starting the NetBSD mvme68k kernel from an NFS server. tapeimage/ stboot This file contains a boot sector for Motorola MVME boards. It must be the first file written to a tape in order to make the tape bootable. bootst This file contains a bootstrap program which knows how to load the NetBSD mvme68k ramdisk image from tape. This must be the second file written to the tape. netbsd-RAMDISK.gz This is the NetBSD mvme68k ramdisk image. It contains a GENERIC kernel and a built in RAMDISK with just enough tools to par- tition a disk, dump the miniroot kernel to it and make the disk bootable. This must be the third file written to the tape. Note: Each directory in the mvme68k binary distribution also has its own checksum files, just as the source distribution does. NetBSD/mvme68k System Requirements and Supported Devices NetBSD/mvme68k 4.0 runs on Motorola MVME147 , MVME162 , MVME167 , MVME172 , and MVME177 Single Board Computers. The minimal configuration requires 8 MB of RAM and ~200 MB of disk space. To install the entire system requires much more disk space (approx. 600 MB additional space is necessary for full sources. Double that if you want to recompile it all!). To run X (clients only) or compile the sys- tem, more RAM is recommended. Good performance requires 16 MB of RAM, or 32 MB when running the X Window System. Note that you can install NetBSD 4.0 on a system with only 4 MB of onboard RAM, but you will need to use a VMEbus RAM card with at least another 4 MB to augment the onboard memory in order to actually install the system. Here is a table of recommended HD partition sizes for a full install: Partition Suggested Needed / (root) 32 MB 26 MB /usr 200 MB 150 MB /var 32 MB 6 MB swap 2-3 *RAM 16 MB Anything else is up to you! Note that the NetBSD/mvme68k installation procedure uses a miniroot image which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image ( 7.5 MB). Supported VME147 hardware o Serial ports (RS232) - built-in console - ttyZ1 - ttyZ2 - ttyZ3 o Parallel port - On-board centronics style printer port o Network interfaces: - On-board Lance Ethernet (le) o SCSI - Most SCSI disks, tapes, CD-ROMs, etc - On-board wd33c93 SCSI bus interface chip (async only) o Miscellaneous: - Battery-backed real-time clock - VMEbus RAM cards - Any VMEbus interface cards with Machine Independent drivers Supported VME162/VME172 hardware o Serial ports (RS232) - built-in console - ttyC1 - ttyC2 - ttyC3 o Network interfaces: - On-board Intel Ethernet (ie) o SCSI - Most SCSI disks, tapes, CD-ROMs, etc - On-board ncr53c710 SCSI I/O processor chip o Miscellaneous: - Battery-backed real-time clock - VMEbus RAM cards - Any VMEbus interface cards with Machine Independent drivers Supported VME167/VME177 hardware o Serial ports (RS232) - built-in console - ttyZ1 - ttyZ2 - ttyZ3 o Parallel port - On-board centronics style printer port o Network interfaces: - On-board Intel Ethernet (ie) o SCSI - Most SCSI disks, tapes, CD-ROMs, etc - On-board ncr53c710 SCSI I/O Processor chip o Miscellaneous: - Battery-backed real-time clock - VMEbus RAM cards - Any VMEbus interface cards with Machine Independent drivers If it's not on the above lists, there is no support for it in this release. Getting the NetBSD System on to Useful Media Installation is supported from several media types, including: o Tape o NFS o CD-ROM o FTP Note that installing on a `bare' machine requires either a bootable tape drive or an ethernet to a compatible NFS server. MVME147 may also need to be booted over an RS232 connection. The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below. In order to create installation media, you will need all the files and subdirectories in these two directories: .../NetBSD-4.0/mvme68k/installation .../NetBSD-4.0/mvme68k/binary Creating boot/install tapes Installing from tape is the simplest method of all. This method uses two tapes, one containing a bootable ramdisk and miniroot, the other contain- ing the installation sets. The boot tape is created as follows: # cd .../NetBSD-4.0/mvme68k/installation # set T = /dev/nrst0 # mt -f $T rewind # dd if=tapeimage/stboot of=$T obs=8k conv=osync # dd if=tapeimage/bootst of=$T obs=8k conv=osync # gzip -dc tapeimage/netbsd-RAMDISK.gz | dd of=$T obs=8k conv=osync # gzip -dc miniroot/miniroot.fs.gz | dd of=$T obs=8k conv=osync # mt -f $T rewind The installation set tape is created as follows: # cd .../NetBSD-4.0/mvme68k/binary/sets # set T = /dev/nrst0 # mt -f $T rewind # for f in base etc comp games man misc text; do gzip -d $f.tgz | dd of=$T bs=8k conv=osync # done # mt -f $T rewind If the tape does not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. Consult the tape-related man- ual pages on the system where the tapes are created for more details. Boot/Install from NFS server If your machine has a disk and network connection, but no tape drive, it may be convenient for you to install NetBSD over the network. This involves temporarily booting your machine over NFS, just long enough so you can initialize its disk. This method requires that you have access to an NFS server on your network so you can configure it to support disk- less boot for your machine. Configuring the NFS server is normally a task for a system administrator, and is not trivial. If you are using a NetBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, consult the documentation that came with it (i.e. add_client(8) on SunOS). Booting an MVME147 from ethernet is not possible without first download- ing a small bootstrap program (sboot) via RS232. See the section enti- tled Installing from NFS for details on how to accomplish this. sboot expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RARP It will look for a filename derived from the machine's IP address expressed in hexadecimal, with an extension of `.147'. For example, an MVME147 with IP address 130.115.144.11 will make an TFTP request for 8273900B.147. Normally, this file is just a symbolic link to the NetBSD/mvme68k netboot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). The net- boot program may be found in the install directory of this distribution. The MVME162 , MVME167 , MVME172 , and MVME177 boot ROMs have code builtin to boot over ethernet from a TFTP server. You should configure it to download the same netboot program as is used for MVME147. The netboot program will query a bootparamd server to find the NFS server address and path name for its root, and then load a kernel from that location. The server should have a copy of the netbsd-RAMDISK kernel in the root area for your client (no other files are needed in the client root, although it might be a convenient place to put the uncompressed miniroot image) and /etc/bootparams on the server should have an entry for your client and its root directory. Note that you should rename the netbsd-RAMDISK kernel to just netbsd in the client's root directory before trying to netboot the client. The client will need access to the miniroot image, which can be provided using NFS or remote shell. If using NFS, miniroot.fs.gz should be expanded on the server, because doing so from the RAMDISK shell is not so easy. The unzipped miniroot takes about 7.5 MB of space. If you will be installing NetBSD on several clients, it may be useful to know that you can use a single NFS root for all the clients as long as they only use the netbsd-RAMDISK kernel. There will be no conflict between clients because the RAM-disk kernel will not use the NFS root. No swap file is needed; the RAM-disk kernel does not use that either. Install/Upgrade from CD-ROM This method requires that you boot from another device (i.e. tape or net- work, as described above). You may need to make a boot tape on another machine using the files provided on the CD-ROM. Once you have booted netbsd-RAMDISK (the RAMDISK kernel) and loaded the miniroot, you can load any of the distribution sets directly from the CD-ROM. The install pro- gram in the miniroot automates the work required to mount the CD-ROM and extract the files. Install/Upgrade via FTP This method requires that you boot from another device (i.e. tape or net- work, as described above). You may need to make a boot tape on another machine using the files in .../install (which you get via FTP). Once you have booted netbsd-RAMDISK (the RAM-disk kernel) and loaded the miniroot, you can load any of the distribution sets over the net using FTP. The install program in the miniroot automates the work required to configure the network interface and transfer the files. This method, of course, requires network access to an FTP server. This might be a local system, or it might even be ftp.NetBSD.org itself. If you wish to use ftp.NetBSD.org as your FTP file server, you may want to keep the following information handy: No IP Address: ftp.NetBSD.org Login: anonymous Password: your e-mail address Server path: /pub/NetBSD/NetBSD-4.0/mvme68k/binary Note: If you're not using a nameserver during installation, you might find 204.152.184.75 handy; it's the IP address of ftp.NetBSD.org as of October, 2000. Preparing your System for NetBSD installation mvme68k machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of backing up all data on any attached storage devices. The exception to the above is that MVME162 , MVME167 , MVME172 and MVME177 boards require a jumper to be removed or DIP switch changed before NetBSD can be installed. On MVME162-LX and MVME172-LX pins 1-2 of jumper J11 must be removed. On MVME162-P2/P4 and MVME172-P2/P4 switch S4, position 8 must be set to OFF. On MVME167 and MVME177 pins 1-2 of jumper J1 must be removed. Once you've made any necessary jumper changes, the following instructions should make your machine ``NetBSD Ready''. Power-up your MVME147 board. You should have the bug prompt: COLD Start Onboard RAM start = $00000000, stop = $007FFFFF 147-Bug Or, if you have an MVME162/172 or MVME167/177 board (the following boot message is from MVME167; the others are similar): MVME167 Debugger/Diagnostics Release Version 2.3 - 02/25/94 COLD Start Local Memory Found =02000000 (&33554432) MPU Clock Speed =33Mhz 167-Bug Make sure the RAM size looks ok (if you've got an 8 MB MVME147 or a 32 MB MVME167 you should have the same value as we do). Also make sure the clock is ticking: 1xx-Bugtime Sunday 12/21/31 16:25:14 1xx-Bugtime Sunday 12/21/31 16:25:15 1xx-Bug Note that NetBSD bases its year at 1968, and adds the year offset in the system's real-time clock to get the current year. So the 31 here equates to 1999. You may have to adjust your clock using the set command to com- ply with NetBSD 's requirements. Don't worry if the `Day of the week' is not correct, as NetBSD doesn't use it. Motorola has acknowledged a year 2000 bug in some versions of the MVME147 whereby the day of the week doesn't get set correctly by the 147Bug PROM. NetBSD does not affect Also make sure that your board's ethernet address is initialised to the correct value. You'll find the address on a label on the inside of the MVME147's front panel, and on the VMEbus P2 connector of the other board types. On the MVME147, enter the last five digits of the address using the lsad command. On the MVME162/172 and MVME167/177, you should use the cnfg command. The NetBSD kernel reads the first two long words of the onboard NVRAM to determine the starting and ending address of any VMEbus RAM that should be used by the system. You should verify that this area is set properly for your configuration. If you have no VMEbus RAM boards, the values should be set to zero (0). For an MVME162, MVME167, MVME172 or MVME177 board, at the 1xx-Bug prompt: 1xx-Bugmm fffc0000 ;l fffc0000: xxxxxxxx?0 fffc0004: xxxxxxxx?0 fffc0008: xxxxxxxx?. 1xx-Bug For an MVME147 board, at the 147Bug prompt: 147Bugmm fffe0764 ;l fffe0764: xxxxxxxx?0 fffe0768: xxxxxxxx?0 fffe076c: xxxxxxxx?. If you do have VMEbus RAM available and want NetBSD to use it, the first long word should be set to the starting address of this RAM and the sec- ond long word should be set to the ending address. If you have more than one VMEbus RAM board installed, the starting and ending addresses must be contiguous from one board to the next. Also note that, for various reasons beyond the scope of this document, VMEbus RAM should be configured in A32 address space. To install successfully to a local SCSI disk, you need to ensure that the system is aware of what targets are connected to the SCSI bus. This can be done by issuing the following command: 1xx-Bug iot;t At this point, Bug will scan for any attached SCSI devices. After a short delay, a list of SCSI devices will be displayed. 147Bug will ask if LUNs should be assigned from SCSI ids, to which you should answer Y. You should also answer Y when asked if the information is to be saved to NVRAM. 16xBug does not prompt for this information. The following installation instructions will assume that your target SCSI disk drive appears at SCSI-ID 0. If you have a tape drive, the instruc- tions assume is is configured for SCSI-ID 5. When the RAMDISK root boots, NetBSD will refer to these devices as sd0 and rst0 respectively. You may wish to note these down; you'll be using them a lot. :-) Installing the NetBSD System Installing NetBSD is a relatively complex process, but if you have this document in hand it should not be too difficult. There are several ways to install NetBSD onto your disk. If your MVME147 machine has a tape drive the easiest way is Installing from tape (details below). All other machines can be installed easily over the network from a suitable NFS server. See Installing from NFS for details. Otherwise, if you have another mvme68k machine running NetBSD you can initialize the disk on that machine and then move the disk. Installing from tape Create the NetBSD/mvme68k 4.0 boot tape as described in the section enti- tled Preparing a boot tape. Then, with the tape in the drive, type the following at the Bug prompt: 147-Bug bo 5 16x-Bug bo 0,50 As mentioned earlier, this assumes your tape is jumpered for SCSI-ID 5. As the tape loads (which may take 20 to 30 seconds), you will see a series of status messages. It may be useful if you can capture these messages to a file, or a scrollable xterm window. In particular, you should make a note of the lines which describe the geometry of the SCSI disks detected by NetBSD. They are of the form: sd0 at scsibus0 targ 0 lun 0: Maker, Disk, Foo SCSI1 0/direct fixed sd0: 800 MB, 800 cyl, 16 head, 128 sec, 512 bytes/sect x 1638400 sectors The information of most interest is the number of sectors; for the ficti- tious disk above, it's 1638400. You will need this number when you come to create a disklabel for that drive. Here is an example of an MVME147 system booting from tape: RAM address from VMEbus = $00000000 Booting from: VME147, Controller 5, Device 0 Loading: Operating System Volume: NBSD IPL loaded at: $003F0000 BSD MVME147 tapeboot [$Revision: 1.18 $] 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997, 1998, 1999, 2000 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000 steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . Note: The exact text of the messages will vary depending on which mvme68k variant you're using. Finally, you will see the following "welcome" message: Welcome to the NetBSD/mvme68k RAMDISK root! This environment is designed to do only four things: 1: Partition your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Make that partition bootable (using 'installboot') 4: Reboot (using the swap partition, i.e. /dev/sd0b). Copying the miniroot can be done several ways, allowing the source of the miniroot image to be on any of these: boot tape, NFS server, TFTP server, rsh server The easiest is loading from tape, which is done as follows: mt -f /dev/nrst0 rewind mt -f /dev/nrst0 fsf 3 dd if=/dev/nrst0 of=/dev/rsd0b bs=8k conv=sync (For help with other methods, please see the install notes.) To reboot using the swap partition after running installboot, first use halt, then at the Bug monitor prompt use a command like: 1x7Bug bo 0,,b: To view this message again, type: cat /.welcome # You must now create a disklabel on the disk you wish to use for the root file system (/). This will usually be sd0. The disklabel is used by NetBSD to identify the starting block and size of each partition on the disk. Partitions are named sd0a, sd0b, sd0c, etc, up to sd0h. The mvme68k port of NetBSD makes some assumptions about the first three partitions on a boot disk: sd0a The root file system (/). sd0b The swap partition. sd0c The whole disk. Also known as the raw partition. The raw partition is special; NetBSD is able to use it even if the disk has no label. You should never create a file system on the Raw Parti- tion, even on a non-boot disk. It is good practice to put /usr on a different partition than / (root, AKA sd0a). So, the first available partition for /usr is sd0d. Refer to the section entitled NetBSD System Requirements and Supported Devices for information on the recommended sizes of the / (root), /usr and swap par- titions. You are not required to define any partitions beyond sd0d, but if you have a large disk drive, you might want to create several other parti- tions for file systems such as /home or /usr/src. Note that at this time you are only required to partition the root/boot disk; you will get the opportunity to partition any other disks in your system from the main miniroot installation program. To create the disklabel and partitions, use the edlabel program, passing it the name of the Raw Partition of your root/boot disk. # edlabel /dev/rsd0c edlabel menu: print - display the current disk label modify - prompt for changes to the label write - write the new label to disk quit - terminate program edlabel The program shows what commands it recognizes; print, modify, write, and quit. It will accept the first letter of a command if you don't feel like typing each one in full. To start creating the basic partitions, you should enter m (modify) at the edlabel prompt, then enter the letter corresponding to the first partition, a. edlabel m modify subcommands: @: modify disk parameters a-h: modify partition s: standardize geometry q: quit this subcommand edlabel/modify a a (root) 0 (0/00/00) 0 (0/00/00) unused start as blkno or cyls/trks/sects: 0 length as nblks or cyls/trks/sects: 65536 type: 4.2BSD edlabel/modify When you enter the start and length of a partition, you can use either blocks or cylinder/track/sector notation. If this is the first time you've partitioned a disk for NetBSD, it's probably easiest to use block notation. The above example creates partition `a', starting at block zero and with a size of 65536 blocks. Note that the usual size of a block is 512 bytes, so this creates a 32 MB partition. The type of the partition should be 4.2BSD, otherwise you won't be able to create a file system on it. Next, create a swap partition (b). Note that the minimum size of this swap partition should be 8 MB, otherwise you won't be able to use a mini- root to complete the NetBSD installation! edlabel/modify b b (swap) 0 (0/00/00) 0 (0/00/00) unused start as blkno or cyls/trks/sects: 65536 length as nblks or cyls/trks/sects: 32768 type: swap edlabel/modify Here, we specify a value for start such that the swap partition follows immediately after partition `a', i.e. 65536. The length of the swap par- tition should be a multiple of the amount of RAM you have in your system. Here, we've chosen 32768, or 16 MB. The next available block on the drive is thus 65536 + 32768. We will use this to create partition `d' for our /usr file system. (Note that for a busy system, or a system with more than 8 MB of RAM, you'll be better off with a 32 or 64 MB swap par- tition.) edlabel/modify d d (user) 0 (0/00/00) 0 (0/00/00) unused start as blkno or cyls/trks/sects: 98304 length as nblks or cyls/trks/sects: 1540096 type: 4.2BSD edlabel/modify q edlabel As you can see, we've chosen to assign the remainder of the disk to /usr. Since there are 1638400 sectors on the example disk (did you remember to note down the number of sectors on your disk during boot?), and partition d starts at sector 98304, a simple bit of arithmetic (1638400 - 98304) gives d a size of 1540096. Note that the above partition sizes are just guidelines. If your disk is large enough, you should resize the partitions appropriately and perhaps also create a /var partition as well. You now need to write this new disklabel, together with the partition details you've just entered, to disk. You might also try the `p' command to view the partitions. Once written, you can quit back to the shell using `q'. edlabel p type_num: 4 sub_type: 0 type_name: SCSI disk pack_name: fictitious bytes/sector: 512 sectors/track: 128 tracks/cylinder: 16 cylinders: 800 sectors/cylinder: 2048 partition start (c/t/s) nblks (c/t/s) type a (root) 0 (0/00/00) 65536 (32/00/00) 4.2BSD b (swap) 65536 (32/00/00) 32768 (48/00/00) swap c (disk) 0 (0/00/00) 1638400 (800/00/00) unused d (user) 98304 (48/00/00) 1540096 (752/00/00) 4.2BSD edlabel w edlabel q # Now that your disk's partitioned, you need to get the proper installation miniroot image onto it. The miniroot image is designed to be copied into the swap partition of your disk. This is a safe place which won't be overwritten by the installation procedure. From the shell prompt, use the following commands to copy the miniroot image from tape to swap (b). # mt -f /dev/nrst0 rewind # mt -f /dev/nrst0 fsf 3 # dd if=/dev/nrst0 of=/dev/rsd0b bs=8k conv=osync The disk and the miniroot must now be made bootable using the installboot(8) command. To do this, issue the following commands: # mount /dev/sd0b /mnt # installboot /mnt/usr/mdec/bootsd /bootxx /dev/rsd0b # umount /dev/sd0b You can now shutdown the system. # halt signal 15 syncing disks... done unmounting / (root_device)... halted 147-Bug reset Reset Local SCSI Bus [Y,N] N? y Automatic reset of known SCSI Buses on RESET [Y,N] Y? Cold/Warm Reset flag [C,W] = C? Execute Soft Reset [Y,N] N? y Resetting the other types of MVME boards are very similar. You should now reboot from that just installed miniroot. See the section entitled Booting the miniroot for details. Installing from NFS Before you can install from NFS, you must have already configured your NFS server to support your machine as a bootable client. Instructions for configuring the server are found in the section entitled Getting the NetBSD System onto Useful Media above. To get started on the MVME147, you need to download sboot into RAM (you will find sboot in the install directory of the mvme68k distribution). You can either do that through the console line or through a 2nd serial connection. For example, an MVME147 connected to a sun4/110 and accessed via tip(1) can be loaded as follows: lo 0 ~Ccat sboot go 4000 Which will look like this: 147-Bug lo 0 ~CLocal command? cat sboot away for 11 seconds ! 147-Bug g 4000 Effective address: 00004000 sboot: serial line bootstrap program (end = 6018) Now, if you want to do it through serial line 1, then connect serial line one to a machine. At the 147-Bug prompt type tm 1 You should then login to the machine it is connected to. Then press CONTROL-A to escape to Bug. Do lo 1;x=cat sboot ... then when that is done you can reconnect tm 1 and logout. Then do go 4000 and you've got the prompt of sboot. Once you've got the prompt, you can boot the RAMDISK kernel from the server: b le0: ethernet address: 8:0:3e:20:cb:87 My ip address is: 192.168.1.4 Server ip address is: 192.168.1.1 4800 Download was a success! See below for the next step in booting MVME147. The MVME162, MVME167, MVME172 and MVME177 boards are able to download netboot directly using TFTP. To enable this, you must first configure the networking parameters on the board as described in the section enti- tled "Preparing your System for NetBSD Installation. On a properly con- figured MVME162/172 or MVME167/177, all you need to type is: 1xx-Bug nbo For all board types, the boot messages are very similar: Start @ 0x8000 ... BSD MVME147 netboot (via sboot) [$Revision: 1.18 $] device: le0 attached to 08:00:3e:20:cb:87 boot: client IP address: 192.168.1.4 boot: client name: soapy root addr=192.168.1.1 path=/export/soapy 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997, 1998, 1999, 2000 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.5 (RAMDISK) #1: Sun Oct 29 16:19:04 GMT 2000 steve@fatbob:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . After the boot program loads the RAMDISK kernel, you should see the wel- come screen as shown in the "tape boot" section above. You now need to create a disklabel with partition information on the SCSI disk on which you intend to create your root file system (/). Follow the instructions in the previous section entitled Installing from tape to do this. (But stop short of the part which describes how to copy the mini- root from tape.) You must now configure the network interface before you can access the NFS server containing the miniroot image. For example the command: # ifconfig le0 inet 192.168.1.4 up will bring up the MVME147 network interface le0 with that address. The command: # ifconfig ie0 inet 192.168.1.4 up will bring up the MVME162/172 or MVME167/177 network interface ie0 with that address. The next step is to copy the miniroot from your server. This can be done using either NFS or remote shell. (In the examples that follow, the server has IP address 192.168.1.1) You may then need to add a default route if the server is on a different subnet: # route add default 192.168.1.2 1 You can look at the route table using: # route show Now mount the NFS file system containing the miniroot image: # mount -r 192.168.1.1:/export/soapy /mnt The procedure is simpler if you have space for an expanded (not com- pressed) copy of the miniroot image. In that case: # dd if=/mnt/miniroot of=/dev/rsd0b bs=8k Otherwise, you will need to use gzcat to expand the miniroot image while copying. # gzcat miniroot.fs.gz | dd of=/dev/rsd0b obs=8k conv=osync You must now make the disk bootable. Refer to the previous section on installing from tape, where it describes how to run installboot. This is immediately following the part which explains how to copy the miniroot from tape. Booting the miniroot Assuming the miniroot is installed on partition `b' of the disk with SCSI-ID 0, then the boot command is: 1xx-Bug bo 0,,b: The command line parameters above are: 0 controller (usually zero) ,, bug argument separators b: tell the bootstrap code to boot from partition b You should see a bunch of boot messages, followed by messages from the miniroot kernel just as you did when the RAMDISK kernel booted. You will then be prompted to enter the root device. Since the miniroot was booted from the swap partition, you should enter sd0b. You will then be asked for the swap device and file system type. Just press RETURN twice to accept the defaults. When asked to enter a terminal type, either accept the default, or use whatever the TERM environment variable is set to in the shell of your host system: boot device: sd0 root device (default sd0a): sd0b dump device (default sd0b): (return) file system (default generic): (return) root on sd0b dumps on sd0b mountroot: trying ffs... root file system type: ffs init: copying out path `/sbin/init' 11 erase ^H, werase ^W, kill ^U, intr ^C Terminal type? [vt100] return Congratulations! The system should now be running the miniroot installa- tion program. Miniroot install program: The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. Starting with NetBSD version 1.6, you have the option of using sysinst instead of the old installation and upgrade shell scripts. At this time, sysinst is not capable of installing distribution sets from tape. In such a case, you should fallback to the shell script installation or upgrade procedure. In all other cases, sysinst should be used. Note that as soon as sysinst can deal with tapes, the shell script tools will be removed. The miniroot's install program (both sysinst and the shell script ver- sion) will: o Allow you to place disklabels on additional disks. The disk we are installing on should already have been partitioned using the RAMDISK kernel. Note that partition sizes and offsets are expressed in sectors. When you fill out the disklabel, you will need to specify partition types and file system parameters. If you're unsure what these values should be, use the following defaults: fstype: 4.2BSD fsize: 1024 bsize: 4096 cpg: 16 If the partition will be a swap partition, use the following: fstype: swap fsize: 0 (or blank) bsize: 0 (or blank) cpg: 0 (or blank) Note that partition `c' is special; it covers then entire disk and should not be assigned to a file system. The number of partitions is currently fixed at 8. o Create file systems on target partitions. o Allow you to set up your system's network configuration. Remember to specify host names without the domain name appended to the end. For example use foo instead of foo.bar.org. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for con- figuration again. o Mount target file systems. You will be given the opportunity to man- ually edit the resulting /etc/fstab. o Extract binary sets from the media of your choice. o Copy configuration information gathered during the installation process to your root file system (/). o Make device nodes in your root file system under /dev. o Copy a new kernel onto your root partition (/). o Install a new boot block. o Check your file systems for integrity. First-time installation on a system through a method other than the installation program is possible, but strongly discouraged. Running the sysinst installation program 1. Introduction Using sysinst, installing NetBSD is a relatively easy process. You still should read this document and have it in hand when doing the installation process. This document tries to be a good guideline for the installation and as such covers many details for the sake of completeness. Do not let this discourage you; the install program is not hard to use. 2. General The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. sysinst is a menu driven installation system that allows for some freedom in doing the installation. Sometimes, questions will be asked and in many cases the default answer will be displayed in brackets (``[ ]'') after the question. If you wish to stop the installation, you may press CONTROL-C at any time, but if you do, you'll have to begin the installation process again from scratch by running the /sysinst pro- gram from the command prompt. It is not necessary to reboot. 3. Quick install First, let's describe a quick install. The other sections of this document go into the installation procedure in more detail, but you may find that you do not need this. If you want detailed instruc- tions, skip to the next section. This section describes a basic installation, using a CD-ROM install as an example. o What you need. - The distribution sets (in this example, they are on CD). - One 1.44 MB 3.5" floppy. - A CD-ROM drive (SCSI), a hard disk and a minimum of 4 MB of memory installed. - The hard disk should have at least 100 + n megabytes of space free, where n is the number of megabytes of main mem- ory in your system. If you wish to install the X Window System as well, you will need at least 120 MB more. o The Quick Installation - Insert the first boot floppy you just created. Boot the computer. After language selection, the main menu will be displayed. .***********************************************. * NetBSD-4.0 Install System * * * *>a: Install NetBSD to hard disk * * b: Upgrade NetBSD on a hard disk * * c: Re-install sets or install additional sets * * d: Reboot the computer * * e: Utility menu * * x: Exit Install System * .***********************************************. - If you wish, you can configure some network settings immedi- ately by choosing the Utility menu and then Configure network. It isn't actually required at this point, but it may be more convenient. Go back to the main menu. - Choose install. - You will be guided through some steps regarding the setup of your disk, and the selection of distributed components to install. When in doubt, refer to the rest of this document for details. - After your disk has been prepared, choose CD-ROM as the medium. The default values for the path and device should be ok. - After all the files have been unpacked, go back to the main menu and select reboot, after you have removed the boot- floppy from the drive. - NetBSD will now boot. If you haven't already done so in sysinst, you should log in as root, and set a password for that account. You are also advised to edit the file /etc/rc.conf to match your system needs. - Your installation is now complete. - For configuring the X window system, if installed, see the files in /usr/X11R6/lib/X11/doc. Further information can be found on http://www.xfree86.org/. 4. Booting NetBSD Boot your machine. The boot loader will start, and will print a countdown and begin booting. If the boot loader messages do not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the install floppy image to a different disk, and using that. It will take a while to load the kernel from the floppy, probably around a minute or so, then, the kernel boot messages will be dis- played. This may take a little while also, as NetBSD will be prob- ing your system to discover which hardware devices are installed. The most important thing to know is that wd0 is NetBSD's name for your first IDE disk, wd1 the second, etc. sd0 is your first SCSI disk, sd1 the second, etc. Note that once the system has finished booting, you need not leave the floppy in the disk drive. Once NetBSD has booted and printed all the boot messages, you will be presented with a welcome message and a main menu. It will also include instructions for using the menus. 5. Network configuration If you will not use network operation during the installation, but you do want your machine to be configured for networking once it is installed, you should first go to the Utility menu, and select the Configure network option. If you only want to temporarily use net- working during the installation, you can specify these parameters later. If you are not using the Domain Name System (DNS), you can give an empty response in reply to answers relating to this. 6. Installation drive selection and parameters To start the installation, select Install NetBSD to hard disk from the main menu. The first thing is to identify the disk on which you want to install NetBSD. sysinst will report a list of disks it finds and ask you for your selection. Depending on how many disks are found, you may get a different message. You should see disk names like sd0 or sd1. 7. Partitioning the disk o Which portion of the disk to use. You will be asked if you want to use the entire disk or only part of the disk. If you decide to use the entire disk for NetBSD, it will be checked if there are already other systems present on the disk, and you will be asked to confirm whether you want to overwrite these. 8. Editing the NetBSD disklabel The partition table of the NetBSD part of a disk is called a disklabel. There are 4 layouts for the NetBSD part of the disk that you can pick from: Standard, Standard with X, Custom and Use Existing. The first two use a set of default values (that you can change) suitable for a normal installation, possibly including X. With the Custom option you can specify everything yourself. The last option uses the partition info already present on the disk. You will be presented with the current layout of the NetBSD diskla- bel, and given a chance to change it. For each partition, you can set the type, offset and size, block and fragment size, and the mount point. The type that NetBSD uses for normal file storage is called 4.2BSD. A swap partition has a special type called swap. Some partitions in the disklabel have a fixed purpose. a Root partition (/) b Swap partition. c The NetBSD portion of the disk. d-h Available for other use. Traditionally, d is the par- tition mounted on /usr, but this is historical prac- tice and not a fixed value. You will then be asked to name your disk's disklabel. The default response will be ok for most purposes. If you choose to name it something different, make sure the name is a single word and con- tains no special characters. You don't need to remember this name. 9. Preparing your hard disk You are now at the point of no return. Nothing has been written to your disk yet, but if you confirm that you want to install NetBSD, your hard drive will be modified. If you are sure you want to pro- ceed, enter yes at the prompt. The install program will now label your disk and make the file sys- tems you specified. The file systems will be initialized to contain NetBSD bootstrapping binaries and configuration files. You will see messages on your screen from the various NetBSD disk preparation tools that are running. There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. Otherwise, you can continue the installa- tion program after pressing the return key. 10. Getting the distribution sets The NetBSD distribution consists of a number of sets, that come in the form of gzipped tarfiles. A few sets must be installed for a working system, others are optional. At this point of the installa- tion, you will be presented with a menu which enables you to choose from one of the following methods of installing the sets. Some of these methods will first load the sets on your hard disk, others will extract the sets directly. For all these methods, the first step is making the sets available for extraction, and then do the actual installation. The sets can be made available in a few different ways. The following sections describe each of those methods. After reading the one about the method you will be using, you can continue to the section labeled `Extracting the distribution sets'. 11. Installation using ftp To be able to install using ftp, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you if you want to use DHCP, and if not to provide data like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these ques- tions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, the directory on that host, the account name and password used to log into that host using ftp, and optionally a proxy server to use. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the ftp server. sysinst will proceed to transfer all the default set files from the remote site to your hard disk. 12. Installation using NFS To be able to install using NFS, you first need to configure your network setup, if you haven't already at the start of the install procedure. sysinst will do this for you, asking you if you want to use DHCP, and if not to provide data like IP address, hostname, etc. If you do not have name service set up for the machine that you are installing on, you can just press RETURN in answer to these ques- tions, and DNS will not be used. You will also be asked to specify the host that you want to transfer the sets from, and the directory on that host that the files are in. This directory should be mountable by the machine you are installing on, i.e. correctly exported to your machine. If you did not set up DNS when answering the questions to configure networking, you will need to specify an IP address instead of a hostname for the NFS server. 13. Installation from CD-ROM When installing from a CD-ROM, you will be asked to specify the device name for your CD-ROM player (usually cd0), and the directory name on the CD-ROM where the distribution files are. sysinst will then check if the files are indeed available in the specified location, and proceed to the actual extraction of the sets. 14. Installation from an unmounted file system In order to install from a local file system, you will need to spec- ify the device that the file system resides on (for example sd1e) the type of the file system, and the directory on the specified file system where the sets are located. sysinst will then check if it can indeed access the sets at that location. 15. Installation from a local directory This option assumes that you have already done some preparation yourself. The sets should be located in a directory on a file sys- tem that is already accessible. sysinst will ask you for the name of this directory. 16. Extracting the distribution sets After the install sets containing the NetBSD distribution have been made available, you can either extract all the sets (a full instal- lation), or only extract sets that you have selected. In the latter case, you will be shown the currently selected sets, and given the opportunity to select the sets you want. Some sets always need to be installed (kern, base, and etc) they will not be shown in this selection menu. Before extraction begins, you can elect to watch the files being extracted; the name of each file that is extracted will be shown. This can slow down the installation process considerably, especially on machines with slow graphics consoles or serial consoles. Alter- natively, you will be asked if you wish to have a progress bar. This is the preferred option as it shows progress without signifi- cantly slowing down the installation process. After all the files have been extracted, all the necessary device node files will be created. If you have already configured network- ing, you will be asked if you want to use this configuration for normal operation. If so, these values will be installed in the net- work configuration files. The next menu will allow you to select the time zone that you're in, to make sure your clock has the right offset from UTC. Finally you will be asked to select a password encryption algorithm and can then set a password for the "root" account, to prevent the machine coming up without access restric- tions. 17. Finalizing your installation Congratulations, you have successfully installed NetBSD 4.0. You can now reboot the machine, and boot NetBSD from hard disk. Post installation steps Once you've got the operating system running, there are a few things you need to do in order to bring the system into a properly configured state, with the most important ones described below. 1. Configuring /etc/rc.conf If you or the installation software haven't done any configuration of /etc/rc.conf (sysinst usually will), the system will drop you into single user mode on first reboot with the message /etc/rc.conf is not configured. Multiuser boot aborted. and with the root file system (/) mounted read-only. When the sys- tem asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a terminal type, respond with vt220 (or whatever is appropriate for your terminal type) and press RETURN. You may need to type one of the following commands to get your delete key to work properly, depending on your keyboard: # stty erase '^h' # stty erase '^?' At this point, you need to configure at least one file in the /etc directory. You will need to mount your root file system read/write with: # /sbin/mount -u -w / Change to the /etc directory and take a look at the /etc/rc.conf file. Modify it to your tastes, making sure that you set rc_configured=YES so that your changes will be enabled and a multi- user boot can proceed. Default values for the various programs can be found in /etc/defaults/rc.conf, where some in-line documentation may be found. More complete documentation can be found in rc.conf(5). If your /usr directory is on a separate partition and you do not know how to use ed, you will have to mount your /usr partition to gain access to ex or vi. Do the following: # mount /usr # export TERM=vt220 If you have /var on a separate partition, you need to repeat that step for it. After that, you can edit /etc/rc.conf with vi(1). When you have finished, type exit at the prompt to leave the single- user shell and continue with the multi-user boot. Other values that need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your network interface, along the lines of ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_le0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an /etc/resolv.conf file or (if you are feeling a little more adventur- ous) run named(8). See resolv.conf(5) or named(8) for more informa- tion. Instead of manually configuring network and naming service, DHCP can be used by setting dhclient=YES in /etc/rc.conf. Other files in /etc that may require modification or setting up include /etc/mailer.conf, /etc/nsswitch.conf, and /etc/wscons.conf. 2. Logging in After reboot, you can log in as root at the login prompt. Unless you've set a password in sysinst, there is no initial password. If you're using the machine in a networked environment, you should cre- ate an account for yourself (see below) and protect it and the ``root'' account with good passwords. By default, root login from the network is disabled (even via ssh(1)). One way to become root over the network is to log in as a different user that belongs to group ``wheel'' (see group(5)) and use su(1) to become root. Unless you have connected an unusual terminal device as the console you can just press RETURN when it prompts for Terminal type? [...]. 3. Adding accounts Use the useradd(8) command to add accounts to your system. Do not edit /etc/passwd directly! See vipw(8) and pwd_mkdb(8) if you want to edit the password database. 4. The X Window System If you have installed the X Window System, look at the files in /usr/X11R6/lib/X11/doc for information. Don't forget to add /usr/X11R6/bin to your path in your shell's dot file so that you have access to the X binaries. 5. Installing third party packages If you wish to install any of the software freely available for UNIX-like systems you are strongly advised to first check the NetBSD package system. This automatically handles any changes necessary to make the software run on NetBSD, retrieval and installation of any other packages on which the software may depend, and simplifies installation (and deinstallation), both from source and precompiled binaries. o More information on the package system is at http://www.NetBSD.org/docs/software/packages.html o A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/README.html o Precompiled binaries can be found at ftp://ftp.NetBSD.org/pub/NetBSD/packages/ usually in the 4.0/mvme68k/All subdir. You can install them with the following commands under sh(1): # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/mvme68k/All # export PKG_PATH # pkg_add -v tcsh # pkg_add -v bash # pkg_add -v perl # pkg_add -v apache # pkg_add -v kde # pkg_add -v firefox ... If you are using csh(1) then replace the first two lines with the following: # setenv PKG_PATH ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/mvme68k/All ... The above commands will install the Tenex-csh and Bourne Again shell, the Perl programming language, Apache web server, KDE desktop environment and the Firefox web browser as well as all the packages they depend on. o Package sources for compiling packages on your own can be obtained by retrieving the file ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc.tar.gz They are typically extracted into /usr/pkgsrc (though other locations work fine), with the commands: # mkdir /usr/pkgsrc # cd /usr/pkgsrc # tar -zxpf pkgsrc.tar.gz After extracting, see the README and doc/pkgsrc.txt files in the extraction directory (e.g. /usr/pkgsrc/README) for more infor- mation. 6. Misc o Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) afterwards. o The /etc/postfix/main.cf file will almost definitely need to be adjusted. If you prefer a different MTA, then install it using the NetBSD package system or by hand and adjust /etc/mailer.conf. o Edit /etc/rc.local to run any local daemons you use. o Many of the /etc files are documented in section 5 of the man- ual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System It is possible to easily upgrade your existing NetBSD/mvme68k system using the upgrade program in the miniroot or by manually performing the same steps as the miniroot upgrade program. Upgrading using the miniroot If you wish to upgrade your system by this method, simply select the upgrade option once the miniroot has booted. The upgrade program with then guide you through the procedure. The upgrade program will: 1. Enable the network based on your system's current network configura- tion. 2. Mount your existing file systems. 3. Extract binary sets from the media of your choice. 4. Fixup your system's existing /etc/fstab, changing the occurrences of ufs to ffs and let you edit the resulting file. 5. Make new device nodes in your root file system under /dev. 6. Don't forget to extract the kern set from the distribution. Note: The existing kernel will not be backed up; doing so would be pointless, since older kernels may not be capable of running NetBSD 4.0 executables. 7. Install a new boot block. 8. Check your file systems for integrity. 9. You'll have to reboot your system manually Manual upgrade While using the miniroot's upgrade program is the preferred method of upgrading your system, it is possible to upgrade your system manually. To do this, follow the following procedure: 1. Place at least the base binary set in a file system accessible to the target machine. A local file system is preferred, since the NFS subsystem in the NetBSD 4.0 kernel may be incompatible with your old binaries. 2. Back up your pre-existing kernel and copy the 4.0 kernel into your root partition (/). 3. Reboot with the 4.0 kernel into single-user mode. 4. Check all file systems: # /sbin/fsck -pf 5. Mount all local file systems: # /sbin/mount -a -t nonfs 6. If you keep /usr or /usr/share on an NFS server, you will want to mount those file systems as well. To do this, you will need to enable the network: # sh /etc/rc.d/network start 7. Make sure you are in the root file system (/) and extract the base binary set: # cd / # pax -zrvpe -f /path/to/base.tgz 8. Install a new boot block: # cd /usr/mdec # cp bootsd /.bootsd # ./installboot /.bootsd bootxx root-disk E.g.: root-disk could be /dev/rsd0a. 9. Sync the file systems: # sync 10. At this point you may extract any other binary sets you may have placed on local file systems, or you may wish to extract additional sets at a later time. To extract these sets, use the following com- mands: # cd / # pax -zrvpe -f path_to_set Note: You should not extract the etc set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand. Compatibility Issues With Previous NetBSD Releases Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 4.0 . N.B. when using sysinst for upgrading, it will automatically invoke postinstall fix and thus all issues that are fixed by postinstall by default (see below) will be handled. Issues affecting an upgrade from NetBSD 2.1 and older releases. See the section below on upgrading from NetBSD 3.x as well. It is very important that you populate the directory /etc/pam.d with appropriate configuration files for Pluggable Authentication Modules (PAM) because you will not be able to login any more otherwise. Using postinstall as described below will take care of this. Please refer to http://www.NetBSD.org/docs/guide/en/chap-pam.html for documentation about PAM. The following issues can generally be resolved by running postinstall with the etc set : postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/pam.d/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* The following issues need to be resolved manually: o The user `_pflogd' and the groups `_pflogd' and `authpf' need to be created. Issues affecting an upgrade from NetBSD 3.x releases. The following issues can generally be resolved by running postinstall with the etc set : postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: o Various files in /etc need upgrading. These include: - /etc/defaults/* - /etc/mtree/* - /etc/daily - /etc/weekly - /etc/monthly - /etc/security - /etc/rc.subr - /etc/rc - /etc/rc.shutdown - /etc/rc.d/* - /etc/envsys.conf The following issues need to be resolved manually: o The users `_proxy', `_rwhod', and `_sdpd' and the groups `_proxy', `_rwhod' and `_sdpd' need to be created and the user `uucp' needs to be updated. o A number of things have been removed from the NetBSD 4.0 release including: the evbsh5 port, the Fortran 77 compiler (g77), NETCCITT, NETNS, Sendmail, Sushi, UUCP, and Vinum. If you were using any of these, then please see the "Components removed from NetBSD" section near the beginning of this docu- ment. o The replacement of Sendmail by Postfix can be handled automati- cally by postinstall but it is not done by default. If you want to transition to Postfix, the command postinstall -s /path/to/etc.tgz fix mailerconf will update your /etc/mailer.conf file to use Postfix as the MTA. When using sysinst to upgrade the system, it will ask if you want this to be done. Note that if you have a customized Sendmail setup, you need to set up Postfix in an equivalent way; there is no tool for auto- matic conversion of Sendmail configuration to a Postfix one. Postfix will be started up automatically when the system boots. You may see messages like "$sendmail is not set properly" at boot. You can suppress them by removing /etc/rc.d/sendmail and /etc/rc.d/smmsp. Those files and other parts of sendmail con- figuration like files under /usr/share/sendmail are not removed by default while upgrading for those who want to continue using sendmail from outside the base system. If you want to delete them, postinstall can be used: postinstall -s /path/to/etc.tgz fix sendmail Issues with GDB 6.5 Some architectures (arm, i386, powerpc and sparc64) have switched to a newer gdb version (6.5) in this release. Unfortunately support for debugging programs using the SA (scheduler activation) based thread library, is incomplete in this gdb version. Furthermore kernel crash- dumps can not be debugged due to a missing identification in the kernel binaries. Both issues have been addressed on the wrstuden-fixsa branch, but did not make it into the NetBSD release. Both will be fixed in the next patch release. Using online NetBSD documentation Documentation is available if you first install the manual distribution set. Traditionally, the ``man pages'' (documentation) are denoted by `name(section)'. Some examples of this are o intro(1), o man(1), o apropros(1), o passwd(1), and o passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The man command is used to view the documentation on a topic, and is started by entering man [section] topic. The brackets [] around the sec- tion should not be entered, but rather indicate that the section is optional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after log- ging in, enter # man passwd to read the documentation for passwd(1). To view the documentation for passwd(5), enter # man 5 passwd instead. If you are unsure of what man page you are looking for, enter # apropos subject-word where subject-word is your topic of interest; a list of possibly related man pages will be displayed. Administrivia If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at majordomo@NetBSD.org. To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instruc- tions. There are various mailing lists set up to deal with comments and ques- tions about this release. Please send comments to: netbsd-comments@NetBSD.org. To report bugs, use the send-pr(1) command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.org. Use of send-pr(1) is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses, or visit http://www.NetBSD.org/mailinglists/. If you're interested in doing a serious amount of work on a specific port, you probably should contact the `owner' of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send us mail or subscribe to: netbsd-help@NetBSD.org. As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP or WWW somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to o The former members of UCB's Computer Systems Research Group, includ- ing (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. o The Internet Systems Consortium, Inc. for hosting the NetBSD FTP, CVS, AnonCVS, mail, mail archive, GNATS, SUP, Rsync and WWW servers. o The Internet Research Institute in Japan for hosting the server which runs the CVSweb interface to the NetBSD source tree. o The Lulea Academic Computer Society for providing the backup services server. o The Columbia University Computer Science Department for hosting the NYC build cluster. o The Western Washington University Computer Science Department for running the WWU build cluster that produces daily snapshots. o The many organizations that provide NetBSD mirror sites. o Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. o We list the individuals and organizations that have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it at http://www.NetBSD.org/donations/. (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) o Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to be mentioned, tell us!) We are... (in alphabetical order) The NetBSD core group: Alistair Crooks agc@NetBSD.org Quentin Garnier cube@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Matt Thomas matt@NetBSD.org Christos Zoulas christos@NetBSD.org The portmasters (and their ports): Anders Magnusson ragge vax Andrew Doran ad amd64 Andrew Doran ad i386 Andrey Petrov petrov sparc64 Ben Harris bjh21 acorn26 Cherry G. Mathew cherry ia64 Chris Gilbert chris cats Darrin Jewell dbj next68k Erik Berls cyber cobalt Gavan Fantom gavan iyonix IWAMOTO Toshihiro toshii hpcarm Ichiro FUKUHARA ichiro hpcarm Ignatios Souvatzis is amiga Izumi Tsutsui tsutsui ews4800mips Izumi Tsutsui tsutsui hp300 Izumi Tsutsui tsutsui news68k Jaime A Fournier ober bebox Jaime A Fournier ober zaurus Jason Thorpe thorpej algor Jason Thorpe thorpej evbarm Jason Thorpe thorpej shark Jonathan Stone jonathan pmax Julian Coleman jdc atari Manuel Bouyer bouyer xen Marcus Comstedt marcus dreamcast Martin Husemann martin sparc64 Matt Fredette fredette sun2 Matt Thomas matt alpha Matt Thomas matt netwinder Matthias Drochner drochner cesfic Michael Lorenz macallan macppc NISHIMURA Takeshi nsmrtks x68k Nathan Williams nathanw sun3 Nick Hudson skrll hp700 Noriyuki Soda soda arc Paul Kranenburg pk sparc Phil Nelson phil pc532 Reinoud Zandijk reinoud acorn32 Ross Harvey ross alpha Soren Jorvang soren sgimips Scott Reynolds scottr mac68k Shin Takemura takemura hpcmips Simon Burge simonb evbmips Simon Burge simonb pmax Simon Burge simonb sbmips Steve Woodford scw evbppc Steve Woodford scw mvme68k Steve Woodford scw mvmeppc Takayoshi Kochi kochi ia64 Tim Rightnour garbled prep Tohru Nishimura nisimura luna68k Tohru Nishimura nisimura sandpoint Wayne Knowles wdk mipsco Wolfgang Solfrank ws ofppc The NetBSD 4.0 Release Engineering team: Grant Beattie grant@NetBSD.org Manuel Bouyer bouyer@NetBSD.org David Brownlee abs@NetBSD.org Pavel Cahyna pavel@NetBSD.org James Chacon jmc@NetBSD.org Julian Coleman jdc@NetBSD.org Havard Eidnes he@NetBSD.org Liam J. Foy liamjfoy@NetBSD.org John Heasley heas@NetBSD.org Geert Hendrickx ghen@NetBSD.org Soren Jacobsen snj@NetBSD.org Daniel de Kok daniel@NetBSD.org Phil Nelson phil@NetBSD.org Jeff Rizzo riz@NetBSD.org NetBSD Developers: Nathan Ahlstrom nra@NetBSD.org Steve Allen wormey@NetBSD.org Jukka Andberg jandberg@NetBSD.org Julian Assange proff@NetBSD.org Lennart Augustsson augustss@NetBSD.org Christoph Badura bad@NetBSD.org Bang Jun-Young junyoung@NetBSD.org Dieter Baron dillo@NetBSD.org Robert V. Baron rvb@NetBSD.org Alan Barrett apb@NetBSD.org Grant Beattie grant@NetBSD.org Jason Beegan jtb@NetBSD.org Erik Berls cyber@NetBSD.org Hiroyuki Bessho bsh@NetBSD.org John Birrell jb@NetBSD.org Mason Loring Bliss mason@NetBSD.org Charles Blundell cb@NetBSD.org Rafal Boni rafal@NetBSD.org Stephen Borrill sborrill@NetBSD.org Sean Boudreau seanb@NetBSD.org Manuel Bouyer bouyer@NetBSD.org John Brezak brezak@NetBSD.org Allen Briggs briggs@NetBSD.org Mark Brinicombe mark@NetBSD.org Aaron Brown abrown@NetBSD.org Andrew Brown atatat@NetBSD.org David Brownlee abs@NetBSD.org Frederick Bruckman fredb@NetBSD.org Jon Buller jonb@NetBSD.org Simon Burge simonb@NetBSD.org Robert Byrnes byrnes@NetBSD.org Pavel Cahyna pavel@NetBSD.org D'Arcy J.M. Cain darcy@NetBSD.org Dave Carrel carrel@NetBSD.org Daniel Carosone dan@NetBSD.org James Chacon jmc@NetBSD.org Bill Coldwell billc@NetBSD.org Julian Coleman jdc@NetBSD.org Ben Collver ben@NetBSD.org Jeremy Cooper jeremy@NetBSD.org Chuck Cranor chuck@NetBSD.org Alistair Crooks agc@NetBSD.org Aidan Cully aidan@NetBSD.org Garrett D'Amore gdamore@NetBSD.org Johan Danielsson joda@NetBSD.org John Darrow jdarrow@NetBSD.org Jed Davis jld@NetBSD.org Matt DeBergalis deberg@NetBSD.org Arnaud Degroote degroote@NetBSD.org Rob Deker deker@NetBSD.org Chris G. Demetriou cgd@NetBSD.org Tracy Di Marco White gendalia@NetBSD.org Jaromir Dolecek jdolecek@NetBSD.org Andy Doran ad@NetBSD.org Roland Dowdeswell elric@NetBSD.org Emmanuel Dreyfus manu@NetBSD.org Matthias Drochner drochner@NetBSD.org Jun Ebihara jun@NetBSD.org Havard Eidnes he@NetBSD.org Stoned Elipot seb@NetBSD.org Michael van Elst mlelstv@NetBSD.org Enami Tsugutomo enami@NetBSD.org Bernd Ernesti veego@NetBSD.org Erik Fair fair@NetBSD.org Gavan Fantom gavan@NetBSD.org Hauke Fath hauke@NetBSD.org Hubert Feyrer hubertf@NetBSD.org Jason R. Fink jrf@NetBSD.org Matt J. Fleming mjf@NetBSD.org Marty Fouts marty@NetBSD.org Liam J. Foy liamjfoy@NetBSD.org Matt Fredette fredette@NetBSD.org Thorsten Frueauf frueauf@NetBSD.org Castor Fu castor@NetBSD.org Ichiro Fukuhara ichiro@NetBSD.org Quentin Garnier cube@NetBSD.org Thomas Gerner thomas@NetBSD.org Simon J. Gerraty sjg@NetBSD.org Justin Gibbs gibbs@NetBSD.org Chris Gilbert chris@NetBSD.org Eric Gillespie epg@NetBSD.org Michael Graff explorer@NetBSD.org Brian C. Grayson bgrayson@NetBSD.org Matthew Green mrg@NetBSD.org Andreas Gustafsson gson@NetBSD.org Ulrich Habel rhaen@NetBSD.org Jun-ichiro itojun Hagino itojun@NetBSD.org Adam Hamsik haad@NetBSD.org Juergen Hannken-Illjes hannken@NetBSD.org Charles M. Hannum mycroft@NetBSD.org Ben Harris bjh21@NetBSD.org Ross Harvey ross@NetBSD.org Eric Haszlakiewicz erh@NetBSD.org John Hawkinson jhawk@NetBSD.org HAMAJIMA Katsuomi hamajima@NetBSD.org HAYAKAWA Koichi haya@NetBSD.org John Heasley heas@NetBSD.org Geert Hendrickx ghen@NetBSD.org Rene Hexel rh@NetBSD.org Iain Hibbert plunky@NetBSD.org Kouichirou Hiratsuka hira@NetBSD.org Michael L. Hitch mhitch@NetBSD.org Jachym Holecek freza@NetBSD.org Christian E. Hopps chopps@NetBSD.org Ken Hornstein kenh@NetBSD.org Marc Horowitz marc@NetBSD.org Eduardo Horvath eeh@NetBSD.org Nick Hudson skrll@NetBSD.org Shell Hung shell@NetBSD.org Martin Husemann martin@NetBSD.org Dean Huxley dean@NetBSD.org Love Hornquist Astrand lha@NetBSD.org Bernardo Innocenti bernie@NetBSD.org Tetsuya Isaki isaki@NetBSD.org ITOH Yasufumi itohy@NetBSD.org IWAMOTO Toshihiro toshii@NetBSD.org Matthew Jacob mjacob@NetBSD.org Soren Jacobsen snj@NetBSD.org Lonhyn T. Jasinskyj lonhyn@NetBSD.org Darrin Jewell dbj@NetBSD.org Nicolas Joly njoly@NetBSD.org Chris Jones cjones@NetBSD.org Soren Jorvang soren@NetBSD.org Takahiro Kambe taca@NetBSD.org Antti Kantee pooka@NetBSD.org Masanori Kanaoka kanaoka@NetBSD.org Frank Kardel kardel@NetBSD.org Mattias Karlsson keihan@NetBSD.org KAWAMOTO Yosihisa kawamoto@NetBSD.org Mario Kemper magick@NetBSD.org Min Sik Kim minskim@NetBSD.org Thomas Klausner wiz@NetBSD.org Klaus Klein kleink@NetBSD.org John Klos jklos@NetBSD.org Wayne Knowles wdk@NetBSD.org Takayoshi Kochi kochi@NetBSD.org John Kohl jtk@NetBSD.org Daniel de Kok daniel@NetBSD.org Paul Kranenburg pk@NetBSD.org Lubomir Kundrak lkundrak@NetBSD.org Martti Kuparinen martti@NetBSD.org Kentaro A. Kurahone kurahone@NetBSD.org Kevin Lahey kml@NetBSD.org David Laight dsl@NetBSD.org Johnny C. Lam jlam@NetBSD.org Martin J. Laubach mjl@NetBSD.org Greg Lehey grog@NetBSD.org Ted Lemon mellon@NetBSD.org Christian Limpach cl@NetBSD.org Frank van der Linden fvdl@NetBSD.org Joel Lindholm joel@NetBSD.org Mike Long mikel@NetBSD.org Michael Lorenz macallan@NetBSD.org Warner Losh imp@NetBSD.org Tomasz Luchowski zuntum@NetBSD.org Federico Lupi federico@NetBSD.org Brett Lymn blymn@NetBSD.org Paul Mackerras paulus@NetBSD.org Anders Magnusson ragge@NetBSD.org MAEKAWA Masahide gehenna@NetBSD.org David Maxwell david@NetBSD.org Dan McMahill dmcmahill@NetBSD.org Gregory McGarry gmcgarry@NetBSD.org Jared D. McNeill jmcneill@NetBSD.org Neil J. McRae neil@NetBSD.org Perry Metzger perry@NetBSD.org Simas Mockevicius symka@NetBSD.org Juan Romero Pardines xtraeme@NetBSD.org Julio M. Merino Vidal jmmv@NetBSD.org Minoura Makoto minoura@NetBSD.org Luke Mewburn lukem@NetBSD.org der Mouse mouse@NetBSD.org Joseph Myers jsm@NetBSD.org Ken Nakata kenn@NetBSD.org Takeshi Nakayama nakayama@NetBSD.org Phil Nelson phil@NetBSD.org John Nemeth jnemeth@NetBSD.org Bob Nestor rnestor@NetBSD.org NISHIMURA Takeshi nsmrtks@NetBSD.org Tohru Nishimura nisimura@NetBSD.org NONAKA Kimihiro nonaka@NetBSD.org Takehiko NOZAKI tnozaki@NetBSD.org Tobias Nygren tnn@NetBSD.org OBATA Akio obache@NetBSD.org Jesse Off joff@NetBSD.org Tatoku Ogaito tacha@NetBSD.org OKANO Takayoshi kano@NetBSD.org Masaru Oki oki@NetBSD.org Atsushi Onoe onoe@NetBSD.org Greg Oster oster@NetBSD.org Jonathan Perkin sketch@NetBSD.org Herb Peyerl hpeyerl@NetBSD.org Matthias Pfaller matthias@NetBSD.org Chris Pinnock cjep@NetBSD.org Adrian Portelli adrianp@NetBSD.org Rui Paulo rpaulo@NetBSD.org Peter Postma peter@NetBSD.org Dante Profeta dante@NetBSD.org Chris Provenzano proven@NetBSD.org Niels Provos provos@NetBSD.org Mindaugas Rasiukevicius rmind@NetBSD.org Michael Rauch mrauch@NetBSD.org Marc Recht recht@NetBSD.org Darren Reed darrenr@NetBSD.org Jeremy C. Reed reed@NetBSD.org Antoine Reilles tonio@NetBSD.org Tyler R. Retzlaff rtr@NetBSD.org Scott Reynolds scottr@NetBSD.org Michael Richardson mcr@NetBSD.org Tim Rightnour garbled@NetBSD.org Alan Ritter rittera@NetBSD.org Jeff Rizzo riz@NetBSD.org Gordon Ross gwr@NetBSD.org Steve Rumble rumble@NetBSD.org Ilpo Ruotsalainen lonewolf@NetBSD.org Heiko W. Rupp hwr@NetBSD.org David Sainty dsainty@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org Kazuki Sakamoto sakamoto@NetBSD.org Curt Sampson cjs@NetBSD.org Wilfredo Sanchez wsanchez@NetBSD.org Ty Sarna tsarna@NetBSD.org SATO Kazumi sato@NetBSD.org Jan Schaumann jschauma@NetBSD.org Matthias Scheler tron@NetBSD.org Karl Schilke (rAT) rat@NetBSD.org Amitai Schlair schmonz@NetBSD.org Konrad Schroder perseant@NetBSD.org Georg Schwarz schwarz@NetBSD.org Lubomir Sedlacik salo@NetBSD.org Christopher SEKIYA sekiya@NetBSD.org Reed Shadgett dent@NetBSD.org John Shannon shannonjr@NetBSD.org Tim Shepard shep@NetBSD.org Takeshi Shibagaki shiba@NetBSD.org Naoto Shimazaki igy@NetBSD.org Takao Shinohara shin@NetBSD.org Takuya SHIOZAKI tshiozak@NetBSD.org Daniel Sieger dsieger@NetBSD.org Chuck Silvers chs@NetBSD.org Thor Lancelot Simon tls@NetBSD.org Jeff Smith jeffs@NetBSD.org Noriyuki Soda soda@NetBSD.org Wolfgang Solfrank ws@NetBSD.org T K Spindler dogcow@NetBSD.org SOMEYA Yoshihiko someya@NetBSD.org Bill Sommerfeld sommerfeld@NetBSD.org Jorg Sonnenberger joerg@NetBSD.org Ignatios Souvatzis is@NetBSD.org Bill Squier groo@NetBSD.org Jonathan Stone jonathan@NetBSD.org Bill Studenmund wrstuden@NetBSD.org Kevin Sullivan sullivan@NetBSD.org SUNAGAWA Keiki kei@NetBSD.org Kimmo Suominen kim@NetBSD.org Shin Takemura takemura@NetBSD.org TAMURA Kent kent@NetBSD.org Shin'ichiro TAYA taya@NetBSD.org Ian Lance Taylor ian@NetBSD.org Matt Thomas matt@NetBSD.org Jason Thorpe thorpej@NetBSD.org Christoph Toshok toshok@NetBSD.org Greg Troxel gdt@NetBSD.org Tsubai Masanari tsubai@NetBSD.org Izumi Tsutsui tsutsui@NetBSD.org UCHIYAMA Yasushi uch@NetBSD.org Masao Uebayashi uebayasi@NetBSD.org Shuichiro URATA ur@NetBSD.org Valeriy E. Ushakov uwe@NetBSD.org Todd Vierling tv@NetBSD.org Aymeric Vincent aymeric@NetBSD.org Paul Vixie vixie@NetBSD.org Mike M. Volokhov mishka@NetBSD.org Krister Walfridsson kristerw@NetBSD.org Lex Wennmacher wennmach@NetBSD.org Leo Weppelman leo@NetBSD.org Assar Westerlund assar@NetBSD.org Todd Whitesel toddpw@NetBSD.org Frank Wille phx@NetBSD.org Nathan Williams nathanw@NetBSD.org Rob Windsor windsor@NetBSD.org Dan Winship danw@NetBSD.org Arnaud Lacombe alc@NetBSD.org Jim Wise jwise@NetBSD.org Michael Wolfson mbw@NetBSD.org Steve Woodford scw@NetBSD.org Colin Wood ender@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Yuji Yamano yyamano@NetBSD.org Reinoud Zandijk reinoud@NetBSD.org S.P.Zeidler spz@NetBSD.org Maria Zevenhoven maria7@NetBSD.org Christos Zoulas christos@NetBSD.org Other contributors: Dave Burgess burgess@cynjut.infonet.net Brian R. Gaeke brg@dgate.org Brad Grantham grantham@tenon.com Lawrence Kesteloot kesteloo@cs.unc.edu Waldi Ravens waldi@moacs.indiv.nl.net Dedication NetBSD 4.0 is dedicated to the memory of Jun-Ichiro "itojun" Hagino, who died in October 2007. Itojun was a member of the KAME project, which provided IPv6 and IPsec support; he was also a member of the NetBSD core team (the technical management for the project), and one of the Security Officers. Due to Itojun's efforts, NetBSD was the first open source operating system with a production ready IPv6 networking stack, which was included in the base system before many people knew what IPv6 was. We are grateful to have known and worked with Itojun, and we know that he will be missed. This release is therefore dedicated, with thanks, to his memory. Legal Mumbo-Jumbo All product names mentioned herein are trademarks or registered trade- marks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: NetBSD is a registered trademark of The NetBSD Foundation, Inc. This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the NetBSD Foundation. This product includes software developed by The NetBSD Foundation, Inc. and its contributors. This product includes software developed for the NetBSD Project. See http://www.netbsd.org/ for information about NetBSD. This product contains software developed by Ignatios Souvatzis for the NetBSD project. This product contains software written by Ignatios Souvatzis and Michael L. Hitch for the NetBSD project. This product contains software written by Michael L. Hitch for the NetBSD project. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com) This product includes cryptographic software written by Eric Young (eay@mincom.oz.au) This product includes software designed by William Allen Simpson. This product includes software developed at Ludd, University of Lulea, Sweden and its contributors. This product includes software developed at Ludd, University of Lulea. This product includes software developed at the Information Technology Division, US Naval Research Laboratory. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by David Jones and Gordon Ross This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Hellmuth Michaelis and Joerg Wunsch This product includes software developed by Internet Research Institute, Inc. This product includes software developed by Leo Weppelman and Waldi Ravens. This product includes software developed by Mika Kortelainen This product includes software developed by Aaron Brown and Harvard Uni- versity. This product includes software developed by Adam Ciarcinski for the NetBSD project. This product includes software developed by Adam Glass and Charles M. Hannum. This product includes software developed by Adam Glass. This product includes software developed by Advanced Risc Machines Ltd. This product includes software developed by Alex Zepeda, and Colin Wood for the NetBSD Projet. This product includes software developed by Alex Zepeda. This product includes software developed by Alistair G. Crooks. This product includes software developed by Alistair G. Crooks. for the NetBSD project. This product includes software developed by Allen Briggs This product includes software developed by Amancio Hasty and Roger Hardiman This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Bill Paul. This product includes software developed by Bodo Moeller. (If available, substitute umlauted o for oe) This product includes software developed by Boris Popov. This product includes software developed by Brad Pepers This product includes software developed by Bradley A. Grantham. This product includes software developed by Brini. This product includes software developed by Causality Limited. This product includes software developed by Charles D. Cranor and Seth Widoff. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor, Washington University, and the University of California, Berkeley and its contribu- tors. This product includes software developed by Charles D. Cranor, Washington University, the University of California, Berkeley and its contributors. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles M. Hannum. This product includes software developed by Christian E. Hopps, Ezra Story, Kari Mettinen, Markus Wild, Lutz Vieweg and Michael Teske. This product includes software developed by Christian E. Hopps. This product includes software developed by Christian Limpach This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by Chuck Silvers. This product includes software developed by Colin Wood for the NetBSD Project. This product includes software developed by Colin Wood. This product includes software developed by Cybernet Corporation and Nan Yang Computer Services Limited This product includes software developed by Daishi Kato This product includes software developed by Dale Rahn. This product includes software developed by Daniel Widenfalk and Michael L. Hitch. This product includes software developed by Daniel Widenfalk for the NetBSD Project. This product includes software developed by Darrin B. Jewell This product includes software developed by David Miller. This product includes software developed by Dean Huxley. This product includes software developed by Eduardo Horvath. This product includes software developed by Eric S. Hvozda. This product includes software developed by Eric S. Raymond This product includes software developed by Eric Young (eay@@min- com.oz.au) This product includes software developed by Eric Young (eay@crypt- soft.com) This product includes software developed by Eric Young (eay@mincom.oz.au) This product includes software developed by Ezra Story and by Kari Met- tinen. This product includes software developed by Ezra Story, by Kari Mettinen and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, Michael Teske and by Bernd Ernesti. This product includes software developed by Ezra Story, by Kari Mettinen, and Michael Teske. This product includes software developed by Ezra Story. This product includes software developed by Frank van der Linden for the NetBSD Project. This product includes software developed by Gardner Buchanan. This product includes software developed by Gary Thomas. This product includes software developed by Gordon Ross This product includes software developed by Gordon W. Ross This product includes software developed by HAYAKAWA Koichi. This product includes software developed by Harvard University and its contributors. This product includes software developed by Harvard University. This product includes software developed by Herb Peyerl. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hibbert This product includes software developed by Ian F. Darwin and others. This product includes software developed by Ian W. Dall. This product includes software developed by Ichiro FUKUHARA. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Internet Initiative Japan Inc. This product includes software developed by James R. Maynard III. This product includes software developed by Jared D. McNeill. This product includes software developed by Jason L. Wright This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/ This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by Joerg Wunsch This product includes software developed by John Birrell. This product includes software developed by John P. Wittkoski. This product includes software developed by John Polstra. This product includes software developed by Jonathan R. Stone for the NetBSD Project. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Juan Romero Pardines for the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Jukka Marin. This product includes software developed by Julian Highfield. This product includes software developed by Kazuhisa Shimizu. This product includes software developed by Kazuki Sakamoto. This product includes software developed by Kenneth Stailey. This product includes software developed by Kiyoshi Ikehara. This product includes software developed by Klaus Burkert,by Bernd Ernesti, by Michael van Elst, and by the University of California, Berke- ley and its contributors. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Leo Weppelman for the NetBSD Project. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Luke Mewburn. This product includes software developed by Lutz Vieweg. This product includes software developed by MINOURA Makoto, Takuya Harakawa. This product includes software developed by Manuel Bouyer. This product includes software developed by Marc Horowitz. This product includes software developed by Marcus Comstedt. This product includes software developed by Mark Brinicombe for the NetBSD project. This product includes software developed by Mark Brinicombe. This product includes software developed by Mark Murray This product includes software developed by Mark Tinguely and Jim Lowe This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Masanobu Saitoh. This product includes software developed by Masaru Oki. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matt DeBergalis This product includes software developed by Matthew Fredette. This product includes software developed by Matthias Pfaller. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Michael Graff. This product includes software developed by Michael L. Hitch. This product includes software developed by Michael Shalayeff. This product includes software developed by Michael Smith. This product includes software developed by Mike Glover and contributors. This product includes software developed by Mike Pritchard. This product includes software developed by Minoura Makoto. This product includes software developed by Nan Yang Computer Services Limited. This product includes software developed by Niels Provos. This product includes software developed by Niklas Hallqvist, Brandon Creighton and Job de Haas. This product includes software developed by Niklas Hallqvist. This product includes software developed by Onno van der Linden. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Per Fogelstrom This product includes software developed by Peter Galbavy. This product includes software developed by Phase One, Inc. This product includes software developed by Philip A. Nelson. This product includes software developed by Philip L. Budne. This product includes software developed by RiscBSD. This product includes software developed by Roar Thronaes. This product includes software developed by Rodney W. Grimes. This product includes software developed by Roger Hardiman This product includes software developed by Roland C. Dowdeswell. This product includes software developed by Rolf Grossmann. This product includes software developed by Ross Harvey for the NetBSD Project. This product includes software developed by Ross Harvey. This product includes software developed by Scott Bartram. This product includes software developed by Scott Stevens. This product includes software developed by Shingo WATANABE. This product includes software developed by Softweyr LLC, the University of California, Berkeley, and its contributors. This product includes software developed by Soren S. Jorvang. This product includes software developed by Stephan Thesing. This product includes software developed by Steve Woodford. This product includes software developed by Takashi Hamada This product includes software developed by Takumi Nakamura. This product includes software developed by Tatoku Ogaito for the NetBSD Project. This product includes software developed by Terrence R. Lambert. This product includes software developed by Tetsuya Isaki. This product includes software developed by Thomas Gerner This product includes software developed by Thomas Klausner for the NetBSD Project. This product includes software developed by Tobias Weingartner. This product includes software developed by Todd C. Miller. This product includes software developed by Tohru Nishimura and Reinoud Zandijk for the NetBSD Project. This product includes software developed by Tohru Nishimura for the NetBSD Project. This product includes software developed by Tohru Nishimura. for the NetBSD Project. This product includes software developed by TooLs GmbH. This product includes software developed by Toru Nishimura. This product includes software developed by Trimble Navigation, Ltd. This product includes software developed by WIDE Project and its contrib- utors. This product includes software developed by Waldi Ravens. This product includes software developed by Wasabi Systems for Zembu Labs, Inc. http://www.zembu.com/ This product includes software developed by Winning Strategies, Inc. This product includes software developed by Wolfgang Solfrank. This product includes software developed by Yasushi Yamasaki This product includes software developed by Zembu Labs, Inc. This product includes software developed by the Alice Group. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the Charles D. Cranor, Wash- ington University, University of California, Berkeley and its contribu- tors. This product includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by the David Muir Sharnoff. This product includes software developed by the Harvard University and its contributors. This product includes software developed by the Kungliga Tekniska Hogskolan and its contributors. This product includes software developed by the Network Research Group at Lawrence Berkeley Laboratory. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.OpenSSL.org/) This product includes software developed by the PocketBSD project and its contributors. This product includes software developed by the RiscBSD kernel team This product includes software developed by the RiscBSD team. This product includes software developed by the SMCC Technology Develop- ment Group at Sun Microsystems, Inc. This product includes software developed by the University of California, Berkeley and its contributors, as well as the Trustees of Columbia Uni- versity. This product includes software developed by the University of California, Lawrence Berkeley Laboratory and its contributors. This product includes software developed by the University of California, Lawrence Berkeley Laboratory. This product includes software developed by the University of Illinois at Urbana and their contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Labora- tory, and its contributors. This product includes software developed for the FreeBSD project This product includes software developed for the NetBSD Project by Bernd Ernesti. This product includes software developed for the NetBSD Project by Christopher G. Demetriou. This product includes software developed for the NetBSD Project by Chris- tos Zoulas This product includes software developed for the NetBSD Project by Emmanuel Dreyfus. This product includes software developed for the NetBSD Project by Frank van der Linden This product includes software developed for the NetBSD Project by Igna- tios Souvatzis. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Michael L. Hitch. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Scott Bartram and Frank van der Linden This product includes software developed for the NetBSD Project by Alle- gro Networks, Inc., and Wasabi Systems, Inc. This product includes software developed for the NetBSD Project by Genetec Corporation. This product includes software developed for the NetBSD Project by Jonathan Stone. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by SUNET, Swedish University Computer Network. This product includes software developed for the NetBSD Project by Shigeyuki Fukushima. This product includes software developed for the NetBSD Project by Wasabi Systems, Inc. This product includes software developed under OpenBSD by Per Fogelstrom Opsycon AB for RTMX Inc, North Carolina, USA. This product includes software developed under OpenBSD by Per Fogelstrom. This software is a component of "386BSD" developed by William F. Jolitz, TeleMuse. This software was developed by Holger Veit and Brian Moore for use with "386BSD" and similar operating systems. "Similar operating systems" includes mainly non-profit oriented systems for research and education, including but not restricted to "NetBSD", "FreeBSD", "Mach" (by CMU). This software includes software developed by the Computer Systems Labora- tory at the University of Utah. This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/). This product includes software developed by Marshall M. Midden. This product includes software developed or owned by Caldera Interna- tional, Inc. The Institute of Electrical and Electronics Engineers and The Open Group, have given us permission to reprint portions of their documentation. In the following statement, the phrase ``this text'' refers to portions of the system documentation. Portions of this text are reprinted and reproduced in electronic form in NetBSD, from IEEE Std 1003.1, 2004 Edition, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2004 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between these versions and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.open- group.org/unix/online.html. This notice shall appear on any product containing this material This product includes software developed by David Jones. This product includes software developed by Steve C. Woodford. The End NetBSD December 15, 2007 NetBSD