diff --git a/distrib/notes/mvme68k/contents b/distrib/notes/mvme68k/contents new file mode 100644 index 000000000000..9f6d94af55fb --- /dev/null +++ b/distrib/notes/mvme68k/contents @@ -0,0 +1,137 @@ +The mvme68k-specific portion of the NetBSD _VER release is found in the +"mvme68k" subdirectory of the distribution. That subdirectory is laid +out as follows: + +.../NetBSD-_VER/mvme68k/ + INSTALL.txt Installation notes; this file. + + install/ Boot programs, a VME147 kernel, + a stand-alone RAMDISK kernel, and + a miniroot filesystem image. + see below. + + binary/ mvme68k binary distribution sets; + see below. + + security/ mvme68k security distribution; + see below. + +.../mvme68k/install/ + +The NetBSD/mvme68k install distribution contains files that can be +used to install NetBSD onto a completely "bare" VME147. The files +in the "mvme68k/install" directory are described below: + + miniroot.gz A gzipped copy of the miniroot filesystem. + This image is to be un-gzipped and copied + into the swap area of a disk. + + netbsd-rd.gz A gzipped copy of the "RAMDISK kernel" + for installing the miniroot filesystem. + + netbsd.gz A gzipped VME147 kernel (for upgrade) + + stboot A tape boot-block, in the form required to + allow 147-Bug to boot from tape. This is the + first segment of a boot tape. + + bootst A copy of the tape boot program, used + as the second segment of a boot tape. + + sboot A copy of the serial boot program. This is + necessary if you don't have a tape drive, + but you _do_ have another system which can + act as a boot and NFS server. This is also + useful if you are installing a diskless + NetBSD/mvme68k system. + + netboot A copy of the network boot program. Used + in conjunction with sboot to get your system + booted over a network. + +These files can be used to make a boot tape suitable for installing +NetBSD/mvme68k. These files can also be used to configure an NFS server +to support installation "over the network". See the section "Getting +the NetBSD System onto Useful Media" for instructions on either method. + +.../mvme68k/binary/ + +The NetBSD/mvme68k binary distribution sets contain the binaries which +comprise the NetBSD _VER release for the VME147. There are seven binary +distribution sets, and the "security" distribution set. The binary +distribution sets are as follows: + + base The NetBSD/mvme68k _VER 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. + [ 9.2M gzipped, 26.5M uncompressed ] + + comp The NetBSD/mvme68k 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. + [ 6.9M gzipped, 24.1M uncompressed ] + + etc This distribution set contains the system configuration + files that reside in /etc and in several other places. + This set MUST be installed if you are installing the + system from scratch, but should NOT be used if you are + upgrading. (If you are upgrading, it's recommended that + you get a copy of this set and CAREFULLY upgrade your + configuration files by hand.) + [ 53K gzipped, 327K uncompressed ] + + games This set includes the games and their manual pages. + [ 2.9M gzipped, 7.5M uncompressed ] + + man This set includes all of the manual pages for the + binaries and other software contained in the base set. + Note that it does not include any of the manual pages + that are included in the other sets. + [ 2.5K gzipped, 10.3M uncompressed ] + + misc This set includes the system dictionaries (which are + rather large), the typesettable document set, and + man pages for other architectures which happen to be + installed from the source tree by default. + [ 2.3M gzipped, 8.7M uncompressed ] + + text This set includes NetBSD's text processing tools, + including groff, all related programs, and their + manual pages. + [ 1.0M gzipped, 3.9M uncompressed ] + +.../mvme68k/security/ + +The mvme68k security distribution set is named "secr" and can be found +in the "mvme68k/security" subdirectory of the NetBSD _VER distribution +tree. It contains executables which are built in the "src/domestic" portion +of 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 mvme68k binary distribution sets are distributed as gzipped tar files. +Each mvme68k 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" flag is very important! + +For best results, it is recommended that you follow the installation +and/or upgrade procedures documented in this file. diff --git a/distrib/notes/mvme68k/hardware b/distrib/notes/mvme68k/hardware new file mode 100644 index 000000000000..fec409acc6a9 --- /dev/null +++ b/distrib/notes/mvme68k/hardware @@ -0,0 +1,39 @@ +NetBSD/mvme68k _VER runs on Motorola MVME147 boards. + +The minimal configuration requires 4M of RAM and ~100MB of disk space. +To install the entire system requires much more disk space (approx. +200MB additional space is necessary for full sources. Double that if you +want to recompile it all!). To run X (clients only) or compile the system, +more RAM is recommended. Good performance requires 8MB of RAM, or 16 MB +when running the X Window System. + +Here is a table of recommended HD partition sizes for a full install: + partition: advise needed + root (/) 20M 12M + user (/usr) 100M 80M + swap (2 or 3 * RAM) 8M + Anything else is up to you! + +Note that the mvme68k installation procedure uses a `miniroot' image +which is placed into the swap area of the disk. The swap partition +must be large enough to hold this miniroot image (> 6Mb). + +The following VME147 hardware is supported: + + Serial ports (RS232): + built-in console, tty01, tty02 and tty03 + + Parallel port: + On-board centronics style printer port + + Network interfaces: + On-board Lance Ethernet (le) + + SCSI: (Most SCSI disks, tapes, CD-ROMs, etc.) + On-board wd33c93 SCSI bus interface chip (async only for now). + + Miscellaneous: + Battery-backed real-time clock. + VMEbus RAM cards. + +If it's not on this list, there is no support for it in this release. diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install new file mode 100644 index 000000000000..94e0eda39336 --- /dev/null +++ b/distrib/notes/mvme68k/install @@ -0,0 +1,502 @@ +Installing NetBSD is a relatively complex process, but if you have +this document in hand it should not be too difficult. + +There are several ways to install NetBSD onto your disk. If your +machine has a tape drive the easiest way is "Installing from tape" +(details below). If your machine is on a network with a suitable +NFS server, then "Installing from NFS" is the next best method. +Otherwise, if you have another VME147 machine running NetBSD you can +initialize the disk on that machine and then move the disk. + + +* Installing from tape: + +Create the NetBSD/mvme68k _VER boot tape as described in the section +entitled "Preparing a boot tape". Then, with the tape in the drive, +type the following at the 147Bug prompt: + +--> 147-Bug> bo 5 + +As mentioned earlier, this assumes your tape is jumpered for SCSI-id 5. + +As the tape loads (which may take 20 to 30 seconds), you will see a +series of status messages. It may be useful if you can capture these +messages to a file, or a scrollable xterm window. In particular, you +should make a note of the lines which describe the geometry of the +SCSI disks detected by NetBSD. They are of the form: + +sd0 at scsibus0 targ 0 lun 0: SCSI1 0/direct fixed +sd0: 148MB, 967 cyl, 9 head, 35 sec, 512 bytes/sect x 304605 sectors + +The information of most interest is the number of sectors; here it's +304605. You will need this number when you come to create a disklabel +for that drive. + +[ START OF STATUS MESSAGES ] + +RAM address from VMEbus = $00000000 + +Booting from: VME147, Controller 5, Device 0 +Loading: Operating System + +Volume: NBSD + +IPL loaded at: $003F0000 +>> BSD MVME147 tapeboot [$Revision: 1.1 $] +578616+422344+55540+[46032+51284]=0x11a6e4 +Start @ 0x8000 ... +Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. +Copyright (c) 1982, 1986, 1989, 1991, 1993 + The Regents of the University of California. All rights reserved. + +NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997 + steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK +Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU +real mem = 7237632 +avail mem = 6381568 +using 88 buffers containing 360448 bytes of memory +mainbus0 (root) +pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 +clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM + . + . + +[ END OF STATUS MESSAGES ] + +Note that the exact text of the messages will vary depending on which +MVME147 variant you're using. + +Finally, you will see the following "welcome" message: + +[ START OF WELCOME MESSAGE ] + + Welcome to the NetBSD/mvme68k RAMDISK root! + +This environment is designed to do only four things: + 1: Partititon your disk (use the command: edlabel /dev/rsd0c) + 2: Copy a miniroot image into the swap partition (/dev/rsd0b) + 3: Make that partition bootable (using 'installboot') + 4: Reboot (using the swap partition, i.e. /dev/sd0b). + +Copying the miniroot can be done several ways, allowing the source +of the miniroot image to be on any of these: + boot tape, NFS server, TFTP server, rsh server + +The easiest is loading from tape, which is done as follows: + mt -f /dev/nrst0 rewind + mt -f /dev/nrst0 fsf 3 + dd bs=8k if=/dev/nrst0 of=/dev/rsd0b +(For help with other methods, please see the install notes.) + +To reboot using the swap partition after running installboot, first +use "halt", then at the Bug monitor prompt use a command like: + bo 0,,b: + +To view this message again, type: cat /.welcome +ssh: + +[ END OF WELCOME MESSAGE ] + +You must now create a disklabel on the disk you wish to use for the +root filesystem. This will usually be 'sd0'. The disklabel is used by +NetBSD to identify the starting block and size of each partition on +the disk. + +Partitions are named 'sd0a', 'sd0b', 'sd0c' etc, up to 'sd0h'. The +mvme68k port of NetBSD makes some assumptions about the first three +partitions on a boot disk: + + sd0a The root filesystem. + sd0b The swap partition. + sd0c The whole disk. Also known as the Raw Partition. + +The 'Raw Partition' is special; NetBSD is able to use it even if the +disk has no label. You should never create a filesystem on the Raw +Partition, even on a non-boot disk. + +It is good practice to put /usr on a different partition than / (sd0a). +So, the first available partition for /usr is 'sd0d'. Refer to the +section entitled "NetBSD System Requirements and Supported Devices" for +information on the recommended sizes of the /, /usr and swap partitions. + +You are not required to define any partitions beyond sd0d, but if you +have a large disk drive, you might want to create several other partitions +for filesystems such as /home or /usr/src. Note that at this time you +are only required to partition the root/boot disk; you will get the +opportunity to partition any other disks in your system from the main +'miniroot' installation program. + +To create the disklabel and partitions, use the 'edlabel' program, +passing it the name of the Raw Partition of your root/boot disk. Note +that '-->' at the start of a line in the following examples indicates +you are being prompted to enter some information. Obviously, you won't +see this when you run the program for real. + +--> ssh: edlabel /dev/rsd0c + edlabel menu: + print - display the current disk label + modify - prompt for changes to the label + write - write the new label to disk + quit - terminate program + edlabel> + +The program shows what commands it recognises; "print", "modify", +"write" and "quit". It will accept the first letter of a command if +you don't feel like typing each one in full. + +To start creating the basic partitions, you should enter 'm' (modify) +at the edlabel prompt, then enter the letter corresponding to the first +partition, 'a'. (Note: the program shows "a-i : modify partition". This +is incorrect for port-mvme68k. Only letters 'a' to 'h' are acceptable. +This will be fixed in the next release.) + +--> edlabel> m + modify subcommands: + @ : modify disk parameters + a-i : modify partition + s : standarize geometry + q : quit this subcommand +--> edlabel/modify> a + a (root) 0 (0/00/00) 0 (0/00/00) unused +--> start as or : 0 +--> length as or : 38000 +--> type: 4.2BSD + edlabel/modify> + +When you enter the start and length of a partition, you can use either +blocks or cylinder/track/sector notation. If this is the first time +you've partitioned a disk for NetBSD, it's probably easiest to use block +notation. The above example creates partition 'a', starting at block zero +and with a size of 38000 blocks. Note that the usual size of a block is +512 bytes, so this creates a 19Mb partition. + +The 'type' of the partition should be "4.2BSD", otherwise you won't +be able to create a filesystem on it. + +Next, create a swap partition (b). Note that the minimum size of this +swap partition should be 8Mb, otherwise you won't be able to use a +miniroot to complete the NetBSD installation! + +--> edlabel/modify> b + b (swap) 0 (0/00/00) 0 (0/00/00) unused +--> start as or : 38000 +--> length as or : 32768 +--> type: swap + edlabel/modify> + +Here, we specify a value for 'start' such that the swap partition follows +immediately after partition 'a', i.e. 38000. The length of the swap +partition should be a multiple of the amount of RAM you have in your +system. Here, I've chosen 32768, or 16Mb. The next available block on the +drive is thus 38000 + 32768. We will use this to create partition 'd' for +our /usr filesystem. (Note that for a busy system, or a system with more +than 8Mb of RAM, you'll be better off with a 32 or 64Mb swap partition.) + +--> edlabel/modify> d + d (user) 0 (0/00/00) 0 (0/00/00) unused +--> start as or : 70768 +--> length as or : 233837 +--> type: 4.2BSD +--> edlabel/modify> q + edlabel> + +As you can see, I've chosen to assign the remainder of the disk to /usr. +Since there are 304605 sectors on the example disk (did you remember to +note down the number of sectors on your disk during boot?), and partition +'d' starts at sector 70768, a simple bit of arithmetic (304605 - 70768) +gives 'd' a size of 233837. + +You now need to write this new disklabel, together with the partition +details you've just entered, to disk. You might also try the 'p' command +to view the partitions. Once written, you can quit back to ssh using 'q'. + +--> edlabel> p + type_num: 4 + sub_type: 0 + type_name: SCSI disk + pack_name: fictitious + bytes/sector: 512 + sectors/track: 35 + tracks/cylinder: 9 + cylinders: 967 + sectors/cylinder: 315 + partition start (c/t/s) nblks (c/t/s) type + + a (root) 0 (0/00/00) 38000 (120/05/25)* 4.2BSD + b (swap) 38000 (120/05/25)* 32768 (104/00/08)* swap + c (disk) 0 (0/00/00) 304605 (967/00/00) unused + d (user) 70768 (224/05/33)* 233837 (742/03/02)* 4.2BSD +--> edlabel> w +--> edlabel> q + ssh: + + +Now that your disk's partitioned, you need to get the proper installation +miniroot image onto it. The miniroot image is designed to be copied into +the swap partition of your disk. This is a safe place which won't be +overwritten by the installation procedure. From the ssh prompt, use the +following commands to copy the miniroot image from tape to swap (b). + +--> ssh: mt -f /dev/nrst0 rewind +--> ssh: mt -f /dev/nrst0 fsf 3 +--> ssh: dd bs=8k if=/dev/nrst0 of=/dev/rsd0b + +The disk and the miniroot must now be made bootable using the +'installboot' command, To do this, issue the following commands: + +--> ssh: mount /dev/sd0b /mnt +--> ssh: installboot /mnt/usr/mdec/bootsd /bootxx /dev/rsd0b +--> ssh: umount /dev/sd0b + +You can now shutdown the system. + +--> ssh: halt + signal 15 + ssh: syncing disks... done + unmounting /mnt (/dev/sd1b)... + unmounting / (root_device)... + halted + +--> 147-Bug>reset +--> Reset Local SCSI Bus [Y,N] N? y +--> Automatic reset of known SCSI Buses on RESET [Y,N] = Y? +--> Cold/Warm Reset flag [C,W] = C? +--> Execute Soft Reset [Y,N] N? y + +You should now reboot from that just installed miniroot. See the section +entitled "Booting the miniroot" for details. + + +* Installing from NFS: + +Before you can install from NFS, you must have already configured +your NFS server to support your machine as a bootable client. +Instructions for configuring the server are found in the section +entitled "Getting the NetBSD System onto Useful Media" above. + +To get started, you need to download "sboot" into RAM (you will find +'sboot' in the "install" directory of the mvme68k distribution). +You can either do that through the console line or through a 2nd serial +connection. For example, a VME147 connected to a sun4/110 and accessed +via "tip" can be loaded as follows: + + lo 0 + ~Ccat sboot + go 4000 + +Which will look like this: + +--> 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 = 6018) + + >>> + +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 whatever 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 boot the RAMDISK kernel +from the server: + +--> >>> b + + le0: ethernet address: 8:0:3e:20:cb:87 + My ip address is: 192.168.1.4 + Server ip address is: 192.168.1.1 + 4800 + Download was a success! + Start @ 0x8000 ... + >> BSD MVME147 netboot (via sboot) [$Revision: 1.1 $] + device: le0 attached to 08:00:3e:20:cb:87 + boot: client IP address: 192.168.1.4 + boot: client name: soapy + root addr=192.168.1.1 path=/export/soapy + 578616+422344+55540+[46032+51284]=0x11a6e4 + Start @ 0x8000 ... + Copyright (c) 1996, 1997 The NetBSD Foundation, Inc. All rights reserved. + Copyright (c) 1982, 1986, 1989, 1991, 1993 + The Regents of the University of California. All rights reserved. + + NetBSD 1.3 (RAMDISK) #1: Sun Dec 21 16:19:04 GMT 1997 + steve@soapy.mctavish.demon.co.uk:/usr/src/sys/arch/mvme68k/compile/RAMDISK + Motorola MVME-147S: 25MHz MC68030 CPU+MMU, MC68882 FPU + real mem = 7237632 + avail mem = 6381568 + using 88 buffers containing 360448 bytes of memory + mainbus0 (root) + pcc0 at mainbus0: Peripheral Channel Controller, rev 0, vecbase 0x40 + clock0 at pcc0 offset 0x0 ipl 5: Mostek MK48T02, 2048 bytes of NVRAM + . + . + +After the boot program loads the RAMDISK kernel, you should see the +welcome screen as shown in the "tape boot" section above. + +You now need to create a disklabel with partition information on the +SCSI disk on which you intend to create your root filesystem. Follow +the instructions in the previous section entitled "Installing from +tape" to do this. (But stop short of the part which describes how to +copy the miniroot from tape.) + +You must now configure the network interface before you can access the +NFS server containing the miniroot image. For example the command: + +--> ssh: ifconfig le0 inet 192.168.1.4 up + +will bring up the network interface 'le0' with that address. The next +step is to copy the miniroot from your server. This can be done using +either NFS or remote shell. (In the examples that follow, the server has +IP address 192.168.1.1) You may then need to add a default route if the +server is on a different subnet: + +--> ssh: route add default 192.168.1.2 1 + +You can look at the route table using: + +--> ssh: route show + +Now mount the NFS filesystem containing the miniroot image: + +--> ssh: mount -r 192.168.1.1:/export/soapy /mnt + +The procedure is simpler if you have space for an expanded (not +compressed) copy of the miniroot image. In that case: + +--> ssh: dd bs=8k if=/mnt/miniroot of=/dev/rsd0b + +Otherwise, you will need to use "zcat" to expand the miniroot image +while copying. This is tricky because the "ssh" program (small shell) +does not handle sh(1) pipeline syntax. Instead, you first run the reader +in the background with its input set to /dev/pipe and then run the other +program in the foreground with its output to /dev/pipe. The result looks +like this: + +--> ssh: run -bg dd obs=8k if=/dev/pipe of=/dev/rsd0b +--> ssh: run -o /dev/pipe zcat /mnt/install/miniroot.gz + +To load the miniroot using rsh to the server, you would use a pair +of commands similar to the above. Here is another example: + +--> ssh: run -b dd obs=8k if=/dev/pipe of=/dev/rsd0b +--> ssh: run -o /dev/pipe rsh 192.168.1.1 zcat miniroot.gz + +You must now make the disk bootable. Refer to the previous section on +installing from tape, where it describes how to run 'installboot'. +This is immediately following the part which explains how to copy the +miniroot from tape. + + +* Booting the miniroot: + +Assuming the miniroot is installed on partition 'b' of the disk with +SCSI-id 0, then the 147Bug boot command is: + + 147-Bug> bo 0,,b: + +The command line parameters above are: + + 0 controller (usually zero) + ,, bug argument separators + b: tell the bootstrap code to boot from partition 'b' + +You should see a bunch of boot messages, followed by messages from +the miniroot kernel just as you did when the RAMDISK kernel booted. + +You will then be prompted to enter the root device. Since the miniroot +was booted from the swap partition, you should enter 'sd0b'. You will +then be asked for the swap device and filesystem type. Just press +return twice to accept the defaults. When asked to enter a terminal +type, either accept the default, or use whatever the TERM environment +variable is set to in the shell of your host system: + + vmel0 at vmechip0 + boot device: sd0 +--> root device (default sd0a): sd0b +--> dump device (default sd0b): +--> file system (default generic): + root on sd0b dumps on sd0b + mountroot: trying ffs... + root file system type: ffs + init: copying out path `/sbin/init' 11 + erase ^H, werase ^W, kill ^U, intr ^C +--> Terminal type? [vt100] + +Congratulations! The system should now be running the miniroot +installation program. + + +Miniroot install program: +------------------------ + +The miniroot's install program is very simple to use. It will guide +you through the entire process, and is well automated. Additional +improvements are planned for future releases. + +The miniroot's install program will: + + * Allow you to place disklabels on additional disks. + The disk we are installing on should already have + been partitioned using the RAMDISK kernel. + + Note that partition sizes and offsets are expressed + in sectors. When you fill out the disklabel, you will + need to specify partition types and filesystem parameters. + If you're unsure what the these values should be, use the + following defaults: + + fstype: 4.2BSD + fsize: 1024 + bsize: 4096 + cpg: 16 + + If the partition will be a swap partition, use the following: + + fstype: swap + fsize: 0 (or blank) + bsize: 0 (or blank) + cpg: 0 (or blank) + + Note that partition 'c' is special; it covers then entire + disk and should not be assigned to a filesystem. + + The number of partitions is currently fixed at 8. + + * Create filesystems on target partitions. + + * Allow you to set up your system's network configuration. + Remember to specify host names without the domain name + appended to the end. For example use `foo' instead of + `foo.bar.org'. If, during the process of configuring + the network interfaces, you make a mistake, you will + be able to re-configure that interface by simply selecting + it for configuration again. + + * Mount target filesystems. You will be given the opportunity + to manually edit the resulting /etc/fstab. + + * Extract binary sets from the media of your choice. + + * Copy configuration information gathered during the + installation process to your root filesystem. + + * Make device nodes in your root filesystem. + + * Copy a new kernel onto your root partition. + + * Install a new boot block. + + * Check your filesystems for integrity. + +First-time installation on a system through a method other than the +installation program is possible, but strongly discouraged. diff --git a/distrib/notes/mvme68k/legal b/distrib/notes/mvme68k/legal new file mode 100644 index 000000000000..76b3fd98b867 --- /dev/null +++ b/distrib/notes/mvme68k/legal @@ -0,0 +1,17 @@ + This product includes software developed by the Computer + Systems Laboratory at the University of Utah. + + This product includes software developed by the University of + Vermont and State Agricultural College and Garrett A. Wollman. + + This product includes software developed by Charles D. Cranor. + + This product includes software developed by Adam Glass. + + This product includes software developed by Charles Hannum. + + This product includes software developed by David Jones. + + This product includes software developed by Gordon W. Ross. + + This product includes software developed by Steve C. Woodford. diff --git a/distrib/notes/mvme68k/prep b/distrib/notes/mvme68k/prep new file mode 100644 index 000000000000..3d6d3b50ee23 --- /dev/null +++ b/distrib/notes/mvme68k/prep @@ -0,0 +1,54 @@ +mvme68k 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. + +The following instructions should make your machine "NetBSD Ready". + +Power-up your VME147. You should have the "bug" prompt: + + COLD Start + + Onboard RAM start = $00000000, stop = $007FFFFF + + 147-Bug> + +Make sure the value for "stop" looks ok (if you've got 8MB you should +have the same value as I do). Also make sure the clock is ticking: + + 147-Bug>time + Sunday 12/21/29 16:25:14 + 147-Bug>time + Sunday 12/21/29 16:25:15 + 147-Bug> + +Note that NetBSD bases it's year at 1968, and adds the year offset in +the VME147's real-time clock to get the current year. So the '29' here +equates to 1997. You may have to adjust your clock using the 'set' +command to comply with NetBSD's requirements. Don't worry if the +"Day of the week" is not correct, NetBSD doesn't use it. (Actually, +Motorola have acknowledged a year 2000 bug whereby the day of the week +doesn't get set correctly by the 147Bug PROM. IT DOES NOT AFFECT NETBSD!) + +Also make sure that your VME147's ethernet address is initialised to +the correct value. You'll find the address on a label on the inside of +the board's front panel. Enter the last five digits of the address +using the 'lsad' command. + +To install successfully to a local SCSI disk, you need to ensure that +147Bug is aware of what targets are connected to the SCSI bus. This +can be done by issueing the following command: + +--> 147-Bug> iot;t + +At this point, 147Bug will scan for any attached SCSI devices. After +a short delay, a list of SCSI devices will be displayed. You will be +asked if Bug should assign LUNs to SCSI ids, to which you should +answer Y. You should also answer Y when asked if the information is +to be saved to NVRAM. + +The following installation instructions will assume that your target +SCSI disk drive appears at SCSI-id 0. If you have a tape drive, the +instructions assume is is configured for SCSI-id 5. When the RAMDISK +root boots, NetBSD will refer to these devices as 'sd0' and 'rst0' +respectively. You may wish to note these down; you'll be using them +a lot. :-) diff --git a/distrib/notes/mvme68k/upgrade b/distrib/notes/mvme68k/upgrade new file mode 100644 index 000000000000..8b287e0dd9f5 --- /dev/null +++ b/distrib/notes/mvme68k/upgrade @@ -0,0 +1,96 @@ +It is possible to easily upgrade your existing NetBSD/mvme68k system +using the upgrade program in the miniroot. If you wish to upgrade +your system by this method, simply select the `upgrade' option once +the miniroot has booted. The upgrade program with then guide you +through the procedure. The upgrade program will: + + * Enable the network based on your system's current + network configuration. + + * Mount your existing filesystems. + + * Extract binary sets from the media of your choice. + + * Fixup your system's existing /etc/fstab, and if necessary, + changing the occurrences of `ufs' to `ffs' and let you + edit the resulting file. + + * Make new device nodes in your root filesystem. + + * Copy a new kernel onto your root partition. + NOTE: the existing kernel WILL NOT be backed up; doing + so would be pointless, since older kernels may not be + capable of running NetBSD _VER executables. + + * Install a new boot block. + + * Check your filesystems for integrity. + +While using the miniroot's upgrade program is the preferred method +of upgrading your system, it is possible to upgrade your system +manually. To do this, follow the following procedure: + + * Place _at least_ the `base' binary set in a filesystem + accessible to the target machine. A local filesystem + is preferred, since the NFS subsystem in the NetBSD _VER + kernel may be incompatible with your old binaries. + + * Back up your pre-existing kernel and copy the _VER + kernel into your root partition. + + * Reboot with the _VER kernel into single-user mode. + + * Check all filesystems: + + /sbin/fsck -pf + + * Mount all local filesystems: + + /sbin/mount -a -t nonfs + + * If you keep /usr or /usr/share on an NFS server, you + will want to mount those filesystems as well. To do + this, you will need to enable the network: + + sh /etc/netstart + + * Run the update(8) daemon, to ensure that new programs + are actually stored on disk. + + update + + * Make sure you are in the root filesystem and extract + the `base' binary set: + + cd / + tar --unlink -zxvpf /path/to/base.tgz + + NOTE: the `--unlink' option is _very_ important! + + * Delete system files in /sbin which now live in /usr/sbin: + + cd /sbin + rm -f mountd rtquery quotacheck dumpfs dumplfs + + * Install a new boot block (you may need to be running in + single-user mode to do this...): + + cd /usr/mdec + cp bootsd /.bootsd + ./installboot /.bootsd bootxx + + * Sync the filesystems: + + sync + + * At this point you may extract any other binary sets + you may have placed on local filesystems, or you may + wish to extract additional sets at a later time. + To extract these sets, use the following commands: + + cd / + tar --unlink -zxvpf + +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. diff --git a/distrib/notes/mvme68k/whatis b/distrib/notes/mvme68k/whatis new file mode 100644 index 000000000000..38c1f307d5b2 --- /dev/null +++ b/distrib/notes/mvme68k/whatis @@ -0,0 +1 @@ +This is the fourth public release of NetBSD for the VME147. diff --git a/distrib/notes/mvme68k/xfer b/distrib/notes/mvme68k/xfer new file mode 100644 index 000000000000..fea3e30d2267 --- /dev/null +++ b/distrib/notes/mvme68k/xfer @@ -0,0 +1,141 @@ +Installation is supported from several media types, including: + + * Tape + * NFS + * CD-ROM + * FTP + +Note that installing on a "bare" machine requires either a bootable +tape drive or an ethernet and RS232 connection to a compatible NFS server. + +The procedure for transferring the distribution sets onto installation +media depends on the type of media. Instructions for each type of media +are given below. + +In order to create installation media, you will need all the files in +these two directories: + + .../NetBSD-_VER/mvme68k/install + .../NetBSD-_VER/mvme68k/binary + + +* Creating boot/install tapes: + +Installing from tape is the simplest method of all. This method uses two +tapes, one containing a bootable ramdisk and miniroot, the other containing +the installation sets. + +The boot tape is created as follows: + +--> cd .../NetBSD-_VER/mvme68k/install +--> set T = /dev/nrst0 +--> mt -f $T rewind +--> dd if=stboot of=$T +--> dd if=bootst of=$T obs=8k conv=osync +--> gzip -dc netbsd-rd.gz | dd of=$T obs=8k conv=osync +--> gzip -dc miniroot.gz | dd of=$T obs=8k conv=osync +--> mt -f $T rewind + +The installation set tape is created as follows: + +--> cd .../NetBSD-_VER/mvme68k/binary +--> set T = /dev/nrst0 +--> mt -f $T rewind +--> foreach f (base etc comp games man misc text) +--> gzip -d < $f.tgz | dd of=$T bs=8k +--> end +--> mt -f $T rewind + +If the tape does not work as expected, you may need to explicitly +set the EOF mark at the end of each tape segment. Consult the tape- +related manual pages on the system where the tapes are created for +more details. + + +* Boot/Install from NFS server: + +If your machine has a disk and network connection, but no tape drive, +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). + +Booting a VME147 from ethernet is not possible without first downloading +a small bootstrap program (sboot) via RS232. See the section entitiled +"Installing from NFS" for details on how to accomplish this. + +sboot expects to be able to download a second stage bootstrap +program via TFTP after having acquired its IP address through RARP +It will look for a filename derived from the machine's IP address +expressed in hexadecimal, with an extension of ".147". For example, +a VME147 with IP address 130.115.144.11 will make an TFTP request for +`8273900B.147'. Normally, this file is just a symbolic link to the +NetBSD/mvme68k "netboot" 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). The netboot program may be found in the +install directory of this distribution. + +The netboot program will query a bootparamd server to find the NFS +server address and path name for its root, and then load a kernel from +that location. The server should have a copy of the netbsd-rd kernel in +the root area for your client (no other files are needed in the client +root, although it might be a convenient place to put the uncompressed +miniroot image) and /etc/bootparams on the server should have an entry +for your client and its root directory. Note that you should rename the +netbsd-rd kernel to just 'netbsd' in the client's root directory before +trying to netboot the client. + +The client will need access to the miniroot image, which can be +provided using NFS or remote shell. If using NFS, miniroot.gz should be +expanded on the server, because doing so from the RAMDISK shell is not +so easy. The unzipped miniroot takes about 6Mb of space. + +If you will be installing NetBSD on several clients, it may be useful +to know that you can use a single NFS root for all the clients as long +as they only use the netbsd-rd kernel. There will be no conflict +between clients because the RAM-disk kernel will not use the NFS root. +No swap file is needed; the RAM-disk kernel does not use that either. + + +* Install/Upgrade from CD-ROM: + +This method requires that you boot from another device (i.e. tape +or network, as described above). You may need to make a boot tape +on another machine using the files provided on the CD-ROM. Once +you have booted netbsd-rd (the RAMDISK kernel) and loaded the +miniroot, you can load any of the distribution sets directly from +the CD-ROM. The "install" program in the miniroot automates the +work required to mount the CD-ROM and extract the files. + + +* Install/Upgrade via FTP: + +This method requires that you boot from another device (i.e. tape +or network, as described above). You may need to make a boot tape +on another machine using the files in .../install (which you get +via FTP). Once you have booted netbsd-rd (the RAM-disk kernel) +and loaded the miniroot, you can load any of the distribution sets +over the net using FTP. The "install" program in the miniroot +automates the work required to configure the network interface and +transfer the files. + +This method, of course, requires network access to an FTP server. +This might be a local system, or it might even be ftp.NetBSD.ORG +itself. If you wish to use ftp.NetBSD.ORG as your FTP file +server, you may want to keep the following information handy: + + IP Address: ftp.NetBSD.ORG + Login: anonymous + Password: + Server path: /pub/NetBSD/NetBSD-_VER/mvme68k/binary + +Note: if you're not using a nameserver duing installation, +you might find 206.86.8.12 handy; it's the IP address of +ftp.NetBSD.ORG as of September 2, 1996.