from netbsd

7 files changed, 227 insertions, 45 deletions

diff --git a/distrib/notes/sparc/contents b/distrib/notes/sparc/contents
index 8e22ef36da0..c013629d235 100644
--- a/distrib/notes/sparc/contents
+++ b/distrib/notes/sparc/contents
@@ -1,8 +1,8 @@
-The sparc-specific portion of the NetBSD 1.0 release is found in the
+The sparc-specific portion of the NetBSD 1.1 release is found in the
 "sparc" subdirectory of the distribution.  That subdirectory is laid
 out as follows:
 
-.../NetBSD-1.0/sparc/
+.../NetBSD-1.1/sparc/
 			binary/		sparc binary distribution sets;
 					see below.
 
@@ -13,20 +13,20 @@ out as follows:
 					and installation script.
 
 The NetBSD/sparc binary distribution sets contain the binaries which
-comprise the NetBSD 1.0 release for the sparc.  There are seven binary
+comprise the NetBSD 1.1 release for the sparc.  There are seven binary
 distribution sets, and the "security" distribution set.  The binary
 distribution sets can be found in subdirectories of the "sparc/binary"
-subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
+subdirectory of the NetBSD 1.1 distribution tree, and are as follows:
 
-	base10	The NetBSD/sparc 1.0 base binary distribution.  You
+	base11	The NetBSD/sparc 1.1 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
 		includes shared library support, and excludes
 		everything described below.
-		[ 7.3M gzipped, 22.7M uncompressed ]
+		[ 8.0M gzipped, 24.4M uncompressed ]
 
-	comp10	The NetBSD/sparc Compiler tools.  All of the tools
+	comp11	The NetBSD/sparc 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,
@@ -35,38 +35,38 @@ subdirectory of the NetBSD 1.0 distribution tree, and are as follows:
 		set).  This set also includes the manual pages for all
 		of the utilities it contains, as well as the system
 		call and library manual pages.
-		[ 4.9M gzipped, 15.9M uncompressed ]
+		[ 5.4M gzipped, 17.6M uncompressed ]
 
-	etc10	This distribution set contains the system
+	etc11	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, 285K uncompressed ]
+		[ 62K gzipped, 338K uncompressed ]
 
-	games10	This set includes the games and their manual pages.
-		[ 1.2M gzipped, 3.3M uncompressed ]
+	games11	This set includes the games and their manual pages.
+		[ 2.9M gzipped, 7.4M uncompressed ]
 
-	man10	This set includes all of the manual pages for the
+	man11	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, 2.9M uncompressed ]
+		[ 0.8M gzipped, 3.3M uncompressed ]
 
-	misc10	This set includes the system dictionaries (which are
+	misc11	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.9M uncompressed ]
+		[ 1.9M gzipped, 6.6M uncompressed ]
 
-	text10	This set includes NetBSD's text processing tools,
+	text11	This set includes NetBSD's text processing tools,
 		including groff, all related programs, and their
 		manual pages.
 		[ 0.8M gzipped, 3.1M uncompressed ]
 
-The sparc security distribution set is named "secr10" and can be found
+The sparc security distribution set is named "secr11" and can be found
 in the "sparc/security" subdirectory of the NetBSD 1.0 distribution
 tree.  It contains crypt.c (the source file for the DES encryption
 algorithm) and the binaries which depend on it.  It can only be found
diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware
index 977abd4f808..d425275cfe8 100644
--- a/distrib/notes/sparc/hardware
+++ b/distrib/notes/sparc/hardware
@@ -1,6 +1,16 @@
-NetBSD/sparc 1.0 runs on Sun4c class machines only, which includes
-the SS1, SS1+, SS2, IPC, ELC, IPX, and the SLC.  It does not run
-on Sun4, Sun4m, or Sun4d machines.
+NetBSD/sparc 1.1 runs on the following classes of machines:
+	- sun4c (e.g. the SS1, SS1+, SS2, IPC, ELC, IPX, and SLC)
+	- sun4 (e.g. the 4/100, 4/200, and 4/300.   note that support
+		for the 4/400 processor is incomplete)
+
+NetBSD/sparc 1.1 does *not* run on these machines (yet):
+	- sun-4/400 (lacking support for the I/O cache, and has
+			ethernet problems)
+	- sun4m (e.g. sparc classic, 4, 5, 10, and 20)
+	- sun4d (e.g. sparc center 2000)
+
+Work on porting NetBSD/sparc to the sun4m platform is currently in 
+progress, but was not ready in time for the 1.1 release.
 
 The minimal configuration requires 4M of RAM and ~60M of disk space.
 To install the entire system requires much more disk space, and to run
