How to re-create JS:

Warning... JS is a very intricate system of software from various
sources of Solaris media and a bunch of freeware. Using this document
to re-create JS will result in a "Ford Taurus", instead of a Jaguar XJS.
In other words, the beauty and simplicity of JS on the outside is part of
the beauty of the JS on the inside.  (you might want to start with Sun's
Flash install if you really want a Ford Taurus before going down the 
Casper Dik Autoinstall route, or even trying to cleanroom duplicate all
functionaliry of the JS...)

Another way to look at it, is the documentation is more effectively in
the components of JS itself. It's all a bunch of korn-shell scripts, 
which work from templates and copy in pre-modified files.  to document
this procedure would produce 3x the amount of material than the JS itself.

anyways, to create the taurus, here is the recipe.

-start with stock soalris cdrom release
-select a subset (about 665) of the 900 or so Solaris pkg's
 which are on the three cdrom's. (software, docs, install)
 Things like thai locale, Kodak Color Management system, uucp are
 removed from the "Product" tree. and .pkgtoc is updated.
-begin with the autoinstall suite of Casper Dik, customize the
 confs and files appropriately.  
 ftp.fwi.uva.nl/pub/comp/solaris/autoinstall has the magical package.
-get yassp and during a postinstall script, make these yassp.conf edits:
/NFS=/s/NO/YES/
/XNTPD=/s/NO/YES/
/VOLMGT=/s/NO/YES/
/DEVFSADM=/s/NO/YES/
/DEVLINKS=/s/NO/YES/
/AUTOFS=/s/NO/YES/
/# RUNINETD=NO/
s/^# RUNINETD=NO/RUNINETD=YES/

yassp also includes security programs such as  tripwire, tcpwrappers, 
and some log-magangement utilities. JS currently does nothing with those 
other than let yassp install those as appropriate. Manual intervention is 
needed to change the default yassp behavior. (vi /etc/yassp.conf)

After the standard Solaris Jumpstart is finished, a "finish script"
is run. That is where the Casper-Dik autoinstall suite is run. 
The Casper Dik Autoinstall suite follows a standard algorithm to perform
actions listed in the .conf files. (eg: mkdir.conf, copy.conf, append.conf...)

The algorithm looks something like this:
  findfile(filename) {   ls -ld install/filename/`uname -n`
                   else ls -ld install/filename/`domainname`
                   else ls -ld install/filename/`for i in /etc/INSTALL_CLASS; 
                                                 grep $i ; done`
                   else ls -ld install/filename/default
           }

so, as you can see, /etc/INSTALL_CLASS can "put a machine in a class". 
or, you can for example have the class "DMZ" run an empty inetd.conf,
while other hosts not in DMZ class get the "default" inetd.conf file.

One of the files dropped in from that is postinstall.sh.  On subsequent
reboot, this script is run, and things such as post-patching, and
configuration of Disksuite (RAID software) happens. At this stage,
the machine will also send out a status email to notify interested
parties that the machine has finished autoinstalling.