<div class="gmail_quote">On Tue, Sep 14, 2010 at 9:31 AM, Tomeu Vizoso <span dir="ltr"><<a href="mailto:tomeu@sugarlabs.org">tomeu@sugarlabs.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Tue, Sep 14, 2010 at 01:52, Christoph Derndorfer<br>
<<a href="mailto:christoph.derndorfer@gmail.com">christoph.derndorfer@gmail.com</a>> wrote:<br>
> On Tue, Sep 14, 2010 at 12:13 AM, Bernie Innocenti <<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>><br>
> wrote:<br>
>><br>
>> > > -------- Forwarded Message --------<br>
>> > > From: Bernie Innocenti <<a href="mailto:bernie@codewiz.org">bernie@codewiz.org</a>><br>
>> > > To: Christoph Derndorfer <<a href="mailto:christoph.derndorfer@gmail.com">christoph.derndorfer@gmail.com</a>><br>
>> > > Cc: <a href="mailto:dextrose@lists.sugarlabs.org">dextrose@lists.sugarlabs.org</a>, Sugar Devel<br>
>> > > <<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a>>, <a href="mailto:christoph.derndorfer@olpc.at">christoph.derndorfer@olpc.at</a><br>
>> > > Subject: Re: [Dextrose] Question about upgrading from 802 to<br>
>> > > Dextrose<br>
>> > > Date: Mon, 13 Sep 2010 23:01:04 +0200<br>
>> > ><br>
>> > > On Mon, 2010-09-13 at 18:45 +0200, Christoph Derndorfer wrote:<br>
>> > > > as previously mentioned to Bernie I'm thinking about using the<br>
>> > > > international spin of Dextrose on the 25 XO-1s that we're using in<br>
>> > > > our<br>
>> > > > Austrian pilot project.<br>
>> > > ><br>
>> > > > IIRC correctly those XO-1s are currently running 802 and now I was<br>
>> > > > wondering whether there was a way to upgrade them to Dextrose<br>
>> > > > without<br>
>> > > > erasing the Journal (e.g. something like olpc-update but using<br>
>> > > > Dextrose rather OLPC's 10.1.2).<br>
>> > ><br>
>> > > For the first upgrade in Paraguay, we used two very simple shell<br>
>> > > scripts<br>
>> > > to backup the journal to a tarball on a usb stick.<br>
>> > ><br>
>> > > The procedure was somewhat cumbersome:<br>
>> > ><br>
>> > > 1) plug in usb stick<br>
>> > > 2) open terminal<br>
>> > > 3) /media/USBSTICK/backup_script<br>
>> > > 4) wait<br>
>> > > 5) cleanly unmount usb stick<br>
>> > > 6) reboot<br>
>> > > 7) flash<br>
>> > > 8) boot into sugar<br>
>> > > 9) open terminal<br>
>> > > 10) /media/USBSTICK/restore_script<br>
><br>
> Thanks a lot for these instructions.<br>
><br>
>><br>
>> > > Of course, we did this only for specific laptops where the user wanted<br>
>> > > to preserve information. Many users were perfectly with erasing their<br>
>> > > journal completely. Some kids asked to save only one or two files.<br>
>> > ><br>
>> > > If you have a schoolserver, then you should already have daily backups<br>
>> > > even with 802. You're just missing a restore function.<br>
><br>
> Interesting, I wasn't aware of that.<br>
><br>
> If I remember correctly I had set up XS 0.5 at the school, how would I find<br>
> out whether the backups were made and if so how do I restore them to the XOs<br>
> after I install Dextrose on them?<br>
<br>
</div></div>There's quite a bit of info here:<br>
<a href="http://wiki.laptop.org/go/Category:SchoolServer" target="_blank">http://wiki.laptop.org/go/Category:SchoolServer</a><br></blockquote><div><br>The closest documentation for what I want to do is <a href="http://wiki.laptop.org/go/XS_backup_restore#XO-initiated_full_restore">http://wiki.laptop.org/go/XS_backup_restore#XO-initiated_full_restore</a> but I'm not sure I fully understand it. Basically I need to find out the backup dir for each laptop via an HTTP GET, then rsync on tht dir 3 times and then rebuild the metadata, right?<br>
<br>Almost sounds like Bernie's 10 step tarball approach is actually easier here... :-/<br><br>Christoph<br></div></div><br>-- <br>Christoph Derndorfer<br>co-editor, olpcnews<br>url: <a href="http://www.olpcnews.com">www.olpcnews.com</a><br>
e-mail: <a href="mailto:christoph@olpcnews.com">christoph@olpcnews.com</a><br>