summaryrefslogtreecommitdiff
path: root/distrib/notes
diff options
context:
space:
mode:
authorTheo de Raadt <deraadt@cvs.openbsd.org>1995-11-19 13:35:17 +0000
committerTheo de Raadt <deraadt@cvs.openbsd.org>1995-11-19 13:35:17 +0000
commitc60b51d4ff7bd3ebed5f4e3479258726e5f33357 (patch)
treecb998f741e7d1b39cdaffd968196fcb0022026b1 /distrib/notes
parentf3ddfa78a84053c1ca5ed087c63e770ec9afe720 (diff)
from netbsd; will be customized to openbsd later of course...
Diffstat (limited to 'distrib/notes')
-rw-r--r--distrib/notes/donations10
-rw-r--r--distrib/notes/hp300/contents16
-rw-r--r--distrib/notes/hp300/install42
-rw-r--r--distrib/notes/sparc/install44
4 files changed, 100 insertions, 12 deletions
diff --git a/distrib/notes/donations b/distrib/notes/donations
index eb5d1b0235c..a716ee90134 100644
--- a/distrib/notes/donations
+++ b/distrib/notes/donations
@@ -1,8 +1,18 @@
+ Jason Brazile
+ Dave Burgess
+ Charles Conn
+ Canada Connect Corporation
Brian Carlstrom
+ Tom Coulter
+ Charles D. Cranor
Demon Internet, UK
+ Greg Gingerich
Michael L. Hitch
+ Scott Kaplan
+ Chris Legrow
Herb Peyerl
Mike Price
Thor Lancelot Simon
Bill Sommerfeld
+ Paul Southworth
Steve Wadlow
diff --git a/distrib/notes/hp300/contents b/distrib/notes/hp300/contents
index dab1af1295d..92aea172da6 100644
--- a/distrib/notes/hp300/contents
+++ b/distrib/notes/hp300/contents
@@ -68,12 +68,12 @@ the NetBSD 1.1 distribution tree, and are as follows:
The hp300 security distribution set is named "secr11" and can be found
in the "hp300/security" subdirectory of the NetBSD 1.1 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
-on those sites which carry the complete NetBSD distribution and that
-can legally obtain it. (Remember, because of United States law, this
-distribution set may not be exported to locations outside of the
-United States and Canada.) [ XXXK gzipped, XXXK uncompressed ]
+tree. It contains executables which are built in the "src/domestic" portion
+if the NetBSD source tree. It can only be found on those sites which carry
+the complete NetBSD distribution and that can legally obtain it. (Remember,
+because of United States law, this distribution set may not be exported to
+locations outside of the United States and Canada.)
+[ 128K gzipped, 275K uncompressed ]
The hp300 binary distribution sets are distributed as gzipped tar files.
Each hp300 binary distribution set also has its own "CKSUMS" file, just
@@ -84,6 +84,10 @@ The following are included in the `.../install' directory:
SYS_INST.gz A gzipped copy of the SYS_INST miniroot
installation program.
+ SYS_NBOOT.gz A gzipped copy of the network boot block.
+ This is useful if you are installing
+ a diskless NetBSD/hp300 system.
+
inst-11.fs.gz A gzipped copy of the miniroot filesystem.
netbsd.gz A gzipped GENERIC kernel.
diff --git a/distrib/notes/hp300/install b/distrib/notes/hp300/install
index 0c282aa9395..446ebec2b0a 100644
--- a/distrib/notes/hp300/install
+++ b/distrib/notes/hp300/install
@@ -6,7 +6,47 @@ The miniroot's install program will:
* Allow you to place disklabels on additional disks.
Note that partition sizes and offsets are expressed
- in sectors.
+ in sectors. When you fill out the disklabel, you will
+ need to specify partition types and filesystem parameters.
+ If you're unsure what the these values should be, use the
+ following:
+
+ fstype: 4.2BSD
+ fsize: 1024
+ bsize: 4096
+ cpg: 16
+
+ If the partition will be a swap partition, use the following:
+
+ fstype: swap
+ fsize: 0 (or blank)
+ bsize: 0 (or blank)
+ cpg: 0 (or blank)
+
+ You will also need to specify the number of partitions.
+ The number of partitions is determined by the `index' of
+ the last partition letter, where a == 1, b == 2, etc.
+ Therefore, if the last filled partition is partition `g',
+ there are 7 partitions. Any partitions with size of 0
+ may be removed from the list.
+
+ If the disk is the boot disk, you _must_ offset the root
+ partition (`a') one cylinder, as the hp300 boot code
+ if large enough to spill past the label area. In this case,
+ the `c' partition must be fstype `boot'.
+
+ Anything after a `#' is a comment.
+
+ The following is an example disklabel partition map:
+
+7 partitions:
+# size offset fstype [fsize bsize cpg]
+ a: 30912 448 4.2BSD 1024 8192 16 # (Cyl. 1 - 69)
+ b: 130816 31360 swap # (Cyl. 70 - 361)
+ c: 1296512 0 boot # (Cyl. 0 - 2893)
+ e: 81984 162176 4.2BSD 1024 8192 16 # (Cyl. 362 - 544)
+ f: 102592 244160 4.2BSD 1024 4096 16 # (Cyl. 545 - 773)
+ g: 949760 346752 4.2BSD 1024 8192 16 # (Cyl. 774 - 2893)
* Create filesystems on target partitions.
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install
index 48297a1fd3d..eb56c18a544 100644
--- a/distrib/notes/sparc/install
+++ b/distrib/notes/sparc/install
@@ -18,6 +18,39 @@ If the server runs another operating system, you'll have to consult
documentation that came with it (on SunOS systems, add_client(8) is a
good start).
+Your Sparcstation expects to be able to download a second stage bootstrap
+program via TFTP after havinf acquired its IP address through RevARP when
+instructed to boot "over the net". It will look for a filename composed of
+the machine's IP address followed by the machine's architecture, separated
+by a period. For example, a sun4c machine which has been assigned IP
+address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'.
+Normally, this file is symbolic link to an appropriate second-stage
+boot program, which should be located in a place where the TFTP daemon
+can find it (remember, many TFTP daemons run in a chroot'ed environment).
+You can find the boot program in `/usr/mdec/boot' in the NetBSD/sparc
+distribution. Unfortunately, it is necessary to install this file
+differently for sun4 and sun4c clients: the sun4 version needs to have its
+`a.out' header stripped off (otherwise the machine will crash), while the
+sun4c version must retain it (otherwise the PROM will complain).
+
+Here's an example to illustrate this whole mess:
+
+ server# cd /<client-root-dir>/usr/mdec
+ if client is a sun4:
+ server# set SKIP=1
+ server# set KARCH=SUN4
+ else
+ server# set SKIP=0
+ server# set KARCH=SUN4C
+ server# dd if=boot of=/tftpboot/boot.sparc.netbsd.$KARCH skip=$SKIP bs=32
+ server# cd /tftpboot
+ server# ln -s boot.sparc.netbsd.$KARCH 8273900B.$KARCH
+
+Note: some versions of Openboot ROMs (sun4c) seem to require that the
+boot program size is nicely rounded. Therefore it may be necessary to
+strip(8) off the symbol table.
+
+
As noted above in the section `Preparing your System for NetBSD Installation',
you have several options when choosing a location to store the installation
filesets. However, the easiest way is to put the *.tar.gz files you want
@@ -200,13 +233,13 @@ On version 2 OpenBOOT ROMs:
ok setenv boot-device /sbus/esp/sd@0,0
-Congratulations, you have successfully installed NetBSD 1.0. When you
+Congratulations, you have successfully installed NetBSD 1.1. When you
reboot into NetBSD, you should log in as "root" at the login prompt.
There is no initial password, but if you're using the machine in a
networked environment, you should create yourself an account and
protect it and the "root" account with good passwords.
-Some of the files in the NetBSD 1.0 distribution might need to be
+Some of the files in the NetBSD 1.1 distribution might need to be
tailored for your site. In particular, the /etc/sendmail.cf file will
almost definitely need to be adjusted, and other files in /etc will
probably need to be modified. If you are unfamiliar with UN*X-like
@@ -224,7 +257,8 @@ least the following pieces:
gzip (GNU gzip) SunOS binary
gtar (GNU tar) SunOS binary
the "install.sh" script
- a "/boot" file from a SunOS sun4c machine
+ a "/boot" file from a SunOS machine that matches your machine type
+ (e.g. sun or sun4c)
a kernel, most likely "/netbsd"
All these pieces, except "/boot", are supplied in the NetBSD/sparc
@@ -274,13 +308,13 @@ The installboot man page says to do something like this:
sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a
You can now extract the provided "*.tar.gz files onto your disk. The
-provided script, "install.sh" will help you:
+provided script, "install_from_sunos.sh" will help you:
sunos# ls -FC
base.tar.gz etc.tar.gz man.tar.gz secr.tar.gz
comp.tar.gz games.tar.gz misc.tar.gz text.tar.gz
install.sh netbsd.id3_scsi
- sunos# ./install.sh
+ sunos# ./install_from_sunos.sh
[...]
This script NEEDS gzip and gtar (GNU gzip and GNU tar) on your