[Sugar-devel] Sugar-devel Digest, Vol 58, Issue 47

[Jerry Vonau]

On Sat, 2013-08-24 at 09:21 +0200, Tony Anderson wrote:
> Hi, Jerry
> 
> I think the difference in approach is that you have a centralized 
> organization supporting widely distributed deployments. In that case 
> providing an image with the necessary customizations is probably much 
> easier.
> 
> For those of us supporting a stack of XOs in a room, it is very simple 
> to run a post-install (post-flash?) script. It adds a few minutes per XO 
> since the flash has to be done by usb key anyway. This also avoids the 
> 'locked' XO problem.
> 

True, not much you can do with locked boxes.

> I had the experience in Rwanda of attempting to do a local OS build. The 
> first step was to download about 10GB of repository. Not going to happen 
> in the internet environment there. A deployment who wants to rebuild 
> must make sure that it has the repositories available on hard drives 
> capable of doing the build offline.
> 

Maybe I can help you out with that, I can't see how you need 10GB of
data: 

du -c -s -h build/cache/imgcreate/
2.7G	build/cache/imgcreate/
2.7G	total

plus activities

That is what olpc-os-builder has cached, from multiple runs with
fedora_updates' yum repo turned on grabbing the latest rpms when
available. Once the cache is populated you can use olpc-os-builder
offline, this might be a new feature since you tried last.

Jerry

> Tony
> 
> 
> On 08/24/2013 08:34 AM, Jerry Vonau wrote:
> > On Sat, 2013-08-24 at 15:13 +1100, David Leeming wrote:
> >> >That's all understood. However the task at hand is that a regional bank has
> >> >donated 200 XO 1.5s to two schools in the Solomons and they want to play
> >> >videos and music on them. I can't say, well sorry they gave you the wrong
> >> >ones.
> >> >
> >> >Another issue was that 2GB 1.5s were supplied with 11.3.1 and have very
> >> >limited memory and the journals become full within a few days use, so we
> >> >have the job now of upgrading them all with 8GB cards kindly forwarded to us
> >> >by OLPC.
> >> >
> >> >With the extra memory we thought we'd upgrade to 13.2.0 but if we can't find
> >> >a way to conveniently install codecs on them all we have the choice of
> >> >staying with 11.3.1 which is still pretty good.
> >> >
> > To install the codecs I would strongly suggest that you explore
> > os-olpc-builder and brew up what you need into an image that you can
> > install on unlocked machines. That is what I do for the OLPC Australia.
>