INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL - Installation procedure for NetBSD/x68k DESCRIPTION About this Document This document describes the installation procedure for NetBSD 1.4.2 on the x68k 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 UN*X-like operating system derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on twenty different system architectures featuring eight distinct families of CPUs, and is being ported to more. The NetBSD 1.4.2 release contains complete binary releases for fifteen different machine types. (The remaining ones are not fully supported at this time and are thus not part of the binary distri- bution. For information on them, please see the NetBSD web site at http://www.netbsd.org/) NetBSD is a completely integrated system. In addition to its highly portable, high performance kernel, NetBSD features a complete set of user utilities, compilers for several languages, The X Window System, and nu- merous 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. Upgrade path to NetBSD 1.4.2 If you are not installing your system ``from scratch'' but instead are going to upgrade an existing system already running NetBSD you need to know which versions you can upgrade with NetBSD 1.4.2. NetBSD 1.4.2 is an upgrade of NetBSD 1.4.1, NetBSD 1.4 and earlier re- leases of NetBSD such as versions 1.3.3, 1.2 etc. The intermediate development versions of code available on the main trunk in our CVS repository (also known as ``NetBSD-current'') from after the point where the release cycle for 1.4 was started are designated by ver- sion identifiers such as 1.4A, 1.4B, 1.4P etc. These identifiers do not designate releases, but indicate major changes in internal kernel APIs. Note that the kernel from NetBSD 1.4.2 can not be used to upgrade a sys- tem running one of those intermediate development versions. Trying to use the NetBSD 1.4.2 kernel on such a system will in all probability re- sult in problems. Please also note that it is not possible to do a direct ``version'' com- parison between any of the intermediate development versions mentioned above and 1.4.2 to determine if a given feature is present or absent in 1.4.2. The development of 1.4, 1.4.1 and 1.4.2 is done on a separate branch in the CVS repository which was created when the release cylcle for 1.4 was started, and during the release cycles for all these versions selective fixes (with minor impact on the stability of the code on the release branch) have been imported from the main development trunk. So, there are features in 1.4.2 which were not in e.g. 1.4H, but the reverse is also true. Major Changes Between 1.4.1 and 1.4.2 The complete list of changes between NetBSD 1.4.1 and 1.4.2 can be found in the file CHANGES-1.4.2 in the top directory of the source tree. The following are the highlights only. o A driver for the Alteon Gigabit Ethernet cards has been added, see ti(4). o A driver for the Realtek 8129/8239 Fast Ethernet PCI cards have been added, see rl(4). o A driver for the DPT SmartCache and SmartRAID III or IV SCSI adapters has been added, see dpt(4). o A driver for the BOCA IOAT66 6-port ISA serial adapter has been added, see ioat(4). o Support for the X-surf Amiga board has been added. o Support has been added for ext2fs revision 1, with read-only support for the ``sparse super'' and the ``filetype'' options. o BIND has been upgraded to version 8.2.2-P5. o The IPF packet filtering software has been updated to version 3.3.5. o Tcpdump now does hex/ascii dumps of packet contents if asked to do so. o An implementation of the System V user management utilities has been added. o The name ``errno'' is now always a macro which expands to a function call. This is done to ease the integration of thread libraries with the code in both system and third-party libraries. Please include to access the correct definition of ``errno''. o A utility for making temporary files for shell scripts has been added, see mktemp(1). o The automounter utility amd(8) has been updated to fix a security problem. o A security problem in procfs has been fixed. Procfs is not used by default in NetBSD. o The floating point emulation on the ports using the m68k CPU has been reverted to the version in NetBSD 1.4 (the version in 1.4.1 had prob- lems). o Several subsystems have received substantial work, such as RAIDframe, LFS, and the package tools. In addition, many, many bugs have been fixed -- more than 100 problems reported through our problem tracking system have been fixed, and many other non-reported problems have also been found and fixed. See the CHANGES-1.4.2 file for the complete list. Known caveats with 1.4.2 The following are the major known issues with NetBSD 1.4.2. o The upgrade of ipf(8) caused a change of the kernel API. Thus, if you are using ipf(8) you need to upgrade both the kernel and the us- er-land utilities to control that feature in order for it to work. o As part of fixing a kernel bug, ``struct vfsnode'' needed to change size. This will unfortunately, and contrary to tradition for patch releases, cause incompatibilities for users of file system LKMs com- piled for 1.4 and 1.4.1. o Although LFS has been improved between 1.4.1 and 1.4.2, it can proba- bly still be characterized as being of ``beta test'' quality, e.g. filling the file system still gives ``interesting'' effects. It should probably not be used to store critical data quite yet. o The version of the IPF packet filtering software in NetBSD 1.4.2 must be enabled with ``ipf -E'' before filtering or NAT rules can be set. Failure to do so may result in a panic. Major Changes Between 1.4 and 1.4.1 The complete list of changes between NetBSD 1.4 and 1.4.1 can be found in the file CHANGES-1.4.1 in the top directory of the source tree. o The NetBSD/alpha port's compatibility for Digital UNIX executables has been greatly improved. o Many bug fixes and improvements of the installation tools and utili- ties. o Support for more PCI serial/parallel cards has been added. o It is now possible to boot NetBSD/i386 on systems with 1GB of RAM. o The floating point emulation on the ports using the m68k CPU has been upgraded. o A fatal problem with /dev/random has been found and fixed. o Support for Alpha 21264 ev6 based systems has been added to NetB- SD/alpha. Major Changes Between 1.3 and 1.4 The NetBSD 1.4 release is a substantial improvement over its predeces- sors. We have provided numerous significant functional enhancements, in- cluding support for many new devices, integration of hundreds of bug fix- es, new and updated kernel subsystems, and many userland enhancements. The results of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to completely summarize the nearly two years of develop- ment that went into the NetBSD 1.4 release. Some highlights include: o Substantial improvements in the TCP/IP implementation, including nu- merous performance enhancements and bug fixes by Jason Thorpe and others. o A new, high efficiency kernel memory pool allocator by Paul Kranen- burg. This has been integrated into most kernel subsystems. o A new, totally rewritten virtual memory subsystem, UVM, created by Chuck Cranor, which is substantially cleaner and better performing than the old Mach derived VM subsystem. o Improved POSIX and XPG standards compliance. o Completion of the integration of all remaining 4.4BSD Lite-2 kernel improvements and bug fixes that had not been previously integrated. (Integration of all userland components was completed before NetBSD 1.3) o Several new ports, including macppc, bebox, sparc64, next68k, and others, have been integrated into the source tree. o The system compilers have been upgraded to egcs 1.1.1, and the system compiler toolchain now (mostly) uses the latest versions of GNU binu- tils instead of the obsolete versions left over from 4.4BSD Lite. o Everyone's favorite ftp(1) client has been improved even further. See the man page for details. o A new architecture independent console driver, wscons(4), has been integrated into many ports. o Numerous improvements have been made to the audio subsystem support, including support for MIDI device drivers. o Linux compatibility support has been improved. o A number of scheduler enhancements have yielded dramatic improvements in interactive performance and better control of background tasks. o Several network tunneling protocols, including GRE and IP in IP, have been implemented. o Kernel support for the CODA distributed file system has been added. o Manuel Bouyer completed major changes to the IDE support. It is now architecture independent. Major changes have been made to the IDE code for better error handling, improved ATAPI support, 32 bit data I/O support and bus-master DMA support on PCI IDE controllers. o Lennart Augustsson has added full USB support, permitting the use of a wide variety of Universal Serial Bus peripherals. The drivers should easily port to any future platforms that support the PCI bus. See usb(4) for an overview. o RAIDframe, version 1.1, from the Parallel Data Laboratory at Carnegie Mellon University, has been integrated. Supports RAID levels 0, 1, 4, 5, and more. o Luke Mewburn added nsswitch.conf(5) functionality to the system to specify the search order for system databases. o syslogd(8) now supports listening on multiple sockets, to make the chrooting of servers easier. o Most third party packages have been updated to the latest stable re- lease. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.4.2 is the third public major release of NetBSD for the x68k platform. In addition to above port-independent improvements, many device drivers are reorganized, and some of them now utilize the machine-independent backend. Also the boot program is improved to load the kernel from any hard drives. 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 ac- tivities. o periodically organizing workshops for developers and other interested people to discuss ongoing work. We intend to begin narrowing the time delay between releases. Our ambi- tion is to provide a full release every six to eight months. We hope to support even 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. In addition, Anonymous CVS access to the NetBSD source tree has been added since NetBSD 1.4.1; see http://www.netbsd.org/Changes/#anoncvs-available We have also added a browsable CVS repository on the web at http://cvsweb.netbsd.org/cgi-bin/cvsweb.cgi/ We intend to integrate free, positive changes from whatever sources sub- mit them, providing that they are well thought-out and increase the us- ability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD Please refer to http://www.netbsd.org/Sites/net.html. NetBSD 1.4.2 Release Contents The root directory of the NetBSD 1.4.2 release is organized as follows: .../NetBSD-1.4.2/ BUGS Known bugs list (somewhat incomplete and out of date). CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.4.2 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 di- rectory per architecture, for each of the architectures for which NetBSD 1.4.2 has a binary distribution. There are also 'README.export- control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The NetBSD project maintains a web page at http://www.NetBSD.ORG/Misc/crypto-export.html which should contain up-to-date information on this issue. 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: secrsrc.tgz: This set contains the "domestic" sources. These sources may be subject to United States export regulations. 421K gzipped, 2M uncompressed gnusrc.tgz: This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. 19M gzipped, 84.3M uncompressed syssrc.tgz: This set contains the sources to the NetBSD 1.4.2 ker- nel, config(8), and dbsym(8). 13.9M gzipped, 68.3M uncompressed sharesrc.tgz: This set contains the "share" sources, which include the sources for the man pages not associated with any par- ticular program, the sources for the typesettable docu- ment set, the dictionaries, and more. 3M gzipped, 11.9M uncompressed src.tgz: This set contains all of the NetBSD 1.4.2 sources which are not mentioned above. 14.4M gzipped, 67.4M uncompressed Most of the above source sets are located in the source/sets subdirectory of the distribution tree. The secrsrc.tgz set is contained in the source/security subdirectory. This set, which may only be available to users in the United States and Canada, contains the sources normally found in /usr/src/domestic - primarily Kerberos and other cryptographic security related software. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the Unit- ed States and Canada. Again, see http://www.NetBSD.ORG/Misc/crypto-export.html for updated information on this issue.) The source sets are distributed as compressed tar files. They may be un- packed into /usr/src with the command: cat set_name.tgz | gunzip | (cd /; tar xpf - ) The sets/Split/ and security/Split/ subdirectories contain split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are are named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) The split distributions may be reassembled and extracted with cat as follows: cat set_name.?? | gunzip | (cd /; tar xpf - ) In each of the source distribution set directories, there is a file named CKSUMS which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the in- tegrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. Checksums based on other algorithms may also be present - see the release(7) man page for details. NetBSD/x68k Subdirectory Structure The x68k-specific portion of the NetBSD 1.4.2 release is found in the x68k subdirectory of the distribution: .../NetBSD-1.4.2/x68k/ INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes; this file. The .more file contains underlined text using the more(1) conventions for indicat- ing italic and bold display. binary/ sets/ x68k binary distribution sets; see below. security/ x68k security distribution; see below. installation/ floppy/ x68k boot and installation floppies; see below. misc/ Miscellaneous x68k installation utilities which run on Human68k; see installation section, below. Binary Distribution Sets The NetBSD x68k binary distribution sets contain the binaries which com- prise the NetBSD 1.4.2 release for the x68k. There are eight binary dis- tribution sets and the security distribution set. The binary distribu- tion sets can be found in the x68k/binary/sets subdirectory of the NetBSD 1.4.2 distribution tree, and are as follows: base The NetBSD 1.4.2 x68k base binary distribution. You must in- stall this distribution set. It contains the base NetBSD utilities that are necessary for the system to run and be minimally functional. It includes shared library support, and excludes everything described below. 10.2M gzipped, 28.8M 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. 8.1M gzipped, 27.3M 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. (If you are upgrading, it's recommended that you get a copy of this set and carefully upgrade your configuration files by hand.) 57K gzipped, 340K uncompressed games This set includes the games and their manual pages. 2.8M gzipped, 7M uncompressed kern This set contains a NetBSD/x68k 1.4.2 GENERIC kernel, named /netbsd. You must install this distribution set. 627k gzipped, 1.4M 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. 4M gzipped, 15.9M uncompressed misc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share. 2.2M gzipped, 8.4M uncompressed text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. 1.3M gzipped, 4.5M uncompressed The x68k security distribution set is named secr and can be found in the x68k/binary/security subdirectory of the NetBSD 1.4.2 distribution tree. It contains security- related binaries which depend on cryptographic source code. You do not need this distribution set to use encrypted passwords in your password file; the base distribution includes a crypt library which can perform only the one-way encryption function. The security distribution includes a version of the Kerberos IV network security system, and a Kerberized version of telnet(1) program. The secr distribution set can be found only on those sites which carry the complete NetBSD distribution and which can legally obtain it. Because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada. See http://www.NetBSD.ORG/Misc/crypto-export.html for updated information on this issue. NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 3.3.6. Binary sets for the X Window system are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. 2.4M gzippeed, 7.7M uncompressed xcomp The extra libraries and include files needed to compile X source code. 1.6M gzipped, 6.8M uncompressed xcontrib Programs that were contributed to X. 179k gzipped, 670k uncompressed xfont Fonts needed by X. 5.7M gzipped, 7.0M uncompressed xserver The X68k and Xprt servers with man pages and the runtime configuration file. 1.4M gzipped, 3.4M uncompressed The x68k 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 files are /-relative and therefore are extracted below the current directory. That is, if you want to extract the binaries into your system, i.e. replace the system binaries with them, you have to run the tar xfp command from /. Note Each directory in the x68k binary distribution also has its own checksum files, just as the source distribution does: All BSDSUM files are historic BSD checksums for the various files in that directory, in the format produced by the command: cksum -o 1 file All CKSUM files are POSIX checksums for the various files in that directory, in the format produced by the command: cksum file. All MD5 files are MD5 digests for the various files in that direc- tory, in the format produced by the command: cksum -m file. All SYSVSUM files are historic AT&T System V UNIX checksums for the various files in that directory, in the format produced by the command: cksum -o -2 file. The MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest possible range of system can check the integrity of the release files. NetBSD/x68k System Requirements and Supported Devices NetBSD/x68k 1.4.2 runs on the Sharp X68030 series PCs with a true MC68030 MPU (not the original MC68EC030). Since the processor of the X68030 se- ries is the MC68EC030, you need to replace it with an MC68030. Simply re- move the old chip and put in the new one instead. The largest difficulty might be to open your X68030. In addition, some accelerators are supported: o Xellent30 series o 040turbo o Jupiter-X (040 / 060) o 060turbo This means all models of X680x0 series PC except for CZ-600C and CZ-674C, by using the appropriate accelerator, can run NetBSD!! Note that the processor for the Xellent30 series is MC68EC030, so you need to replace your processor as well as for X68030. For 68030 systems, installing MC68881 or MC68882 FPCP is highly recom- mended but not required. The minimal configuration requires 4M of RAM and about 100M of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. Here is a table of recommended HD partition sizes for a full install: Partition Advised With X Needed With X root (/) 25M 25M 20M 20M user (/usr) 150M 200M 100M 125M swap 2*RAM... local (/local) up to you... As you may note the recommended size of /usr is 70M greater than needed. This is to leave room for a kernel source and compile tree as you will probably want to compile your own kernel. (ALL is large and bulky to ac- commodate all people). Supported devices include: o Sharp genuine SCSI interface (builtin / optional) * SCSI hard- disks, CD-ROM drives, tape drives, scanners,... o Mankai Seisakusho Mach-2 SCSI interface o The builtin floppy drives o The builtin frame buffer (both of the text and graphics screen) o The builtin serial (RS-232C) o The builtin parallel (Centronics printer interface) o The standard keyboard o The mouse / trackball o NS16550 serial o Neptune-X ethernet Hopefully, the AD-PCM sound device will be supported on the future re- leases. Getting the NetBSD System on to Useful Media Installation is supported from several media types, including: o Removable SCSI hard disk, or Magneto-Optical disk (MO) o Tape o Remote NFS partition o FTP You'll need to have a install floppy disk. On the first, you'll put the install floppy image. If you are using a UN*X-like system to write the floppy images to disks, you should use the dd command to copy the file system images (.fs files) directly to the raw floppy disks. It is suggested that you read the dd(1) manual page or ask your system administrator to determine the correct set of arguments to use; it will be slightly different from system to system, and a comprehensive list of the possibilities is beyond the scope of this document. If you are using Human68k to write the floppy images to disks, you should use the rawrite utility, provided in the installation/misc directory of the NetBSD distribution. It will write the file system images (.fs files) to disks. If you can retrieve loadbsd.x utility and netbsd.INSTALL file which can be found in installation/misc directory into your Human68k disk, you can run installation kernel without preparing the special boot floppy. Sim- ply type: loadbsd netbsd.INSTALL from the Human68k command line, then NetBSD will start the installation sequence. Obviously, the steps necessary to prepare the distribution sets for in- stallation or upgrade depend on which installation medium you choose. The steps for the various media are outlined below. Install From Removable SCSI Hard Disk or MO To install NetBSD from a removable device the media must be of the IBM Super-floppy format. The Human68k format is not recog- nized by this release of the NetBSD/x68k. If you have a MS-DOS (or MS-Windows) machine with an MO drive connected, use it. If you don't, and if you have a program to handle IBM format MO for Human68k, copy all the files in the subdirectory x68k/binaries and CHANGE THEIR NAMES IN UPPER CASE. Install From Tape To install or upgrade NetBSD using a tape, you need to do the following: To install NetBSD from a tape, you need to make a tape that con- tains the distribution set files, in "tar" format. If you're mak- ing the tape on a UN*X-like system, the easiest way to do so is probably something like: tar cf tape_device dist_directories where tape_device is the name of the tape device that describes the tape drive you're using (possibly /dev/rst0, or something similar, but it will vary from system to system. (If you can't figure it out, ask your system administrator.) In the above ex- ample, dist_directories are the distribution sets' directories, for the distribution sets you wish to place on the tape. For in- stance, to put the base and etc distributions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: cd .../NetBSD-1.4.2 # the top of the tree cd x68k/binary/sets tar cf tape_device base.tgz etc.tgz (Note that you still need to fill in tape_device in the example.) Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go di- rectly to the section on upgrading. Install From Remote NFS Partition To install or upgrade NetBSD using a remote partition, mounted via NFS, you must do the following: Note This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Place the NetBSD distribution sets you wish to install into a di- rectory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the /etc/exports file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the the numeric IP address of the NFS server, and, if the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetB- SD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once the NFS server is set up properly and you have the informa- tion mentioned above, you can proceed to the next step in the in- stallation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the section on upgrading. Install via FTP To install or upgrade NetBSD by using FTP to get the installation sets, you must do the following: Note This method of installation is recommended only for those already familiar with using BSD network configuration and management commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this installation/upgrade method are easy; all you make sure that there's some FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. You need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD ma- chine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once you have this information, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go di- rectly to the section on upgrading. If you are upgrading NetBSD, you also have the option of installing NetB- SD by putting the new distribution sets somewhere in your existing file system, and using them from there. To do that, you must do the following: 1. Place the distribution sets you wish to upgrade somewhere in your current file system tree. At a bare minimum, you must upgrade the "base" binary distribution, and so must put the "base.tgz" set some- where in your file system. If you wish, you can do the other sets, as well, but you should NOT upgrade the "etc" distribution; the "etc" distribution contains system configuration files that you should review and update by hand. 2. Once you have done this, you can proceed to the next step in the up- grade process, actually upgrading your system. Preparing your System for NetBSD Installation Note Currently NetBSD/x68k requires a dedicated disk when you install it for the first time. In other words NetBSD/x68k cannot be in- stalled on the hard disk on which Human68k or any other operating systems reside. This is because of the poor installer, and the system itself can share a single disk with other OSs. This prob- lem should be fixed in the next release. What you have to do to prepare the disk is only to physically format your hard disk by using FORMAT.x utility of Human68k to install the master boot program on your disk. You can now proceed with the installation in- structions. Installing the NetBSD System Installing NetBSD is a relatively complex process, but if you have this document in hand and are careful to read and remember the information which is presented to you by the install program, it shouldn't be too much trouble. Before you begin, you should know the geometry of your hard disk, i.e. the sector size (note that sector sizes other than 512 bytes are not cur- rently supported), the number of sectors per track, the number of tracks per cylinder (also known as the number of heads), and the number of cylinders on the disk. The NetBSD kernel will try to discover these pa- rameters on its own, and if it can it will print them at boot time. If possible, you should use the parameters it prints. (You might not be able to because you're sharing your disk with another operating system, or because your disk is old enough that the kernel can't figure out its geometry.) You should now be ready to install NetBSD. It might be handy for you to have a pencil, some paper, and a calculator handy. The following is a walk-through of the steps you will take while getting NetBSD installed on your hard disk. If any question has a default answer, it will be displayed in brackets ("[]") after the question. If you wish to stop the installation, you may hit Control-C at any time, but if you do, you'll have to begin the installation process again from scratch. 1. Boot your machine using of boot floppy. If the boot prompt does not appear in a reasonable amount of time, you either have a bad boot floppy or a hardware problem. Try writing the boot floppy image to a different disk, and using that. If it still doesn't work, NetBSD probably can't be run on your hardware. This can probably be consid- ered a bug, so you might want to report it. If you do, please in- clude as many details about your system configuration as you can. It will take a while to load the kernel from the floppy, probably around a minute or so. 2. You will then be presented with the NetBSD kernel boot messages. You will want to read them, to determine your disk's name and geometry. Its name will be something like "sd0" and the geometry will be printed on a line that begins with its name. As mentioned above, you will need your disk's geometry when creating NetBSD's partitions. You will also need to know the name, to tell the install tools what disk to install on. 3. You will be presented with a welcome message and a prompt asking whether you are going to "install" NetBSD or "upgrade" an exisiting system. Select "install" to start installation. 4. You will be presented a prompt asking if you wish to proceed with the installation process. If you wish to proceed, enter "y" and hit return. 5. The install program will then tell you which disks it can install on, and ask you which it should use. Reply with the name of your disk. 6. You will then be asked to name your disk's disklabel. The default response is "mysd", and for most purposes it will be OK. If you choose to name it something different, make sure the name is a sin- gle word and contains no special characters. You don't need to re- member this name. 7. You will be prompted for your disk's geometry information, i.e. the number of bytes per sector, cylinders on the disk, tracks per cylin- der (heads), and sectors per track. Enter them when they are re- quested. If you make a mistake, hit Control-C and when you get to the shell prompt, restart the install process by running the "in- stall" command. Once you have entered this data, the install program will tell you the total size of your disk, in both sectors, and cylinders. Remember this number; if you're installing on the whole disk, you'll need it again soon. 8. When describing your partitions, you will have the option of enter- ing data about them in units of disk sectors or cylinders. If you choose to enter the information in units of sectors, remember that, for optimal performance, partitions should begin and end on cylinder boundaries. You will be asked about which units you wish to use, and you should reply with "c" for cylinders, or "s" for sectors. 9. You will be asked to enter the size of your NetBSD root partition. It should be at least 20M, but if you are going to be doing develop- ment, 25M is a more desirable size. This size should be expressed in units of sectors or cylinders, depending on which you said you want- ed to use. 10. Next, you will be asked for the size of your swap partition. You should probably allocate twice as much swap space as you have real memory. Systems that will be heavily used should have more swap space allocated, and systems that will be lightly used can get by with less. If you want the system to be able to save crash dumps when it panics, you will need at least as much swap space as you have RAM. Again, this number should be expressed in units of sectors or cylinders, as appropriate. 11. The install program will then ask you for information about the rest of the partitions you want on your disk. For most purposes, you will want only one more partition, "/usr". (Machines used as servers will probably also want /var as a separate partition. That can be done with these installation tools, but is not covered here.) The install program will tell you how much space there is left to be al- located in the NetBSD area of the disk, and, if you only want one more partition ("/usr"), you should enter it at the prompt when the installer asks you how large the next partition should be. It will then ask you for the name of the mount point for that partition. If you're doing a basic installation, that is "/usr". 12. 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, and its contents may be scrambled at the whim of the install program. This is especially likely if you have given the install program incorrect information. If you are sure you want to proceed, enter "yes" at the prompt. 13. The install program will now label your disk and make the file sys- tems you specified. The filesystems will be initialized to contain NetBSD bootstrapping binaries and configuration files. It will also create an /etc/fstab for your system, and mount all of the file sys- tems under /mnt. (In other words, your root partition will be mount- ed on /mnt, your /usr partition on /mnt/usr, and so on.) There should be no errors in this section of the installation. If there are, restart from the beginning of the installation process. 14. You will be placed at a shell prompt ("#"). The remaining tasks are to copy the kernel from the kernel copy floppy to the hard drive's root filesystem and install the distribution sets. The flow of in- stallation differs depending on your hardware resources, and on what media the distribution sets reside. To install from removable hard disk The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the com- mand "Set_tmp_dir", and enter the name of the temporary directo- ry. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. Insert the media onto the drive. Check the device name of your drive from the boot message. The device name is something like "sd2" depending on the SCSI disk drives connected to your ma- chine. Note that the boot message can be displayed with the com- mand more /kern/msgbuf. Mount the disk on the temporary directory with a command like: mount -t msdos /dev/sd2c tmp_dir if your removable drive's name is sd2. Run the Extract command once for each distribution set you wish to install. For instance, if you wish to install the base distri- bution set, followed by the kern distribution set, and finally the etc distribution set, use the commands: Extract base Extract kern Extract etc For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted. To install from floppy The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the com- mand Set_tmp_dir, and enter the name of the temporary directory. (Don't forget that if your disk is still mounted under /mnt; you should probably pick a directory under /mnt/usr.) After you have picked a temporary directory, enter the Load_fd command, to load the distribution sets from your floppies. You will be asked which floppy drive to use. Enter "0" (zero) if you're using the first floppy drive (i.e. what DOS would call "A:"), or enter "1" if you're using the second. You will be prompted to insert a floppy into the drive, to have its contents copied to your hard disk. Do so, and hit return to begin copying. When that is done, read the remainder of the flop- pies that contain the distribution sets that you want to install, one by one. When the last is read, and you are being prompted for another, hit Control-C. Run the "Extract" command once for each distribution set you wish to install. For instance, if you wish to install the "base" dis- tribution set, followed by the "kern" distribution set, and fi- nally the "etc" distribution set, use the commands: Extract base Extract kern Extract etc For each extraction, it will ask you if the extraction should be verbose. If you reply affirmatively, it will print out the name of each file that's being extracted. Note If you know that you will be running low on disk space when installing NetBSD, you can load and extract one dis- tribution set at a time. To do this, load only the flop- pies which contain the files for the first distribution set, extract them, and then change to the temporary direc- tory and remove them with the command "rm set_name.??". Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install from tape The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the com- mand "Set_tmp_dir", and enter the name of the temporary directo- ry. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. After you have picked a temporary directory, enter the "Load_tape" command, to load the distribution sets from tape. You will be asked which tape drive to use. The default is "rst0", which is correct if you're using the SCSI tape drive with the lowest SCSI ID number. (For the SCSI tape drive with the next lowest SCSI ID number, you should use "rst1", and so on.) You will be prompted to hit return when you have inserted the tape into the tape drive. When you do, the contents of the tape will be extracted into the temporary directory, and the names of the files being extracted will be printed. After the tape has been extracted, to go the directory containing the first distribution set you wish to install. (Depending on how you made the tape, it's probably a subdirectory of the temporary directory you specified above.) Once there, run the "Set_tmp_dir" command again, and accept its default answer by hitting return at the prompt. Use the Extract command to extract the distribution set. For in- stance, if you're extracting the "base" set, use the command: Extract base You will be asked if you wish the extraction to be verbose. If you reply affirmatively, the name of each file being extracted will be printed. Repeat the previous two steps for each distribution set you wish to install. Change to the set's directory, run "Set_tmp_dir", and then run Extract set_name to extract the set. Once you are finished extracting all of the sets that you wish to install, you should proceed to the instructions below (after the last install medium type-specific instructions), that explain how you should configure your system. To install via FTP or NFS The first thing you should do is pick a temporary directory where the distribution files can be stored. To do this, enter the com- mand "Set_tmp_dir", and enter the name of the temporary directo- ry. (Don't forget that your disk is mounted under /mnt; you should probably pick a directory under /mnt/usr.) The default is /mnt/usr/distrib. Configure the network interface. To use SLIP, type the following command sequence: slattach -h -s speed tty00 ifconfig sl0 my_ipaddr peer_ipaddr where speed is the network speed, and my_ipaddr is the numeric IP address of the machine you are going to install NetBSD/x68k, while peer_ipaddr is the address of the peer machine connected with your machine. You might have to configure the peer SLIP in- terface with similar sequence (depending on the peer system). For instance, the sequence slattach -h -s 38400 tty00 ifconfig sl0 192.168.0.1 192.168.0.10 configures the SLIP interface for the network between your ma- chine (with IP address 192.168.0.1) and the peer (192.168.0.10) with speed 38400 bps. Note that IP addresses 192.168.*.* are the private IP addresses described in RFC 1597. To use ethernet, do following: ifconfig ne0 my_ipaddr where my_ipaddr is the numeric IP address of the machine you are going to install NetBSD/x68k. ne0 is the interface name which correspond to the Neptune-X or clone. If you are NFS-mounting the distribution sets, mount them on the temporary directory with a command like: mount -t nfs serv_ipaddr:dist_dir tmp_dir where serv_ipaddr is the server's numeric IP address, dist_dir is the path to the distribution files on the server, and tmp_dir is the name of the local temporary directory. Once this is done, proceed as if you had loaded the files from tape, changing to the appropriate directories, running Set_tmp_dir and running Extract as appropriate. If you are retrieving the distribution sets using ftp, change in- to the temporary directory, and execute the command: ftp serv_ipaddr where serv_ipaddr is once again the server's numeric IP address. Get the files with FTP, taking care to use binary mode when transferring the files. Once you have all of the files for the distribution sets that you wish to install, you can proceed using the instructions above, as if you had installed from a floppy. Note As with the floppy install, if you're short on disk space, you can transfer only one set at a time, extract it, and then delete it in order to save space.) Once you have finished extracting all of the distribution sets that you wish to install, and are back at the "#" prompt, you are ready to configure your system. The configuration utility expects that you have installed the "base" and "etc" distribution sets. If you have not, you will not be able to run it successfully (nor will you have a functional system, in any case). To configure your newly-installed NetBSD system, run the command "Configure". It will ask you for the system's host name, domain name, and other network configuration information. It will set up your configuration files and make the device nodes for the newly-in- stalled system. Congratulations, you have successfully installed NetBSD 1.4.2. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a net- worked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some of the files in the NetBSD 1.4.2 distribution might need to be tai- lored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc including /etc/rc.conf will probably need to be modified, as well. If you are unfa- miliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. 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 propperly configured state, with the most important ones described below. 1. Configuring /etc/rc.conf If you haven't done any configuration of /etc/rc.conf, 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 filesystem mounted read-write. When the system asks you to choose a shell, simply hit return to get to a prompt. If you are asked for a terminal type, respond with vt220 (or whatever is appropriate for your terminal type) and hit return. At this point, you need to configure at least one file in the /etc directory. 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. If your /usr directory is on a separate partition and you do not know how to use 'ed' or 'ex', you will have to mount your /usr partition to gain access to 'vi'. Do the follow- ing: mount /usr export TERM=vt220 If you have /var on a seperate 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 en- vironment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your interface , along the lines of ifconfig_de0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_de0="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. Other files in /etc that are new to NetBSD 1.4 and may require modi- fication 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. There is no initial password, but if you're using the machine in a networked environment, you should create an account for yourself (see below) and protect it and the "root" account with good passwords. 3. Adding accounts Use the vipw(8) command to add accounts to your system, do not edit /etc/passwd directly. See adduser(8) for more information on the process of how to add a new user to the system. 4. The X Window System If you have installed the X window system, look at the files in /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 3rd party packages There is a lot of software freely available for Unix-based systems, almost all of which can run on NetBSD. Modifications are usually needed to when transferring programs between different Unix-like systems, so the NetBSD packages collection incorporates any such changes necessary to make that software run on NetBSD, and makes the installation (and deinstallation) of the software packages easy. There's also the option of building a package from source, in case there's no precompiled binary available. Precompiled binaries can be found at ftp://ftp.netbsd.org/pub/NetBSD/packages/ Package sources for compiling packages can be obtained by retrieving the file ftp://ftp.netbsd.org/pub/NetBSD/NetBSD- current/tar_files/pkgsrc.tar.gz and extracting it into /usr/pkgsrc. See /usr/pkgsrc/README then for more information. 6. Misc o To adjust the system to your local timezone, point the /etc/localtime symlink to the appropriate file under /usr/share/zoneinfo. o Edit /etc/aliases to forward root mail to the right place (run newaliases(1) afterwards.) o The /etc/sendmail.cf file will almost definitely need to be ad- justed; files aiding in this can be found in /usr/share/sendmail. See the README file there for more infor- mation. 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 manu- al; so just invoking man filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System The upgrade to NetBSD 1.4.2 is a binary upgrade; it can be quite diffi- cult to advance to a later version by recompiling from source due primar- ily to interdependencies in the various components. To do the upgrade, you must have the bootable install floppy boot.fs, or, loadbsd.x utility and netbsd.INSTALL file which can be found in installation/misc in your Human68k disk. You must also have at least the base and kern binary distribution sets available, so that you can upgrade with it, using one of the upgrade methods described below. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are being overwritten in place, you only need space for the new binaries, which weren't previously on the system. If you have a few megabytes free on each of your root and /usr partitions, you should have enough space. Since upgrading involves replacing the boot blocks on your NetBSD parti- tion, the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to back up any important data on your disk, whether on the NetBSD partition or on another operat- ing system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: 1. Boot your machine using of the boot.fs floppy, or boot with loadbsd.x utility. 2. You will be presented with a welcome message and a prompt asking whether you are going to "install" NetBSD or "upgrade" an exisiting system. Select "upgrade" to start. 3. You will be presented with some information about the upgrade pro- cess and a warning message, and will be asked if you wish to proceed with the upgrade process. If you answer negatively, the upgrade process will stop, and your disk will not be modified. If you an- swer affirmatively, the upgrade process will begin, and your disk will be modified. You may hit Control-C to stop the upgrade process at any time. However, if you hit it at an inopportune moment, your system may be left in an inconsistent (and possibly unusable) state. 4. You will be asked if you wish to upgrade your file systems to the new file system format. If you do, reply affirmatively. If you don't have your file systems upgraded now, you should probably do it manually after the install process is complete, by using "fsck -c 2". Read the fsck(8) manual page for more details. Note that this step is only important when upgrading from a pre-NetBSD 1.0 release. 5. The upgrade program will then check your root file system, and, if you approved, will upgrade it to the new file system format. It will then mount your root file system on /mnt. 6. If your file systems are being upgraded, the upgrade script will copy the new fsck(8) program to your hard disk and upgrade your re- maining file systems. 7. The upgrade program will then automatically replace the boot blocks on your disk with newer versions, and mount all of your file systems under /mnt. (In other words, your root partition will be mounted on /mnt, your /usr partition on /mnt/usr, etc.) 8. If you don't already have the NetBSD distribution sets on your disk, look in the installation section for information on how to transfer them to your disk. 9. If you don't have the disk space to copy all of the distribution on- to the hard drive, you can install a kernel on the hard drive as de- tailed a few paragraphs below, then boot off the hard drive. Now you can copy and install distribution sets incrementally from your lone floppy drive. Once the distribution sets are transferred to your disk, continue here. (Obviously, if the NetBSD distribution sets are already on your disk, because you've transferred them before starting the up- grade process, you don't need to transfer them again now!) 10. After the software has been transferred to the machine (or mounted, in the case of upgrading via NFS or CD-ROM), change into the direc- tory containing the "base.tgz" distribution set. Once you are there, run the "Set_tmp_dir" command, and hit return at the prompt to select the default answer for the temporary directory's path name. (It should be the path name of the directory that you're in.) 11. Run the command "Extract kern" to upgrade the kernel. 12. Run the command "Extract base" to upgrade the base distribution. 13. Repeat the above two steps for all of the sets you wish to upgrade. (For each, change into the directory containing the set, run "Set_tmp_dir" and accept the default path name, then run the "Ex- tract " command.) 14. If you were previously using the security distribution set, you must upgrade to the new version, or you will not be able to log in when the upgrade process is complete. Similarly, if you were not previ- ously using the security set, you must not upgrade to the new ver- sion. 15. When you are done upgrading all of the distribution sets you wish to upgrade, issue the command "Cleanup". It will clean up the instal- lation, by remaking some system databases. When it is complete, all you have to do is to reboot(8) your system. Your system has now been upgraded to NetBSD 1.4.2. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 1.4.2 system. However, that doesn't mean that you're finished with the upgrade process. There are several things that you should do, or might have to do, to insure that the system works properly. First, if you did not upgrade your file systems to the new file system format during the upgrade process, and you are upgrading from a pre-1.0 NetBSD, you may want to do so now, with "fsck -c 2". If you are unsure about the process, it's suggested that you read the fsck(8) manual page. Second, you will probably want to get the etc distribution, extract it, and compare its contents with those in your /etc/ directory. You will probably want to replace some of your system configuration files, or in- corporate some of the changes in the new versions into yours. Third, you will probably want to update the set of device nodes you have in /dev. If you've changed the contents of /dev by hand, you will need to be careful about this, but if not, you can just cd into /dev, and run the command "sh MAKEDEV all". Fourth, you must deal with certain changes in the formats of some of the configuration files. The most notable change is that the "options" given to many of the file systems in /etc/fstab or by hand have changed, and some of the file systems have changed names. *IMPORTANT*: ANY INSTANCES OF "ufs" IN /etc/fstab MUST BE CHANGED TO "ffs". Important: any instances of ufs in /etc/fstab must be changed to ffs. To find out what the new options are, it's suggested that you read the manual page for the file systems' mount commands, for example mount_nfs(8) for NFS. Note The information for mounts of type ffs, i.e. Fast File System, is contained in the mount(8) man page. Finally, you will want to delete old binaries that were part of the ver- sion of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. If you are upgrading from a pre-1.0 NetBSD, you might also want to recompile any locally-built binaries, to take advan- tage of the shared libraries. (Note that any new binaries that you build will be dynamically linked, and therefore take advantage of the shared libraries, by default. For information on how to make statically linked binaries, see the cc(1) and ld(1) manual pages.) 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 1.4.2 Note Only issues effecting an upgrade from NetBSD 1.3 or NetBSD 1.3.x are decribed here. o "machine" directory/link in "/usr/include" Description Some architecture may fail to install the comp set because the /usr/include/machine directory changed to a symbolic link in NetBSD 1.4. Fix If this happens, you can use the command # rm -r /usr/include/machine to remove the old directory and it contents and reinstall the comp set. 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 op- tional. If you don't ask for a particular section, the topic with the lowest numbered section name will be displayed. For instance, after log- ging in, enter man passwd to read the documentation for passwd(1). To view the documentation for passwd(5)m 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 in- clude 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. If you're inter- ested 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 some- where, 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 Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. o UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. o Vixie Enterprises for hosting the NetBSD FTP, WWW and SUP server. o Redback Networks, Inc. for hosting the NetBSD Mail server. 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 Dave Burgess burgess@cynjut.infonet.net has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. o The following individuals and organiztions (each in alphabetical or- der) have made donations or loans of hardware and/or money, to sup- port NetBSD development, and deserve credit for it: Steve Allen Jason Birnschein Mason Loring Bliss Jason Brazile Mark Brinicombe David Brownlee Simon Burge Dave Burgess Ralph Campbell Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Scott Ellis Hubert Feyrer Castor Fu Greg Gingerich William Gnadt Michael Graff Guenther Grau Ross Harvey Charles M. Hannum Michael L. Hitch Kenneth Alan Hornstein Jordan K. Hubbard Soren Jorvang Scott Kaplan Noah M. Keiserman John Kohl Chris Legrow Ted Lemon Neil J. McRae Perry E. Metzger Herb Peyerl Mike Price Dave Rand Michael Richardson Heiko W. Rupp Brad Salai Chuck Silvers Thor Lancelot Simon Bill Sommerfeld Paul Southworth Ted Spradley Kimmo Suominen Jason R. Thorpe Steve Wadlow Krister Walfridsson Jim Wise Christos Zoulas AboveNet Communications, Inc. Advanced System Products, Inc. Avalon Computer Systems Bay Area Internet Solutions Brains Corporation, Japan Canada Connect Corporation Co-operative Research Centre for Enterprise Distributed Systems Technology Demon Internet, UK Digital Equipment Corporation Easynet, UK Free Hardware Foundation Innovation Development Enterprises of America Internet Software Consortium MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Piermont Information Systems Inc. VMC Harald Frank, Germany Warped Communications, Inc. (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 mentioned, tell us!) We are... (in alphabetical order) The NetBSD core group: Alistair Crooks agc@NetBSD.ORG Jun-ichiro itojun Hagino itojun@NetBSD.ORG Frank van der Linden fvdl@NetBSD.ORG Luke Mewburn lukem@NetBSD.ORG Christos Zoulas christos@NetBSD.ORG The portmasters (and their ports): Mark Brinicombe mark@NetBSD.ORG arm32 Jeremy Cooper jeremy@NetBSD.ORG sun3x Ross Harvey ross@NetBSD.ORG alpha Ignatios Souvatzis is@NetBSD.ORG amiga Jun-ichiro itojun Hagino itojun@NetBSD.ORG sh3 Eduardo Horvath eeh@NetBSD.ORG sparc64 Paul Kranenburg pk@NetBSD.ORG sparc Anders Magnusson ragge@NetBSD.ORG vax Tsubai Masanari tsubai@NetBSD.ORG macppc Tsubai Masanari tsubai@NetBSD.ORG newsmips Minoura Makoto minoura@NetBSD.ORG x68k Phil Nelson phil@NetBSD.ORG pc532 Scott Reynolds scottr@NetBSD.ORG mac68k Darrin Jewell dbj@NetBSD.ORG next68k Kazuki Sakamoto sakamoto@NetBSD.ORG bebox Wolfgang Solfrank ws@NetBSD.ORG ofppc Jonathan Stone jonathan@NetBSD.ORG pmax Shin Takemura takemura@NetBSD.ORG hpcmips Jason Thorpe thorpej@NetBSD.ORG hp300 Frank van der Linden fvdl@NetBSD.ORG i386 Leo Weppelman leo@NetBSD.ORG atari Nathan Williams nathanw@NetBSD.ORG sun3 Steve Woodford scw@NetBSD.ORG mvme68k The NetBSD 1.4.2 Release Engineering team: Chris G. Demetriou cgd@NetBSD.ORG Havard Eidnes he@NetBSD.ORG Ted Lemon mellon@NetBSD.ORG Perry Metzger perry@NetBSD.ORG Curt Sampson cjs@NetBSD.ORG Developers and other contributors: Steve Allen wormey@NetBSD.ORG Julian Assange proff@NetBSD.ORG Lennart Augustsson augustss@NetBSD.ORG Christoph Badura bad@NetBSD.ORG Robert V. Baron rvb@NetBSD.ORG Erik Berls cyber@NetBSD.ORG John Birrell jb@NetBSD.ORG Mason Loring Bliss mason@NetBSD.ORG Manuel Bouyer bouyer@NetBSD.ORG John Brezak brezak@NetBSD.ORG Allen Briggs briggs@NetBSD.ORG Aaron Brown abrown@NetBSD.ORG David Brownlee abs@NetBSD.ORG Frederick Bruckman fredb@NetBSD.ORG Jon Buller jonb@NetBSD.ORG Simon Burge simonb@NetBSD.ORG Dave Burgess burgess@cynjut.infonet.net Robert Byrnes byrnes@NetBSD.org D'Arcy J.M. Cain darcy@NetBSD.ORG Dave Carrel carrel@NetBSD.ORG Bill Coldwell billc@NetBSD.ORG Julian Coleman jdc@NetBSD.ORG Chuck Cranor chuck@NetBSD.ORG Aidan Cully aidan@NetBSD.ORG Johan Danielsson joda@NetBSD.ORG Matt DeBergalis deberg@NetBSD.ORG Rob Deker deker@NetBSD.ORG Chris G. Demetriou cgd@NetBSD.ORG Jaromir Dolecek jdolecek@NetBSD.ORG Andy Doran ad@NetBSD.ORG Roland Dowdeswell elric@NetBSD.ORG Matthias Drochner drochner@NetBSD.ORG Jun Ebihara jun@NetBSD.ORG Havard Eidnes he@NetBSD.ORG Enami Tsugutomo enami@NetBSD.ORG Bernd Ernesti veego@NetBSD.ORG Erik Fair fair@NetBSD.ORG Hubert Feyrer hubertf@NetBSD.ORG Thorsten Frueauf frueauf@NetBSD.ORG Castor Fu castor@NetBSD.ORG Brian R. Gaeke brg@dgate.org Thomas Gerner thomas@NetBSD.ORG Simon J. Gerraty sjg@NetBSD.ORG Justin Gibbs gibbs@NetBSD.ORG Adam Glass glass@NetBSD.ORG Michael Graff explorer@NetBSD.ORG Brian C. Grayson bgrayson@NetBSD.ORG Brad Grantham grantham@tenon.com Matthew Green mrg@NetBSD.ORG Juergen Hannken-Illjes hannken@NetBSD.ORG Charles M. Hannum mycroft@NetBSD.ORG Eric Haszlakiewicz erh@NetBSD.ORG HAYAKAWA Koichi haya@NetBSD.ORG Rene Hexel rh@NetBSD.ORG Michael L. Hitch mhitch@NetBSD.ORG Christian E. Hopps chopps@NetBSD.ORG Ken Hornstein kenh@NetBSD.ORG Marc Horowitz marc@NetBSD.ORG Dean Huxley dean@netbsd.org ITOH Yasufumi itohy@NetBSD.ORG Matthew Jacob mjacob@NetBSD.ORG Lonhyn T. Jasinskyj lonhyn@NetBSD.ORG Chris Jones cjones@NetBSD.ORG Soren Jorvang soren@NetBSD.ORG Antti Kantee pooka@NetBSD.ORG Lawrence Kesteloot kesteloo@cs.unc.edu Thomas Klausner wiz@NetBSD.ORG Klaus Klein kleink@NetBSD.ORG John Kohl jtk@NetBSD.ORG Kevin Lahey kml@NetBSD.ORG Johnny C. Lam jlam@NetBSD.ORG Martin J. Laubach mjl@NetBSD.ORG Ted Lemon mellon@NetBSD.ORG Joel Lindholm joel@NetBSD.ORG Mike Long mikel@NetBSD.ORG Warner Losh imp@NetBSD.ORG Brett Lymn blymn@NetBSD.ORG Paul Mackerras paulus@NetBSD.ORG Dan McMahill dmcmahill@NetBSD.ORG Neil J. McRae neil@NetBSD.ORG Perry Metzger perry@NetBSD.ORG der Mouse mouse@NetBSD.ORG Joseph Myers jsm@NetBSD.ORG Ken Nakata kenn@NetBSD.ORG Bob Nestor rnestor@NetBSD.ORG Tohru Nishimura nisimura@NetBSD.ORG Masaru Oki oki@NetBSD.ORG Greg Oster oster@NetBSD.ORG Herb Peyerl hpeyerl@NetBSD.ORG Matthias Pfaller matthias@NetBSD.ORG Dante Profeta dante@NetBSD.ORG Chris Provenzano proven@NetBSD.ORG Waldi Ravens waldi@moacs.indiv.nl.net Darren Reed darrenr@NetBSD.ORG Michael Richardson mcr@NetBSD.ORG Tim Rightnour garbled@NetBSD.ORG Gordon Ross gwr@NetBSD.ORG Heiko W. Rupp hwr@NetBSD.ORG SAITOH Masanobu msaitoh@NetBSD.ORG Curt Sampson cjs@NetBSD.ORG Wilfredo Sanchez wsanchez@NetBSD.ORG Ty Sarna tsarna@NetBSD.ORG SATO Kazumi sato@NetBSD.ORG Matthias Scheler tron@NetBSD.ORG Karl Schilke (rAT) rat@NetBSD.ORG Konrad Schroder perseant@NetBSD.ORG Tim Shepard shep@NetBSD.ORG Takao Shinohara shin@NetBSD.ORG Chuck Silvers chs@NetBSD.ORG Thor Lancelot Simon tls@NetBSD.ORG Noriyuki Soda soda@NetBSD.ORG Bill Sommerfeld sommerfeld@NetBSD.ORG Bill Studenmund wrstuden@NetBSD.ORG Kevin Sullivan sullivan@NetBSD.ORG Kimmo Suominen kim@NetBSD.ORG Matt Thomas matt@NetBSD.ORG Christoph Toshok toshok@NetBSD.ORG Izumi Tsutsui tsutsui@NetBSD.ORG UCHIYAMA Yasushi uch@NetBSD.ORG Todd Vierling tv@NetBSD.ORG Aymeric Vincent aymeric@NetBSD.ORG Paul Vixie vixie@NetBSD.ORG Krister Walfridsson kristerw@NetBSD.ORG Lex Wennmacher wennmach@NetBSD.ORG Assar Westerlund assar@NetBSD.ORG Rob Windsor windsor@NetBSD.ORG Dan Winship danw@NetBSD.ORG Jim Wise jwise@NetBSD.ORG Colin Wood ender@NetBSD.ORG Legal Mumbo-Jumbo The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engi- neering Group at Lawrence Berkeley Laboratory. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Adam Glass and Charles Han- num. This product includes software developed by Adam Glass. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Charles D. Cranor and Wash- ington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Wep- pelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Herb Peyerl. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And Com- munications, http://www.and.com/. This product includes software developed by Joachim Koenig-Baltes. This product includes software developed by Jochen Pohl for The NetBSD Project. This product includes software developed by John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Mark Brinicombe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by the Center for Software Sci- ence at the University of Utah. This product includes software developed by the University of Calgary De- partment of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Con- sortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Pier- mont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Michael Graff for the NetBSD Project. This product includes software developed by Niklas Hallqvist, C Stone and Job de Haas. This product includes software developed by Masaru Oki. This product includes software developed by Masanobu Saitoh. This product includes software developed by Takumi Nakamura. This product includes software developed by Kazuhisa Shimizu. This product includes software developed by Takuya HARAKAWA. This product includes software developed by MINOURA Makoto. This product includes software developed by Yasushi YAMASAKI. This product includes software developed by ITOH Yasufumi. NetBSD 23 March 1999 30