INSTALL(8) NetBSD System Manager's Manual INSTALL(8) NAME INSTALL -- Installation procedure for NetBSD/sparc. CONTENTS About this Document............................................2 Quick install notes for the impatient..........................3 What is NetBSD?................................................3 Changes Between The NetBSD 3.0.2 and 3.0.3 updates.............4 Supported devices...........................................4 Kernel......................................................4 Networking..................................................4 File system.................................................4 Security....................................................4 Miscellaneous...............................................5 alpha specific..............................................5 mac68k specific.............................................5 sparc specific..............................................5 Changes Between The NetBSD 3.0.1 and 3.0.2 updates.............5 Kernel......................................................5 Networking..................................................5 File system.................................................6 Libraries...................................................6 Security....................................................6 Miscellaneous...............................................6 amd64 specific..............................................6 sparc specific..............................................6 mac68k specific.............................................6 Changes Between The NetBSD 3.0 release and 3.0.1 update........6 Kernel......................................................6 Networking..................................................7 File system.................................................7 Libraries...................................................7 Security....................................................8 Miscellaneous...............................................8 acorn26 specific............................................8 amiga specific..............................................9 hp300 specific..............................................9 i386 specific...............................................9 m68k specific...............................................9 mips specific...............................................9 powerpc specific............................................9 sparc specific..............................................9 xen specific................................................9 The Future of NetBSD...........................................9 Sources of NetBSD.............................................10 NetBSD 3.0.3 Release Contents.................................10 NetBSD/sparc subdirectory structure........................11 Binary distribution sets...................................12 NetBSD/sparc System Requirements and Supported Devices........14 Supported machines.........................................14 Machines not supported by NetBSD/sparc.....................15 Supported devices..........................................15 Unsupported devices........................................18 Getting the NetBSD System on to Useful Media..................19 Preparing your System for NetBSD installation.................21 Configuring your PROM......................................21 Determining how to access your SCSI disk from the..........23 Determining how to boot from an SBUS card..................24 Deciding on partition sizes................................25 Configuration of network interfaces........................26 Installing the NetBSD System..................................26 Installing NetBSD by placing a bootable file system on.....26 Installing NetBSD by using a bootable CD-ROM...............27 Installing NetBSD by using the bootable floppies...........28 Installing NetBSD by using a netboot setup.................29 Installing NetBSD by using a bootable tape.................34 Running the installation scripts...........................35 Post installation steps.......................................36 Upgrading a previously-installed NetBSD System................39 Compatibility Issues With Previous NetBSD Releases............40 Issues affecting an upgrade from NetBSD 2.1 and older......40 Using online NetBSD documentation.............................40 Administrivia.................................................41 Thanks go to..................................................42 We are........................................................47 Legal Mumbo-Jumbo.............................................53 The End.......................................................61 DESCRIPTION About this Document This document describes the installation procedure for NetBSD 3.0.3 on the sparc platform. It is available in four different formats titled INSTALL.ext, where .ext is one of .ps, .html, .more, or .txt: .ps PostScript. .html Standard Internet HTML. .more The enhanced text format used on UNIX -like systems by the more(1) and less(1) pager utility programs. This is the format in which the on-line man pages are generally pre- sented. .txt Plain old ASCII. You are reading the ASCII version. Quick install notes for the impatient This section contains some brief notes describing what you need to install NetBSD 3.0.3 on a machine of the sparc architecture. o Fetch the CD image, sparccd.iso or the floppy disk images, sparc/install/floppy/disk1.gz and sparc/install/floppy/disk2. You need either the pair of floppies or the CD to boot your system. Alternatively, you may netboot the installation kernel. This process is covered below, in detail. o The actual binary distribution is in the sparc/binary/sets/ direc- tory. When you boot the install floppies or CD-ROM, the installation program can fetch these files for you (using e.g. ftp), if you have a network connection. There are several other methods to get the binary sets onto your machine. You will at a minimum need the following sets: kern-GENERIC.tgz, base.tgz and etc.tgz. In a typical workstation installation you will probably want all the installation sets. o Make sure your sparc's CD-ROM drive is bootable. Burn the CD. Oth- erwise, write the floppy images directly to a pair of floppies (after uncompressing disk1.gz). The disk(s) you just prepared will be used to boot the installation kernel, which contains all the tools required to install NetBSD. o You will need to get to the OpenBoot PROM ``ok'' prompt. After your system first powers on, and displays some initial information, press the STOP-A keys, or send a BREAK if you're on a serial console. At the ``ok'' prompt, type the command to boot your system into NetBSD. The command to boot from CD is one of the following commands (depend- ing on your model): ``b sd(,30,)'', ``boot sd(,30,)'', or ``boot cdrom''. The command to boot from floppy is either ``boot fd(,,1)'' or ``boot floppy''. The installer will prompt you to insert the second floppy when it is ready for it. o For third-party programs which are not part of the base NetBSD dis- tribution, you will want to explore the pkgsrc system with its more than 5400 program packages. What is NetBSD? The NetBSD Operating System is a fully functional Open Source UNIX -like operating system derived from the University of California, Berkeley Net- working Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on fifty four different system architectures (ports), featuring sev- enteen machine architectures across fifteen distinct CPU families, and is being ported to more. The NetBSD 3.0.3 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. 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 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.2 and 3.0.3 updates The NetBSD 3.0.3 update is the third security/critical update of the NetBSD 3.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. These fixes will also appear in future releases (NetBSD 3.2 etc), together with other less-critical fixes and feature enhancements. Specific updates are as follows: Supported devices o wd(4): fix broken Seagate drives ST3160021A and ST3160811A. Kernel o Don't accept a compressed vnd(4) image with block size 0 to avoid a kernel panic. Networking o Fix get-lease-hostnames option in dhcpd.conf(5) to make dhcpd(8) use the DNS hostname as the DHCP hostname given to the client. o Fix TCP window scaling in ipfilter(4). o Update BIND to version 9.3.2. File system o Prevent a kernel panic when creating snapshots on filesystems which use quota's. o Fix a coredump in dump(8) when using -X (filesystem internal snap- shots). o Fix a panic when one user has 65536 active vnodes on a quota-enabled file system. Security o Fix a buffer overflow in glob(3), which affected ftpd(8) and possibly other programs (SA2006-027). o X11: fix an integer overflow in the Render and DBE extensions (SA2007-002). o BIND: fix multiple Denial of Service vulnerabilities (SA2007-003). o Fix a buffer overflow in iso(4) which could potentially lead to a local root compromise (SA2007-004). o Fix an integer underflow in file(1) which could lead to an exploitable heap overflow. o X11: fix a number of possible memory corruptions due to integer over- flows (CVE 2007-1003, 1351, 1352, 1667). o Fix a denial of service vulnerability in racoon(8) which could allow an attacker to disrupt a connection between IPSec peers. o Disable processing or routing header type 0 (RH0) IPv6 packets since they can be used for DoS attacks (CVE-2007-2242). Provide a sysctl (net.inet6.ip6.rht0) to re-enable them. Note: the sysctl may be removed completely in future NetBSD releases. o Two veriexec(4) flaws have been fixed: users can no longer rename a file to a veriexec protected file or run unfingerprinted files at strict level two or above. o file(1) has been updated to version 4.21, including and integer underflow and an integer overflow fix (CVE-2007-1536 and CVE-2007-2799). Miscellaneous o Fix some problems with etcupdate(8) for upgrading. o Update time zoneinfo to tzdata2007f. o Set /etc/postfix/post-install mode 555 (executable) instead of 444. o passwd(1): display a message indicating who's password is being changed, to avoid confusion after su(1). o The /etc/daily, weekly, monthly and security scripts now use $TMPDIR instead of /tmp. alpha specific o Fix alignment problems causing regular panics on NetBSD/alpha and NetBSD/sparc. mac68k specific o Avoid a kernel panic before reboot. sparc specific o Fix alignment problems causing regular panics on NetBSD/alpha and NetBSD/sparc. Changes Between The NetBSD 3.0.1 and 3.0.2 updates The NetBSD 3.0.2 update is the second security/critical update of the NetBSD 3.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. These fixes will also appear in future releases (NetBSD 3.1 etc), together with other less-critical fixes and feature enhancements. Specific updates are as follows: Kernel o Avoid a panic in page fault handling that could occer under low-mem- ory conditions. Networking o Changed the default sshd_config(8) to enable SSH version 2 only. o Don't accept TCP connections to broadcast addresses. File system o Fixed race condition in NFS renaming that could cause the renamed file to be deleted. Libraries o When a user is created, initialize the string of secondary groups to avoid it containing garbage when none is added. Security o Fixed a buffer overflow in the in-kernel PPP code share by ISDN PPP interfaces ippp(4) and pppoe(4) (SA2006-019). o X11: fixed an integer overflow in FreeType (SA2006-020). o Fixed a potential DoS attack with sendmail(8) (SA2006-017). o Fixed a DoS vulnerability in BIND (SA2006-022). o Fixed a RSA signature forgery in openssl(1) (SA2006-023). o X11: fixed a vulnerability in Adobe Type 1 font handling (SA2006-021). o Fixed a number of DoS vulnerabilities in openssl(1) (SA in prepara- tion, CVE entries: 2006-2937, 2940, 3738 and 4343). o Fixed a number of DoS vulnerabilities in sshd(8) (SA in preparation, CVE entries: 2006-4924 and 5051). Miscellaneous o Fixed cross-building from GCC 4.x hosts. amd64 specific o Make sure that the system reboots after a panic instead of halting. sparc specific o Disabled threading in named(8) on sparc and sparc64 to avoid a crash. mac68k specific o sysinst now newfs'es and mounts the target filesystem(s). Changes Between The NetBSD 3.0 release and 3.0.1 update The NetBSD 3.0.1 update is the first security/critical update of the NetBSD 3.0 release branch. This represents a selected subset of fixes deemed critical in nature for stability or security reasons. These fixes will also appear in future releases (NetBSD 3.1 etc), together with other less-critical fixes and feature enhancements. Specific updates are as follows: Kernel o Hold kernel_lock while calling systrace_exit(). o In systrace_make_msg(), sleep uninterruptibly while waiting for the response from the systrace daemon, so that the message protocol between the kernel and the daemon doesn't get out of sync. o RAIDframe: mark used spares as failed if they encounter IO errors. o wdc(4): after a reset don't wait for drives to come ready if there are no drives (fixes a 30s hang after resume). o Fix support in wd(4) for 1 and 2TB disks. o Fix a bug in the fragment cache which could cause kernel panics (SA2006-004). o Fix a crash caused by azalia(4) when a connection list has invalid NIDs. o aic(4): work around an rbus resource allocation problem so cards work again. o RAIDframe was erroneously re-initializing the Parity Stripe Status pool each time a new array was configured. This causes grief with things like 'vmstat -m' by causing it to loop. Make RAIDframe only initialize PSS bits once. o twe(4): fix a memory leak in the TWEIO_GET_PARAM ioctl. o Prevent system crashes caused by malformed ELF interpreters (SA2006-008). o usb(4): Allow a NULL pointer as argument to usb_get_next_event(), and don't allocate a "struct usb_event" on stack in usb_add_event(). o Check the "oldlen" argument to sysctl(2) before passing it to vslock(9). This prevents a local DOS (SA2006-013). o Use a pmatch(9) expression which should catch all present and future seagate drives larger than 200GB for the WD_QUIRK_FORCE_LBA48 quirks. o Fix the 'audioctl of death' problem (SA2006-014). o Limit the size of any kernel buffers allocated by the VOP_READDIR routines to MAXBSIZE. Networking o Make sure all bridge(4) structs are initialized to 0. o Fix a memory disclosure in bridge(4) (SA2006-005). o Use sigaction(2) to setup automatic disposal of child processes after daemonizing rpc.statd(8). This is more portable and avoids zombie rpc.statd(8) processes after an NFS client running e.g. Mac OS X shuts down. o Prevent system crash when attempting to gather information about a non-existing alias of a network interface via the SIOCGIFALIAS ioctl (SA2006-012). o Fix a panic caused by insufficient validation when parsing IPv6 socket options (SA2006-016). File system o Change union_unmount() to not play with the fs root vnode explicitly. Let it get recycled along with all of the others. This is important as if the root vnode has already been reclaimed, then we get a panic when we try to vget it. Libraries o xdr_rec.c missing a bugfix for an improper security check. The cor- rect way to check for a zero record length is to check for it without the LAST_FRAG marker in it, since it's legal to send a LAST_FRAG marker with 0 bytes of data. o pam_nologin(8): use the class of the user, not then default class, when checking for nologin and ignorelogin login.conf(5) capabilities. o pam_unix(8): fix an uninitialized variable, and remove some unreach- able code. o Make PAM work on NetBSD ports without shared library support. o Make password aging work again. o Fix a bug in signal handling which could e.g get the MySQL daemon stuck in a tight loop after receiving a HUP signal. Security o Improve rnd(4) code probing for the Intel hardware RNG to avoid false detections (SA2006-009). o mail(1) creates record file with insecure umask (SA2006-007). o Fix a remote code execution vulnerability in sendmail (SA2006-010). o A vulnerability was found in the fast_ipsec(4) stack that renders the IPSec anti-replay service ineffective under certain circumstances (SA2006-011). o Fix a number of small security problems with the games. o Fix an FPU Information leak on i386/amd64/Xen platforms with AMD CPUs (SA2006-015). o Fix several integer overflows and NULL-pointer dereferences in freetype2. o Fix a denial of service vulnerability in sendmail when handling mal- formed multipart MIME messages (SA2006-017). Miscellaneous o Sync the Nvidia drivers with XFree86's sources as of December 24th, 2005. These changes fix lots of problems (i.e. freezes) with the latest cards (such as a GeForce 6600GT). o Give systrace its own version of realpath() that does what it wants, call it intercept_realpath(). Unbreaks systrace. o login(1), pam_securetty(8): don't issue a different message for root login on an insecure terminal. o Fix some unpaired sigblocks which possibly leave a process with all signals blocked (esp. apparant under Gnome). o Fix a NULL pointer dereference in ftp(1). o Make sh(1) expand "$@" correctly again. acorn26 specific o Avoid panics under NetBSD/acorn26 whenever a process exits. o Stop NetBSD/acorn26 from allocating eight times as much pool memory as it needs, leading to a rapid exhaustion of physical memory. NetBSD/acorn26 now boots multi-user again. amiga specific o Installer: don't ask for the root device before the user had a chance to identify how it's called under NetBSD. hp300 specific o Fix the bootloader so it doesn't print garbage to the bitmap console. o Fix a huge number of pkgsrc build problems. o Fix boot failure problem on HP400t with fb console. o Fix a problem with the probe of SCSI disks in the installer. i386 specific o Update pciide at pnpbios to work with the last changes to wdc(4), especially the deferral of drive probe. m68k specific o Fix a huge number of pkgsrc build problems. mips specific o Avoid kernel panics caused by binaries compiled with "-mips2" or bet- ter. o Update FPE trapsignal functions for new siginfo. powerpc specific o Avoid pthreads program crashes. sparc specific o For GCC3 and later, use the __builtin_va* constructs. Avoids a build problem with Firefox. xen specific o Avoid dom0 kernel crash when destroying a domain with active I/O going. o Fix the FPU problems detected by paranoia on a NetBSD/Xen guest. o Check the destination ethernet address when not in promiscous mode. Fix a problem where packets would be duplicated, possibly looping, when a domU is doing IP routing. o Avoid panics under high system load. NetBSD 3.0.3 is the ninth major release for the sparc. NetBSD 3.0.3 on sparc is, as usual, also fully backward compatible with old NetBSD/sparc binaries, so you don't need to recompile all your local programs provided you set the appropriate binary compatibility options in your kernel configuration. 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 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. 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 3.0.3 Release Contents The root directory of the NetBSD 3.0.3 release is organized as follows: .../NetBSD-3.0.3/ CHANGES Changes since earlier NetBSD releases. LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 3.0.3 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 3.0.3 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. 79 MB gzipped, 367 MB uncompressed pkgsrc This set contains the ``pkgsrc'' sources, which contain the in- frastructure to build third-party packages. 24 MB gzipped, 200 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. 5 MB gzipped, 20 MB uncompressed src This set contains all of the base NetBSD 3.0.3 sources which are not in gnusrc, sharesrc, or syssrc. 37 MB gzipped, 176 MB uncompressed syssrc This set contains the sources to the NetBSD 3.0.3 kernel for all architectures; config(8); and dbsym(8). 26 MB gzipped, 140 MB uncompressed xsrc This set contains the sources to the X Window System. 84 MB gzipped, 450 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 -m 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 MD5 digest is the safest checksum, followed by the POSIX checksum. The other two checksums are provided only to ensure that the widest pos- sible range of system can check the integrity of the release files. NetBSD/sparc subdirectory structure The sparc-specific portion of the NetBSD 3.0.3 release is found in the sparc subdirectory of the distribution: .../NetBSD-3.0.3/sparc/. It con- tains the following files and directories: INSTALL.html INSTALL.ps INSTALL.txt INSTALL.more Installation notes in various file formats, including this file. The .more file contains underlined text using the more(1) conventions for indicating italic and bold display. binary/ kernel/ netbsd-GENERIC.gz A gzipped NetBSD kernel containing code for everything supported in this release. netbsd-GENERIC.MP.gz A gzipped NetBSD kernel containing code for everything supported in this release. This kernel also supports SMP on systems with more than one CPU. netbsd-GENERIC_SCSI3.gz A kernel with SCSI ID 3 explicitly mapped to sd0. netbsd-KRUPS.gz A kernel for JavaStation-NC (Krups) machines. netbsd-MRCOFFEE.gz A kernel for JavaStation-1 (Mr. Coffee) machines using Open Boot Prom firmware. netbsd-MRCOFFEE_OFW.gz A kernel for JavaStation-1 (Mr. Coffee) machines using OpenFirmware. netbsd-GENERIC_SUN4U.gz A kernel which supports sparc64 hard- ware in 32-bit mode only. See the sparc64 INSTALL notes for help installing this kernel on your sparc64 hardware. sets/ sparc binary distribution sets; see below. installation/ bootfs/ Netbootable RAM disk kernel and the file system in the RAM disk; see below. floppy/ sparc boot and installation floppies; see below. miniroot/ sparc miniroot file system image; see below. netboot/ Netboot bootloader and root filesystem with install tools; see below. tape/ sparc boot and installation tapes; see below. Binary distribution sets The NetBSD sparc binary distribution sets contain the binaries which com- prise the NetBSD 3.0.3 release for the sparc. The binary distribution sets can be found in the sparc/binary/sets subdirectory of the NetBSD 3.0.3 distribution tree, and are as follows: base The NetBSD 3.0.3 sparc 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. 18 MB gzipped, 51 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. 21 MB gzipped, 77 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/sparc 3.0.3 GENERIC kernel named /netbsd. You must install this distribution set. 2 MB gzipped, 4 MB uncompressed kern-GENERIC.MP This set contains a NetBSD/sparc 3.0.3 GENERIC.MP kernel, which will use multiple processors (if present), named /netbsd. 2 MB gzipped, 4 MB uncompressed kern-GENERIC_SCSI3 This set contains a NetBSD/sparc 3.0.3 GENERIC_SCSI3 kernel, which will set SCSI ID 3 to sd0, named /netbsd. 2 MB gzipped, 4 MB uncompressed kern-GENERIC_SUN4U This set contains a NetBSD/sparc 3.0.3 GENERIC_SUN4U kernel, which supports only UltraSPARC systems in 32 bit mode, named /netbsd. 3 MB gzipped, 6 MB uncompressed kern-KRUPS This set contains a NetBSD/sparc 3.0.3 GENERIC-KRUPS kernel, which supports the JavaStation-NC, named /netbsd. 1 MB gzipped, 2 MB uncompressed kern-MRCOFFEE This set contains a NetBSD/sparc 3.0.3 MRCOFFE kernel, which which supports the OpenBOOT PROM 2 JavaStation-1, named /netbsd. 1 MB gzipped, 2 MB uncompressed kern-MRCOFFEE_OFW This set contains a NetBSD/sparc 3.0.3 MRCOFFE_OFW kernel, which which supports the OpenFirmware JavaStation-1, named /netbsd. 1 MB gzipped, 2 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, 30 MB uncompressed misc This set includes the (rather large) system dictionaries, the typesettable document set, and other files from /usr/share. 3 MB gzipped, 9 MB uncompressed text This set includes NetBSD's text processing tools, including groff(1), all related programs, and their manual pages. 2 MB gzipped, 7 MB uncompressed NetBSD maintains its own set of sources for the X Window System in order to assure tight integration and compatibility. These sources are based on XFree86, and tightly track XFree86 releases. They are currently equivalent to XFree86 4.4.0. Binary sets for the X Window System are distributed with NetBSD. The sets are: xbase The basic files needed for a complete X client environment. This does not include the X servers. 6 MB gzipped, 18 MB uncompressed xcomp The extra libraries and include files needed to compile X source code. 12 MB gzipped, 42 MB uncompressed xfont Fonts needed by X. 31 MB gzipped, 39 MB uncompressed xetc Configuration files for X which could be locally modified. 0.03 MB gzipped, 0.17 MB uncompressed xserver The X server. This includes Xsun, Xsun24, XsunMono and Xvfb servers with man pages. 5 MB gzipped, 13 MB uncompressed The sparc 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: The distribution cannot be extracted using the SunOS tar program Note: Each directory in the sparc binary distribution also has its own checksum files, just as the source distribution does. NetBSD/sparc System Requirements and Supported Devices The minimum configuration requires 4 MB of RAM and 60 MB of disk space. To install the entire system requires about 260 MB (not including swap). To install the X window system you need at least 295 MB (not including swap) and 8 MB RAM. NetBSD with 4 MB of RAM feels like Solaris with 4 MB of RAM -- slow. Note that until you have around 16 MB of RAM, getting more RAM is more important than getting a faster CPU. Supported machines o sun4 - 4/100 - 4/200 - 4/300 - 4/400 o sun4c - SPARCstation/server 1 - SPARCstation/server 1+ - SPARCstation/server 2 - IPC - ELC - IPX - SLC o sun4c clones - Aries Parrot II - Opus/5000 - Opus/5250 - FORCE Sparc CPU1e/4 - FORCE Sparc CPU2e/4 (and possibly more) Note: NetBSD doesn't support the VME interface on the FORCE models o sun4m - 4/600 - SPARC Classic - SPARC LX - SPARCstation 4 - SPARCstation/server 5 - SPARCstation/server 10 - SPARCstation/server 20 - SPARCstation Voyager - JavaStation-1 (Mr. Coffee) - JavaStation-NC (Krups) Note: All known SuperSPARC, hyperSPARC, microSPARC, and Tur- boSPARC CPUs are supported o sun4m clones - Axil 245 - Axil 311 - Axil 320 - Cycle C C Cycle 5-IP - DTKstation/Classic+ - RDI PowerLite-85 - RDI PowerLite-110 - RDI BriteLite - Ross sparc 20 - Transtec SS5/170 - Tatung microCOMPstation 5 - Twinhead TWINstation 5G - TWS SuperCOMPstation-20S - Tadpole SPARCbook 3 series (and possibly more) Machines not supported by NetBSD/sparc o sun4d - SPARCcenter 1000 - SPARCcenter 2000 o sun4u and other UltraSPARC based machines in 64-bit mode. They are supported in 32-bit mode with the NetBSD/sparc GENERIC_SUN4U kernel. UltraSPARC based machines in 32-bit or 64-bit mode are sup- ported by the NetBSD/sparc64 port. Refer to http://www.NetBSD.org/Ports/sparc64/index.html o Solbourne machines Supported devices o sun4m mbus CPU modules; Sun 4/600, SPARCstation/server 10, SPARCstation/server 20, and clones - cpu0; All single-CPU systems are supported - cpuN; All hardware compatible dual-, tri- and quad- CPU SuperSPARC-I, SuperSPARC-II, and hyperSPARC sys- tems are supported with the SMP kernel (GENERIC.MP) http://www.NetBSD.org/Ports/sparc/faq.html#smp-cpus o sun4c and sun4m video; Sbus card, on-board, or optional - bwtwo; 1 bpp framebuffer. On-board and Sbus card (MG1 and MG2) - cgthree; 8 bpp framebuffer. On-board and Sbus card - cgsix; 8 bpp accelerated framebuffer. On-board and Sbus card (GX, GX+, TGX, and TGX+) - cgfourteen; SX 24 bpp accelerated framebuffer. On-board SPARCstation 10SX and SPARCstation 20, requires optional 4 or 8 MB VSIMM, limited to cgthree emulation - tcx; S24 accelerated color framebuffer. On-board SPARCstation 4 (8 bpp), JavaStation-1 (24 bpp), and optional on SPARCstation 5 (24 bpp), limited to cgthree emulation - pnozz; Weitek p9100 24 bpp accelerated framebuffer. On-board Tadpole SPARCbook 3GS and 3GX, limited to cgthree emulation - zx; ZX and TZX 24 bpp accelerated framebuffer. Sbus card (leo) limited to text console (no X) - igsfb; 24 bpp IGS C1682 accelerated framebuffer. On-board JavaStation-NC limited to text console (no X) o sun4 video; VME card, on-board, or P4 (supported only on 4/100 and 4/300 series machines) - bwtwo; 1 bpp framebuffer. On-board and P4 - cgtwo; 8 bpp framebuffer. VME card - cgfour; 8 bpp framebuffer with overlay. P4 - cgsix; LEGO 8 bpp accelerated framebuffer. P4 - cgeight; TC 24 bpp framebuffer with overlay. P4 (not well tested) o Network interfaces - be; 100 Mbps half-duplex ``Big Mac'' ethernet. Sbus card - en; Efficient Networks, Inc. ATM interface. Sbus card - hme; 100 Mbps full-duplex ``Happy Meal'' ethernet. On-board (JavaStation-NC) and Sbus card This hardware is not supported on the sun4c platform - ie; 10 Mbps Intel 82586 ethernet. On-board (4/100 and 4/200, may not be working prop- erly on 4/400) and VME card - le; 10 Mbps AMD 9790 Lance ethernet. On-board (4/300, sun4c, and sun4m) and Sbus card - qec; One 100 Mbps be interface and four 10 Mbps Mace ethernet interfaces. Sbus card - qfe; four 100 Mbps full-duplex ``Happy Meal'' ether- net interfaces. Sbus card - misc: various ethernet interfaces are found on multi- function Sbus cards (e.g. along with SCSI), the eth- ernet interfaces work even if the other functions do not o SCSI interfaces - esp; 5 MB/s and 10 MB/s (Fast) NCR 53C9x SCSI con- troller, and 20 MB/s (Fast+Wide) FAS336 controller (known as `fas' on Solaris). On-board (sun4c, sun4m, 4/300, Ultra 1e, and Ultra 2) and Sbus cards - isp; 10 MB/s (Fast) and 20 MB/s (Fast+Wide) Qlogic ISP 10x0 family. Sbus card - si; 5 MB/s NCR 5380 SCSI controller. VME card (Interrupt driven and polled DMA) - sw; 5 MB/s NCR 5380 ``SCSI Weird'' controller. Onboard 4/110 (polled DMA only) - misc: SCSI functionality is sometimes found on multi- function Sbus cards (e.g. along with ethernet), the SCSI esp and isp portions of those cards should work, even if the other functions do not. Note: Non-Sun SCSI CD-ROMs may have trouble booting any OS, NetBSD or otherwise. Your CD-ROM must support 512 byte blocks for the OpenBoot PROM to load a file. Most newer CD-ROM drives sup- port this automatically, and many older drives allow you to set it using a jumper. See http://www.ebsinc.com/solaris/suncdrom.html for information on bootable CD-ROMs o VME disk interfaces - xd; Xylogics 7053 VME/SMD disk controller - xy; Xylogics 450/451 VME disk controller Note: VME/IPI disks are not supported o Floppy drives - fd; floppy disk drive. On-board sun4c and sun4m - sd; SCSI floppy drive, acts as a SCSI drive to ker- nel. found with some SPARCbook 3 machines o PCMCIA/Cardbus devices - nell; PCMCIA interface On-board (SPARCstation Voyager) and Sbus card. All devices listed in the Machine-independent PCMCIA driv- ers page should work, but very few have been tested with NetBSD/sparc. http://www.NetBSD.org/Hardware/pcmcia.html Note: See the FAQ for more information. http://www.NetBSD.org/Ports/sparc/faq.html#nell o Serial interfaces - zs; Zilog 8530 serial ports, which can be used as the system console On-board sun4, sun4c, and sun4m - com; Zilog 85C30 serial ports (ns16550a) On-board Tadpole SPARCbook 3GS and 3GX (internal 14.4 kbps modem, use /dev/ttyC0) JavaStation-1, and JavaS- tation-NC o Input devices - Sun keyboard and mouse - SPARCbook 3 keyboard and joystick - Third-party keyboards, mice, and trackballs - PS/2 keyboards and mice on JavaStation models o Audio interfaces - audioamd; AMD 7930-based 8000 Hz, 8 bit, mono, mu- law. On-board sun4c and SPARC Classic - audiocs; CS4231-based 44 KHz, 16 bit, stereo, PCM. On-board SPARCStation 5, JavaStation-1, JavaStation- NC, and optional on SPARCStation 4. o Misc cards - mtty / mbpp; Magma Serial/Parallel ports. Sbus card - xbox; Sun Sbus expander device o Parallel ports - bpp; Bi-directional parallel port. On-board and Sbus card Unsupported devices - DBRIe-based audio and ISDN. On-board some sun4m machines (such as SPARCstation 10, SPARCstation 20, SPARC LX, SPARCstation Voyager, and Tadpole SPARCbook 3) - sc; Sun SCSI. VME card - cgtwelve; I.e. GS, 24 bpp framebuffer. Sbus card - PCMCIA interface On-board Tadpole SPARCbook 3GS and 3GX Getting the NetBSD System on to Useful Media Note that if you are installing or upgrading from a writable media, the media can be write-protected if you wish. These systems mount a root image from inside the kernel, and will not need to write to the media. If you booted from a floppy, the floppy disk may be removed from the drive after the system has booted. Installation is supported from several media types, including: - CD-ROM / DVD - MS-DOS floppy - FTP - Remote NFS partition - Tape - Existing NetBSD partitions, if performing an upgrade The steps necessary to prepare the distribution sets for installation depend upon which installation medium you choose. The steps for the various media are outlined below. CD-ROM / DVD Find out where the distribution set files are on the CD-ROM or DVD. Likely locations are binary/sets and sparc/binary/sets. Proceed to the instruction on installation. MS-DOS floppy NetBSD doesn't include split sets to keep the distribution size down. They can be created on a seperate machine using the split(1) command, running e.g. split -b 235k base.tgz base. to split the base.tgz file from sparc/binary/sets into files named base.aa, base.ab, and so on. Repeat this for all set_name.tgz files, split- ting them into set_name.xx files. Count the number of set_name.xx files that make up the distribution sets you want to install or upgrade. You will need one sixth that number of 1.44 MB floppies. Format all of the floppies with MS-DOS. Do not make any of them bootable MS-DOS floppies, i.e. don't use format /s to format them. (If the floppies are bootable, then the MS-DOS system files that make them bootable will take up some space, and you won't be able to fit the distri- bution set parts on the disks.) If you're using floppies that are formatted for MS-DOS by their manufacturers, they probably aren't bootable, and you can use them out of the box. Place all of the set_name.xx files on the MS-DOS disks. Once you have the files on MS-DOS disks, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the sec- tion on upgrading. FTP The preparations for this installation/upgrade method are easy; all you need to do is make sure that there's an FTP site from which you can retrieve the NetBSD distribution when you're about to install or upgrade. If you don't have DHCP available on your network, you will need to know the numeric IP address of that site, and, if it's not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. If you don't have access to a functioning nameserver during installation, the IPv4 address of ftp.NetBSD.org is 204.152.184.75 and the IPv6 address is 2001:4f8:4:7:2e0:81ff:fe21:6563 (as of June, 2004). 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 exist- ing installation, go directly to the section on upgrading. Note: This method of installation is recom- mended for those familiar with using BSD network configuration and management com- mands. If you aren't, this documentation should help, but is not intended to be all-encompassing. NFS Place the NetBSD distribution sets you wish to install into a directory on an NFS server, and make that directory mountable by the machine on which you are installing or upgrading NetBSD. This will probably require modifying the /etc/exports file on of the NFS server and resetting its mount daemon (mountd). (Both of these actions will probably require superuser privileges on the server.) You need to know the numeric IP address of the NFS server, and, if you don't have DHCP avail- able on your network and the server is not on a network directly connected to the machine on which you're installing or upgrading NetBSD, you need to know the numeric IP address of the router closest to the NetBSD machine. Finally, you need to know the numeric IP address of the NetBSD machine itself. Once the NFS server is set up properly and you have the information mentioned above, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the sec- tion on upgrading. Note: This method of installation is recom- mended for those already familiar with using BSD network configuration and man- agement commands. If you aren't, this documentation should help, but is not intended to be all-encompassing. Tape To install NetBSD from a tape, you need to make a tape that contains the distribution set files, in `tar' format. If you're making the tape on a UNIX -like sys- tem, the easiest way to do so is probably some- thing 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; pos- sibly /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 example, dist_directories are the distribution sets' directories, for the distri- bution sets you wish to place on the tape. For instance, to put the misc, base, and etc distri- butions on tape (in order to do the absolute minimum installation to a new disk), you would do the following: # cd .../NetBSD-3.0.3 # cd sparc/binary # tar -cf tape_device misc etc kern Note: You still need to fill in tape_device in the example. Once you have the files on the tape, you can proceed to the next step in the installation or upgrade process. If you're installing NetBSD from scratch, go to the section on preparing your hard disk, below. If you're upgrading an existing installation, go directly to the sec- tion on upgrading. Preparing your System for NetBSD installation Configuring your PROM Before you start, you should configure your PROM. There are three categories of PROM: ``sunmon'' (sometimes called Restricted Prompt, sun monitor, or old command mode), OpenBoot PROM 1, and OpenBoot PROM 2. The sun4 machines only have sun- mon. Some of the early sun4c models default to sunmon but have OpenBoot PROM 1. The later sun4c models and all sun4m models have OpenBoot PROM 2. First, you need to stop your system from automatically booting when powered on. Pressing the STOP key (sometimes called the L1 key, found on the left side of your keyboard) and the a key will halt your system and give you a PROM prompt. If you are using a Tadpole SPARCbook, you press the Pause and a keys. If you are using a serial console, send a ``BREAK'' signal from your terminal (the method of sending ``BREAK'' varies from ter- minal to terminal). If the ethernet address of your sparc system is ff:ff:ff:ff:ff:ff, then your NVRAM battery is dead and you will have trouble using ethernet (among other problems). Read the Sun NVRAM/Hostid FAQ. http://www.squirrel.com/squirrel/sun-nvram-hostid.faq.html If you have a valid ethernet address and you plan to netboot, write down your system's ethernet address. Next, you should set your system to always use the OpenBoot PROM (sometimes called ``new command mode'') if it defaults to sunmon. The NetBSD kernel relies on some of the functionality provided by the OpenBoot PROM. If your machine gives you a `' prompt instead of an `ok' prompt, type: n ok setenv sunmon-compat? false ok Next, if you are using any security features of OpenBoot PROM, you should turn them off -- NetBSD can't deal well with this. ok setenv security-mode none If you are using a serial console, the NetBSD/sparc installer defaults to using 9600 bps, 8N1 settings. You may want to con- figure your system and serial terminal like this prior to boot- ing the installer. Additionally, a new installation of NetBSD/sparc will default to these settings as well. The OpenBoot PROM 1 machines (SPARCstation/server 1, SPARCsta- tion/server 1+, IPC, and SLC) have an odd SCSI quirk you should be aware of. There are three SCSI addressing schemes used by your system: SCSI target ID (set by physical jumpers on the device), PROM `unit' number (set by OpenBoot PROM 1, based on its SCSI target ID), and the name you reference within an oper- ating system (set by the kernel, based on the PROM `unit' num- ber). Sun shipped these systems with the internal drives set to SCSI target IDs 3 and 1. The default value of the OpenBoot PROM variable `sd-targets' is `31204567.' This variable maps how the OpenBoot PROM 1 assigns `unit' numbers based on the SCSI target ID. Thus the device at SCSI target ID 3 is considered `unit' 0, and the SCSI device at target ID 0 is `unit' 3. When you type ``boot scsi(0,0,0)'', the OpenBoot PROM will boot from `unit' 0 (which is SCSI target ID 3, the internal hard drive). The SunOS kernel is hard-wired to map sd0 to SCSI target 3, and sd3 to SCSI target 0. PROM Unit# SCSI Target SunOS name 0 3 sd0 1 1 sd1 2 2 sd2 3 0 sd3 4 4 st0 5 5 st1 6 6 cdrom The NetBSD/sparc GENERIC kernel does not wire things down as does SunOS. It names the disks in the order that the SCSI tar- gets are probed (01234567). If you only have one disk, it is always sd0 regardless of its SCSI target ID or its PROM `unit' number, and there are no problems. If you have two disks, one at SCSI ID 2 ( `unit' 2) and SCSI ID 3 ( `unit' 0), then they are recognized as sd0 and sd1 respectively. This can be a prob- lem if you are not aware of it, particularly when creating an fstab. There are two approaches to fixing this problem: changing the mapping that OpenBoot PROM 1 does, and changing the NetBSD ker- nel configuration. To get OpenBoot PROM 1 to number the SCSI `unit' numbers the same as the SCSI target IDs, you need to run this command: ok setenv sd-targets 01234567 This may, however, cause problems if you were to later attempt to use SunOS on this machine or if you reset the OpenBoot PROM variables. The other approach is to use a NetBSD kernel that matches the PROM's odd target mapping by treating `unit' 0 (i.e. SCSI tar- get ID 3) as sd0 and `unit' 3 (i.e. SCSI target ID 0) as sd3. The GENERIC_SCSI3 kernel performs this target mapping, but the GENERIC and INSTALL kernels do not. Note: This is also a concern when you start building your own customised kernels. The machines with OpenBoot PROM 2 (SPARCstation/server 2, ELC, IPX, and all sun4m models) have a similar SCSI target mapping in the form of a devalias entry. That is, the device alias disk is shorthand for the disk at SCSI ID 3 on the internal SCSI controller. Normally, the disk device alias is what the PROM uses as the default boot device, i.e. in the absence of a device argument to the boot command. Note that there are also pre-configured device alias entries for disk0, disk1, disk2 and disk3, which are in fact a one-to-one mapping to the SCSI tar- gets 0 to 3 (all on the internal SCSI controller). Again, it may be advantageous to use a fixed ``SCSI target'' to ``NetBSD disk unit'' mapping in your kernel configuration file (such as is done in the GENERIC_SCSI3 kernel) to ensure that your disks remain showing up at the same NetBSD device unit numbers even if you add disks to your system at a later time. Determining how to access your SCSI disk from the PROM sunmon and OpenBoot PROM 1 use an archaic sd(c,u,p) syntax to address SCSI devices. OpenBoot PROM 2 uses a more intuitive syntax using device aliases. To calculate the parameters for sunmon and OpenBoot PROM 1: c specifies the SCSI controller number (first is 0, second is 1, ...) u the hexadecimal number obtained from evaluating the expression (8 * TARGET) + LUN p the partition number from which to boot (`0' = `a', `1' = `b', etc.) Therefore, to boot from the swap partition on the internal hard drive (first SCSI bus, target 0, lun 0, partition 1), one would use: ok boot sd(0,0,1) To boot from a CD-ROM (first SCSI bus, target 6, lun 0, parti- tion dynamically determined), one would use: ok boot sd(0,30,) And, to boot from a kernel named netbsd-GENERIC on the fourth partition ( `d', often the /usr partition) on an external hard drive (first SCSI bus, target 2, lun 0, partition 3), one would use: ok boot sd(0,10,3)netbsd-GENERIC Now, for OpenBoot PROM 2, SCSI devices are specified by an OpenBOOT devalias which provides simple mnemonics for the full path to the device. Type devalias in OpenBoot PROM 2 to get a list of all of the available aliases. Just the alias and par- tition are necessary when booting. Therefore, to boot from the swap partition on the internal hard drive (OpenBoot PROM 2 assumes the internal hard drive is at target 3), one would use: ok boot disk:b To boot from a CD-ROM (OpenBoot PROM 2 assumes the CD-ROM is at target 6), one would use: ok boot cdrom And, to boot from a kernel named netbsd-GENERIC on the fourth partition ( `d', often the /usr partition) on an external hard drive (target 2, partition 3), one would use: ok boot disk2:d netbsd-GENERIC The full device path specifier for OpenBoot PROM 2 depends on how OpenBoot PROM 2 recognizes your SCSI controller. Typically, one would use something like: /sbus/esp/sd@t,p where t is the SCSI target and p is the partition number. Determining how to boot from an SBUS card Some SBUS cards have firmware that lets you use them as a boot device. These cards do not automatically create a devalias entry, so you must traverse the device tree to figure out what the OpenBoot PROM calls your card. You will be using OpenBoot PROM commands at the `ok' prompt. First `cd' to the top of the device tree and list the nodes there. The following is the procedure to boot from an HME card in a SPARC Classic. ok cd / ok ls ffd3b790 TI,TMS390S10@0,f8fffffc ffd2d254 virtual-memory@0,0 ffd2d198 memory@0,0 ffd2b65c obio ffd2b310 iommu@0,10000000 ffd2b2a0 openprom ffd24af0 aliases ffd24abc options ffd24a88 packages Usually, you can simply type in the name before the at (@) sign and the OpenBoot PROM will fill in the rest. ok cd iommu ok ls ffd2b454 sbus@0,10001000 ok cd sbus ok ls ffd467e8 cgthree@3,0 ffd42a1c SUNW,hme@1,8c00000 ffd4297c le@0,c00000 ffd40d28 ledma@4,8400010 ffd40c9c SUNW,bpp@4,c800000 ffd40c00 audio@4,1300000 ffd3dc68 espdma@4,8400000 ok cd SUNW,hme ok ls ok pwd /iommu@0,10000000/sbus@0,10001000/SUNW,hme@1,8c00000 OK, now we know the path to the HME device in this example. Now, we need to determine if it's capable of booting. If it is, it will have the word `open'. ok words reset seek load open close watch-net selftest obp-selftest write read preamble-32 enable-link-pulse disable-link-pulse force-speeds reset-transceiver use-bit-bang-mode use-frame-mode dump-phys transfer-speed=10 transfer-speed=100 mii-write mii-read create-rev-id Great! Also, in case you're interested in further details about your hardware, you can use the `.attributes' command. ok .attributes hm-rev 00000022 version 1.18 model SUNW,501-2919 device_type network intr 00000037 00000000 interrupts 00000004 address-bits 00000030 max-frame-size 00004000 reg 00000001 08c00000 00000108 00000001 08c02000 00002000 00000001 08c04000 00002000 00000001 08c06000 00002000 00000001 08c07000 00000020 name SUNW,hme ok So, when it's time to type in a boot command, use the shortened version of the pwd command. In this example, you'd type: ok boot /iommu/sbus/SUNW,hme And when the kernel is done booting, it may not automatically use your card as the root device -- you may need to type in the NetBSD/sparc name for that device: root on sd0a dumps on sd0b no file system for sd0 (dev 0x700) cannot mount root, error = 79 root device (default sd0a): ? use one of: fd0[a-h] le0 le1 hme0 sd0[a-h] halt root device (default sd0a): hme0 dump device: hme0 file system (default generic): nfs root on hme0 Deciding on partition sizes If you're installing NetBSD/sparc for the first time it's a good idea to look at the partition sizes of disk you intend installing NetBSD/sparc on. Assuming a classic partition scheme with / (root) and /usr file systems, a comfortable size for the NetBSD root file system partition is about 20 MB; a good initial size for the swap par- tition is twice the amount of physical memory in your machine (though, unlike SunOS 4.x, there are no restrictions on the size of the swap partition that would render part of your mem- ory unusable). A full binary installation takes about 275 MB in /usr. Most sparc systems have trouble booting if the root partition extends beyond the first 2 GB of your disk. Configuration of network interfaces Some network devices (i.e. the built-in le interface on sun4m machines) allow a choice between operating on a UTP or a AUI port once the NetBSD kernel is running. The le driver supports automatic detection of the port which is actually connected to the wire. Additionally, some of the Fast ethernet devices (such as be, hme, qec, and qfe) support selection of various speeds and options. The default is to attempt to automatically detect the speed. If automatic detection is not available or not working properly in your environment, you may have to specify the type connec- tion using the media parameter of ifconfig(8). During instal- lation, you'll get the opportunity to specify the appropriate medium. Use 10base5 or AUI to select the AUI connector, or 10baseT or UTP to select the UTP connector. Fast ethernet interfaces default to auto, which usually does not detect prop- erly and runs at `10BaseT' speed. The options are 10baseT, 10baseTX, and auto. The hme and qfe interfaces also allow 10baseT-FDX and 100baseT-FDX. Installing the NetBSD System Installing NetBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. There are several ways to install NetBSD onto your system. The easiest way is to use the miniroot.fs image copied to your local disk's swap partition or a scratch drive. If your Sparc is hooked up in a network, you may configure another UNIX -like machine as a netboot server for your Sparc. Alternatively, there is a pair of floppy images that will boot your system and run the installer. For more information on the commands and variables available in the OpenBoot PROM (present in all sun4c and sun4m machines), go to http://docs.sun.com and search for ``openboot reference'' (without quotes). Installing NetBSD by placing a bootable file system on a partitioned hard drive installation/miniroot/miniroot.fs.gz is a compressed, self-con- tained NetBSD file system holding all utilities necessary to install NetBSD onto a disk attached to your system. It is dis- tributed as a compressed plain file you will transfer to a raw disk partition. You will then boot this installer using the appropriate PROM command. The simplest case is where you place the miniroot.fs file system on the swap partition of your disk. Alternatively, you can place it on any other unused partition on any disk (such as a Zip disk). Be forewarned that you will not be able to install NetBSD onto the partition that contains the miniroot.fs as this partition is needed during the install process. Loading the file system onto a raw partition is straightfor- ward. First, download miniroot.fs to your system. Next, reboot in single-user mode (i.e. boot -s) to ensure that your system will not be swapping. Finally, place the miniroot.fs on your partition of choice. On NetBSD or SunOS the commands are: # gunzip miniroot.fs.gz # dd if=miniroot.fs of=/dev/rsd0b bs=4k conv=sync Here, /dev/rsd0b is assumed to be your swap partition. If you decide to place miniroot.fs on a non-swap partition, it will overwrite all of the contents of that partition, but you will not need to reboot into single-user mode to write it. After transferring the file system to disk, bring the system down by: # halt Then boot the installer by typing the appropriate command at the PROM prompt (this example is for the swap partition): sunmon b sd(,,1)netbsd -s OpenBoot PROM 1 ok boot sd(,,1)netbsd -s OpenBoot PROM 2 ok boot disk:b netbsd -s The monitor boot command will load the NetBSD kernel contained in the file system image. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below. Installing NetBSD by using a bootable CD-ROM If you wish to burn a CD-R containing a bootable NetBSD instal- lation, then you can either burn the prepared disk image in installation/cdrom/netbsd-sparc.iso or create your own. If you wish to create your own, you should follow the directions on the NetBSD Bootable CD-ROM HOW-TO at: http://www.NetBSD.org/Documentation/bootcd.html#sparcimage Once you have downloaded netbsd-sparc.iso or created your own disk image, then you need to burn it to a CD-R. The CD-ROM attached to your Sparc must support 512 byte sectors to be bootable. All Sun brand CD-ROMs will work, as well as many other manufacturers. See the Sun CD-ROM FAQ: http://saturn.tlug.org/suncdfaq/ Sun sets their CD-ROM drives to SCSI ID 6. We recommend you do the same. Boot the installer by typing the appropriate command at the PROM prompt: sunmon b sd(,30,) OpenBoot PROM 1 ok boot sd(,30,) OpenBoot PROM 2 ok boot cdrom After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below. Installing NetBSD by using the bootable floppies The NetBSD install floppies only work on the sun4c and sun4m machines. Making the install floppies is fairly straightfor- ward. NetBSD and SunOS use the same commands. First, get two 1.44 MB floppy disks and format them either using the fdformat(8) com- mand or a PC. # fdformat Be sure that the `fdformat' command completes successfully before proceeding; on NetBSD success is a string of all `V 's', and on SunOS success is a string of `. 's'. Next, transfer the two floppy images (installation/floppy/disk1.gz and installation/floppy/disk2) to the disks you just formatted. You can do this step from NetBSD, SunOS, or a Windows machine using rawrite.exe (avail- able in the NetBSD/i386 distribution). Insert the first floppy and run the following commands: # gunzip disk1.gz # dd if=disk1 of=/dev/rfd0a bs=36k # eject floppy Insert the second floppy and run the following commands: # dd if=disk2 of=/dev/rfd0a bs=36k conv=sync # eject floppy Note that disk2 may be a symlink to .tgz file; do not uncom- press it, just follow the instructions above, verbatim. After writing the two floppies, be sure to label them so you can later identify them. Insert the floppy made from disk1 into your Sparc. From the OpenBoot prompt, boot the floppy with the following command: OpenBoot PROM 1 ok boot fd(,,1) OpenBoot PROM 1 (alternate) ok boot /fd OpenBoot PROM 2 ok boot floppy After the initial probe messages you'll be asked to insert the floppy labeled ``NetBSD disk2''. If the floppy is not automat- ically ejected, you can either use a straightened paperclip to eject the disk or do the following: Press the STOP key (sometimes called the L1 key, found on the left side of your keyboard) and the a key, which will halt your system and give you a PROM prompt. ok eject ok go Now, insert the floppy labeled disk2. After the installation tools have been loaded, you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below. Installing NetBSD by using a netboot setup 1. Introduction To netboot a sparc, you must configure one or more servers to provide information and files to your sparc (the `client ).' If you are using NetBSD (any architecture) on your netboot server(s), the information provided here should be sufficient to configure everything. Addition- ally, you may wish to look at the diskless(8) manual page and the manual pages for each daemon you'll be configur- ing. If the server(s) are another operating system, you should consult the NetBSD Diskless HOW-TO, which will walk you through the steps necessary to configure the netboot services on a variety of platforms. http://www.NetBSD.org/Documentation/network/netboot/ You may either netboot the installer so you can install onto a locally attached disk, or you may run your system entirely over the network. Briefly, the netboot process involves discovery, boot- strap, 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 containing the kernel. Once the kernel is loaded, it starts executing. For RAM disk kernels, it mounts the RAM disk file system and begins executing the installer from the RAM disk. For normal (non-RAM disk) kernels, the kernel tries to mount the NFS share that had the kernel and starts executing the installation tools or init(8). All sparc systems except JavaStations with OpenFirmware PROM use a combination of RARP and BOOTP for the discovery stage. In the past, these systems used RARP and BOOT- PARAMS. JavaStations booting from OpenFirmware use DHCP. TFTP is used in the bootstrap phase to download the boot- strap program, boot.net, which has been linked to a file name appropriate to the client's architecture and IP address as described in the TFTP section below. JavaSta- tions with OpenFirmware need a special bootstrap program, bootjs.net, which is a version of boot.net in ELF format. It is not linked to the IP address. 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 (ether- net hardware 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 ser- vices on one machine called `server.test.net' with the client's files exported from the directory /export/client/root. You should, of course, replace all of these with the names, addresses, and paths appropriate to your environment. You should set up each netboot stage in order (i.e. dis- covery, bootstrap, kernel, and then file system) so that you can test them as you proceed. 2. dhcpd(8) in bootpd(8) compatible mode Put the following lines in your /etc/dhcpd.conf (see dhcpd.conf(5) and dhcp-options(5) for more information): ddns-update-style none; # Do not use any dynamic DNS features # allow bootp; # Allow bootp requests, thus the dhcp server # will act as a bootp server. # authoritative; # master DHCP server for this subnet # subnet 192.168.1.0 netmask 255.255.255.0 { # Which network interface to listen on. # The zeros indicate the range of addresses # that are allowed to connect. } group { # Set of parameters common to all clients # in this "group". # option broadcast-address 192.168.1.255; option domain-name "test.net"; option domain-name-servers dns.test.net; option routers router.test.net; option subnet-mask 255.255.255.0; # # An individual client. # host client.test.net { hardware ethernet CC:CC:CC:CC:CC:CC; fixed-address 192.168.1.10; # # Name of the host (if the fixed address # doesn't resolve to a simple name). # option host-name "client"; # # Name of the bootloader or kernel # to download via tftp. # # Only needed for JavaStations with OpenFirmware! # filename "bootjs.net"; # # The path on the NFS server. # option root-path "/export/client/root"; # # If your DHCP server is not your NFS server, supply the # address of the NFS server. Since we assume you run everything # on one server, this is not needed. # # next-server server.test.net; } #you may paste another "host" entry here for additional #clients on this network } Note that for JavaStations booting from OpenFirmware you do not need the allow bootp; statement, since this machines use real DHCP. 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 run- ning, 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. rarpd(8) Note: no rarpd is needed to boot OpenFirmware based JavaS- tations. Create an /etc/ethers file with the following line: CC:CC:CC:CC:CC:CC client Add your client to the server's /etc/hosts file: 192.168.1.10 client You will need to start the rarpd. If it's already run- ning, 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/rarpd restart 4. tftpd(8) The default configuration of the TFTP server is to run in a chroot(8) environment in the /tftpboot directory. Thus, the first order of business is to create this directory: # mkdir -p /tftpboot Next, edit /etc/inetd.conf and uncomment the line with the TFTP daemon: tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /tftpboot Now, restart inetd(8). If the server is running NetBSD, you can achieve this with: # /etc/rc.d/inetd restart Now, you need to copy the bootloader for your sparc machine to /tftpboot. Get boot.net from the installation/netboot directory of the distribution. # cp boot.net /tftpboot Now, you need to link boot.net to the filename that your sparc will look for. It will look for a filename composed of the machine's IP address (in hexadecimal) followed by the machine's architecture, separated by a period. For example, a sun4c machine which has been assigned IP address 192.168.1.10, will make a TFTP request for C0A8010A.SUN4C. You can use bc(1) to help calculate the filename: # bc obase=16 192 C0 168 A8 1 1 10 A quit # cd /tftpboot # ln -s boot.net C0A8010A.SUN4C For OpenFirmware based JavaStations you use the file bootjs.net and do not create a symlink for the IP address. This machines do full DHCP autoconfiguration, so the boot- strap filename is provided by the DHCP server. 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 5. nfsd(8), mountd(8), and rpcbind(8) Now your system should be able to load the bootstrap pro- gram 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 shar- ing: /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 6. NetBSD kernel and installation tools 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 If you are netbooting the installer, copy the distribution files to the client's root directory and extract the tools from installation/netboot/rootfs.tgz. # cp *tgz /export/client/root # cd /export/client/root # tar -xpzf rootfs.tgz 7. Client file system You can skip this step if you do not plan to run your client diskless after installation. Otherwise, you need to extract and set up the client's installation of NetBSD. The Diskless HOW-TO describes how to provide better secu- rity and save space on the NFS server over the procedure listed here. http://www.NetBSD.org/Documentation/network/netboot/nfs.html - Extracting distribution sets # cd /export/client/root # tar -xpzf /path/to/files/base.tgz # tar -xpzf /path/to/files/etc.tgz Continue with the other non-essential distribution sets if desired. - Set up swap # mkdir /export/client/root/swap # dd if=/dev/zero of=/export/client/swap bs=4k count=4k # echo '/export/client/swap -maproot=root:wheel client.test.net' | cat /etc/exports # /etc/rc.d/mountd restart This creates a 16 MB swap file and exports it to the client. - Create device nodes # cd /export/client/root/dev # ./MAKEDEV all This procedure only works on NetBSD hosts. - Set up the client's fstab(5) Create a file in /export/client/root/etc/fstab with the following lines: server:/export/client/swap none swap sw,nfsmntpt=/swap server:/export/client/root / nfs rw 0 0 - Set up the client's rc.conf(5) Edit /export/client/root/etc/rc.conf rc_configured=YES hostname="client" defaultroute="192.168.1.1" nfs_client=YES auto_ifconfig=NO net_interfaces="" Make sure rc does not reconfigure the network device since it will lose its connection to the NFS server with your root file system. - Set up the client's hosts(5) file. Edit /export/client/root/etc/hosts ::1 localhost 127.0.0.1 localhost 192.168.1.10 client.test.net client 192.168.1.5 server.test.net server 8. Setting up the server daemons If you want these services to start up every time you boot your server, make sure the following lines are present in your /etc/rc.conf: dhcpd=YES dhcpd_flags="-q" rarpd=YES rarpd_flags="-a" 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. Now, netboot your Sparc from the server by entering the appro- priate boot command at the monitor prompt. Depending on the PROM version in your machine, this command takes one of the following forms: sunmon b le()netbsd OpenBoot PROM 1 ok b le()netbsd OpenBoot PROM 2 ok boot net netbsd After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section Running the installation scripts. below. Installing NetBSD by using a bootable tape Sun sets their tape drives to SCSI ID 4. We recommend you do the same. Get the tape images (installation/tape/tapefile1.gz and installation/tape/tapefile2) and transfer them to a tape. Make sure you use the `no rewind scsi tape' device. Run the follow- ing commands: # gunzip tapefile1.gz # mt -f /dev/nrst0 rew # dd if=tapefile1 of=/dev/nrst0 bs=4k # dd if=tapefile2 of=/dev/nrst0 bs=4k Now you can transfer the NetBSD 3.0.3. distribution sets from (binary/sets) to the tape by using a series of additional # dd if=aset.tgz of=/dev/nrst0 bs=4k commands. See also the section Getting the NetBSD System on to Useful Media. Be sure to mark the location of these files on the tape; you'll need them during the installation procedure. Insert the tape into your Sparc's tapestation. Boot the installer by typing the appropriate command at the PROM prompt: sunmon b st() OpenBoot PROM 1 ok boot st() OpenBoot PROM 2 ok boot tape After the initial probe messages you'll be asked to confirm the tape device and tape file number containing the installation tools. Then, proceed to the section Running the installation scripts. below. Running the installation scripts The first thing that the installation scripts will inquire about is the type of console you're using on your machine. If you're using a Sun frame buffer display, choose the terminal type sun (this is presented as the default). Note: if your frame buffer device is a cgsix Sbus board, you should change the terminal type to sun-cgsix to avoid triggering a bug in the board's firmware code that can garble your screen. If you're using a terminal device connected to a serial port, choose a terminal type appropriate for that device, e.g. vt100 or vt200. Next, you will be presented with a choice of two installation methods: a new full-screen sysinst program, or the traditional script-based miniroot program. The sysinst program is easier to use, but the miniroot program is more flexible. Both of these installation methods will follow the same set of proce- dures and will fully install NetBSD on your Sparc. You will frequently be asked for confirmation before the system proceeds with each phase of the installation process. Occasionally, you will have to provide a piece of information such as the name of the disk you want to install on, partition- ing information, or IP addresses and domain names you want to assign. If your system has more than one disk, you may want to look at the output of the dmesg(8) command to see how your disks have been identified by the kernel. Note: If you repartition a hard drive, be certain that every partition starts on a cylinder boundary for compatibil- ity with the Sparc ROM. The installation script goes through the following phases: - determination of the disk on which to install NetBSD - checking/creation of the partition information on the disk - creating and mounting the NetBSD file systems - setup of network configuration - extraction of the distribution tar files - installation of bootstrap programs Now try a reboot. Initially we'd suggest you boot sd()netbsd -bs, then try multiuser after that. If you boot single-user the NetBSD incantation to make the root file system writable is # mount -u /dev/sd0a / Your PROM might have been setup to instruct the boot program to load a file called vmunix. On OpenBoot PROM systems you can change it to load netbsd instead using the following commands: OpenBoot PROM 1 ok setenv boot-from sd(0,0,0)netbsd OpenBoot PROM 2 ok setenv boot-file netbsd ok setenv boot-device disk:a Congratulations, you have successfully installed NetBSD 3.0.3. 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 prop- erly configured state, with the most important ones described below. 1. Configuring /etc/rc.conf If you or the installation software haven't done any con- figuration 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 system asks you to choose a shell, simply press RETURN to get to a /bin/sh prompt. If you are asked for a termi- nal type, respond with sun for a local console, or what- ever is appropriate for your serial console (some systems display garbage with a sun terminal type, you may need to use sun-ss5) 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 follow- ing: # mount /usr # export TERM=sun 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 con- tinue with the multi-user boot. Other values that need to be set in /etc/rc.conf for a networked environment are hostname and possibly defaultroute, furthermore add an ifconfig_int for your network interface, along the lines of ifconfig_le0="inet 123.45.67.89 netmask 255.255.255.0" or, if you have myname.my.dom in /etc/hosts: ifconfig_le0="inet myname.my.dom netmask 255.255.255.0" To enable proper hostname resolution, you will also want to add an /etc/resolv.conf file or (if you are feeling a little more adventurous) run named(8). See resolv.conf(5) or named(8) for more information. 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 set- ting up include /etc/mailer.conf, /etc/nsswitch.conf, and /etc/wscons.conf. 2. Select the proper terminal devices If you are using a serial console, you will have to edit the /etc/ttys file and change sun to the appropriate ter- minal type, such as vt220. 3. 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 ini- tial password. 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. 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? [...]. 4. 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. 5. 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 bina- ries. 6. Installing third party packages If you wish to install any of the software freely avail- able 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 installa- tion (and deinstallation), both from source and precom- piled binaries. - More information on the package system is at http://www.NetBSD.org/Documentation/software/packages.html - A list of available packages suitable for browsing is at ftp://ftp.NetBSD.org/pub/NetBSD/packages/pkgsrc/README.html - Precompiled binaries can be found at ,: ftp://ftp.NetBSD.org/pub/NetBSD/packages/ usually in the 3.0.3/sparc/All subdir. You can install them with the following commands under sh(1): # PKG_PATH=ftp://ftp.NetBSD.org/pub/NetBSD/packages/3.0.3/sparc/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 mozilla ... 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/3.0.3/sparc/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 Mozilla web browser as well as all the packages they depend on. - Package sources for compiling packages on your own can be obtained by retrieving the file ftp://ftp.NetBSD.org/pub/NetBSD/NetBSD-current/tar_files/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 information. 7. Misc - Edit /etc/mail/aliases to forward root mail to the right place. Don't forget to run newaliases(1) after- wards. - The /etc/mail/sendmail.cf file will almost definitely need to be adjusted; files aiding in this can be found in /usr/share/sendmail. See the README file there for more information. If you prefer postfix as MTA, adjust /etc/mailer.conf. - Edit /etc/rc.local to run any local daemons you use. - Many of the /etc files are documented in section 5 of the manual; so just invoking # man 5 filename is likely to give you more information on these files. Upgrading a previously-installed NetBSD System The upgrade to NetBSD 3.0.3 is a binary upgrade; it can be quite difficult to update the system from an earlier version by recompiling from source, primarily due to interdependencies in the various components. To do the upgrade, you must boot from the installer kernel using one of the methods described above. You must also have at least the base and kern binary distribution sets available, so that you can upgrade with them, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since files already installed on the system are overwritten in place, you only need additional free space for files which weren't previ- ously installed or to account for growth of the sets between releases. 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 kernel, the boot blocks on your NetBSD partition, 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 the NetBSD partition or on another operating system's partition on your disk before begin- ning the upgrade process. The upgrade procedure using the sysinst tool is similar to an installation, but without the hard disk partitioning. sysinst will attempt to merge the settings stored in your /etc direc- tory with the new version of NetBSD. Getting the binary sets is done in the same manner as the installation procedure; refer to the installation part of the document for how to do this. Also, some sanity checks are done, i.e. file systems are checked before unpacking the sets. After a new kernel has been copied to your hard disk, your machine is a complete NetBSD 3.0.3 system. However, that doesn't mean that you're finished with the upgrade process. You will probably want to update the set of device nodes you have in /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 Finally, you will want to delete old binaries that were part of the version of NetBSD that you upgraded from and have since been removed from the NetBSD distribution. NetBSD/sparc has switched its executable format from the old a.out format to ELF, the now more commonly used and supported format. Your old binaries will continue to work just fine. The installation procedure will try to take the necessary steps to accomplish this. The most important step is to move the old a.out shared libraries in /usr/lib and /usr/X11R6/lib (if X was installed) to /emul/aout, where they will be automatically found if an older a.out binary is executed. sysinst will use an existing /emul and / or /emul/aout directory if available, and will create it (as a symbolic link to /usr/aout) if neces- sary. If you already had a /emul directory, or a symbolic link by that name, sysinst should rename it and tell you about it. The network bootstrap /usr/mdec/boot.net and GENERIC and INSTALL kernels now try DHCP/BOOTP before falling back to boot- params. 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 3.0.3. Issues affecting an upgrade from NetBSD 2.1 and older releases. It is very important that you populate the directory /etc/pam.d with appropriate configuration files for the Pluggable Authen- tication 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/guide/en/chap-pam.html for documentation about PAM. The following issues can generally be resolved by extracting the etc set into a temporary directory and running postinstall: postinstall -s /path/to/etc.tgz check postinstall -s /path/to/etc.tgz fix Issues fixed by postinstall: - Various files in /etc need upgrading. These include: o /etc/defaults/* o /etc/mtree/* o /etc/pam.d/* o /etc/daily o /etc/weekly o /etc/monthly o /etc/security o /etc/rc.subr o /etc/rc o /etc/rc.shutdown o /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. 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 sec- tion 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 section 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 logging 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 avail- able via the mailing list server at majordomo@NetBSD.org. To get help on using the mail- ing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions 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 dis- cuss 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 mate- rial 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, including (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 inter- face to the NetBSD source tree. o The Helsinki University of Technology in Finland for hosting the NetBSD backup CVS and backup server. o SSH Communications Security in Finland for oper- ating the backup server. 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 The following individuals and organizations (each in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: AMD - Advanced Micro Devices, Inc. ASA Computers Aaron Wall ABE Masayuki AboveNet Communications, Inc. Achim Grolms Adam Kasper Adaptec Advanced System Products, Inc. Akihiro IIJIMA Alex Poylisher Algorithmics, Ltd. Alistair Crooks Allegro Networks Aloys Keller Andreas Berg Andreas Jellinghaus Andrew Brown Andrew Gillham Andy Hagans Antonio Larripa Arend Harrewijne Armijn Hemel Atsushi YOKOYAMA Avalon Computer Systems Bay Area Internet Solutions Ben Collver Benoit Lepage Bernhard Moellemann Bill Coldwell Bill Sommerfeld Bill Squier Brad Salai Brains Corporation, Japan Brian Carlstrom Brian McGroarty Brian Mitchell Canada Connect Corporation Carl Shapiro Castor Fu Central Iowa (Model) Railroad Charles Conn Charles D. Cranor Charles M. Hannum Chris Legrow Chris Townsend Christer O. Andersson Christopher G. Demetriou Christos Zoulas Chuck Silvers Cologne Chip AG Computer und Literatur Verlag Computertechnik Krienke & Nolte Computing Services Department, The University of Liverpool Convert Tools Co-operative Research Centre for Enterprise Distributed Curt Sampson DAYOMON from Japan Damicon Kraa, Finland Daniel de Kok Dave Burgess Dave Rand Dave Tyson David Brownlee Dayton Clark Demon Internet, UK Derek Fellion Digital Equipment Corporation Distributed Processing Technology Distro Jockey Douglas J. Trainor Dr.ir. F.W. Dillema Easynet, UK Ed Braaten Edward Richley emuty Eric and Rosemary Spahr Erik Berls Erik E. Fair Erkki Ruohtula Ernst Lehmann Espen Randen Ewald Kicker Florent Parent Frank Kardel Free Hardware Foundation Front Range *BSD User Group FUKAUMI Naoki Gan Uesli Starling Garth R. Patil Geert Hendrickx (ghen) Geert Jan de Groot GK Meier Gordon Zaft Grant Beattie Greg Gingerich Greg Girczyc Guenther Grau HP Sweden Hanno Wagner Hans Huebner Harald Koerfgen Haroon Khalid Harry McDonald Hauke Fath Heiko W. Rupp Herb Peyerl Hernani Marques Madeira Hidekichi Ookubo Hideyuki Kido Hisashi Fujinaka Holger Weiss Hubert Feyrer IBM Corporation IMAI Kiyoshi Innovation Development Enterprises of America Intel Internet Software Consortium Internet Users Forever IKI Interoute Telecommunications, UK JNUG (raised at JNUG meeting & BOF August 2005) James Bursa James Chacon Jan Joris Vereijken Jason Birnschein Jason Brazile Jason R. Thorpe Jeff Rizzo Jeff Woodall - Portland, OR Jens Schoenfeld Jim Wise Joachim Nink Joachim Thiemann Joel CARNAT John Heasley John Kohl John P. Refling Jonathan P. Kay Jordan K. Hubbard Jorgen Lundman Karl Wagner Kenji Hisazumi Kenneth Alan Hornstein Kenneth P. Stox Kevin Keith Woo Kevin Sullivan Klaus Lichti Kimmo Suominen Korea BSD User Forum Krister Waldfridsson Kwok Ng Lars Mathiassen Lehmanns Fachbochhandlung Lex Wennmacher LinuxFest Northwest Luke Maurits Luke Mewburn MS Macro System GmbH, Germany Maki Kato Marc Tooley Marcus Wyremblewski Mark Brinicombe Mark Houde Mark Perkins Mark S. Thomas Mason Loring Bliss Martin Cernohorsky Martin J. Ekendahl Matt Dainty Matt Thomas Matthew Jacob Matthew Sporleder Matthias Scheler Mattias Karlsson Mel Kravitz Michael Graff Michael "Kvedulv" Moll Michael L. Hitch Michael Richardson Michael Thompson Michael W. James Mike Price Mirko Thiesen (Thiesi) Murphy Software BV, Netherlands Neil J. McRae Noah M. Keiserman Norman R. McBride Numerical Aerospace Simulation Facility, NASA Ames Research Olaf "Rhialto" Seibert Oliver Cahagne Oppedahl & Larson LLP Palle Lyckegaard Paul Ripke Paul Southworth Pawel Rogocz Pearson Education Perry E. Metzger Petar Bogdanovic Peter C. Wallace Peter J. Bui Peter Postma Petri T. Koistinen Phil Thomas Piermont Information Systems Inc. Pierre-Philipp Braun Precedence Technologies Ltd Public Access Networks Corporation Ralph Campbell Randy Ray Real Weasel Reinoud Zandijk Renewed Health Company Richard Nelson Rob Windsor Robert Pankratz Robert Thille Roland Lichti Ross Harvey Ryan Campbell SDF Public Access Unix, Inc. 501(c)(7) SMC Networks Inc. Salient Systems Inc. Sander van Dijk Scott Ellis Scott Kaplan Scott Walters Sean Davis Simon Burge Soren Jacobsen Soren Jorvang Stephen Borrill Stephen Early Steve Allen Steve Wadlow Steven M. Bellovin SunROOT# Project Sylvain Schmitz Takahiro Kambe TAKEUCHI Yoji Tamotsu Kanoh Tasis Michalakopoulos (Athens, Greece) Tatoku Ogaito Ted Lemon Ted Spradley The Names Database The NetBSD Mission The People's Republic of Ames Thierry Lacoste Thierry Laronde Thomas Runge Thor Lancelot Simon Tim Law Timo Scholer Tino Hanich Tino Wildenhain Tom Coulter Tom Ivar Helbekkmo Tom Lyon Tomas Dabasinskas Torsten Harenberg Toru Nishimura Toshiba Turbocat's Development Tyler Sarna UTN Web Directory VMC Harald Frank, Germany Warped Communications, Inc. Wasabi Systems, Inc. Whitecross Database Systems Ltd. William Gnadt Worria Affordable Web Hosting Worria Web Hosting wwwTrace Traceroute Server Directory Yusuke Yokota Zach Metzinger (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 men- tioned, tell us!) We are... (in alphabetical order) The NetBSD core group: Allen Briggs briggs@NetBSD.org Matt Thomas matt@NetBSD.org Valeriy E. Ushakov uwe@NetBSD.org YAMAMOTO Takashi yamt@NetBSD.org Christos Zoulas christos@NetBSD.org The portmasters (and their ports): ~ Allen Briggs briggs@NetBSD.org sandpoint Anders Magnusson ragge@NetBSD.org vax Andrey Petrov petrov@NetBSD.org sparc64 Ben Harris bjh21@NetBSD.org acorn26 Chris Gilbert chris@NetBSD.org cats Christian Limpach cl@NetBSD.org xen Eduardo Horvath eeh@NetBSD.org evbppc Frank van der Linden fvdl@NetBSD.org amd64 Frank van der Linden fvdl@NetBSD.org i386 Gavan Fantom gavan@NetBSD.org iyonix IWAMOTO Toshihiro toshii@NetBSD.org hpcarm Ichiro Fukuhara ichiro@NetBSD.org hpcarm Ignatios Souvatzis is@NetBSD.org amiga Izumi Tsutsui tsutsui@NetBSD.org hp300 Izumi Tsutsui tsutsui@NetBSD.org news68k Jason Thorpe thorpej@NetBSD.org algor Jason Thorpe thorpej@NetBSD.org evbarm Jason Thorpe thorpej@NetBSD.org shark Jeremy Cooper jeremy@NetBSD.org sun3 Jonathan Stone jonathan@NetBSD.org pmax Julian Coleman jdc@NetBSD.org atari Jun-ichiro itojun Hagino itojun@NetBSD.org evbsh3 Jun-ichiro itojun Hagino itojun@NetBSD.org mmeye Kazuki Sakamoto sakamoto@NetBSD.org bebox Lennart Augustsson augustss@NetBSD.org pmppc Marcus Comstedt marcus@NetBSD.org dreamcast Martin Husemann martin@NetBSD.org sparc64 Matt DeBergalis deberg@NetBSD.org next68k Matt Fredette fredette@NetBSD.org hp700 Matt Fredette fredette@NetBSD.org sun2 Matt Thomas matt@NetBSD.org alpha Matt Thomas matt@NetBSD.org netwinder Matthias Drochner drochner@NetBSD.org cesfic NISHIMURA Takeshi nsmrtks@NetBSD.org x68k NONAKA Kimihiro nonaka@NetBSD.org prep Nathan Williams nathanw@NetBSD.org sun3 Noriyuki Soda soda@NetBSD.org arc Paul Kranenburg pk@NetBSD.org sparc Phil Nelson phil@NetBSD.org pc532 Reinoud Zandijk reinoud@NetBSD.org acorn32 Ross Harvey ross@NetBSD.org alpha Soren Jorvang soren@NetBSD.org cobalt Soren Jorvang soren@NetBSD.org sgimips Scott Reynolds scottr@NetBSD.org mac68k Shin Takemura takemura@NetBSD.org hpcmips Simon Burge simonb@NetBSD.org evbmips Simon Burge simonb@NetBSD.org evbppc Simon Burge simonb@NetBSD.org pmax Simon Burge simonb@NetBSD.org sbmips Steve Woodford scw@NetBSD.org evbsh5 Steve Woodford scw@NetBSD.org mvme68k Steve Woodford scw@NetBSD.org mvmeppc Tohru Nishimura nisimura@NetBSD.org luna68k Tsubai Masanari tsubai@NetBSD.org macppc Tsubai Masanari tsubai@NetBSD.org newsmips UCHIYAMA Yasushi uch@NetBSD.org hpcsh UCHIYAMA Yasushi uch@NetBSD.org playstation2 Wayne Knowles wdk@NetBSD.org mipsco Wolfgang Solfrank ws@NetBSD.org ofppc The NetBSD 3.0.3 Release Engineering team: Grant Beattie grant@NetBSD.org Erik Berls cyber@NetBSD.org James Chacon jmc@NetBSD.org Julian Coleman jdc@NetBSD.org Havard Eidnes he@NetBSD.org Jun-ichiro itojun Hagino itojun@NetBSD.org Geert Hendrickx ghen@NetBSD.org Soren Jacobsen snj@NetBSD.org SAITOH Masanobu msaitoh@NetBSD.org Luke Mewburn lukem@NetBSD.org Jeff Rizzo riz@NetBSD.org Matthias Scheler tron@NetBSD.org Curt Sampson cjs@NetBSD.org Jim Wise jwise@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 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 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 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 Johan Danielsson joda@NetBSD.org John Darrow jdarrow@NetBSD.org Jed Davis jld@NetBSD.org Matt DeBergalis deberg@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 Elad Efrat elad@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 Hubert Feyrer hubertf@NetBSD.org Jason R. Fink jrf@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 Adam Glass glass@NetBSD.org Michael Graff explorer@NetBSD.org Brian C. Grayson bgrayson@NetBSD.org Matthew Green mrg@NetBSD.org Andreas Gustafsson gson@NetBSD.org Jun-ichiro itojun Hagino itojun@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 Kouichirou Hiratsuka hira@NetBSD.org Michael L. Hitch mhitch@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 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 Martti Kuparinen martti@NetBSD.org Kentaro A. Kurahone kurahone@NetBSD.org Kevin Lahey kml@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 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 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 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 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 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 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 Nathan Williams nathanw@NetBSD.org Rob Windsor windsor@NetBSD.org Dan Winship danw@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 Legal Mumbo-Jumbo All product names mentioned herein are trademarks or registered trademarks of their respective owners. The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the Uni- versity 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 Weppelman. 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 Wep- pelman and Waldi Ravens. This product includes software developed by Mika Kortelainen This product includes software developed by Aaron Brown and Harvard University. This product includes software developed by Adam Cia- rcinski 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 Washington University. This product includes software developed by Charles D. Cranor, Washington University, and the University of California, Berkeley and its contributors. 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 Califor- nia, 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 Christo- pher G. Demetriou for the NetBSD Project. This product includes software developed by Christo- pher 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 Hux- ley. 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@@mincom.oz.au) This product includes software developed by Eric Young (eay@cryptsoft.com) This product includes software developed by Eric Young (eay@mincom.oz.au) This product includes software developed by Ezra Story and by Kari Mettinen. 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 Pey- erl. This product includes software developed by Hubert Feyrer for the NetBSD Project. This product includes software developed by Iain Hib- bert 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 Communications, 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 Bir- rell. This product includes software developed by John P. Wittkoski. This product includes software developed by John Pol- stra. 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 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, Berkeley and its con- tributors. This product includes software developed by LAN Media Corporation and its contributors. This product includes software developed by Leo Wep- pelman for the NetBSD Project. This product includes software developed by Leo Wep- pelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Luke Mew- burn. 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 Mur- ray 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 Kra- nenburg. 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 Har- vey for the NetBSD Project. This product includes software developed by Ross Har- vey. 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 contributors. 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 Cen- ter for Software Science at the University of Utah. This product includes software developed by the Charles D. Cranor, Washington University, University of California, Berkeley and its contributors. This product includes software developed by the Com- puter Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the David Muir Sharnoff. This product includes software developed by the Har- vard University and its contributors. This product includes software developed by the Kung- liga Tekniska Hogskolan and its contributors. This product includes software developed by the Net- work 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/) his product includes software developed by the Pock- etBSD 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 Development Group at Sun Microsystems, Inc. This product includes software developed by the Uni- versity of California, Berkeley and its contributors, as well as the Trustees of Columbia University. This product includes software developed by the Uni- versity of California, Lawrence Berkeley Laboratory and its contributors. This product includes software developed by the Uni- versity of California, Lawrence Berkeley Laboratory. This product includes software developed by the Uni- versity of Illinois at Urbana and their contributors. This product includes software developed by the Uni- versity of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed 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 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 Christos 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 Ignatios 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 Allegro 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 Piermont 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 educa- tion, including but not restricted to "NetBSD", "FreeBSD", "Mach" (by CMU). This software includes software developed by the Com- puter Systems Laboratory 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 the Alice Group. This product includes software developed by David Miller. The End NetBSD August 22, 2004 NetBSD