INSTALLATION NOTES for NetBSD/sparc 1.0 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 system. It is a fully functional UN*X-like system which runs on several 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.0 is a milestone release. The hardest part of the 4.4BSD-Lite integration, the kernel, has been completed and has been running in "production use" for quite some time. Also, NetBSD 1.0 is the first true multi-architecture release of NetBSD. At the time of NetBSD 0.9, the i386 port was considered 'production quality' and the hp300 port was barely working. The NetBSD 1.0 source supports nine architectures, and complete binary releases for most of them will be made available. NetBSD 1.0 supports many new and improved features, the most important relating to file systems. New and improved versions of both the Berkeley Fast File System and the free implementation of the NFS protocol were provided, as part of the 4.4-Lite release. The new versions include such improvements as support for 64-bit file sizes, for local files, and "lease" support for NFS, to improve performance. In addition to the file system improvements, many other parts of the system have been improved considerably. For instance, the virtual memory code has substantially improved performance, and many of the kernel's interfaces have been cleaned up. Many new user programs have been added in NetBSD 1.0, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. Additionally, support for shared libraries has been added, for most architectures, allowing a significant savings in both RAM consumption and disk space. NetBSD 1.0 is the first release for the sparc, although numerous people have been running "snapshots" for some time. It has all the standard NetBSD features, plus you can also enable SunOS binary compatibility in the kernel which will run more than 95% of SunOS executables. The Future of NetBSD: --- ------ -- ------ 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. This includes integrating the remainder of the 4.4BSD-Lite tape, as quickly as we can ensure that everything works properly. 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/NetBSD-1.0 AFS path: /afs/iastate.edu/public/ftp/pub/netbsd/NetBSD-1.0 ftp.eecs.umich.edu Anonymous FTP Anon-FTP path: BSD/NetBSD/NetBSD-1.0 gatekeeper.dec.com Anonymous FTP Anon-FTP path: pub/BSD/NetBSD/NetBSD-1.0 wipux2.wifo.uni-mannheim.de Anonymous FTP, SUP Anon-FTP path: pub/NetBSD/NetBSD-1.0 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/NetBSD-1.0 SUP: contact peter@demon.net for SUP server status/information ftp.uni-regensburg.de Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.unit.no Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.stacken.kth.se Anonymous FTP Anon-FTP path: pub/OS/NetBSD/NetBSD-1.0 flick.lerc.nasa.gov Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 coombs.anu.edu.au Anonymous FTP Anon-FTP path: pub/NetBSD/NetBSD-1.0 ftp.netbsd.org Anonymous FTP, SUP Anon-FTP path: pub/NetBSD/NetBSD-1.0 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 Chris Demetriou . NetBSD 1.0 Release Contents: ------ --- ------- -------- The NetBSD 1.0 release is organized in the following way: .../NetBSD-1.0/ 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.0 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.0 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, excluding those portions which should not be exported from the U.S. (Those are contained in each architecture's "security" binary distribution set.) The source distribution sets are as follows: gsrc10 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.7M gzipped, 32.0M uncompressed ] ksrc10 This set contains the sources to the NetBSD 1.0 kernel, config(8), config.new(8) and dbsym(8). [ 4.5M gzipped, 20.8M uncompressed ] ssrc10 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.3M gzipped, 8.5M uncompressed ] src10 This set contains all of the NetBSD 1.0 sources which are not mentioned above. [ 7.1M gzipped, 33.4M uncompressed ] It is worth noting that unless all of the source distribution sets are installed, 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) command. 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.0 release is found in the "sparc" subdirectory of the distribution. That subdirectory is laid out as follows: .../NetBSD-1.0/sparc/ binary/ sparc binary distribution sets; see below. security/ sparc security distribution; see below; install/ Base GENERIC kernels, tools, and installation script. The NetBSD/sparc binary distribution sets contain the binaries which comprise the NetBSD 1.0 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.0 distribution tree, and are as follows: base10 The NetBSD/sparc 1.0 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.3M gzipped, 22.7M uncompressed ] comp10 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. [ 4.9M gzipped, 15.9M uncompressed ] etc10 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.) [ 50K gzipped, 285K uncompressed ] games10 This set includes the games and their manual pages. [ 1.2M gzipped, 3.3M uncompressed ] man10 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.7M gzipped, 2.9M uncompressed ] misc10 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.7M gzipped, 5.9M uncompressed ] text10 This set includes NetBSD's text processing tools, including groff, all related programs, and their manual pages. [ 0.8M gzipped, 3.1M uncompressed ] The sparc security distribution set is named "secr10" and can be found in the "sparc/security" subdirectory of the NetBSD 1.0 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, 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.0 runs on Sun4c class machines only, which includes the SS1, SS1+, SS2, IPC, ELC, IPX, and the SLC. It does not run on Sun4, Sun4m, or Sun4d machines. 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: Video: cgthree, cgsix, and bwtwo frame buffers Serial ports: ttya and ttyb On-board AMD Lance ethernet Some SCSI CD-ROM drives Sun keyboard and mouse Hardware the we do NOT currently support, but get many questions about: The floppy drive. The next release will likely run on many more machines. In particular, some Sun4 support will be there, and perhaps even Sun4m. Getting the NetBSD System on to Useful Media: ------- --- ------ ------ -- -- ------ ----- Installation is done from SunOS, or a previous NetBSD install. Preparing your System for NetBSD Installation: --------- ---- ------ --- ------ ------------ You will need SunOS to install NetBSD. 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. You need a SunOS machine to install NetBSD. You also need at least the following pieces: the *.tar.gz files you want to install (as a minimum, base.tar.gz) gzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary the "install.sh" script a "/boot" file from a SunOS sun4c machine a kernel, most likely "netbsd.id3_scsi" All these pieces, except "/boot", are supplied in the NetBSD/sparc distribution. You need to format and partition the disk using SunOS (since NetBSD/sparc uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. sd2a 28140 0 / sd2b 16170 28140 swap sd2c 204540 0 `whole disk' sd2g 160230 44310 /usr BTW, These are not recommended sizes. They simply match the first (tiny) disk that NetBSD/sparc ran on. Use SunOS to newfs the partitions which will have filesystems on them. (NetBSD's filesystem format is identical to SunOS). sunos# newfs /dev/rsd2a [... lots of output] sunos# newfs /dev/rsd2g [... lots of output] NOTE: If you are able to, there is a performance benefit from newfs'ing using NetBSD. If you newfs using the NetBSD newfs command, be sure to use the -O flag for your / partition, so that newfs will use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem format. If you forget, you will not be able to boot -- the SunOS boot blocks do not understand the extended 4.4BSD filesystem format. Mount those partitions in a tree formation, under /mnt; ie: sunos# df Filesystem kbytes used avail capacity Mounted on [...] /dev/sd2a 11501 0 11501 0% /mnt /dev/sd2g 179529 0 179529 0% /mnt/usr Place a standard SunOS "/boot" program in /mnt (your new root partition), and use the SunOS command "installboot" to make it work. The installboot man page says to do something like this: sunos# cp /boot /mnt/boot sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a You can now extract the provided "*.tar.gz files onto your disk. The provided script, "install.sh" will help you: sunos# ls -FC base.tar.gz etc.tar.gz man.tar.gz secr.tar.gz comp.tar.gz games.tar.gz misc.tar.gz text.tar.gz install.sh netbsd.id3_scsi sunos# ./install.sh [...] This script NEEDS gzip and gtar (GNU gzip and GNU tar) on your execution path! The tar files are in a "new format" that includes directory information, and SunOS tar will not read them. Statically linked versions of these programs for SunOS are supplied in the distribution. After the files have been extracted, repair /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of course :-) The install script copies the kernel called "netbsd.id3_scsi" to /mnt/netbsd. Two sample kernels are supplied: "netbsd.first_scsi" and "netbsd.id3_scsi". An explanation follows: Unlike SunOS and the OpenBOOT ROM, NetBSD numbers scsi drives sequentially as it finds them. The drive with the lowest scsi-id will be called sd0, the next one sd1, etc. 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 If you have two drives, NetBSD and the OpenBOOT ROM will likely disagree. The "netbsd.id3_scsi" kernel gets around this problem by hard-wiring scsi-id#3 to sd0. The remaining drives will be dynamically mapped to other sd* numbers. If you have more than one drive you will want to use this kernel. If you know what you are doing the other kernel, "netbsd.first_scsi" will do the standard NetBSD probe ordering. 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 Now try a reboot. (If needed, swap your scsi id's first). 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 read-write is netbsd# mount -u /dev/sd0a / The OpenBOOT ROM normally tries to load a file called "vmunix". You can change it to load NetBSD instead using the following command: >n ok setenv boot-from sd(0,0,0)netbsd ok Congratulations, you have successfully installed NetBSD 1.0. 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.0 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: --------- - ---------- --------- ------ ------ Upgrading NetBSD/sparc is not something someone is likely to do, since this is the first real distribution. Since a number of critical interfaces have changed quite significantly, your best bet is to reinstall completely, perhaps saving a few files in /etc and /usr/local. 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 has provided a home for sun-lamp, 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. 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: Brian Carlstrom Demon Internet, UK Michael L. Hitch Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld 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.) Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. 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 team: Chris G. Demetriou Theo de Raadt Adam Glass Charles Hannum The port-masters (and their ports): Allen Briggs (mac68k) (and the rest of the 'Alice' group) Theo de Raadt (sparc) Charles Hannum (i386, hp300) Chris Hopps (amiga) Adam Glass (pmax) Paul Mackerras (da30) Anders Magnusson (vax) Phil Nelson (pc532) Gordon Ross (sun3) Supporting cast: Steve Allen John Brezak Dave Burgess J.T. Conklin Hubert Feyrer Brad Grantham Lawrence Kesteloot Paul Kranenburg Herb Peyerl Matthias Pfaller Chris Provenzano Wolfgang Solfrank 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 Paul Kranenburg. This product includes software developed by Philip A. Nelson.