[Sugar-devel] Community OS 14.1.0 Version 2

[tkkang at nurturingasia.com]

Looking forward to a rebuild that would work on a SD card for XO-1.

To make life easier when running the XO from SD, turning power management off is good:-) 

[powerd]
enable_idle_suspend=0



>-----Original Message-----
>From: Samuel Greenfeld [mailto:samuel at greenfeld.org]
>Sent: Thursday, March 5, 2015 10:25 PM
>To: 'Sebastian Silva'
>Cc: 'OLPC Devel', sugar-devel at lists.sugarlabs.org
>Subject: Re: [Sugar-devel] Community OS 14.1.0 Version 2
>
>No this isn't the build that runs off an SD card.
>
>If there is that much interest I will re-build the XO-1 image with the
>additional SD card image tonight.
>
>Apart from the XO-1, the olpc-os-builder configurations I am using are
>basically what you see in OLPC's Git repository, with the "xx" changed to
>"qq" and "Community Build" added as the name of the deployment.
>
>
>On Thu, Mar 5, 2015 at 9:20 AM, Sebastian Silva <sebastian at fuentelibre.org>
>wrote:
>
>> Downloading
>>
>> http://www.greenfeld.org/xo/community/builds/14.1.0/build_2/xo-1/41002qq0.img
>> for XO1 now.
>>
>> Is this the one that runs off of SD card?
>>
>> I'm interested for Perú, but as you can imagine, it doesn't depend on
>> me. Our team (Platform team + SomosAzucar) did build the last official
>> image Peru is using so who knows.
>>
>> Just for your reference, we built the image in 2011, they tested it (and
>> we fixed it) all 2012 and they deployed it in 2013-2014.
>>
>> It would be good to make something available that is more up to date,
>> even if it's not an "official" update.
>>
>> Regards,
>> Sebastian
>>
>>
>> El 05/03/15 a las 07:06, James Cameron escibió:
>> > On Thu, Mar 05, 2015 at 06:55:13AM -0500, Samuel Greenfeld wrote:
>> >> The updated images can be found at
>> http://www.greenfeld.org/xo/community/
>> >> builds/14.1.0/build_2/
>> > I've heard there may be one or two microdeployments some interested in
>> > SD card builds on XO-1.  If you want to cover that, add the module
>> > [sd_card_image] to your .ini file.  Let me know if it is broken.
>> >
>>
>>
>