Well, creating points which go 'INTO' your server is probably not a really good strategy.<br><br>However, one could do it the other way with ssh keys (i.e. no login), 'from' the server.<br><br>I've thought about this before... one solution... server has a webpage which allows the XO to see and logon, and user clicks 'back me up now'. The webpage detects the IP of the XO, writes it to a special file of 'XO laptops to backup'. A server cron job, checks for this file, and grabs a IP from the list, initiates a ssh request 'into' the XO laptop using previously shared keys, 'grabs' the needed files, then closes the connection. <br>
<br>I think that this would be safer scenario, than having a bunch of random XO's connecting 'INTO' a server.<br><br>*shrug*<br>-ixo<br><br><div class="gmail_quote">On Mon, Jan 28, 2008 at 3:05 AM, Luke Gorrie <<a href="mailto:lukego@gmail.com">lukego@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Ivan Krstiæ <<a href="mailto:krstic@solarsail.hcs.harvard.edu">krstic@solarsail.hcs.harvard.edu</a>> writes:<br>
<br>
> On Jan 22, 2008, at 10:28 PM, Bryan Berry wrote:<br>
>> We really need the incremental backup feature. That is a core<br>
>> requirement that came up many times in last week's OLPC Learning<br>
>> Conference.<br>
><br>
> I'll see about finishing it up for you, then. Please ping me from time<br>
> to time to make sure this doesn't drop off my radar.<br>
<br>
</div>Just out of curiosity: would having the XOs periodically (cron)<br>
rsync-over-ssh /home/olpc to the school server be hopelessly naive for<br>
some reason?<br>
<div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br>