This directory contains a "template" of what is required for site 
customizations of HEPL.  The intent of this documentation is NOT intended 
to tell you how to customize RedHat releases.  It only describes the 
changes I have made.

Defintions used in this document.

	where <default> is the default directory of the base
	RPMS.  In our case that will be HEPL.

	  /HEPL/RPMS/ 

	where <sitename> is your sitename which is the directory			under sites/ . 

	In this example it will be "example" 

	  /sites/example/
			
        where <tree> is the directory where <default>/ exists
		
	In this example it is /mnt/src/hepl30rolling/i386/
	Note that it must be a full path name. 
 	 
/base/

     comps.xml      	     File that contains what is installed
     comps.xml.main          Your working copy of the comps.xml file 
     cp.comps.xml.main.sh    Script to move comps.xml.main over as comps.xml
			     and save old one in oldcomps

	
     hdlist	    	     Created by the genhdlist command
     hdlist2	             when you use the --site <site> option
			
	        genhdlist --default <default> --site sites/<sitename> <tree>

			    --default <default>

			    Defines where <default>/RPMS is located under <tree>
			    Required.
			
			    --site <sitelocation>
	
			    <sitelocation> is <tree>/sites/<sitename>

			    If --site is left off, hdlist and hdlist2 will 
                            be created in the <tree><default>/base/ direcory.
                            This is needed when rpms are added or removed from 
                            the <tree>/<default>/RPMS/ directory.
 
			    --site <sitelocation> is required when RPMS are 
                            added or removed from the 
                           <tree>/sites/<sitename>/Updates directory.

     genhdlist --default HEPL --site sites/example /mnt/src/hepl30rolling/i386/
	
			   A script to run genhdlist is included in
			   /sites/example/build/scripts/build.hdlist.example.sh
			   See /sites/example/build/scripts/README first


     netstg2.img      Created by "/usr/lib/anaconda-runtime/buildinstall" 
     stage2.img	      See /sites/example/build/scripts/build.release.example.sh
     hdstg2.img       See /sites/example/build/scripts/README first
     pkgorder

/Updates/

    Location for "customized" rpms.  You can either replace/override rpms
    from <tree>/<default>/RPMS/ or add your own rpms.  It is up to you to 
    make sure that all added or modified rpms can get their dependencies met 
    between <tree>/<default>/RPMS/ and /sites/<sitename>/Updates  .  
	
    If you add or delete or change RPMS in <tree>/sites/<sitename>/Updates/)
    then you need to remake your /sites/<sitename>/base/hdlist* files.  This is 
    done with genhdlist.  See above for more info on genhdlist.

    What you can put in here:

       custom installer kernel

		kernel-BOOT-   ....   
  
       Any RPMS that you need that are not in /<default>/RPMS/
       Note that if you want these RPMS to be installed by default you must
       include them in your /sites/<sitename>/base/comps.xml file

       custom installer -- This is a alternative to /sites/<sitename>/RHupdates/

		anaconda-* 

/build/

   isolinux/

	Customizations to the isolinux files used to make the install floppy
	and cd images. Get originals from /isolinux/ . For more info on
	isolinux see /usr/share/doc/syslinux* .

	boot.msg

		Your customized boot.msg file. 

	isolinux.cfg

		Your customized isolinux.cfg file. 

	splash.lss       

		Your customized splash.lss file.  This is the "image"
		that is seen at the top of the boot media.
		The .lss file format is an ascii based picture format. 
		It is generated by using the pngtopnm program.
	 
        README

		Documentation on how/what to change in this directory.

   scripts/
     
	 README
	   Very important
	   Explains what all the other scripts here do.
	   
	 locations.include
	 build.hdlist.example.sh
	 build.release.example.sh
	 make.products.img.sh
	 make.updates.img.sh
	   
	   For explanation as to what these scripts do, read the README

   documentation/

	Contains more detailed documentation on building sites.

/RHupdates/

   Your customizations to the installer.  Other way is to make new anaconda-*
   rpms and put them in /sites/<sitename>/Updates/

/documentation/

   <sitename>.releasenote

	Linked from /HEPL.documentation/sites/<sitename> 
	Your releasenotes.  Contents are up to you.

   any other documentation you want

/images/

   bootdisk.img     These are created by "/usr/lib/anaconda-runtime/buildinstall
   drvblock.img     
   drvnet.img	    See /sites/example/build/scripts/build.release.example.sh
   pcmciadd.img     See /sites/example/build/scripts/README first 
   boot.iso
   pxeboot
   README


------------------------------------------------------------------------------
Steps for making your own site customization
------------------------------------------------------------------------------
In this example we will call our new site "newsite" so $SITE is "newsite".
The <tree> is in /mnt/src/hepl30rolling/i386/ and is defined as $TREE
and <default> is HEPL and is defined as $DEFAULT

cd $TREE
mkdir sites/newsite
cd sites/example
find . -print | cpio -pvdum ../newsite    # copy over example area as a start
cd ../newsite

<add and remove RPMS in "Updates" to customize as you want, You probably
would want to make your own yum-conf rpm.  Install the SRPM for yum-conf and
modify for your use.  You will need to change the version .  Put your new 
yum-conf in "Updates", You also would want to change example-release to contain 
your own release name.  If you change the name from example-release to something
else you will have to change the example-release entry in base/comps* > 

cd base

<modify "comps.xml.main" to include added RPMS and other site
customizations, The one included here is the same as what is in HEPL itself,
with hepl-release changed to example-release>

sh cp.comps.xml.main.sh 
cd -

<modify files in "build/isolinux" as described in "build/isolinux/README">

<modify or remove contents in "RHupdates/textw" and "RHupdates/" depending on 
your needs , most would want to remove the contents of "RHupdates/iw" as 
it contains an example with a hardcoded url which is probably not what you want, it was only included to show what could be done.>

cd build/scripts

<modify locations.include to fix TREE= and SITE= to be 
TREE=<where ever your tree is located>  # In our case it is already ok.
SITE=newsite, Also change --product string in build.release.example.sh>

sh build.updates.example.sh    # Need to do whenever you change contents of
			       # $TREE/sites/$SITE/RHupdates/

sh build.hdlist.example.sh     # Run this whenever you change contents of
			       # $TREE/sites/$SITE/Updates/

sh build.release.example.sh    # Only need to run this when changing installer
			       # kernel , but at least 1 time

<now test install with images in "$TREE/sites/$SITE/images/">



while <notdone>

   <add and remove RPMS in "$TREE/sites/$SITE/Updates" to customize as you want>

   <run build.hdlist.example.sh after each batch of changes>

   <modify comps.xml.main and run cp.comps.xml.main.sh as needed>

   <test with install images in "images/", only need to rebuild when
    installer kernel changes or anaconda rpms change and you want to
    include those changes>

I am sure this is not complete, but it is close.  

-Connie Sieh
csieh@fnal.gov