>No, at this time those do not exist. That's deliberate. In many (most)
>cases,
>Jumpstart finish scripts exist to work around gaps in the feature set or
>implementation. We want to understand what the real requirements are
>and build those into the product.
Don't try that; after reading a large part of the AI opensolaris
autoinstallation documentation I can only conclude that people have read
the jumpstart installation but they have no idea how jumpstart is used in
practice.
First of all, everyone who uses jumpstart in a large environment doesn't
actually need to do anything when a new client is installed.
Secondly, in a past live, I used the begin/finish script to customize
*everything* in a system.
This includes:
- installing something other than Solaris (SunOS 4.x)
- later it was used to install Linux also
- any possible other mechanism you can come up with.
Not having a finish script will leave you with a gap; by trying to
"understand the real requirement" you're not even close to discovering why
Jumpstart is fantastic.
We needed to wait until Solaris 2.2 came out (or some unofficial patch
from Sun for Solaris 2.1) but from that point it sliced and diced.
Understand that many people who use Jumpstart hardly ever run
"add_install_client" or any of the other scripts.
Before you want to improve on jumpstart you must REALLY understand
jumpstart; that, unfortunately, requires sysadmin experience at a large
customer.
Casper
