This section describes how to start (or boot) the installation program. Once the installation program is running, you will be able to choose from several installation methods. You can choose from the following installation methods: CD-ROM, NFS, hard disk, and FTP. (Note that if the installation program is booted directly from CD-ROM, the installation will automatically proceed from that CD-ROM.)
There are two different ways an UltraPenguin installation can be started:
If your SPARC system has a fully Sun-supported CD-ROM drive, you can boot directly from the UltraPenguin CD-ROM. For SPARC systems with a PROM version of 2.0 or better, use the following command when in new command mode:
SPARC systems with PROM versions less than 2.0 may not be able to boot from a CD-ROM at all. Theoretically, if your SPARC system has a CD-ROM at SCSI id 6, the following command should boot the UltraPenguin installation program:
Note that using an NFS-mounted root after booting from CD-ROM is not supported, as the filesystem on the UltraPenguin CD-ROM performs the same function as an NFS-mounted root. Therefore, no additional boot command arguments should be given for CD-ROM boots.
There are two types of network boots supported by the UltraPenguin installation program:
While booting your SPARC system from the network is fairly straightforward, there are several requirements:
If you are going to use
rarp, please refer to the previous section
which describes how to use an NFS-mounted root.
If you are going to set up a TFTP server on an UltraPenguin system,
simply install the latest
tftp package using RPM, and make sure
the line in
inetd.conf that will run
tftp is uncommented.
Don't forget to
kill -HUP inetd if you needed to make any changes to
Next, you'll need to make a symlink describing the SPARC system to be booted, and pointing to the file from which it should boot. The name of the symlink contains two items:
To convert the more common ``dotted decimal'' IP address into its hex equivalent, convert each of the address' four groups of numbers into hex. If the resulting hex number is only one digit, add a leading zero to it. Then append all four hex numbers together. For example, take the IP address 10.0.2.254. Convert each set of four numbers into hex, and add a leading zero where necessary:
10 = A or 0A 0 = 0 or 00 2 = 2 or 02 254 = FE or FE
Therefore, the IP address 10.0.2.254 in hex is: 0A0002FE.
The second part of the symlink name is the SPARC system's architecture.
For our example, we'll use
SUN4M. The IP address and architecture
are separated by a dot, resulting in this symlink name:
SUN4U architecture, you should call the symlink just by the IP
address in hex, so don't try to put
.SUN4U in there. The filename for
an Ultra box looks like this:
The last step is figuring out what this symlink should point to.
For booting from network with ramdisk, you put the
images/tftpboot.img image onto the TFTP server. This image contains
kernels for both 32bit and 64bit boxes and will autodetect at boot time,
which one to run.
Place the appropriate file in the TFTP server's directory, and create the symlink. In this example, we're using the image that includes a ramdisk:
ln -s tftpboot.img 0A0002FE.SUN4M
Alternately, you can put there the
file, which is kind of swiss army knife for situations when you'll be in
trouble with your 32bit or 64bit SPARC systems. It contains a lot of
programs you can directly use to mend your filesystems, install new things
and stuff like that.
You're now ready to boot. If you're going to boot
simply use the following command (in new command mode):
On the other hand, if you're going to boot from
vmlinux and use an
NFS-mounted root, use this command:
boot net linux nfsroot=nfs.server.IP.address:/path/to/RH/image
nfs.server.ip.address with the NFS server's IP address,
/path/to/RH/image with the path to the exported directory
containing the appropriate UltraPenguin files.
SPARC systems with PROM versions less than 2.0 should use this boot command, appending the usual NFS root argument if required: