[GRLUG] Imaging software improvements

[Szymon Machajewski]

You may want to take a look at g4l (ghost for linux).
an iso.

http://sourceforge.net/projects/g4l


Thank you.
 
Szymon Machajewski

Solutions Engineer / DBA
Red Hat Certified Engineer
Oracle Certified Associate
Microsoft Certified Solution Developer
www.grcc.edu/smachaje 


>>> "Michael Mol" <mikemol at gmail.com> 11/13/2006 9:34 AM >>>
I'm passively familiar with two system imaging software packages,
Symantec's Ghost and Novell's system imaging software. (Don't remember
the name.)

One thing I've noticed is that they don't handle errors very well.
When I watch a batch of ten or fifteen computers getting imaged, if
one machine fails, that machine aborts, and a second attempt has to be
made for it after the rest of the systems are done transferring data.
The new attempt doesn't resume where the old attempt left off, though;
it starts from the beginning, which means another couple hours of
waiting.

I've thought of what I see as a better way to write imaging software.
Basically, you break the transmission into chunks, and check each
chunk's md5sum against what the server says it should be.  One could
break the disk image into chunks, or the filesystem.

Once the server is done multicasting the entire image, the client
computers would report which chunks failed, and those chunks would be
transmitted again. If the same chunk failed on many computers, it
would get a higher priority in retransmission than those chunks that
failed on fewer computers.

Thoughts?

-- 
:wq
_______________________________________________
grlug mailing list
grlug at grlug.org 
http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug