On Thu, Apr 10, 2008 at 5:19 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > Not sure. That's for updating the part of the laptop that _isn't_ > created by the user. We care here about the other ;) Don't know if the > plan is for OS updates to be in the school server. Martin would know, > I guess.
Yes, but we aren't there yet ;-) > There are many ways of arbitrating access to the backup service, and > as you pointed out, this should happen without taking much bandwidth. > See http://wiki.laptop.org/go/XS_backup_restore for a proposal. I didn't know about that page. Interesting - but I don't think I'll go for HTTP-based backup/restore. > I would like to know if there already exist any plans about backups. Martin? Right now we have the registration process, and that pushes an SSH pub key from the XO to the XS, and creates a system account on the XS, I want to - move that "user acct creation" to a chroot or vserver - use it to backup/restore over ssh - initially, use rsync over ssh for the backup (and define a simple scheme to walk the stored data) - longer term, move to a git-like protocol on the wire - at some point, have a git-like storage mechanism on the server side, with a sliding window over time the above merits a more fleshed out description but I'm dealing with lousy connectivity atm - so apologies for now... cheers, martin -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list [email protected] http://lists.laptop.org/listinfo/server-devel
