INSTALLATION NOTES for NetBSD/pc532 1.3.3 Be sure to read _ALL_ of this document before you try to install NetBSD/pc532. 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.3 release is a security and bug fix update for the NetBSD 1.3 release. The NetBSD 1.3 release was 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. For the pc532 port, there are a few known problems. They include: a) ppp reports a lot of input errors on some machines. b) Some tape drives do not work very well. Some have hung the system. c) The serial drivers do not have all the desired features. (ttyflags is the most glaring.) 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 December 01, 1998. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. FTP mirrors ----------- Australia * ftp.au.netbsd.org RMIT University, Melbourne ftp://ftp.au.netbsd.org/pub/NetBSD * ftp2.au.netbsd.org University of Queensland, Brisbane ftp://ftp2.au.netbsd.org/pub/NetBSD Austria * ftp.at.netbsd.org University of Technology, Vienna ftp://ftp.at.netbsd.org/pub/NetBSD Brazil * ftp.ravel.ufrj.br Cidade Universitaria ftp://ftp.ravel.ufrj.br/pub/NetBSD Denmark * ftp.dk.netbsd.org Aalborg University ftp://ftp.dk.netbsd.org/pub/NetBSD Finland * ftp.fi.netbsd.org The Finnish University and Research Network, Espoo ftp://ftp.fi.netbsd.org/pub/NetBSD France * ftp.fr.netbsd.org Paris University ftp://ftp.fr.netbsd.org/pub/NetBSD Germany * ftp.de.netbsd.org University of Trier ftp://ftp.de.netbsd.org/pub/NetBSD * ftp2.de.netbsd.org University of Erlangen-Nuremberg ftp://ftp2.de.netbsd.org/pub/NetBSD * ftp.uni-regensburg.de University of Regensburg ftp://ftp.uni-regensburg.de/pub/comp/os/NetBSD Japan * ftp.jp.netbsd.org Internet Research Institute Inc., Tokyo ftp://ftp.jp.netbsd.org/pub/NetBSD * ftp.dti.ad.jp ftp://ftp.dti.ad.jp/pub/NetBSD/ * mirror.nucba.ac.jp Nagoya University of Commerce and Business ftp://mirror.nucba.ac.jp/mirror/NetBSD * netbsd.tohoku.ac.jp Tohoku University ftp://netbsd.tohoku.ac.jp/NetBSD Korea * sunsite.kren.ne.kr Seoul National University ftp://sunsite.kren.ne.kr/pub/OS/NetBSD Netherlands * ftp.nl.netbsd.org University of Amsterdam ftp://ftp.nl.netbsd.org/pub/NetBSD Norway * ftp.no.netbsd.org ftp://ftp.no.netbsd.org/pub/NetBSD * ftp.ntnu.no Norwegian University of Science and Technology ftp://ftp.ntnu.no/pub/NetBSD * skarven.itea.ntnu.no Norwegian University of Science and Technology ftp://skarven.itea.ntnu.no/pub/NetBSD Russia * ftp.ru.netbsd.org Landau Institute for Theoretical Physics, Chernogolovka ftp://ftp.ru.netbsd.org/pub/NetBSD Sweden * ftp.stacken.kth.se Royal Institute of Technology, Stockholm ftp://ftp.stacken.kth.se/pub/OS/NetBSD * ftp.sunet.se Swedish University NETwork, Uppsala ftp://ftp.sunet.se/pub/os/NetBSD UK * ftp.uk.netbsd.org Domino, London ftp://ftp.uk.netbsd.org/pub/NetBSD * sunsite.org.uk ftp://sunsite.org.uk/packages/netbsd USA * ftp.netbsd.org Silicon Valley, California ftp://ftp.netbsd.org/pub/NetBSD * ftp.cs.umn.edu University of Minnesota ftp://ftp.cs.umn.edu/pub/NetBSD * ftp.eecs.umich.edu University of Michigan, Ann Arbor ftp://ftp.eecs.umich.edu/pub/NetBSD * ftp.iastate.edu Iowa State University ftp://ftp.iastate.edu/pub/netbsd * ftp.op.net ftp://ftp.op.net/pub/NetBSD AFS mirrors ----------- Sweden * ftp.stacken.kth.se Royal Institute of Technology, Stockholm AFS path: /afs/stacken.kth.se/ftp/pub/OS/NetBSD USA * ftp.iastate.edu Iowa State University AFS path: /afs/iastate.edu/public/ftp/pub/netbsd NFS mirrors ----------- UK * sunsite.org.uk Instructions: mount -o ro sunsite.org.uk:/public/packages/netbsd /mnt SUP mirrors ----------- Australia * sup.au.netbsd.org RMIT University, Melbourne Instructions: ftp://sup.au.netbsd.org/pub/NetBSD/sup/README.sup France * sup.fr.netbsd.org Paris University Instructions: Similar to sup.netbsd.org Germany * sup.de.netbsd.org University of Trier Instructions: ftp://sup.de.netbsd.org/pub/NetBSD/sup/supfile.example * sup.owl.de Instructions: ftp://sup.owl.de/pub/sup/supfile.example Japan * sup.jp.netbsd.org Internet Research Institute Inc., Tokyo Instructions: ftp://sup.jp.netbsd.org/pub/NetBSD/sup/README.sup Norway * skarven.itea.ntnu.no Norwegian University of Science and Technology 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 * sup.uk.netbsd.org Domino, London Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup USA * sup.netbsd.org Silicon Valley, California Instructions: See ftp://ftp.netbsd.org/pub/NetBSD/sup/README.sup * ftp.cs.umn.edu University of Minnesota Instructions: hostbase=/ftp/ftp/packages/NetBSD, collections are the same as on sup.NetBSD.ORG WWW mirrors ----------- Australia * www.au.netbsd.org RMIT University, Melbourne http://www.au.netbsd.org/ Austria * www.at.netbsd.org University of Technology, Vienna http://www.at.netbsd.org/ Finland * www.fi.netbsd.org Global Wire Oy, Lappeenranta http://www.fi.netbsd.org/ France * www.fr.netbsd.org Paris University http://www.fr.netbsd.org/ Germany * www.de.netbsd.org http://www.de.netbsd.org/ Japan * www.jp.netbsd.org Internet Research Institute Inc., Tokyo http://www.jp.netbsd.org/ Norway * www.no.netbsd.org http://www.no.netbsd.org/ USA * www.netbsd.org Western Washington State University http://www.netbsd.org/ * www2.us.netbsd.org New York http://www.us.netbsd.org/ NetBSD 1.3.3 Release Contents: ------ ----- ------- -------- The NetBSD 1.3.3 release is organized in the following way: .../NetBSD-1.3.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.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.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.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.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 pc532-specific portion of the NetBSD 1.3.3 release is found in the "pc532" subdirectory of the distribution. That subdirectory contains the files as follows: .../NetBSD-1.3.3/pc532/ INSTALL Installation notes; this file. .../NetBSD-1.3.3/pc532/binary/sets base.tgz base distribution comp.tgz compiler tools & libraries etc.tgz files for /etc kern.tgz distribution kernel, install and upgrade games.tgz /usr/games and friends man.tgz /usr/man misc.tgz various text.tgz groff and friends .../NetBSD-1.3.3/pc532/installation/floppy floppy-144.gz Installation file system. .../NetBSD-1.3.3/pc532/ download.c.gz Source for a pc532 ROM compat download pgm The binary distribution consists of the following files: base.tgz The NetBSD/pc532 1.3.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 excludes everything described below. [ 9.4M gzipped ] comp.tgz The NetBSD/pc532 Compiler tools. All of the tools relating to C, C++, Objective C, and FORTRAN (yes, there are two, although NO FORTRAN compiler!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries. This set also includes the manual pages for all the utilities it contains, as well as the system call and library manual pages. [ 6.8M gzipped ] etc.tgz 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 ] games.tgz This set includes the games and their manual pages. [ 2.9M gzipped ] kern.tgz This is the default kernel for both the standard install and for the upgrade. man.tgz 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.4M gzipped ] misc.tgz 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.2M gzipped ] text.tgz This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 1.0M gzipped ] The pc532 distribution set does not include a security distribution. If you are in the US and want the security distribution you must get the security source distribution and recompile libcrypt.a and recompile the following programs: ed, ftpd, makekey, rexecd, uucpd, init, lock, login, passwd, skeyinit, su, tn3270, pppd The initial installation process on a pc532 without NetBSD/pc532 is supported by the following files: Initial file system used via SCSI floppy or downloaded into memory: floppy-144.fs -- file system containing boot loader and install kernel with 2MB ram root file system. download.c -- source for the program to download inst-11.fs into memory via the pc532 ROM monitor. The upgrade process is supported by having a copy of a 1.3.3 kernel available. This file is: kern.tgz -- contains a kernel produced from the DEFAULT configuration file in pc532/conf. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/pc532 1.3.3 runs on a PC532 computer. It supports a subset of the "standard" hardware to date. This is defined as: 4 - 32 Megs of memory 8 serial lines done by 4 scn2681 chips the NCR DP8490 SCSI chip (scsi only) Most SCSI disks work (fixed and floppy) A few SCSI tapes work Some SCSI CD-ROM drives work The Matthias Pfaller Parallel Port. NetBSD/pc532 currently expects the ROM monitor to be the "autoboot monitor" of Oct/Nov 1991. It includes support to set up auto booting of NetBSD, including a secondary boot program that the autoboot monitor will load that in turn loads the NetBSD kernel from a NetBSD file system. (Source and ROM images of the autoboot monitor are located at ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz.) Most of the pc532 specific development of NetBSD/pc532 was done on a machine with 8-Megs of memory. It should run with 4-Megs of memory although it may be slower. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- The "standard" method of getting NetBSD/pc532 onto your pc532 is via the console terminal and using the downloading parts of the ROM monitor. As such, usually another computer has the distribution on disk and is connected via a serial line to your pc532's console port. A terminal connected to the attached host computer is used to access the pc532 console via a terminal program. The source for a program called download is part of this distribution. Download sends data to the ROM monitor over the serial line. You may need to find and read the documentation about the ROM monitor download command and other low level comands. Other methods of getting NetBSD/pc532 on your pc532 may include SCSI tape or SCSI floppy disk or cloning a disk on a system already running NetBSD/pc532. If you have some operating system already running on your pc532, you can use that OS to get NetBSD/pc532 on a hard disk much easier than with the ROM monitor. (NetBSD/pc532 was developed from Minix/pc532 until it was self hosting. You can run NetBSD and Minix or other OS off the same disk.) Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ The major preparation needed is to make sure you can recover any current bits stored on your pc532. If you don't care about your data on the disk, you don't need to do anything. Installing the NetBSD System: ---------- --- ------ ------ (IF you already have NetBSD/pc532 installed and you only want to update your system, see the next section.) To install NetBSD/pc532, there are several things you need to know. First, NetBSD "autoconfigs" the scsi devices. floppy-144.fs has only support for disks configured into the kernel. Starting the search at SCSI address 0, lun 0 and increasing, the first disk found will be sd0 regardless of the address, the second will be sd1. KLONDIKE for example has the following devices installed: sd0 -> ID 0 LUN 0: Quantum LP52S hard disk drive sd1 -> ID 1 LUN 0: Micropolis 4110 hard disk drive sd2 -> ID 2 LUN 0: Teac FC-1, 3.5" floppy disk drive sd3 -> ID 2 LUN 1: Teac FC-1, 5.25" floppy disk drive cd0 -> ID 3 LUN 0: Toshiba XM-4101TA CD-ROM drive st0 -> ID 4 LUN 0: Tandberg TDC3600 QIC tape drive Only sd0-sd3 are supported by the floppy-144.fs kernel. Next you need to know what the install script wants to do. This install is script on the ram disk root that can do most of the work of configuring your disk. a) The script assumes your are using the first n sectors of your disk, where you can specify n. It will allow you to create up to 5 file system partitions, one swap partition and one boot partition. b) You should know how many total sectors are on your disk. The configure will report a head, track, and cylinder count, but I have found that on my disks, it reports something that makes a smaller disk than I really had. c) It is possible to have the install script make a partition over your save area AND not make a new file system, thus preserving what is there. Then, later you can make a new file system after you no longer need the stuff there. You will need to do only one boot to get things working from the disk. The Install Procedure: a) Adjust your console device settings. The floppy-144.fs kernel will come up with 9600 baud, 7 bits, even parity and one stop bit. Adjust your terminal to match these settings. The monitor's baud rate can be changed with "baud d'9600". b) Get floppy-144.fs and boot the kernel. From Floppy: (and using the autoboot monitor) If you have a 1.44 meg SCSI floppy drive, you can put floppy-144.fs onto a 3.5" floppy disk. Insert the disk into your floppy drive and use the monitor's boot command to boot the default image from the floppy. The image booted will ask you for a kernel to load. Answer sdXa:/netbsd Replace X with your drive number. For KLONDIKE X would be "2". Tape: You will need to load a copy of floppy-144.fs into RAM. - load the floppy-144.fs at 0x260000 - run at 0x3BE020 The boot program will ask you now for a kernel to load. Answer md0a:/netbsd.gz Serial line: Provided with the distribution is source for program called download. (download.c) This program when used as "download file" will read the contents of the file and output to standard output a byte sequence used by the pc532 ROM monitor to download a binary file into RAM. Using this program on a computer connected to the pc532, one can load a copy of floppy-144.fs into RAM at 0x260000. The boot sequence is now the same as with tape. c) The floppy-144.fs will run the new sysinst utility as the standard setup. It assumes a VT100 compatible terminal. If you don't want to try using sysinst or you dont' have a VT100, type f followed by the return. Then following these instructions for installation. If you want to use sysinst, read the i386 INSTALL instructions to learn about sysinst. Note: sysinst does not support SLIP or PPP connections. c) Choose a disk geometry. For me, the reported geometry left some sectors "unallocated". That is, the autoconfig message said the disk had 2428 cylinders, 9 heads, and 93 sectors/track. This gives a total of 2032236 sectors, but I knew that I had 2053880 sectors. To help in this process, there is a program "factor" that is on the floppy-144.fs. The usage is "factor number" and it lists the prime factors of number. For example, with the 2053880 sector disk I got: ---->~/sd1 steelhead[3]$ factor 2053880 2053880: 2 2 2 5 51347 Not many to choose from, so I tried ... ---->~/sd1 steelhead[4]$ factor 2053820 2053820: 2 2 5 103 997 Now I'd like to get about a meg per track: steelhead[5]$ echo "2 * 997"|bc 1994 Now I need the number of tracks (or cylinders): steelhead[5]$ echo "2 * 5 * 103"|bc 1030 So I ended up choosing 1030 cylinders, 1 head, 1994 sectors/track. I "lost" only 60 sectors, but got a "resonable geometry". d) run "install" -- it will ask you for the disk geometry and other questions. It will ask you for the geometry and then ask you how many of those sectors you want to use for NetBSD. It also wants to know the size of your boot partition (to be used with the auto-boot monitor), your root partition, your swap partition, and then any other partitions you may want. For the "other" partitions, it will ask for a mount point. The mount point will be "relative to /" and should not include the leading "/". Also, IF you do not want the partition to have newfs run on it (that is it might be the last one and have a copy of floppy-144.fs) enter "NO" to the mount point and it will not run newfs on the partition. It will enter the partition into the disklabel. e) look around, if you want ... and then halt NetBSD. f) reboot the machine. Using the autoboot monitor, all you should have to do is give the ROM monitor command "boot". The secondary UFS boot program eventually times out and auto-loads /netbsd. You can get it to do it faster by hitting "return". (If you are not using the autoboot monitor, you will have to figure out the starting sector of the boot images partition and manually load the NetBSD boot loader from the disk using the read command. If you would rather use the autoboot monitor you can get source and ROM images from the URL ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz.) g) Now it is time to load all the other files of the distribution: You can do this via -- a) a TCP/IP link (slip, ppp or plip) you have ifconfig, slattach, route, netstat, hostname and ftp on the mini-root. You can even use nfs... Plip is only an option if you have installed a centronics port in your pc532. You do have access to vi to edit your network files. (/etc/resolv.conf, ...) b) floppy disk c) tape d) cd-rom (If you have a CD with NetBSD/532, which most likely won't happen for a while after _VER release.) -- mount -rt cd9660 /dev/cd0a /mnt Get the .tgz files from the cd-rom e) Use the ROM compatable "download" program. The program download is included in the initial installation and can be used as the receive end of the download by using it as "download -r file_to_write". If the CRC is correct, the file is retained. If the CRC is not correct, the file is deleted. h) Load the .tgz files. Choose a place to put them. I would make a directory /gz.files and put them there. If you are "short on space," you might want to load them and extract them one at a time. A minimum installation is "base" and "etc". It takes about 32 Megs installed + 20 Megs for the base.tgz. i) Extract the tar files in /. For example, if your *.tgz were in a directory /gz.files, to extract base.tgz you would: - cd / - tar -xpzf /gz.files/base.tgz --unlink Add v to the flags if you want a verbose extract. The --unlink is to make sure that the install versions of sh, init, ... are replaced by their proper versons in base.tgz. I think it is wise to include the --unlink for other things. j) Extract at least "base", "etc" and "kern" for a new installation. For "update" extracts, move /etc to /etc.old and then extract "etc". You should extract "etc" for upgrades. For "full" installations, extract all files. k) Edit the information in /etc - rc.conf - Many of the following things can be configured here - hosts - host name and address information - myname - your host name - mygate - hostname of gateway (assuming you have one) - resolv.conf - which nameserver to use - ifconfig.{sl0,ppp0,plip0} - interface hostname - netstart - configures the network and says if sendmail should be started - ttys - make sure the console entry has the correct speed - gettytab - I find "ap" instead of "ep" in the default entry works better for me. - fstab - make sure it includes all partitions you want mounted - localtime - this is usually a link into /usr/share/zoneinfo Now you can adjust the kernel's default baud rate to match your monitor's default baud rate. Do the following: gdb -w /netbsd set scndefaultrate = YOUR_BAUD_RATE quit where YOUR_BAUD_RATE is the actual value, 19200, 38400 or something slower than 9600. If you set scndefaultrate to something bogus, you'll probably not be able to reboot... So be carefull! l) Reboot the machine and it should come up in multi-user mode *IF* you got it configured correctly. m) Enjoy! And help fix bugs and improve NetBSD/pc532! Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ The upgrade to NetBSD 1.3.3 is a binary upgrade; it can be quite difficult to advance to a later version by recompiling from source due primarily to interdependencies in the various components. To do the upgrade, you must have at least base.tgz on disk and a copy of the proper netbsd.default. It will require quite a bit of disk space to do the upgrade. Since upgrading involves replacing the kernel, and most of the system binaries, it has the potential to cause data loss. You are strongly advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the NetBSD partition or on another operating system's partition, before beginning the upgrade process. To upgrade your system, follow the following instructions: Assuming you have space, load the .tgz files onto disk some place. Then boot the floppy-144.fs image via the method you use. Under the install system, extract the .tgz files as mentioned below or read the i386 INSTALL notes for how to use sysinst. Extract the .tgz files. Remember to use the --unlink option with tar so it can replace binaries currently in use. For example, to extract base.tgz: cd / tar -xpzf /gz.files/base.tgz --unlink Extract all the .tgz files you want. You should carefully work at upgrading /etc. There may be changes to file formats depending on what version of NetBSD/pc532 you are running. BE CAREFUL IF YOU ARE NOT RUNNING WITH SECURITY. The 1.3.3 distribution does contain support for password encryption. If you are upgrading from 1.0, it would be reasonable to save a copy of master.passwd and remove all passwords until after you upgrade. (NetBSD-1.0 did not ship with password encryption.) Place netbsd.default in / as the file netbsd. Reboot. (Remember, detbsd.default is a 9600 console line kernel. Read the last part of the new installation part of these notes to find out how to change your default speed.) After reboot, you should make sure you check your new file systems. 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.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: Paul Kranenburg Herb Peyerl Scott Reynolds Christos Zoulas The port-masters (and their ports): Mark Brinicombe (arm32) Jeremy Cooper (sun3x) Chuck Cranor (mvme68k) Charles Hannum (i386) Ross Harvey (alpha) Chris Hopps (amiga) Eduardo Horvath (sparc64) Paul Kranenburg (sparc) Ted Lemon (pmax) Anders Magnusson (vax) Tsubai Masanari (macppc, newsmips) Phil Nelson (pc532) Masaru Oki (x68k) Scott Reynolds (mac68k) Gordon Ross (sun3, sun3x) Kazuki Sakamoto (bebox) Wolfgang Solfrank (powerpc) Jonathan Stone (pmax) Jason Thorpe (hp300) Frank van der Linden (i386) Leo Weppelman (atari) The NetBSD 1.3.3 Release Engineering team: Chris G. Demetriou Ted Lemon Perry Metzger Jason Thorpe Supporting cast: Steve Allen Lennart Augustsson Christoph Badura Manuel Bouyer Robert V. Baron John Birrell Manuel Bouyer John Brezak Allen Briggs Aaron Brown David Brownlee Simon Burge Dave Burgess Dave Carrel Bill Coldwell Alistair Crooks Aidan Cully Rob Deker Chris G. Demetriou Matthias Drochner Enami Tsugutomo Bernd Ernesti Erik Fair Hubert Feyrer Thorsten Frueauf Brian R. Gaeke Thomas Gerner Justin Gibbs Adam Glass Michael Graff Brad Grantham Matthew Green Juergen Hannken-Illjes Charles M. Hannum Eric Haszlakiewicz Michael L. Hitch Ken Hornstein Marc Horowitz ITOH Yasufumi Matthew Jacob Lonhyn T. Jasinskyj Darrin Jewell Lawrence Kesteloot Klaus Klein John Kohl Kevin Lahey Ted Lemon Mike Long Paul Mackerras Neil J. McRae Perry Metzger Luke Mewburn Minoura Makoto der Mouse Tohru Nishimura Greg Oster Herb Peyerl Matthias Pfaller Dante Profeta Chris Provenzano Waldi Ravens Darren Reed Tim Rightnour Heiko W. Rupp SAITOH Masanobu Kazuki Sakamoto Curt Sampson Wilfredo Sanchez Ty Sarna Matthias Scheler Karl Schilke (rAT) Tim Shepard Chuck Silvers Thor Lancelot Simon Noriyuki Soda Wolfgang Solfrank Bill Sommerfeld Ignatios Souvatzis Bill Studenmund Kevin Sullivan Kimmo Suominen Matt Thomas Christoph Toshok Todd Vierling Paul Vixie Krister Walfridsson Nathan Williams 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 Alice Group. This product includes software developed by Philip L. Budne. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Philip A. Nelson. This product includes software developed by Matthias Pfaller. This product includes software at the Helsinki University of Technology. Some files have the following copyright: /* * Copyright (c) 1992 Helsinki University of Technology * All Rights Reserved. * * Permission to use, copy, modify and distribute this software and its * documentation is hereby granted, provided that both the copyright * notice and this permission notice appear in all copies of the * software, derivative works or modified versions, and any portions * thereof, and that both notices appear in supporting documentation. * * HELSINKI UNIVERSITY OF TECHNOLOGY ALLOWS FREE USE OF THIS SOFTWARE IN * ITS "AS IS" CONDITION. HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIMS ANY * LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE * USE OF THIS SOFTWARE. */ At least one file contains: * Copyright 1990 by Open Software Foundation, * Grenoble, FRANCE * * All Rights Reserved * * Permission to use, copy, modify, and distribute this software and * its documentation for any purpose and without fee is hereby granted, * provided that the above copyright notice appears in all copies and * that both the copyright notice and this permission notice appear in * supporting documentation, and that the name of OSF or Open Software * Foundation not be used in advertising or publicity pertaining to * distribution of the software without specific, written prior * permission. * * OSF DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE * INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, * IN NO EVENT SHALL OSF BE LIABLE FOR ANY SPECIAL, INDIRECT, OR * CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM * LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT, * NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. */ Some files have the following copyright: /* * Mach Operating System * Copyright (c) 1992 Carnegie Mellon University * Copyright (c) 1992 Helsinki University of Technology * All Rights Reserved. * * Permission to use, copy, modify and distribute this software and its * documentation is hereby granted, provided that both the copyright * notice and this permission notice appear in all copies of the * software, derivative works or modified versions, and any portions * thereof, and that both notices appear in supporting documentation. * * CARNEGIE MELLON AND HELSINKI UNIVERSITY OF TECHNOLOGY ALLOW FREE USE * OF THIS SOFTWARE IN ITS "AS IS" CONDITION. CARNEGIE MELLON AND * HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIM ANY LIABILITY OF ANY KIND * FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. * * Carnegie Mellon requests users of this software to return to * * Software Distribution Coordinator or Software.Distribution@CS.CMU.EDU * School of Computer Science * Carnegie Mellon University * Pittsburgh PA 15213-3890 * * any improvements or extensions that they make and grant Carnegie Mellon * the rights to redistribute these changes. */ The IEEE floating point support in /usr/src/sys/arch/pc532/fpu has the following copyright: /* * IEEE floating point support for NS32081 and NS32381 fpus. * Copyright (c) 1995 Ian Dall * All Rights Reserved. * * Permission to use, copy, modify and distribute this software and its * documentation is hereby granted, provided that both the copyright * notice and this permission notice appear in all copies of the * software, derivative works or modified versions, and any portions * thereof, and that both notices appear in supporting documentation. * * IAN DALL ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS" CONDITION. * IAN DALL DISCLAIMS ANY LIABILITY OF ANY KIND FOR ANY DAMAGES * WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE. */