diff options
author | Miod Vallat <miod@cvs.openbsd.org> | 2001-10-14 18:28:03 +0000 |
---|---|---|
committer | Miod Vallat <miod@cvs.openbsd.org> | 2001-10-14 18:28:03 +0000 |
commit | 0a42c6b79a779df0a541501224a661ec24a1a298 (patch) | |
tree | 220c69b72a53eab65771abfa4cd7a87ee1a6d7e8 | |
parent | 5965b80d9f8a8cac7c1601a1628091fbf4d785a3 (diff) |
Solaris friendly update!
- Provide typical Solaris command lines for creating floppies, dumping
miniroots to disks, and filling tapes.
- Make the tape generation script more versatile.
- When SunOS add_client(8) is mentioned, mention Solaris share(1M) as well.
- Add ``Installing from Solaris'' instructions for sparc and sparc64 ports
- While there, slight fixes to the ``Installing from SunOS'' sections on
sparc and sun3.
-rw-r--r-- | distrib/notes/m4.common | 59 | ||||
-rw-r--r-- | distrib/notes/mvme68k/install | 6 | ||||
-rw-r--r-- | distrib/notes/sparc/install | 117 | ||||
-rw-r--r-- | distrib/notes/sparc/xfer | 32 | ||||
-rw-r--r-- | distrib/notes/sparc64/install | 96 | ||||
-rw-r--r-- | distrib/notes/sparc64/xfer | 34 | ||||
-rw-r--r-- | distrib/notes/sun3/install | 25 |
7 files changed, 292 insertions, 77 deletions
diff --git a/distrib/notes/m4.common b/distrib/notes/m4.common index 76250158f1d..064c81b9e1e 100644 --- a/distrib/notes/m4.common +++ b/distrib/notes/m4.common @@ -1,5 +1,5 @@ dnl -dnl $OpenBSD: m4.common,v 1.25 2001/10/10 23:58:27 miod Exp $ +dnl $OpenBSD: m4.common,v 1.26 2001/10/14 18:27:57 miod Exp $ dnl dnl simulate an include path with a macro 'includeit'. define(`includeit',`sinclude('INCLUDE/`$1)sinclude('INCLUDE/../`$1)')dnl @@ -87,8 +87,8 @@ define({:-OpenBSDcomp-:}, relating to C, C++, and fortran are supported. This set includes the system {:-include-:} files (/usr/{:-include-:}), the linker, the compiler tool chain, and the various system - libraries{:--:}ifelse(X$3,Xshared,{:- (except the shared - libraries, which are included as part of the base set).-:},.) + libraries{:--:}ifelse(X$3,Xshared,{:- (except the shared libraries, which are + included as part of the base set).-:},.) This set also includes the manual pages for all of the utilities it contains, as well as the system call and library manual pages.showsize($1,$2)-:})dnl @@ -181,8 +181,8 @@ dnl Use as: OpenBSDfloppydesc(single, The) or OpenBSDfloppydesc(three, Each, s) define({:-OpenBSDfloppydesc-:}, {:-Bootable installation/upgrade floppy image$3: - The $1 floppy image$3 can be copied to a floppy using rawrite.exe - or `dd', as described later in this document. + The $1 floppy image$3 can be copied to a floppy using rawrite.exe, + ntrw.exe or `dd', as described later in this document. $2 floppy image is a bootable install floppy which can be used both to install and to upgrade OpenBSD to the current version. It is also useful for maintenance and disaster recovery.-:})dnl @@ -602,7 +602,7 @@ define({:-OpenBSDXferFloppyFromDOS-:}, (i.e read-only).-:})dnl dnl define({:-OpenBSDXferFloppyFromUNIX-:}, -{:-Creating a bootable floppy disk using SunOS or other Un*x-like system: +{:-Creating a bootable floppy disk using SunOS, Solaris or other Un*x-like system: First, you will need obtain a local copy of the bootable filesystem image as described above. If possible use the cksum(1) or md5(1) @@ -610,11 +610,14 @@ define({:-OpenBSDXferFloppyFromUNIX-:}, the CKSUM or MD5 files on the mirror site. Next, use the dd(1) utility to copy the file to the floppy drive. - Under SunOS, the command would be: - + The command would likely be, under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rfd0c bs=36b + and, under Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/rdiskette0 bs=36b + but you may need to turn off the volume management daemon, vold(1M), + before attempting the copy. - If you are using something other than SunOS, you may have to adapt + If you are using another operating system, 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 @@ -653,14 +656,14 @@ define({:-OpenBSDXferBareTape-:}, "/tmp/maketape". #! /bin/sh - tape=/dev/nrst0 - mt -f ${tape} rewind + TAPE=${TAPE:-/dev/nrst0} + mt -f ${TAPE} rewind for file in base etc comp game man misc $1 do - dd if=${file}OSrev.tgz of=${tape} obs=8k conv=sync + dd if=${file}OSrev.tgz of=${TAPE} obs=8k conv=sync done - tar cf ${tape} bsd - mt -f ${tape} offline + tar cf ${TAPE} bsd + mt -f ${TAPE} offline # end of script And then: @@ -669,7 +672,11 @@ define({:-OpenBSDXferBareTape-:}, sh -x /tmp/maketape If you're using a system other than OpenBSD or SunOS, the tape - name and other requirements may change. + name and other requirements may change. You can override the + default device name (/dev/nrst0) with the TAPE environment + variable. For example, under Solaris, you would probably run: + + TAPE=/dev/rmt/0n sh -x /tmp/maketape Note that, when installing, the tape can be write-protected (i.e. read-only).-:})dnl @@ -693,22 +700,22 @@ define({:-OpenBSDXferBootTape-:}, "/tmp/maketape". #! /bin/sh - tape=/dev/nrst0 - mt -f ${tape} rewind + TAPE=${TAPE:-/dev/nrst0} + mt -f ${TAPE} rewind if test {:-$-:}# -lt 1 then - dd of=${tape} if=$2 -ifelse(X$3,X,,{:- dd of=${tape} if=$3 + dd of=${TAPE} if=$2 +ifelse(X$3,X,,{:- dd of=${TAPE} if=$3 -:})dnl -ifelse(X$4,X,,{:- dd of=${tape} if=$4 +ifelse(X$4,X,,{:- dd of=${TAPE} if=$4 -:})dnl fi for file in base etc comp game man misc $1 do - dd if=${file}OSrev.tgz of=${tape} obs=8k conv=sync + dd if=${file}OSrev.tgz of=${TAPE} obs=8k conv=sync done - tar cf ${tape} bsd - mt -f ${tape} offline + tar cf ${TAPE} bsd + mt -f ${TAPE} offline # end of script And then: @@ -725,7 +732,11 @@ ifelse(X$4,X,,{:- dd of=${tape} if=$4 sh -x /tmp/maketape noboot If you're using a system other than OpenBSD or SunOS, the tape - name and other requirements may change. + name and other requirements may change. You can override the + default device name (/dev/nrst0) with the TAPE environment + variable. For example, under Solaris, you would probably run: + + TAPE=/dev/rmt/0n sh -x /tmp/maketape Note that, when installing, the tape can be write-protected (i.e. read-only).-:})dnl diff --git a/distrib/notes/mvme68k/install b/distrib/notes/mvme68k/install index 0ef473b0508..194e9ca3d54 100644 --- a/distrib/notes/mvme68k/install +++ b/distrib/notes/mvme68k/install @@ -52,7 +52,8 @@ 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) and -the Sun System/Networks administrators guide constitute a good start). +the Sun System/Networks administrators guide constitute a good start; +on Solaris systems, share(1M) is a good starting point as well). You should then setup your workstation using the NIOT command at the BUG prompt. The Load Address should be 0x3F0000, and the Execution Address @@ -72,7 +73,8 @@ 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) and -the Sun System/Networks administrators guide constitute a good start). +the Sun System/Networks administrators guide constitute a good start; +on Solaris systems, share(1M) is a good starting point as well). Second, make sure you use a terminal emulator able to read files from the local machine and send their contents over the serial link. OpenBSD ships diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 0f5b77eb0cb..571b0ae1521 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -12,8 +12,9 @@ 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). +or Solaris system, using the system tools, as well as gunzip (and gnu tar +on SunOS); see ``Installing from SunOS'' or ``Installing from Solaris'' +below. Booting from the Installation Media: @@ -143,7 +144,8 @@ 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) and -the Sun System/Networks administrators guide constitute a good start). +the Sun System/Networks administrators guide constitute a good start; +on Solaris systems, share(1M) is a good starting point as well). Boot your workstation from the server by entering the appropriate `boot' @@ -318,18 +320,19 @@ and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. + 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" + - the *.tgz files you want to install (as a minimum, base{:--:}OSrev.tgzand + 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. sun4m or sun4c) + - an OpenBSD kernel, most likely "/bsd" All these pieces, except "/boot" and the GNU utilities are supplied in the OpenBSD/MACHINE distribution. @@ -348,7 +351,7 @@ partition sizes. Here is an example layout: 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). +(OpenBSD's filesystem format is almost identical to SunOS). sunos# newfs /dev/rsd0a [... lots of output] @@ -385,7 +388,7 @@ The installboot man page says to do something like this: 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 + 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 -) @@ -409,6 +412,96 @@ course :-) Now proceed to reboot the machine and the customize your installation. +Installing from Solaris: + +You need a machine running under Solaris to install OpenBSD. You will +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) Solaris binary +- a boot block file from a Solaris machine that matches your machine type, + for ufs filesystem, such as /usr/platform/`uname -i`/lib/fs/ufs/bootblk +- an OpenBSD kernel, most likely "/bsd" + +All these pieces, except the boot block and the GNU utilities are supplied +in the OpenBSD/MACHINE distribution. + +You need to format and partition the disk using Solaris (since +OpenBSD/MACHINE uses Sun compatible disk labels.) Give yourself adequate +partition sizes. Here is an example layout: + + solaris# prtvtoc -s /dev/rdsk/c0t1d0s2 + * First Sector Last + * Partition Tag Flags Sector Count Sector Mount Directory + 0 2 00 0 80000 79999 / + 1 3 01 80000 256000 335999 + 2 5 00 0 4165271 4165270 + 3 7 00 336000 100000 435999 /tmp + 4 7 00 436000 100000 535999 /var + 5 7 00 536000 400000 935999 /var/tmp + 6 4 00 936000 3229271 4165270 /usr + +Use Solaris to newfs the partitions which will have filesystems on them. +(OpenBSD's filesystem format is almost identical to Solaris). + + solaris# newfs /dev/rdsk/c0t1d0s0 + [... lots of output] + +Repeat for any other partition (in this example, /dev/rdsk/c0t1d0s3, +/dev/rdsk/c0t1d0s4, /dev/rdsk/c0t1d0s5 and /dev/rdsk/c0t1d0s6). + +dnl XXX I had no time to check the -O restriction is still necessary. +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 Solaris boot +blocks do not understand the extended 4.4BSD filesystem format. + +Mount those partitions in a tree formation, under /mnt; ie: + + solaris# df -k + Filesystem kbytes used avail capacity Mounted on + [...] + /dev/dsk/c0t1d0s0 38427 0 38427 0% /mnt + /dev/dsk/c0t1d0s3 48249 0 48249 0% /mnt/tmp + /dev/dsk/c0t1d0s4 48249 0 48249 0% /mnt/var + /dev/dsk/c0t1d0s5 193536 0 193536 0% /mnt/var/tmp + /dev/dsk/c0t1d0s6 1564024 0 1564024 0% /mnt/usr + +Place the boot block in /mnt (your new root partition), and use the Solaris +command "installboot" to make it work. +The installboot man page says to do something like this: + + solaris# cp /usr/platform/`uname -i`/lib/fs/ufs/bootblk /mnt/bootblk + solaris# sync; sync + solaris# /usr/sbin/installboot /mnt/bootblk /dev/rdsk/c0t1d0s0 + +You can now extract the provided "*.tgz files onto your disk. + + solaris# 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 + solaris{:-#-:} gunzip < base{:--:}OSrev.tgz | (cd /mnt; tar xvpf -) + [...] for each set + +And finally copy an OpenBSD kernel (either bsd or bsd.scsi3) onto your disk. + + solaris# cp bsd.scsi3 /mnt/bsd + +The GNU gunzip program is not distributed as part of Solaris, but may be +present in your /usr/local/bin. If not, you will need to obtain it from a +GNU archive and install before proceeding. + +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 diff --git a/distrib/notes/sparc/xfer b/distrib/notes/sparc/xfer index 9b4dd432d39..53ad8768843 100644 --- a/distrib/notes/sparc/xfer +++ b/distrib/notes/sparc/xfer @@ -12,11 +12,11 @@ work only with the floppy or the miniroot installation. If you have the OpenBSD CD-ROM distribution (and a CD-ROM drive), you may be able boot from it. Not all sparc systems support booting from -CD-ROM and the current boot images is only known to work on sun4c and +CD-ROM and the current boot image is only known to work on sun4c and some sun4m architecture workstations. If you can boot from the CD-ROM, you are home free and can proceed to the installation steps. If not, you will need to do some setup work to prepare a bootable image, either -a floppy, hard drive, or compatible net boot server. +a floppy, hard drive, tape, or compatible net boot server. In addition to the bootable image, you also need to consider how to access the binary distribution sets to actually install the system. If @@ -34,7 +34,7 @@ OpenBSDXferFloppyFromDOS OpenBSDXferFloppyFromUNIX -Creating a bootable hard disk using SunOS or other Un*x-like system: +Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system: If you don't have a floppy drive you can copy the floppy installation image "floppy{:--:}OSrev.fs" or the mini-root "miniroot{:--:}OSrev.fs" @@ -52,11 +52,14 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. - Under SunOS, the command would be: - + The command would likely be, under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rsd0b bs=36b - or - dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b + and under Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0t0d0s1 bs=36b + - or - + dd if=miniroot{:--:}OSrev.fs of=/dev/rdsk/c0t0d0s1 bs=36b 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 @@ -80,8 +83,10 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: completed the installation process. To copy the floppy image to the whole disk, overwriting labels: - + Under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=36b + and under Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0tXd0s2 bs=36b Two notes - X should be replaced by the unit number of the target disk, which is most likely *not* the disk/partition that's your @@ -91,16 +96,19 @@ Creating a bootable hard disk using SunOS or other Un*x-like system: 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 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. + SunOS or Solaris, use format(8/1M) and newfs(8/1M) 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 floppy image to the hard disk, preserving SunOS, Solaris, NetBSD or OpenBSD labels: - + Under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=1b skip=1 seek=1 + and Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0tXd0s2 \ + bs=1b skip=1 seek=1 You need to be sure that your version of dd(1) supports the skip and seek operands, otherwise you can try a technique like: diff --git a/distrib/notes/sparc64/install b/distrib/notes/sparc64/install index 03579043a1b..f485b42fa66 100644 --- a/distrib/notes/sparc64/install +++ b/distrib/notes/sparc64/install @@ -16,6 +16,9 @@ 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 Solaris +system, using the system tools, as well as gunzip; see ``Installing from +Solaris'' below. Booting from the Installation Media: @@ -73,7 +76,6 @@ partition naming a=0, b=1... ok boot disk1:b bsd # example - scsi target 1 or # second ide drive -dnl Change wording if miniroot available During the boot, the kernel might not be able to determine by itself which device it has been booted from. In this case, it will ask you for the root and swap devices. Answer the device and partition you @@ -91,7 +93,8 @@ 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) and -the Sun System/Networks administrators guide constitute a good start). +the Sun System/Networks administrators guide constitute a good start; +on Solaris systems, share(1M) is a good starting point as well). Boot your workstation from the server by entering the appropriate `boot' @@ -254,6 +257,95 @@ and add "local" to the end of the tty configuration line, and run 'ttyflags -a' to put your changes into effect. +Installing from Solaris: + +You need a machine running under Solaris to install OpenBSD. You will +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) Solaris binary + - a boot block file from a Solaris machine that matches your machine type, + for ufs filesystem, such as /usr/platform/`uname -i`/lib/fs/ufs/bootblk + - an OpenBSD kernel + +All these pieces, except the boot block and the GNU utilities are supplied +in the OpenBSD/MACHINE distribution. + +You need to format and partition the disk using Solaris (since +OpenBSD/MACHINE uses Sun compatible disk labels.) Give yourself adequate +partition sizes. Here is an example layout: + + solaris# prtvtoc -s /dev/rdsk/c0t1d0s2 + * First Sector Last + * Partition Tag Flags Sector Count Sector Mount Directory + 0 2 00 0 80000 79999 / + 1 3 01 80000 256000 335999 + 2 5 00 0 4165271 4165270 + 3 7 00 336000 100000 435999 /tmp + 4 7 00 436000 100000 535999 /var + 5 7 00 536000 400000 935999 /var/tmp + 6 4 00 936000 3229271 4165270 /usr + +Use Solaris to newfs the partitions which will have filesystems on them. +(OpenBSD's filesystem format is almost identical to Solaris). + + solaris# newfs /dev/rdsk/c0t1d0s0 + [... lots of output] + +Repeat for any other partition (in this example, /dev/rdsk/c0t1d0s3, +/dev/rdsk/c0t1d0s4, /dev/rdsk/c0t1d0s5 and /dev/rdsk/c0t1d0s6). + +dnl XXX I had no time to check the -O restriction is still necessary. +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 Solaris boot +blocks do not understand the extended 4.4BSD filesystem format. + +Mount those partitions in a tree formation, under /mnt; ie: + + solaris# df -k + Filesystem kbytes used avail capacity Mounted on + [...] + /dev/dsk/c0t1d0s0 38427 0 38427 0% /mnt + /dev/dsk/c0t1d0s3 48249 0 48249 0% /mnt/tmp + /dev/dsk/c0t1d0s4 48249 0 48249 0% /mnt/var + /dev/dsk/c0t1d0s5 193536 0 193536 0% /mnt/var/tmp + /dev/dsk/c0t1d0s6 1564024 0 1564024 0% /mnt/usr + +Place the boot block in /mnt (your new root partition), and use the Solaris +command "installboot" to make it work. +The installboot man page says to do something like this: + + solaris# cp /usr/platform/`uname -i`/lib/fs/ufs/bootblk /mnt/bootblk + solaris# sync; sync + solaris# /usr/sbin/installboot /mnt/bootblk /dev/rdsk/c0t1d0s0 + +You can now extract the provided "*.tgz files onto your disk. + + solaris# ls -FC + base{:--:}OSrev.tgz etc{:--:}OSrev.tgz misc{:--:}OSrev.tgz xserv{:--:}OSrev.tgz + bsd game{:--:}OSrev.tgz xbase{:--:}OSrev.tgz xshare{:--:}OSrev.tgz + comp{:--:}OSrev.tgz man{:--:}OSrev.tgz xfont{:--:}OSrev.tgz + solaris{:-#-:} gunzip < base{:--:}OSrev.tgz | (cd /mnt; tar xvpf -) + [...] for each set + +And finally copy the OpenBSD kernel onto your disk. + + solaris# cp bsd /mnt/bsd + +The GNU gunzip program is not distributed as part of Solaris, but may be +present in your /usr/local/bin. If not, you will need to obtain it from a +GNU archive and install before proceeding. + +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: diff --git a/distrib/notes/sparc64/xfer b/distrib/notes/sparc64/xfer index a4e0909cb09..0a377916b45 100644 --- a/distrib/notes/sparc64/xfer +++ b/distrib/notes/sparc64/xfer @@ -28,11 +28,11 @@ dnl the target system's disk. OpenBSDXferFloppyFromDOS -OpenBSDXferFloppyFromUnix +OpenBSDXferFloppyFromUNIX dnl XXX make sure to adapt text, especially examples, once miniroot dnl is available as well. -Creating a bootable hard disk using SunOS or other Un*x-like system: +Creating a bootable hard disk using SunOS, Solaris or other Un*x-like system: dnl If you don't have a floppy drive you can copy the floppy dnl installation image "floppy{:--:}OSrev.fs" or the mini-root "miniroot{:--:}OSrev.fs" @@ -56,11 +56,14 @@ dnl single user mode), and then booting from that partition. which have a compatible view of SunOS disk labels and partitions. Use the dd(1) utility to copy the file to the hard drive. - Under SunOS, the command would be: - + The command would likely be, under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rsd0b bs=36b dnl - or - dnl dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b + and under Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/c0t0d0s1 bs=36b +dnl - or - +dnl dd if=miniroot{:--:}OSrev.fs of=/dev/c0t0d0s1 bs=36b 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 @@ -83,10 +86,22 @@ dnl dd if=miniroot{:--:}OSrev.fs of=/dev/rsd0b bs=36b create a "fictitious label" that will let you access the whole disk. + 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 actually runs off a ram-disk image in the kernel. +dnl XXX uncomment end of paragraph once miniroot available +dnl since it actually runs off a ram-disk image in the kernel. In +dnl contrast the miniroot is a normal unix root filesystem and you +dnl must place in a partition that will not be overwritten until you've +dnl completed the installation process. + To copy the floppy image to the hard disk, preserving SunOS, Solaris, NetBSD or OpenBSD labels: - + Under SunOS: dd if=floppy{:--:}OSrev.fs of=/dev/rsdXc bs=1b skip=1 seek=1 + and Solaris: + dd if=floppy{:--:}OSrev.fs of=/dev/rdsk/c0tXd0s2 \ + bs=1b skip=1 seek=1 You need to be sure that your version of dd(1) supports the skip and seek operands, otherwise you can try a technique like: @@ -116,15 +131,8 @@ Creating a network bootable setup using SunOS or other Un*x-like system: OpenBSDXferPrelude -The floppy installation allows installing OpenBSD directly from FTP -mirror sites over the internet, however you must consider the speed and -reliability of your internet connection for this option. It may save -much time and frustration to use ftp get/reget to transfer the -distribution sets to a local server or disk and perform the installation -from there, rather than directly from the internet. - -OpenBSDXferBareTape +OpenBSDXferBareTape(xbase xfont xserv xshare) OpenBSDXferNFS diff --git a/distrib/notes/sun3/install b/distrib/notes/sun3/install index 3eb1acf35df..4ef6c99a545 100644 --- a/distrib/notes/sun3/install +++ b/distrib/notes/sun3/install @@ -11,8 +11,8 @@ 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). +system, using the system tools, as well as gnu tar and gunzip (see +``Installing from SunOS'' below). Booting from the Installation Media: @@ -53,7 +53,8 @@ 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) and -the Sun System/Networks administrators guide constitute a good start). +the Sun System/Networks administrators guide constitute a good start; +on Solaris systems, share(1M) is a good starting point as well). Boot your workstation from the server by entering the appropriate `boot' command at the monitor prompt. Depending on the ethernet chip in your @@ -225,12 +226,12 @@ 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 machine (not sun3x!) - a kernel, most likely "/bsd" + - 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 machine (not sun3x!) + - an OpenBSD kernel All these pieces, except "/boot" and the GNU utilities are supplied in the OpenBSD/MACHINE distribution. @@ -286,9 +287,8 @@ The installboot man page says to do something like this: 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 - game{:--:}OSrev.tgz xbase{:--:}OSrev.tgz + base{:--:}OSrev.tgz comp{:--:}OSrev.tgz game{:--:}OSrev.tgz misc{:--:}OSrev.tgz + bsd etc{:--:}OSrev.tgz man{:--:}OSrev.tgz sunos{:-#-:} gunzip < base{:--:}OSrev.tgz | (cd /mnt; gtar xvpf -) [...] for each set @@ -310,6 +310,7 @@ course :-) Now proceed to reboot the machine and the customize your installation. + Net Boot or Diskless Setup Information: The setup is similar to SunOS diskless setup, but not identical, because |