diff options
40 files changed, 138 insertions, 139 deletions
diff --git a/distrib/notes/amiga/install b/distrib/notes/amiga/install index 464c158c99e..0c4063776d2 100644 --- a/distrib/notes/amiga/install +++ b/distrib/notes/amiga/install @@ -270,7 +270,7 @@ begin again from scratch. You will also have to identify the type of file system residing in the partition identified. Currently you can install from partitions that has been formatted as - Berkely fast file system (ffs) or AmigaDOS FFS (ados). + Berkeley fast file system (ffs) or AmigaDOS FFS (ados). You will also have to provide the relative path to the directory on the file system where the distribution sets diff --git a/distrib/notes/amiga/prep b/distrib/notes/amiga/prep index e6b44638a6d..7018961d264 100644 --- a/distrib/notes/amiga/prep +++ b/distrib/notes/amiga/prep @@ -105,7 +105,7 @@ Choosing installation root filesystem type: Transferring the miniroot filesystem: The OpenBSD/amiga installation or upgrade can use a "miniroot" - fileystem which is installed on the partition used by OpenBSD + filesystem which is installed on the partition used by OpenBSD for swapping. Once the hard disk has been prepared for OpenBSD, the miniroot @@ -131,7 +131,7 @@ Transferring the miniroot filesystem: To transfer the miniroot using an older BSD, you should be booted up in single user state on the current system, or use the - "shutdown now" command to shutdown to single-uyser state. Then + "shutdown now" command to shutdown to single-user state. Then copy the miniroot using dd: dd if=miniroot22.fs of=/dev/rsdXb where /dev/rsdXb should be the device path of the swap partition diff --git a/distrib/notes/amiga/upgrade b/distrib/notes/amiga/upgrade index a9cd7215144..2cc92f4efe7 100644 --- a/distrib/notes/amiga/upgrade +++ b/distrib/notes/amiga/upgrade @@ -6,7 +6,7 @@ allowed them to do so. To do the upgrade, and if you are using the miniroot installation, you must have the OpenBSD kernel on AmigaDOS and you must transfer the root filesystem miniroot22.fs onto the swap partition of the OpenBSD hard disk. -If you are using the ramdsik installation, the bsd.rd kernel is enough. +If you are using the ramdisk installation, the bsd.rd kernel is enough. You must also have at least the "base22" binary distribution set available, so that you can upgrade with it, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install diff --git a/distrib/notes/atari/contents b/distrib/notes/atari/contents index 3c6790b6169..e26179314ee 100644 --- a/distrib/notes/atari/contents +++ b/distrib/notes/atari/contents @@ -27,7 +27,7 @@ Bootable Kernel floppy: This TOS disk contains the loadbsd and chg_part programs and the GENERIC kernel. It is setup so that you can insert it - int your floppy drive, and start the programs from GEM. + into your floppy drive, and start the programs from GEM. This floppy is named boot-22.fs diff --git a/distrib/notes/atari/hardware b/distrib/notes/atari/hardware index 86c5d6968df..0d9209cac90 100644 --- a/distrib/notes/atari/hardware +++ b/distrib/notes/atari/hardware @@ -16,7 +16,7 @@ large and bulky to accommodate all people, BOOT is small and might not have all the features you want). Supported devices include: - - The buildin SCSI host adapter + - The built-in SCSI host adapter - Should support most SCSI-drives. The drives that are currently tested are: MAXTOR 7245S, MAXTOR 7080S, SEAGATE ST157N diff --git a/distrib/notes/atari/install b/distrib/notes/atari/install index eb1c8089e65..3112ecb1a52 100644 --- a/distrib/notes/atari/install +++ b/distrib/notes/atari/install @@ -30,8 +30,8 @@ begin again from scratch. kernel to load the install filesystem into RAMdisk. While While the kernel is loading, it will show a '.' for each track loaded. After loading 80 tracks, it will ask you - to insert the next floppy. At this time, inser the BSD - install floppy 2 and hit any key. The kernel continous + to insert the next floppy. At this time, insert the BSD + install floppy 2 and hit any key. The kernel continuous loading another 40 tracks before it continues to boot. The system should continue to boot. For now ignore WARNING: @@ -128,7 +128,7 @@ begin again from scratch. Extract game20 If the distribution sets are in different directories, - you will need to cd to each directory in turn, runing + you will need to cd to each directory in turn, running "Set_tmp_dir" and the appropriate "Extract" command(s). Continue this process until you've finished installing @@ -225,7 +225,7 @@ boot OpenBSD this time with the command: loadbsd bsd -You need to do your final tweeks now. First mount your file systems +You need to do your final tweaks now. First mount your file systems like so: mount -av @@ -251,7 +251,7 @@ you could do the following: into this partition. Also, edit your /etc/fstab to always mount this partition, say as /kernels. Now make a symlink from /bsd to /kernels/bsd. - This sceme is particulary handy when you want to make your + This scheme is particularly handy when you want to make your own kernel. When compilation is finished, you just copy your kernel to /kernels/bsd and reboot. It's wise to make sure there is _always_ a 'know to work' kernel image diff --git a/distrib/notes/atari/prep b/distrib/notes/atari/prep index 2aa186071ad..80705768931 100644 --- a/distrib/notes/atari/prep +++ b/distrib/notes/atari/prep @@ -19,14 +19,14 @@ OpenBSD/atari system. How this should be done is described in "upgrading to OpenBSD-labeling". Using AHDI partitioning: - The paritioning can be done with the AHDI-disk that is - provided with your TT or Falcon. Note that the AHDI partioning - function erases all partions on your harddisk even if they are + The partitioning can be done with the AHDI-disk that is + provided with your TT or Falcon. Note that the AHDI partitioning + function erases all partitions on your hard disk even if they are not changed! I know this is rather stupid, but don't say I didn't warn you. - You will need the 'chg_part' program from the bootdisk to - prepare your harddisk a bit more. This program will change the + You will need the 'chg_part' program from the boot disk to + prepare your hard disk a bit more. This program will change the partition-id so OpenBSD knows which partitions it can use. The synopsis is: chg_part <driveno> <partno> <new_id> @@ -49,12 +49,12 @@ Using AHDI partitioning: Upgrading to OpenBSD-labeling: First of all the new disk label functions are fully backwards - compatible with the current (old) behaviour, therefore you don't + compatible with the current (old) behavior, therefore you don't have to rename partition identifiers if you don't want to. The only limitation is that you won't be able to write a disklabel to your harddisk ("Device not configured."). - If you'ld like to have the flexibility of the OpenBSD disk label, + If you'd like to have the flexibility of the OpenBSD disk label, the procedure is very simple: change the identifier of the AHDI partition that contains your OpenBSD root filesystem from NBR to NBD. Boot OpenBSD; run `disklabel -e sd?'; disklabel will start vi; @@ -91,7 +91,7 @@ Upgrading to OpenBSD-labeling: So what do you do if you have a new disk, that will be exclusively used by OpenBSD? Very simple: don't let it get `infected' by the AHDI `virus'. ,-) Just connect the disk to your TT/Falcon; boot - OpenBSD; run `disklabel -e'; you'll see only one large partiton `d' - (there won't be any filesytem on it yet); you can create partitions + OpenBSD; run `disklabel -e'; you'll see only one large partition `d' + (there won't be any filesystem on it yet); you can create partitions in any way you want, as you're no longer limited by an AHDI partition table. diff --git a/distrib/notes/atari/xfer b/distrib/notes/atari/xfer index d1d9b8b16f6..4d386a35459 100644 --- a/distrib/notes/atari/xfer +++ b/distrib/notes/atari/xfer @@ -14,12 +14,12 @@ the disk. To write onto fd0 use: dd if=inst-10.fs.1 of=/dev/rfd0b bs=9b -If you are using TOS to make the floppies, grab the 'rawwrite' utility +If you are using TOS to make the floppies, grab the 'rawrite' utility from the "atari/utils" directory and issue the command: - rawwrite boot-10.fs + rawrite boot-10.fs This will create the boot-floppy on the floppy in drive a. The floppies -should be pre-formatted on 720Kb for both the 'dd' and 'rawwrite' commands +should be pre-formatted on 720Kb for both the 'dd' and 'rawrite' commands to work. Pre-formatting can be best done using the desktop format command. Some other utilities seem to be giving problems. diff --git a/distrib/notes/hp300/contents b/distrib/notes/hp300/contents index 552f58fad9c..f67ad6f7aa5 100644 --- a/distrib/notes/hp300/contents +++ b/distrib/notes/hp300/contents @@ -62,7 +62,7 @@ subdirectory of the OpenBSD 2.2 distribution tree, and are as follows: [ 94K gzipped, 500K uncompressed ] games22 This set includes the games and their manual pages. - [ 2.7M gzipped, 6.6M uncompressed ] + [ 2.7M gzipped, 6.7M uncompressed ] man22 This set includes all of the manual pages for the binaries and other software contained in the base set. diff --git a/distrib/notes/hp300/install b/distrib/notes/hp300/install index ecd545968d9..023455b8f77 100644 --- a/distrib/notes/hp300/install +++ b/distrib/notes/hp300/install @@ -56,7 +56,7 @@ process again from scratch. type it can install on, and ask you which it should use. The name of the disk is typically "hd0" for HPIB/CS80 drives or "sd0" for SCSI drives. If you do not wish to install on the - first disk, you should use the appropiate number in place of "0". + first disk, you should use the appropriate number in place of "0". Reply with the name of your disk. Next you will have to edit or create a disklabel for the disk diff --git a/distrib/notes/hp300/prep b/distrib/notes/hp300/prep index ddbd0bc580b..f0798fbe6e8 100644 --- a/distrib/notes/hp300/prep +++ b/distrib/notes/hp300/prep @@ -1,12 +1,12 @@ The ramdisk kernel may be loaded from the network, from CD-ROM, or other SCSI devices (such as Zip(tm) disk). This section primarily describes the -setup required for a network boot, but does offer information pretaining to +setup required for a network boot, but does offer information pertaining to installation from other media. Note that loading from HPIB or SCSI cartridge tape is possible, but not currently supported. You will need information about your disk's geometry, based on 512-byte sectors. You must have this information before proceeding. The -file `HP-IB.geometry' has geometry inforomation for several HP-IB disks, +file `HP-IB.geometry' has geometry information for several HP-IB disks, but may be incomplete. Geometry may be calculated from an HP-UX `/etc/disktab' entry, but note that HP-UX geometry is based on 1024 byte sectors, while OpenBSD's is based on 512 byte sectors. @@ -31,7 +31,7 @@ In order to complete this process, you will need the following from the SYS_UBOOT The unified boot block file. - bsd.rd The gziped RAMDISK kernel image. + bsd.rd The gzipped RAMDISK kernel image. To boot SYS_UBOOT via the network, you will need a system capable of handling boot requests for an hp300. If you will use this method, see diff --git a/distrib/notes/i386/contents b/distrib/notes/i386/contents index 7929278c366..92bef5aaadd 100644 --- a/distrib/notes/i386/contents +++ b/distrib/notes/i386/contents @@ -25,7 +25,7 @@ As well you may be interested in .../2.2/tools/ miscellaneous i386 installation utilities like - rawwrite.exe, gzip.exe, and pfdisk.exe; see + rawrite.exe, gzip.exe, and pfdisk.exe; see installation section, below. diff --git a/distrib/notes/i386/hardware b/distrib/notes/i386/hardware index 9edf27b7e9b..ced67865797 100644 --- a/distrib/notes/i386/hardware +++ b/distrib/notes/i386/hardware @@ -246,7 +246,7 @@ soft config setting. Unfortunately, the kernel's autconfiguration process (specifically, some of the devices it probes for) cause conflicts with the SMC Elite Ultra, and very often cause it to lose it's configuration and fail it's own probe. -If thise happens, you must boot the computer into DOS, and run the EzSetup +If this happens, you must boot the computer into DOS, and run the EzSetup program available from SMC. The complete URL of which is ftp://ftp.smc.com/pub/nics/ethernet/elite_ultra/gez122.exe. This program will allow you to reconfigure and recover a card that has lost it's diff --git a/distrib/notes/i386/prep b/distrib/notes/i386/prep index c50cd158eda..73ed0dac0a3 100644 --- a/distrib/notes/i386/prep +++ b/distrib/notes/i386/prep @@ -38,7 +38,7 @@ operating system. If that operating system is already set up to use the entire disk, you will have to back it up, remove and recreate a smaller partition for it, and then restore the data from that partition. You do not have to create an OpenBSD partition at this time, the OpenBSD install- -ation will give you an oppotunity to create the partition needed for +ation will give you an opportunity to create the partition needed for OpenBSD. Finally, do whatever is necessary to restore order to the partition diff --git a/distrib/notes/i386/upgrade b/distrib/notes/i386/upgrade index 3951aa129c0..510e9e06c76 100644 --- a/distrib/notes/i386/upgrade +++ b/distrib/notes/i386/upgrade @@ -8,11 +8,11 @@ Also, OpenBSD now uses partition ID 0xA6 (166 decimal), but will continue to work with 0xA5 for compatibility reasons. However, if you change the partition ID to 0xA6, you will be able to share the disk with 386BSD, FreeBSD or NetBSD. Note that the latter three can -NOT easily share the disk with each others. +NOT easily share the disk with each other. To do the upgrade, you must have the appropriate kernel-copy floppy -image on a disk, and the upgr20.fs floppy image on another. You must -also have at least the "base20" binary distribution set available, +image on a disk, and the floppy22.fs floppy image on another. You must +also have at least the "base22" binary distribution set available, so that you can upgrade with it, using one of the upgrade methods described above. Finally, you must have sufficient disk space available to install the new binaries. Since the old binaries are @@ -31,18 +31,17 @@ process. To upgrade your system, follow the following instructions: Boot your machine using of the appropriate kernel-copy floppy. - When presented with the boot prompt (the prompt begins with - "Boot" and ends with ":-"), hit return. + When presented with the boot prompt (the "boot>" prompt), hit return. You will be prompted to insert a file system floppy. Remove - the kernel-copy floppy and insert the upgr20 floppy, then hit + the kernel-copy floppy and insert the upgr22 floppy, then hit any key to continue booting. While booting, you will probably see several warnings. You should be warned that no swap space is present, and that init(8) cannot find /etc/rc. Do not be alarmed, these are completely normal. When you reach the prompt asking you for a - shell name, just hit return. + shell name, just hit return, then type 'upgrade'. You will be presented with some information about the upgrade process and a warning message, and will be asked if you wish @@ -96,13 +95,13 @@ To upgrade your system, follow the following instructions: After the software has been transferred to the machine (or mounted, in the case of upgrading via NFS), change into the - directory containing the "base20" distribution set. Once you + directory containing the "base22" distribution set. Once you are there, run the "Set_tmp_dir" command, and hit return at the prompt to select the default answer for the temporary directory's path name. (It should be the path name of the directory that you're in.) - Run the command "Extract base20" to upgrade the base + Run the command "Extract base22" to upgrade the base distribution. Repeat the above two steps for all of the sets you wish to @@ -121,7 +120,7 @@ To upgrade your system, follow the following instructions: up the installation, by remaking some system databases. When it is complete, you should use "halt" to halt the system. - When the system is halted, remove the "upgr20" floppy from + When the system is halted, remove the "upgr22" floppy from the floppy drive, and replace it with the OpenBSD 2.2 kernel-copy floppy that you previously booted from. Reboot with that floppy. @@ -159,7 +158,7 @@ Your system has now been upgraded to OpenBSD 2.2. There are several things that you should do, or might have to do, to insure that the system works properly. - Second, you will probably want to get the etc20 distribution, + Second, you will probably want to get the etc22 distribution, extract it, and compare its contents with those in your /etc/ directory. You will probably want to replace some of your system configuration files, or incorporate some of the changes diff --git a/distrib/notes/mac68k/contents b/distrib/notes/mac68k/contents index cd804820f98..2a3e9c129c8 100644 --- a/distrib/notes/mac68k/contents +++ b/distrib/notes/mac68k/contents @@ -81,7 +81,7 @@ and are as follows: man pages for other architectures which happen to be installed from the source tree by default as well as many other sundry system files and programs. This set - is not necessarry but will improve the functionallity + is not necessary but will improve the functionality of many system programs. [ 1.7M gzipped, 5.9M uncompressed ] @@ -104,7 +104,7 @@ this directory are as follows: Installer_1.1f.sea.hqx This is the MacOS program used to install downloaded sets (such as those from the bins directory) onto a BSD partition. It - is necessarry in either the case of a fresh install or an + is necessary in either the case of a fresh install or an upgrade. Mkfs_1.45.sea.hqx diff --git a/distrib/notes/mac68k/hardware b/distrib/notes/mac68k/hardware index 4c8f9b8596a..db70ac3e91a 100644 --- a/distrib/notes/mac68k/hardware +++ b/distrib/notes/mac68k/hardware @@ -8,7 +8,7 @@ distribution (note that this does not count swap space!). Much more disk space is required to install the source and objects as well (about another 105MB). -OpenBSD/mac68k 2.2 now runs on most 680x0 Macintoshes. Specifically, it +OpenBSD/mac68k 2.2 now runs on most 680x0 MacIntosh's. Specifically, it should work on: 68020 with 68851 PMMU and 68881 FPU 68030 with 68882 FPU (most Macs have this) @@ -52,5 +52,5 @@ What isn't supported, but often asked about: Machines based on Apple's IOP technology including the Mac IIfx. Machines based on the 68LC040 processor. Unfortunately, the chip itself contains a major bug which is presently being worked - on. However, machiens such as the Centris 605 don't work + on. However, machines such as the Centris 605 don't work right now. diff --git a/distrib/notes/mac68k/install b/distrib/notes/mac68k/install index bc401b79d52..7046593b4df 100644 --- a/distrib/notes/mac68k/install +++ b/distrib/notes/mac68k/install @@ -59,7 +59,7 @@ If you are installing onto a single root partition, proceed to the partition(s) by hand: * Select "Build Devices" from the "File" menu. This builds - the necessarry tree of device files on your filesystem in + the necessary tree of device files on your filesystem in /dev. * Select "Mini Shell" from the "File" menu. @@ -70,7 +70,7 @@ If you are installing onto a single root partition, proceed to the the first scsi disk, sd0, on /usr, you would type: mount /dev/sd0b /usr - * Type "quit" to exi the minishell after you have mounted + * Type "quit" to exit the minishell after you have mounted all the filesystems. Installation of base files: diff --git a/distrib/notes/mac68k/prep b/distrib/notes/mac68k/prep index 75eed831ba4..801a60b81f9 100644 --- a/distrib/notes/mac68k/prep +++ b/distrib/notes/mac68k/prep @@ -40,12 +40,12 @@ software on the MacOS side. In the Memory control panel, you should turn Virtual Memory off whenever you are planning to use the BSD/Mac68k Booter. You should also assure that your machine is using 32-bit addressing. If there is no "Addressing:" option in your Memory control panel and your -machien is supported, your probably will need Mode32. Mode32 is a control +machine is supported, your probably will need Mode32. Mode32 is a control panel and extension combination which enable 32-bit addressing on older Macs which do not use it by default. This program is available from any Info-Mac mirror. Finally, we recommend strongly that, at least for the purposes of -setting the system up, you run with the machine's montior in 1-bit ("Black -and White" in the mOnitors control panel) mode. +setting the system up, you run with the machine's monitor in 1-bit ("Black +and White" in the monitor's control panel) mode. All of that done and accounted for, you are now set to install OpenBSD on your hard drive. diff --git a/distrib/notes/mac68k/upgrade b/distrib/notes/mac68k/upgrade index b4bdb9f8d96..dc7b07b2a42 100644 --- a/distrib/notes/mac68k/upgrade +++ b/distrib/notes/mac68k/upgrade @@ -8,6 +8,6 @@ Instead, download it while running OpenBSD and put it in /tmp or some other harmless place and unpack it with a command like 'tar zxvf etc22.tar.gz'. You will then have an etc directory with current system configuration files in it. Use this to carefully upgrade your files in the running /etc and -reboot the system. Also, it is hihgly recommended that when upgrading your +reboot the system. Also, it is highly recommended that when upgrading your kernel binary (/bsd) you backup the old, working kernel and extract bsd22.tar.gz into / only from OpenBSD. diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install index 193b95f75e0..a77675c196d 100644 --- a/distrib/notes/mvme68k/install +++ b/distrib/notes/mvme68k/install @@ -2,7 +2,7 @@ Installing OpenBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. There are several ways to install OpenBSD onto a disk. The easiest way -nin terms of preliminary setup is to use the OpenBSD miniroot that can +in terms of preliminary setup is to use the OpenBSD miniroot that can be booted off your local disk's swap partition. Alternatively, if your Sparcstation is hooked up in a network you can find a server and arrange for a diskless setup which is a convenient way to install on a machine @@ -79,7 +79,7 @@ root directory, as well as the path of the client's root on that server. Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corresponding to the root filesystem. If successful, the boot -rogram starts reading from the remote root filesystem in search of the +program starts reading from the remote root filesystem in search of the kernel which is then read into memory. @@ -164,7 +164,7 @@ the disk. DO NOT USE `disklabel -r ...' TO INITIALIZE YOUR DISK LABEL; THIS WILL LEAD TO UNPREDICTABLE RESULTS. This deficiency will be fixed in a next release. -Here follows an example of what you'll see while in the dislabel editor. +Here follows an example of what you'll see while in the disklabel editor. Do not touch any of the parameters except for the `label: ' entry and the actual partition size information at the bottom (the lines starting with `a:', `b:', ...). diff --git a/distrib/notes/pc532/install b/distrib/notes/pc532/install index 5c1a984654d..9cf08b35145 100644 --- a/distrib/notes/pc532/install +++ b/distrib/notes/pc532/install @@ -105,7 +105,7 @@ The Install Procedure: 1030 So I ended up choosing 1030 cylinders, 1 head, 1994 sectors/track. - I "lost" only 60 sectors, but got a "resonable geometry". + I "lost" only 60 sectors, but got a "reasonable geometry". d) run "install" -- it will ask you for the disk geometry and other questions. It will ask you for the geometry and then ask you @@ -147,7 +147,7 @@ The Install Procedure: d) cdrom (If you have a CD with OpenBSD/532 ...) - e) Use the ROM compatable "download" program. The program + e) Use the ROM compatible "download" program. The program download is included in the initial installation and can be used as the receive end of the download by using it as "download -r file_to_write". If the CRC is @@ -198,7 +198,7 @@ The Install Procedure: where YOUR_BAUD_RATE is the actual value, 19200, 38400 or something slower than 9600. If you set scndefaultrate to something bogus, you'll probably - not be able to reboot... So be carefull! + not be able to reboot... So be careful! l) Reboot the machine and it should come up in multi-user mode *IF* diff --git a/distrib/notes/pc532/upgrade b/distrib/notes/pc532/upgrade index 9be75f81fdb..12ec72f6b92 100644 --- a/distrib/notes/pc532/upgrade +++ b/distrib/notes/pc532/upgrade @@ -30,7 +30,7 @@ To upgrade your system, follow the following instructions: depending on what version of OpenBSD/pc532 you are running. BE CAREFUL IF YOU ARE NOT RUNNING WITH SECURITY. The - 2.0 distribution does contain support for password encription. + 2.0 distribution does contain support for password encryption. It would be reasonable to save a copy of master.passwd and remove all passwords until after you upgrade. diff --git a/distrib/notes/pc532/xfer b/distrib/notes/pc532/xfer index 7120d3ea1df..b54266c9811 100644 --- a/distrib/notes/pc532/xfer +++ b/distrib/notes/pc532/xfer @@ -8,7 +8,7 @@ a program called download is part of this distribution. Download sends data to the ROM monitor over the serial line. You may need to find and read the documentation about the ROM monitor -download command and other low level comands. +download command and other low level commands. Other methods of getting OpenBSD/pc532 on your pc532 may include SCSI tape or SCSI floppy disk or cloning a disk on a system diff --git a/distrib/notes/pmax/hardware b/distrib/notes/pmax/hardware index fa737a7b85a..34d65d0859e 100644 --- a/distrib/notes/pmax/hardware +++ b/distrib/notes/pmax/hardware @@ -1,9 +1,9 @@ OpenBSD/pmax 2.2 runs on the following classes of machines: - Decstation 2100 and 3100, also known as "pmin" and "pmax" - - Personal Decstations (5000/20, and /25) also knonw as "MAXINE" - - Decstation 5000/120, /125, and /133, also knonw as "3MIN" - - Decstation 5000/200, also knonw as "3MAX" - - Decstation 5000/240, als knonw as "3MAXPLUS" + - Personal Decstations (5000/20, and /25) also known as "MAXINE" + - Decstation 5000/120, /125, and /133, also known as "3MIN" + - Decstation 5000/200, also known as "3MAX" + - Decstation 5000/240, also known as "3MAXPLUS" OpenBSD/pmax 2.2 does *not* (yet) run on these machines: - Decstation 5100 (an r2000-based cousin of the Decstation 3100) @@ -22,15 +22,15 @@ faster CPU. Supported devices include: Decstation 2100 and 3100 baseboard video: - pm one-bit mono or 8-bit pseudocolour fraem buffers. + pm one-bit mono or 8-bit pseudocolor frame buffers. Decstation 5000 series TurboChannel video: PMAG-DV Personal Decstation baseboard 1024x768 frame buffer. - PMAG-BA 1024x768 8-bit colour frame buffer. - PMAGB-BA 1024x768 8-bit colour frame buffer. + PMAG-BA 1024x768 8-bit color frame buffer. + PMAGB-BA 1024x768 8-bit color frame buffer. PMAG-AA 1280x1024 four-bit greyscale frame buffer. - NOTE: All supported DECstation vide produces sync-on-green. + NOTE: All supported DECstation video produces sync-on-green. Be sure to use either a DEC-compatible fixed-sync monitor or a multisync monitor that supports sync-on-green. diff --git a/distrib/notes/pmax/install b/distrib/notes/pmax/install index d7d2aa37304..9774c60e05e 100644 --- a/distrib/notes/pmax/install +++ b/distrib/notes/pmax/install @@ -4,7 +4,7 @@ this document in hand it shouldn't be too much trouble. Also i wanted to note that the installation procedure via install script is new for the pmax and i had only the chance of limited testing for it - so if you run into any problems with it or if this -documentation is somehow unclear - please send me a mail and i'll try +documentation is somehow unclear - please send me a mail and I'll try to help you or to fix the problem. There are several ways to install OpenBSD onto a disk. The easiest way @@ -17,7 +17,7 @@ setup which is another convenient way to install OpenBSD/pmax. Installing using the OpenBSD simpleroot. The simpleroot is a self-contained OpenBSD filesystem holding a complete -OpenBSD/pmax rootfilesystem plus all utilities necessary to install +OpenBSD/pmax root filesystem plus all utilities necessary to install OpenBSD on a local disk. It is distributed as a plain file designed to be transferred to a raw disk from which it can be booted using the appropriate PROM command. @@ -25,7 +25,7 @@ appropriate PROM command. Loading the simpleroot onto your raw partition is simple. You can do this on any machine you can hang on the disk which you plan to put onto the pmax which allows you to write to the raw disk - i.e. on all -UN*X like operatingsystems it should work using "dd". On OpenBSD +UN*X like operating systems it should work using "dd". On OpenBSD as well as SunOS you use a command like: # dd if=simpleroot22.fs of=/dev/rsd0c bs=20b conv=sync @@ -83,7 +83,7 @@ documentation that came with it (on SunOS systems, add_client(8) is a good start). One part of the distribution of OpenBSD/pmax is a file called -simpleroot22.tar.gz which is a good start for the rootfilesystem area on +simpleroot22.tar.gz which is a good start for the root filesystem area on the NFS server then you want to install via network. A few configuration files need to be edited: @@ -113,9 +113,9 @@ devices on the server using mv ../MAKEDEV* . ./MAKEDEV all -This may not not work correctly on some operatingsystems. +This may not not work correctly on some operating systems. -Ok here is in shortform what you have to do on the Server to prepare a +Ok here is in short form what you have to do on the Server to prepare a diskless installation of OpenBSD/pmax assuming the Server is an OpenBSD machine (for instance a PC running OpenBSD/i386). As said above for other systems you'll have to look into the supplied @@ -123,7 +123,7 @@ documentation for that systems. All the following should apply also without any major changes to an FreeBSD or NetBSD server. If the following instructions are not enough - you may look at the -manpages for the following commands: +man pages for the following commands: * tftpd * rarpd @@ -201,13 +201,13 @@ Ok - now let's see what to do to set up the server: --- snip --- prospero is the hostname of the server in this example -* start the rquired daemons on the server: +* start the required daemons on the server: /usr/sbin/rpc.bootparamd /usr/sbin/rarpd -a and bootpd - either by uncommenting the entry in /etc/inetd.conf and - sending inetd an HUP signal like above or by starting it explicitely + sending inetd an HUP signal like above or by starting it explicitly /usr/sbin/bootpd @@ -224,13 +224,13 @@ Ok - now let's see what to do to set up the server: If you plan to use OpenBSD/pmax on a diskless system in the future - keep in mind that the Decstations can only boot ecoff format kernels -via net - so you have to convert them explicitely after the kernel +via net - so you have to convert them explicitly after the kernel compilation to ecoff - therefor in the kernel compile dir you can do the following after the kernel compile has finished elf2ecoff bsd.elf bsd.ecoff -then you can use the bsd.ecoff for netbooting - as a startingpoint for +then you can use the bsd.ecoff for netbooting - as a starting point for the kernel config file you may choose GENERIC_NFS. After you have set up everything correctly you can boot your system @@ -241,12 +241,12 @@ Continuing the installation from single user mode If you have reached single user mode either via booting the simpleroot image or via booting over the network you will have to -relabel/label your disk and put filesystems on the patitions. +relabel/label your disk and put filesystems on the partitions. So here's what you have to do after going into single user mode: - simpleroot image (assuming you have the simpleroot on rz0 and want - to install on that disk too - everytinh behind the ";" is comment) + to install on that disk too - everything behind the ";" is comment) # fsck /dev/rrz0a ; check the filesystem # mount /dev/rz0a / ; mount / read write @@ -264,7 +264,7 @@ installing - please first look at I'll try to collect there any hints, fixes and so on. If your problem can't be solved that way just send me a mail to graichen@OpenBSD.org -and i'll try to help you fixing it. +and I'll try to help you fixing it. If you should somehow fail using the install script and want to restart - you may have to umount any filesystems mounted while running @@ -274,15 +274,15 @@ the install script (so all except /) and clean /tmp using: then it should be possible to rerun it again. -Now some more notes about labeling the disk - which you will hjave to +Now some more notes about labeling the disk - which you will have to do in the process of running the install script. -Here follows an example of what you'll see while in the dislabel editor. +Here follows an example of what you'll see while in the disklabel editor. Do not touch any of the parameters except for the `label: ' entry and the actual partition size information at the bottom (the lines starting with `a:', `b:', ...). -If you are using the simpleroot image and wan't to install onto the +If you are using the simpleroot image and want to install onto the same disk you put the simpleroot on you'll also have to change the sector, track, cylinder, etc. entries to match the values for your disk. The Problem is to get those values for your disk :-) - you can @@ -381,10 +381,10 @@ Note: if you have finished the disklabeling and exited the editor for editing the label in the process of the installation and if you then get a message like: "no disklabel on disk - use the -r option to write one" you should ignore it and answer no to the question if you want to -reedit the disklabel - this is due to a problem with the pmax +re-edit the disklabel - this is due to a problem with the pmax disklabel code and it should be worked around by the install script. -So what does the install script explicitely do ? +So what does the install script explicitly do ? These script will do most of the work of transferring the system from the tar files onto your disk. You will frequently be asked for confirmation diff --git a/distrib/notes/pmax/prep b/distrib/notes/pmax/prep index 15eb1258dc0..f73ea0cee28 100644 --- a/distrib/notes/pmax/prep +++ b/distrib/notes/pmax/prep @@ -20,7 +20,7 @@ least not for the root and the swap partitions) because they are set in the simpleroot image to to 32M for root and 64M for swap. About the rest of your disk you can still decide yourself. -Asumming a classic partition scheme with root (`/') and /usr filesystems, +Assuming a classic partition scheme with root (`/') and /usr filesystems, a comfortable size for the OpenBSD root filesystem partition is about 32M; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike Ultrix, there are no restrictions on diff --git a/distrib/notes/pmax/whatis b/distrib/notes/pmax/whatis index 33243608692..681808e05e0 100644 --- a/distrib/notes/pmax/whatis +++ b/distrib/notes/pmax/whatis @@ -1,4 +1,4 @@ OpenBSD 2.2 is the first public release of OpenBSD for the DECstation and DECsystem family of computers. This release includes kernel -support for ELF shared libraries and uses them througout the +support for ELF shared libraries and uses them throughout the userland. diff --git a/distrib/notes/pmax/xfer b/distrib/notes/pmax/xfer index 1fa81970656..21a5f30410f 100644 --- a/distrib/notes/pmax/xfer +++ b/distrib/notes/pmax/xfer @@ -6,7 +6,7 @@ Installation is supported from several media types, including: The steps necessary to prepare the distribution sets for installation depend on which method of installation you choose. The various methods are explained below. -Those are only the preparationis required before you start +Those are only the preparations required before you start the installation. To prepare for installing via an NFS partition: diff --git a/distrib/notes/powerpc/contents b/distrib/notes/powerpc/contents index 4ac2eca8f7f..b2eff768c7e 100644 --- a/distrib/notes/powerpc/contents +++ b/distrib/notes/powerpc/contents @@ -5,7 +5,7 @@ out as follows: .../2.2/powerpc/ INSTALL.powerpc Installation notes; this file. - CKSUM Output of the cksum(1) and md5(1) progams + CKSUM Output of the cksum(1) and md5(1) programs MD5 usable for verification of the correctness of downloaded files. @@ -23,7 +23,7 @@ As well you may be interested in .../2.2/tools/ miscellaneous i386 installation utilities like - rawwrite.exe, gzip.exe, and pfdisk.exe; see + rawrite.exe, gzip.exe, and pfdisk.exe; see installation section, below. diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware index 6c078f46126..d999a78f657 100644 --- a/distrib/notes/sparc/hardware +++ b/distrib/notes/sparc/hardware @@ -14,14 +14,14 @@ OpenBSD/sparc 2.2 does NOT run on these machines (yet): multi-processor issues. - sun4u (e.g. Ultrasparcs) -- currently no support for 64-bit Sparc architecture extensions. - - clones that are differnt from the Sun systems (e.g. Solbourne) + - clones that are different from the Sun systems (e.g. Solbourne) 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 X or compile the system, more RAM is recommended. (OpenBSD with 4M of RAM feels like Solaris with 4M of RAM.) Note that until you have around 16M of RAM, getting more RAM is more important than getting a -faster CPU.) Installation from "ramdisk" kernels requries 8M of RAM. +faster CPU.) Installation from "ramdisk" kernels requires 8M of RAM. Supported devices include: sun4c and sun4m SBus video: @@ -101,7 +101,7 @@ status and check for updates. If you have Sparc hardware you can donate or make available at nominal cost, please mention this on the lists, many things aren't being tested -or developed simply because devlopers usually have only a Sparcstation +or developed simply because developers usually have only a Sparcstation at hand, not an array of systems. Donation or mid/long term loan of UltraSparc (sun4u) or HyperSparc (sun4m) systems would help ensure the long-term viability of OpenBSD on Sparc based systems. diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 0c9bef18961..7dcb1807a80 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -27,7 +27,7 @@ This section of the install document is really broken into several parts: - installing from Sun OS - net boot or diskless setup information -The first section explains why we have two differnt install scripts. +The first section explains why we have two different install scripts. The second section gets you up to the point where you've booted the kernel from whatever media or setup described in the previous section, to where you have to respond to prompts from the install script(s). The next two @@ -44,7 +44,7 @@ version that is not well tested and the older multi-floppy set. Both accomplish the same thing, but the install/upgrade scripts and procedures are quite different between the old and new version. -The other difference bewtween the the two forms are in their bootblocks, +The other difference between the the two forms are in their bootblocks, and filesystems. The "floppy22.fs" image is the compressed ramdisk form, the "kc22.fs" paired with either "inst22.fs" or "upgr22.fs" comprise a bootable kernel floppy and associated install/upgrade filesystem floppy. @@ -57,8 +57,8 @@ Booting from the Installation Media: Prior to attempting an installation, you should make sure that everything of value on the target system has been backed up. While installing OpenBSD -does not neccessarily wipe out all the partitions on the hard disk, errors -during the install process can have unforseen consequences and you will +does not necessarily wipe out all the partitions on the hard disk, errors +during the install process can have unforeseen consequences and you will probably render the system unbootable if you start, but do not complete the installation. Have the installation media for the prior installation, be it a SunOS CD-ROM or *BSD install diskettes is good insurance if you @@ -67,13 +67,13 @@ 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 architecure and age, you may needed to reference the PROM +on the system architecture and age, you may needed to reference the PROM monitor manual for your system for details. There are three main cases: sun4 (older servers, deskside workstations): - promt is a ">", boot command is "b", uses sd(c,s,p) syntax + prompt is a ">", boot command is "b", uses sd(c,s,p) syntax with s defined as scsi-unit*8+lun in hex OpenBoot Version 1 (newer servers, desktop workstations): prompt is "ok", boot command is "boot" uses sd(c,s,p) syntax @@ -87,7 +87,7 @@ as the default by doing a "setenv sunmon-compat? false" command, followed by a "reset" command. Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks, this -is described elsewere in some detail. For the purposes of this section, +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. @@ -100,7 +100,7 @@ Booting from Floppy Disk installation media: This will cause the kernel contained in the floppy to be booted. After the kernel loads, it will eject the bootable floppy and prompt for a filesystem floppy - for the two floppy installation insert -the appropriate filesystem flopppy, for the ramdisk installion, +the appropriate filesystem floppy, for the ramdisk installation, just hit return, the filesystem image is internal to the kernel. After the initial device probe messages you'll asked to start the @@ -114,14 +114,14 @@ Booting From CD-ROM installation media: ok boot sd(,6,0)bsd # for version 1 OpenBOOT ROMs ok boot cdrom bsd # for version 2 OpenBOOT ROMs -If the boot is successul, you will get a loader version message, +If the boot is successful, you will get a loader version message, executable sizes and then the Kernel copyright and device probe messages. Boot failure modes are typically a lot of CD-ROM drive action, but no messages or complaints about magic numbers, checksums or formats. Not all sparc systems support bootable CDROMS and the current -boot image is only known to work on sun4c architctures. If it +boot image is only known to work on sun4c architectures. If it does not work, you'll have to create a boot floppy or bootable hard disk using the instructions under preparing boot media. @@ -130,7 +130,7 @@ install or upgrade procedure. Proceed to the section `Running the installation scripts' below. -Booting from SCSI disk (miniroot or flopy image) +Booting from SCSI disk (miniroot or floppy image) Boot the miniroot by typing the appropriate command at the PROM: @@ -195,7 +195,7 @@ may be a better option. or slow network connection, most likely more than a minute. If some action doesn't eventually happen, or the spinning cursor has stopped and nothing further has happened, either your boot medias - is proably bad, your diskless setup isn't correct or you may have + is probably bad, your diskless setup isn't correct or you may have a hardware or configuration problem. You will then be presented with the OpenBSD kernel boot @@ -213,13 +213,13 @@ may be a better option. alarmed, these are completely normal. The first warning occurs because while OpenBSD/sparc can boot from the floppy drive, the kernel itself lacks a floppy driver for some - architctures. + architectures. When the loading process is complete, the boot floppy will be ejected and you will be prompted to insert a filesystem floppy, just hit return since the filesystem is contained in the kernel image just loaded. Next there will be a prompt asking you for - a shell name, just hit return to start executing the installion + a shell name, just hit return to start executing the installation setup script. You will next be asked for your terminal type. If you are @@ -292,7 +292,7 @@ may be a better option. link0 -link1 Use UTP (twisted pair) port -link0 link1 Use AUI port -*** IMPORTANT - these are the correct setting for Sparc ehternet cards, +*** IMPORTANT - these are the correct setting for Sparc ethernet cards, the suggestions shown by the install script are generic and may or may not be correct... @@ -684,7 +684,7 @@ use internal NFS routines to load the kernel image directly from the exported root partition. Please understand that no one gets this right the first try, since -there is a lot of setup and all the host deamons must be running and +there is a lot of setup and all the host daemons must be running and configured correctly. If you have problems, extract the diskless(8) manpage, find someone who's been through it before and use the host syslog and tcpdump(8) to get visibility of what's happening (or not). @@ -731,14 +731,14 @@ root directory, as well as the path of the client's root on that server. Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root filesystem server, asking for an NFS file handle corresponding to the root filesystem. If successful, the boot -rogram starts reading from the remote root filesystem in search of the +program starts reading from the remote root filesystem in search of the kernel which is then read into memory. You will want export the miniroot22.fs filesystem to the client. You can dd this filesystem image to some spare partition, mount and export tat partition or use tar to copy the contents to a more convenient spot. -Alternatively you an build bootable partition from the ditribution sets +Alternatively you an build bootable partition from the distribution sets as follows: Unpack `base.tar.gz' and `etc.tar.gz' on the server in the root directory diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep index d0807bb564d..67dc33a3d27 100644 --- a/distrib/notes/sparc/prep +++ b/distrib/notes/sparc/prep @@ -94,7 +94,7 @@ OpenBSD partitions. OpenBSD and Sun BSD bootblocks are similar in concept, though implemented -differntly. The OpenBSD bootblocks are architecture independent and also +differently. The OpenBSD bootblocks are architecture independent and also understand the extended disklabels with 16 partitions. You can use SunOS bootblocks, but remember that OpenBSD bootblocks must be installed with OpenBSD installboot and SunOS bootblocks with SunOS installboot. diff --git a/distrib/notes/sparc/upgrade b/distrib/notes/sparc/upgrade index 900009c8c79..47c73f3f964 100644 --- a/distrib/notes/sparc/upgrade +++ b/distrib/notes/sparc/upgrade @@ -3,9 +3,9 @@ instructions in the section "Installing OpenBSD". If you are upgrading with the miniroot or the new single floppy image, select the (U)pdate option rather than the (I)nstall option at the prompt -in the inststall process. +in the install process. -If you are using the old multi-floppy installsyion procedure, use the +If you are using the old multi-floppy installation procedure, use the "upgr22.fs" floppy rather than the "inst22.fs" floppy when prompted to put in the filesystem diskette. When you arrive at the shell prompt, run the "upgrade" script rather than "install" script. diff --git a/distrib/notes/sparc/whatis b/distrib/notes/sparc/whatis index 9cfb85d4967..aed3582c862 100644 --- a/distrib/notes/sparc/whatis +++ b/distrib/notes/sparc/whatis @@ -11,7 +11,7 @@ development" rather than a production ready release. There are still known problems with the kernel and missing support for some common devices. What this means is that if you try to install OpenBSD/sparc as a replacement -for SunOS or Solaris in a production envionnment, you will get the features +for SunOS or Solaris in a production environment, you will get the features mentioned above, but probably not a stable/reliable system. On the other hand, if you're looking for an operating system for a personal workstation or for working with unix tools and internals, you might find OpenBSD/sparc diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer index 62025bdcf5d..d608d31f7ef 100644 --- a/distrib/notes/sparc/xfer +++ b/distrib/notes/sparc/xfer @@ -32,7 +32,7 @@ the sets to a local FTP or NFS server, or copy them to a partition on the target system's disk or onto a SCSI tape. The variety of options listed may seem confusing, but situations vary -widely in terms of what peripherals and what sort of network arragements +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. @@ -72,11 +72,11 @@ Creating a bootable floppy disk using SunOS or other Un*x-like system: files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. - Under SunOS, the comand would be: + Under SunOS, the command would be: dd if=floppy22.fs of=/dev/rfdc0 bs=36b - If you are using someting other than SunOS, you may have to adapt + If you are using something other than SunOS, you may have to adapt this to conform to local naming conventions for the floppy and options suitable for copying to a "raw" floppy image. The key issue is that the device name used for the floppy *must* be one @@ -108,10 +108,10 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: the disklabel issues described below under "uncompatible systems". This requires that you be running SunOS, Solaris, OpenBSD or NetBSD - which have a compatible view of SunOS disk labels and paritions. + which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the floppy drive. - Under SunOS, the comand would be: + Under SunOS, the command would be: dd if=floppy22.fs of=/dev/rsd0b bs=36b - or - @@ -119,7 +119,7 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: The blocksize is arbitrary as long as it's a multiple of 512-bytes and within the maximum supported by the driver, i.e. bs=126b may - not work for all cases. Again, device/parition names may vary, + not work for all cases. Again, device/partition names may vary, depending on the OS involved. If you are preparing the hard drive on an incompatible system or @@ -128,14 +128,14 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: you prepare a bootable hard-drive even if don't have a working operating system on your Sparc, but it important to understand that the bootable image installed this way includes a "disk label" - which can wipe out any pre-existing disklabels or paritioning for + which can wipe out any pre-existing disklabels or partitioning for the drive. The floppy image is used only for booting, and can be placed in a partition that will be overwritten during the install process, - since it actaully runs of of a ram-disk image in the kernel. In + since it actually runs of of a ram-disk image in the kernel. In contrast the miniroot is a normal unix root filesystem and you - must place in a parition that will not be overwritten until you've + must place in a partition that will not be overwritten until you've completed the installation process. To copy the floppy image to the whole disk, overwriting labels: @@ -143,20 +143,20 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: dd if=floppy22.fs of=/dev/rsdXc bs=36b Two notes - X should be replaced by the unit number of the target - disk, which is most likely *not* the disk/paritition that's your + disk, which is most likely *not* the disk/partition that's your current root partition. Again names may vary depending on the - OS involved. Second, after doing this, the disklable will be one - that would be appropiate for a floppy, i.e. one parition of 2880 + OS involved. Second, after doing this, the disklabel will be one + that would be appropriate for a floppy, i.e. one partition of 2880 block, and you'll probably want to change that later on. If you're starting with a virgin disk and trying to do this under - SunOS, use format(8) and newfs(8) to set up the paritions and - mark the intended parition as an normal partiton type. If you're + SunOS, use format(8) and newfs(8) to set up the partitions and + mark the intended partition as an normal partition type. If you're using OpenBSD, perhaps on another architecture, OpenBSD will create a "fictitious label" that will let you access the whole disk. - To copy the flopy image to the hard disk, preserving SunOS, + To copy the floppy image to the hard disk, preserving SunOS, Solaris NetBSD or OpenBSD labels: dd if=floppy22.fs of=/dev/rsdXc bs=1b skip=1 seek=1 @@ -169,7 +169,7 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: dd if=/tmp/label of=/dev/rsdXc bs=1b count=1 In either case, you've created a situation where the disklabel - and the filesystem information don't agree about the paritition + and the filesystem information don't agree about the partition size and geometry, however the results will be usable. @@ -177,9 +177,9 @@ Creating a network bootable setup using SunOS or other Un*x-like system: The details of setting up a network bootable environment vary considerably, depending on the networks host. Extract the - OpenBSD diskless(8) man page from the share.tar.gz distibution + OpenBSD diskless(8) man page from the share.tar.gz distribution set or see the copy on the OpenBSD web page. You will also - need to reference the relevant man pages or adminstrators guide + need to reference the relevant man pages or administrators guide for the host system. Basically, you will need to set up reverse-arp (rarpd) and boot diff --git a/distrib/notes/sun3/hardware b/distrib/notes/sun3/hardware index 383ce2b5401..be07feae09a 100644 --- a/distrib/notes/sun3/hardware +++ b/distrib/notes/sun3/hardware @@ -41,7 +41,7 @@ The following Sun3 hardware is supported: Note 1: The "si" driver now supports DMA and disconnect/reselect - but due to the imaturity of the DMA code, those features + but due to the immaturity of the DMA code, those features are disabled by default. To enable DMA (and get faster SCSI performance) patch the variable si_options in the file /usr/src/sys/arch/sun3/dev/ncr_si.c as indicated. diff --git a/distrib/notes/sun3/install b/distrib/notes/sun3/install index 99e311833ca..87692e5c436 100644 --- a/distrib/notes/sun3/install +++ b/distrib/notes/sun3/install @@ -27,7 +27,7 @@ messages, and then the following "welcome" screen: Welcome to the OpenBSD/sun3 RAMDISK root! This environment is designed to do only three things: -1: Partititon your disk (use the command: edlabel /dev/rsd0c) +1: Partition your disk (use the command: edlabel /dev/rsd0c) 2: Copy a miniroot image into the swap partition (/dev/rsd0b) 3: Reboot (using the swap partition, i.e. /dev/sd?b). diff --git a/distrib/notes/sun3/prep b/distrib/notes/sun3/prep index d5603deae5f..064dd250b4a 100644 --- a/distrib/notes/sun3/prep +++ b/distrib/notes/sun3/prep @@ -5,7 +5,7 @@ ALL DATA on any attached storage devices. You will need to know the SCSI target ID of the drive on which you will install OpenBSD. Note that SunOS/sun3 uses confusing names for -the SCSI devcies: target 1 is sd2, target 2 is sd4, etc. +the SCSI devices: target 1 is sd2, target 2 is sd4, etc. It might be a good time to run the diagnostics on your Sun3. First, attach a terminal to the "ttya" serial port, then set the "Diag/Norm" diff --git a/distrib/notes/sun3/whatis b/distrib/notes/sun3/whatis index 057e8c40706..ad5109dc30f 100644 --- a/distrib/notes/sun3/whatis +++ b/distrib/notes/sun3/whatis @@ -15,7 +15,7 @@ New features added since the 1.0 release include: Sun3/260 models (and vastly improved performance) * SMD disk drivers -- almost (still need testing) -Old features (from 1.0 and earier) worth mentioning: +Old features (from 1.0 and earlier) worth mentioning: * SunOS 4.1 compatibility (runs most Sun3 applications) * Supports most SCSI devices (CD-ROM, etc) * Diskless boot capability |