.\" $NetBSD: install,v 1.4 2000/10/29 14:08:10 lukem Exp $ .\" .\" Copyright (c) 1999, 2000 The NetBSD Foundation, Inc. .\" All rights reserved. .\" .\" Redistribution and use in source and binary forms, with or without .\" modification, are permitted provided that the following conditions .\" are met: .\" 1. Redistributions of source code must retain the above copyright .\" notice, this list of conditions and the following disclaimer. .\" 2. Redistributions in binary form must reproduce the above copyright .\" notice, this list of conditions and the following disclaimer in the .\" documentation and/or other materials provided with the distribution. .\" 3. All advertising materials mentioning features or use of this software .\" must display the following acknowledgement: .\" This product includes software developed by the NetBSD .\" Foundation, Inc. and its contributors. .\" 4. Neither the name of The NetBSD Foundation nor the names of its .\" contributors may be used to endorse or promote products derived .\" from this software without specific prior written permission. .\" .\" THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS .\" ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED .\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR .\" PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS .\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR .\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF .\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS .\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE .\" POSSIBILITY OF SUCH DAMAGE. .\" . Installing .Nx is a relatively complex process, but if you have this document in hand it shouldn't be too much trouble. .Pp There are several ways to install .Nx onto a disk. The easiest way in terms of preliminary setup is to use the .Nx miniroot that can be booted off your local disk's swap partition. Alternatively, if your UltraSPARC is hooked up in a network you can find a server and 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 (see the section `Installing .Nx by using a diskless setup' below). . .Ss2 Installing NetBSD by using the NetBSD miniroot . The miniroot is a self-contained .Nx file system holding all utilities necessary to install .Nx on a local disk. It is distributed as a plain file designed to be transferred to a raw disk partition from which it can be booted using the appropriate OpenBoot PROM command. Usually, the miniroot will be loaded into the swap partition of a disk. If needed, you can use any other unused partition, but remember that the partition will then not available during the installation process. .Pp Loading the miniroot onto your raw partition is simple. On .Nx as well as .Tn Solaris you use a command like: .Pp .Dl # Ic "dd if=miniroot.fs of=/dev/rdsk/c0t0d0s1 bs=4k conv=sync" .Pp (Here, .Li /dev/rdsk/c0t0d0s1 is assumed to be your swap partition.) There's a potential problem here if .Pa /dev/rdsk/c0t0d0s1 is actually in use as a swap partition by your currently running system. If you don't have another disk or partition to spare, you can usually get away with running this command anyway after first booting into single-user mode to ensure a quiet system. .Pp After transferring the miniroot to disk, bring the system down by: .Pp .Dl # Ic halt .Pp Then boot the miniroot by typing the appropriate command at the OpenBoot PROM: .Pp .Dl ok Ic "boot disk:b netbsd -s" .Pp If you've loaded the miniroot onto some other disk than .Li sd0 adapt the boot specifier accordingly, e.g.: .Pp .Dl ok Ic "boot disk1:b netbsd -s" .Pp The monitor boot command will cause the .Nx kernel contained in the miniroot image to be booted. After the initial probe messages you'll be asked to start the install or upgrade procedure. Proceed to the section .Sx Running the installation scripts below. . .Ss2 Installing NetBSD by using a diskless setup . First, you must setup a diskless client configuration on a server. If you are using a .Nx system as the boot-server, have a look at the .Xr 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 .Tn SunOS systems, .Xr add_client 8 is a good start.) .Pp Your SPARCstation 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 .Sq "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 .Pa 8273900B.SUN4U . 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 .Pa /usr/mdec/ofwboot.net in the .Nx*M distribution. .(Note The .Pa /usr/mdec/ofwboot does not know about netbooting. .Note) .Pp After the boot program has been loaded into memory and given control by the OpenBoot PROM, it starts locating the machine's remote root directory through the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the local net. The answer to this request (if it comes in) contains the client's name. This name is used in next step, a BOOTPARAM GETFILE request - sent to the server that responded to the WHOAMI request - requesting the name and address of the machine that will serve the client's root directory, as well as the path of the client's root on that server. .Pp Finally, this information (if it comes in) is used to issue a REMOTE MOUNT request to the client's root file system server, asking for an NFS file handle corresponding to the root file system. If successful, the boot program starts reading from the remote root file system in search of the kernel which is then read into memory. .Pp As noted above in the section .Sx Preparing your System for Nx Installation you have several options when choosing a location to store the installation filesets. However, the easiest way is to put the .Pa *.tgz files you want to install into the root directory for your client on the server. .Pp Next, unpack .Pa base.tgz and .Pa etc.tgz on the server in the root directory for your machine. If you elect to use a separately NFS-mounted file system for .Pa /usr with your diskless setup, make sure the .Pa ./usr base files in .Pa base.tgz end up in the correct location. One way to do this is to temporarily use a loopback mount on the server, re-routing .Ar root Ns Pa /usr to your server's exported .Nx .Pa /usr directory. Also put the kernel and the install/upgrade scripts into the root directory. .Pp A few configuration files need to be edited: .(tag indent .It Ar root Ns Pa /etc/hosts Add the IP addresses of both server and client. .It Ar root Ns Pa /etc/myname This files contains the client's hostname; use the same name as in \*/etc/hosts. .It Ar root Ns Pa /etc/fstab Enter the entries for the remotely mounted file systems. For example: .Pp .Dl server:/export/root/client / nfs rw 0 0 .Dl server:/export/exec/sun4u.netbsd /usr nfs rw 0 0 .tag) .Pp Now you must populate the .Pa /dev directory for your client. If your server runs .Tn SunOS 4.x, you can simply change your working directory to .Ar root Ns Pa /dev and run the MAKEDEV script: .Ic sh MAKEDEV all . .Pp On .Tn Solaris systems, .Ic 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 .Nx . However, you may want to correct them if you plan to use the diskless setup regularly. In that case, you may re-run .Ic MAKEDEV on your .Nx machine once it has booted. .Pp Boot your workstation from the server by entering the appropriate .Ic boot command at the monitor prompt. Depending on the OpenBoot PROM version in your machine, this command takes one of the following forms: .Pp .Dl "ok boot net netbsd -s" .Pp This will boot the .Nx kernel in single-user mode. .Pp If you use a diskless setup with a separately NFS-mounted .Pa /usr file system, mount .Pa /usr by hand now: .Pp .Dl netbsd# Ic "mount /usr" .Pp .(Note For miniroot installs, the text editor is vi. .Note) .Pp When using .Xr disklabel 8 to edit disklabels the -e switch will invoke the editor on the label. The -i switch will run an interactive session. .Pp At this point, it's worth checking the disk label and partition sizes on the disk you want to install .Nx onto. .Nx understands .Tn SunOS Ns No -style disklabels, so if your disk was previously used by .Tn SunOS there will be a usable label on it. Use .Ic "disklabel -e \*" or .Ic "disklabel -i \*" (where .Em \* is the device name assigned by the .Nx kernel, e.g. .Li sd0 ) to view and modify the partition sizes. See the section .Sx Preparing your System for Nx Installation above for suggestions about disk partition sizes. .Pp If you are installing on a SCSI disk that does .Em not have a .Tn SunOS or .Nx label on it, you may still be able to use .Xr disklabel 8 but you'll have to create all partitions from scratch. If your disk is listed in .Pa /etc/disktab , you may use the entry (which in most cases only defines a .Sq Li c partition to describe the whole disk) to put an initial label on the disk. Then proceed with .Ic "disklabel -e \*" .Ic "disklabel -i \*" to create a partition layout that suits your needs. .(Note Because of the built-in compatibility with .Tn SunOS Ns No -style labels, .Em "Always make sure all your partitions start and end on cylinder boundaries." .Note) .Pp Here follows an example of what you'll see while in the dislabel editor. Do not touch any of the parameters except for the .Sq Li label: entry and the actual partition size information at the bottom (the lines starting with .Sq Li a: , .Sq Li b: , ...). .Pp The size and offset fields are given in sector units. Be sure to make these numbers multiples of the of the number of sectors per cylinder: the kernel might be picky about these things, but aside from this you'll have the least chance of wasting disk space. Partitions on which you intend to have a mountable file system, should be given fstype .Li 4.2BSD . Remember, the .Sq Li c partition should describe The whole disk and typically does not require editing. The .Sq Li "(Cyl. x - y)" info that appears after the hash .Sq Li # character is treated as a comment and need not be filled in when altering partitions. .(Note The line containing .Sq Li "8 partitions:" is best left alone, even if you define less then eight partitions. If this line displays a different number and the program complains about it (after you leave the editor), then try setting it to .Sq Li "8 partitions:" . .Note) . .Ss2 Sample disklabel screen .(disp netbsd# disklabel sd2 # /dev/rsd2c: type: SCSI disk: SCSI disk label: Hold Your Breath flags: bytes/sector: 512 sectors/track: 64 tracks/cylinder: 7 sectors/cylinder: 448 cylinders: 1429 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsz bsz cpg] a: 50176 0 4.2BSD 0 0 0 # (Cyl. 0 - 111) b: 64512 50176 swap # (Cyl. 112 - 255) c: 640192 0 unknown # (Cyl. 0 - 1428) d: 525504 114688 4.2BSD 0 0 0 # (Cyl. 256 - 1428) .disp) .Pp To begin installation or the upgrade procedure, run sysinst: .Pp .Dl netbsd# Ic sysinst . .Ss2 Running sysinst . The sysinst program will do most of the work of transferring the system from the distribution sets onto your disk. You will frequently be asked for confirmation before sysinst proceeds with each phase of the installation process. .Pp Occasionally, you will have to provide a piece of information such as the name of the disk you want to install on or IP addresses and domain names you want to assign. If your system has more than one disk, you may want to look at the output of the .Xr dmesg 8 command to see how your disks have been identified by the kernel. .Pp The installation script goes through the following phases: .(bullet determination of the disk to install .Nx on .It checking of the partition information on the disk .It setting of the local timezone .It creating and mounting the .Nx file systems .It setup of IP configuration .It extraction of the distribution tar files .It installation of boot programs .bullet) .Pp Now try a reboot. Initially we'd suggest you .Ic "boot netbsd -bs" , then try multiuser after that. If you boot single-user the .Nx incantation to make the root file system .Pq Pa / writable is .Pp .Dl netbsd# Ic "mount -u /dev/sd0a /" .Pp .Em Congratulations , you have successfully installed .Nx \*V.