@@ -10,16 +20,36 @@ around 16M of RAM, getting more RAM is more important than getting a
 faster CPU.)
 
 Supported devices include:
-	Video: cgthree, cgsix, and bwtwo frame buffers
-	Serial ports: ttya and ttyb
-	On-board AMD Lance ethernet
-	Some SCSI CD-ROM drives
-	Sun keyboard and mouse
+	sun4c sbus video: 
+		cgsix, cgthree, and bwtwo frame buffers
+	sun4 video (not thoroughly tested?): 
+		P4 on-board bwtwo, and VME cgtwo card
+	serial ports: 
+		ttya and ttyb (can be used as console if needed)
+	ethernet: 
+		on-board AMD Lance ethernet ("le0"), 
+		Sbus AMD Lance ethernet cards, 
+		on-board Intel 82586 ethernet (ie0 on 4/100's and 4/200's), 
+		VME Intel 82586 ethernet cards
+	SCSI: 
+		on-board "esp" SCSI controller (sun4c's, and the 4/300),
+		sbus "esp" SCSI controller, 
+		Sun "SUN-3"/"si" VME SCSI controller (polled mode only, slow),
+		Sun "SCSI Weird"/"sw" on-board controller (4/110 only, polled)
+	VME disks:
+		Xylogics 7053 VME/SMD disk controller ("xd"),
+		Xylogics 450/451 VME disk controller ("xy")
+		[note: VME/IPI disks are not supported]
+	sun floppy disk drive on sun4c's
+	sun keyboard and mouse
+	sun4c audio
+
 
 Hardware the we do NOT currently support, but get many questions
 about:
-	The floppy drive.
+	sun4m, including multiprocessor machines
+	interrupt driven SCSI driver for sun-4/100's and sun-4/200's
+
+The next release will hopefully run on many more machines.  In
+particular, some Sun4m support will be there.
 
-The next release will likely run on many more machines.  In
-particular, some Sun4 support will be there, and perhaps even
-Sun4m.
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install
index cb9437e7f6c..3fb8ac3de5f 100644
--- a/distrib/notes/sparc/install
+++ b/distrib/notes/sparc/install
@@ -8,6 +8,7 @@ a single disk attached. Alternatively, you could use SunOS (booted from
 a local disk) and install NetBSD onto a second disk. For the latter method,
 skip to the section "Installing from SunOS" below.
 
+
 Installing using a diskless setup.
 
 First, you must setup a diskless client configuration on a server. Consult
@@ -16,11 +17,36 @@ Put all the *.tar.gz files you want to install into the root directory
 for your client on the server.
 
 Next, unpack base.tar.gz on the server in the root directory for your machine.
+If you elect to you a separately NFS-mounted filesystem for `/usr' on your
+diskless setup, make sure the "./usr" base files in base.tar.gz end up
+in the correct location. One way to do this is to temporarily use a loopback
+mount on the server, re-routing <root>/usr to your server's exported
+NetBSD "/usr" directory. Also put the kernel into the root directory.
+
 A few configuration files need to be edited:
 
 	<root>/etc/hosts
+		Add the IP addresses of both server and client.
+
 	<root>/etc/myname
+		This files contains the client's hostname; use the same
+		name as in <root>/etc/hosts.
+
 	<root>/etc/fstab
+		Enter the entries for the remotely mounted filesystems.
+		For example:
+			server:/export/root/client       /     nfs  rw 0 0
+			server:/export/exec/sun4.netbsd  /usr  nfs  rw 0 0
+
+Now you must populate the the `/dev' directory for your client. If you server
+runs SunOS 4.x, you can simply change your working directory to `<root>/dev'
+and run the MAKEDEV script: `sh MAKEDEV all'.
+
+On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error
+messages about unknown user and groups. These errors are inconsequential
+for the purpose of installing NetBSD. However, you may want to correct them
+if you plan to the diskless setup regularly. In that case, you may re-run
+MAKEDEV on your NetBSD machine once it has booted.
 
 Boot your workstation from the server by entering the appropriate `boot'
 command at the monitor prompt. Depending on the PROM version in your machine,
@@ -42,12 +68,42 @@ instead of `ok', type:
     ok
 ]]
 
