INSTALLATION NOTES for NetBSD/sparc 1.2 Be sure to read _ALL_ of this document before you try to install NetBSD/sparc. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.2 improves upon the successful 1.1 release, and adds ... Significant changes include: Continuing the multi-platform tradition, the integration of the DEC Alpha port has been completed, and new ports to ARM and x68k were added. Sparc port supports 4m machines, Amiga port supports DraCo. Standard C Prototypes have been added to the Kernel. Kernel support for the NTP phased lock loop. The PINT (PINT is not TWAIN) SCSI scanner driver interface has been integrated. See http://www.dol-esa.gov/~kstailey/pint for more details. GCC, Libg++, and many other third party programs have been upgraded to more recent versions. Kernel interfaces have continued to be refined, and moreq subsystems and device drivers are shared among the different ports. You can look for this trend to continue. NetBSD 1.2 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. NetBSD 1.2 is also the first release to see machine-independent disk striping. The concatenated disk driver (ccd), which was previously supported only by the hp300 port, has been vastly improved. Many bugs were fixed, and explicit references to device-dependent routines removed and replaced by calls to the generic "vnode operation" routines. In addition, several features were added, including partition support, dynamic configuration and unconfiguration via a user space system utility program, and virtually unlimited number of component devices. Many new user programs have been added in NetBSD 1.2, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. NetBSD 1.2 is the third release for the sparc. Many more sparc models and devices are now supported. In addition to the SunOS 4.1 compatibility present in NetBSD/sparc 1.0, version 1.2 will also run some number of SunOS 5 (SVR4) executables in binary emulation mode. The Future of NetBSD: --- ------ -- ------ The NetBSD Foundation was recently incorporated as a non-profit organization. It's purpose is to encourage, foster and promote the free exchange of computer software, namely the NetBSD Operating System. The foundation will allow for many things to be handled more smoothly than could be done with our previous informal organization. In particular, it provides the framework to deal with other parties that wish to become involved in the NetBSD Project. (IN WHAT WAY? Money, donations, etc) We believe that the NetBSD Foundation will help improve the quality of NetBSD by: * providing better organization to keep track of development efforts, including co-ordination with groups working in related fields. * providing a framework to receive donations of goods and services and to own the resources necessary to run the NetBSD Project. * providing a better position from which to undertake promotional activities. * periodically organizing workshops for developers and other interested people to discuss ongoing work. We hope to have regular releases of the full binary and source trees, but these are difficult to coordinate, especially with all of the architectures which we now support! We hope to support even _more_ hardware in the future, and have a rather large number of other ideas about what can be done to improve NetBSD. We intend to continue our current practice of making the NetBSD-current development source available on a daily or nearly-daily basis. We intend to integrate free, positive changes from whatever sources will provide them, providing that they are well thought-out and increase the usability of the system. Above all, we hope to create a stable and accessible system, and to be responsive to the needs and desires of NetBSD users, because it is for and because of them that NetBSD exists. Sources of NetBSD: ------- -- ------ Host name Services Provided ---- ---- -------- -------- ftp.iastate.edu Anonymous FTP, AFS Anon-FTP path: pub/netbsd AFS path: /afs/iastate.edu/public/ftp/pub/netbsd ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/misc/sup/supfile.example via anonymous FTP and read it as an example. ftp.demon.co.uk Anonymous FTP, possibly SUP Anon-FTP path: pub/BSD/NetBSD SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD ftp.funet.fi Anonymous FTP Anon-FTP path: pub/unix/NetBSD ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD SUP: get the file pub/sup/README.sup via anonymous FTP from ftp.netbsd.org, and read it for instructions. If you wish to become a distribution site for NetBSD, contact mirrors@netbsd.org. NetBSD 1.2 Release Contents: ------ --- ------- -------- The NetBSD 1.2 release is organized in the following way: .../NetBSD-1.2/ 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.2 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures that NetBSD 1.2 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system. The source distribution sets are as follows: dsrc12 This set contains the "domestic" sources. These sources contain export-restricted encryption code and should not be exported from the U.S. [ 140K gzipped, 655K uncompressed ] gsrc12 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.1M gzipped, 30.4M uncompressed ] ksrc12 This set contains the sources to the NetBSD 1.2 kernel, config(8), config.old(8) and dbsym(8). [ 6.0M gzipped, 27.0M uncompressed ] ssrc12 This set contains the "share" sources, which include the sources for the man pages not associated with any particular program, the sources for the typesettable document set, the dictionaries, and more. [ 2.4M gzipped, 8.9M uncompressed ] src12 This set contains all of the NetBSD 1.2 sources which are not mentioned above. [ 9.3M gzipped, 41.6M uncompressed ] It is worth noting that unless all of the source distribution sets are installed (except the domestic set), you can't rebuild and install the system from scratch, straight out of the box. However, all that is required to rebuild the system in that case is a trivial modification to one Makefile. The source distribution sets are distributed as groups of files named "set_name.xx" where "set_name" is the distribution set name, and "xx" is the sequence number of the file, starting with "aa" for the first file in the distribution set, then "ab" for the next, and so on. All of these files except the last one of each set should be exactly 240,640 bytes long. (The last file is just long enough to contain the remainder of the data for that distribution set.) Catted together, the files belonging to a source distribution set comprise a gzipped tar file. If you want to look at list of the files contained in the set, you could use the command: cat set_name.?? | gunzip | tar tvf - or to actually extract the files contained in the set: cat set_name.?? | gunzip | tar xfp - In each of the source distribution set directories, there is a file named "CKSUMS" which contains the checksums of the files in that directory, as generated by the cksum(1) utility. You can use cksum to check the integrity of the archives, if you suspect that one of the files is corrupt and have access to a cksum binary. The sparc-specific portion of the NetBSD 1.2 release is found in the "sparc" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.2/sparc/ binary/ sparc binary distribution sets; see below. security/ sparc security distribution; see below; install/ Base GENERIC kernels, tools, and installation/upgrade scripts. The NetBSD/sparc binary distribution sets contain the binaries which comprise the NetBSD 1.2 release for the sparc. There are seven binary distribution sets, and the "security" distribution set. The binary distribution sets can be found in subdirectories of the "sparc/binary" subdirectory of the NetBSD 1.2 distribution tree, and are as follows: base12 The NetBSD/sparc 1.2 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. [ 8.6M gzipped, 25.8M uncompressed ] comp12 The NetBSD/sparc Compiler tools. All of the tools relating to C, C++, and FORTRAN (yes, there are two!). This set includes the system include files (/usr/include), the linker, the compiler tool chain, and the various system libraries (except the shared libraries, which are included as part of the base set). This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages. [ 6.2M gzipped, 20.9M uncompressed ] etc12 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.) [ 72K gzipped, 368K uncompressed ] games12 This set includes the games and their manual pages. [ 2.9M gzipped, 7.4M uncompressed ] man12 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.9M gzipped, 3.6M uncompressed ] misc12 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.6M uncompressed ] text12 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 0.8M gzipped, 3.1M uncompressed ] xbin12 This set is the X11R6.1 binary and library set. It includes all the programs, fonts and libraries used in the X window system, and is mandatory to use X. [ 11M gzipped, 20M uncompressed ] xcon12 This set is the X11R6.1 contributed software collection, made up from programs in the contrib distribution. [ ? gzipped, ? uncompressed ] xinc12 This set is the X11R6.1 include set. [ 0.3M gzipped, 2.2M uncompressed ] xman12 This set in the X11R6.1 manual set. [ 0.5M gzipped, 2.9M uncompressed ] The sparc security distribution set is named "secr12" and can be found in the "sparc/security" subdirectory of the NetBSD 1.2 distribution tree. It contains crypt.c (the source file for the DES encryption algorithm) and the binaries which depend on it. It can only be found on those sites which carry the complete NetBSD distribution and that can legally obtain it. (Remember, because of United States law, this distribution set may not be exported to locations outside of the United States and Canada.) [ 127K gzipped, 337K uncompressed ] The sparc binary distribution sets are distributed in the same form as the source distribution sets; catted together, the members of a set form a gzipped tar file. Each sparc binary distribution set also has its own "CKSUMS" file, just as the source distribution sets do. The binary sets are "rooted" at /, that is, if you want to extract the binaries "into" your system, i.e. replace the system binaries with them, you have to run the "tar xfp" from /. Also note that if you upgrade or install this way, those programs that you are using at the time will NOT be replaced. If you follow the normal installation or upgrade procedures, this will be taken care of for you. The "sparc/install" directory contains an install script, an upgrade script, a "miniroot" filesystem, and two GENERIC kernels. As well, the distribution cannot be extracted using the SunOS "tar" program so SunOS statically-linked versions of gzip (GNU gzip) and gtar (GNU tar) are provided. NetBSD System Requirements and Supported Devices: ------ ------ ------------ --- --------- ------- NetBSD/sparc 1.2 runs on the following classes of machines: - sun4c (e.g. the SS1, SS1+, SS2, IPC, ELC, IPX, and SLC) - sun4 (e.g. the 4/100, 4/200, and 4/300. note that support for the 4/400 processor is incomplete) - sun4m (e.g. Classic, LX, SS4, SS5, SS10, and SS20) NetBSD/sparc 1.2 does *not* run on these machines (yet): - sun-4/400 (lacking support for the I/O cache, and has ethernet problems) - sun4d (e.g. sparc center 2000) - sun4u (e.g. Ultrasparcs) The minimal configuration requires 4M of RAM and ~60M of disk space. To install the entire system requires much more disk space, and to run X or compile the system, more RAM is recommended. (NetBSD with 4M of RAM feels like Solaris with 4M of RAM.) Note that until you have around 16M of RAM, getting more RAM is more important than getting a faster CPU.) Supported devices include: sun4c sbus video: cgsix, cgthree, and bwtwo frame buffers sun4 video (not thoroughly tested?): P4 on-board bwtwo, and VME cgtwo card serial ports: ttya and ttyb (can be used as console if needed) ethernet: on-board AMD Lance ethernet ("le0"), Sbus AMD Lance ethernet cards, on-board Intel 82586 ethernet (ie0 on 4/100's and 4/200's), VME Intel 82586 ethernet cards SCSI: on-board "esp" SCSI controller (sun4c's, and the 4/300), sbus "esp" SCSI controller, Sun "SUN-3"/"si" VME SCSI controller (polled mode only, slow), Sun "SCSI Weird"/"sw" on-board controller (4/110 only, polled) VME disks: Xylogics 7053 VME/SMD disk controller ("xd"), Xylogics 450/451 VME disk controller ("xy") [note: VME/IPI disks are not supported] sun floppy disk drive on sun4c's sun keyboard and mouse sun4c audio Hardware the we do NOT currently support, but get many questions about: multiprocessor sun4m machines audio drivers for sun4m machines floppy driver for sun4m machines interrupt driven SCSI driver for sun-4/100's and sun-4/200's Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is supported from several media types, including: NFS partitions FTP Tape The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. To prepare for installing via an NFS partition: Place the NetBSD software you wish to install into a directory on an NFS server, and make that directory mountable by the machine which you will be installing NetBSD on. This will probably require modifying the /etc/exports file of the NFS server and resetting mountd, acts which will require superuser privileges. Note the numeric IP address of the NFS server and of the router closest to the the new NetBSD machine, if the NFS server is not on a network which is directly attached to the NetBSD machine. If you are using a diskless setup to install NetBSD on your machine, you can take advantage of the fact that the above has already been done on your machine's server. So, you can conveniently put the NetBSD filesets in your machine's root filesystem on the server where the install program can find them. Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. To prepare for installing via FTP: NOTE: this method of installation is recommended only for those already familiar with using the BSD network-manipulation commands and interfaces. If you aren't, this documentation should help, but is not intended to be all-encompassing. The preparations for this method of installation are easy: all you have to do is make sure that there's some FTP site from which you can retrieve the NetBSD installation when it's time to do the install. You should know the numeric IP address of that site, the numeric IP address of your nearest router if one is necessary Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. To prepare for installing via a tape: To install NetBSD from a tape, you need to somehow get the NetBSD filesets you wish to install on your system on to the appropriate kind of tape, in tar format. If you're making the tape on a UN*X system, the easiest way to do so is: tar cvf where "" is the name of the tape device that describes the tape drive you're using (possibly something like /dev/nrst0, but we make no guarantees 8-). Under SunOS 5.x, this would be something like /dev/rmt/0mbn. Again, your mileage may vary. If you can't figure it out, ask your system administrator. "" are the names of the "set_name.nnn" files which you want to be placed on the tape. Once you have done this, you can proceed to the next step in the installation process, preparing your system for NetBSD installation. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ Before you start you might need to consider your disk configuration to sort out a quirk in SCSI-ID to SD-UNIT mapping that exists on Sun Sparcstations. Upon leaving the factory, SunOS and the OpenBOOT ROM map according to this table: SCSI-ID -> SunOS SD-UNIT 0 sd3 1 sd1 2 sd2 3 sd0 4 sd4 5 sd5 6 sd6 Unlike SunOS and the OpenBOOT ROM, a generic NetBSD kernel numbers scsi drives sequentially as it finds them. The drive with the lowest scsi-id will be called sd0, the next one sd1, etc. To ease the installation process, the default NetBSD kernel in the distribution is setup to match the Sun mapping above by hard-wiring scsi-id#3 to sd0 and scsi-id#0 to sd3. The remaining drives will be dynamically mapped to other sd* numbers. A truely generic NetBSD kernel is also provided as `/netbsd.GENERIC', which will do the standard NetBSD probe ordering. If your configuration differs from the default Sun setup, you can try to use this kernel to complete the installation. NOTE: this is also a concern when you start building your own customised kernels. Your OpenBOOT ROM may need some setup. make sure you boot from `new command mode'. If your machine comes up and gives you a `>' prompt instead of `ok', type: >n ok setenv sunmon-compat? false ok This is needed because netbsd cannot handle the old-mode yet, and will firework on you. Also, you cannot use the security modes of the sparc OpenBOOT ROM. ok setenv security-mode none If you're installing NetBSD/sparc for the first time it's a good idea to look at the partition sizes of disk you intend installing NetBSD on. Asumming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the NetBSD root filesystem partition is about 20MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike SunOS 4.x, there are no restrictions on the size of the swap partition that would render part of your memory unusable). A full binary installation takes about 60MB in `/usr'. Some network devices (`le') allow a choice between operating on a UTP or a AUI port. Automatic detection of which port is actually connected to the wire is not yet fully implemented in this release. This means that you may have to specify a `link-layer directive' during the installation process. The magic is `link0' to force the use of the UTP port, and `link1' to force the use of the AUI port. Installing the NetBSD System: ---------- --- ------ ------ Installing NetBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. There are several ways to install NetBSD onto a disk. The easiest way in terms of preliminary setup is to use the NetBSD miniroot that can be booted off your local disk's swap partition. Alternatively, if your Sparcstation is hooked up in a network you can find a server and arrange for a diskless setup which is a convenient way to install on a machine whose disk does not currently hold a usable operating system (see the section `Installing using a diskless setup' below). Installing using the NetBSD miniroot. The miniroot is a self-contained NetBSD filesystem holding all utilities necessary to install NetBSD on a local disk. It is distributed as a plain file designed to be transferred to a raw disk partition from which it can be booted using the appropriate PROM command. Usually, the miniroot will be loaded into the swap partition of a disk. If needed, you can use any other unused partition, but remember that the partition will then not available during the installation process. Loading the miniroot onto your raw partition is simple. On NetBSD as well as SunOS you use a command like: # dd if=miniroot-12.fs of=/dev/rsd0b bs=20b conv=sync (here `/dev/rsd0b' is assumed to be your swap partition). There's a potential problem here if /dev/rsd0b is actually in use as a swap partition by your currently running system. If you don't have another disk or partition to spare, you can usually get away with running this command anyway after first booting into single-user mode to ensure a quiet system. After transferring the miniroot to disk, bring the system down by: # halt Then boot the miniroot by typing the appropriate command at the PROM: > b sd(,,1)netbsd -s # for sun4 monitors ok boot sd(,,1)netbsd -s # for version 1 OpenBOOT ROMs ok boot disk:b netbsd -s # for version 2 OpenBOOT ROMs If you've loaded the miniroot onto some other disk than `sd0' adapt the boot specifier accordingly, e.g.: ok boot disk1:b netbsd -s to boot from SCSI disk target 1 from a version 2 OpenBOOT ROM. This will cause the kernel contained in the miniroot to be booted. After the initial probe messages you'll asked to start the install or upgrade procedure. Proceed to the section `Running the installation scripts' below. Installing using a diskless setup. First, you must setup a diskless client configuration on a server. 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, you'll have to consult documentation that came with it (on SunOS systems, add_client(8) is a good start). Your Sparcstation expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename composed of the machine's IP address followed by the machine's architecture, separated by a period. For example, a sun4c machine which has been assigned IP address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). You can find the boot program in `/usr/mdec/boot' in the NetBSD/sparc distribution. Unfortunately, it is necessary to install this file differently for sun4 and sun4c clients: the sun4 version needs to have its `a.out' header stripped off (otherwise the machine will crash), while the sun4c version must retain it (otherwise the PROM will complain). Here's an example to illustrate this whole mess: server# cd //usr/mdec if client is a sun4: server# set SKIP=1 server# set KARCH=SUN4 else server# set SKIP=0 server# set KARCH=SUN4C server# dd if=boot of=/tftpboot/boot.sparc.netbsd.$KARCH skip=$SKIP bs=32 server# cd /tftpboot server# ln -s boot.sparc.netbsd.$KARCH 8273900B.$KARCH Note: some versions of Openboot ROMs (sun4c/sun4m) seem to require that the boot program size is nicely rounded. Therefore it may be necessary to strip(8) off the symbol table. After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request (if it comes in) contains the client's name. This name is used in next step, a BOOTPARAM GETFILE request -- sent to the server that responded to the WHOAMI request -- requesting the name and address of the machine that will serve the client's root directory, as well as the path of the client's root on that server. Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corresponding to the root filesystem. If successful, the boot program starts reading from the remote root filesystem in search of the kernel which is then read into memory. As noted above in the section `Preparing your System for NetBSD Installation', you have several options when choosing a location to store the installation filesets. However, the easiest way is to put the *.tar.gz files you want to install into the root directory for your client on the server. Next, unpack `base.tar.gz' and `etc.tar.gz' on the server in the root directory for your machine. If you elect to use a separately NFS-mounted filesystem for `/usr' with your diskless setup, make sure the "./usr" base files in base.tar.gz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing /usr to your server's exported NetBSD "/usr" directory. Also put the kernel and the install/upgrade scripts into the root directory. A few configuration files need to be edited: /etc/hosts Add the IP addresses of both server and client. /etc/myname This files contains the client's hostname; use the same name as in /etc/hosts. /etc/fstab Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 server:/export/exec/sun4.netbsd /usr nfs rw 0 0 Now you must populate the the `/dev' directory for your client. If you server runs SunOS 4.x, you can simply change your working directory to `/dev' and run the MAKEDEV script: `sh MAKEDEV all'. On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error messages about unknown user and groups. These errors are inconsequential for the purpose of installing NetBSD. However, you may want to correct them if you plan to use the diskless setup regularly. In that case, you may re-run MAKEDEV on your NetBSD machine once it has booted. Boot your workstation from the server by entering the appropriate `boot' command at the monitor prompt. Depending on the PROM version in your machine, this command takes one of the following forms: > b le()netbsd -s # for sun4 monitors ok boot le()netbsd -s # for version 1 OpenBOOT ROMs ok boot net netbsd -s # for version 2 OpenBOOT ROMs This will boot the NetBSD kernel in single-user mode. [[ NOTE: the latter two examples assume you operate the OpenBOOT ROM in "new command mode". If your machine comes up and gives you a `>' prompt instead of `ok', type: >n # enter native OpenBOOT mode ok setenv sunmon-compat? false # make it permanent ok ]] If you use a diskless setup with a separately NFS-mounted /usr filesystem, mount /usr by hand now: netbsd# mount /usr At this point, it's worth checking the disk label and partition sizes on the disk you want to install NetBSD onto. NetBSD understands SunOS-style disklabels, so if your disk was previously used by SunOS there will be a usable label on it. Use `disklabel -e ' (where is the device name assigned by the NetBSD kernel, e.g. `sd0') to view and modify the partition sizes. See the section `Preparing your System for NetBSD Installation' above for suggestions about disk partition sizes. Make sure all your partitions start and end on cylinder boundaries. NOTE: if you are installing on a SCSI disk that does *not* have a SunOS or NetBSD label on it, you may still be able to use disklabel(8) but you'll have to create all partitions from scratch. If your disk is listed in `/etc/disktab', you may use the entry (which in most cases only defines a `c' partition to describe the whole disk) to put an initial label on the disk. DO NOT USE `disklabel -r ...' TO INITIALIZE YOUR DISK LABEL; THIS WILL LEAD TO UNPREDICTABLE RESULTS. This deficiency will be fixed in a next release. Here follows an example of what you'll see while in the dislabel editor. Do not touch any of the parameters except for the `label: ' entry and the actual partition size information at the bottom (the lines starting with `a:', `b:', ...). The size and offset fields are given in sector units. Be sure to make these numbers multiples of the of the number of sectors per cylinder: the kernel might be picky about these things, but aside from this you'll have the least chance of wasting disk space. Partitions on which you intend to have a mountable filesystem, should be given fstype `4.2BSD'. Remember, the `c' partition should describe the whole disk. The `(Cyl. x - y)' info that appears after the hash (`#') character is treated as a comment and need not be filled in when altering partitions. Special note: the line containing `8 partitions:' is best left alone, even if you define less then eight partitions. If this line displays a different number and the program complains about it (after you leave the editor), then try setting it to `8 partitions:'. netbsd# disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: Hold Your Breath flags: bytes/sector: 512 sectors/track: 64 tracks/cylinder: 7 sectors/cylinder: 448 cylinders: 1429 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: #size offset fstype [fsize bsize cpg] a: 50176 0 4.2BSD 0 0 0 # (Cyl. 0 - 111) b: 64512 50176 swap # (Cyl. 112 - 255) c: 640192 0 unknown # (Cyl. 0 - 1428) d: 525504 114688 4.2BSD 0 0 0 # (Cyl. 256 - 1428) If you are upgrading a NetBSD installation, start the upgrade script: netbsd# sh upgrade.sh else, start the installation script: netbsd# sh install.sh Running the installation scripts. The installation scripts will do most of the work of transferring the system from the distribution sets onto your disk. You will frequently be asked for confirmation before the script proceeds with each phase of the installation process. Occasionally, you'll have to provide a piece of information such as the name of the disk you want to install on or IP addresses and domain names you want to assign. If your system has more than one disk, you may want to look at the output of the dmesg(8) command to see how your disks have been identified by the kernel. The installation script goes through the following phases: - determination of the disk to install NetBSD on - checking of the partition information on the disk - creating and mounting the NetBSD filesystems - setup of IP configuration - extraction of the distribution tar files - installation of boot programs Now try a reboot. Initially I'd suggest you "boot sd()netbsd -bs", then try multiuser after that. If you boot single-user the NetBSD incantation to make the root filesystem writable is netbsd# mount -u /dev/sd0a / The Sun monitor might have been setup to instruct the boot program to load a file called "vmunix". On OpenBOOT ROM systems you can change it to load "netbsd" instead using the following commands: On version 1 OpenBOOT ROMs: >n ok setenv boot-from sd(0,0,0)netbsd ok On version 2 OpenBOOT ROMs: ok setenv boot-file netbsd ok setenv boot-device /sbus/esp/sd@0,0 Congratulations, you have successfully installed NetBSD 1.2. When you reboot into NetBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. Some of the files in the NetBSD 1.2 distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified. If you are unfamiliar with UN*X-like system administration, it's recommended that you buy a book that discusses it. Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ To upgrade to NetBSD 1.2 from a previous version follow the instructions in the section `Installing NetBSD', but run the script `upgrade.sh' in stead of `install.sh'. The upgrade script will use the existing disk partitions to install the new system in, and also preserves the files in `/etc'. Using online NetBSD documentation ----- ------ ------ ------------- Documentation is available if you first install the manual distribution set. Traditionally, the UN*X "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: ------------- Registration? What's that? If you've got something to say, do so! We'd like your input. There are various mailing lists available via the mailing list server at . To get help on using the mailing list server, send mail to that address with an empty body, and it will reply with instructions. There are various mailing lists set up to deal with comments and questions about this release. Please send comments to: netbsd-comments@NetBSD.ORG To report bugs, use the 'send-pr' command shipped with NetBSD, and fill in as much information about the problem as you can. Good bug reports include lots of details. Additionally, bug reports can be sent by mail to: netbsd-bugs@NetBSD.ORG Use of 'send-pr' is encouraged, however, because bugs reported with it are entered into the NetBSD bugs database, and thus can't slip through the cracks. There are also port-specific mailing lists, to discuss aspects of each port of NetBSD. Use majordomo to find their addresses. If you're interested in doing a serious amount of work on a specific port, you probably should contact the "owner" of that port (listed below). If you'd like to help with this effort, and have an idea as to how you could be useful, send mail and/or subscribe to: netbsd-help@NetBSD.ORG As a favor, please avoid mailing huge documents or files to these mailing lists. Instead, put the material you would have sent up for FTP somewhere, then mail the appropriate list about it, or, if you'd rather not do that, mail the list saying you'll send the data to those who want it. Thanks go to: ------ -- -- Members and former members of UCB's Computer Systems Research Group, including (but not limited to): Keith Bostic Ralph Campbell Mike Karels Marshall Kirk McKusick for their ongoing work on BSD systems, support, and encouragement. Also, our thanks go to: Mike Hibler Rick Macklem Jan-Simon Pendry Chris Torek for answering lots of questions, fixing bugs, and doing the various work they've done. UC Berkeley's Experimental Computing Facility provided a home for sun-lamp in the past, people to look after it, and a sense of humor. Rob Robertson, too, has added his unique sense of humor to things, and for a long time provided the primary FTP site for NetBSD. Without CVS, this project would be impossible to manage, so our hats go off to Brian Berliner, Jeff Polk, and the various other people who've had a hand in making CVS a useful tool. Alistair G. Crooks has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Bay Area Internet Solutions Jason Brazile Dave Burgess Canada Connect Corporation Charles Conn Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Easynet, UK Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow MS Macro System GmbH, Germany 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): Allen Briggs (mac68k) Mark Brinicombe (arm32) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Anders Magnusson (vax) Phil Nelson (pc532) Masaru Oki (x68k) Gordon Ross (sun3) Jonathan Stone (pmax) Jason Thorpe (hp300) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Dave Burgess Bernd Ernesti Hubert Feyrer Adam Glass Brad Grantham Matthew Green Michael L. Hitch Lawrence Kesteloot John Kohl Ted Lemon Paul Mackerras Neil J. McRae Perry Metzger Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Thor Lancelot Simon Wolfgang Solfrank Ignatios Souvatzis Frank van der Linden 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 Christopher G. Demetriou for the NetBSD Project. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by John Kohl. This product includes software developed by Paul Kranenburg. This product includes software developed by Terrence R. Lambert. This product includes software developed for the NetBSD Project by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl for the NetBSD Project. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed for the NetBSD Project by Jason R. Thorpe. This product includes software developed by Jason R. Thorpe for And Communications, http://www.and.com/ This product includes software developed by TooLs GmbH. This product includes software developed for the NetBSD Project by John M. Vinopal. This product includes software developed by Christos Zoulas. This product includes software developed by the Alice Group. This product includes software developed by Charles D. Cranor. This product includes software developed by Peter Galbavy. This product includes software developed by Rolf Grossmann. This product includes software developed by David Miller. This product includes software developed by Gordon W. Ross. 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.