diff options
Diffstat (limited to 'distrib/notes/sparc')
| -rw-r--r-- | distrib/notes/sparc/hardware | 6 | ||||
| -rw-r--r-- | distrib/notes/sparc/install | 36 | ||||
| -rw-r--r-- | distrib/notes/sparc/prep | 2 | ||||
| -rw-r--r-- | distrib/notes/sparc/upgrade | 4 | ||||
| -rw-r--r-- | distrib/notes/sparc/whatis | 2 | ||||
| -rw-r--r-- | distrib/notes/sparc/xfer | 36 |
6 files changed, 43 insertions, 43 deletions
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 |