-Start the installation procedure:
+If you use a diskless setup with a separately NFS-mounted /usr filesystem,
+mount /usr by hand now:
+
+netbsd# mount /usr
+
+At this point, it's worth checking the disk label and partition sizes on
+the disk you want to install NetBSD onto. NetBSD understands SunOS-style
+disklabels, so if your disk was previously used by SunOS there will be
+a usable label on it. Use `disklabel -e <disk>' (where <disk> is the
+device name assigned by the NetBSD kernel, e.g. `sd0') to view and
+modify the partition sizes. A comfortable size for the root filesystem
+partition is about 20MB; a good initial size for the swap partition is
+twice the amount of physical memory in your machine (though, unlike
+SunOS 4.x, there are no restrictions on the size of the swap partition
+that would render part of your memory unusable). A full binary installation
+takes about 60MB in `/usr'. Make all your partitions start and end on
+cylinder boundaries.
+
+NOTE: if you are installing on a SCSI disk that does *not* have a SunOS
+or NetBSD label on it, you may still be able to use disklabel(8) but you'll
+have to create all partitions from scratch. If your disk is listed in
+`/etc/disktab', you may use the entry (which in most cases only defines
+a `c' partition to describe the whole disk) to put an initial label on
+the disk.
+
+
+If you are upgrading a NetBSD installation, start the upgrade script:
+
+#netbsd ./upgrade.sh
+
+else, start the installation procedure:
 
 netbsd# ./install.sh
 
 
-This script will do most of the work of transferring the system from the
+These scripts will do most of the work of transferring the system from the
 tar files onto your disk. You will frequently be asked for confirmation
 before the script proceeds with each phase of the installation process.
 Occasionally, you'll have to provide a piece of information such as the
diff --git a/distrib/notes/sparc/legal b/distrib/notes/sparc/legal
index 295e8480bdc..d82afb8856f 100644
--- a/distrib/notes/sparc/legal
+++ b/distrib/notes/sparc/legal
@@ -1,4 +1,17 @@
-	This product includes software developed by Philip A. Nelson.
+	This product includes software developed by the Alice Group.
 
-	This product includes software developed by Paul Kranenburg.
+	This product includes software developed by Charles D. Cranor.
+
+	This product includes software developed by Peter Galbavy.
+
+	This product includes software developed by Rolf Grossmann.
+
+	This product includes software developed by David Miller.
+
+	This product includes software developed by Gordon W. Ross.
+
+	This product includes software developed by Charles Hannum, by the
+	University of Vermont and State Agricultural College and Garrett A.
+	Wollman, by William F. Jolitz, and by the University of California,
+	Berkeley, Lawrence Berkeley Laboratory, and its contributors.
 
diff --git a/distrib/notes/sparc/upgrade b/distrib/notes/sparc/upgrade
index 4141ecd51e6..b8f5b80ae75 100644
--- a/distrib/notes/sparc/upgrade
+++ b/distrib/notes/sparc/upgrade
@@ -1,5 +1,6 @@
-Upgrading NetBSD/sparc is not something someone is likely to do,
-since this is the first real distribution.  Since a number of
-critical interfaces have changed quite significantly, your best
-bet is to reinstall completely, perhaps saving a few files in
-/etc and /usr/local.
+To upgrade to NetBSD 1.1 from a previous version follow the instructions
+in the section "Installing NetBSD", but run the script `upgrade.sh'
+in stead of `install.sh'.
+
+The upgrade script will use the existing disk partitions to install the
+new system in, and also preserves the files in `/etc'.
diff --git a/distrib/notes/sparc/whatis b/distrib/notes/sparc/whatis
index a354a011d93..cbd9dcecc3a 100644
--- a/distrib/notes/sparc/whatis
+++ b/distrib/notes/sparc/whatis
@@ -1,5 +1,5 @@
-NetBSD 1.0 is the first release for the sparc, although numerous
-people have been running "snapshots" for some time.  It has all the
-standard NetBSD features, plus you can also enable SunOS binary
-compatibility in the kernel which will run more than 95% of SunOS
-executables.
+NetBSD 1.1 is the second release for the sparc. Many more sparc
+models and devices are now supported.
+In addition to the SunOS 4.1 compatibility present in NetBSD/sparc 1.0,
+version 1.1 will also run some number of SunOS 5 (SVR4) executables
+in binary emulation mode.
diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer
index 445ec92c59f..aed6d069e1b 100644
--- a/distrib/notes/sparc/xfer
+++ b/distrib/notes/sparc/xfer
@@ -1 +1,83 @@
-Installation is done from SunOS, or a previous NetBSD install.
+Installation is supported from several media types, including:
+	NFS partitions
+	FTP
+	Tape
+
+The steps necessary to prepare the distribution sets
+for installation depend on which method of installation
+you choose.  The various methods are explained below.
+
+To prepare for installing via an NFS partition:
+
+	Since the current NetBSD/sparc installation program uses
+	a diskless setup for your workstation, you will already
+	have prepared an NFS directory for use as a remote
+	root filesystem (see the `install' document for details).
+	The easiest way is to put the NetBSD filesets in this
+	root filesystem on the server where the install program
+	will find them.
+
+	However, you have the option to put the filesets in
+	another directory or even on another NFS server. To do
+	so, follow these guide lines:
+
+	Place the NetBSD software you wish to install into
+	a directory on an NFS server, and make that directory
+	mountable by the machine which you will be installing
+	NetBSD on.  This will probably require modifying the
+	/etc/exports file of the NFS server and resetting
+	mountd, acts which will require superuser privileges.
+	Note the numeric IP address of the NFS server and of
+	the router closest to the the new NetBSD machine,
+	if the NFS server is not on a network which is
+	directly attached to the NetBSD machine.
+
+	Once you have done this, you can proceed to the next
+	step in the installation process, preparing your
+	system for NetBSD installation.
+
+To prepare for installing via FTP:
+
+	NOTE: this method of installation is recommended
+	      only for those already familiar with using
+	      the BSD network-manipulation commands and
+	      interfaces.  If you aren't, this documentation
+	      should help, but is not intended to be
+	      all-encompassing.
+
+	The preparations for this method of installation
+	are easy: all you have to do is make sure that
+	there's some FTP site from which you can retrieve
+	the NetBSD installation when it's time to do
+	the install.  You should know the numeric IP
+	address of that site, the numeric IP address of
+	your nearest router if one is necessary
+
+	Once you have done this, you can proceed to the next
+	step in the installation process, preparing your
+	system for NetBSD installation.
+
+To prepare for installing via a tape:
+
+	To install NetBSD from a tape, you need to somehow
+	get the NetBSD filesets you wish to install on
+	your system on to the appropriate kind of tape,
+	in tar format.
+
+	If you're making the tape on a UN*X system, the easiest
+	way to do so is:
+
+		tar cvf <tape_device> <files>
+
+	where "<tape_device>" is the name of the tape device
+	that describes the tape drive you're using (possibly
+	something like /dev/nrst0, but we make no guarantees 8-).
+	Under SunOS 5.x, this would be something like /dev/rmt/0mbn.
+	Again, your mileage may vary.  If you can't figure it out,
+	ask your system administrator.  "<files>" are the names
+	of the "set_name.nnn" files which you want to be placed
+	on the tape.
+
+	Once you have done this, you can proceed to the next
+	step in the installation process, preparing your 
+	system for NetBSD installation.