The Jumpstart Class File
A class file is a configuration file that specifies how
to partition the disks on a client and what software is
to be installed. The class file is put on the boot server,
which should be local to each department. This allows
the local administrator to configure and reconfigure installations
at will without the assistance of OIT.
The rules file contains only one rule, a wild card
rule matching a class file that will be on the local
boot server, so this file does not have to be changed
for each new installation.
The Class File
The Class file contains information about what software
packages will be installed and how the disks will be
partitioned. This file can be found on your local system
as <bootserver_root>/Solaris_9/config/class.local.
There is a symlink in the same directory named class.default.
You can opt to create your own class file on a per host
basis, named, for example, class.<hostname>. If
you change the class.default link to point to your new
class file it will be used by jumpstart.
Here is the sample class file (class.local)
provided by OIT:
Generic Class file for Solaris 9 servers and workstations.
Installation Directives
The install_type of initial_install means that
the software will be placed on the disks without regard
for existing data. Disks will be formatted, and existing
data will be lost.
install_type
initial_install
The system_type of standalone means that this system
will have a local root disk associated with it and will
boot by itself.
system_type standalone
The partition type "explicit" means we are
providing a partition table in this class file that
should be used rather than the default.
partitioning explicit
Cluster and Package Configuration
In addition to Sun's provided clusters, Boston University
has defined two cluster types, SUNWCbuue and SUNWCbuhs
to offer a more refined and general useful set of software
for the university.
The BU User Environment
(SUNWCbuue)
This cluster is what most people will want for desktop
workstations or servers with real X consoles. It provides
graphical user interface support and applications that
are appropriate for users working on the console.
The BU Headless
Server (SUNWCbuhs)
This is a more stripped down cluster that provides a
version of Solaris that is appropriate for systems without
X consoles, typically things we refer to as servers.
CDE is not installed, nor are some applications that
are not useful without a console. A full development
and user environment is present, so this is a practical
choice for both development and productions systems,
including multiuser systems.
Note that all remote X applications will work,
such as xterm/dtterm.
Which one do I pick?
If you can, pick SUNWCbuhs, because the limited amount
of software will help increase the security of the system.
If you have an X console on the system that you plan
to use, however, you will probably want SUNWCbuue. Reducing
the amount of software, by selecting SUNWbuhs also speeds
up the installation and patching process.
If neither cluster fits your needs you can always install
one of Sun's supplied clusters, such as SUNWCprog. If
you plan to use BU's jumpstart server and Sun cluster,
be sure to include the package SUNWtcsh or you will
not be able to log in after the installation. See Sun's
"Solaris 9: Operating Environment Package List", for
more information on Sun's clusters.
Neither BU developed cluster contains X font server
support, yp (NIS) support, Network Cache Accelerator
software (a special Sun product that is not generally
useful (and may in fact hurt general purpose systems,
Bootserver Prerequisite software (required to install
& setup a remote bootserver for Custom Jumpstart
Installations), Solaris Volume Manager (Disk Suite)
software or CDRW software. If you wish to use this software,
you should uncomment the appropriate lines below.
| X font server package |
| package |
SUNWxwcft |
add |
| package |
SUNWxwfs |
add |
| package |
SUNWxwfnt |
add |
| package |
SUNWxwoft |
add |
| |
|
|
| NIS server software package |
| package |
SUNWypr |
add |
| package |
SUNWypu |
add |
| |
|
|
| Network cache accelerator
product package |
| package |
SUNWncar |
add |
| package |
SUNWncarx |
add |
| package |
SUNWncau |
add |
| package |
SUNWncaux |
add |
| |
|
|
| Boot Server product package |
| (Prerequisite for a Jumpstart
Bootserver) |
| package |
SUNWbsr |
add |
| package |
SUNWbsu |
add |
| package |
SUNWtftp |
add |
| package |
SUNWtftpr |
add |
| |
|
|
| Solaris Volume Manager product
package (Disk Suite) |
| package |
SUNWmdr |
add |
| package |
SUNWmdu |
add |
| package |
SUNWmdx |
add |
| |
|
|
| CDRW product package |
| package |
SUNWcdrw |
add |
| |
|
|
Partitioning Notes
Help! What do I do?
If you are feeling a little bit scared about these configuration
files, you needn't be. First, you can always choose
to use one of our default files, such as the class.default
file contained in this document if it is sufficient
for your needs.
If you have more specific needs, you still needn't
be afraid of the syntax. In fact, it is sufficient for
you to communicate to us how you want the disks partitioned
and we will be happy to create an appropriate class
file for you.
|
 |
