NetBSD/distrib/notes/pc532/install

	$NetBSD: install,v 1.6 1998/01/19 20:34:35 phil Exp $

(IF you already have NetBSD/pc532 installed and you only want to update
your system, see the next section.)

To install NetBSD/pc532, there are several things you need to know.
First, NetBSD "autoconfigs" the scsi devices. floppy-144.fs has only
support for disks configured into the kernel. Starting the search at
SCSI address 0, lun 0 and increasing, the first disk found will be sd0
regardless of the address, the second will be sd1. KLONDIKE for example
has the following devices installed:

	sd0 -> ID 0 LUN 0: Quantum LP52S hard disk drive
	sd1 -> ID 1 LUN 0: Micropolis 4110 hard disk drive
	sd2 -> ID 2 LUN 0: Teac FC-1, 3.5" floppy disk drive
	sd3 -> ID 2 LUN 1: Teac FC-1, 5.25" floppy disk drive
	cd0 -> ID 3 LUN 0: Toshiba XM-4101TA CD-ROM drive
	st0 -> ID 4 LUN 0: Tandberg TDC3600 QIC tape drive

Only sd0-sd3 are supported by the floppy-144.fs kernel.

Next you need to know what the install script wants to do.  This install
is script on the ram disk root that can do most of the work of configuring
your disk.

  a) The script assumes your are using the first n sectors of your
	disk, where you can specify n.  It will allow you to create
	up to 5 file system partitions, one swap partition and one
	boot partition.

  b) You should know how many total sectors are on your disk.  The
	configure will report a head, track, and cylinder count, but
	I have found that on my disks, it reports something that makes
	a smaller disk than I really had.

  c) It is possible to have the install script make a partition
	over your save area AND not make a new file system, thus
	preserving what is there. Then, later you can make a new
	file system after you no longer need the stuff there. You
	will need to do only one boot to get things working from
	the disk.

