On Tue, Feb 17, 2009 at 16:59, Christoph Derndorfer <e0425...@student.tuwien.ac.at> wrote: > Hi Chris, > > thanks a lot for your reply and all the information! > > It looks as though we should try to get the devkeys as soon as possible > so we are prepared for whatever might happen in the future. > > Other than that what I take away from this thread is that upgrading > those XOs to the latest Sugar code will require quite a lot of > preparation and work.
Right now yes, as we are still in development, but once someone develops a way to deploy a release with Sugar 0.84 on XOs, everybody will benefit from it. An alternative to reflashing or setting up a local olpc-update server would be installing one of the live images to a sd card and running a script to copy the DS from flash to there. That may be a bit more convenient in some situations but you would need anyway a developer key. HTH, Tomeu > Christoph > > Chris Ball schrieb: >> Hi Christoph, >> >> > Off the top of my head I'm wondering whether there's a chance to >> > get the Sugar 0.84 release signed so it can be run on XOs without >> > having to request a developer key? >> >> I think you should go the devkey route. OLPC can't sign any builds that >> don't contain its security infrastructure (if it did, an attacker in a >> deployment with security enabled could just reflash to this new build, >> escaping the security) and Sugar Labs is unlikely to produce a build >> with all the OLPC stuff in. >> >> I should mention that the olpcfriends gang is considering the idea of >> conducting community XO releases for a release following 8.2.x; if one >> of those is created with OLPC's security work in, I can imagine it being >> signed. OLPC's trying to phase out its centralized security, though, so >> I still recommend getting the devkeys. >> >> > Thinking of copy-nand I realize that this would also wipe the >> > Journal with everything the children have created so far... Is >> > there any way to avoid that and do some sort of olpc-update that >> > actually downloads the Sugar 0.84 release? >> >> The "Sugar 0.84 release" won't be something that's bootable on an XO, >> it's just Sugar. Once you know which OS release that contains Sugar >> 0.84 you'd like to use, though, it's possible to do what you describe; >> olpc-update takes a --server flag to allow you to specify your own >> update server, and you can run your own olpc-update daemon on an XS >> server (which can be somewhere out on the public net, if you like). >> >> - Chris. > > -- > Christoph Derndorfer > co-editor, olpcnews > url: www.olpcnews.com > e-mail: christ...@olpcnews.com > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > IAEP@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/iaep > _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep