On Wed, Apr 30, 2008 at 3:37 AM, Eben Eliason <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 28, 2008 at 7:23 PM, Martin Langhoff
> I was actually referring to a case where the child wanted to do a
> restore on their current laptop, rather than a new one, in which case
> no new association is needed a
On Tue, Apr 29, 2008 at 11:11 PM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote:
> > That would be _very_ costly on the server side. Let the rsync
> > complete, and do a bulk import.
>
> Ok, we just have to take in account that the bulk import will block
> all activity requiring the DS.
This is a o
On Mon, Apr 28, 2008 at 7:23 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> On Tue, Apr 29, 2008 at 5:14 AM, Eben Eliason <[EMAIL PROTECTED]> wrote:
> > On Mon, Apr 28, 2008 at 12:58 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
> > > On Mon, Apr 28, 2008 at 10:33:13AM -0400, Eben Eliason wrote
On Tue, Apr 29, 2008 at 1:34 AM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> On Tue, Apr 29, 2008 at 2:14 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote:
> > >- Q: Does it make sense to always maintain the CJSON-formatted
> > > metadata anyway? (This would specially make sense if some of the
On Tue, Apr 29, 2008 at 2:14 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote:
> >- Q: Does it make sense to always maintain the CJSON-formatted
> > metadata anyway? (This would specially make sense if some of the DS
> > corruption reports being discussed are tracked down to Xapian.)
>
> Extrac
On Tue, Apr 29, 2008 at 5:14 AM, Eben Eliason <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 28, 2008 at 12:58 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
> > On Mon, Apr 28, 2008 at 10:33:13AM -0400, Eben Eliason wrote:
> > > Well, I guess I need to know a bit more about the technical details
> >
On Mon, Apr 28, 2008 at 12:58 PM, Michael Stone <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 28, 2008 at 10:33:13AM -0400, Eben Eliason wrote:
> > Well, I guess I need to know a bit more about the technical details
> > that will be in play in this circumstance. Since we don't have unique
> > userna
On Mon, Apr 28, 2008 at 10:33:13AM -0400, Eben Eliason wrote:
> Well, I guess I need to know a bit more about the technical details
> that will be in play in this circumstance. Since we don't have unique
> usernames or passwords, the only identifier for the individual and her
> data is her key, ri
On Mon, Apr 28, 2008 at 10:14 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote:
> On Thu, Apr 24, 2008 at 6:18 AM, Martin Langhoff
> <[EMAIL PROTECTED]> wrote:
> >
> > - Initial HTTP check for protocol and XS availability stays. We drop
> > the 'nonce' value.
> > - Q: Any reason for this being
On Thu, Apr 24, 2008 at 6:18 AM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
>
> - Initial HTTP check for protocol and XS availability stays. We drop
> the 'nonce' value.
> - Q: Any reason for this being REST vs XML-RPC for the registration service?
>
> - Preparations are simpler
>- No ne
On Thu, Apr 24, 2008 at 4:22 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> I'll tidy-up and update http://wiki.laptop.org/go/XS_backup_restore -
Done. Feedback welcome. It's Friday here, I'll be hacking on this on
Monday (NZ time) so you guys have a chance to rip it to shreds before
I start...
On Wed, Apr 23, 2008 at 8:46 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> Tomeu,
>
> Superb - thanks for the info! some questions below...
>
> 2008/4/23 Tomeu Vizoso <[EMAIL PROTECTED]>:
>
> > We have in ~/.sugar/default/datastore/store all the files that contain
> > the "opaque" data of e
On Thu, Apr 24, 2008 at 4:18 PM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> with my notes from the last software-status meeting and a few other
> bits and pieces, my plan is to follow roughly the spec but with a few
> changes.
I'll tidy-up and update http://wiki.laptop.org/go/XS_backup_restor
Tomeu, Ivan,
with my notes from the last software-status meeting and a few other
bits and pieces, my plan is to follow roughly the spec but with a few
changes.
Making a backup:
- Initial HTTP check for protocol and XS availability stays. We drop
the 'nonce' value.
- Q: Any reason for this bein
On Tue, Apr 22, 2008 at 12:18 PM, Ivan Krstić
<[EMAIL PROTECTED]> wrote:
> On Apr 22, 2008, at 12:46 AM, Martin Langhoff wrote:
> > Wad's too simple, I am hoping to use a slightly simplified version of
> > Ivan's. For the restore part, I think I will drastically simplify
> > things from Ivan's a
Tomeu,
Superb - thanks for the info! some questions below...
2008/4/23 Tomeu Vizoso <[EMAIL PROTECTED]>:
> We have in ~/.sugar/default/datastore/store all the files that contain
> the "opaque" data of every entry, named by an uuid that identifies the
> entry.
So this is the actual data store
2008/4/23 Martin Langhoff <[EMAIL PROTECTED]>:
> 2008/4/23 Eben Eliason <[EMAIL PROTECTED]>:
>
> > 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> >
> > > On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> > > <[EMAIL PROTECTED]> wrote:
> > > > My solution is the simplest design I could crea
2008/4/22 Eben Eliason <[EMAIL PROTECTED]>:
> 2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
> > 2008/4/22 Eben Eliason <[EMAIL PROTECTED]>:
> > > 2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
> > > > 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> > > > > On Tue, Apr 22, 2008 at 10:18 PM, Ivan
2008/4/23 Eben Eliason <[EMAIL PROTECTED]>:
> 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
>
> > On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> > <[EMAIL PROTECTED]> wrote:
> > > My solution is the simplest design I could create that allows both
> > > emergency restore (laptop FS has been
2008/4/22 Kim Quirk <[EMAIL PROTECTED]>:
> I'm not seeing the use case that I *think* is the primary one:
That's still listed as the main one, at least in Ivan's email, and
definitely from my perspective. This discussion of how to deal with
the secondary one with minimal fuss and with a good fit w
I'm not seeing the use case that I *think* is the primary one:
1) Backup and restore from a disaster recovery perspective.
and the secondary that goes with that is:
2) Ability to restore to a new laptop (as in the child lost the laptop or it
died and they need to restore their work to a new lapto
2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
> 2008/4/22 Eben Eliason <[EMAIL PROTECTED]>:
>
>
> > 2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
> >
> > > 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> > >
> > > > On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> > > > <[EMAIL PROTECTED]> wr
2008/4/22 Eben Eliason <[EMAIL PROTECTED]>:
> 2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
>
> > 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> >
> > > On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> > > <[EMAIL PROTECTED]> wrote:
> > > > My solution is the simplest design I could create
2008/4/22 Tomeu Vizoso <[EMAIL PROTECTED]>:
> 2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
>
> > On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> > <[EMAIL PROTECTED]> wrote:
> > > My solution is the simplest design I could create that allows both
> > > emergency restore (laptop FS has been
2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> <[EMAIL PROTECTED]> wrote:
> > My solution is the simplest design I could create that allows both
> > emergency restore (laptop FS has been trashed, get everything back) and
> > individual file res
2008/4/22 Martin Langhoff <[EMAIL PROTECTED]>:
> On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
> <[EMAIL PROTECTED]> wrote:
> > My solution is the simplest design I could create that allows both
> > emergency restore (laptop FS has been trashed, get everything back) and
> > individual file res
On Tue, Apr 22, 2008 at 10:18 PM, Ivan Krstić
<[EMAIL PROTECTED]> wrote:
> My solution is the simplest design I could create that allows both
> emergency restore (laptop FS has been trashed, get everything back) and
> individual file restore and sharing via a web interface running on the XS,
Inde
On Apr 22, 2008, at 12:46 AM, Martin Langhoff wrote:
> Wad's too simple, I am hoping to use a slightly simplified version of
> Ivan's. For the restore part, I think I will drastically simplify
> things from Ivan's approach.
My solution is the simplest design I could create that allows both
emerg
On Tue, Apr 22, 2008 at 6:46 AM, Martin Langhoff
<[EMAIL PROTECTED]> wrote:
> Hi Michael,
>
> thanks for looking into this - I had the wikipage in my sight, but not
> the bugs you listed. Excellent, reading up to fill the gaps.
>
>
> > Based on feedback from Peru, Mexico, and Nepal, the "restor
FYI,
Awhile back ago, I developed a quick-n-dirty little *rsync* script which
can be ran on the XO Laptop at any time and regularly.
Here's the latest online version...
http://wiki.laptop.org/go/User:Ixo/Script/xo-backup-server
I've set it up on my XO. And run it when-ever and where-ever i
Hi Michael,
thanks for looking into this - I had the wikipage in my sight, but not
the bugs you listed. Excellent, reading up to fill the gaps.
> Based on feedback from Peru, Mexico, and Nepal, the "restoration from
> disaster-recovery backups" XO/XS coordination feature has been steadily
> ri
Martin,
Based on feedback from Peru, Mexico, and Nepal, the "restoration from
disaster-recovery backups" XO/XS coordination feature has been steadily
rising in priority. I also notice that "Backups" is your first line-item
on the XS-0.3 roadmap.
My large question is: "what changes need to be made
32 matches
Mail list logo