The Install Procedure:

  a) Adjust your console device settings.
	The floppy-144.fs kernel will come up with 9600 baud, 7 bits,
	even parity and one stop bit. Adjust your terminal to match
	these settings. The monitor's baud rate can be changed with
	"baud d'9600".

  b) Get floppy-144.fs and boot the kernel.

	From Floppy: (and using the autoboot monitor)
	If you have a 1.44 meg SCSI floppy drive, you can put floppy-144.fs
	onto a 3.5" floppy disk. Insert the disk into your floppy
	drive and use the monitor's boot command to boot the default
	image from the floppy. The image booted will ask you for a
	kernel to load. Answer
		sdXa:/netbsd
	Replace X with your drive number. For KLONDIKE X would be "2".

	Tape:
	You will need to load a copy of floppy-144.fs into RAM.
		- load the floppy-144.fs at 0x260000
		- run at 0x3EB020
	The boot program will ask you now for a kernel to load. Answer
		md0a:/netbsd.gz

	Serial line:
	Provided with the distribution is source for program called 
	download.  (download.c)  This program when used as
	"download file" will read the contents of the file and
	output to standard output a byte sequence used by the pc532
	ROM monitor to download a binary file into RAM.  Using this
	program on a computer connected to the pc532, one can
	load a copy of floppy-144.fs into RAM at 0x260000.  The boot
	sequence is now the same as with tape.

  c) The floppy-144.fs will run the new sysinst utility as the standard
     setup.  It assumes a VT100 compatible terminal.  If you don't want
     to try using sysinst or you dont' have a VT100, type f followed by
     the return.  Then following these instructions for installation.
     If you want to use sysinst, read the i386 INSTALL instructions to
     learn about sysinst.  Note: sysinst does not support SLIP or PPP
     connections.

  c) Choose a disk geometry.  For me, the reported geometry left
	some sectors "unallocated".  That is, the autoconfig message
	said the disk had 2428 cylinders, 9 heads, and 93 sectors/track.
	This gives a total of 2032236 sectors, but I knew that I had
	2053880 sectors.

	To help in this process, there is a program "factor" that is
	on the floppy-144.fs.  The usage is "factor number" and it lists
	the prime factors of number.
	For example, with the 2053880 sector disk I got:

	---->~/sd1

	steelhead[3]$ factor 2053880
	2053880: 2 2 2 5 51347

	Not many to choose from, so I tried ...

	---->~/sd1
	steelhead[4]$ factor 2053820
	2053820: 2 2 5 103 997

	Now I'd like to get about a meg per track:
	steelhead[5]$ echo "2 * 997"|bc
	1994

	Now I need the number of tracks (or cylinders):
	steelhead[5]$ echo "2 * 5 * 103"|bc
	1030

	So I ended up choosing 1030 cylinders, 1 head, 1994 sectors/track.
	I "lost" only 60 sectors, but got a "resonable geometry".

  d) run "install"  -- it will ask you for the disk geometry and other
	questions.  It will ask you for the geometry and then ask you
	how many of those sectors you want to use for NetBSD. It also
	wants to know the size of your boot partition (to be used with
	the auto-boot monitor), your root partition, your swap partition,
	and then any other partitions you may want.  For the "other"
	partitions, it will ask for a mount point.  The mount point will
	be "relative to /" and should not include the leading "/".  Also,
	IF you do not want the partition to have newfs run on it (that is
	it might be the last one and have a copy of floppy-144.fs) enter "NO"
	to the mount point and it will not run newfs on the partition.
	It will enter the partition into the disklabel.

  e) look around, if you want ... and then halt NetBSD.

  f) reboot the machine.  Using the autoboot monitor, all you should have
	to do is give the ROM monitor command "boot".  The secondary
	UFS boot program eventually times out and auto-loads /netbsd.
	You can get it to do it faster by hitting "return".
	(If you are not using the autoboot monitor,  you will have to
	figure out the starting sector of the boot images partition
	and manually load the NetBSD boot loader from the disk using
	the read command.  If you would rather use the autoboot monitor
	you can get source and ROM images from the URL
	ftp://ftp.cs.wwu.edu/pub/pc532/mon.auto.tar.gz.)


  g) Now it is time to load all the other files of the distribution:
	You can do this via --

	a) a TCP/IP link (slip, ppp or plip)
		you have ifconfig, slattach, route, netstat,
		hostname and ftp on the mini-root. You can even
		use nfs...
		Plip is only an option if you have installed a
		centronics port in your pc532.
		You do have access to vi to edit your network
		files. (/etc/resolv.conf, ...)

	b) floppy disk

	c) tape

	d) cd-rom (If you have a CD with NetBSD/532, which most likely
	   won't happen for a while after _VER release.)
	   -- mount -rt cd9660 /dev/cd0a /mnt
	   Get the .tgz files from the cd-rom

	e) Use the ROM compatable "download" program.  The program
	   download is included in the initial installation and
           can be used as the receive end of the download by 
	   using it as "download -r file_to_write".  If the CRC is
	   correct, the file is retained.  If the CRC is not 
	   correct, the file is deleted.

  h) Load the .tgz files.  Choose a place to put them.  I would make
	a directory /gz.files and put them there.  If you are "short
	on space," you might want to load them and extract them one
	at a time.  A minimum installation is "base" and "etc".  It
	takes about 32 Megs installed + 20 Megs for the base.tgz.

  i) Extract the tar files in /.  For example, if your *.tgz were
	in a directory /gz.files, to extract base.tgz you would:

	- cd / 
	- tar -xpzf /gz.files/base.tgz --unlink

	Add v to the flags if you want a verbose extract.
	The --unlink is to make sure that the install versions
	of sh, init, ... are replaced by their proper versons
	in base.tgz.  I think it is wise to include the --unlink
	for other things.

  j) Extract at least "base", "etc" and "kern" for a new installation.
	For "update" extracts, move /etc to /etc.old and then extract
	"etc".  You should extract "etc" for upgrades.  For "full" 
	installations, 	extract all files.

  k) Edit the information in /etc

	- rc.conf - Many of the following things can be configured here
	- hosts   -  host name and address information
	- myname  -  your host name
	- mygate  -  hostname of gateway (assuming you have one)
	- resolv.conf - which nameserver to use
	- ifconfig.{sl0,ppp0,plip0} - interface hostname
	- netstart - configures the network and says if sendmail should
			be started
	- ttys    -  make sure the console entry has the correct speed
	- gettytab - I find "ap" instead of "ep" in the default entry
			works better for me.
	- fstab	  -  make sure it includes all partitions you want mounted
	- localtime - this is usually a link into /usr/share/zoneinfo

	Now you can adjust the kernel's default baud rate to match your
	monitor's default baud rate. Do the following:
		gdb -w /netbsd
		set scndefaultrate = YOUR_BAUD_RATE
		quit
	where YOUR_BAUD_RATE is the actual value, 19200, 38400 or
	something slower than 9600.
	If you set scndefaultrate to something bogus, you'll probably
	not be able to reboot... So be carefull!
	

  l) Reboot the machine and it should come up in multi-user mode *IF*
	you got it configured correctly.

  m) Enjoy!  And help fix bugs and improve NetBSD/pc532!