If there is a team of administrators involved, a revision control/sourcecode management system like CVS can make coordination easier: many people can work on the configuration files simultaneously, while the system helps avoiding conflicts (and if they occur it helps resolving them). Another advantage lies in branching: while the administrator works out a new configuration and tries it out using a test system, other clients aren't disturbed in any way, because they use another branch of the configuration.
First you should setup a CVS repository and within it a module to store the FAI configuration files. In this example a cvs pserver will be used for read-only access to the configuration files by the clients, while ssh is used for the developers access (rw)[16].
The relevant variables in /etc/fai/fai.conf
and
/etc/fai/make-fai-nfsroot.conf
for CVS are:
FAI_CVSROOT=":pserver:client@cvs.local.net:/var/lib/cvs"
FAI_CVSMODULE="config"
FAI_CVSTAG="STABLE"
If you use a cvs pserver for storing configuration files, the file
/root/.cvspass
has to exist and be valid in the nfsroot. CVS uses
this file to get the password for the pserver. You can create it most easiely
if you try
cvs -d$FAI_CVSROOT login
and then copy the generated line from your ~/.cvspass
into
/root/.cvspass
in the nfsroot.
FAI Guide (Fully Automatic Installation)
FAI Guide version 2.4.4, 9 aug 2004 for FAI package version 2.6lange@informatik.uni-koeln.de