INSTALLATION NOTES for NetBSD/mvme68k 1.3 Be sure to read _ALL_ of this document before you try to install NetBSD/mvme68k. What is NetBSD? ---- -- ------ The NetBSD Operating System is a fully functional UN*X-like system derived from the Berkeley Networking Release 2 (Net/2), 4.4BSD-Lite, and 4.4BSD-Lite2 sources. NetBSD runs on many architectures and is being ported to more. 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 this release wouldn't have come about. The NetBSD 1.3 release is a landmark. Building upon the successful NetBSD 1.2 release, we have provided numerous and significant functional enhancements, including support for many new devices, integration of many bug fixes, new and updated kernel subsystems, and many userland enhancements. The results of these improvements is a stable operating system fit for production use that rivals most commercially available systems. It is impossible to summarize the 18 months of development that went into the NetBSD 1.3 release. Some of the significant changes include: Support for machine independent device drivers has been radically improved with the addition of the "bus.h" interface, providing a high quality abstraction for machine and architecture independent device access. The bus_dma interface has also been integrated, providing a machine-independent abstraction for DMA mapping. This permits many good things, including (among many) clean multi-platform bounce buffer support. Framework support for ISA "Plug and Play" has been added, as well as support for numerous "Plug and Play" devices. APM support has been added to NetBSD/i386. An initial cut of multi-platform PCMCIA support has been added. Support for ATAPI devices (initially just ATAPI CD-ROM drives) has been added. Support for Sun 3/80s (sun3x architecture) has been added. Support for R4000 DECstations has been added. Integration/merger of 4.4BSD Lite-2 sources into userland programs has nearly been completed. Most of userland now compiles with high levels of gcc warnings turned on, which has lead to the discovery and elimination of many bugs. The i386 boot blocks have been completely replaced with a new, libsa based two stage boot system. This has permitted integration of compressed boot support (see below). Many ports now support booting of compressed kernels, and feature new "Single Floppy" install systems that boot compressed install kernels and ramdisks. We intend to do substantial work on improving ease of installation in the future. "ypserv" has been added, thus completing our support for the "yp" network information system suite. Support for the Linux "ext2fs" filesystem and for FAT32 "msdosfs" filesystems has been added. TCP now has a SYN "compressed state engine" which provides increased robustness under high levels of received SYNs (as in the case of "SYN flood" attacks.) (Much of this code was derived from sources provided by BSDI.) An initial implementation of Path MTU discovery has been integrated (though it is not turned on by default). An initial kernel based random number generator pseudodevice has been added. Several major fixes have been integrated for the VM subsystem, including the fix of a notorious VM leak, improved synchronization between mmap()ed and open()ed files, and massively improved performance in low real memory conditions. A new swap subsystem has radically improved configuration and management of swap devices and adds swapping to files. Userland ntp support, including xntpd, has been integrated. The audio subsystems have been substantially debugged and improved, and now offer substantial emulation of the OSS audio interface, thus providing the ability to cleanly run emulated Linux and FreeBSD versions of sound intensive programs. A "packages" system has been adapted from FreeBSD and will provide binary package installations for third party applications. The XFree86 X source tree has been made a supported part of the NetBSD distribution, and X servers (if built for this port), libraries and utilities are now shipped with our releases. The ftp(1) program has been made astoundingly overfunctional. It supports command line editing, tab completion, status bars, automatic download of URLs specified on the command line, firewall support and many other features. All ports now use "new" config. Old config has been laid to rest. The ARP subsystem and API has been rewritten to make it less ethernet-centric. A new if_media subsystem has been added which allows network interfaces to be configured using media type names rather than device-specific mode bits. Many kernel interface manual pages have been added to manual section 9. Several ports support much more hardware. Many updates to bring NetBSD closer to standards compliance. Most third party packages have been updated to the latest stable release. As has been noted, there have also been innumerable bug fixes. Kernel interfaces have continued to be refined, and more subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.3 also includes some refinement to the NetBSD binary emulation system (which includes FreeBSD, HP-UX, iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility), bringing NetBSD closer to the goal of making the emulation as accurate as possible. In the near future, we hope to integrate a fully rewritten Virtual Memory subsystem, kernel threads, and SMP support. This is the fourth public release of NetBSD for the VME147. 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 computer 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: * providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. * providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. * providing a better position from which to undertake promotional activities. * periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and 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 will provide 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: ------- -- ------ NetBSD Mirror Site List The following sites mirror NetBSD as of Sep 22, 1997 If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. FTP mirrors ----------- Australia * ftp://ftp.au.netbsd.org/pub/NetBSD Brazil * ftp://ftp.ravel.ufrj.br/pub/NetBSD Germany * ftp://ftp.de.netbsd.org/pub/NetBSD * ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD Japan * ftp://netbsd.tohoku.ac.jp/NetBSD Netherlands * ftp://ftp.nl.netbsd.org/pub/comp/NetBSD Norway * ftp://ftp.ntnu.no/pub/NetBSD * ftp://skarven.itea.ntnu.no/pub/NetBSD Sweden * ftp://ftp.stacken.kth.se/pub/OS/NetBSD * ftp://ftp.sunet.se/pub/os/NetBSD UK * ftp://ftp.DOMINO.ORG/pub/NetBSD USA * ftp://ftp.netbsd.org/pub/NetBSD * ftp://ftp.cs.umn.edu/pub/NetBSD * ftp://ftp.cslab.vt.edu/pub/NetBSD * ftp://ftp.eecs.umich.edu/pub/NetBSD * ftp://ftp.iastate.edu/pub/netbsd * ftp://ftp.op.net/pub/NetBSD SUP mirrors ----------- Australia * ftp.au.netbsd.org Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup Germany * ftp.de.netbsd.org Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example Norway * skarven.itea.ntnu.no Instructions: Use this line as your sup file to get /usr/README.supinfo- skarven:current release=supinfo host=skarven.itea.ntnu.no use-rel-suffix backup delete old base=/usr prefix=/usr hostbase=/supmirror UK * ftp.domino.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup USA * sup.netbsd.org Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup * ftp.cs.umn.edu Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG AFS mirrors ----------- USA * ftp.iastate.edu AFS path: /afs/iastate.edu/public/ftp/pub/netbsd NetBSD 1.3 Release Contents: ------ --- ------- -------- The NetBSD 1.3 release is organized in the following way: .../NetBSD-1.3/ BUGS Known bugs list (incomplete and out of date). CHANGES Changes since NetBSD's last release (and before). LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.3 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (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 1.3 has a binary distribution. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (i.e. the `domestic' portion) that may be subject to export regulations of the United States. It is your responsibility to determine whether or not it is legal for you to export these portions and to act accordingly. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: secrsrc.tgz: This set contains the "domestic" sources. These sources may be subject to United States export regulations. [ 412K gzipped, 1.8M uncompressed ] gnusrc.tgz: This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 15.6M gzipped, 66.4M uncompressed ] syssrc.tgz: This set contains the sources to the NetBSD 1.3 kernel, config(8), and dbsym(8). [ 10.7M gzipped, 50.0M uncompressed ] sharesrc.tgz: 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. [ 2.9M gzipped, 11.1M uncompressed ] src.tgz: This set contains all of the NetBSD 1.3 sources which are not mentioned above. [ 13.9M gzipped, 60.7M uncompressed ] It is worth noting that unless all of the source distribution sets are installed (except the domestic set), you can't rebuild and install the system from scratch, straight out of the box. However, all that is required to rebuild the system in that case is a trivial modification to one Makefile. Most of the above source sets are located in the source/sets subdirectory of the distribution tree. The secrsrc.tgz set is contained in the source/security subdirectory. This set, which is available only to users in the United States and Canada, contains the sources normally found in /usr/src/domestic -- primarily kerberos and other cryptographic security related software. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) The source sets are distributed as compressed tar files. They may be unpacked into /usr/src with the command: cat set_name.tgz | gunzip | (cd /; tar xpf - ) The sets/Split/ and security/Split/ subdirectories contain split versions of the source sets for those users who need to load the source sets from floppy or otherwise need a split distribution. The split sets are are named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) The split distributions may be reassembled and extracted with "cat" as follows: cat set_name.?? | gunzip | (cd /; tar xpf - ) In each of the source distribution set directories, there is a file named "CKSUMS" which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the integrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. Checksums based on other algorithms may also be present -- see the release(7) man page for details. The mvme68k-specific portion of the NetBSD 1.3 release is found in the "mvme68k" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3/mvme68k/ INSTALL Installation notes; this file. installation/ Boot programs, a stand-alone RAMDISK kernel, and a miniroot filesystem image. see below. binary/ mvme68k binary distribution sets; see below. security/ mvme68k security distribution; see below. .../mvme68k/installation/ miniroot/ The miniroot filesystem image. netboot/ Two programs needed to boot a VME147 kernel over the network. tapeimage/ Tape boot programs, and a RAMDISK kernel. The NetBSD/mvme68k install distribution contains files that can be used to install NetBSD onto a completely "bare" VME147. The files in the "mvme68k/installation/*" directories are described below: miniroot.gz A gzipped copy of the miniroot filesystem. This image is to be un-gzipped and copied into the swap area of a disk. netbsd-rd.gz A gzipped copy of the "RAMDISK kernel" for installing the miniroot filesystem. stboot A tape boot-block, in the form required to allow 147-Bug to boot from tape. This is the first segment of a boot tape. bootst A copy of the tape boot program, used as the second segment of a boot tape. sboot A copy of the serial boot program. This is necessary if you don't have a tape drive, but you _do_ have another system which can act as a boot and NFS server. This is also useful if you are installing a diskless NetBSD/mvme68k system. netboot A copy of the network boot program. Used in conjunction with sboot to get your system booted over a network. These files can be used to make a boot tape suitable for installing NetBSD/mvme68k. These files can also be used to configure an NFS server to support installation "over the network". See the section "Getting the NetBSD System onto Useful Media" for instructions on either method. .../mvme68k/binary/sets The NetBSD/mvme68k binary distribution sets contain the binaries which comprise the NetBSD 1.3 release for the VME147. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets are as follows: base The NetBSD/mvme68k 1.3 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 minimally functional. It includes shared library support, and excludes everything described below. [ 9.2M gzipped, 26.5M uncompressed ] comp The NetBSD/mvme68k Compiler tools. All of the tools relating to C and C++. This set includes the system include files (/usr/include), the linker, the compiler tool chain, 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. [ 6.9M gzipped, 24.1M uncompressed ] etc This distribution set contains the system configuration files that reside in /etc and in several other places. This set MUST be installed if you are installing the system from scratch, but should NOT be used if you are upgrading. (If you are upgrading, it's recommended that you get a copy of this set and CAREFULLY upgrade your configuration files by hand.) [ 53K gzipped, 327K uncompressed ] games This set includes the games and their manual pages. [ 2.9M gzipped, 7.5M 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. [ 2.5K gzipped, 10.3M uncompressed ] misc This set includes the system dictionaries (which are rather large), the typesettable document set, and man pages for other architectures which happen to be installed from the source tree by default. [ 2.3M gzipped, 8.7M uncompressed ] text This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.0M gzipped, 3.9M uncompressed ] .../mvme68k/security/ The mvme68k security distribution set is named "secr" and can be found in the "mvme68k/security" subdirectory of the NetBSD 1.3 distribution tree. It contains executables which are built in the "src/domestic" portion of the NetBSD source tree. It can only be found on those sites which carry the complete NetBSD distribution and that can legally obtain it. (Remember, because of United States law, it may not be legal to distribute this set to locations outside of the United States and Canada.) [ 128K gzipped, 275K uncompressed ] .../mvme68k/kernel/ The mvme68k kernel directory contains a gzip'ed VME147 specific kernel image. This should be used when upgrading from a previous version of NetBSD. Before starting the upgrade, you should unzip and copy this kernel in place of your existing /netbsd image, then reboot. The mvme68k binary distribution sets are distributed as gzipped tar files. Each mvme68k binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. The instructions given for extracting the source sets work equally well for the binary sets, but it is worth noting that if you use that method, the files are extracted "below" the current directory. That is, if you want to extract the binaries "into" your system, i.e. replace the system binaries with them, you have to run the command: tar --unlink -zxvpf set.tar.gz from /. Note that the "--unlink" flag is very important! For best results, it is recommended that you follow the installation and/or upgrade procedures documented in this file. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/mvme68k 1.3 runs on Motorola MVME147 boards. The minimal configuration requires 4M of RAM and ~100MB of disk space. To install the entire system requires much more disk space (approx. 200MB additional space is necessary for full sources. Double that if you want to recompile it all!). To run X (clients only) or compile the system, more RAM is recommended. Good performance requires 8MB of RAM, or 16 MB when running the X Window System. Here is a table of recommended HD partition sizes for a full install: partition: advise needed root (/) 20M 12M user (/usr) 100M 80M swap (2 or 3 * RAM) 8M Anything else is up to you! Note that the mvme68k installation procedure uses a `miniroot' image which is placed into the swap area of the disk. The swap partition must be large enough to hold this miniroot image (> 6Mb). The following VME147 hardware is supported: Serial ports (RS232): built-in console, tty01, tty02 and tty03 Parallel port: On-board centronics style printer port Network interfaces: On-board Lance Ethernet (le) SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.) On-board wd33c93 SCSI bus interface chip (async only for now). Miscellaneous: Battery-backed real-time clock. VMEbus RAM cards. If it's not on this list, there is no support for it in this release. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: * Tape * NFS * CD-ROM * FTP Note that installing on a "bare" machine requires either a bootable tape drive or an ethernet and RS232 connection to a compatible NFS server. The procedure for transferring the distribution sets onto installation media depends on the type of media. Instructions for each type of media are given below. In order to create installation media, you will need all the files and subdirectories in these two directories: .../NetBSD-1.3/mvme68k/installation .../NetBSD-1.3/mvme68k/binary * Creating boot/install tapes: Installing from tape is the simplest method of all. This method uses two tapes, one containing a bootable ramdisk and miniroot, the other containing the installation sets. The boot tape is created as follows: --> cd .../NetBSD-1.3/mvme68k/installation --> set T = /dev/nrst0 --> mt -f $T rewind --> dd if=tapeimage/stboot of=$T --> dd if=tapeimage/bootst of=$T obs=8k conv=osync --> gzip -dc tapeimage/netbsd-rd.gz | dd of=$T obs=8k conv=osync --> gzip -dc miniroot/miniroot.gz | dd of=$T obs=8k conv=osync --> mt -f $T rewind The installation set tape is created as follows: --> cd .../NetBSD-1.3/mvme68k/binary/sets --> set T = /dev/nrst0 --> mt -f $T rewind --> foreach f (base etc comp games man misc text) --> gzip -d < $f.tgz | dd of=$T bs=8k --> end --> mt -f $T rewind If the tape does not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. Consult the tape- related manual pages on the system where the tapes are created for more details. * Boot/Install from NFS server: If your machine has a disk and network connection, but no tape drive, it may be convenient for you to install NetBSD over the network. This involves temporarily booting your machine over NFS, just long enough so you can initialize its disk. This method requires that you have access to an NFS server on your network so you can configure it to support diskless boot for your machine. Configuring the NFS server is normally a task for a system administrator, and is not trivial. If you are using a NetBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, consult the documentation that came with it (i.e. add_client(8) on SunOS). Booting a VME147 from ethernet is not possible without first downloading a small bootstrap program (sboot) via RS232. See the section entitiled "Installing from NFS" for details on how to accomplish this. sboot expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RARP It will look for a filename derived from the machine's IP address expressed in hexadecimal, with an extension of ".147". For example, a VME147 with IP address 130.115.144.11 will make an TFTP request for `8273900B.147'. Normally, this file is just a symbolic link to the NetBSD/mvme68k "netboot" program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). The netboot program may be found in the install directory of this distribution. The netboot program will query a bootparamd server to find the NFS server address and path name for its root, and then load a kernel from that location. The server should have a copy of the netbsd-rd kernel in the root area for your client (no other files are needed in the client root, although it might be a convenient place to put the uncompressed miniroot image) and /etc/bootparams on the server should have an entry for your client and its root directory. Note that you should rename the netbsd-rd kernel to just 'netbsd' in the client's root directory before trying to netboot the client. The client will need access to the miniroot image, which can be provided using NFS or remote shell. If using NFS, miniroot.gz should be expanded on the server, because doing so from the RAMDISK shell is not so easy. The unzipped miniroot takes about 6Mb of space. If you will be installing NetBSD on several clients, it may be useful to know that you can use a single NFS root for all the clients as long as they only use the netbsd-rd kernel. There will be no conflict between clients because the RAM-disk kernel will not use the NFS root. No swap file is needed; the RAM-disk kernel does not use that either. * Install/Upgrade from CD-ROM: This method requires that you boot from another device (i.e. tape or network, as described above). You may need to make a boot tape on another machine using the files provided on the CD-ROM. Once you have booted netbsd-rd (the RAMDISK kernel) and loaded the miniroot, you can load any of the distribution sets directly from the CD-ROM. The "install" program in the miniroot automates the work required to mount the CD-ROM and extract the files. * Install/Upgrade via FTP: This method requires that you boot from another device (i.e. tape or network, as described above). You may need to make a boot tape on another machine using the files in .../install (which you get via FTP). Once you have booted netbsd-rd (the RAM-disk kernel) and loaded the miniroot, you can load any of the distribution sets over the net using FTP. The "install" program in the miniroot automates the work required to configure the network interface and transfer the files. This method, of course, requires network access to an FTP server. This might be a local system, or it might even be ftp.NetBSD.ORG itself. If you wish to use ftp.NetBSD.ORG as your FTP file server, you may want to keep the following information handy: IP Address: ftp.NetBSD.ORG Login: anonymous Password: Server path: /pub/NetBSD/NetBSD-1.3/mvme68k/binary Note: if you're not using a nameserver duing installation, you might find 204.152.184.75 handy; it's the IP address of ftp.NetBSD.ORG as of January 3, 1997. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ mvme68k machines usually need little or no preparation before installing NetBSD, other than the usual, well advised precaution of BACKING UP ALL DATA on any attached storage devices. The following instructions should make your machine "NetBSD Ready". Power-up your VME147. You should have the "bug" prompt: COLD Start Onboard RAM start = $00000000, stop = $007FFFFF 147-Bug> Make sure the value for "stop" looks ok (if you've got 8MB you should have the same value as I do). Also make sure the clock is ticking: 147-Bug>time Sunday 12/21/29 16:25:14 147-Bug>time Sunday 12/21/29 16:25:15 147-Bug> Note that NetBSD bases it's year at 1968, and adds the year offset in the VME147's real-time clock to get the current year. So the '29' here equates to 1997. You may have to adjust your clock using the 'set' command to comply with NetBSD's requirements. Don't worry if the "Day of the week" is not correct, NetBSD doesn't use it. (Actually, Motorola have acknowledged a year 2000 bug whereby the day of the week doesn't get set correctly by the 147Bug PROM. IT DOES NOT AFFECT NETBSD!) Also make sure that your VME147's ethernet address is initialised to the correct value. You'll find the address on a label on the inside of the board's front panel. Enter the last five digits of the address using the 'lsad' command. To install successfully to a local SCSI disk, you need to ensure that 147Bug is aware of what targets are connected to the SCSI bus. This can be done by issueing the following command: --> 147-Bug> iot;t At this point, 147Bug will scan for any attached SCSI devices. After a short delay, a list of SCSI devices will be displayed. You will be asked if Bug should assign LUNs to SCSI ids, to which you should answer Y. You should also answer Y when asked if the information is to be saved to NVRAM. The following installation instructions will assume that your target SCSI disk drive appears at SCSI-id 0. If you have a tape drive, the instructions assume is is configured for SCSI-id 5. When the RAMDISK root boots, NetBSD will refer to these devices as 'sd0' and 'rst0' respectively. You may wish to note these down; you'll be using them a lot. :-) Installing the NetBSD System: ---------- --- ------ ------ Installing NetBSD is a relatively complex process, but if you have this document in hand it should not be too difficult. There are several ways to install NetBSD onto your disk. If your machine has a tape drive the easiest way is "Installing from tape" (details below). If your machine is on a network with a suitable NFS server, then "Installing from NFS" is the next best method. Otherwise, if you have another VME147 machine running NetBSD you can initialize the disk on that machine and then move the disk. * Installing from tape: Create the NetBSD/mvme68k 1.3 boot tape as described in the section entitled "Preparing a boot tape". Then, with the tape in the drive, type the following at the 147Bug prompt: --> 147-Bug> bo 5 As mentioned earlier, this assumes your tape is jumpered for SCSI-id 5. As the tape loads (which may take 20 to 30 seconds), you will see a series of status messages. It may be useful if you can capture these messages to a file, or a scrollable xterm window. In particular, you should make a note of the lines which describe the geometry of the SCSI disks detected by NetBSD. They are of the form: sd0 at scsibus0 targ 0 lun 0: SCSI1 0/direct fixed sd0: 148MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors The information of most interest is the number of sectors; here it's 304605. You will need this number when you come to create a disklabel for that drive. [ START OF STATUS MESSAGES ] RAM address from VMEbus = $00000000 Booting from: VME147, Controller 5, Device 0 Loading: Operating System Volume: NBSD IPL loaded at: $003F0000 >> BSD MVME147 tapeboot [$Revision: 1.2 $] 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997 steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . [ END OF STATUS MESSAGES ] Note that the exact text of the messages will vary depending on which MVME147 variant you're using. Finally, you will see the following "welcome" message: [ START OF WELCOME MESSAGE ] Welcome to the NetBSD/mvme68k RAMDISK root! This environment is designed to do only four things: 1: Partititon your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Make that partition bootable (using 'installboot') 4: Reboot (using the swap partition, i.e. /dev/sd0b). Copying the miniroot can be done several ways, allowing the source of the miniroot image to be on any of these: boot tape, NFS server, TFTP server, rsh server The easiest is loading from tape, which is done as follows: mt -f /dev/nrst0 rewind mt -f /dev/nrst0 fsf 3 dd bs=8k if=/dev/nrst0 of=/dev/rsd0b (For help with other methods, please see the install notes.) To reboot using the swap partition after running installboot, first use "halt", then at the Bug monitor prompt use a command like: bo 0,,b: To view this message again, type: cat /.welcome ssh: [ END OF WELCOME MESSAGE ] You must now create a disklabel on the disk you wish to use for the root filesystem. This will usually be 'sd0'. The disklabel is used by NetBSD to identify the starting block and size of each partition on the disk. Partitions are named 'sd0a', 'sd0b', 'sd0c' etc, up to 'sd0h'. The mvme68k port of NetBSD makes some assumptions about the first three partitions on a boot disk: sd0a The root filesystem. sd0b The swap partition. sd0c The whole disk. Also known as the Raw Partition. The 'Raw Partition' is special; NetBSD is able to use it even if the disk has no label. You should never create a filesystem on the Raw Partition, even on a non-boot disk. It is good practice to put /usr on a different partition than / (sd0a). So, the first available partition for /usr is 'sd0d'. Refer to the section entitled "NetBSD System Requirements and Supported Devices" for information on the recommended sizes of the /, /usr and swap partitions. You are not required to define any partitions beyond sd0d, but if you have a large disk drive, you might want to create several other partitions for filesystems such as /home or /usr/src. Note that at this time you are only required to partition the root/boot disk; you will get the opportunity to partition any other disks in your system from the main 'miniroot' installation program. To create the disklabel and partitions, use the 'edlabel' program, passing it the name of the Raw Partition of your root/boot disk. Note that '-->' at the start of a line in the following examples indicates you are being prompted to enter some information. Obviously, you won't see this when you run the program for real. --> ssh: edlabel /dev/rsd0c edlabel menu: print - display the current disk label modify - prompt for changes to the label write - write the new label to disk quit - terminate program edlabel> The program shows what commands it recognises; "print", "modify", "write" and "quit". It will accept the first letter of a command if you don't feel like typing each one in full. To start creating the basic partitions, you should enter 'm' (modify) at the edlabel prompt, then enter the letter corresponding to the first partition, 'a'. --> edlabel> m modify subcommands: @ : modify disk parameters a-h : modify partition s : standarize geometry q : quit this subcommand --> edlabel/modify> a a (root) 0 (0/00/00) 0 (0/00/00) unused --> start as or : 0 --> length as or : 38000 --> type: 4.2BSD edlabel/modify> When you enter the start and length of a partition, you can use either blocks or cylinder/track/sector notation. If this is the first time you've partitioned a disk for NetBSD, it's probably easiest to use block notation. The above example creates partition 'a', starting at block zero and with a size of 38000 blocks. Note that the usual size of a block is 512 bytes, so this creates a 19Mb partition. The 'type' of the partition should be "4.2BSD", otherwise you won't be able to create a filesystem on it. Next, create a swap partition (b). Note that the minimum size of this swap partition should be 8Mb, otherwise you won't be able to use a miniroot to complete the NetBSD installation! --> edlabel/modify> b b (swap) 0 (0/00/00) 0 (0/00/00) unused --> start as or : 38000 --> length as or : 32768 --> type: swap edlabel/modify> Here, we specify a value for 'start' such that the swap partition follows immediately after partition 'a', i.e. 38000. The length of the swap partition should be a multiple of the amount of RAM you have in your system. Here, I've chosen 32768, or 16Mb. The next available block on the drive is thus 38000 + 32768. We will use this to create partition 'd' for our /usr filesystem. (Note that for a busy system, or a system with more than 8Mb of RAM, you'll be better off with a 32 or 64Mb swap partition.) --> edlabel/modify> d d (user) 0 (0/00/00) 0 (0/00/00) unused --> start as or : 70768 --> length as or : 233837 --> type: 4.2BSD --> edlabel/modify> q edlabel> As you can see, I've chosen to assign the remainder of the disk to /usr. Since there are 304605 sectors on the example disk (did you remember to note down the number of sectors on your disk during boot?), and partition 'd' starts at sector 70768, a simple bit of arithmetic (304605 - 70768) gives 'd' a size of 233837. You now need to write this new disklabel, together with the partition details you've just entered, to disk. You might also try the 'p' command to view the partitions. Once written, you can quit back to ssh using 'q'. --> edlabel> p type_num: 4 sub_type: 0 type_name: SCSI disk pack_name: fictitious bytes/sector: 512 sectors/track: 35 tracks/cylinder: 9 cylinders: 967 sectors/cylinder: 315 partition start (c/t/s) nblks (c/t/s) type a (root) 0 (0/00/00) 38000 (120/05/25)* 4.2BSD b (swap) 38000 (120/05/25)* 32768 (104/00/08)* swap c (disk) 0 (0/00/00) 304605 (967/00/00) unused d (user) 70768 (224/05/33)* 233837 (742/03/02)* 4.2BSD --> edlabel> w --> edlabel> q ssh: Now that your disk's partitioned, you need to get the proper installation miniroot image onto it. The miniroot image is designed to be copied into the swap partition of your disk. This is a safe place which won't be overwritten by the installation procedure. From the ssh prompt, use the following commands to copy the miniroot image from tape to swap (b). --> ssh: mt -f /dev/nrst0 rewind --> ssh: mt -f /dev/nrst0 fsf 3 --> ssh: dd bs=8k if=/dev/nrst0 of=/dev/rsd0b The disk and the miniroot must now be made bootable using the 'installboot' command, To do this, issue the following commands: --> ssh: mount /dev/sd0b /mnt --> ssh: installboot /mnt/usr/mdec/bootsd /bootxx /dev/rsd0b --> ssh: umount /dev/sd0b You can now shutdown the system. --> ssh: halt signal 15 ssh: syncing disks... done unmounting /mnt (/dev/sd1b)... unmounting / (root_device)... halted --> 147-Bug>reset --> Reset Local SCSI Bus [Y,N] N? y --> Automatic reset of known SCSI Buses on RESET [Y,N] = Y? --> Cold/Warm Reset flag [C,W] = C? --> Execute Soft Reset [Y,N] N? y You should now reboot from that just installed miniroot. See the section entitled "Booting the miniroot" for details. * Installing from NFS: Before you can install from NFS, you must have already configured your NFS server to support your machine as a bootable client. Instructions for configuring the server are found in the section entitled "Getting the NetBSD System onto Useful Media" above. To get started, you need to download "sboot" into RAM (you will find 'sboot' in the "install" directory of the mvme68k distribution). You can either do that through the console line or through a 2nd serial connection. For example, a VME147 connected to a sun4/110 and accessed via "tip" can be loaded as follows: lo 0 ~Ccat sboot go 4000 Which will look like this: --> 147-Bug>lo 0 --> ~CLocal command? cat sboot away for 11 seconds ! --> 147-Bug>g 4000 Effective address: 00004000 sboot: serial line bootstrap program (&end = 6018) >>> Now, if you want to do it through serial line 1, then connect serial line one to a machine. At the "147-Bug> " prompt do this "tm 1". You should then login to whatever machine it is connected to. Then hit "^A" to escape to Bug. do "lo 1;x=cat sboot" ... then when that is done you can reconnect "tm 1" and logout. Then do "go 4000" and you've got ">>> " prompt of sboot. Once you've got the ">>> " prompt, you can boot the RAMDISK kernel from the server: --> >>> b le0: ethernet address: 8:0:3e:20:cb:87 My ip address is: 192.168.1.4 Server ip address is: 192.168.1.1 4800 Download was a success! Start @ 0x8000 ... >> BSD MVME147 netboot (via sboot) [$Revision: 1.2 $] device: le0 attached to 08:00:3e:20:cb:87 boot: client IP address: 192.168.1.4 boot: client name: soapy root addr=192.168.1.1 path=/export/soapy 578616+422344+55540+[46032+51284]=0x11a6e4 Start @ 0x8000 ... Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997 steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU real mem = 7237632 avail mem = 6381568 using 88 buffers containing 360448 bytes of memory mainbus0 (root) pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM . . After the boot program loads the RAMDISK kernel, you should see the welcome screen as shown in the "tape boot" section above. You now need to create a disklabel with partition information on the SCSI disk on which you intend to create your root filesystem. Follow the instructions in the previous section entitled "Installing from tape" to do this. (But stop short of the part which describes how to copy the miniroot from tape.) You must now configure the network interface before you can access the NFS server containing the miniroot image. For example the command: --> ssh: ifconfig le0 inet 192.168.1.4 up will bring up the network interface 'le0' with that address. The next step is to copy the miniroot from your server. This can be done using either NFS or remote shell. (In the examples that follow, the server has IP address 192.168.1.1) You may then need to add a default route if the server is on a different subnet: --> ssh: route add default 192.168.1.2 1 You can look at the route table using: --> ssh: route show Now mount the NFS filesystem containing the miniroot image: --> ssh: mount -r 192.168.1.1:/export/soapy /mnt The procedure is simpler if you have space for an expanded (not compressed) copy of the miniroot image. In that case: --> ssh: dd bs=8k if=/mnt/miniroot of=/dev/rsd0b Otherwise, you will need to use "zcat" to expand the miniroot image while copying. This is tricky because the "ssh" program (small shell) does not handle sh(1) pipeline syntax. Instead, you first run the reader in the background with its input set to /dev/pipe and then run the other program in the foreground with its output to /dev/pipe. The result looks like this: --> ssh: run -bg dd obs=8k if=/dev/pipe of=/dev/rsd0b --> ssh: run -o /dev/pipe zcat /mnt/install/miniroot.gz To load the miniroot using rsh to the server, you would use a pair of commands similar to the above. Here is another example: --> ssh: run -b dd obs=8k if=/dev/pipe of=/dev/rsd0b --> ssh: run -o /dev/pipe rsh 192.168.1.1 zcat miniroot.gz You must now make the disk bootable. Refer to the previous section on installing from tape, where it describes how to run 'installboot'. This is immediately following the part which explains how to copy the miniroot from tape. * Booting the miniroot: Assuming the miniroot is installed on partition 'b' of the disk with SCSI-id 0, then the 147Bug boot command is: 147-Bug> bo 0,,b: The command line parameters above are: 0 controller (usually zero) ,, bug argument separators b: tell the bootstrap code to boot from partition 'b' You should see a bunch of boot messages, followed by messages from the miniroot kernel just as you did when the RAMDISK kernel booted. You will then be prompted to enter the root device. Since the miniroot was booted from the swap partition, you should enter 'sd0b'. You will then be asked for the swap device and filesystem type. Just press return twice to accept the defaults. When asked to enter a terminal type, either accept the default, or use whatever the TERM environment variable is set to in the shell of your host system: vmel0 at vmechip0 boot device: sd0 --> root device (default sd0a): sd0b --> dump device (default sd0b): --> file system (default generic): root on sd0b dumps on sd0b mountroot: trying ffs... root file system type: ffs init: copying out path `/sbin/init' 11 erase ^H, werase ^W, kill ^U, intr ^C --> Terminal type? [vt100] Congratulations! The system should now be running the miniroot installation program. Miniroot install program: ------------------------ The miniroot's install program is very simple to use. It will guide you through the entire process, and is well automated. Additional improvements are planned for future releases. The miniroot's install program will: * Allow you to place disklabels on additional disks. The disk we are installing on should already have been partitioned using the RAMDISK kernel. Note that partition sizes and offsets are expressed in sectors. When you fill out the disklabel, you will need to specify partition types and filesystem parameters. If you're unsure what the these values should be, use the following defaults: fstype: 4.2BSD fsize: 1024 bsize: 4096 cpg: 16 If the partition will be a swap partition, use the following: fstype: swap fsize: 0 (or blank) bsize: 0 (or blank) cpg: 0 (or blank) Note that partition 'c' is special; it covers then entire disk and should not be assigned to a filesystem. The number of partitions is currently fixed at 8. * Create filesystems on target partitions. * Allow you to set up your system's network configuration. Remember to specify host names without the domain name appended to the end. For example use `foo' instead of `foo.bar.org'. If, during the process of configuring the network interfaces, you make a mistake, you will be able to re-configure that interface by simply selecting it for configuration again. * Mount target filesystems. You will be given the opportunity to manually edit the resulting /etc/fstab. * Extract binary sets from the media of your choice. * Copy configuration information gathered during the installation process to your root filesystem. * Make device nodes in your root filesystem. * Copy a new kernel onto your root partition. * Install a new boot block. * Check your filesystems for integrity. First-time installation on a system through a method other than the installation program is possible, but strongly discouraged. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ It is possible to easily upgrade your existing NetBSD/mvme68k system using the upgrade program in the miniroot. If you wish to upgrade your system by this method, simply select the `upgrade' option once the miniroot has booted. The upgrade program with then guide you through the procedure. The upgrade program will: * Enable the network based on your system's current network configuration. * Mount your existing filesystems. * Extract binary sets from the media of your choice. * Fixup your system's existing /etc/fstab, and if necessary, changing the occurrences of `ufs' to `ffs' and let you edit the resulting file. * Make new device nodes in your root filesystem. * Copy a new kernel onto your root partition. NOTE: the existing kernel WILL NOT be backed up; doing so would be pointless, since older kernels may not be capable of running NetBSD 1.3 executables. * Install a new boot block. * Check your filesystems for integrity. While using the miniroot's upgrade program is the preferred method of upgrading your system, it is possible to upgrade your system manually. To do this, follow the following procedure: * Place _at least_ the `base' binary set in a filesystem accessible to the target machine. A local filesystem is preferred, since the NFS subsystem in the NetBSD 1.3 kernel may be incompatible with your old binaries. * Back up your pre-existing kernel and copy the 1.3 kernel into your root partition. * Reboot with the 1.3 kernel into single-user mode. * Check all filesystems: /sbin/fsck -pf * Mount all local filesystems: /sbin/mount -a -t nonfs * If you keep /usr or /usr/share on an NFS server, you will want to mount those filesystems as well. To do this, you will need to enable the network: sh /etc/netstart * Run the update(8) daemon, to ensure that new programs are actually stored on disk. update * Make sure you are in the root filesystem and extract the `base' binary set: cd / tar --unlink -zxvpf /path/to/base.tgz NOTE: the `--unlink' option is _very_ important! * Delete system files in /sbin which now live in /usr/sbin: cd /sbin rm -f mountd rtquery quotacheck dumpfs dumplfs * Install a new boot block (you may need to be running in single-user mode to do this...): cd /usr/mdec cp bootsd /.bootsd ./installboot /.bootsd bootxx * Sync the filesystems: sync * At this point you may extract any other binary sets you may have placed on local filesystems, or you may wish to extract additional sets at a later time. To extract these sets, use the following commands: cd / tar --unlink -zxvpf NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, you should extract that set into another area and carefully merge the changes by hand. Compatibility Issues With Previous NetBSD Releases: ------------- ------ ---- -------- ------ -------- Users upgrading from previous versions of NetBSD may wish to bear the following problems and compatibility issues in mind when upgrading to NetBSD 1.3: * Swap configuration Description: All swap partitions are now configured by the swapctl(8) program. The kernel no longer configures a "default" swap partition. Because of this, all swap partitions (even the old "default") must be listed in /etc/fstab. Many users of previous releases relied on the kernel configuring a "default" swap partition and did not list any swap space in /etc/fstab at all -- such users will now have no swap space configured unless they list swap partitions in /etc/fstab! Common symptoms of of this problem include machine crashes during builds, and similar memory intensive activities. Fix: The most common position for a swap partition is the `b' partition of the drive the root file system is on. For diskless systems, check the new swapctl(8) manual for more detail on how this is done. Example fstab entries: /dev/sd0b none swap sw,priority=0 /dev/sd1b none swap sw,priority=5 * NFS daemons and other programs in /sbin moved Description: The NFS daemons (nfsd, nfsiod, mountd) have been moved from the /sbin to the /usr/sbin directory. When new binaries are loaded over old ones during upgrade, most programs get overlaid and replaced, but unless these binaries are explicitly removed they will not disappear. The installation subsystems on some NetBSD architectures will not properly remove these binaries. Due to changes in the NFS subsystem, the old NFS daemon binaries will not work correctly, and will cause serious problems. Unfortunately, the default startup script (/etc/rc) will run the old binaries in /sbin if they are present instead of the new ones in /usr/sbin. Some other programs (dumpfs, dumplfs and quotacheck) have also been moved from /sbin to /usr/sbin, and old versions may be left behind by accident. They, too, may cause difficulties. Fix: Remove the old daemon binaries (/sbin/nfsiod, /sbin/nfsd, /sbin/mountd, etc.) after your upgrade has finished. You may wish to do an "ls -lt /sbin | more" to help determine which binaries were not replaced/removed during your upgrade. * AMANDA, The Advanced Maryland Automatic Network Disk Archiver, from http://www.amanda.org Description: Due to a change in the output of dump(8) to ensure consistency in the messages, AMANDA's dump output parser breaks. Error messages such as the following may be an indication that this problem is present: FAILURE AND STRANGE DUMP SUMMARY: hostname wd0e lev 1 FAILED [no backup size line] Versions affected: 2.3.0.4, and most likely earlier versions Workaround/Fix: One of: * Apply the patch found at: ftp://ftp.netbsd.org/pub/NetBSD/misc/patches/amanda-pre-2.4.patch * Upgrade to AMANDA 2.4.0 or newer. The side effect of this is that the network protocol is incompatible with earlier versions. 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 intro(1), man(1), apropros(1), passwd(1), and passwd(5). The section numbers group the topics into several categories, but three are of primary interest: user commands are in section 1, file formats are in section 5, and administrative information is in section 8. The 'man' command is used to view the documentation on a topic, and is started by entering 'man [section] topic'. The brackets [] around the 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 least-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 available via the mailing list server at . To get help on using the mailing 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' 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' is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. If you're 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 mail and/or subscribe to: netbsd-help@NetBSD.ORG As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP 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: ------ -- -- Members and 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. Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Best Internet Communications for hosting the NetBSD FTP and SUP server. Cygnus Support for hosting the NetBSD Mail server. 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. Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Bay Area Internet Solutions Jason Brazile David Brownlee Simon Burge Dave Burgess Ralph Campbell Canada Connect Corporation Brian Carlstrom James Chacon Bill Coldwell Charles Conn Tom Coulter Charles D. Cranor Christopher G. Demetriou Demon Internet, UK Easynet, UK Scott Ellis Free Hardware Foundation Greg Gingerich Michael L. Hitch Innovation Development Enterprises of America Scott Kaplan Chris Legrow Neil J. McRae Perry E. Metzger MS Macro System GmbH, Germany Numerical Aerospace Simulation Facility, NASA Ames Research Center Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Jason R. Thorpe Steve Wadlow (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.) Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) We are: -- --- (in alphabetical order) The NetBSD core group: J.T. Conklin Charles Hannum Paul Kranenburg Jason Thorpe Christos Zoulas The port-masters (and their ports): Mark Brinicombe (arm32) Jeremy Cooper (sun3x) Chuck Cranor (mvme68k) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Scott Reynolds (mac68k) Gordon Ross (sun3, sun3x) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) The NetBSD 1.3 Release Engineering team: Ted Lemon Perry Metzger Jason Thorpe Supporting cast: Steve Allen Lennart Augustsson Christoph Badura John Birrell Manuel Bouyer John Brezak Allen Briggs Aaron Brown David Brownlee Simon Burge Dave Burgess Dave Carrel Bill Coldwell Alistair Crooks Rob Deker Chris G. Demetriou Matthias Drochner Bernd Ernesti Erik Fair Hubert Feyrer Brian R. Gaeke Justin Gibbs Adam Glass Michael Graff Brad Grantham Matthew Green Juergen Hannken-Illjes Michael L. Hitch Marc Horowitz Matthew Jacob Lonhyn T. Jasinskyj Lawrence Kesteloot Klaus Klein John Kohl Kevin Lahey Ted Lemon Mike Long Paul Mackerras SAITOH Masanobu Neil J. McRae Perry Metzger Luke Mewburn der Mouse Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Darren Reed Kazuki Sakamoto Curt Sampson Wilfredo Sanchez Karl Schilke (rAT) Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Bill Sommerfeld Ignatios Souvatzis Bill Studenmund Kevin Sullivan Matt Thomas Enami Tsugutomo Todd Vierling Paul Vixie Colin Wood Steve Woodford Dedication: ---------- The Release Engineering team would like to dedicate the NetBSD 1.3 release to the memory of the late Koji Imada, who was killed in a motorcycle accident in August, 1997 at the age of 28. A doctoral student in Mathematical Science at Nagoya University, he was a user of NetBSD and a contributor to the project since 1993. Well remembered by his friends, he was also known as a connoisseur of gins, teas, and the motorcycles he loved to ride. His death came as a shock, and he will be greatly missed by all of us. May he rest in peace. Legal Mumbo-jumbo: ----- ----- ----- The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by the NetBSD Foundation, Inc. and its contributors. This product includes software developed by Adam Glass and Charles Hannum. This product includes software developed by Adam Glass. This product includes software developed by Berkeley Software Design, Inc. This product includes software developed by Charles D. Cranor and Washington University. This product includes software developed by Charles D. Cranor. This product includes software developed by Charles Hannum, by the University of Vermont and State Agricultural College and Garrett A. Wollman, by William F. Jolitz, and by the University of California, Berkeley, Lawrence Berkeley Laboratory, and its contributors. This product includes software developed by Charles Hannum. This product includes software developed by Charles M. Hannum. This product includes software developed by Chris Provenzano. This product includes software developed by Christian E. Hopps. This product includes software developed by Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Christos Zoulas. This product includes software developed by David Jones and Gordon Ross. This product includes software developed by Dean Huxley. This product includes software developed by Eric S. Hvozda. This product includes software developed by Ezra Story. This product includes software developed by Gordon Ross. This product includes software developed by Gordon W. Ross and Leo Weppelman. This product includes software developed by Gordon W. Ross. This product includes software developed by Herb Peyerl. This product includes software developed by Ian W. Dall. This product includes software developed by Ignatios Souvatzis for the NetBSD Project. This product includes software developed by Jason R. Thorpe for And 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 John Polstra. This product includes software developed by Jonathan Stone and Jason R. Thorpe for the NetBSD Project. This product includes software developed by Jonathan Stone for the NetBSD Project. This product includes software developed by Jonathan Stone. This product includes software developed by Julian Highfield. This product includes software developed by Kenneth Stailey. This product includes software developed by Leo Weppelman. This product includes software developed by Lloyd Parkes. This product includes software developed by Mark Brinicombe. This product includes software developed by Markus Wild. This product includes software developed by Martin Husemann and Wolfgang Solfrank. This product includes software developed by Mats O Jansson and Charles D. Cranor. This product includes software developed by Mats O Jansson. This product includes software developed by Matthias Pfaller. This product includes software developed by Paul Kranenburg. This product includes software developed by Paul Mackerras. This product includes software developed by Peter Galbavy. This product includes software developed by Philip A. Nelson. This product includes software developed by Rodney W. Grimes. This product includes software developed by Scott Bartram. This product includes software developed by SigmaSoft, Th. This product includes software developed by Terrence R. Lambert. This product includes software developed by Theo de Raadt and John Brezak. This product includes software developed by Theo de Raadt. This product includes software developed by TooLs GmbH. This product includes software developed by Winning Strategies, Inc. This product includes software developed by the Center for Software Science at the University of Utah. This product includes software developed by the University of Calgary Department of Computer Science and its contributors. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed for the FreeBSD project. This product includes software developed for the Internet Software Consortium by Ted Lemon. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed for the NetBSD Project by Matthias Drochner. This product includes software developed for the NetBSD Project by Matthieu Herrb. This product includes software developed for the NetBSD Project by Perry E. Metzger. This product includes software developed for the NetBSD Project by Piermont Information Systems Inc. This product includes software developed for the NetBSD Project by Ted Lemon. This product includes software developed by the Computer Systems Laboratory at the University of Utah. This product includes software developed by the University of Vermont and State Agricultural College and Garrett A. Wollman. This product includes software developed by Charles D. Cranor. This product includes software developed by Adam Glass. This product includes software developed by Charles Hannum. This product includes software developed by David Jones. This product includes software developed by Gordon W. Ross. This product includes software developed by Steve C. Woodford.