summaryrefslogtreecommitdiff
path: root/distrib/notes/sparc64
diff options
context:
space:
mode:
authorMiod Vallat <miod@cvs.openbsd.org>2001-10-01 23:31:10 +0000
committerMiod Vallat <miod@cvs.openbsd.org>2001-10-01 23:31:10 +0000
commit22c1454340d51f204870c35335e5bd2e61c9b655 (patch)
treeaf3f33600657fe1cae7a58b67bb18245318221f4 /distrib/notes/sparc64
parent2c6cacdb1d363b7b8051271730474d03f195b9a3 (diff)
- update supported hardware list
- remove more sparc'isms. The more you remove, the more there are... - describe more fun installation methods - fix a random typo
Diffstat (limited to 'distrib/notes/sparc64')
-rw-r--r--distrib/notes/sparc64/contents2
-rw-r--r--distrib/notes/sparc64/install20
-rw-r--r--distrib/notes/sparc64/prep1
-rw-r--r--distrib/notes/sparc64/upgrade2
-rw-r--r--distrib/notes/sparc64/xfer41
5 files changed, 49 insertions, 17 deletions
diff --git a/distrib/notes/sparc64/contents b/distrib/notes/sparc64/contents
index 507d83eb8c6..c0cad41aa98 100644
--- a/distrib/notes/sparc64/contents
+++ b/distrib/notes/sparc64/contents
@@ -30,8 +30,6 @@ maintenance and disaster recovery.
The kernel and boot images are provided for net booting installations.
-Bootable installation images:
-
DistributionDescription(six)
OpenBSDbase(24.3M,74.9M,shared)
diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install
index 75da6c24157..ac435ecdaa9 100644
--- a/distrib/notes/sparc64/install
+++ b/distrib/notes/sparc64/install
@@ -33,9 +33,7 @@ insurance if you want to be able to "go back" for some reason.
After taking care of all that, bring your system down gracefully using
the shutdown(8) and/or halt(8) commands. This will get you to the monitor
-prompt. Sun PROM monitor commands and setup differ considerably depending
-on the system architecture and age, you may needed to reference the PROM
-monitor manual for your system for details.
+prompt.
dnl XXX no floppy available yet
dnl Booting from Floppy Disk installation media:
@@ -139,12 +137,16 @@ dnl MACHINE models.
you should choose the terminal type from amongst those listed.
(If your terminal type is xterm, just use vt100).
- After entering the terminal type you will be greeted by a
- welcome message and asked if you really want to continue.
- Assuming you answered yes, the install program will then tell
- you which disks of that type it can install on, and ask you
- which it should use. The name of the disk is typically "sd0".
- Reply with the name of your disk.
+ After entering the terminal type you will be asked whether you
+ wish to do an "(I)nstall" or an "(U)pgrade". Enter 'I' for a
+ fresh install or 'U' to upgrade an existing installation.
+
+ You will be presented with a welcome message and asked if
+ you really want to continue. Assuming you answered yes, the
+ install program will then tell you which disks of that type
+ it can install on, and ask you which it should use. The name
+ of the disk is typically "sd0" for SCSI drives and "wd0" for
+ IDE drives. Reply with the name of your disk.
Next you will have to edit or create a disklabel for the disk
OpenBSD is being installed on. The installation script will
diff --git a/distrib/notes/sparc64/prep b/distrib/notes/sparc64/prep
index 986a552a412..9aa07219d60 100644
--- a/distrib/notes/sparc64/prep
+++ b/distrib/notes/sparc64/prep
@@ -1,4 +1,3 @@
-
Your OpenBOOT ROM may need some setup. You cannot use the security modes
of the OpenBOOT ROM. Make sure that the ROM security modes are disabled:
diff --git a/distrib/notes/sparc64/upgrade b/distrib/notes/sparc64/upgrade
index 906a3abbc56..f4509409b34 100644
--- a/distrib/notes/sparc64/upgrade
+++ b/distrib/notes/sparc64/upgrade
@@ -1,7 +1,7 @@
Since OpenBSD OSREV is the first release for MACHINE systems, upgrades
are not expected.
If you have been using an old OpenBSD/MACHINE snapshot, you can follow the
-follwing instructions.
+following instructions.
dnl XXX replace when floppy disk available
dnl OpenBSDUpgrade({:- or the installation floppy-:})
diff --git a/distrib/notes/sparc64/xfer b/distrib/notes/sparc64/xfer
index d008a6ae19c..a9311d1a8af 100644
--- a/distrib/notes/sparc64/xfer
+++ b/distrib/notes/sparc64/xfer
@@ -1,14 +1,12 @@
Installation is supported from several media types, including:
FFS partitions
+ Tape
Remote NFS partition
CD-ROM
FTP
HTTP
-Not all methods are supported on all Sparc Systems and some of them
-work only with the floppy or the miniroot installation.
-
dnl XXX uncomment when cd-rom distribution available
dnl If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you
dnl may be able boot from it. If you can boot from the CD-ROM,
@@ -33,7 +31,7 @@ widely in terms of what peripherals and what sort of network arrangements
a user has, the intent is to provide some way that will be practical.
dnl
-dnl XXX no floppy available yet
+dnl XXX uncomment when floppy available
dnl Creating a bootable floppy disk using DOS/Windows:
dnl
dnl First you need to get access to the OpenBSD Bootable floppy
@@ -208,6 +206,41 @@ dnl distribution sets to a local server or disk and perform the installation
dnl from there, rather than directly on the internet.
dnl
+To install or upgrade OpenBSD using a tape, you need to do the following:
+
+ To install OpenBSD from a tape, you need to make a tape that
+ contains the distribution set files, each in "tar" format or
+ in "gzipped tar format". First you will need to transfer the
+ distribution sets to your local system, using ftp or by mounting
+ the CD-ROM containing the release. Then you need to make a tape
+ containing the files.
+
+ If you're making the tape on a UN*X-like system, the easiest way
+ to do so is make a shell script along the following lines, call it
+ "/tmp/maketape".
+
+ #! /bin/sh
+ tape=/dev/nrst0
+ mt -f ${tape} rewind
+ for file in base etc comp game man misc
+ do
+ dd if=${file}OSrev.tgz of=${tape} obs=8k conv=sync
+ done
+ tar cf ${tape} bsd
+ mt -f ${tape} offline
+ # end of script
+
+
+ And then:
+
+ cd .../OSREV/sparc
+ sh -x /tmp/maketape
+
+
+ If you're using a system other than OpenBSD or SunOS, the tape
+ name and other requirements may change.
+
+
To install OpenBSD using a remote partition, mounted via
NFS, you must do the following: