<div class="gmail_quote">moving onto list...</div><div class="gmail_quote"> </div><div class="gmail_quote">Forwarded conversation Subject: Suggestion:The SugarClone script needs to generate an.iso file of a SugarClone customized USB ------------------------ From: Thomas C Gilliard <<a href="mailto:satellit@bendbroadband.com">satellit@bendbroadband.com</a>> Date: Sun, May 2, 2010 at 8:40 AM To: Frederick Grose <<a href="mailto:fgrose@gmail.com">fgrose@gmail.com</a>> Cc: Mel Chua <<a href="mailto:mel@melchua.com">mel@melchua.com</a>> Suggestions to consider: If the, easy to use, SugarClone script could somehow generate an.iso file of a Master customized USB, we would have a great method for generation of Mirabelle Spins. The .iso format would then allow easy and cheap distribution. New persistent sticks could be created from them via liveusb-creator or the livecd-iso-to-disk script. (I know we are looking for a "dead easy" way to do this) This would negate need for the use of kickstart files, revisor and other such tools and make it very easy for a deployment or a teacher at a school to make multiple copies of the customized live usb soas sticks for their use. Maybe also generate a difference file and include it on the .iso to reflect all changes from a stock .iso.? (This would be nice for troubleshooting and support) I do not know if this is possible to do. Tom Gilliard satellit ---------- From: Mel Chua <<a href="mailto:mel@melchua.com">mel@melchua.com</a>> Date: Sun, May 2, 2010 at 9:22 AM To: Thomas C Gilliard <<a href="mailto:satellit@bendbroadband.com">satellit@bendbroadband.com</a>> Cc: Frederick Grose <<a href="mailto:fgrose@gmail.com">fgrose@gmail.com</a>> What this would essentially do is remove the "view source" functionality for remixing the sticks themselves, since kickstart files are how we make the package (and therefore the Activity) selections on the SoaS images remixable for large deployments *and* easily shareable between deployments (swapping kickstart files and looking for diffs in text is much easier for a deployment support staffer to do than swapping .isos and looking for binary diffs). So I don't think this is a practical design to aim for, since we already make and distribute .iso files, and provide instructions others can follow to remix their own from the documentation and sources we hve provided. --Mel<div><div></div></div> </div>