(no subject)

I am trying to get a handle on  filesets and I'm having
a brain block. 

I have been checking out the code but this is a part that is hard
for me to analyze since the "meat" (i.e. the actual filesets)
is in Luke's production environment.
 
Let me outline some random thoughts and perhaps 
I can get some feedback to help me understand the concept
better.

Previously in isconf 2i when we wanted to synchronize
a set of files from the gold server to the client we
would (in the makefile) "cd /" and then rsync one or
more  representative root trees from the gold server
(common tree, os specific tree, etc..)

Although the representative root trees may indeed be
controlled in CVS, if a client is rebuilt, it has
the possibility of functioning different because
the fileset it will rsync when repeating steps
may reflect contents that was historically not
there at the initial build and which in some way 
conflicts with the early stanzas in the makefile.

If I understand correctly, filesets was introduced 
to move this 'cd /; rsync from goldhost' functionality
into the makefile state-engine paradigm so that
a strict sequencing of when a set of files is introduced
onto the client. 

What confuses me is that once filesets are added
to a client, the client then appears to rsync the
filesets everytime isconf is run.

If these filesets are updated in any manner on
the goldhost, it seems, at least to some extent,
we are back to the original dilema.

This is my understanding and help in improving it
and the theory behind it is much appreciated!

Thanks,

Kevin 

-- 
.___________________________________. 
| Kevin Counts     [email protected]  |
| 813.974.1466 (w) 727.460.9522 (c) |
| http://www.digicat.org            |
`-----------------------------------'


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com