NetBSD/distrib/notes/mvme68k/xfer

.\"	$NetBSD: xfer,v 1.4 1999/01/13 07:30:07 ross Exp $	
.
Installation is supported from several media types, including:
.Bl -bullet -compact
.Pp
.It
Tape
.It
NFS
.It
CD-ROM
.It
FTP
.El
Note that installing on a "bare" machine requires either a bootable
tape drive or an ethernet and RS232 connection to a compatible NFS server.
.Pp
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.
.Pp
In order to create installation media, you will need all the files and
subdirectories in these two directories:
.Pp
.Dl Pa \&.../NetBSD-\*V/mvme68k/installation
.Dl Pa \&.../NetBSD-\*V/mvme68k/binary
.
.Ss2 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.
.Pp
The boot tape is created as follows:
.Pp
.D1 Ic "cd .../NetBSD-\*V/mvme68k/installation
.D1 Ic "set T = /dev/nrst0
.D1 Ic "mt -f $T rewind
.D1 Ic "dd if=tapeimage/stboot of=$T
.D1 Ic "dd if=tapeimage/bootst of=$T obs=8k conv=osync
.D1 Ic "gzip -dc tapeimage/netbsd-rd.gz | dd of=$T obs=8k conv=osync
.D1 Ic "gzip -dc miniroot/miniroot.gz  | dd of=$T obs=8k conv=osync
.D1 Ic "mt -f $T rewind
.Pp
The installation set tape is created as follows:
.Pp
.D1 Ic "cd .../NetBSD-\*V/mvme68k/binary/sets
.D1 Ic "set T = /dev/nrst0
.D1 Ic "mt -f $T rewind
.D1 Ic "foreach f (base etc comp games man misc text)
.D1 Ic "gzip -d \*< $f.tgz | dd of=$T bs=8k
.D1 Ic "end
.D1 Ic "mt -f $T rewind
.Pp
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.
.
.Ss2 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
.Nx
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.
.Pp
If you are using a
.Nx
system as the boot-server, have a look at
the
.Xr 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).
.Pp
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.
.Pp
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.
.Pp
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.
.Pp
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.
.Pp
If you will be installing
.Nx
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.
.
.Ss2 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.
.
.Ss2 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.
.Pp
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:
.Pp
.Dl No IP Address: ftp.NetBSD.ORG
.Dl Login: Ic anonymous
.Dl Password: Ar your e-mail address
.Dl Server path: Ic /pub/NetBSD/NetBSD-\*V/mvme68k/binary
.(Note
If you're not using a nameserver duing installation,
you might find 204.152.184.75 handy; it's the IP address of
ftp.NetBSD.ORG as of January 3, 1997.
.Note)