diff options
Diffstat (limited to 'distrib/notes/sparc/install')
| -rw-r--r-- | distrib/notes/sparc/install | 86 |
1 files changed, 43 insertions, 43 deletions
diff --git a/distrib/notes/sparc/install b/distrib/notes/sparc/install index 95bf439d384..ca3f2496b1d 100644 --- a/distrib/notes/sparc/install +++ b/distrib/notes/sparc/install @@ -1,18 +1,18 @@ -Installing NetBSD is a relatively complex process, but if you have +Installing OpenBSD is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. -There are several ways to install NetBSD onto a disk. If your Sparcstation +There are several ways to install OpenBSD onto a disk. If your Sparcstation is hooked up in a network you can find find a server and arrange for a diskless setup which is a convenient way to install on a machine with a single disk attached. Alternatively, you could use SunOS (booted from -a local disk) and install NetBSD onto a second disk. For the latter method, +a local disk) and install OpenBSD onto a second disk. For the latter method, skip to the section "Installing from SunOS" below. Installing using a diskless setup. First, you must setup a diskless client configuration on a server. If -you are using a NetBSD system as the boot-server, have a look at the +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 @@ -27,7 +27,7 @@ address 130.115.144.11, will make an TFTP request for `8273900B.SUN4C'. Normally, this file is 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 NetBSD/sparc +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 @@ -42,16 +42,16 @@ Here's an example to illustrate this whole mess: else server# set SKIP=0 server# set KARCH=SUN4C - server# dd if=boot of=/tftpboot/boot.sparc.netbsd.$KARCH skip=$SKIP bs=32 + server# dd if=boot of=/tftpboot/boot.sparc.bsd.$KARCH skip=$SKIP bs=32 server# cd /tftpboot - server# ln -s boot.sparc.netbsd.$KARCH 8273900B.$KARCH + server# ln -s boot.sparc.bsd.$KARCH 8273900B.$KARCH Note: some versions of Openboot ROMs (sun4c) seem to require that the boot program size is nicely rounded. Therefore it may be necessary to strip(8) off the symbol table. -As noted above in the section `Preparing your System for NetBSD Installation', +As noted above in the section `Preparing your System for OpenBSD Installation', you have several options when choosing a location to store the installation filesets. However, the easiest way is to put the *.tar.gz files you want to install into the root directory for your client on the server. @@ -61,7 +61,7 @@ directory for your machine. If you elect to use a separately NFS-mounted filesystem for `/usr' with your diskless setup, make sure the "./usr" base files in base.tar.gz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing <root>/usr to -your server's exported NetBSD "/usr" directory. Also put the kernel and the +your server's exported OpenBSD "/usr" directory. Also put the kernel and the install/upgrade scripts into the root directory. A few configuration files need to be edited: @@ -77,7 +77,7 @@ 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.netbsd /usr nfs rw 0 0 + server:/export/exec/sun4.bsd /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' @@ -85,19 +85,19 @@ 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 NetBSD. However, you may want to correct them +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 NetBSD machine once it has booted. +MAKEDEV on your OpenBSD machine once it has booted. 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: - > b le()netbsd -s # for sun4 monitors - ok boot le()netbsd -s # for version 1 OpenBOOT ROMs - ok boot net netbsd -s # for version 2 OpenBOOT ROMs + > b le()bsd -s # for sun4 monitors + ok boot le()bsd -s # for version 1 OpenBOOT ROMs + ok boot net bsd -s # for version 2 OpenBOOT ROMs -This will boot the NetBSD kernel in single-user mode. +This will boot the OpenBSD kernel in single-user mode. [[ NOTE: the latter two examples assume you operate the OpenBOOT ROM in @@ -112,13 +112,13 @@ instead of `ok', type: If you use a diskless setup with a separately NFS-mounted /usr filesystem, mount /usr by hand now: -netbsd# mount /usr +openbsd# mount /usr At this point, it's worth checking the disk label and partition sizes on -the disk you want to install NetBSD onto. NetBSD understands SunOS-style +the disk you want to install OpenBSD onto. OpenBSD understands SunOS-style disklabels, so if your disk was previously used by SunOS there will be a usable label on it. Use `disklabel -e <disk>' (where <disk> is the -device name assigned by the NetBSD kernel, e.g. `sd0') to view and +device name assigned by the OpenBSD kernel, e.g. `sd0') to view and modify the partition sizes. A comfortable size for the root filesystem partition is about 20MB; a good initial size for the swap partition is twice the amount of physical memory in your machine (though, unlike @@ -128,7 +128,7 @@ takes about 60MB in `/usr'. Make all your partitions start and end on cylinder boundaries. NOTE: if you are installing on a SCSI disk that does *not* have a SunOS -or NetBSD label on it, you may still be able to use disklabel(8) but you'll +or OpenBSD label on it, you may still be able to use disklabel(8) but you'll have to create all partitions from scratch. If your disk is listed in `/etc/disktab', you may use the entry (which in most cases only defines a `c' partition to describe the whole disk) to put an initial label on @@ -156,7 +156,7 @@ the editor), then try setting it to `8 partitions:'. <BEGIN SAMPLE DISKLABEL SCREEN> -netbsd# disklabel sd2 +openbsd# disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk @@ -184,13 +184,13 @@ drivedata: 0 <END SAMPLE DISKLABEL SCREEN> -If you are upgrading a NetBSD installation, start the upgrade script: +If you are upgrading a OpenBSD installation, start the upgrade script: -netbsd# sh upgrade.sh +openbsd# sh upgrade.sh else, start the installation script: -netbsd# sh install.sh +openbsd# sh install.sh These scripts will do most of the work of transferring the system from the @@ -204,42 +204,42 @@ have been identified by the kernel. The installation script goes through the following phases: - - determination of the disk to install NetBSD on + - determination of the disk to install OpenBSD on - checking of the partition information on the disk - - creating and mounting the NetBSD filesystems + - creating and mounting the OpenBSD filesystems - setup of IP configuration - extraction of the distribution tar files - installation of boot programs Now try a reboot. (If needed, swap your scsi id's first). Initially -I'd suggest you "boot sd()netbsd -bs", then try multiuser after that. -if you boot single-user the NetBSD incantation to make the root +I'd suggest you "boot sd()bsd -bs", then try multiuser after that. +if you boot single-user the OpenBSD incantation to make the root filesystem writable is - netbsd# mount -u /dev/sd0a / + openbsd# mount -u /dev/sd0a / The Sun monitor normally tries to load a file called "vmunix". On -OpenBOOT ROM systems you can change it to load NetBSD instead using +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)netbsd + ok setenv boot-from sd(0,0,0)bsd ok On version 2 OpenBOOT ROMs: - ok setenv boot-file netbsd + ok setenv boot-file bsd ok setenv boot-device /sbus/esp/sd@0,0 -Congratulations, you have successfully installed NetBSD RELEASE. When you -reboot into NetBSD, you should log in as "root" at the login prompt. +Congratulations, you have successfully installed OpenBSD RELEASE. When you +reboot into OpenBSD, you should log in as "root" at the login prompt. There is no initial password, but if you're using the machine in a networked environment, you should create yourself an account and protect it and the "root" account with good passwords. -Some of the files in the NetBSD RELEASE distribution might need to be +Some of the files in the OpenBSD RELEASE distribution might need to be tailored for your site. In particular, the /etc/sendmail.cf file will almost definitely need to be adjusted, and other files in /etc will probably need to be modified. If you are unfamiliar with UN*X-like @@ -250,7 +250,7 @@ discusses it. Installing from SunOS. -You need a SunOS machine to install NetBSD. You also need at +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) @@ -259,13 +259,13 @@ least the following pieces: 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 "/netbsd" + a kernel, most likely "/bsd" -All these pieces, except "/boot", are supplied in the NetBSD/sparc +All these pieces, except "/boot", are supplied in the OpenBSD/sparc distribution. You need to format and partition the disk using SunOS (since -NetBSD/sparc uses SunOS disk labels.) Give yourself adequate +OpenBSD/sparc uses SunOS disk labels.) Give yourself adequate partition sizes. Here is an example layout: partition size offset will be.. @@ -275,10 +275,10 @@ partition sizes. Here is an example layout: sd2g 160230 44310 /usr BTW, These are not recommended sizes. They simply match the first -(tiny) disk that NetBSD/sparc ran on. +(tiny) disk that OpenBSD/sparc ran on. Use SunOS to newfs the partitions which will have filesystems on them. -(NetBSD's filesystem format is identical to SunOS). +(OpenBSD's filesystem format is identical to SunOS). sunos# newfs /dev/rsd2a [... lots of output] @@ -286,7 +286,7 @@ Use SunOS to newfs the partitions which will have filesystems on them. [... lots of output] NOTE: If you are able to, there is a performance benefit from -newfs'ing using NetBSD. If you newfs using the NetBSD newfs command, +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 @@ -313,7 +313,7 @@ provided script, "install_from_sunos.sh" will help you: sunos# ls -FC base.tar.gz etc.tar.gz man.tar.gz secr.tar.gz comp.tar.gz games.tar.gz misc.tar.gz text.tar.gz - install.sh netbsd.id3_scsi + install.sh bsd.id3_scsi sunos# ./install_from_sunos.sh [...] |