- 论坛徽章:
- 0
|
Installing the configurator Tools
=================================
1) Download the tarball from
http://www.deer-run.com/~hal/jumpstart/configurator/config.tar.Z
2) Unpack the tarball to create a directory called "configurator".
To unpack the tarball:
cd /path/to/inst/dir
zcat /path/to/tarball/config.tar.Z | tar xf -
If you are planning to use the configurator tools as part of a custom
Jumpstart, it works best if the install directory is in the same
partition as your Jumpstart configuration directory.
3) Add an entry to your /etc/dfs/dfstab file to share the configurator
hierarchy:
share -F nfs -o ro,anon=0 /path/to/inst/dir/configurator
4) Run the "shareall" command (as root) to share the new directory.
5) Download the Sun recommended patch clusters for your target machines
from ftp://sunsolve.sun.com/pub/patches and install them in the
configurator/patches directory (see configurator/patches/00README
for further instructions).
6) Place any site-specific configurations files you want installed on
the target platform in the configurator/files directory. This
directory should mirror the OS directory structure, so if you want
configurator to install an /etc/inet/ntp.conf file for you, you
need to put that file in configurator/files/etc/inet (see the
configurator/README file for more information).
7) Place any local packages you want installed in the configurator/packages
directory. You will also need to properly configure the PACKAGES
configuration variable (see configurator/conf/00README)
8) Review the configuration settings in configurator/conf and the
configurator/conf/00README file to see what site-specific configuration
changes may be necessary (and how to perform them). Note that if
you're interested in performing the CIS benchmark operations
(rather than the steps from the "Solaris Security: Step-by-Step" guide,
which is the default), pay close attention to the
configurator/conf/00README.CIS-benchmark file (as well as the CIS-*.conf
files in this directory).
Installing the configurator Tools
=================================
1) Download the tarball from
http://www.deer-run.com/~hal/jumpstart/configurator/config.tar.Z
2) Unpack the tarball to create a directory called "configurator".
To unpack the tarball:
cd /path/to/inst/dir
zcat /path/to/tarball/config.tar.Z | tar xf -
If you are planning to use the configurator tools as part of a custom
Jumpstart, it works best if the install directory is in the same
partition as your Jumpstart configuration directory.
3) Add an entry to your /etc/dfs/dfstab file to share the configurator
hierarchy:
share -F nfs -o ro,anon=0 /path/to/inst/dir/configurator
4) Run the "shareall" command (as root) to share the new directory.
5) Download the Sun recommended patch clusters for your target machines
from ftp://sunsolve.sun.com/pub/patches and install them in the
configurator/patches directory (see configurator/patches/00README
for further instructions).
6) Place any site-specific configurations files you want installed on
the target platform in the configurator/files directory. This
directory should mirror the OS directory structure, so if you want
configurator to install an /etc/inet/ntp.conf file for you, you
need to put that file in configurator/files/etc/inet (see the
configurator/README file for more information).
7) Place any local packages you want installed in the configurator/packages
directory. You will also need to properly configure the PACKAGES
configuration variable (see configurator/conf/00README)
8) Review the configuration settings in configurator/conf and the
configurator/conf/00README file to see what site-specific configuration
changes may be necessary (and how to perform them). Note that if
you're interested in performing the CIS benchmark operations
(rather than the steps from the "Solaris Security: Step-by-Step" guide,
which is the default), pay close attention to the
configurator/conf/00README.CIS-benchmark file (as well as the CIS-*.conf
files in this directory).
Running configurator By Hand
============================
1) Install a new OS from CD-ROM on the target machine.
2) Mount the configurator tree onto /mnt via NFS (if you use a different
mount point, you will need to change the value of $CONFROOT at the
top of the configurator script).
3) Run /mnt/bin/configurator
4) reboot -- -r
Running configurator Via Jumpstart
==================================
NOTE: This section assumes that the administrator has familiarity with
the basic Jumpstart process and that a properly configured Jumpstart
environment (with Boot, Config, and Install servers) is available.
For more information on the Jumpstart process, see the "Solaris Advanced
Installation Guide" (available from http://docs.sun.com) and/or
http://www.deer-run.com/~hal/Jumpstart.pdf
1) Edit the configurator/bin/config-trig script and verify that the
variables at the top of the script are set appropriately for your
platform. In particular, make sure that the value of $MOUNTPT
from config-trig matches the value of $CONFROOT in the configurator
script.
2) Copy (or link) the config-trig script into your Jumpstart configuration
directory (the place where your rules file and system profile files
live).
3) Edit the rules file in your Jumpstart configuration directory and
add the config-trig script as a custom post-install script for the
appropriate rules. A sample entry might look like
network 10.1.1.0 - system.prof config-trig
4) Run the check script to rebuild your rules.ok file
5) Jumpstart the target machine(s) normally. Each system will go
through the normal Jumpstart process and reboot automatically.
The configurator process will be triggered during the first reboot
after the Jumpstart. At the end of the configurator process, the
system will again reboot automatically and come up in its final
configuration.
本文来自ChinaUnix博客,如果查看原文请点:http://blog.chinaunix.net/u/4019/showart_23420.html |
|