<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Martin Langhoff wrote:
<blockquote
cite="mid:46a038f90810081806n55fa1act14566af90059b34b@mail.gmail.com"
type="cite">
<pre wrap="">On Thu, Oct 9, 2008 at 10:44 AM, Reuben K. Caron <a class="moz-txt-link-rfc2396E" href="mailto:reuben@laptop.org"><reuben@laptop.org></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Great, thanks. I was steered to the correct files and got it to work from
both the USB and command line. The files I used can be found at:
</pre>
</blockquote>
<pre wrap=""><!---->
Cool. Are you doing this on xs-0.5? If you update to the newest rpms
from the olpcxs-testing repo you'll get a nice chime indicating that
it started, and another nice chime meaning "I'm done".
</pre>
</blockquote>
I'm using xs-0.4. I'll look forward to that feature in .5 as the chime
will be much nicer then monitoring the progress of
tmp->xo-builds->pub/builds.<br>
<blockquote
cite="mid:46a038f90810081806n55fa1act14566af90059b34b@mail.gmail.com"
type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">Out of curiosity why do we require the tree files which come from:
<a class="moz-txt-link-freetext" href="http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/build767/devel_jffs2/">http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/build767/devel_jffs2/</a>
</pre>
</blockquote>
<pre wrap=""><!---->
I'm just following what Scott did for his own rsync updater server. I
didn't get into the details of why -- as a matter of expediency, I did
my bit of cargo-cult programming there :-)
In other words: monkey-see, martin-do
</pre>
</blockquote>
ah ha! gotcha, thanks.<br>
</body>
</html>