Click here to go directly to the howto (last modified on 2003-07-05) * 2003-07-05
   - important changes in version 2.0 of the update_release.py script. Now it will only merge those rpms so that the resulting installation tree will have no dependencies nor conflicts problems.
   - the update_release.cron script was modified to remove corrupted rpms if any (this can happen if the connexion is broken when downloading rpm updates) before merging.
   - added a section on configuring the ntp service to have a global time synchronization.
   - added a script called ip2hex.sh to convert an IP address to an hex format. This script is needed when setting up PXE.
   - added some explanations on the installation process.
   - added the part on maintaining the linux boxes with cfengine.
   - added a script called configure_deploysrv.sh which assists you in the process of setting up the deployment server.
* 2003-05-06
   - added a patch for mirror because it breaks under Redhat 9 (bad parsing of files). Thanks to Jesse who reported me the problem.
   - added a command "chkconfig --add yum" in the kickstart files in order to be sure that yum will be activated at startup.
* 2003-05-03
   - added a section "Network installation using a network installation CD".
   - the script /etc/cron.daily/yum.conf was modified to reboot after every installation of a new kernel in order to load the new installed kernel.
   - added some lines at the end of the section "Merging the updates" that tell how the script update_release.cron can be executed before the linux boxes access the updated installation tree.
   - the mount command in the %post section in the kickstart files takes a long time to execute. The problem was fixed by using the "nolock" option.
* 2003-04-24
   - the script /etc/cron.daily/update_release.cron was modified to merge the updates and update the yum repository only if mirror gets new rpms in the updates dir. Also, some arguments were added to the script.
   - Continue with the section "Maintaining".
   - More about requirements 3 and 4 (iptables ...)
   - Create a customized package group (modify comps.xml).