1 $NetBSD: xfer,v 1.3 1998/01/09 18:46:58 perry Exp $ 2 3Installation is supported from several media types, including: 4 5 * Tape 6 * NFS 7 * CD-ROM 8 * FTP 9 10Note that installing on a "bare" machine requires either a bootable 11tape drive or an ethernet and RS232 connection to a compatible NFS server. 12 13The procedure for transferring the distribution sets onto installation 14media depends on the type of media. Instructions for each type of media 15are given below. 16 17In order to create installation media, you will need all the files and 18subdirectories in these two directories: 19 20 .../NetBSD-_VER/mvme68k/installation 21 .../NetBSD-_VER/mvme68k/binary 22 23 24* Creating boot/install tapes: 25 26Installing from tape is the simplest method of all. This method uses two 27tapes, one containing a bootable ramdisk and miniroot, the other containing 28the installation sets. 29 30The boot tape is created as follows: 31 32--> cd .../NetBSD-_VER/mvme68k/installation 33--> set T = /dev/nrst0 34--> mt -f $T rewind 35--> dd if=tapeimage/stboot of=$T 36--> dd if=tapeimage/bootst of=$T obs=8k conv=osync 37--> gzip -dc tapeimage/netbsd-rd.gz | dd of=$T obs=8k conv=osync 38--> gzip -dc miniroot/miniroot.gz | dd of=$T obs=8k conv=osync 39--> mt -f $T rewind 40 41The installation set tape is created as follows: 42 43--> cd .../NetBSD-_VER/mvme68k/binary/sets 44--> set T = /dev/nrst0 45--> mt -f $T rewind 46--> foreach f (base etc comp games man misc text) 47--> gzip -d < $f.tgz | dd of=$T bs=8k 48--> end 49--> mt -f $T rewind 50 51If the tape does not work as expected, you may need to explicitly 52set the EOF mark at the end of each tape segment. Consult the tape- 53related manual pages on the system where the tapes are created for 54more details. 55 56 57* Boot/Install from NFS server: 58 59If your machine has a disk and network connection, but no tape drive, 60it may be convenient for you to install NetBSD over the network. This 61involves temporarily booting your machine over NFS, just long enough 62so you can initialize its disk. This method requires that you have 63access to an NFS server on your network so you can configure it to 64support diskless boot for your machine. Configuring the NFS server 65is normally a task for a system administrator, and is not trivial. 66 67If you are using a NetBSD system as the boot-server, have a look at 68the diskless(8) manual page for guidelines on how to proceed with 69this. If the server runs another operating system, consult the 70documentation that came with it (i.e. add_client(8) on SunOS). 71 72Booting a VME147 from ethernet is not possible without first downloading 73a small bootstrap program (sboot) via RS232. See the section entitiled 74"Installing from NFS" for details on how to accomplish this. 75 76sboot expects to be able to download a second stage bootstrap 77program via TFTP after having acquired its IP address through RARP 78It will look for a filename derived from the machine's IP address 79expressed in hexadecimal, with an extension of ".147". For example, 80a VME147 with IP address 130.115.144.11 will make an TFTP request for 81`8273900B.147'. Normally, this file is just a symbolic link to the 82NetBSD/mvme68k "netboot" program, which should be located in a place 83where the TFTP daemon can find it (remember, many TFTP daemons run in 84a chroot'ed environment). The netboot program may be found in the 85install directory of this distribution. 86 87The netboot program will query a bootparamd server to find the NFS 88server address and path name for its root, and then load a kernel from 89that location. The server should have a copy of the netbsd-rd kernel in 90the root area for your client (no other files are needed in the client 91root, although it might be a convenient place to put the uncompressed 92miniroot image) and /etc/bootparams on the server should have an entry 93for your client and its root directory. Note that you should rename the 94netbsd-rd kernel to just 'netbsd' in the client's root directory before 95trying to netboot the client. 96 97The client will need access to the miniroot image, which can be 98provided using NFS or remote shell. If using NFS, miniroot.gz should be 99expanded on the server, because doing so from the RAMDISK shell is not 100so easy. The unzipped miniroot takes about 6Mb of space. 101 102If you will be installing NetBSD on several clients, it may be useful 103to know that you can use a single NFS root for all the clients as long 104as they only use the netbsd-rd kernel. There will be no conflict 105between clients because the RAM-disk kernel will not use the NFS root. 106No swap file is needed; the RAM-disk kernel does not use that either. 107 108 109* Install/Upgrade from CD-ROM: 110 111This method requires that you boot from another device (i.e. tape 112or network, as described above). You may need to make a boot tape 113on another machine using the files provided on the CD-ROM. Once 114you have booted netbsd-rd (the RAMDISK kernel) and loaded the 115miniroot, you can load any of the distribution sets directly from 116the CD-ROM. The "install" program in the miniroot automates the 117work required to mount the CD-ROM and extract the files. 118 119 120* Install/Upgrade via FTP: 121 122This method requires that you boot from another device (i.e. tape 123or network, as described above). You may need to make a boot tape 124on another machine using the files in .../install (which you get 125via FTP). Once you have booted netbsd-rd (the RAM-disk kernel) 126and loaded the miniroot, you can load any of the distribution sets 127over the net using FTP. The "install" program in the miniroot 128automates the work required to configure the network interface and 129transfer the files. 130 131This method, of course, requires network access to an FTP server. 132This might be a local system, or it might even be ftp.NetBSD.ORG 133itself. If you wish to use ftp.NetBSD.ORG as your FTP file 134server, you may want to keep the following information handy: 135 136 IP Address: ftp.NetBSD.ORG 137 Login: anonymous 138 Password: <your e-mail address> 139 Server path: /pub/NetBSD/NetBSD-_VER/mvme68k/binary 140 141Note: if you're not using a nameserver duing installation, 142you might find 204.152.184.75 handy; it's the IP address of 143ftp.NetBSD.ORG as of January 3, 1997. 144