summaryrefslogtreecommitdiff
path: root/distrib/notes/alpha
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2004-03-17 09:25:11 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2004-03-17 09:25:11 +0000
commit992866d50243e49ac5d348aefb9e13c04303aee0 (patch)
tree7735cd7f8507b6d965eb5f71961b757cf18ece13 /distrib/notes/alpha
parent7846de0caa516d0a12a6dcd92f07eb2a31f023e1 (diff)
grammar, consistency fixes, and typos;
ok miod@
Diffstat (limited to 'distrib/notes/alpha')
-rw-r--r--distrib/notes/alpha/contents4
-rw-r--r--distrib/notes/alpha/hardware28
-rw-r--r--distrib/notes/alpha/install6
-rw-r--r--distrib/notes/alpha/prep16
-rw-r--r--distrib/notes/alpha/xfer4
5 files changed, 29 insertions, 29 deletions
diff --git a/distrib/notes/alpha/contents b/distrib/notes/alpha/contents
index 5913cb5a083..8a6dadc92c8 100644
--- a/distrib/notes/alpha/contents
+++ b/distrib/notes/alpha/contents
@@ -1,4 +1,4 @@
-dnl $OpenBSD: contents,v 1.31 2003/09/09 22:29:02 miod Exp $
+dnl $OpenBSD: contents,v 1.32 2004/03/17 09:25:09 jmc Exp $
TopPart
OpenBSDfloppy
@@ -11,7 +11,7 @@ dnl - AlphaStation 500, 600
- AXPpci33 based machines, including
``Noname'', UDB, Multia
- EB164 based machines, including
- PC164, 164SX and 164LX
+ PC164, 164SX, and 164LX
- Personal Workstation (Miata)
floppyB{:--:}OSrev.fs Another MACHINE boot and installation floppy;
diff --git a/distrib/notes/alpha/hardware b/distrib/notes/alpha/hardware
index 1821ff01d43..50d3fbcd944 100644
--- a/distrib/notes/alpha/hardware
+++ b/distrib/notes/alpha/hardware
@@ -1,4 +1,4 @@
-dnl $OpenBSD: hardware,v 1.39 2004/03/16 08:24:59 jmc Exp $
+dnl $OpenBSD: hardware,v 1.40 2004/03/17 09:25:09 jmc Exp $
OpenBSD/MACHINE OSREV is expected to run on the following hardware.
If you have hardware that is listed here and are unable to run
OpenBSD, or if you are able to run OpenBSD on hardware not listed
@@ -10,7 +10,7 @@ Supported hardware:
chipset (only one processor on the DS20 will be used)
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21143 ethernet.
+ Built-in DEC21143 Ethernet.
Built-in ISP SCSI.
Built-in IDE controller.
Built-in USB should work, but has not been thoroughly
@@ -24,7 +24,7 @@ Supported hardware:
API UP1000 machines and other EV6 machines using the Irongate chipset
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21040 ethernet.
+ Built-in DEC21040 Ethernet.
Built-in IDE controller works, though there may be stability
issues.
Unsupported devices:
@@ -38,7 +38,7 @@ Supported hardware:
trying to install OpenBSD on them.
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21043 ethernet.
+ Built-in DEC21043 Ethernet.
Built-in ISP SCSI, when present (i.e. on ``au'' models).
Built-in IDE controller.
Most PCI devices (see below).
@@ -67,7 +67,7 @@ Supported hardware:
AlphaServer 800, 1000 and 1000A
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21040 ethernet.
+ Built-in DEC21040 Ethernet.
Built-in ISP SCSI.
PCI graphics card (TGA or VGA compatible).
Most PCI devices (see below).
@@ -81,7 +81,7 @@ dnl uncomment when support is back on track
dnl AlphaStation 500 and 600
dnl Supported devices:
dnl Built-in serial and parallel ports.
-dnl Built-in DEC21040 ethernet.
+dnl Built-in DEC21040 Ethernet.
dnl Built-in ISP SCSI.
dnl PCI graphics card (TGA or VGA compatible).
dnl Most PCI devices (see below).
@@ -94,7 +94,7 @@ dnl
AlphaStation 200, 250, 255 and 400
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21040 ethernet.
+ Built-in DEC21040 Ethernet.
Built-in ISP SCSI.
PCI graphics card (TGA or VGA compatible).
Most PCI devices (see below).
@@ -107,9 +107,9 @@ dnl
AXPpci based machines (including ``Noname'', UDB, Multia)
Supported devices:
Built-in serial and parallel ports.
- Built-in DEC21040 ethernet.
+ Built-in DEC21040 Ethernet.
Built-in 53C810 SCSI (siop).
- Built-in IDE controller. (though, will not boot from ide)
+ Built-in IDE controller. (will not boot from IDE, though)
PCI graphics card (TGA or VGA compatible).
Most PCI devices (see below).
Some ISA devices (see below).
@@ -120,9 +120,9 @@ dnl
DEC 3000 models 300{,L,X,LX}
Supported devices:
Built-in serial ports.
- Built-in LANCE ethernet.
+ Built-in LANCE Ethernet.
Built-in SCSI (53C94).
- TURBOchannel LANCE ethernet cards (PMAD-A).
+ TURBOchannel LANCE Ethernet cards (PMAD-A).
TURBOchannel SCSI (53C94) (PMAZ-A).
TURBOchannel DEFTA FDDI cards (PMAF-FA).
Unsupported devices:
@@ -133,9 +133,9 @@ dnl
DEC 3000 models 400,500,500X,600,700,800,900
Supported devices:
Built-in serial ports.
- Built-in LANCE ethernet.
+ Built-in LANCE Ethernet.
Built-in SCSI (53C94 or 53CF94-2).
- TURBOchannel LANCE ethernet cards (PMAD-A).
+ TURBOchannel LANCE Ethernet cards (PMAD-A).
TURBOchannel SCSI (53C94) (PMAZ-A).
TURBOchannel DEFTA FDDI cards (PMAF-FA).
Unsupported devices:
@@ -156,7 +156,7 @@ dnl be disguised AlphaStation machines
DEC 4000, 7000, and 10000 systems (FutureBus+ and XMIBus based)
EB64+ based systems
Samsung 164BX/UX (no SRM)
- Multiprocessor alpha systems
+ Multiprocessor Alpha systems
VME Alpha systems
Supported Peripherals:
diff --git a/distrib/notes/alpha/install b/distrib/notes/alpha/install
index a6e0a6da17d..858c9f0e0f5 100644
--- a/distrib/notes/alpha/install
+++ b/distrib/notes/alpha/install
@@ -1,4 +1,4 @@
-dnl $OpenBSD: install,v 1.23 2004/03/16 08:24:59 jmc Exp $
+dnl $OpenBSD: install,v 1.24 2004/03/17 09:25:09 jmc Exp $
OpenBSDInstallPrelude
dnl XXX document mopbooting from the SRM console.
@@ -31,7 +31,7 @@ Booting from CD-ROM installation media:
with DKA for a SCSI CD-ROM drive). If your drive shows up with
a drive number with trailing zeros, you will want to ignore them
(unless it is DKA0). For example, if your CD-ROM drive is listed
- as DKA600, you want to use dka6 (device ID's are case
+ as DKA600, you want to use dka6 (device IDs are case
insensitive).
On all MACHINE computers but the TURBOchannel DEC 3000 series,
@@ -65,7 +65,7 @@ OpenBSDBootMsgs
installing from a non-serial console, the default of "vt220"
is correct. If you are installing from a serial console
you should choose the terminal type from amongst those listed.
- (If your terminal type is xterm, just use vt220).
+ (If your terminal type is xterm, just use vt220.)
OpenBSDInstallPart3({:- or "wd0" for IDE drives-:})
diff --git a/distrib/notes/alpha/prep b/distrib/notes/alpha/prep
index 4f26b61ebb7..0409123befd 100644
--- a/distrib/notes/alpha/prep
+++ b/distrib/notes/alpha/prep
@@ -1,4 +1,4 @@
-dnl $OpenBSD: prep,v 1.20 2003/09/06 22:22:42 miod Exp $
+dnl $OpenBSD: prep,v 1.21 2004/03/17 09:25:09 jmc Exp $
OpenBSD/MACHINE requires the SRM console. Some alphas come with
the AlphaBIOS (also known as the ARC firmware on older machines) instead;
this is what Windows NT uses. It is fairly simple to replace the AlphaBIOS
@@ -6,7 +6,7 @@ with the SRM firmware.
Switching your MACHINE to SRM console:
Recent machines (such as the Miata and later models) have enough flash
- rom space to carry both the AlphaBIOS and the SRM console.
+ ROM space to carry both the AlphaBIOS and the SRM console.
To switch to SRM from AlphaBIOS, do the following:
- enter the AlphaBIOS setup upon startup
(F2 key, or ^B from serial console)
@@ -21,7 +21,7 @@ Switching your MACHINE to SRM console:
flash, and you will have to upgrade your firmware.
You can get replacement firmware either from a firmware update CD-ROM
- or via ftp from
+ or via FTP from
ftp://ftp.digital.com/pub/DEC/Alpha/firmware/
Please refer to
http://ftp.digital.com/pub/DEC/Alpha/firmware/readme.html
@@ -42,13 +42,13 @@ Using the SRM console:
information to boot OpenBSD/MACHINE.
To see a list of devices connected to your alpha, you can
- use the "show device" command. For booting the devices you
+ use the "show device" command. For booting, the devices you
are interested in are "dva0" (the floppy drive) and
"dka*" (the disk drives).
You can set ROM variables by saying "set VARIABLE VALUE".
Some variables you will want to set:
- auto_action Determines what happens when you turn power on,
+ auto_action Determines what happens when you turn the power on,
halt, or crash your machine. Valid values
{:-include-:} "halt", "boot", and "restart".
Most users will want to set this to "boot".
@@ -61,7 +61,7 @@ Using the SRM console:
boot_osflags Flags to pass to the kernel.
IMPORTANT! For multiuser boot, this needs to be
set to "a".
- To see a list of all variables on your machine use the "show"
+ To see a list of all variables on your machine, use the "show"
command with no arguments.
You can bypass the boot_file and boot_osflags values from the command
@@ -79,7 +79,7 @@ SRM console boot device restrictions:
The built-in disk controllers on your MACHINE will always be supported,
however on IDE-based machines, such as the EB164, 164SX and 164LX, as
well as the low-end Personal Workstation (non-u models), you can plug
- an SCSI controller, and boot from it if it is recognized.
+ in a SCSI controller, and boot from it if it is recognized.
Recent SRM releases for these machines will be able to boot from the
following controllers:
@@ -128,4 +128,4 @@ OpenBSD/MACHINE console device restrictions:
use display && keyboard console'', then you need to use a serial
console.
If your machine was not listed in the list above, please report this
- on <alpha@OpenBSD.org>.
+ to <alpha@OpenBSD.org>.
diff --git a/distrib/notes/alpha/xfer b/distrib/notes/alpha/xfer
index 54e087a3eeb..92f1b8726f5 100644
--- a/distrib/notes/alpha/xfer
+++ b/distrib/notes/alpha/xfer
@@ -1,4 +1,4 @@
-dnl $OpenBSD: xfer,v 1.25 2003/03/24 11:33:56 miod Exp $
+dnl $OpenBSD: xfer,v 1.26 2004/03/17 09:25:09 jmc Exp $
Installation is supported from several media types, including:
CD-ROM (NOT supported if booting from floppy)
@@ -35,7 +35,7 @@ If you neither have a floppy drive nor a CD-ROM drive on your alpha:
disk which will confuse the install script. To fix this
you need to ask for a shell (answer "s" to the first question)
when booting your disk and do "dd if=/dev/zero of=/dev/rsd0c
- count=20" assuming your booted from sd0. After doing this you will
+ count=20", assuming you booted from sd0. After doing this you will
not be able to boot that disk again unless you complete
the install. You can now enter "install" and start the
actual install process.