1998-10-21 18:32:36 +04:00
|
|
|
$NetBSD: xfer,v 1.3 1998/10/21 14:32:36 minoura Exp $
|
1998-01-09 21:45:24 +03:00
|
|
|
|
1996-06-17 15:26:04 +04:00
|
|
|
Installation is supported from several media types, including:
|
|
|
|
|
1998-10-21 18:32:36 +04:00
|
|
|
Removable SCSI hard disk, or Magneto-Optical disk (MO)
|
1996-06-17 15:26:04 +04:00
|
|
|
Tape
|
|
|
|
Remote NFS partition
|
|
|
|
FTP
|
|
|
|
|
|
|
|
No matter which installation medium you choose, you'll need to have
|
|
|
|
a floppy disk. On the first, you'll put the install or upgrade floppy
|
|
|
|
image, depending on whether you're installing NetBSD for the first time,
|
|
|
|
or upgrading a previous installation.
|
|
|
|
|
|
|
|
If you are using a UN*X-like system to write the floppy images to
|
|
|
|
disks, you should use the "dd" command to copy the file system images
|
|
|
|
(.fs files) directly to the raw floppy disks. It is suggested that
|
|
|
|
you read the dd(1) manual page or ask your system administrator to
|
|
|
|
determine the correct set of arguments to use; it will be slightly
|
|
|
|
different from system to system, and a comprehensive list of the
|
|
|
|
possibilities is beyond the scope of this document.
|
|
|
|
|
|
|
|
If you are using Human68k to write the floppy images to disks, you should
|
|
|
|
use the "rawrite" utility, provided in the "x68k/utils" directory
|
|
|
|
of the NetBSD distribution. It will write the file system images (.fs
|
|
|
|
files) to disks.
|
|
|
|
|
|
|
|
Note that, when installing, the install floppy MUST not be write-protected.
|
|
|
|
The install program needs to write some temporary files, and if the
|
|
|
|
disk is write-protected, it can't. If you're upgrading your system,
|
|
|
|
the upgrade floppy may be write-protected.
|
|
|
|
|
|
|
|
Obviously, the steps necessary to prepare the distribution sets for
|
|
|
|
installation or upgrade depend on which installation medium you
|
|
|
|
choose. The steps for the various media are outlined below.
|
|
|
|
|
1998-10-21 18:32:36 +04:00
|
|
|
To install or upgrade NetBSD using
|
|
|
|
|
|
|
|
To install or upgrade NetBSD using a removable SCSI harddisk or MO,
|
|
|
|
you need to the following:
|
|
|
|
|
|
|
|
To install NetBSD from a removablethe media MUST be of the IBM
|
|
|
|
`Super-floppy' format. The Human68k format is not recognized
|
|
|
|
by this release of the NetBSD/x68k. If you have a MS-DOS (or
|
|
|
|
MS-Windows) machine with an MO drive connected, use it. If
|
|
|
|
you don't, and if you have a program to handle IBM format MO
|
|
|
|
for Human68k, copy all the files in the subdirectory
|
|
|
|
"x68k/binaries" and CHANGE THEIR NAMES IN UPPER CASE.
|
1996-06-17 15:26:04 +04:00
|
|
|
|
|
|
|
To install or upgrade NetBSD using a tape, you need to do the
|
|
|
|
following:
|
|
|
|
|
|
|
|
To install NetBSD from a tape, you need to make a tape that
|
|
|
|
contains the distribution set files, in "tar" format. If
|
|
|
|
you're making the tape on a UN*X-like system, the easiest way
|
|
|
|
to do so is probably something like:
|
|
|
|
|
|
|
|
tar cf <tape_device> <dist_directories>
|
|
|
|
|
|
|
|
where "<tape_device>" is the name of the tape device that
|
|
|
|
describes the tape drive you're using (possibly /dev/rst0, or
|
|
|
|
something similar, but it will vary from system to system.
|
|
|
|
(If you can't figure it out, ask your system administrator.)
|
|
|
|
In the above example, "<dist_directories>" are the
|
|
|
|
distribution sets' directories, for the distribution sets you
|
1998-10-21 18:32:36 +04:00
|
|
|
wish to place on the tape. For instance, to put the "base"
|
|
|
|
and "etc" distributions on tape (in order to do the absolute
|
1996-06-17 15:26:04 +04:00
|
|
|
minimum installation to a new disk), you would do the
|
|
|
|
following:
|
|
|
|
|
1998-10-21 18:32:36 +04:00
|
|
|
cd .../NetBSD-_VER # the top of the tree
|
|
|
|
cd x68k/binary/sets
|
|
|
|
tar cf <tape_device> base.tgz etc.tgz
|
1996-06-17 15:26:04 +04:00
|
|
|
|
|
|
|
(Note that you still need to fill in "<tape_device>" in the
|
|
|
|
example.)
|
|
|
|
|
|
|
|
Once you have the files on the tape, you can proceed to the
|
|
|
|
next step in the installation or upgrade process. If you're
|
|
|
|
installing NetBSD from scratch, go to the section on preparing
|
|
|
|
your hard disk, below. If you're upgrading an existing
|
|
|
|
installation, go directly to the section on upgrading.
|
|
|
|
|
|
|
|
To install or upgrade NetBSD using a remote partition, mounted via
|
|
|
|
NFS, you must do the following:
|
|
|
|
|
|
|
|
NOTE: This method of installation is recommended only for
|
|
|
|
those already familiar with using BSD network
|
|
|
|
configuration and management commands. If you aren't,
|
|
|
|
this documentation should help, but is not intended to
|
|
|
|
be all-encompassing.
|
|
|
|
|
|
|
|
Place the NetBSD distribution sets you wish to install into a
|
|
|
|
directory on an NFS server, and make that directory mountable
|
|
|
|
by the machine on which you are installing or upgrading NetBSD.
|
|
|
|
This will probably require modifying the /etc/exports file on
|
|
|
|
of the NFS server and resetting its mount daemon (mountd).
|
|
|
|
(Both of these actions will probably require superuser
|
|
|
|
privileges on the server.)
|
|
|
|
|
|
|
|
You need to know the the numeric IP address of the NFS server,
|
|
|
|
and, if the server is not on a network directly connected to
|
|
|
|
the machine on which you're installing or upgrading NetBSD,
|
|
|
|
you need to know the numeric IP address of the router closest
|
|
|
|
to the NetBSD machine. Finally, you need to know the numeric
|
|
|
|
IP address of the NetBSD machine itself.
|
|
|
|
|
|
|
|
Once the NFS server is set up properly and you have the
|
|
|
|
information mentioned above, you can proceed to the next step
|
|
|
|
in the installation or upgrade process. If you're installing
|
|
|
|
NetBSD from scratch, go to the section on preparing your hard
|
|
|
|
disk, below. If you're upgrading an existing installation, go
|
|
|
|
directly to the section on upgrading.
|
|
|
|
|
|
|
|
To install or upgrade NetBSD by using FTP to get the installation
|
|
|
|
sets, you must do the following:
|
|
|
|
|
|
|
|
NOTE: This method of installation is recommended only for
|
|
|
|
those already familiar with using BSD network
|
|
|
|
configuration and management commands. If you aren't,
|
|
|
|
this documentation should help, but is not intended to
|
|
|
|
be all-encompassing.
|
|
|
|
|
|
|
|
The preparations for this installation/upgrade method are
|
|
|
|
easy; all you make sure that there's some FTP site from which
|
|
|
|
you can retrieve the NetBSD distribution when you're about to
|
|
|
|
install or upgrade. You need to know the numeric IP address
|
|
|
|
of that site, and, if it's not on a network directly connected
|
|
|
|
to the machine on which you're installing or upgrading NetBSD,
|
|
|
|
you need to know the numeric IP address of the router closest
|
|
|
|
to the NetBSD machine. Finally, you need to know the numeric
|
|
|
|
IP address of the NetBSD machine itself.
|
|
|
|
|
|
|
|
Once you have this information, you can proceed to the next
|
|
|
|
step in the installation or upgrade process. If you're
|
|
|
|
installing NetBSD from scratch, go to the section on
|
|
|
|
preparing your hard disk, below. If you're upgrading an
|
|
|
|
existing installation, go directly to the section on
|
|
|
|
upgrading.
|
|
|
|
|
|
|
|
If you are upgrading NetBSD, you also have the option of installing
|
|
|
|
NetBSD by putting the new distribution sets somewhere in your existing
|
|
|
|
file system, and using them from there. To do that, you must do the
|
|
|
|
following:
|
|
|
|
|
|
|
|
Place the distribution sets you wish to upgrade somewhere in
|
|
|
|
your current file system tree. At a bare minimum, you must
|
|
|
|
upgrade the "base" binary distribution, and so must put the
|
1998-10-21 18:32:36 +04:00
|
|
|
"base.tgz" set somewhere in your file system. If you wish,
|
1996-06-17 15:26:04 +04:00
|
|
|
you can do the other sets, as well, but you should NOT upgrade
|
|
|
|
the "etc" distribution; the "etc" distribution contains system
|
|
|
|
configuration files that you should review and update by hand.
|
|
|
|
|
|
|
|
Once you have done this, you can proceed to the next step in
|
|
|
|
the upgrade process, actually upgrading your system.
|