Home | History | Annotate | Line # | Download | only in i386
xfer revision 1.12
      1   1.1      cgd Installation is supported from several media types, including:
      2   1.1      cgd 
      3   1.1      cgd 	DOS floppies
      4   1.1      cgd 	Tape
      5   1.1      cgd 	Remote NFS partition
      6   1.1      cgd 	FTP
      7   1.1      cgd 
      8   1.6    perry No matter which installation medium you choose, you'll need to have a
      9  1.12    perry floppy disk (either 1.2M or 1.44M will work).  You'll put the boot
     10  1.12    perry floppy image ("boot.fs" for 1.44M floppies, "boot-small.fs" for 1.2M
     11  1.12    perry floppies) onto this disk, which contains software to install or
     12  1.12    perry upgrade your NetBSD system.
     13   1.8    perry 
     14   1.8    perry [Note: previous versions of NetBSD used several floppy images,
     15   1.8    perry including several kernel/boot floppies depending on hardware
     16   1.9    mikel configuration, an install floppy, and an upgrade floppy. NetBSD _VER
     17  1.12    perry only requires a single floppy for all tasks.]
     18   1.1      cgd 
     19   1.1      cgd If you are using a UN*X-like system to write the floppy images to
     20   1.8    perry disks, you should use the "dd" command to copy the file system image
     21   1.8    perry (.fs file) directly to the raw floppy disk.  It is suggested that you
     22   1.8    perry read the dd(1) manual page or ask your system administrator to
     23   1.1      cgd determine the correct set of arguments to use; it will be slightly
     24   1.1      cgd different from system to system, and a comprehensive list of the
     25   1.1      cgd possibilities is beyond the scope of this document.
     26   1.1      cgd 
     27   1.8    perry If you are using DOS to write the floppy image to disk, you should
     28   1.1      cgd use the "rawrite" utility, provided in the "i386/utilities" directory
     29   1.8    perry of the NetBSD distribution.  It will write the file system image (.fs
     30   1.8    perry file) to disks.
     31   1.1      cgd 
     32   1.6    perry Note that, when installing or upgrading, the floppy can be
     33   1.6    perry write-protected if you wish. These systems mount ramdisks as their
     34   1.6    perry root file systems once booted, and will not need to write to the
     35   1.6    perry floppy itself at any time -- indeed, once booted, the floppy may be
     36   1.6    perry removed from the disk drive.
     37   1.1      cgd 
     38   1.1      cgd Obviously, the steps necessary to prepare the distribution sets for
     39   1.1      cgd installation or upgrade depend on which installation medium you
     40   1.1      cgd choose.  The steps for the various media are outlined below.
     41   1.1      cgd 
     42   1.1      cgd To install or upgrade NetBSD using DOS floppies, you need to do the
     43   1.1      cgd following:
     44   1.1      cgd 
     45   1.2      cgd 	Count the number of "set_name.xx" files that make up the
     46   1.1      cgd 	distribution sets you want to install or upgrade.  You will
     47   1.1      cgd 	need one fifth that number of 1.2M floppies, or one sixth that
     48   1.1      cgd 	number of 1.44M floppies.  You should only use one size of
     49   1.1      cgd 	floppy for the install or upgrade procedure; you can't use
     50   1.3  mycroft 	some 1.2M floppies and some 1.44M floppies.
     51   1.1      cgd 
     52   1.1      cgd 	Format all of the floppies with DOS.  DO NOT make any of them
     53   1.1      cgd 	bootable DOS floppies, i.e. don't use "format/s" to format
     54   1.1      cgd 	them.  (If the floppies are bootable, then the DOS system
     55   1.1      cgd 	files that make them bootable will take up some space, and you
     56   1.1      cgd 	won't be able to fit as many distribution set parts per disk.)
     57   1.1      cgd 	If you're using floppies that are formatted for DOS by their
     58   1.1      cgd 	manufacturers, they probably aren't bootable, and you can use
     59   1.1      cgd 	them out of the box.
     60   1.1      cgd 
     61   1.1      cgd 	Place all of the "set_name.xx" files on the DOS disks, five
     62   1.1      cgd 	per disk if you're using 1.2M disks, six per disk if you're
     63   1.1      cgd 	using 1.44M disks.  How you do this is up to you; there are
     64   1.1      cgd 	many possibilities.  You could, for instance, use a DOS
     65   1.1      cgd 	terminal program to download them on to the floppies, or use
     66   1.1      cgd 	a UN*X-like system capable of reading and writing DOS file
     67   1.1      cgd 	systems (either with "mtools" or a real DOS file system)
     68   1.1      cgd 	to place them on the disk.
     69   1.1      cgd 
     70   1.1      cgd 	Once you have the files on DOS disks, you can proceed to the
     71   1.1      cgd 	next step in the installation or upgrade process.  If you're
     72   1.1      cgd 	installing NetBSD from scratch, go to the section on preparing
     73   1.1      cgd 	your hard disk, below.  If you're upgrading an existing
     74   1.1      cgd 	installation, go directly to the section on upgrading.
     75   1.1      cgd 
     76   1.1      cgd To install or upgrade NetBSD using a tape, you need to do the
     77   1.1      cgd following:
     78   1.1      cgd 
     79   1.1      cgd 	To install NetBSD from a tape, you need to make a tape that
     80   1.1      cgd 	contains the distribution set files, in "tar" format.  If
     81   1.1      cgd 	you're making the tape on a UN*X-like system, the easiest way
     82   1.1      cgd 	to do so is probably something like:
     83   1.1      cgd 
     84   1.1      cgd 		tar cf <tape_device> <dist_directories>
     85   1.1      cgd 
     86   1.1      cgd 	where "<tape_device>" is the name of the tape device that
     87   1.1      cgd 	describes the tape drive you're using (possibly /dev/rst0, or
     88   1.1      cgd 	something similar, but it will vary from system to system.
     89   1.1      cgd 	(If you can't figure it out, ask your system administrator.)
     90   1.1      cgd 	In the above example, "<dist_directories>" are the
     91   1.1      cgd 	distribution sets' directories, for the distribution sets you
     92   1.7    perry 	wish to place on the tape.  For instance, to put the
     93  1.12    perry 	"kern", "base" and "etc" distributions on tape (in
     94   1.7    perry 	order to do the absolute minimum installation to a new disk),
     95   1.7    perry 	you would do the following:
     96   1.1      cgd 
     97   1.9    mikel 		cd .../NetBSD-_VER		# the top of the tree
     98   1.1      cgd 		cd i386/binary
     99  1.12    perry 		tar cf <tape_device> base etc kern
    100   1.1      cgd 
    101   1.1      cgd 	(Note that you still need to fill in "<tape_device>" in the
    102   1.1      cgd 	example.)
    103   1.1      cgd 
    104   1.1      cgd 	Once you have the files on the tape, you can proceed to the
    105   1.1      cgd 	next step in the installation or upgrade process.  If you're
    106   1.1      cgd 	installing NetBSD from scratch, go to the section on preparing
    107   1.1      cgd 	your hard disk, below.  If you're upgrading an existing
    108   1.1      cgd 	installation, go directly to the section on upgrading.
    109   1.1      cgd 
    110   1.1      cgd To install or upgrade NetBSD using a remote partition, mounted via
    111   1.1      cgd NFS, you must do the following:
    112   1.1      cgd 
    113   1.1      cgd 	NOTE:	This method of installation is recommended only for
    114   1.1      cgd 		those already familiar with using BSD network
    115   1.1      cgd 		configuration and management commands.  If you aren't,
    116   1.1      cgd 		this documentation should help, but is not intended to
    117   1.1      cgd 		be all-encompassing.
    118   1.1      cgd 
    119   1.1      cgd 	Place the NetBSD distribution sets you wish to install into a
    120   1.1      cgd 	directory on an NFS server, and make that directory mountable
    121   1.1      cgd 	by the machine on which you are installing or upgrading NetBSD.
    122   1.1      cgd 	This will probably require modifying the /etc/exports file on
    123   1.1      cgd 	of the NFS server and resetting its mount daemon (mountd).
    124   1.1      cgd 	(Both of these actions will probably require superuser
    125   1.1      cgd 	privileges on the server.)
    126   1.1      cgd 
    127   1.1      cgd 	You need to know the the numeric IP address of the NFS server,
    128   1.1      cgd 	and, if the server is not on a network directly connected to
    129   1.1      cgd 	the machine on which you're installing or upgrading NetBSD,
    130   1.1      cgd 	you need to know the numeric IP address of the router closest
    131   1.1      cgd 	to the NetBSD machine.  Finally, you need to know the numeric
    132   1.1      cgd 	IP address of the NetBSD machine itself.
    133   1.1      cgd 
    134   1.1      cgd 	Once the NFS server is set up properly and you have the
    135   1.1      cgd 	information mentioned above, you can proceed to the next step
    136   1.1      cgd 	in the installation or upgrade process.  If you're installing
    137   1.1      cgd 	NetBSD from scratch, go to the section on preparing your hard
    138   1.1      cgd 	disk, below.  If you're upgrading an existing installation, go
    139   1.1      cgd 	directly to the section on upgrading.
    140   1.1      cgd 
    141   1.1      cgd To install or upgrade NetBSD by using FTP to get the installation
    142   1.1      cgd sets, you must do the following:
    143   1.1      cgd 
    144   1.1      cgd 	NOTE:	This method of installation is recommended only for
    145   1.1      cgd 		those already familiar with using BSD network
    146   1.1      cgd 		configuration and management commands.  If you aren't,
    147   1.1      cgd 		this documentation should help, but is not intended to
    148   1.1      cgd 		be all-encompassing.
    149   1.1      cgd 
    150   1.1      cgd 	The preparations for this installation/upgrade method are
    151   1.1      cgd 	easy; all you make sure that there's some FTP site from which
    152   1.1      cgd 	you can retrieve the NetBSD distribution when you're about to
    153   1.1      cgd 	install or upgrade.  You need to know the numeric IP address
    154   1.1      cgd 	of that site, and, if it's not on a network directly connected
    155   1.1      cgd 	to the machine on which you're installing or upgrading NetBSD,
    156   1.1      cgd 	you need to know the numeric IP address of the router closest
    157   1.1      cgd 	to the NetBSD machine.  Finally, you need to know the numeric
    158   1.1      cgd 	IP address of the NetBSD machine itself.
    159   1.1      cgd 
    160   1.1      cgd 	Once you have this information, you can proceed to the next
    161   1.1      cgd 	step in the installation or upgrade process.  If you're
    162   1.1      cgd 	installing NetBSD from scratch, go to the section on
    163   1.1      cgd 	preparing your hard disk, below.  If you're upgrading an
    164   1.1      cgd 	existing installation, go directly to the section on
    165   1.1      cgd 	upgrading.
    166   1.1      cgd 
    167   1.1      cgd If you are upgrading NetBSD, you also have the option of installing
    168   1.1      cgd NetBSD by putting the new distribution sets somewhere in your existing
    169   1.1      cgd file system, and using them from there.  To do that, you must do the
    170   1.1      cgd following:
    171   1.1      cgd 
    172   1.7    perry         Place the distribution sets you wish to upgrade somewhere in
    173  1.10    perry         your current file system tree. Please note that the /dev on
    174  1.10    perry         the floppy used for upgrades only knows about wd0, wd1, sd0,
    175  1.10    perry         sd1 and sd2. If you have more than two IDE drives or more than
    176  1.10    perry         three SCSI drives, you should take care not to place the sets
    177  1.10    perry         on the high numbered drives.
    178  1.10    perry 
    179  1.10    perry         At a bare minimum, you must upgrade the "base" and "kern"
    180  1.12    perry         binary distribution, and so must put the "base" and
    181  1.12    perry         "kern" sets somewhere in your file system.  If you wish,
    182  1.10    perry         you can do the other sets, as well, but you should NOT upgrade
    183  1.10    perry         the "etc" distribution; the "etc" distribution contains system
    184  1.10    perry         configuration files that you should review and update by hand.
    185   1.1      cgd 
    186   1.1      cgd 	Once you have done this, you can proceed to the next step in
    187   1.1      cgd 	the upgrade process, actually upgrading your system.
    188