[SoaS] Suggestion:The SugarClone script needs to run from CD to make a "customized"non-persistent soas USB

[Thomas C Gilliard]

Fred;

Another idea on using your script:

I just tried soas-i386-20100501.07.iso burned to a CD
booted from it and then ran in sugar-terminal
su
wget http://people.sugarlabs.org/fgrose/SugarClone
chmod 077 SugarClone
./SugarClone
Got Error:
.....................................
There appears to be no persistent overlay file on this image.
Cleaning up to exit..
Problem: Transfer of SugarClone failed.
Exit Code 1 was reported. Exiting..
.....................................
If you also looked in home /live user for SugarClone besides /mnt/live
and allowed a non-persistent build to go ahead from running /dev/sr0
this would be a great and easy way to make a customized USB as one can load
and modify the running CD using memory.

Tom Gilliard
satellit

Frederick Grose wrote:
> moving onto list...
>
> Forwarded conversation
> Subject: Suggestion:The SugarClone script needs to generate an.iso file of a
> SugarClone customized USB
> ------------------------
>
> From: *Thomas C Gilliard* <satellit at bendbroadband.com>
> Date: Sun, May 2, 2010 at 8:40 AM
> To: Frederick Grose <fgrose at gmail.com>
> Cc: Mel Chua <mel at melchua.com>
>
>
> 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* <mel at melchua.com>
> Date: Sun, May 2, 2010 at 9:22 AM
> To: Thomas C Gilliard <satellit at bendbroadband.com>
> Cc: Frederick Grose <fgrose at gmail.com>
>
>
> 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
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> SoaS mailing list
> SoaS at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/soas
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sugarlabs.org/archive/soas/attachments/20100502/c8356cfc/attachment.htm