The JS image can be described in it's most simple view as this:

<H2> From The single 700MB cdrom view </H2>
<ol>
<li> Standard Solaris "Product":   600MB  (See README.VERSION for exact version)
<li>  .install_config 276 MB  (standard Solaris Jumpstart technology)
<ol>  
<li>  217 MB of Sun Patches (up from the 02/02 release)
<li>  54  MB of "unbundled products" (yassp, java-1.3, ssh...)
<li>  4.2 MB of "custom JS files" (/etc/passwd, perl, gzip,bzip...)
</ol>
</ol>

First we start with a virgin "Solaris 8 02/02" (or whatever is specified in README.VERSION)
 media set of 2 cdroms which total about 1 GB. We then "Trim the fat" from a full+OEM install
by removing (deselecting) packages such as: uucp, kcms, Asian locales and
others. (the international locale parts comprise about 400MB of this 
material which is "removed". 
<ul>
<li>JS builds upon "autoinstall.tar.gz" from Casper Dik @ Sun.de and his work since 1993.
<li>It would be useful to familiarize yourself with that base distrubition he provides.
</ul>

<H2> From the viewpoint of a unix admin who is familiar with Jumpstart</H2>

<UL>
<li>The Jumpstart server at Your site should be the host "JumpHost" on the server network.
<li>Clients are only able to jumpstart from a master-jumpstart server on the same
subnet due to nature of bootp/tftp/rarp. 
<li>The Jumpstart tree is mounted under /jumpstart on that host. 
<li>Modifications to this tree are (or will be) under cvs source version control and differences between versions can 
(will) easily be displayed with "webcvs". 
<li>a script called addclient is used to pre-configure a host being network jumpstarted. (see below)
</UL>

<b>Addclient:</b> network jumpstart preperation script (like add_install_client)
<br>  This script is a curses-based korn-shell script which is a wrapper for
the standard Sun Jumpstart <i>add_install_client</i> script. 
<br> It provides the exact same functionality with a nice front-end. 
<br> Addclient can also provide a means of "pre-classifying" a new client, 
but this functionality needs a bit of integration and infrastructure apps to 
become fully functional. 
<br>(eg: mph, machine JS repository, filesystem tmp/SAVE directory, and the various customized postinstall
scripts which will make this class unique.

<H3>Learn from the logfiles which an autoinstall produces:</H3>
check out the log files: ><a href="log/">/etc/opt/JS/log/*</a>    

then figure out that they were created with the autoinstall process, 
during miniroot, and then _after_ the install, 
run by /.autoinstall/postisntall.sh

<br>

<b>Then,</b> enter into the <a href="files/">/net/jumpstartmaster/jumpstart/slice0/.install_class/install/files</a>directory and browse around. 
Understand that the files' installation are dictated by
the <a href="copy.conf">copy.conf</a> file (also provided here).  

Lastly, you can read the <a href="README.howitworks">README.howitworks</a> for the simple
algoritm on chosing _which_ flavor of file goes to what machine.