[SoaS] [Server-devel] Journal and Google
fgrose at gmail.com
Sun Jul 18 10:25:01 EDT 2010
On Sun, Jul 18, 2010 at 5:04 AM, Tabitha Roder <tabitha at tabitha.net.nz>wrote:
> Has anyone tried backing up the Journal to Google docs? A school told us
> they are using google apps (for education) and would like Sugar to store the
> Journal in Google clouds. Really, what they would like is a backup system so
> loss of the device doesn't mean the loss of all the student's work -- the
> school server provides a backup system, this may be sufficient. Does anyone
> have success stories we can show them along the "Little Johnny started
> learning how to customise his operating system now his XO won't boot, we
> reflashed it, and all his Sugar activity work was restored from the XS".
> I'm guessing tight integration with a cloud isn't a design goal of the
> school server but if it can hand off to the cloud this would make them
> happier. They have a google partner who can make at least some magic happen,
> does anyone have any pointers on how to do a feasibility study?
> Google Education Apps: http://www.google.com/a/help/intl/en/edu/index.html
If Sugar on a Stick images are prepared with a separate, persistent Home
directory (with the --home-size-mb option of livecd-iso-to-disk, or with the
--copy-home option of
http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Sugar_Clone, that allows one
to share a customized Journal) then the entire, Home directory (with the
Journal) can be backed-up, shared, or swapped by means of the
/LiveOS/home.img file (an un-compressed filesystem package that is loop
mounted in the LiveOS to provide the /home/ directory). The persistent home
feature is available in all SoaS versions by invoking the livecd-ico-to-disk
patches that will make the copy-overlay and copy-home customization features
more readily available.
A cloud-based swapping service for home.img files seems quite reasonable for
those with sufficient Internet bandwidth.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SoaS