Home | History | Annotate | Line # | Download | only in hp300
xfer revision 1.1.2.1
      1 Installation is supported from several media types, including:
      2 	Tape
      3 	CD-ROM
      4 	NFS
      5 	FTP
      6 
      7 The steps necessary to prepare the distribution sets
      8 for installation depend on which method of installation
      9 you choose.  The various methods are explained below.
     10 
     11 To prepare for installing via a tape:
     12 
     13 	If you wish to load SYS_INST from tape, it must
     14 	appear on the tape before any other files.  To copy
     15 	this onto tape, use a command like the following:
     16 
     17 		dd if=SYS_INST of=<tape_device> bs=20b
     18 
     19 	Note that not all HP BOOTROMs support booting from
     20 	SCSI tapes.
     21 
     22 	Copying the miniroot to disk from tape is not currently
     23 	supported.  However, it is planned for a future release.
     24 
     25 	If you wish to extract binary sets onto your disk from
     26 	tape, you must first place them on the tape.  The easiest
     27 	way to do this is with the dd(1) command.  Make sure you
     28 	use a `no-rewind-on-close' tape device.  For example:
     29 
     30 		for file in base11.tar.gz etc11.tar.gz; do
     31 			dd if=${file} of=/dev/nrst0 bs=20b
     32 		done
     33 
     34 	Note that depending on your tape drive, you may need to
     35 	explicitly set the EOF marker at the end of each file.
     36 	It may also be necessary to use the `conv=osync' argument
     37 	to dd(1).  Note that this argument is incompatible with the
     38 	`bs=' argument.  Consult the tape-related manual pages on the
     39 	system where the tapes are created for more details.
     40 
     41 To prepare for installing via NFS:
     42 
     43 	SYS_INST currently requires an NFS server from which to
     44 	copy the miniroot.
     45 
     46 		* This filesystem must be exported with root permissions,
     47 		  but may be exported read-only.
     48 
     49 		* The miniroot image _must_ reside in the `root' of the
     50 		  mounted filesystem.  For example, if the client system
     51 		  mounts `server:/u', then the miniroot image must reside
     52 		  in /u on the server.  This is due to limitations in the
     53 		  file lookup code used in SYS_INST, and may be fixed in
     54 		  a future release.
     55 
     56 		* If you also wish to install the binary sets from the
     57 		  NFS server, place them in a properly exported filesystem
     58 		  on the server.  Note that these files do not suffer from
     59 		  the same placement restrictions as the miniroot.
     60 
     61 To prepare for installing via FTP:
     62 
     63 	It is possible, using the `install' and `upgrade'
     64 	programs in the miniroot, to extract the binary sets
     65 	directly onto disk from an FTP server.  This is by far
     66 	the easiest installation method, as you may specify to
     67 	have all sets extracted at once, providing that they
     68 	are located in the same directory on the server.
     69 
     70 	All that is required in this case is that you have
     71 	network access to an FTP server.  This may be your
     72 	account on another system, or may even be ftp.NetBSD.ORG
     73 	itself.  If you wish to use ftp.NetBSD.ORG as your FTP
     74 	file server, you may want to keep the following information
     75 	handy:
     76 
     77 		IP Address: 205.149.163.23
     78 		Login: anonymous
     79 		Password: <your e-mail address>
     80 		Server path: /pub/NetBSD/NetBSD-1.1/hp300/binary
     81