summaryrefslogtreecommitdiff
path: root/distrib/notes/sparc
diff options
context:
space:
mode:
Diffstat (limited to 'distrib/notes/sparc')
-rw-r--r--distrib/notes/sparc/contents2
-rw-r--r--distrib/notes/sparc/hardware30
-rw-r--r--distrib/notes/sparc/install32
-rw-r--r--distrib/notes/sparc/prep6
4 files changed, 35 insertions, 35 deletions
diff --git a/distrib/notes/sparc/contents b/distrib/notes/sparc/contents
index 3fba11ad40d..38fb730c4ec 100644
--- a/distrib/notes/sparc/contents
+++ b/distrib/notes/sparc/contents
@@ -2,7 +2,7 @@ TopPart
OpenBSDminiroot
It can be copied to the swap partition of
- an existing OpenBSD, NetBSD, Linux, SunOS,
+ an existing OpenBSD, NetBSD, Linux, SunOS,
or Solaris installation to allow installing
or upgrading to OpenBSD OSREV
diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware
index 4c1c7c44b47..dac05f56071 100644
--- a/distrib/notes/sparc/hardware
+++ b/distrib/notes/sparc/hardware
@@ -29,7 +29,7 @@ OpenBSD/MACHINE OSREV does NOT run on these machines (yet):
XDBus and multiprocessor support issues.
- sun4u (Ultrasparcs)
These machines are supported by the OpenBSD/sparc64 port.
- - clones that are significantly different from the Sun systems
+ - clones that are significantly different from the Sun systems
(e.g. K-Bus based Solbourne)
The minimal configuration requires 4M of RAM and ~60M of disk space.
@@ -40,17 +40,17 @@ around 16M of RAM, getting more RAM is more important than getting a
faster CPU.) Installation from "ramdisk" kernels requires 8M of RAM.
Supported devices {:-include-:}:
- sun4c and sun4m SBus video:
+ sun4c and sun4m SBus video:
cgsix (GX, GX+, TGX, TGX+), cgthree, and bwtwo frame buffers
sun4m on-board machine specific video:
TCX, cgfourteen (aka SX), p9100 (Tadpole 3GS, 3GX)
- sun4 video (not thoroughly tested...):
+ sun4 video (not thoroughly tested...):
P4 -- on-board bwtwo, cgfour, cgsix, cgeight
- VME -- cgtwo, cgthree, cgsix
+ VME -- cgtwo, cgthree, cgsix
- serial ports:
+ serial ports:
ttya and ttyb (can be used as console if needed),
ttyc and ttyd (Sun 4/300 only)
SBus magma serial port cards, including:
@@ -58,18 +58,18 @@ Supported devices {:-include-:}:
4+1Sp, 8+2Sp, and 2+1HS Sp.
SBus Serial Parallel Interface (SUNW,spif)
- 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),
+ 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
SBus SunSwift and Quad FastEthernet cards (hme, qfe)
SBus FastEthernet cards (qec+be)
SBus QuadEthernet cards (qec+qe)
- SCSI:
+ SCSI:
on-board "esp" SCSI controller (sun4c's, and the 4/300),
- SBus "esp" SCSI controller (including 3rd party compatibles),
+ SBus "esp" SCSI controller (including 3rd party compatibles),
Sun "SUN-3"/"si" VME SCSI controller (polled mode only, slow),
Sun "SCSI Weird"/"sw" on-board controller (4/110 only, polled)
@@ -98,7 +98,7 @@ Hardware the we do NOT currently support, but get many questions about:
Interrupt driven SCSI driver for Sun 4/100's and 4/200's
VME mti 16-port serial card
VME alm2 16-port serial card
- VME mcp 4-port serial card
+ VME mcp 4-port serial card
VME IPI controller
VME cgfive framebuffer
VME cgnine framebuffer
@@ -110,9 +110,9 @@ Hardware the we do NOT currently support, but get many questions about:
Tadpole onboard PCMCIA and modem
The supplied GENERIC kernel is the best attempt at a configuration that
-works on the widest range of machinery (sun4, sun4c, and sun4m).
-If you have problems with the OpenBSD OSREV kernel in this distribution,
-please visit the OpenBSD web page (http://www.openbsd.org) and the mailing
+works on the widest range of machinery (sun4, sun4c, and sun4m).
+If you have problems with the OpenBSD OSREV kernel in this distribution,
+please visit the OpenBSD web page (http://www.openbsd.org) and the mailing
lists to review the current status and check for updates and distribution
errata.
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install
index 45c18d79857..177ae470474 100644
--- a/distrib/notes/sparc/install
+++ b/distrib/notes/sparc/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.52 2002/04/17 23:32:12 miod Exp $
+dnl $OpenBSD: install,v 1.53 2002/06/09 05:53:54 todd Exp $
OpenBSDInstallPrelude
There are several ways to install OpenBSD onto a disk. The easiest way
@@ -46,13 +46,13 @@ There are four main cases:
OpenBoot Version 2 (newer servers, desktop workstations):
prompt is "ok", boot command is "boot" uses diskn:p syntax.
OpenBoot Version 2 (certain newer desktop workstations):
- prompt is "ok", boot command is "boot" uses diskn syntax
+ prompt is "ok", boot command is "boot" uses diskn syntax
unless booting from a non-standard partition, in which case:
- boot /sbus/esp/sd@t,0:p bsd (where "t" is the scsi target,
+ boot /sbus/esp/sd@t,0:p bsd (where "t" is the scsi target,
and "p" is the partition. examples would be t="3" and p="b")
-If you expect your workstation to have an OpenBoot Prom but get a ">",
+If you expect your workstation to have an OpenBoot Prom but get a ">",
enter then "n" command to enter the "new command mode". You can set this
as the default by doing a "setenv sunmon-compat? false" command, followed
by a "reset" command.
@@ -62,9 +62,9 @@ is described elsewhere in some detail. For the purposes of this section,
drive 0 refers to the internal or first SCSI drive, which usually has a
SCSI-ID of 3.
-
+
Booting from Floppy Disk installation media:
-
+
ok boot fd()bsd # for version 1 OpenBOOT ROMs
ok boot floppy bsd # for version 2 OpenBOOT ROMs
@@ -97,18 +97,18 @@ Boot the miniroot by typing the appropriate command at the PROM:
> b sd(,,1)bsd # for sun4 monitors*
ok boot sd(,,1)bsd # for version 1 OpenBOOT ROMs
ok boot disk:b bsd # for version 2 OpenBOOT ROMs
- ok boot /sbus/esp/sd@3,0:b bsd # for version 2 OpenBOOT ROMs
+ ok boot /sbus/esp/sd@3,0:b bsd # for version 2 OpenBOOT ROMs
# that won't take disk:p syntax.
If you've loaded the miniroot onto some other disk than the default
drive 0, modify the boot specifier accordingly, keeping in mind the
-drive vs. scsi-id shuffling and partition a=0, b=1...
+drive vs. scsi-id shuffling and partition a=0, b=1...
> b sd(0,10,1)bsd # example - scsi target 2 on sun4 monitors*
ok boot sd(0,3,1)bsd # example - scsi target 0 on v1 OpenBOOT ROM
ok boot disk3:b bsd # example - scsi target 0 on v2 OpenBOOT ROM
- ok boot /sbus/esp/sd@0,0:b bsd # example - scsi target 0 on v2
- # OpenBOOT ROM that won't take
+ ok boot /sbus/esp/sd@0,0:b bsd # example - scsi target 0 on v2
+ # OpenBOOT ROM that won't take
# disk:p syntax.
(*) for sun4 this is scsi-target*8+scsi-lun (usually 0) expressed in hex...
@@ -213,7 +213,7 @@ OpenBSDCommonURL
After completing an installation:
Now try a reboot. (If needed, swap your scsi id's first).
-The Sun monitor normally tries to load a file called "vmunix".
+The Sun monitor normally tries to load a file called "vmunix".
On OpenBOOT ROM systems you can change it to load OpenBSD instead using
the following commands:
@@ -226,7 +226,7 @@ On version 2 OpenBOOT ROMs:
ok setenv boot-file bsd
ok setenv boot-device /sbus/esp/sd@0,0
-On sun4 systems, you may not need to specify the boot file, as
+On sun4 systems, you may not need to specify the boot file, as
the OpenBSD boot blocks will look for "bsd" on the boot device by default.
OpenBSDCongratulations
@@ -236,10 +236,10 @@ need to edit /etc/ttys and change the terminal type, and getty method from
"sun" and "suncons" to "vt100" and "std.9600" or something similar. Also
when running from a serial console, you may wish to adjust the eeprom
settings for input-device, output-device, screen-#columns, and screen-#rows
-as appropriate.
+as appropriate.
In order to use 'tip' on OpenBSD/MACHINE, you'll need to edit /etc/ttys
-and add "local" to the end of the tty configuration line, and run
+and add "local" to the end of the tty configuration line, and run
'ttyflags -a' to put your changes into effect.
@@ -278,7 +278,7 @@ Use SunOS to newfs the partitions which will have filesystems on them.
sunos# newfs /dev/rsd0a
[... lots of output]
-
+
Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f,
/dev/rsd0g, /dev/rsd0h).
@@ -370,7 +370,7 @@ Use Solaris to newfs the partitions which will have filesystems on them.
solaris# newfs /dev/rdsk/c0t1d0s0
[... lots of output]
-
+
Repeat for any other partition (in this example, /dev/rdsk/c0t1d0s3,
/dev/rdsk/c0t1d0s4, /dev/rdsk/c0t1d0s5 and /dev/rdsk/c0t1d0s6).
diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep
index fe41b30366d..059f7b4061d 100644
--- a/distrib/notes/sparc/prep
+++ b/distrib/notes/sparc/prep
@@ -55,8 +55,8 @@ instead of `ok', type:
ok
This is needed because OpenBSD relies on the behaviour of the "new" command
-mode. OpenBSD will not boot correctly on sun4c or sun4m systems that
-are not running in "new" command mode. The sun4 systems such as the 4/110,
+mode. OpenBSD will not boot correctly on sun4c or sun4m systems that
+are not running in "new" command mode. The sun4 systems such as the 4/110,
4/200, and 4/300 system do not have a "new" command mode, and will work
fine as-is.
@@ -86,7 +86,7 @@ both OpenBSD and SunOS environments on the same system.
You should avoid using soft updates (option softdep in /etc/fstab)
on your shared filesystems.
- Although untested, it is likely that SunOS would be confused by a
+ Although untested, it is likely that SunOS would be confused by a
filesystem with soft update flags enabled.
The OpenBSD "Sun Compatible" disklabel have been extended to support 16