[Server-devel] Issue with ds-backup in XS 0.4

[Douglas Bagnall]

hi Bill,

> This raises an operational question.  If someone already has deployed
> XS (0.4 or earlier) against which older XO releases are registered,
> what do they do in order to take advantage of ds-backup?   Should all
> the XOs re-register?  Is there a way to do this without mucking around
> in a terminal window to convince the XO that it isn't registered any
> more?  If one does have to muck around, how should this be done to
> avoid losing other user customizations?

Your options are vi and nano.  Remove the stanzas starting with
"[Jabber]" and "[Server]" from /home/olpc/.sugar/default/config.

Somewhere I have an unregister.py script that does this automatically
-- I'll look for it in the morning, though it won't actually help you
unless you're repeating the operation: getting the script onto the
laptop is more work than the simple edit.

> Perhaps, there is a way to do something on the XS to 'upgrade' the
> registration of older XO releases to add ds-backup functionality? The
> /library/users directory for the older machine does have an
> .ssh/authorized_keys file.  What else is needed on the XS in order for
> backups to work?  I can see no obvious significant differences in the
> /library/users directories.

I am not certain, but I think the lack is on the XO side.  The
.sugar/default/config files probably have the wrong address or no
address for the backup server.  If you could post an example config
file it would help confirm this.

The registration system is not the most advanced piece of OLPC
technology.  There's no good way to repeat, reverse or modify
registration, and more and more of these kinds of bugs will show up as
the registration information is increasingly used.


Douglas