diff options
Diffstat (limited to 'distrib/notes/sparc64/install')
| -rw-r--r-- | distrib/notes/sparc64/install | 388 |
1 files changed, 95 insertions, 293 deletions
diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install index e741c90a244..fc230754c67 100644 --- a/distrib/notes/sparc64/install +++ b/distrib/notes/sparc64/install @@ -1,19 +1,23 @@ OpenBSDInstallPrelude -There are several ways to install OpenBSD onto a disk. The easiest way -in terms of preliminary setup is to use the OpenBSD miniroot that can -be booted off your local disk's swap partition. The normal way is to -use the OpenBSD installation floppy, or an installation tape. - -If your Sparc is hooked up in a network and you can find a server to -arrange for a diskless setup, which is a convenient way to install on a -machine whose disk does not currently hold a usable operating system. +dnl XXX uncomment and alter once there is floppy, cdrom or miniroot +dnl XXX available. +dnl There are several ways to install OpenBSD onto a disk. The easiest way +dnl in terms of preliminary setup is to use the OpenBSD miniroot that can +dnl be booted off your local disk's swap partition. The normal way is to +dnl use the OpenBSD installation floppy. +dnl +dnl If your Sparc is hooked up in a network and you can find a server to +dnl arrange for a diskless setup, which is a convenient way to install on a +dnl machine whose disk does not currently hold a usable operating system. +dnl This is difficult to get set up correctly the first time, but easy to +dnl use afterwards. (see ``Installing using a diskless setup'' below). +Currently, the only way to install OpenBSD/MACHINE is to use a diskless +setup, which is a convenient way to install on a machine whose disk does +not currently hold a usable operating system. This is difficult to get set up correctly the first time, but easy to use afterwards. (see ``Installing using a diskless setup'' below). -It is also possible to install OpenBSD "manually" from a running SunOS -system, using SunOS tools and gnu tar and gunzip (see ``Installing from -SunOS'' below). Booting from the Installation Media: @@ -24,7 +28,7 @@ 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. Having the installation media for the prior installation, -be it a SunOS or OpenBSD CD-ROM or OpenBSD install diskettes is good +be it a Solaris or OpenBSD CD-ROM or OpenBSD install diskettes is good insurance if you want to be able to "go back" for some reason. After taking care of all that, bring your system down gracefully using @@ -33,125 +37,62 @@ prompt. Sun PROM monitor commands and setup differ considerably depending on the system architecture and age, you may needed to reference the PROM monitor manual for your system for details. -There are four main cases: - - sun4 (older servers, deskside workstations): - 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 - with s defined as scsi-unit. - OpenBoot Version 2 (newer servers, desktop workstations): - prompt is "ok", boot command is "boot" uses diskn:p syntax. - OpenBoot Version 2 (certain newer desktop workstations): - prompt is "ok", boot command is "boot" uses diskn syntax - unless booting from a non-standard partition, in which case: - boot /sbus/esp/sd@t,0:p bsd (where "t" is the scsi target, - and "p" is the partition. examples would be t="3" and p="b") - - -If you expect your workstation to have an OpenBoot Prom but get a ">", -enter then "n" command to enter the "new command mode". You can set this -as the default by doing a "setenv sunmon-compat? false" command, followed -by a "reset" command. - -Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks, this -is described elsewhere in some detail. For the purposes of this section, -drive 0 refers to the internal or first SCSI drive, which usually has a -SCSI-ID of 3. - - -Booting from Floppy Disk installation media: - - ok boot fd()bsd # for version 1 OpenBOOT ROMs - ok boot floppy bsd # for version 2 OpenBOOT ROMs - -This will cause the kernel contained in the floppy to be booted. - -After the initial device probe messages you'll asked to start the -install or upgrade procedure. Proceed to the section ``Running the -installation scripts'' below. - - -Booting From CD-ROM installation media: - - > b sd(,30,0)OSREV/sparc/bsd.rd # for Sun4 monitors* - # (not working currently) - ok boot sd(,6,0)OSREV/sparc/bsd.rd # for version 1 OpenBOOT ROMs - ok boot cdrom OSREV/sparc/bsd.rd # for version 2 OpenBOOT ROMs - -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 -activity, 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 and sun4m 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. - -After the initial device probe messages you'll asked to start the -install or upgrade procedure. Proceed to the section ``Running the -installation scripts'' below. - - -Booting from SCSI disk (miniroot or floppy image): - -Boot the miniroot by typing the appropriate command at the PROM: - - > b sd(,,1)bsd # for sun4 monitors* - ok boot sd(,,1)bsd # for version 1 OpenBOOT ROMs - ok boot disk:b bsd # for version 2 OpenBOOT ROMs - ok boot /sbus/esp/sd@3,0:b bsd # for version 2 OpenBOOT ROMs - # that won't take disk:p syntax. - -If you've loaded the miniroot onto some other disk than the default -drive 0, modify the boot specifier accordingly, keeping in mind the -drive vs. scsi-id shuffling and partition a=0, b=1... - - > b sd(0,10,1)bsd # example - scsi target 2 on sun4 monitors* - ok boot sd(0,3,1)bsd # example - scsi target 0 on v1 OpenBOOT ROM - ok boot disk3:b bsd # example - scsi target 0 on v2 OpenBOOT ROM - ok boot /sbus/esp/sd@0,0:b bsd # example - scsi target 0 on v2 - # OpenBOOT ROM that won't take - # disk:p syntax. - -(*) for sun4 this is scsi-target*8+scsi-lun (usually 0) expressed in hex... - -This will cause the kernel contained in the miniroot to be booted. -After the initial device probe messages you'll asked to start the -install or upgrade procedure. Proceed to the section ``Running the -installation scripts'' below. - - -Booting from SCSI tape: - -Boot the miniroot by typing the appropriate command at the PROM: - - > b st(,,1) # for sun4 monitors - # (not working currently) - ok boot st(,,1) # for version 1 OpenBOOT ROMs - ok boot tape:1 # for version 2 OpenBOOT ROMs - ok boot /sbus/esp/st@4,0:1 # for version 2 OpenBOOT ROMs - # that won't take tape:n syntax. - -The above instructions assume your tape drive is the default tape drive -using SCSI id 4. If your drive uses id 5, modify the boot command -accordingly: - - > b st(,28,1) # example - 2nd tape drive on sun4 monitors - ok boot st(,5,1) # example - 2nd tape drive on v1 OpenBOOT ROM - ok boot tape1:1 # example - 2nd tape drive on v2 OpenBOOT ROM - ok boot /sbus/esp/st@5,0:1 # example - 2nd tape drive on v2 - # OpenBOOT ROM that won't take - # tape:n syntax - -This will cause the kernel contained in the miniroot to be booted. -After the initial device probe messages you'll be asked to start the -install or upgrade procedure. Proceed to the section ``Running the -installation scripts'' below. - +dnl XXX to check +dnl Note that OpenBoot Proms also do the Sun SCSI-ID shuffle for disks, this +dnl is described elsewhere in some detail. For the purposes of this section, +dnl drive 0 refers to the internal or first SCSI drive, which usually has a +dnl SCSI-ID of 3. +dnl +dnl +dnl XXX no floppy available yet +dnl Booting from Floppy Disk installation media: +dnl +dnl ok boot floppy bsd +dnl +dnl This will cause the kernel contained in the floppy to be booted. +dnl +dnl After the initial device probe messages you'll asked to start the +dnl install or upgrade procedure. Proceed to the section ``Running the +dnl installation scripts'' below. +dnl +dnl +dnl +dnl XXX no cdrom release yet +dnl Booting From CD-ROM installation media: +dnl +dnl ok boot cdrom OSREV/MACHINE/bsd.rd +dnl +dnl If the boot is successful, you will get a loader version message, +dnl executable sizes and then the Kernel copyright and device probe +dnl messages. Boot failure modes are typically a lot of CD-ROM drive +dnl activity, but no messages or complaints about magic numbers, +dnl checksums or formats. +dnl +dnl After the initial device probe messages you'll asked to start the +dnl install or upgrade procedure. Proceed to the section ``Running the +dnl installation scripts'' below. +dnl +dnl +dnl +dnl XXX no miniroot filesystem yet +dnl Booting from disk (miniroot or floppy image): +dnl +dnl Boot the miniroot by typing the appropriate command at the PROM: +dnl +dnl ok boot disk:b bsd +dnl +dnl If you've loaded the miniroot onto some other disk than the default +dnl drive 0, modify the boot specifier accordingly, keeping in mind the +dnl drive vs. scsi-id shuffling and partition a=0, b=1... +dnl +dnl ok boot disk1:b bsd # example - scsi target 1 or +dnl # second ide drive +dnl +dnl This will cause the kernel contained in the miniroot to be booted. +dnl After the initial device probe messages you'll asked to start the +dnl install or upgrade procedure. Proceed to the section ``Running the +dnl installation scripts'' below. +dnl Installing using a diskless setup: @@ -164,12 +105,9 @@ the Sun System/Networks administrators guide constitute a good start). Boot your workstation from the server by entering the appropriate `boot' -command at the monitor prompt. Depending on the PROM version in your machine, -this command takes one of the following forms: +command at the monitor prompt: - > b le()bsd.rd # for sun4 monitors - ok boot le()bsd.rd # for version 1 OpenBOOT ROMs - ok boot net bsd.rd # for version 2 OpenBOOT ROMs + ok boot net bsd.rd This will cause the kernel provided by the diskless setup to be booted. After the initial probe messages you'll asked to start the install @@ -177,7 +115,9 @@ or upgrade procedure. Proceed to the section ``Running the installation scripts'' below. -Installing using the Floppy, CD-ROM, tape, miniroot or netboot procedure: +dnl XXX Update title when installation media becomes available. +dnl Installing using the Floppy, CD-ROM, miniroot or netboot procedure: +Installing using the netboot procedure: OpenBSDInstallPart2 @@ -193,12 +133,8 @@ OpenBSDInstallPart2 OpenBSDBootMsgs 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 - architectures. + may be warned that no swap space is present. Do not be + alarmed, these are completely normal. Next there will be a prompt asking you for a shell name, just hit return to start executing the installation setup script. @@ -261,17 +197,8 @@ OpenBSDBootMsgs 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 media flags to set. This is driver - dependent, but for the sparc le(4) driver, the flags usually carry - meaning: - - auto Use existing setting (only setup by netboot) - 10baseT Use UTP (twisted pair) port - 10base5 Use AUI port - -*** 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... + the netmask to use and any media flags to set. It is usually safe + to keep the default settings. After all network interfaces have been configured the install pro- gram will ask for a default route and IP address of the primary @@ -285,7 +212,7 @@ OpenBSDBootMsgs 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 + are several install methods supported; FTP, HTTP, 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 @@ -321,17 +248,8 @@ The Sun monitor normally tries to load a file called "vmunix". On OpenBOOT ROM systems you can change it to load OpenBSD instead using the following commands: -On version 1 OpenBOOT ROMs: - >n - ok setenv boot-from sd(0,0,0)bsd - ok - -On version 2 OpenBOOT ROMs: ok setenv boot-file bsd - ok setenv boot-device /sbus/esp/sd@0,0 -On sun4 systems, you may not need to specify the boot file, as -the OpenBSD boot blocks will look for "bsd" on the boot device by default. OpenBSDCongratulations @@ -342,14 +260,7 @@ when running from a serial console, you may wish to adjust the eeprom settings for input-device, output-device, screen-#columns, and screen-#rows as appropriate. -If you plan on using the extra serial ports on 4/300 systems, -you'll need to make sure you have device nodes for them e.g.: - mknod /dev/ttyc c 12 4 - mknod /dev/ttyd c 12 5 -To use these ports for terminals etc, you will want to add them to -/etc/ttys. - -In order to use 'tip' on OpenBSD/sparc, you'll need to edit /etc/ttys +In order to use 'tip' on OpenBSD/MACHINE, you'll need to edit /etc/ttys and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. @@ -358,100 +269,9 @@ it's recommended that you buy a book that discusses it. -Installing from SunOS. - -You need a SunOS machine to install OpenBSD. You also need at -least the following pieces: - - the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgz and - etc{:--:}OSrev.tgz) - gunzip (GNU gzip) SunOS binary - gtar (GNU tar) SunOS binary - 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" 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 -partition sizes. Here is an example layout: - - partition size offset will be.. - sd0a 80000 0 / - sd0b 256000 80000 swap - sd0c 4165271 0 `whole disk' - sd0d 100000 436000 /var - sd0f 100000 336000 /tmp - sd0g 3229271 936000 /usr - sd0h 400000 536000 /var/tmp - -Use SunOS to newfs the partitions which will have filesystems on them. -(OpenBSD's filesystem format is identical to SunOS). - - sunos# newfs /dev/rsd0a - [... lots of output] - -Repeat for any other partition (in this example, /dev/rsd0d, /dev/rsd0f, -/dev/rsd0g, /dev/rsd0h). - -NOTE: If you are able to, there is a performance benefit from -newfs'ing using OpenBSD. If you newfs using the OpenBSD newfs command, -be sure to use the -O flag for your / partition, so that newfs will -use the 4.3BSD filesystem format, rather than the new 4.4BSD filesystem -format. If you forget, you will not be able to boot -- the SunOS boot -blocks do not understand the extended 4.4BSD filesystem format. - -Mount those partitions in a tree formation, under /mnt; ie: - - sunos# df - Filesystem kbytes used avail capacity Mounted on - [...] - /dev/sd0a 38427 0 38427 0% /mnt - /dev/sd0d 48249 0 48249 0% /mnt/var - /dev/sd0f 48249 0 48249 0% /mnt/tmp - /dev/sd0g 1564024 0 1564024 0% /mnt/usr - /dev/sd0h 193536 0 193536 0% /mnt/var/tmp - -Place a standard SunOS "boot" program in /mnt (your new root -partition), and use the SunOS command "installboot" to make it work. -The installboot man page says to do something like this: - - sunos# cp /usr/mdec/sdboot /mnt/boot - sunos# sync; sync - sunos# /usr/mdec/installboot -vlt /mnt/boot /usr/mdec/bootsd /dev/rsd2a - -You can now extract the provided "*.tgz files onto your disk. - - sunos# ls -FC - base{:--:}OSrev.tgz comp{:--:}OSrev.tgz man{:--:}OSrev.tgz xfont{:--:}OSrev.tgz - bsd etc{:--:}OSrev.tgz misc{:--:}OSrev.tgz xserv{:--:}OSrev.tgz - bsd.scsi3 game{:--:}OSrev.tgz xbase{:--:}OSrev.tgz - sunos{:-#-:} gunzip < base{:--:}OSrev.tgz | (cd /mnt; gtar xvpf -) - [...] for each set - -And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. - - sunos# cp bsd.scsi3 /mnt/bsd - -The GNU gunzip and gtar programs are not distributed as part of SunOS, -but may be present in your /usr/local/bin. If not, you will need to -obtain them from a GNU archive and install before proceeding. The -OpenBSD 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 -course :-) - -Now proceed to reboot the machine and the customize your installation. - - Net Boot or Diskless Setup Information: -The set up is similar to SunOS diskless setup, but not identical, because +The set up is similar to the diskless setup, but not identical, because the Sun setup assumes that the bootblocks load a kernel image, which then uses NFS to access the exported root partition, while the OpenBSD bootblocks use internal NFS routines to load the kernel image directly from the @@ -463,35 +283,17 @@ 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). -Your Sparcstation expects to be able to download a second stage bootstrap +Your UltraSPARC expects to be able to download a second stage bootstrap program via TFTP after having acquired its IP address through RevARP when instructed to boot "over the net". It will look for a filename composed of -the machine's IP address followed by the machine's architecture, separated -by a period. For example, a sun4c machine which has been assigned IP -address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'. +the machine's IP address. For example, a machine which has been assigned IP +address 130.115.144.11, will make an TFTP request for `8273900B'. Normally, this file is a symbolic link to an appropriate second-stage boot program, which should be located in a place where the TFTP daemon can find it (remember, many TFTP daemons run in a chroot'ed environment). -You can find the boot program in `/usr/mdec/boot' in the OpenBSD/sparc -distribution. Unfortunately, it is necessary to install this file -differently for sun4 and sun4c clients: the sun4 version needs to have its -`a.out' header stripped off (otherwise the machine will crash), while the -sun4c version must retain it (otherwise the PROM will complain). - -Here's an example to illustrate this whole mess: - - server# cd /<client-root-dir>/usr/mdec - if client is a sun4: - server# set SKIP=1 - server# set KARCH=SUN4 - else - server# set SKIP=0 - server# set KARCH=SUN4C - server# dd if=boot of=/tftpboot/boot.sparc.OpenBSD.$KARCH skip=$SKIP bs=32 - server# cd /tftpboot - server# ln -s boot.sparc.OpenBSD.$KARCH 8273900B.$KARCH - +You can find the boot program in `/usr/mdec/boot' in the OpenBSD/MACHINE +distribution. After the boot program has been loaded into memory and given control by the PROM, it starts locating the machine's remote root directory through @@ -536,15 +338,15 @@ A few configuration files need to be edited: Enter the entries for the remotely mounted filesystems. For example: server:/export/root/client / nfs rw 0 0 - server:/export/exec/sun4.OpenBSD /usr nfs rw 0 0 + server:/export/exec/MACHINE.OpenBSD /usr nfs rw 0 0 Now you must populate the the `/dev' directory for your client. If you server runs SunOS 4.x, you can simply change your working directory to `<root>/dev' and run the MAKEDEV script: `sh MAKEDEV all'. -On SunOS 5.x systems, MAKEDEV can also be used, but there'll be error -messages about unknown user and groups. These errors are inconsequential -for the purpose of installing OpenBSD. However, you may want to correct them -if you plan to the diskless setup regularly. In that case, you may re-run -MAKEDEV on your OpenBSD machine once it has booted. +On Solaris (SunOS 5.x) systems, MAKEDEV can also be used, but there'll be +error messages about unknown user and groups. These errors are +inconsequential for the purpose of installing OpenBSD. However, you may +want to correct them if you plan to the diskless setup regularly. In that +case, you may re-run MAKEDEV on your OpenBSD machine once it has booted. |