diff options
Diffstat (limited to 'distrib/notes/sparc')
| -rw-r--r-- | distrib/notes/sparc/contents | 7 | ||||
| -rw-r--r-- | distrib/notes/sparc/hardware | 5 | ||||
| -rw-r--r-- | distrib/notes/sparc/install | 347 | ||||
| -rw-r--r-- | distrib/notes/sparc/prep | 50 | ||||
| -rw-r--r-- | distrib/notes/sparc/upgrade | 18 | ||||
| -rw-r--r-- | distrib/notes/sparc/whatis | 20 |
6 files changed, 399 insertions, 48 deletions
diff --git a/distrib/notes/sparc/contents b/distrib/notes/sparc/contents index 7668fcb4091..cc8c6ba0c5e 100644 --- a/distrib/notes/sparc/contents +++ b/distrib/notes/sparc/contents @@ -5,9 +5,6 @@ as follows: .../2.1/sparc/ INSTALL.sparc Installation notes; this file - floppy.fs The sparc boot and installation - floppy; see below. - kc21.fs The sparc boot floppy; see below. inst21.fs The sparc installation floppy; see below. upgr21.fs The sparc upgrade floppy; see below. @@ -54,8 +51,8 @@ These bootable images are also useful as "failsafe" boots for system maintenance and disaster recovery. The kernel and boot images are provided for net booting installations. -The OpenBSD bootblocks will work with the provided miniroot images, -while Sun bootblocks require a separate kernel image and root filesystem. +While the OpenBSD bootblocks will work with the provided miniroot images, +Sun bootblocks require a separate kernel image and root filesystem. Bootable installation/upgrade floppies: diff --git a/distrib/notes/sparc/hardware b/distrib/notes/sparc/hardware index 71919837259..54df4d93708 100644 --- a/distrib/notes/sparc/hardware +++ b/distrib/notes/sparc/hardware @@ -93,6 +93,11 @@ OpenBSD 2.1 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. +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 +at hand, not an array of systems. + Your support in terms of documenting previously unknown problems with OpenBSD/sparc, helping debug known problems, implementng missing pieces, and testing OpenBSD on various architectures is actively encouraged. diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 27ae5208413..ff7a2777b8e 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -90,7 +90,7 @@ If you've loaded the miniroot onto some other disk than `sd0' adapt the boot specifier accordingly, e.g.: > b sd(0,20,1)bsd # example - scsi target 4 on sun4 monitors* - ok b sd(0,4,1)bsd # example - scsi target 4 on V1 OpenBOOT ROM + ok boot sd(0,4,1)bsd # example - scsi target 4 on V1 OpenBOOT ROM ok boot disk1:b bsd # example - scsi target 1 on v2 OpenBOOT ROM (*) for sun4 this is scsi-target*8+scsi-lun (usually 0) expressed in hex... @@ -107,8 +107,8 @@ First, you must setup a diskless client configuration on a server. If you are using a OpenBSD system as the boot-server, have a look at the diskless(8) manual page for guidelines on how to proceed with this. If the server runs another operating system, you'll have to consult -documentation that came with it (on SunOS systems, add_client(8) is a -good start). +documentation that came with it (on SunOS systems, add_client(8) and +the Sun System/Networks administrators guide constitute a good start). The set up is similar to SunOS diskless setup, but not identical, because the Sun setup assumes that the bootblocks load a kernel image, which then @@ -298,13 +298,333 @@ drivedata: 0 <END SAMPLE DISKLABEL SCREEN> -If you are upgrading a OpenBSD installation, start the upgrade script, or -select "U" from the floppy or miniroot installation script: +Installing using the new Single Floppy procedure. + +The following is a walk-through of the steps you will take while +getting OpenBSD installed on your hard disk. If any question has a +default answer, it will be displayed in brackets ("[]") after the +question. If you wish to stop the installation, you may hit Control-C +at any time, but if you do, you may have to begin the installation +process again from scratch. Using Control-Z to suspend the process +may be a better option. + + Boot your machine using the floppy21.fs floppy. When + presented with the PROM monitor prompt, type(*): + "boot floppy bsd" or "boot fd()bsd" + and then hit return. You should see about the primary and + secondary boot and then the kernel should start to load. + + (*) See the PROM monitor information for your system. + + It will take a while to load the kernel from the floppy, + 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 floppy is + bad or you are having hardware problems. + + You will then be presented with the OpenBSD kernel boot + messages. You will want to read them to determine your + disk's name and geometry. Its name will be something like + "sd0" or "wd0" and the geometry will be printed on a line that + begins with its name. As mentioned above, you will need your + disk's geometry when creating OpenBSD partitions. You will + also need to know the device name to tell the install tools + what disk to install on. + + While booting, you will probably see several warnings. You + may be warned that the kernel can't figure out what device + it booted from and that no swap space is present. Do not be + 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. + + 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 + setup script. + + You will next be asked for your terminal type. If you are + installing from a keyboard/monitor console, the default of + "sun" if 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 vt100). Next you + will be prompted for a choice of which text editor to use at + several places in the install script. You will probably want + to use "vi" if your terminal supports this. + + After entering the terminal type you will be greeted by a + welcome message and asked if you really want to continue. + Assuming you answered yes, the install program will then tell + you which disks of that type it can install on, and ask you + which it should use. The name of the disk is typically "sd0". + Reply with the name of your disk. + + Next you will have to edit or create a disklabel for the disk + OpenBSD is being installed on. The installation script will + invoke the text editor allowing you to do this. Note that + partition 'c' inside this disk label should ALWAYS reflect the + entire disk, including any non-OpenBSD portions. The root file + system should be in partition 'a', and swap is usually in partition + 'b'. It is recommended that you create separate partitions for + root and /usr, you may also want to specify /var and /home + partitions. + + The swap partition (usually 'b') should have a type of "swap", all + other native OpenBSD partitions should have a type of "4.2BSD". + Block and fragment sizes are usually 8192 and 1024 bytes, but can + also be 16384 and 2048 bytes. + + The install program will now label your disk and ask which file + systems should be created on which partitions. It will auto- + matically select the 'a' partition to be the root file system. + Next it will ask for which disk and partition you want a file + system created on. This will be the same as the disk name (eg. + "sd0") with the letter identifying the partition (eg. "d") + appended (eg. "sd0d"). Then it will ask where this partition is + to be mounted, eg. /usr. This process will be repeated until + you just hit return. + + At this point you will be asked to confirm that the file system + information you have entered is correct, and given an opportunity + to change the file system table. Next it will create the new file + systems as specified, OVERWRITING ANY EXISTING DATA. This is the + point of no return. + + After all your file systems have been created, the install program + will give you an opportunity to configure the network. The network + configuration you enter (if any) can then be used to do the install + from another system using NFS, HTTP or FTP, and will also be the + configuration used by the system after the installation is complete. + + If you select to configure the network, the install program will + ask you for a name of your system and the DNS domain name to use. + Note that the host name should be without the domain part, and that + the domain name should NOT include the host name part. + + Next the system will give you a list of network interfaces you can + configure. For each network interface you select to configure, it + will ask for the IP address to use, the symbolic host name to use, + the netmask to use and any interface-specific flags to set. The + interface-specific flags are usually used to determine which media + the network card is to use. This is driver dependent, but for the + sparc le(4) driver, the flags usually carry meaning: + + -link0 -link1 Use existing setting (only setup by netboot) + link0 -link1 Use UTP (twisted pair) port + -link0 link1 Use AUI port + + After all network interfaces have been configured the install pro- + gram will ask for a default route and IP address of the primary + name server to use. You will also be presented with an opportunity + to edit the host table. + + At this point you will be allowed to edit the file system table + that will be used for the remainder of the installation and that + will be used by the finished system, following which the new file + systems will be mounted to complete the installation. + + After these preparatory steps has been completed, you will be + able to extract the distribution sets onto your system. There + are several install methods supported; FTP, HTTP, tape, CD-ROM, NFS + or a local disk partition. To install from a tape, the distrib- + ution sets must have been written to tape prior to running the + installation program, either as tar images or as gzipped tar + images. Note that installation sets on multiple floppies is not + currently supported. + + To install via FTP: + To begin an FTP install you will need the following + pieces of information. Don't be daunted by this list; + the defaults are sufficient for most people. + 1) Proxy server URL if you are using a URL-based + ftp proxy (squid, CERN ftp, Apache 1.2 or higher). + You need to define a proxy if you are behind a + firewall that blocks outgoing ftp (assuming you + have a proxy available to use). + 2) Do you need to use passive mode ftp? Most modern + ftp servers are capable of dealing with passive + ftp connections. You only need to enable this + option if you are behind a firewall that allows + outgoing ftp but blocks incoming tcp ports > 1023. + If in doubt say yes to this option. + Note that you will not be asked about passive + ftp if you are using a proxy. + 3) The IP address (or hostname if you enabled + DNS earlier in the install) of an ftp server + carrying the OpenBSD 2.1 distribution. + If you don't know, just hit return when + asked if you want to see a list of such hosts. + 4) The ftp directory holding the distribution sets. + The default value of pub/OpenBSD/2.1/sparc + is almost always correct. + 5) The login and password for the ftp account. + The default will be correct unless you are + doing non-anonymous ftp. + + For instructions on how to complete the installation via + ftp, see the section named "Common URL installations" below. + + To install via HTTP: + To begin an HTTP install you will need the following + pieces of information: + 1) Proxy server URL if you are using a URL-based + http proxy (squid, CERN ftp, Apache 1.2 or higher). + You need to define a proxy if you are behind a + firewall that blocks outgoing http connections + (assuming you have a proxy available to use). + 3) The IP address (or hostname if you enabled + DNS earlier in the install) of an http server + carrying the OpenBSD 2.1 distribution. + If you don't know, just hit return when + asked if you want to see a list of such hosts. + 4) The directory holding the distribution sets. + There is no standard location for this; + You should use the directory specified + along with the server in the list of official + http mirror sites that you received in step 3. + + For instructions on how to complete the installation via + http, see the section named "Common URL installations" below. + + To install from tape: + In order to install from tape, the distribution sets to be + installed must have been written to tape previously, either + in tar format or gzip-compressed tar format. + + You will also have to identify the tape device where the + distribution sets are to be extracted from. This will + typically be "nrst0" (no-rewind, raw interface). + + Next you will have to provide the file number of the set + that is to be extracted. Note that the file number starts + at 1, which is the first file written to the tape. + + The install program will not automatically detect whether + an image has been compressed, so it will ask for that + information before starting the extraction. + + To install from CD-ROM: + When installing from a CD-ROM, you will be asked which + device holds the distribution sets. This will typically + be either "cd0" or "acd0". Next you will be asked which + partition on the CD-ROM the distribution is to be loaded + from. This is normally partition "a". + + Next you will have to identify the file system type that + has been used to create the distribution on the CD-ROM, + this can be either FFS or ISO CD9660. The OpenBSD CD + distribution uses the CD9660 format. + + You will also have to provide the relative path to the + directory on the CD which holds the distribution, for the + sparc this is "2.1/sparc". + + For instructions on how to complete the installation from + the CD-ROM distribution, see the section named "Common + file system installations" below. + + To install from a NFS mounted directory: + When installing from a NFS-mounted directory, you must + have completed network configuration above, and also + set up the exported file system on the NFS server in + advance. + + First you must identify the IP address of the NFS server + to load the distribution from, and the file system the + server expects you to mount. + + The install program will also ask whether or not TCP + should be used for transport (the default is UDP). Note + that TCP only works with newer NFS servers. + + You will also have to provide the relative path to the + directory on the file system where the distribution sets + are located. Note that this path should not be prefixed + with a '/'. + + For instructions on how to complete the installation from + the CD-ROM distribution, see the section named "Common + file system installations" below. + + To install from a local disk partition: + When installing from a local disk partition, you will + first have to identify which disk holds the distribution + sets. This is normally "sdN" or "wdN" where N is a + number 0 through 9. Next you will have to identify the + partition within that disk that holds the distribution, + this is a single letter between 'a' and 'p'. + + You will also have to identify the type of file system + residing in the partition identified. Currently, you can + only install from partitions that use the fast file system + (ffs). + + You will also have to provide the relative path to the + directory on the file system where the distribution sets + are located. Note that this path should not be prefixed + with a '/'. + + For instructions on how to complete the installation from + the a local disk partition, see the next section. + + Common file system installations: + The following instructions are common to installations + from local disk partitions, NFS mounted directories and + CD-ROMs. + + A list of available distribution sets will be listed. If + any sets has already been extracted, those will be marked + with an X. Enter the name of one distribution set at a + time, until all desired distribution sets has been + installed on your system. + + Common URL installations: + Once you have entered the required information, the + install program will fetch a file list and present + a list of all the distribution sets that were found + in the specified directory. (If no valid sets were found, + you will be notified and given the option of unpacking + any gzipped tar files found or getting a file list if + none were found.) If any sets have already been extracted, + those sets will be marked with an X. + + At this point you may individually select distribution + sets to install or enter "all" to install all of + the sets (which is what most users will want to do). + You may also enter "list" to get a file list or + "done" when you are done selecting distribution sets. + (It is also possible to enter an arbitrary filename + and have it treated as a file set). + + Once you have selected the file sets you want to install + and entered "done" you will be prompted to verify that + you really do want to download and install the files. + Assuming you acquiesce, the files will begin to download + and unpack. If not, you will be given the option of + installing sets via one of the other install methods. + + + When all the selected distribution sets has been extracted, you + will be allowed to select which time zone your system will be + using, all the device nodes needed by the installed system will + be created for you and the file systems will be unmounted. For + this to work properly, it is expected that you have installed + at least the "base21" and "etc21" distribution sets. + + + +Installing using the old Multi-Floppy procedure. + +<floppy boot instructions go here > + +If you are upgrading a OpenBSD installation, start the upgrade script: OpenBSD# sh upgrade.sh -else, start the installation script, or select "I" from the floppy or -miniroot installation script: +else, start the installation script: OpenBSD# sh install.sh @@ -365,7 +685,7 @@ system from a serial console, you may 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 scree-#rows +for input-device, output-device, screen-#columns, and screen-#rows as appropriate. If you plan on using the extra serial ports on 4/300 systems, @@ -394,15 +714,14 @@ You need a SunOS machine to install OpenBSD. You also need at least the following pieces: the *.tar.gz files you want to install (as a minimum, base.tar.gz) - gzip (GNU gzip) SunOS binary + gunzip (GNU gzip) SunOS binary gtar (GNU tar) SunOS binary - the "install.sh" script a "/boot" file from a SunOS machine that matches your machine type (e.g. sun or sun4c) a kernel, most likely "/bsd" -All these pieces, except "/boot", are supplied in the OpenBSD/sparc -distribution. +All these pieces, except "/boot" and the GNU utilities are supplied in +the OpenBSD/sparc distribution. You need to format and partition the disk using SunOS (since OpenBSD/sparc uses SunOS disk labels.) Give yourself adequate @@ -464,8 +783,8 @@ And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. The GNU gunzip and gtar programs are not distributed as part of SunOS, but may be present in your local/bin. If not, you will need to obtain them from a GNU archive and install before proceeding. The OpenBSD -tar files are in a "new format" that includes directory information, -and the standard SunOS tar will not read them. +tar files are in the "new format" that includes directory information, +and the standard SunOS tar will not extract from them successfully. After the files have been extracted, setup /mnt/etc/fstab to match your actual disk layout. (Minus the "/mnt" component of each path, of diff --git a/distrib/notes/sparc/prep b/distrib/notes/sparc/prep index e77da8c9abe..d0807bb564d 100644 --- a/distrib/notes/sparc/prep +++ b/distrib/notes/sparc/prep @@ -58,39 +58,45 @@ Also, you cannot use the security modes of the sparc OpenBOOT ROM. Please note that while OpenBSD and SunOS have a reasonable degree of -compatibility between filesystems and OpenBSD can even run SunOS -binaries (when built with COMPAT_SUNOS), there are some problems to -watch out for. +compatibility between disk labels and filesystems there are some problems +to watch out for during initial installation or when trying to maintain +both OpenBSD and SunOS environments on the same system. If the OpenBSD fsck(8) utility is used on a SunOS filesystem, it will - set OpenBSD "clean flags" and BSD4.4 summary fields in the Superblock. - SunOS will *not* like this, you will have to do a fsck -b 32 under - SunOS to access an alternate superblock to fix the filesystem. You - should always specify SunOS filesystem with "0" in the "fsck passno" - field in /etc/fstab to prevent this, and preferably mount them "RO". + set OpenBSD "clean flags" and BSD4.4 summary fields in the superblock. + SunOS does *not* like this and you will have to do a "fsck -b 32" under + SunOS to access an alternate superblock to repair the filesystem. You + should always specify SunOS filesystem with a "pass number" of 0 in + their /etc/fstab entry to prevent this, and preferably mount them "RO". If SunOS fsck is used on an OpenBSD filesystem in the default OpenBSD - new format (4.4BSD) it will first complain about the superblock and - then about missing . and .. entries. Do *not* try to "correct" these + (4.4BSD) format, it will first complain about the superblock and then + about missing . and .. entries. Do *not* try to "correct" these problems, as attempting to do so will completely trash the filesystem. OpenBSD supports both OpenBSD "native" disklabels and "Sun compatible" disklabels. Unless you have some really good reason, you should stick -with the Sun compatible labels. The disklabel(8) "-r" says to use -OpenBSD labels, which is a bit counter-intuitive and contrary to the -reasons why you'd use "-r" on other OpenBSD ports. Don't use "-r"... +with the Sun compatible labels. The disklabel(8) "-r" switch says to +use OpenBSD labels, which is a bit counter-intuitive and contrary to +the reasons why might want to use "-r" on other OpenBSD ports. -The OpenBSD "Sun Compatible" disklabel are extended to support 16 partitions, -which may be compatible with Solaris, but older SunOS format(8) programs -only see the first 8 parititions and may "lose" information on the extended -paritions. Use SunOS format(8) only with *extreme* caution on drives that -contain OpenBSD partitions. +Don't use "-r" with disklabel(8). -OpenBSD and Sun BSD bootblocks are similar, though differnt. You can use -Sun bootblocks, but the OpenBSD bootblock are architecture independent -and understand the extended disklabels. To install OpenBSD bootblocks, -you must use the OpenBSD installboot and vice versa. +The OpenBSD "Sun Compatible" disklabel have been extended to support 16 +partitions, which may be compatible with Solaris, but the old SunOS +format(8) utility only sees the first 8 partititions and may "lose" +information about the extended partitions. + +Use SunOS format(8) only with *extreme* caution on drives that contain +OpenBSD partitions. + + +OpenBSD and Sun BSD bootblocks are similar in concept, though implemented +differntly. 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 e2437d750ff..05563834835 100644 --- a/distrib/notes/sparc/upgrade +++ b/distrib/notes/sparc/upgrade @@ -1,6 +1,16 @@ -To upgrade to OpenBSD 2.1 from a previous version follow the instructions -in the section "Installing OpenBSD", but run the script `upgrade.sh' -instead of `install.sh'. +To upgrade to OpenBSD 2.1 from a previous version start with the general +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. + +If you are using the old multi-floppy installsyion procedure, use the +"upgr21.fs" floppy rather than the "inst21.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. The upgrade script will use the existing disk partitions to install the -new system in, and also preserves the files in `/etc'. +new system in, and also preserves files in `/etc' which you are likely +to have customized since a previous installation. + diff --git a/distrib/notes/sparc/whatis b/distrib/notes/sparc/whatis index 58b32fd82b4..75645c329c7 100644 --- a/distrib/notes/sparc/whatis +++ b/distrib/notes/sparc/whatis @@ -1,5 +1,19 @@ OpenBSD/sparc 2.1 is brought to you by the same people who did the first -free BSD port (based on Chris Torek's 4.4BSD work). Many more sparc +free BSD sparc port (based on Chris Torek's 4.4BSD work). Many more sparc models and devices are now supported. -In addition to the SunOS 4.1 compatibility, OpenBSD 2.1 will also run some -number of SunOS 5 (SVR4) executables in binary emulation mode. + +In addition to the providing SunOS 4.1 compatibility, OpenBSD 2.1 will +also run some number of SunOS 5 (SVR4) executables in binary emulation mode. + +OpenBSD/sparc has gone though several development cycles since it's origin, +but the OpenBSD/sparc 2.1 release should be considered as "under active +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 +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 +quite satisfactory as released. + |