<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
These Haiti's laptops are a mix of secured and unsecured XO-1s.
They are Give1Get1 redonations, mostly running Release 10.1.3
untouched, we'll be upgrading on the ground in Haiti within days.<br>
<br>
We'd love if the longstanding
<a class="moz-txt-link-freetext" href="http://wiki.laptop.org/go/Customization_stick">http://wiki.laptop.org/go/Customization_stick</a> could be fixed on
13.1.0 (worked like a charm less than a year ago) but yep that may
not be possible this week.<br>
<br>
Thanks Kevin & Tony for interim solutions-<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/9/2013 1:07 PM, George Hunt wrote:<br>
</div>
<blockquote
cite="mid:CADfCcpW644XiNOYBKCqGJBNQ_LRevGKOEmPijVxmBLPzd28xWw@mail.gmail.com"
type="cite">Thanks Kevin,
<div><br>
</div>
<div>I think choice 2 is the best given the current situation.
I've never done an OOB build, I don't have any secured XO-1.0
laptops to verify the signing process. There's an extreme
urgency to meet a Wednesday deadline, and I've got some other
priorities to deal with before leaving, and cannot spend 100%
of my time learning what I need to know.</div>
<div><br>
</div>
<div>I think choice 1 would be a better choice, if I had more time
and confidence with regard to OOB and signing images.</div>
<div><br>
</div>
<div>George<br>
<br>
<div class="gmail_quote">On Sat, Mar 9, 2013 at 12:25 PM, Kevin
Gordon <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:kgordon420@gmail.com" target="_blank">kgordon420@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Adam:
<div><br>
</div>
<div>Assuming secured laptops:<br>
<div><br>
</div>
<div>Choice 1, make the build on a stick using OOB with
signatures.</div>
<div><br>
</div>
<div>Choice 2, a two step reflash process: use a regular
build stick for the desired OS for the reflash. After
the OS is flashed, remove the stick then reboot. Now,
reinsert the stick which *already* would have to have a
little script that you have written yourself, (which you
then you run from terminal). The script could manually
anarchive the contents of the bundle directory and place
them in the right folders, and set the permissions. I'm
sure George or Jerry can whip up a script that meets
your specific need pretty quickly. Be careful your
bundles contain the right version of the sugar
activities for the version of the OS, there are issues
using old .xo with F17+, and only install the
supplemental ones, not ones already installed via the
initial default re-flash.</div>
<div><br>
</div>
<div><br>
</div>
<div>If unsecure you don't need signatures for Choice 1,
and the build process is a little cleaner.</div>
<div><br>
</div>
<div>Cheers</div>
<div><br>
</div>
<div>KG</div>
<div><br>
<div class="gmail_quote">
<div>
<div class="h5">
On Sat, Mar 9, 2013 at 12:05 PM, Holt <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:holt@laptop.org" target="_blank">holt@laptop.org</a>></span>
wrote:<br>
</div>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div class="h5">
<div bgcolor="#FFFFFF" text="#000000"> As we're
leaving to a 250 XO-1 deployment in Haiti
within days, George Hunt & I were
fine-tuning Nick Doiron's Haiti customization
stick of 19 Sugar Activities ( <a
moz-do-not-send="true"
href="http://sugarlabs.org/%7Eholt/haiti-shalom-activities-2011-2012/"
target="_blank">http://sugarlabs.org/~holt/haiti-shalom-activities-2011-2012/</a>
) only to discover <a moz-do-not-send="true"
href="http://wiki.laptop.org/go/Customization_stick" target="_blank">http://wiki.laptop.org/go/Customization_stick</a>
no longer works on Release 13.1.0 and 12.1.0.<br>
<br>
Attached Screenshot JPG shows Customization
Stick failing on 13.1.0, also transcribed
here:<br>
<br>
Traceback (most recent call last):<br>
File "/init", line 32, in do_in_child<br>
try: work()<br>
File "/init", line 53, in unpack_bundles<br>
lout(['/bin/mkdir', '-p', v])<br>
File "/process.py", line 118, in lout<br>
raise CalledProcessError(ret, cmd)<br>
CalledProcessError: Command
'['/bin/mkdir', '-p',
'/sysroot/home/olpc/.bootanim']' returned
non-zero<br>
exit status 1<br>
Bundle installation complete; powering off
in five seconds.<br>
<br>
Release 12.1.0 shows the same error, <i>falsely
announcing "Bundle installation complete".</i><br>
<br>
Is this resolvable? We'd rather not, but
we'll revert to Release 11.3.1 if nec, the
last OS where <a moz-do-not-send="true"
href="http://wiki.laptop.org/go/Customization_stick"
target="_blank">http://wiki.laptop.org/go/Customization_stick</a>
works. Screenshot of success (on Release
11.3.1) attached to illustrate normal working
behavior. (Showing a new activity installing
every second or few as desired, scrolling one
per line, right before powering off...)<br>
<br>
All tips appreciated, cheers & thanks!<br>
<br>
<pre cols="72">--
Help kids everywhere map their world, at <a moz-do-not-send="true" href="http://olpcMAP.net" target="_blank">http://olpcMAP.net</a></pre>
</div>
<br>
</div>
</div>
_______________________________________________<br>
Devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Devel@lists.laptop.org"
target="_blank">Devel@lists.laptop.org</a><br>
<a moz-do-not-send="true"
href="http://lists.laptop.org/listinfo/devel"
target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
<br>
_______________________________________________<br>
support-gang mailing list<br>
<a moz-do-not-send="true"
href="mailto:support-gang@lists.laptop.org">support-gang@lists.laptop.org</a><br>
<a moz-do-not-send="true"
href="http://lists.laptop.org/listinfo/support-gang"
target="_blank">http://lists.laptop.org/listinfo/support-gang</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Help kids everywhere map their world, at <a class="moz-txt-link-freetext" href="http://olpcMAP.net">http://olpcMAP.net</a> !</pre>
</body>
</html>