INSTALLATION NOTES for NetBSD/sun3 1.1 Be sure to read _ALL_ of this document before you try to install NetBSD/sun3. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.1 is a evolutionary release which contains over a year of changes to the kernel, user-level utilities, and documentation. Continuing the multi-platform tradition, NetBSD has added ports to atari and mvme68k based machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.1 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. NetBSD 1.1 is also the first release to see machine-independent disk striping. The concatenated disk driver (ccd), which was previously supported only by the hp300 port, has been vastly improved. Many bugs were fixed, and explicit references to device-dependent routines removed and replaced by calls to the generic "vnode operation" routines. In addition, several features were added, including partition support, dynamic configuration and unconfiguration via a user space system utility program, and virtually unlimited number of component devices. Many new user programs have been added in NetBSD 1.1, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. NetBSD 1.1 is the first "full" release of NetBSD for the sun3, including a full set of binaries. This binary distribution is referred to elsewhere in this document by the name NetBSD/sun3. This release offers improved stability and many new features. New features added since the 1.0 release include: * Native boot programs for disk, network, and tape * Automated installation tools (using a "miniroot") * New SCSI driver supporting DMA, interrupts, and disconnect/reselect with SCSI-2 devices (optional) * Frame buffer drivers for bwtwo, cgtwo, and cgthree, all compatible with SunOS and the X Window System * Support for the Virtually Addressed Cache (VAC) on Sun3/260 models (and vastly improved performance) * SMD disk drivers -- almost (still need testing) Old features (from 1.0 and earier) worth mentioning: * SunOS 4.1 compatibility (runs most Sun3 applications) * Supports most SCSI devices (CD-ROM, etc) * Diskless boot capability * Built-in kernel debugger The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation was recently incorporated as a non-profit organization. It's 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. (IN WHAT WAY? Money, donations, etc) We believe that 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 or nearly-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: ------- -- ------ Host name Services Provided ---- ---- -------- -------- ftp.iastate.edu Anonymous FTP, AFS Anon-FTP path: pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/misc/sup/supfile.example via anonymous FTP and read it as an example. ftp.demon.co.uk Anonymous FTP, possibly SUP Anon-FTP path: pub/BSD/NetBSD SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD ftp.funet.fi Anonymous FTP Anon-FTP path: pub/unix/NetBSD ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/sup/README.sup via anonymous FTP from ftp.netbsd.org, and read it for instructions. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.1 Release Contents: ------ --- ------- -------- The NetBSD 1.1 release is organized in the following way: .../NetBSD-1.1/ 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.1 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 that NetBSD 1.1 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. 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: dsrc11 This set contains the "domestic" sources. These sources contain export-restricted encryption code and should not be exported from the U.S. [ 140K gzipped, 655K uncompressed ] gsrc11 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.1M gzipped, 30.4M uncompressed ] ksrc11 This set contains the sources to the NetBSD 1.1 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc11 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.4M gzipped, 8.9M uncompressed ] src11 This set contains all of the NetBSD 1.1 sources which are not mentioned above. [ 9.3M gzipped, 41.6M 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. The source distribution sets are distributed as groups of files 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.) Catted together, the files belonging to a source distribution set comprise a gzipped tar file. If you want to look at list of the files contained in the set, you could use the command: cat set_name.?? | gunzip | tar tvf - or to actually extract the files contained in the set: cat set_name.?? | gunzip | tar xfp - 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. The sun3-specific portion of the NetBSD 1.1 release is found in the "sun3" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.1/sun3/ INSTALL.txt Installation notes; this file. install/ Boot programs, a GENERIC kernel, a stand-alone RAMDISK kernel, and a miniroot filesystem image. see below. binary/ sun3 binary distribution sets; see below. security/ sun3 security distribution; see below. The NetBSD/sun3 "install" distribution contains files that can be used to install NetBSD onto a completely "bare" sun3. The files in the `.../install' directory 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. netbsd-gen.gz A gzipped GENERIC kernel (for upgrade) netboot A copy of the network boot program. This is useful if you are installing a diskless NetBSD/sun3 system. tapeboot A copy of the tape boot program, used as the first segment of a boot tape. These files can be used to make a boot tape suitable for installing NetBSD/sun3. 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. The NetBSD/sun3 binary distribution sets contain the binaries which comprise the NetBSD 1.1 release for the sun3. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "sun3/binary" subdirectory of the NetBSD 1.1 distribution tree, and are as follows: base11 The NetBSD/sun3 1.1 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. [ 7.2M gzipped, 19M uncompressed ] comp11 The NetBSD/sun3 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. [ 4.6M gzipped, 14.7M uncompressed ] etc11 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.) [ 64K gzipped, 348K uncompressed ] games11 This set includes the games and their manual pages. [ 2.8M gzipped, 6.8M uncompressed ] man11 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. [ 850K gzipped, 3.3M uncompressed ] misc11 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. [ 1.8M gzipped, 6.5M uncompressed ] text11 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 770K gzipped, 2.8M uncompressed ] The sun3 security distribution set is named "secr11" and can be found in the "sun3/security" subdirectory of the NetBSD 1.1 distribution tree. It contains executables which are built in the "src/domestic" portion if 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, this distribution set may not be exported to locations outside of the United States and Canada.) [ 128K gzipped, 275K uncompressed ] The sun3 binary distribution sets are distributed as gzipped tar files. Each sun3 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 "tar xvfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced. If you follow the normal installation or upgrade procedures, this will be taken care of for you. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/sun3 1.1 runs on most Sun3 machines, including: 3/50, 3/60, 3/110 3/75, 3/150, 3/160 3/260, 3/280 NetBSD/sun3 1.1 does not run on the Sun3/80 (sun3x class) because the sun3x MMU and other devices are very different. The minimal configuration requires 4M of RAM and ~80MB of disk space. To install the entire system requires much more disk space (approx. 100MB additional space is necessary for full sources). To run X or compile the system, more RAM is recommended. Good performance requires 8MB of RAM, or 16 MB when running the X Window System. The following Sun3 hardware is supported: Serial ports (RS232): built-in ttya, ttyb Video adapters: bwtwo, cgtwo, cgfour Network interfaces: On-board Lance Ethernet (le) On-board or VME Intel Ethernet (ie) SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.) On-board "si" (SCSI-3) [Note 1] VME "si" (SCSI-3) board [Note 1] SMD Disks: (the big, heavy ones 8^) Xylogics 450/451 [Note 2] Xylogics 753/7053 [Note 2] Input devices: Sun keyboard and mouse Miscellaneous: Battery-backed real-time clock. Note 1: The "si" driver now supports DMA and disconnect/reselect but due to the imaturity of the DMA code, those features are disabled by default. To enable DMA (and get faster SCSI performance) patch the variable si_options in the file /usr/src/sys/arch/sun3/dev/ncr_si.c as indicated. Note 2: SMD disk support is almost ready, but could not be tested in time for this release. Drivers are provided for the Xylogics 450/451 and Xylogics 753/7053 VME boards only as source code. They compile but have never touched a disk. 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 some bootable device; either a tape drive or Sun-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 in these two directories: .../NetBSD-1.1/sun3/install .../NetBSD-1-1/sun3/binary * Creating boot/install tapes: Installing from tape is the simplest method of all. This method uses two tapes; one called the "boot" tape, and another called the "install" tape. The boot tape is created as follows: cd .../NetBSD-1.1/sun3/install set T = /dev/nrst0 mt -f $T rewind dd if=tapeboot of=$T bs=8k conv=sync dd if=netbsd-rd of=$T bs=8k conv=sync gzip -d < miniroot.gz | dd of=$T bs=8k mt -f $T rewind The install tape is created as follows: cd .../NetBSD-1.1/sun3/binary set T = /dev/nrst0 mt -f $T rewind foreach f (base etc comp games man misc text) gzip -d < $f.tar.gz | dd of=$T bs=8k end mt -f $T rewind If the tapes do not work as expected, you may need to explicitly set the EOF mark at the end of each tape segment. (mt -f /dev/nrst0 weof) It may also be necessary to use the `conv=osync' argument to dd(1). Note that this argument is incompatible with the `bs=' argument. 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). Your Sun3 expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RARP when instructed to boot "over the net". It will look for a filename derived from the machine's IP address expressed in hexadecimal. For example, a sun3 which has been assigned IP address 130.115.144.11 will make an TFTP request for `8273900B'. Normally, this file is a symbolic link to the NetBSD/sun3 "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) and /etc/bootparams on the server should have an entry for your client and its root directory. The client will need access to the miniroot image, which can be provided using NFS or remote shell. If using NFS, miniroot.gz must be expanded on the server, because there is no gzip program in the RAMDISK image. The unzipped miniroot takes 8MB 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 RAM-disk 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: 205.149.163.23 Login: anonymous Password: Server path: /pub/NetBSD/NetBSD-1.1/sun3/binary Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Sun3 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. You will need to know the SCSI target ID of the drive on which you will install NetBSD. Note that SunOS/sun3 uses confusing names for the SCSI devcies: target 1 is sd2, target 2 is sd4, etc. It might be a good time to run the diagnostics on your Sun3. First, attach a terminal to the "ttya" serial port, then set the "Diag/Norm" switch to the Diagnostic position, and power-on the machine. The Diag. switch setting forces console interaction to occur on ttya. The console location (ttya, ttyb, or keyboard/display) is controlled by address 0x1F in the EEPROM, which you can examine and change in the PROM monitor by entering "q1f" followed by a numeric value (or just a '.' if you don't want to change it). Console values are: 00: default graphics display 10: tty a (9600-N-8-1) 11: tty b (1200-N-8-1) 20: Color option board on P4 NetBSD will use the EEPROM setting to determine which device to use as the console, so you should make sure it is correct. 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 Sun machine running SunOS you can initialize the disk on that machine and then move the disk. (Installing from SunOS is not recommended.) * Installing from tape: Create the NetBSD/sun3 1.1 boot tape as described in the section entitled "Preparing a boot tape" and boot the tape. At the PROM monitor prompt, use one of the commands: >b st() >b st(0,8,0) The first example will use the tape on SCSI target 4, where the second will use SCSI target 5. The '>' is the monitor prompt. After the tape loads, you should see many lines of configuration messages, and then the following "welcome" screen: Welcome to the NetBSD/sun3 RAMDISK root! This environment is designed to do only three things: 1: Partititon your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Reboot (using the swap partition, i.e. /dev/sd?b). 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 2 dd bs=32k if=/dev/nrst0 of=/dev/rsd0b (For help with other methods, please see the install notes.) To reboot using the swap partition, first use "halt", then at the PROM monitor prompt use a command like: b sd(,,1) -s To view this message again, type: cat /.welcome [ End of "welcome" screen. ] Copy the miniroot as described in the welcome message, and 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 diskless client. Instructions for configuring the server are found in the section entitled "Getting the NetBSD System onto Useful Media" above. First, at the Sun PROM monitor prompt, enter a boot command using the network interface as the boot device. On desktop machines this is "le", and "ie" on the others. Examples: >b le() -s >b ie() -s After the boot program loads the RAMDISK kernel, you should see the welcome screen as shown in the "tape boot" section above. You must configure the network interface before you can use any network resources. For example: ssh> ifconfig ie0 inet 192.233.17.119 up You may also need to add a default route. Example: ssh> route add default 192.233.17.3 1 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.233.16.203) To load the miniroot from an NFS file: ssh> mount -r 192.233.16.203:/server/path /mnt ssh> dd if=/mnt/install/miniroot of=/dev/rsd0b bs=8k To load the miniroot using rsh to the server: ssh> run -b dd if=/dev/pipe of=/dev/rsd0b bs=8k ssh> run -o /dev/pipe rsh 192.233.16.203 zcat miniroot.gz Note that "ssh" does not use "sh" syntax. It is a very small shell designed for the ramdisk kernel. The first command of the above pair runs a "dd" in the background reading /dev/pipe. The second of the pair runs an "rsh" command with its standard output redirected to /dev/pipe. In ssh, the "help" command will show you a list of commands and options (there are only a few). * Booting the miniroot: If the miniroot was installed on partition 'b' of the disk with SCSI target ID=0 then the PROM boot command would be: >b sd(0,0,1) -s With SCSI target ID=2, the the PROM is: >b sd(0,10,1) -s The numbers in parentheses above are: controller (usually zero) unit number (SCSI ID * 8, in hexadecimal) partition number 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: 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) The number of partitions is fixed at 8 (by the Sun PROM). * 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: --------- - ---------- --------- ------ ------ There is no automated upgrade program in this release. (This is the first official release for the Sun3 anyway.) However, it is possible to upgrade your system manually. Manual upgrade procedure: * Place _at least_ the `base' binary set in a filesystem accessible to the target machine. A local filesystem is preferred, since there may be incompatibilities between the NetBSD 1.1 kernel and older route(8) binaries. * Back up your pre-existing kernel and copy the 1.1 kernel into your root partition. * Reboot with the 1.1 kernel into single-user mode. * Check all filesystems: /sbin/fsck -p * 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 NOTE: the route(8) commands may fail due to potential incompatibilities between route(8) and the NetBSD 1.1 kernel. Once you have enabled the network, mount the NFS filesystems. If you use amd(8), you may or may not have to mount these filesystems manually. Your mileage may vary. * Make sure you are in the root filesystem and extract the `base' binary set: cd / tar --unlink -zxvpf /path/to/base11.tar.gz NOTE: the `--unlink' option is _very_ important! * Install a new boot block: cd /usr/mdec cp -p ./ufsboot /mnt/ufsboot sync ; sleep 1 ; sync ./installboot /mnt/ufsboot bootxx /dev/rsd0a # Substitute your root partition here -^ * 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. Administrivia: ------------- Registration? What's that? 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. 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. Alistair G. Crooks has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. 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: Jason Brazile Dave Burgess Charles Conn Canada Connect Corporation Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth 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 The port-masters (and their ports): Allen Briggs (mac68k) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Ted Lemon (pmax) Anders Magnusson (vax) Phil Nelson (pc532) Gordon Ross (sun3) Jason Thorpe (hp300) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Dave Burgess Hubert Feyrer Adam Glass Brad Grantham Matthew Green Michael L. Hitch Lawrence Kesteloot John Kohl Paul Mackerras Neil J. McRae Perry Metzger Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Thor Lancelot Simon Wolfgang Solfrank Frank van der Linden Christos Zoulas 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 Christopher G. Demetriou. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by Paul Kranenburg. This product includes software developed by John Kohl. This product includes software developed by Terrence R. Lambert. This product includes software developed by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Jason Thorpe. This product includes software developed by TooLs GmbH. This product includes software developed by Christos Zoulas. 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 Charles Hannum. This product includes software developed by David Jones. This product includes software developed by Gordon W. Ross.