Resource
|
Name |
Description |
| File System |
file |
Required. The file resource is a handle for
a file system to be installed on the client. There are two
required file system resources: /boot and / (the root file
system). Other file systems can be local (ext2) or NFS mounted,
read/only or read/write. The file resources allocated to clients
should relate to entries in the disk partition table resource
— see the description below of the disk resource
.
|
| Installation
ramdisk |
ramdisk |
Optional.
The installation ramdisk is used to bring up devices during
installation that the kernel does not support — SCSI is
the typical example. |
| Disk
partition table |
disk |
Required.
A list of entries, one for each file system resource, and one
for swap, that describes the size and type of each file system.
File system partitions may be extended (logical), swap or ext2.
The cub script automatically builds the disk partition
table for you and then displays it, giving you the opportunity
to make any necessary edits. The script assumes that all clients
have the same type of disk — IDE, SCSI, or RAID array.
If you were to build a cluster using LUI without running cub,
you would have to build the disk partition table yourself.
The following disk partition table was created during the
sample installation in Using
cub to Install a Beowulf Cluster:
/dev/ida/c0d0p1 ext2
30 m y /boot
/dev/ida/c0d0p2 extended * m n
/dev/ida/c0d0p5 swap 1000 m
/dev/ida/c0d0p6 ext2 * m n /
|
| Linux
kernel |
kernel |
Optional.
The kernel the node will boot from on its first boot from the
local hard drive. You can install a kernel via the rpm resource
described below, or install a custom kernel via the kernel resource. |
| System
map |
map |
Required.
The kernel map associated with the kernel you are
installing on the client node. The map contains a list of
addresses used if you need to debug the kernel.
|
| Source files |
source |
Optional.
Source resources are files copied from server to client
during the installation process – a good example is /edt/shadow
so that the installed node has shadow passwords. |
| User
exit script |
exit |
Optional.
A script that is run one time, after all services are
brought up, the first time the node is booted from the local
hard drive, but not on subsequent reboots. By the
time the user exit script gains control, the permanent file
system has been mounted and all services should be available. |
| List
of installation RPMs |
rpm |
Required.
A list of RPMs to install on the client node. If you
specify a kernel RPM, and also a kernel resource, the kernel
resource will be installed last and becomes the active kernel
when the node is first booted. |
