NetBSD/distrib/notes/vax/xfer

141 lines
5.0 KiB
Plaintext
Raw Normal View History

.\" $NetBSD: xfer,v 1.6 2000/03/04 15:05:19 ragge Exp $
1999-01-13 10:30:01 +03:00
.
Installation is supported from several media types, including:
1999-01-13 10:30:01 +03:00
.Bl -bullet -compact -offset indent
.It
Floppy
.It
FTP
.It
Tape
.It
NFS
1999-01-13 10:30:01 +03:00
.El
.(Note
Installing on a "bare" machine requires some bootable
device; either a tape or floppy drive or a NFS server together
with a machine that can act as a MOP loader, such as another
machine running NetBSD.
NetBSD/vax can use both BOOTP/DHCP and
BOOTPARAMS for netboot installations.
1999-01-13 10:30:01 +03:00
.Note)
.Pp
The procedure for transferring the distribution sets onto
installation media depends on the type of media. most of it is up to
you, depending what you want to install, but preferred are to do
the installation over network as soon as the install kernel is booted.
1999-01-13 10:30:01 +03:00
.
.Ss2 Creating boot tapes
.
Fetch the bootable bootfs image from
.Dl \&.../NetBSD-\*V/vax/installation/bootfs/boot.fs.gz
Gunzip boot.fs.gz and write it on the beginning of the tape.
Under NetBSD this is done (for MSCP tape, with SCSI tape the name is
nrst0) via:
.D1 Ic "gunzip boot.fs.gz
.D1 Ic "mt -f /dev/nrmt0 rewind
.D1 Ic "dd if=boot.fs of=/dev/nrmt0
.D1 Ic "mt -f /dev/nrmt0 rewoffl
.Pp
Under Ultrix the tape name is different:
.D1 Ic "gunzip boot.fs.gz
1999-01-13 10:30:01 +03:00
.D1 Ic "mt -f /dev/rmt0h rewind
.D1 Ic "dd if=boot.fs of=/dev/rmt0h
1999-01-13 10:30:01 +03:00
.D1 Ic "mt -f /dev/rmt0h rewoffl
.Pp
Of course, if you have a tape unit other than unit 0 you have to use
the corresponding unit number.
1999-01-13 10:30:01 +03:00
.Pp
If you wish to install the sets from tape then stage you will need to
download the *.tgz files from
.Dl \&.../NetBSD-\*V/vax/binary/sets Ns Ar {50,33}
(if your disk is less than 200MB you will probably want to exclude the
X sets) and then before the 'mt ... rewoffl' run
.D1 Ic "tar cvf /dev/nrmt0 *.tgz
When you have booted the bootfs and completed the disk partitioning
you will be prompted to 'select medium' for install. At this point
you will need to press ^Z (Ctrl+Z) to suspend the install tool, then
.D1 Ic "cd /mnt
.D1 Ic "mt -f /dev/nrmt0 rewind
.D1 Ic "mt -f /dev/nrmt0 fsf
.D1 Ic "tar xvf /dev/nrmt0
.D1 Ic "fg
then select "install from local dir" and give "/mnt".
Note: If your disk is small you will need to be careful about filling
it up.
.Pp
If you are using any other OS to create bootable tapes, remember that
1999-01-13 10:30:01 +03:00
the blocksize
.Em must
be 512 for the file to be bootable! Otherwise it just won't work.
.
.Ss2 Creating boot floppies
.
Fetch the bootable bootfs image from
.Dl \&.../NetBSD-\*V/vax/installation/bootfs/boot.fs.gz
and gunzip it. It is a 1MB bootable image that will boot from any
floppy of size 1MB and bigger.
Note that you
.Em cannot
install from RX50 floppies due to the small size. This may change
in the future.
.Pp
All floppies except RX50 use a standardized format for storing data
so writing the bootfs to the floppy can be done on any PC. From DOS
the preferred way to do this is using RAWRITE.EXE.
1999-01-13 10:30:01 +03:00
.
.Ss2 Booting from NFS server
.
All VAXen that can boot over network uses MOP, a DEC protocol.
To be able to use MOP, a MOP daemon must be present on one of
the machines on the local network. The boot principle is:
1999-01-13 10:30:01 +03:00
.Bl -bullet -compact -offset indent
.It
The VAX broadcast a wish to load an image.
1999-01-13 10:30:01 +03:00
.It
A mopd answers and send the boot program to the VAX.
.It
The boot program does rarp/bootp requests, mounts the root filesystem
1999-01-13 10:30:01 +03:00
and loads the kernel.
.It
The kernel is loaded and starts executing.
.El
.Pp
If your machine has a disk and network connection, it may be
1999-01-13 10:30:01 +03:00
convenient for you to install NetBSD over the network. This
involves temporarily booting your machine over NFS, just long enough
1999-01-13 10:30:01 +03:00
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
1999-01-13 10:30:01 +03:00
support diskless boot for your machine. Configuring the NFS server
is normally a task for a system administrator, and is not trivial.
1999-01-13 10:30:01 +03:00
.Pp
If you are using a NetBSD system as the boot-server, have a look at
1999-01-13 10:30:01 +03:00
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
There is also very useful documentation at
.Lk http://www.netbsd.org/Documentation/network/netboot/
.Pp
You also must install a MOP loader. If you are booting from another
NetBSD machine, the MOP daemons are included in the distribution,
otherwise you may have to install a MOP loader. A loader can be found at
1999-01-13 10:30:01 +03:00
.Lk ftp.stacken.kth.se:/pub/OS/NetBSD/mopd
Fetch the latest and read the
installation instructions.
.Pp
The file that should be loaded is called boot.mop and is located in
.Dl \&.../NetBSD-\*V/vax/installation/netboot/boot.mop
1999-01-13 10:30:01 +03:00
.Pp
The kernel to load is the same kernel as the bootfs uses and can
be found in
.Dl \&.../NetBSD-\*V/vax/installation/netboot/netbsd.ram.gz
From the install program started in the kernel the rest of the system
can be installed.
There is also a very good (if somewhat out of date) FAQ for netbooting
VAXen at
.Lk http://world.std.com/~bdc/projects/vaxen/VAX-netboot-HOWTO.html
that describes netbooting of VAXen from many different OS'es.