initial import of NetBSD tree

8 files changed, 529 insertions, 0 deletions

diff --git a/distrib/notes/pc532/contents b/distrib/notes/pc532/contents
new file mode 100644
index 00000000000..469913d7fa6
--- /dev/null
+++ b/distrib/notes/pc532/contents
@@ -0,0 +1,113 @@
+The pc532-specific portion of the NetBSD 1.0 release is found in the
+"pc532" subdirectory of the distribution.  That subdirectory contains
+the files as follows:
+
+.../NetBSD-1.0/pc532/
+
+	INSTALL			Installation notes; this file.
+	CKSUM			output of "cksum *.gz"
+	ram.root.gz		Ram root disk
+	util.tar.gz		things to help the install
+	netbsd.rd.9600.gz	"ram disk" root kernel, 9600 baud
+	netbsd.rd.19200.gz	"ram disk" root kernel, 19200 baud
+	netbsd.sd0.9600.gz	sd0a root, 9600 baud console
+	netbsd.sd0.19200.gz	sd0a root, 19200 baud console
+	netbsd.sd1.9600.gz	sd1a root, 9600 baud console
+	netbsd.sd1.19200.gz	sd1a root, 19200 baud console
+	base.tar.gz		base distribution
+	comp.tar.gz		compiler tools & libraries
+	etc.tar.gz		files for /etc
+	games.tar.gz		/usr/games and friends
+	man.tar.gz		/usr/man
+	misc.tar.gz		various
+	text.tar.gz		groff and friends
+
+
+The binary distribution consists of the following files:
+
+	base.tar.gz
+		The NetBSD/pc532 1.0 base binary distribution.  You
+		MUST install this distribution set.  It contains the
+		base NetBSD utilities that are necessary for the
+		system to run and be minimally functional.  It
+		excludes everything described below.
+		[ 15.1M gzipped ]
+
+	comp.tar.gz
+		The NetBSD/pc532 Compiler tools.  All of the tools
+		relating to C, C++, and FORTRAN (yes, there are two!).
+		This set includes the system include files
+		(/usr/include), the linker, the compiler tool chain,
+		and the various system libraries.  This set also includes
+		the manual pages for all the utilities it contains, as well
+		as the system call and library manual pages.
+		[ 4.2M gzipped ]
+
+	etc.tar.gz
+		This distribution set contains the system
+		configuration files that reside in /etc and in several
+		other places.  This set MUST be installed if you are
+		installing the system from scratch, but should NOT be
+		used if you are upgrading.  (If you are upgrading,
+		it's recommended that you get a copy of this set and
+		CAREFULLY upgrade your configuration files by hand.)
+		[ 50K gzipped ]
+
+	games.tar.gz
+		This set includes the games and their manual pages.
+		[ 2.4M gzipped ]
+
+	man.tar.gz
+		This set includes all of the manual pages for the
+		binaries and other software contained in the base set.
+		Note that it does not include any of the manual pages
+		that are included in the other sets.
+		[ 0.7M gzipped ]
+
+	misc.tar.gz
+		This set includes the system dictionaries (which are
+		rather large), the typesettable document set, and
+		man pages for other architectures which happen to be
+		installed from the source tree by default.
+		[ 1.7M gzipped, 5.6M uncompressed ]
+
+	text.tar.gz
+		This set includes NetBSD's text processing tools,
+		including groff, all related programs, and their
+		manual pages.
+		[ 1.1M gzipped ]
+
+The pc532 distribution set does not include a security distribution.
+If you are in the US and want the security distribution you must
+get the security source distribution and recompile libcrypt.a and
+recompile the following programs:
+	ed, ftpd, makekey, rexecd, uucpd, init, lock, login, passwd,
+	skeyinit, su, tn3270, pppd
+
+
+The initial installation process on a pc532 without NetBSD/pc532
+is supported by the following files:
+
+	Initial kernels to loaded into memory and run:
+
+	  netbsd.rd.9600.gz	"ram disk" root kernel, 9600 baud
+	  netbsd.rd.19200.gz	"ram disk" root kernel, 19200 baud
+
+	The initial root file system for the above kernels
+
+	  ram.root.gz		Ram root disk
+
+	Utility programs for helping with the install after a
+	mini-root has been built on a hard disk
+
+	  util.tar.gz		things to help the install
+
+	Bootable kernels for placement in the file system to boot
+	from hard disk.
+	
+	  netbsd.sd0.9600.gz	sd0a root, 9600 baud console
+	  netbsd.sd0.19200.gz	sd0a root, 19200 baud console
+	  netbsd.sd1.9600.gz	sd1a root, 9600 baud console
+	  netbsd.sd1.19200.gz	sd1a root, 19200 baud console
+
+
diff --git a/distrib/notes/pc532/hardware b/distrib/notes/pc532/hardware
new file mode 100644
index 00000000000..1a338056462
--- /dev/null
+++ b/distrib/notes/pc532/hardware
@@ -0,0 +1,20 @@
+NetBSD/pc532 1.0 runs on a PC532 computer.  It supports a subset of the
+"standard" hardware to date.  This is defined as:
+
+	4 - 32 Megs of memory
+	8 serial lines done by 4 scn2681 chips
+	the NCR DP8490 SCSI chip (scsi only)
+		Most SCSI disks work (fixed and floppy)
+		A few SCSI tapes work
+		Some SCSI CD-ROM drives work
+
+NetBSD/pc532 currently expects the ROM monitor to be the "autoboot
+monitor" of Oct/Nov 1991.  It includes support to set up auto booting
+of NetBSD, including a secondary boot program that the autoboot monitor
+will load that in turn loads the NetBSD kernel from a NetBSD file system.
+
+Most of the pc532 specific development of NetBSD/pc532 was done on a
+machine with 8-Megs of memory.  It should run with 4-Megs of memory
+although it may be slower.
+
+
diff --git a/distrib/notes/pc532/install b/distrib/notes/pc532/install
new file mode 100644
index 00000000000..fb9e521ff6e
--- /dev/null
+++ b/distrib/notes/pc532/install
@@ -0,0 +1,220 @@
+(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. inst-11.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 inst-11.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 inst-11.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 inst-11.fs.
+	If you have a 1.44 meg SCSI floppy drive, you can put this
+	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".
+
+	If you don't have a floppy drive, you will have to
+		- load the inst-11.fs at 0x288000
+		- run at 0x3EB820
+	The boot program will ask you now for a kernel to load. Answer
+		rd0a:/netbsd
+
+  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 inst-11.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 the number of tracks:
+	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 ram.root and your
+	kernels) 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, it's time to warm
+	up your eprom burner :-)
+
+  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.
+
+	b) floppy disk
+
+	c) tape
+
+	d) cdrom (If you have a CD with NetBSD/532 ...)
+
+	e) using kermit. (See the notes at the end of this file.)
+
+	f) some other method? (Let me know about it.)
+
+  h) Load the tar.gz 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 + 15 Megs for the base.tar.gz.
+
+  i) Extract the tar files in /.  For example, if your *.tar.gz were
+	in a directory /gz.files, to extract base.tar.gz you would:
+
+	- cd / 
+	- tar -xpzf /gz.files/base.tar.gz --unlink
+
+	Add v to the flags if you want a verbose extract.
+	The --unlink is to make sure that the "ram.root" versions
+	of sh, init, ... are replaced by their full featured versons
+	in base.tar.gz.  I think it is wise to include the --unlink
+	for other things.
+
+  j) Extract at least "base" and "etc" for a new installation.  For
+	"update" extracts, don't extract "etc" directly unless you 
+	have saved your current /etc tree.  For "full" installations,
+	extract all files.
+
+  k) Edit the information in /etc
+
+	- hosts   -  host name and address information
+	- myname  -  your host name
+	- mygate  -  hostname of gateway (assuming you have one)
+	- resolv.conf - which nameserver to use
+	- hostname.{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
+	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!
+
+
+For those who choose to use kermit to help in getting NetBSD/pc532
+installed:
+
+	The following is the Kermit copyright:
+
+	Copyright (C) 1985, 1994, Trustees of Columbia University in the
+	City of New York.  The C-Kermit software may not be, in whole or
+	in part, licensed or sold for profit as a software product
+	itself, nor may it be included in or distributed with commercial
+	products or otherwise distributed by commercial concerns to their
+	clients or customers without written permission of the Office of
+	Kermit Development and Distribution, Columbia University.  This
+	copyright notice must not be removed, altered, or obscured.
+
+	Due to this copyright, we can not include kermit with the standard
+	NetBSD/pc532 distribution.  
+
+	The Office of Kermit Development and Distribution of Columbia
+	University in the City of New York has given permission for
+	us to distribute a NetBSD/pc532 binary.  It is available primarily
+	for bootstrapping purposes and therefore is not a complete package,
+	lacking source code, various supporting text files, and the user
+	manual. Users who wish to use C-Kermit after the bootstrapping
+	process should obtain the full package, including the manual
+	"Using C-Kermit", from Columbia University.
+
+	The NetBSD/pc532 binary is available via ftp from 
+	iceberg.cs.wwu.edu in the directory pub/NetBSD/pc532 as the file
+	kermitbin.tar.gz.
+
diff --git a/distrib/notes/pc532/legal b/distrib/notes/pc532/legal
new file mode 100644
index 00000000000..c61c3a90db2
--- /dev/null
+++ b/distrib/notes/pc532/legal
@@ -0,0 +1,85 @@
+
+	This product includes software developed by the Alice Group.
+
+	This product includes software developed by Philip L. Budne.
+
+	This product includes software developed by Christopher G. Demetriou.
+
+	This product includes software developed by Philip A. Nelson.
+
+	This product includes software at the Helsinki University of
+	Technology.  
+
+Some files have the following copyright:
+/* 
+ * Copyright (c) 1992 Helsinki University of Technology
+ * All Rights Reserved.
+ * 
+ * Permission to use, copy, modify and distribute this software and its
+ * documentation is hereby granted, provided that both the copyright
+ * notice and this permission notice appear in all copies of the
+ * software, derivative works or modified versions, and any portions
+ * thereof, and that both notices appear in supporting documentation.
+ * 
+ * HELSINKI UNIVERSITY OF TECHNOLOGY ALLOWS FREE USE OF THIS SOFTWARE IN
+ * ITS "AS IS" CONDITION. HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIMS ANY
+ * LIABILITY OF ANY KIND FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE
+ * USE OF THIS SOFTWARE.
+ */
+
+
+At least one file contains:
+
+ * Copyright 1990 by Open Software Foundation,
+ * Grenoble, FRANCE
+ *
+ * 		All Rights Reserved
+ * 
+ *   Permission to use, copy, modify, and distribute this software and
+ * its documentation for any purpose and without fee is hereby granted,
+ * provided that the above copyright notice appears in all copies and
+ * that both the copyright notice and this permission notice appear in
+ * supporting documentation, and that the name of OSF or Open Software
+ * Foundation not be used in advertising or publicity pertaining to
+ * distribution of the software without specific, written prior
+ * permission.
+ * 
+ *   OSF DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE
+ * INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS,
+ * IN NO EVENT SHALL OSF BE LIABLE FOR ANY SPECIAL, INDIRECT, OR
+ * CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
+ * LOSS OF USE, DATA OR PROFITS, WHETHER IN ACTION OF CONTRACT,
+ * NEGLIGENCE, OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
+ * WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+ */
+
+
+Some files have the following copyright:
+
+/* 
+ * Mach Operating System
+ * Copyright (c) 1992 Carnegie Mellon University
+ * Copyright (c) 1992 Helsinki University of Technology
+ * All Rights Reserved.
+ * 
+ * Permission to use, copy, modify and distribute this software and its
+ * documentation is hereby granted, provided that both the copyright
+ * notice and this permission notice appear in all copies of the
+ * software, derivative works or modified versions, and any portions
+ * thereof, and that both notices appear in supporting documentation.
+ * 
+ * CARNEGIE MELLON AND HELSINKI UNIVERSITY OF TECHNOLOGY ALLOW FREE USE
+ * OF THIS SOFTWARE IN ITS "AS IS" CONDITION.  CARNEGIE MELLON AND
+ * HELSINKI UNIVERSITY OF TECHNOLOGY DISCLAIM ANY LIABILITY OF ANY KIND
+ * FOR ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
+ * 
+ * Carnegie Mellon requests users of this software to return to
+ * 
+ *  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
+ *  School of Computer Science
+ *  Carnegie Mellon University
+ *  Pittsburgh PA 15213-3890
+ * 
+ * any improvements or extensions that they make and grant Carnegie Mellon 
+ * the rights to redistribute these changes.
+ */
diff --git a/distrib/notes/pc532/prep b/distrib/notes/pc532/prep
new file mode 100644
index 00000000000..73ad339805e
--- /dev/null
+++ b/distrib/notes/pc532/prep
@@ -0,0 +1,3 @@
+The major preparation needed is to make sure you can recover any
+current bits stored on your pc532.  If you don't care about your
+data on the disk, you don't need to do anything.
\ No newline at end of file
diff --git a/distrib/notes/pc532/upgrade b/distrib/notes/pc532/upgrade
new file mode 100644
index 00000000000..57b3b74eaef
--- /dev/null
+++ b/distrib/notes/pc532/upgrade
@@ -0,0 +1,55 @@
+The upgrade to NetBSD 1.0 is a binary upgrade; it would be prohibitive
+to make users upgrade by compiling and installing the 1.0 sources, and
+it would be very difficult to even compile a set of instructions that
+allowed them to do so.  
+
+To do the upgrade, you must have at least base.tar.gz on disk and
+a copy of the proper netbsd.sdx.yyyy.  It will require quite a bit
+of disk space to do the upgrade.
+
+Since upgrading involves replacing the kernel, and most of the system
+binaries, it has the potential to cause data loss.  You are strongly
+advised to BACK UP ANY IMPORTANT DATA ON YOUR DISK, whether on the
+NetBSD partition or on another operating system's partition, before
+beginning the upgrade process.
+
+To upgrade your system, follow the following instructions:
+
+	Make sure your are root.  Just in case the new binaries don't
+	run with the old kernel, make copies of several key binaries
+	from /bin, /sbin and /usr/bin in some directory.  (Things like
+	sh, cp, ls, rm, tar, halt, and others.)
+
+	Extract the tar.gz files.  Remember to use the --unlink
+	option with tar so it can replace binaries currently in use.
+	For example, to extract base.tar.gz:
+
+		cd / 
+		tar -xpzf /gz.files/base.tar.gz --unlink
+
+	Extract all the tar.gz files you want.  You should carefully
+	work at upgrading /etc.  There may be changes to file formats
+	depending on what version of NetBSD/pc532 you are running.
+
+	BE CAREFUL IF YOU ARE RUNNING WITH SECURITY.  The distribution
+	binaries don't support it.  It would be reasonable to save a
+	copy of master.passwd and remove all passwords until after
+	you upgrade to the new security level.
+
+	Place the proper netbsd.sdX.YYYY in / as the file netbsd.
+
+	Reboot.
+
+	After reboot, you should make sure you check your new file systems.
+	Also, you may wish to upgrade your file systems to the new file
+	system format.  After the install process is complete,
+	use "fsck -c 2" to upgrade the file systems. Read the fsck(8)
+	manual page for more details.
+
+	If you upgrade your file systems, you will want to make sure
+	you have the most recent ufs boot program if you use the
+	NetBSD boot program to read the kernel off a ufs file system.
+	Use bim(8) to remove your old boot program and install the
+	newest one if you are using the autoboot monitor.
+
+
diff --git a/distrib/notes/pc532/whatis b/distrib/notes/pc532/whatis
new file mode 100644
index 00000000000..3399a139941
--- /dev/null
+++ b/distrib/notes/pc532/whatis
@@ -0,0 +1,14 @@
+For the pc532 port, there are a few known problems.  They include:
+
+  a) ppp reports a lot of input errors on some machines.
+
+  b) Some tape drives do not work very well.  Some have hung the system.
+
+  c) The serial drivers do not have all the desired features.  (ttyflags
+	is the most glaring.)
+
+  d) The disk driver is polled, not interrupt driven.
+
+  e) kernel support for debugging is not working correctly.
+
+  f) shared libraries are not used yet.
\ No newline at end of file
diff --git a/distrib/notes/pc532/xfer b/distrib/notes/pc532/xfer
new file mode 100644
index 00000000000..a36b90a8c78
--- /dev/null
+++ b/distrib/notes/pc532/xfer
@@ -0,0 +1,19 @@
+The "standard" method of getting NetBSD/pc532 onto your pc532 is
+via the console terminal and using the downloading parts of the
+ROM monitor.  As such, usually another computer has the distribution
+on disk and is connected via a serial line to your pc532's console
+port.  A terminal connected to the attached host computer is used
+to access the pc532 console via a terminal program.  
+
+You may need to find and read the documentation about the ROM monitor
+download command and other low level comands.
+
+Other methods of getting NetBSD/pc532 on your pc532 may include 
+SCSI tape or SCSI floppy disk or cloning a disk on a system
+already running NetBSD/pc532.
+
+If you have some operating system already running on your pc532,
+you can use that OS to get NetBSD/pc532 on a hard disk much easier than
+with the ROM monitor.  (NetBSD/pc532 was developed from Minix/pc532
+until it was self hosting.  You can run NetBSD and Minix or other OS
+off the same disk.)
\ No newline at end of file