INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/next68k. CONTENTS About this Document............................................2 What is NetBSD?................................................2 Changes Between The NetBSD 3.0 and 4.0 Releases................2 Networking..................................................3 File systems................................................3 Drivers.....................................................4 Platforms...................................................6 Kernel subsystems...........................................7 Security....................................................8 Userland....................................................8 Components removed from NetBSD..............................9 The Future of NetBSD..........................................10 Sources of NetBSD.............................................11 NetBSD 4.0 Release Contents...................................11 NetBSD/next68k subdirectory structure......................12 Binary distribution sets...................................12 NetBSD/next68k System Requirements and Supported Devices......14 Supported hardware.........................................14 Unsupported hardware.......................................14 Getting the NetBSD System on to Useful Media..................15 Preparing your System for NetBSD installation.................15 Get to the ROM Monitor prompt..............................15 Change the configuration parameters to netboot.............15 Installing the NetBSD System..................................16 Post installation steps.......................................19 Upgrading a previously-installed NetBSD System................22 Compatibility Issues With Previous NetBSD Releases............22 Issues affecting an upgrade from NetBSD 2.1 and older......22 Issues affecting an upgrade from NetBSD 3.x releases.......23 Issues with GDB 6.5...........................................24 Using online NetBSD documentation.............................24 Administrivia.................................................24 Thanks go to..................................................25 We are........................................................26 Dedication....................................................31 Legal Mumbo-Jumbo.............................................32 The End.......................................................38 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 4.0 on the next68k 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/next68k subdirectory structure The next68k-specific portion of the NetBSD 4.0 release is found in the next68k subdirectory of the distribution: .../NetBSD-4.0/next68k/. 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. sets/ next68k binary distribution sets; see below. installation/ misc/ Miscellaneous next68k installation utilities; see installation section, below. Binary distribution sets The NetBSD next68k binary distribution sets contain the binaries which comprise the NetBSD 4.0 release for the next68k. The binary distribution sets can be found in the next68k/binary/sets subdirectory of the NetBSD 4.0 distribution tree, and are as follows: base The NetBSD 4.0 next68k 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/next68k 4.0 GENERIC kernel, named /netbsd. You must install this distribution set. 2 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. NetBSD/next68k currently does not ship with an X server or X clients. Binary sets for the X Win- dow 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 next68k binary distribution sets are distributed as gzipped tar files named with the extension .tgz, e.g. base.tgz. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the filenames stored in the sets are relative and therefore the files are extracted below the current directory. Therefore, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar -xpf command from the root directory ( / ) of your system. This utility is used only in a Traditional method installation. Note: Each directory in the next68k binary distribution also has its own checksum files, just as the source distribution does. NetBSD/next68k System Requirements and Supported Devices NetBSD/next68k 4.0 will run on the 25 MHz 68040-based NeXT workstations. The Turbo (33 MHz) models are not supported. The 68030 model is not sup- ported. NetBSD/next68k 4.0 does not have any local disk support, so you must netboot and run diskless. The minimum configuration requires 4 MB of RAM and a network server capa- ble of netbooting NetBSD/next68k. Serial consoles are poorly supported by the hardware, see the FAQ for help. Typically it is just easier to use the NeXT monitor and keyboard. http://www.NetBSD.org/ports/next68k/faq.html Supported hardware o CPUs - 68040-25 2-bit grayscale (NeXTcube) - 68040-25 2-bit grayscale (NeXTstation) - 68040-25 16-bit color (NeXTstation Color) o RS232 interfaces - on-board A and B serial ports (zsc). o Network interfaces: - on-board ethernet (xe). o Displays - on-board NeXT monochrome display (nextdisplay). - on-board NeXT 12-bit color display (nextdisplay). o Input devices - NeXT non-adb keyboard (nextkbd). o Miscellaneous - Battery-backed real-time clock. Unsupported hardware o CPUs - 68030-25 2-bit grayscale (NeXT Computer) - 68040-33 2-bit grayscale (NeXTcube Turbo) - 68040-33 2-bit grayscale (NeXTstation Turbo) - 68040-33 16-bit color (NeXTstation Color Turbo) o Disk interfaces - on-board SCSI interface and disks - Floppy drive - Optical disk - non-SCSI CD-ROM o Miscellaneous devices - NeXTdimension 32-bit color framebuffer - 16-bit digital audio - DSP - NeXT Printer Getting the NetBSD System on to Useful Media Because NetBSD/next68k must run diskless, the distribution must be installed to a remote machine that NFS exports to the NeXT machine. As a result, there is no automated install procedure. Begin by retrieving the NetBSD set files onto the serving machine. These can be found at ftp.NetBSD.org. You may want to keep the following information handy: IP Address: ftp.NetBSD.org Login: anonymous Password: your e-mail address Server path: /pub/NetBSD/NetBSD-4.0/next68k/binary/sets Preparing your System for NetBSD installation Get to the ROM Monitor prompt After the system performs its power-on self test, and while it tries to boot an operating system, press the COMMAND-` keys (the backquote is above 7 on the keypad on the right of the keyboard). You should see a prompt like this: NeXT ROM Monitor 2.5 (v66) CPU MC68040 25 MHz, memory 100 nS Backplane slot #0 Ethernet address: 0:0:f:0:fb:90 Memory size 40 MB NeXT Write down the ethernet address. You will need this later to configure the netboot server for your NetBSD/next68k system. Change the configuration parameters to netboot Press the p key to modify the configuration parameters. You will need to change the boot command to en()netbsd which is to boot from the en() eth- ernet device the kernel named netbsd. You should wite down what the original boot command was in case you wish to boot NEXTSTEP in the future. It will probably be sd(). While modifying the parameters, you may wish to set the system to use verbose test mode which will print detailed messages while it is attempting to load the kernel, as opposed to the normal graphic of a network cable. You should not set the extended diagnostics as the system will try to boot a diagnostic kernel. Here is an example configuration session: NeXT p boot command: sd()? en()netbsd DRAM tests: yes? yes perform power-on system test: yes? yes sound out tests: yes? yes SCSI tests: yes? yes loop until keypress: no? no verbose test mode: no? yes boot extended diagnostics: no? no serial port A is alternate console: no? yes allow any ROM command even if password protected: no? no allow boot from any device even if password protected: no? no allow optical drive #0 eject even if password protected: yes? yes enable parity checking if parity memory is present: no? no Now, whenever you reset or power on your system, it will attempt to net- boot. From the ROM Monitor prompt, you can simply type b to netboot. You can also press the power key (above the arrows) to turn off the sys- tem. Installing the NetBSD System 1. Introduction To netboot a next68k, you must configure one or more servers to pro- vide information and files to your next68k (the `client'). If you are using NetBSD (any architecture) on your netboot server(s), the information provided here should be sufficient to configure every- thing. Additionally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configuring. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps neces- sary to configure the netboot services on a variety of platforms. http://www.NetBSD.org/docs/network/netboot/ Briefly, the netboot process involves discovery, bootstrap, kernel and file system stages. In the first stage, the client discovers information about where to find the bootstrap program. Next, it downloads and executes the bootstrap program. The bootstrap program goes through another discovery phase to determine where the kernel is located. The bootstrap program tries to mount the NFS share con- taining the kernel. Once the kernel is loaded, it starts executing. The kernel tries to mount the NFS share that had the kernel and starts executing init(8). All next68k systems use BOOTP for the discovery stage. TFTP is used in the bootstrap phase to download the bootstrap program, boot. NFS is used in both the kernel and file system stages to download the kernel, and to access files on the file server. We will use `CC:CC:CC:CC:CC:CC' as the MAC address (ethernet hard- ware address) of your netboot client machine. You should have determined this address in an earlier stage. In this example, we will use `192.168.1.10' as the IP address of your client and `client.test.net' as its name. We will assume you're providing all of your netboot services on one machine called `server.test.net' with the client's files exported from the directory /export/client/root. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environ- ment. You should set up each netboot stage in order (i.e. discovery, boot- strap, kernel, and then file system) so that you can test them as you proceed. 2. dhcpd(8) in bootpd(8) compatible mode Put the following lines in your /etc/dhcpd.conf (see dhcpd.conf(5) and dhcp-options(5) for more information): ddns-update-style none; # Do not use any dynamic DNS features # allow bootp; # Allow bootp requests, thus the dhcp server # will act as a bootp server. # authoritative; # master DHCP server for this subnet # subnet 192.168.1.0 netmask 255.255.255.0 { # Which network interface to listen on. # The zeros indicate the range of addresses # that are allowed to connect. } group { # Set of parameters common to all clients # in this "group". # option broadcast-address 192.168.1.255; option domain-name "test.net"; option domain-name-servers dns.test.net; option routers router.test.net; option subnet-mask 255.255.255.0; # # An individual client. # host client.test.net { hardware ethernet CC:CC:CC:CC:CC:CC; fixed-address 192.168.1.10; # # Name of the host (if the fixed address # doesn't resolve to a simple name). # option host-name "client"; # # Name of the bootloader or kernel # to download via tftp. # filename "boot"; # # The path on the NFS server. # option root-path "/export/client/root"; # #next68k machines require non-RFC1048 BOOTP # always-reply-rfc1048 false; # # If your DHCP server is not your NFS server, supply the # address of the NFS server. Since we assume you run everything # on one server, this is not needed. # # next-server server.test.net; } #you may paste another "host" entry here for additional #clients on this network } You will need to make sure that the dhcpd.leases file exists. # touch /var/db/dhcpd.leases You will need to start the dhcpd. If it's already running, you will need to restart it to force it to re-read its configuration file. If the server is running NetBSD, you can achieve this with: # /etc/rc.d/dhcpd restart 3. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) environment in the /tftpboot directory. Thus, the first order of business is to create this directory: # mkdir -p /tftpboot Next, edit /etc/inetd.conf and uncomment the line with the TFTP dae- mon: tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot Now, restart inetd(8). If the server is running NetBSD, you can achieve this with: # /etc/rc.d/inetd restart Now, you need to copy the bootloader for your next68k machine to /tftpboot. Get boot from the installation directory of the distri- bution. # cp boot /tftpboot Just to be sure, let's make everything readable. # chmod -R a+rX /tftpboot Sometimes, the arp(8) table gets messed up, and the TFTP server can't communicate with the client. In this case, it will write a log message (via syslogd(8)) to /var/log/messages saying: `tftpd: write: Host is down'. If this is the case, you may need to force the server to map your client's ethernet address to its IP address: # arp -s client CC:CC:CC:CC:CC:CC 4. nfsd(8), mountd(8), and rpcbind(8) Now your system should be able to load the bootstrap program and start looking for the kernel. Let's set up the NFS server. Create the directory you are exporting for the netboot client: # mkdir -p /export/client/root Put the following line in /etc/exports to enable NFS sharing: /export/client/root -maproot=root client.test.net If your server is currently running an NFS server, you only need to restart mountd(8). Otherwise, you need to start rpcbind(8) and nfsd(8). If the server is running NetBSD, you can achieve this with: # /etc/rc.d/rpcbind start # /etc/rc.d/nfsd start # /etc/rc.d/mountd restart 5. NetBSD kernel Now, if you place a kernel named netbsd in /export/client/root your client should boot the kernel. Use binary/kernel/netbsd-GENERIC.gz. # gunzip netbsd-GENERIC.gz # mv netbsd-GENERIC /export/client/root/netbsd 6. Client file system You need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better security and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/docs/network/netboot/nfs.html o Extracting distribution sets # cd /export/client/root # tar -xpzf /path/to/files/base.tgz # tar -xpzf /path/to/files/etc.tgz Continue with the other non-essential distribution sets if desired. o Set up swap # mkdir /export/client/root/swap # dd if=/dev/zero of=/export/client/swap bs=4k count=4k # echo '/export/client/swap -maproot=root:wheel client.test.net' | cat >> /etc/exports # /etc/rc.d/mountd restart This creates a 16 MB swap file and exports it to the client. o Create device nodes # cd /export/client/root/dev # ./MAKEDEV all This procedure only works on NetBSD hosts. o Set up the client's fstab(5) Create a file in /export/client/root/etc/fstab with the follow- ing lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 o Set up the client's rc.conf(5) Edit /export/client/root/etc/rc.conf rc_configured=YES hostname="client" defaultroute="192.168.1.1" nfs_client=YES auto_ifconfig=NO net_interfaces="" Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system. o Set up the client's hosts(5) file. Edit /export/client/root/etc/hosts ::1 localhost 127.0.0.1 localhost 192.168.1.10 client.test.net client 192.168.1.5 server.test.net server 7. Setting up the server daemons You need these services to start up every time you boot your server, make sure the following lines are present in your /etc/rc.conf: dhcpd=YES dhcpd_flags="-q" nfs_server=YES # enable server daemons mountd=YES rpcbind=YES rpcbind_flags="-l" # -l logs libwrap Also, you'll need to make sure the tftpd line in /etc/inetd.conf remains uncommented. 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_xe0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_xe0="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. 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. 4. 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/next68k/All subdir. You can install them with the following commands under sh(1): # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/4.0/next68k/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/next68k/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. 5. 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 NetBSD/next68k does not currently support an upgrade procedure. 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 Darrin B. Jewell. This product includes software developed by Matt DeBergalis. The End NetBSD December 15, 2007 NetBSD