INSTALLATION NOTES for NetBSD/mvme68k 1.1 Be sure to read _ALL_ of this document before you try to install NetBSD/mvme68k. What is NetBSD? ---- -- ------ NetBSD is a Berkeley Networking Release 2 (Net/2) and 4.4BSD-Lite -derived Operating System. It is a fully functional UN*X-like system which runs on many architectures and is being ported to more. NetBSD, as the name implies, is a creation of the members of the network community and without the net it's likely that this release wouldn't have come about. NetBSD 1.1 is a evolutionary release which contains a over a year of changes to the kernel, user-level utilities, and documentation. Continuing the multi-platform tradition, NetBSD has added ports to atari and mvme68k based machines. Kernel interfaces have continued to be refined, and now several subsystems and device drivers are shared among the different ports. We can look for this trend to continue. NetBSD 1.1 has significantly enhanced the binary emulation subsystem (which includes iBCS2, Linux, OSF/1, SunOS, SVR4, Solaris and Ultrix compatibility) and several kernel subsystems have been generalized to support this more readily. The binary emulation strategy is aimed at making the emulation as accurate as possible. NetBSD 1.1 is also the first release to see machine-independent disk striping. The concatenated disk driver (ccd), which was previously supported only by the hp300 port, has been vastly improved. Many bugs were fixed, and explicit references to device-dependent routines were 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 unlimiting the number of component devices. Many new user programs have been added in NetBSD 1.1, as well, bringing it closer to our goal of supplying a complete UN*X-like environment. 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 corporation 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. We believe that the NetBSD Foundation will help improve the quality of NetBSD by: * having a 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/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.funet.fi Anonymous FTP Anon-FTP path: pub/unix/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.1 Release Contents: ------ --- ------- -------- The NetBSD 1.1 release is organized in the following way: .../NetBSD-1.1/ BUGS Known bugs list (incomplete and out of date). CHANGES Changes since NetBSD's last release (and before). LAST_MINUTE Last minute changes. MIRRORS A list of sites that mirror the NetBSD 1.1 distribution. README.files README describing the distribution's contents. TODO NetBSD's todo list (incomplete and out of date). patches/ Post-release source code patches. source/ Source distribution sets; see below. In addition to the files and directories listed above, there is one directory per architecture, for each of the architectures that NetBSD 1.1 has a binary distribution for. There are also 'README.export-control' files sprinkled liberally throughout the distribution tree, which point out that there are some portions of the distribution (e.g. those containing crypt(3)) that should not be exported from the United States, and that if you do export them, it's your fault, not ours. The source distribution sets can be found in subdirectories of the "source" subdirectory of the distribution tree. They contain the complete sources to the system, 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: gsrc11 This set contains the "gnu" sources, including the source for the compiler, assembler, groff, and the other GNU utilities in the binary distribution sets. [ 7.7M gzipped, 32.0M uncompressed ] ksrc11 This set contains the sources to the NetBSD 1.1 kernel, config(8), config.old(8) and dbsym(8). [ 4.5M gzipped, 20.8M uncompressed ] ssrc11 This set contains the "share" sources, which include the sources for the man pages not associated with any particular program, the sources for the typesettable document set, the dictionaries, and more. [ 2.3M gzipped, 8.5M uncompressed ] src11 This set contains all of the NetBSD 1.1 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) 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. Installing the NetBSD System: ---------- --- ------ ------ $NetBSD: README,v 1.1.1.1.2.2 1995/10/20 02:10:17 chuck Exp $ NetBSD/mvme68k port README for NetBSD 1.1 supported environment: Motorola makes a number of m68k VME cards. This port currently only works on the m68030 based VME147 card (diskless only for now). requirements: - VME147 card - a machine to connect the console to - network connection - NFS server (to serve root and swap) future plans: - VME147 scsi disk support how to boot: Booting NetBSD/mvme68k on a VME147 is somewhat painful because the ROM doesn't know how to talk to the ethernet chip. I have solved this problem by downloading a bootstrap into RAM via the console line. First, you will need a mvme68k NFS mountable /usr and root directory. Version 1.1 of NetBSD/mvme68k consists of the following files: export_exec_mvme68k.tar.gz: /export/exec/mvme68k files (mount on /usr) export_root_mvme68k.tar.gz: /export/root/mvme68k files (mount on /) domestic_mvme68k.tar.gz: domestic crypto stuff (restricted to US) README: this file These files can be ftp'd from ftp.netbsd.org in mvme68k area of the 1.1 distribution. First extract the files in the proper place on your NFS server. Then get the following files: /export/exec/mvme68k/mdec/netboot and /export/exec/mvme68k/mdec/sboot. Copy netboot to /tftpboot/boot.mvme68k of your NFS server machine. Make a symbolic link from the hex encoding of your IP address to that file. For example: lrwxrwxrwx 1 root 11 Apr 13 17:27 80FCA93F.147 -> boot.mvme68k [80FCA93F is the IP address (128.252.169.63) of my vme147.] Make sure you've got the right info in /etc/ethers and /etc/bootparams on your server. Now, bring up your 147. You should have the "bug" prompt: COLD Start Onboard RAM start = $00000000, stop = $007FFFFF 147-Bug> Make sure the "stop" looks ok (if you've got 8MB you should have the same value as I). Also make sure the clock is ticking: 147-Bug>time Sunday 5/30/27 16:25:14 147-Bug>time Sunday 5/30/27 16:25:15 147-Bug> Looks good. you now need to download "sboot" into RAM. you can either do that through the console line or through a 2nd serial connection. I have my 147 connected to a sun4/110 and I access it via "tip". to load that way do this: lo 0 ~Ccat sboot go 4000 which will look like this: 147-Bug> 147-Bug>lo 0 ~CLocal command? cat sboot away for 11 seconds ! 147-Bug>g 4000 Effective address: 00004000 sboot: serial line bootstrap program (&end = 5fd8) >>> Now, if you want to do it through serial line 1, then connect serial line one to a machine. At the "147-Bug> " prompt do this "tm 1"... you should then login to what ever machine it is connected to. Then hit "^A" to escape to Bug. do "lo 1;x=cat sboot" ... then when that is done you can reconnect "tm 1" and logout. Then do "go 4000" and you've got ">>> " prompt of sboot. Once you've got the ">>> " prompt you can do commands such as: "b" - boot "netbsd" multiuser "b gennetbsd" - boot "gennetbsd" multiuser "b -s" - boot "netbsd" single user "b gennetbsd -s"- boot "gennetbsd" single user A typical boot looks like this: sboot: serial line bootstrap program (&end = 5fc8) >>> b le0: ethernet address: 8:0:3e:20:cb:87 My ip address is: 128.252.169.63 Server ip address is: 128.252.169.2 3a00 Download was a success! Start @ 0x8000 ... >> NetBSD netboot [$Revision: 1.1.1.1.2.2 $] boot: client addr: 128.252.169.63 boot: client name: vme147 boot: subnet mask: 255.255.0.0 boot: net gateway: 128.252.169.249 boot: server addr: 128.252.169.2 boot: server path: /export/root/vme147 452632+20360+64456+[30120+30477]=0x93809 Start @ 0x88aa ... Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. NetBSD 1.1 (VME147) #4: Thu Oct 12 19:03:10 CDT 1995 chuck@vme147.ccrc.wustl.edu:/ui/netbsd/pain/src/sys/arch/mvme68k/compile/VME147 Motorola MVME147 MC68030 CPU+MMU, ???MHz MC68882 FPU) real mem = 8388608 avail mem = 6823936 using 102 buffers containing 417792 bytes of memory mainbus0 (root) iio0 at mainbus0 addr 0xfffe0000 pcc0 at iio0 offset 0x1000 rev 0 intbvr 0x40 clock0 at iio0 offset 0x7f8 ipl 5 zs0 at iio0 offset 0x3000 ipl 4 le0 at iio0 offset 0x1800 ipl 2 ler2 0x96000 address 08:00:3e:20:cb:87 nfs_boot: using network interface 'le0' nfs_boot: client_addr=0x80fca93f nfs_boot: server_addr=0x80fca902 nfs_boot: hostname=vme147 root on dworkin:/export/root/vme147 root time: 0x30538658 WARNING: clock gained 37 days -- CHECK AND RESET THE DATE! swap on dworkin:/export/swap/vme147 swap size: 0x4000 (blocks) init: copying out path `/sbin/init' 11 Automatic boot in progress: starting file system checks. [etc...] good luck! step by step installation directions: [0] get the distribution [1] unpack export_exec_mvme68k.tar.gz: gunzip, tar xfp, in /export/exec or equiv [2] unpack export_root_mvme68k.tar.gz: gunzip, tar xfp, in /export/root or equiv [3] run "MAKEDEV all" in NFS /export/root/mvme68k/dev directory (may have to add /etc, /usr/etc to the PATH line of MAKEDEV if on non-NetBSD system) [4] fix NFS root's etc/fstab [5] fix NFS root's etc/myname (put your hostname in there) [6] fix NFS root's etc/hosts [7] create the file etc/hostname.le0 with "inet HOSTNAME" in it (replace "HOSTNAME" with your hostname as per etc/hosts) [8] create etc/defaultdomain with your YP domainname (if using YP) [9] adjust etc/localtime symbolic link as needed [10] create etc/mygate with your default router in it (if wanted, also consider turning off routed in etc/netstart) [11] create etc/resolv.conf (if wanted) [12] make sure the mount point for /usr is there (e.g. mkdir /export/root/mvme68k/usr) [13] make sure the var/yp directory is there if you want to run YP [14] boot as described above [note: you may have to add an arp entry for your 147 on your NFS server if your rarpd doesn't add the entry for you. This seems only to be a problem if you are using a NetBSD NFS fileserver. As I use a SunOS fileserver, I don't see this problem.] [15] install domestic stuff if in US [16] have fun Upgrading a previously-installed NetBSD System: --------- - ---------- --------- ------ ------ Upgrading NetBSD/mvme68k is not something someone is likely to do since this is the first real distribution. 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. Alistair G. Crooks has been producing tar file snapshot reports for NetBSD-current users, a very valuable service. Dave Burgess has been maintaining the 386BSD/NetBSD/FreeBSD FAQ for quite some time, and deserves to be recognized for it. The following people (in alphabetical order) have made donations or loans of hardware and/or money, to support NetBSD development, and deserve credit for it: Jason Brazile Dave Burgess Charles Conn Canada Connect Corporation Brian Carlstrom Tom Coulter Charles D. Cranor Demon Internet, UK Greg Gingerich Michael L. Hitch Scott Kaplan Chris Legrow Herb Peyerl Mike Price Thor Lancelot Simon Bill Sommerfeld Paul Southworth Steve Wadlow (If you're not on that list and should be, tell us! We probably were not able to get in touch with you, to verify that you wanted to be listed.) Finally, we thank all of the people who've put sweat and tears into developing NetBSD since its inception in January, 1993. (Obviously, there are a lot more people who deserve thanks here. If you're one of them, and would like to mentioned, tell us!) We are: -- --- (in alphabetical order) The NetBSD core group: J.T. Conklin Charles Hannum Paul Kranenburg The port-masters (and their ports): Allen Briggs (mac68k) Chuck Cranor (mvme68k) Chris G. Demetriou (alpha) Charles Hannum (i386) Chris Hopps (amiga) Paul Kranenburg (sparc) Ted Lemon (pmax) Anders Magnusson (vax) Phil Nelson (pc532) Gordon Ross (sun3) Jason Thorpe (hp300) Leo Weppelman (atari) Supporting cast: Steve Allen John Brezak Dave Burgess Hubert Feyrer Brad Grantham Matthew Green Lawrence Kesteloot John Kohl Paul Mackerras Neil J. McRae Herb Peyerl Matthias Pfaller Chris Provenzano Waldi Ravens Scott Reynolds Wolfgang Solfrank Frank van der Linden Christos Zoulas Legal Mumbo-jumbo: ----- ----- ----- The following notices are required to satisfy the license terms of the software that we have mentioned in this document: This product includes software developed by the University of California, Berkeley and its contributors. This product includes software developed by the Computer Systems Engineering Group at Lawrence Berkeley Laboratory. This product includes software developed by Christopher G. Demetriou. This product includes software developed by Adam Glass. This product includes software developed by Christian E. Hopps. This product includes software developed by Paul Kranenburg. This product includes software developed by John Kohl. This product includes software developed by Terrence R. Lambert. This product includes software developed by Frank van der Linden. This product includes software developed by Philip A. Nelson. This product includes software developed by Jochen Pohl. This product includes software developed by Chris Provenzano. This product includes software developed by Theo de Raadt. This product includes software developed by the David Muir Sharnoff. This product includes software developed by SigmaSoft, Th. Lockert. This product includes software developed by Jason Thorpe. This product includes software developed by TooLs GmbH. This product includes software developed by Christos Zoulas.