INSTALLATION NOTES for NetBSD/vax 1.3 Be sure to read _ALL_ of this document before you try to install NetBSD/vax. 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 second public release of NetBSD for the VAX. 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 vax-specific portion of the NetBSD 1.3 release is found in the "vax" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.3/vax/ INSTALL Installation notes; this file. binary/ vax binary distribution sets; see below. security/ vax security distribution; see below. tk50/ Files to install from tape. rx50/ Files to install from RX50 floppy. rx33/ Files to install from RX33 floppy. netboot/ Files needed when netbooting. .../vax/netboot/ There are a couple of files in the netboot directory; the boot program in different flavours, a generic kernel and a miniroot image. The files are described below: boot The NetBSD loader program, needed to load the kernel or any standalone program from disk/tape/net. boot.mopformat The same as above, but in MOP format. gennetbsd.gz A generic NetBSD/vax kernel, gzipped. miniroot.tar.gz A tar'ed and gzipped miniroot, unpack this to get a small netbooted environment. .../vax/tk50/ .../vax/rx50/ .../vax/rx33/ In these directories there are splitted files of both a small boot utility filesystem and a miniroot. See the section for installing to get more about this. .../vax/binary/ The NetBSD/vax binary distribution sets contain the binaries which comprise the NetBSD 1.3 release for the vax. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in the "vax/binary" subdirectory of the NetBSD 1.3 distribution tree, and are as follows: base13 The NetBSD/vax 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. [ 7.6M gzipped, 21.5M uncompressed ] comp13 The NetBSD/vax 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. [ 5.4M gzipped, 17.2M uncompressed ] etc13 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.) [ 68K gzipped, 350K uncompressed ] games13 This set includes the games and their manual pages. [ 2.9M gzipped, 7.0M uncompressed ] man13 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. [ 0.9K gzipped, 3.5M uncompressed ] misc13 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.9M gzipped, 6.5M uncompressed ] text13 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 0.8M gzipped, 2.9M uncompressed ] .../vax/security/ The vax security distribution set is named "secr13" and can be found in the "vax/security" subdirectory of the NetBSD 1.3 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, it may not be legal to distribute this set to locations outside of the United States and Canada.) [ 128K gzipped, 275K uncompressed ] The vax binary distribution sets are distributed as gzipped tar files. Each vax 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" flags 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: ------ ------ ------------ --- --------- ------- Hardware supported by NetBSD/vax 1.3 includes (but may not be limited to): CPU types: VAX 11/750, VAX 11/78{0,5}, VAX 8200/8250/8300/8350, VAX 8600/8650, MicroVAX II, MicroVAX III, MicroVAX 3600/3800/3900, MicroVAX 3300/3400/3500, MicroVAX 2000/VAXstation 2000 and some VAXstation 3100. Networking: DEUNA/DELUA Unibus ethernet, DEQNA/DELQA Q22 bus ethernet and LANCE chip where available. Serial lines: DHU11/DHV11/DL11/DLV11/DZ11/DZQ11/DZV11 Unibus/Q22 bus asynchronous lines and DZ11-compatible lines on VAXstations. Disks: UDA50 Unibus MSCP controller, KDA50/RQDX1/2/3 Q22 bus MSCP controller, KDB50 BI-bus MSCP controller, MFM and SCSI controllers on VAXstations, RP04/05/06/07 and RM02/03/05/80 Massbus disks, and Console RL02 on VAX 8600. Some third-party controllers are also known to work, other do not. Tapes: TMSCP on Q22 bus (TK50/70), SCSI tapes on VAXstations. The minimal configuration requires 2M of RAM and ~40MB of disk space, but the installation requires at least 4MB RAM and you probably do not want to run with anything less than that. Here is a table of recommended HD partition sizes for a full install: partition: advise needed root (/) 20M 10M user (/usr) 80M 45M swap (2 or 3 * RAM) Anything else is up to you! Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: * Tape * NFS * Floppy * FTP Note that installing on a "bare" machine requires some bootable device; either a tape or floppy drive or Sun-compatible NFS server with MOP capabilities. (Yes, NetBSD/vax uses the same netboot principles as Sun's does). The procedure for transferring the distribution sets onto installation media depends on the type of media. The most is up to you, depending what you want to install, but preferred are to do the installation over network as soon as the miniroot is installed. * Creating boot tapes: Fetch the two files from .../NetBSD-1.3/vax/tk50. Write them onto the tape, first file1 and then file2. Under Ultrix this is done just like this: mt -f /dev/rmt0h rewind dd if=tk50-file1-1.3 of=/dev/nrmt0h dd if=tk50-file2-1.3 of=/dev/rmt0h mt -f /dev/rmt0h rewoffl Under NetBSD this is done the same way, except for the tape name: mt -f /dev/rmt8 rewind dd if=tk50-file1-1.3 of=/dev/nrmt8 dd if=tk50-file2-1.3 of=/dev/rmt8 mt -f /dev/rmt8 rewoffl Of course, if you have another tape unit than 0 you have to use the corresponding unit number. If you are using any other OS to create bootable tapes, remember that the blocksize _must_ be 512 for the file to be bootable! Otherwise it just won't work. * Creating boot floppies: Fetch the files from .../NetBSD-1.3/vax/rx{50,33} depending of which floppy you have. There are three or seven files depending of the density of your floppies. Then just write the floppies using dd (under Unix, if you are creating floppies from DOS use some nice utility for that). There are one bootable floppy and a splitted miniroot image. * Booting from NFS server: All VAXen that can boot over network uses MOP, a DEC protocol. To be able to use MOP, a MOP daemon must be present on one of the machines on the local network. The boot principle is: * The VS2000 broadcast a wish to load an image. * A mopd answers and send the boot program to the VAX. * The boot program does rarp requests, mounts the root filesystem and loads the kernel. * The kernel is loaded and starts executing. If your machine has a disk and network connection, 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). You also must install a MOP loader. If you are booting from another NetBSD machine, MOP are included in the distribution, otherwise you may have to install a MOP loader. A loader can be found at ftp.stacken.kth.se:/pub/OS/NetBSD/mopd. Fetch the latest and read the installation instructions. The file that should be loaded are called boot and are located in .../NetBSD-1.3/vax/install. If you are not using the mopd written by Mats O Jansson (as the NetBSD are) then you should get the file boot.mopformat instead. The miniroot to start from is the one called miniroot.tar.gz located also in the install directory. Fetch it, unzip and untar it wherever you have your root filesystem. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ VAX 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 CSR address of your disk controller(s) if they are on a Qbus/Unibus. The disk controllers must then be at either 772150 (DUA) or 760334 (DUB). These two addresses are the only recognized by the kernel and boot programs. Also; if you are installing on a VAXstation, you must have a serial console. The builtin graphic console are not yet supported. Installing the NetBSD System: ---------- --- ------ ------ Installing NetBSD/vax may be a little bit complex, but it shouldn't be too hard if you have this document available. Device conventions. NetBSD standalone system addresses devices like 'devicename(adapter, controller, unit, partition)' Known devicenames are: mt - MSCP tape. (TK50, TU81, ...) ts - TSV05/TS11 tape. ra - RA??/RD?? disks/floppies. hp - RP??/RM?? disks. rd - RD?? disks on MicroVAX 2000. sd - SCSI disks. st - SCSI tapes. le - LANCE ethernet controller. You can omit parameters; ra(0,0) refers to disk 0 partition a on default controller. On tapes partition refers to file # on the tape. Example: DUB1 (DEC syntax) swap partition will be referred as ra(1,0,1), DRA2 root partition is hp(2,0). The installation principle is to label the root disk, copy a miniroot filesystem onto the swap partition, boot up from that miniroot filesystem, then create root and the other wanted partitions and put system to it. You will have to deal with 2 different "units", one is just a boot filesystem containing 3 files: boot, copy and edlabel, the other is an image of a miniroot filesystem and can be split into several pieces depending of what you are going to install from. Installation from tape: (MicroVAX II/III) Take your newly created boot tape and just boot from it: >>> B/3 MUA0 This means that you will bring upp boot to aks for boot file from TK50. (MUA0 is DEC naming). It will come up something like 2..1..0.. howto 0x3, bdev 0x12, booting...done. (31248+22252) >> NetBSD/vax boot [970610 23:44] << : At the prompt you type edlabel to label the disk, see below about how to use edlabel. When labeling is finished, halt the computer, bring up the boot program again and this time load copy, see below about how to use copy. Remember that you must copy from the second file (1) on the tape. Now go to step 3. Installation from RX33/RX50. (MicroVAX II/III) The difference between RX33 and RX50 is its size. RX50 is 400k and RX33 is 1200k. To boot from floppy type: >>> B/3 DUxy where x is the controller number and y is device number. You will now get up a prompt like >> NetBSD/vax boot [970610 23:44] << : At the prompt you type edlabel to label the disk, see below about how to use it. When labeling is finished, halt the computer, bring up the boot program again and this time load copy, see below about how to use it. Remember that you are will copy from partition 0 when using floppies. Now go to step 3. Installing over network: You can use the same flags when booting over the net as when booting from local disks; like: ">>>B/3 ESA0" will load boot in ask state. From here you can load any file you want, even copy and edlabel if they are located in the exported root fs. Note 1: Netbooting of MicroVAX II/III systems with DEQNA/DELUA ethernet does not work does not work yet because lack of standalone drivers. Mounting of root and swap over NFS works goos though. Note 2: Mopd won't work on VAXen with de/qe ethernet, due to the lack of bpf support for those interfaces. Booting up miniroot. When copying is ready, bring the boot program up a third time, and this time bring up a real system by telling boot where you put your miniroot _and_ also the generic kernel name. Example: ra(0,1)gennetbsd, boots gennetbsd from swap partition on ra0. When kernel is loaded, you will after a while get a question about Root device?. Respond to this with xx?*, where xx is the device name, ? is the unit number and * tells that the system shall use the swap partition as root partition. Example: Root device? ra0* After that a second question: Enter pathname of shell or RETURN for sh: Just type return. Now you will be in a normal single-user shell, and it's just to newfs your partitions, and start installation. A few things that you must remember to do from miniroot: disklabel -B to install boot blocks. MAKEDEV devices in the newly created root filesystem. Copy gennetbsd and boot from miniroot filesystem to the newly created root filesystem. How to use edlabel: Edlabel is a program to edit disklabels on any disks in a standalone environment. Mostly it is used to set labels when doing initial installation procedure. It is started from boot program prompt. You will here be guided through a session, things with ^^^^ under is typed in by the user, comments are within /* */. >> NetBSD/vax boot [970610 23:44] << : edlabel ^^^^^^^ With this program you can modify everything in the on-disk disklabel. To do something useful you must know the exact geometry of your disk, and have ideas about how you want your partitions to be placed on disk. Some hints: The a partition should be at least ~20000 blocks, the b (swap) is depending on your use of the machine but it should almost never be less than ~32000 blocks. Disk geometry for most DEC disks can be found in the disktab file, and applicable disk names can be found above. Remember that disk names is given as disk(adapt, ctrl, disk, part) when using the installation tools. Label which disk? ra(1,0,0) /* See INSTALL text for device types */ ^^^^^^^^^ getdisklabel: no disk label ra(1,0,0): no disk label (E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : e ^ First set disk type. Valid types are: 0 unknown 1 SMD 2 MSCP 3 old DEC 4 SCSI 5 ESDI 6 ST506 7 HP-IB 8 HP-FL 9 type 9 10 floppy 11 ccd 12 vnd Numeric disk type? [0] 2 /* All disks supported this far is MSCP */ Disk name? [] rd54 ^ /* You must know what type your disk is */ badsect? [n] ^^^^ /* No badsectoring yet */ ecc? [n] /* ECC is automatic, don't care */ removable? [n] /* Removable or not, like RA60 */ Interleave? [0] 1 /* All MSCP disks is seen like 1 interleave */ rpm? [0] 3600 ^ /* 3600 rpm is normal */ trackskew? [0] /* don't care */ cylinderskew? [0] /* don't care */ headswitch? [0] /* don't care */ track-to-track? [0] /* don't care */ drivedata 0? [0] /* don't care */ drivedata 1? [0] /* don't care */ drivedata 2? [0] /* don't care */ drivedata 3? [0] /* don't care */ drivedata 4? [0] /* don't care */ bytes/sector? [0] 512 /* Probably only sive on VAX systems */ ^^^ sectors/track? [0] 17 /* You must know this, check disktab file */ ^^ tracks/cylinder? [0] 15 /* You must know this, check disktab file */ ^^ sectors/cylinder? [0] 255 /* sectors/track * tracks/cylinder */ ^^^ cylinders? [0] 1221 /* You must know this, check disktab file */ ^^^^ a partition: offset? [0] /* Partition sizes are set by you. */ size? [0] 20000 /* Take default sizes from disktab or */ b partition: offset? [0] 20000 /* calculate your own partition sizes */ size? [0] 20000 c partition: offset? [0] size? [0] 311200 d partition: offset? [0] size? [0] e partition: offset? [0] 40000 size? [0] 271200 f partition: offset? [0] size? [0] g partition: offset? [0] size? [0] h partition: offset? [0] size? [0] (E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : s /* Show what you've typed */ ^ disk type 2 (MSCP), rd54: interleave 1, rpm 3600, trackskew 0, cylinderskew 0 headswitch 0, track-to-track 0, drivedata: 0 0 0 0 0 bytes/sector: 512 sectors/track: 17 tracks/cylinder: 15 sectors/cylinder: 255 cylinders: 1221 8 partitions: size offset a: 20000, 0 b: 20000, 20000 c: 311200, 0 d: 0, 0 e: 271200, 40000 f: 0, 0 g: 0, 0 h: 0, 0 (E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : w /* Write label to disk */ This program does not (yet) write bootblocks, only disklabel. Remember to write the bootblocks from the miniroot later with the command "disklabel -B ". (E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : q How to use copy: Copy is a standalone program that can copy multiple volumes from disk/tape to disk/tape. Mostly it is used to copy the miniroot filesystem onto the swap partition during initial installation. You will here be guided through a session, things with ^^^^ under is typed in by the user, comments are within /* */. This is an installation from TK50. >> NetBSD/vax boot [970610 23:44] << : copy ^^^^ copy: This program will read miniroot from tape/floppy/disk and install this miniroot onto disk. Specify the device to read from as xx(N,0), where xx is the device-name and N is the unit-number, e.g. "mt(0,1)" for the first TMSCP-tape (TK50), "ra(2,0)" for the third MSCP-disk/floppy (RX33/RX50) device to read from ? mt(0,1) /* Tape 0, file 1 */ ^^^^^^^^ Specify number of blocks to transfer. Usually this is sizeof(miniroot) / 512. It's safe to transfer more blocks than just the miniroot. number of blocks ? 4096 /* Miniroot size is 4096 block */ ^^^^ If your miniroot is split into volumes, then you must specify the number of blocks per volume. (e.g. 800 blocks per RX50, 2400 blocks per RX33) number of blocks per volume ? [4096] Make sure unit tms(0,1) is online and holds the proper volume. Then type 'g' to Go or 'a' to Abort. OK to go on ? [g/a] g /* g == go, a == abort */ ^ Reading ... Reading of miniroot done. (4096 blocks read) Now specify the device to write miniroot to as xx(N,1) where xx is the drive type and N is the drive number. For example: ra(0,1) refers to MSCP drive #0, b partition Root disk ? : ra(0,1) /* Actually DUA0, partition b (swap) */ ^^^^^^^^^ Initializing partition ... done. (4096 blocks written.) Halt the machine and reboot from distribution media, giving second partition as part to mount as root. Ex: : ra(0,1) for ra disk 0, hp(2,1) for massbuss disk 2 Halt/Reboot the machine NOW. ?02 EXT HLT PC = 001005F3 >>> Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ There are no upgrade program for NetBSD/vax, you will have to upgrade your system by hand. Anyway, here are small hints about how to do it: * First replace the kernel, /boot and the boot blocks with new ones. The boot system has changed since 1.2. * Reboot the system to be sure you run with the new kernel. * Untar the wanted distributions. Remember to use the --unlink flag to tar, otherwise you will run into trouble. * Reboot the system once again. * Now you will (hopefully) be up and running in the new world. 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 at Ludd, University of Lule}, Sweden. This product includes software developed by Gordon W. Ross. This product includes software developed by Ben Harris. This product includes software developed by Adam Glass, David Jones, and Gordon Ross.