http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2448
Changes in build 2448 from build: 2444
Size delta: 0.00M
-kernel 2.6.25-20080915.5.olpc.abe7a66b36f344a
+kernel 2.6.25-20080916.1.olpc.658c681b23bec45
-rainbow 0.7.23-1.fc9
+rainbow 0.7.24-1.fc9
--
This mail was automatically
Hi Tony, list,
haven't had a chance to play much with the code. But I applied your
files on top of the latest 1.9, and tweaked lib/javascript.php in a
way that would be compatible with merging it upstream.
It's here
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2449
Changes in build 2449 from build: 2448
Size delta: 0.00M
-bootfw q2e17-1.olpc2.unsigned
+bootfw q2e18-1.olpc2.unsigned
--- Changes for bootfw q2e18-1.olpc2.unsigned from q2e17-1.olpc2.unsigned ---
+ trac 8426 - fixed B2 bricking
On Wed, Sep 17, 2008 at 5:37 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
I'm looking briefly at edublog's moodle code. Was hoping to be able to
cherry-pick the patches making the html editor changes, but your
initial moodle commit is with the _modified_ moodle already...?
ok. not all is lost.
On Sat, Sep 13, 2008 at 5:27 AM, Tarun Pondicherry
[EMAIL PROTECTED] wrote:
I'm curious how to get some bug fixes upstream into ou blog. I think its
not maintained by Moodle right? I'm trying to figure out also where to get
the latest ou blog code to see if those bugs are there. Mostly, just
Am 17.09.2008 um 07:26 schrieb John Gilmore:
The decision to tie application sharing to Mesh and Sugar was a bad
design idea, one which I've been intending to explore fixing.
As Benjamin pointed out, the sharing is *not* tied to the mesh. It
works just as well if both machines can receive
The problem comes from the OLPC marketing that equates mesh with
collaboration which in fact are two independent concepts. What the
UI displays as Mesh Server should be Collaboration Server - it's
only needed to mediate if the laptops who want to collaborate cannot
talk to each other
Am 17.09.2008 um 11:28 schrieb John Gilmore:
The problem comes from the OLPC marketing that equates mesh with
collaboration which in fact are two independent concepts. What the
UI displays as Mesh Server should be Collaboration Server - it's
only needed to mediate if the laptops who want to
I tried to move several tickets on it from blocking to blocked by, but
it looks like I confused trac. It started backtracing and now each of
the dependent bugs has stale information. Can someone with trac foo
fix it up? Or should we just recreate the tracker? This sucks mainly
because it breaks
Folks -
Well, now that we've met I suppose I should introduce myself g.
I started at OLPC as VP of Software Development last week, so I am still
catching up on everything that's happening. I have taken over all software
development responsibilities from Kim Quirk, who's now free to focus more
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2451
Changes in build 2451 from build: 2449
Size delta: 0.00M
-xkeyboard-config 1.3-3.olpc3
+xkeyboard-config 1.3-4.olpc3
--- Changes for xkeyboard-config 1.3-4.olpc3 from 1.3-3.olpc3 ---
+ Make view source work for all keyboards
Folks -
Thanks for the comments and input on how to communicate OLPC activities
better to our various audiences. I want to mention a few things in general
and also look at this specific situation.
I am happy to help better communicate software development activities to the
broader community.
On 17.09.2008 08:22, Mitch Bradley wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q2e18
This is the version that we hope to include in the 8.2 software bundle,
so please test it like crazy.
It won't brick B2s ...
Thanks for fixing this bug! Any chance you can give an assessment about
On Wed, Sep 17, 2008 at 5:05 AM, Bert Freudenberg [EMAIL PROTECTED] wrote:
Yes we do. I think that's just bad UI design - as far as I know the
school server is independent of the mesh, so it should not be labeled
mesh.
+1
I'll open a ticket on this now so it's not lost. Collaboration
server
Hi All,
Very interesting thread on the wireless, mesh and collaboration
technologies.
I think part of the discussion is a debate about what is the best
technology to achieve our goals.
In terms of what the goals are, I wrote a definition of what I think our
collaboration needs to do at:
On Wed, 2008-09-17 at 15:21 +1200, Douglas Bagnall wrote:
The xs-config package creates a file called /fsckoptions (yes, in /),
to stop headless servers from stalling on fsck questions.
How often are you actually getting to having fsck questions? ext3
partitions should be set up by default to
Carl-Daniel Hailfinger wrote:
On 17.09.2008 08:22, Mitch Bradley wrote:
http://wiki.laptop.org/go/OLPC_Firmware_q2e18
This is the version that we hope to include in the 8.2 software bundle,
so please test it like crazy.
It won't brick B2s ...
Thanks for fixing this bug! Any
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2452
Changes in build 2452 from build: 2451
Size delta: 0.00M
-telepathy-salut 0.3.3-6.olpc3
+telepathy-salut 0.3.3-8.olpc3
--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for
On 17 Sep 2008, at 10:28, John Gilmore wrote:
Then why can't my two XO's running 8.2-759, both connected to the same
access point, see each other to collaborate? Neither one shows up in
the other's Network screen. When I run Write on one, and enable
sharing
with My Neighborhood, that
benjamin m. schwartz wrote:
The wired-ethernet case is already working, and has been for a year or
more. Drop Sugar onto two Thinkpads connected to the same subnet, and
they will instantly find each other over Avahi, etc. If it's a wireless
network, or if you have XOs with ethernet
Then why can't my two XO's running 8.2-759, both connected to the same
access point, see each other to collaborate? Neither one shows up in
the other's Network screen. When I run Write on one, and enable sharing
with My Neighborhood, that copy of Write pops up on its own Neighborhood
On Wed, Sep 17, 2008 at 18:52, Gary C Martin [EMAIL PROTECTED] wrote:
On 17 Sep 2008, at 10:28, John Gilmore wrote:
Then why can't my two XO's running 8.2-759, both connected to the same
access point, see each other to collaborate? Neither one shows up in
the other's Network screen. When I
On Sep 17, 2008, at 5:28 AM, John Gilmore wrote:
The problem comes from the OLPC marketing that equates mesh with
collaboration which in fact are two independent concepts. What the
UI displays as Mesh Server should be Collaboration Server - it's
only needed to mediate if the laptops who want
Hi Martin,
Really sorry for the newb mistakes. This is my first time on a project
where the repository is actually significant. I'll be sure to pay close
attention to my commits in the future.
The Moodle I used as a base is from: http://korpelainen.net/weekly19.zip
linked from the forum
On IRC today, Greg asked me several questions. My responses are inline:
* How do we know when are ready to build a release snapshot?
Immediately after we publish a new release snapshot, I enter my
'waiting' state. In this waiting state, I wait for test results and
for new tickets to
John,
dlo#8354 is believed to be fixed in 8.2-760. Can you confirm or deny
this?
Thanks,
Michael
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
On Wed, Sep 17, 2008 at 1:26 AM, John Gilmore [EMAIL PROTECTED] wrote:
Ricardo Carrano said:
There are technical challenges in the way, but OLPC should keep
pushing this for the benefits it will bring. It seems a perfect fit
with the Mission.
Mesh and the Marvell WiFi chip have been two of
Hi!
Is there a way to delete all journal entries in a single step?
(maybe from the terminal tool?)
Regards,
Alejandro
--
Dr. Alejandro Fernández
LIFIA - Laboratorio de Investigación y Formación en Informática Avanzada
Facultad de Informática; Universidad Nacional de La Plata
Calles 50 y 115
La
Ed pointed out to me that I used a bit of jargon, 'release snapshot',
which I had not formerly introduced. By 'release snapshot', I mean a
build in a release stream (e.g. 8.2, rather than joyride) which is in
danger of becoming a release candidate should testing go well. To first
order, (signed)
Hi All,
We need to pick the activities we ship with 8.2 when its manufactured
for G1G1 users. Management needs to sign off on the final list as early
as next week.
Its not definitive but we want your input on what we should include.
What do you think are the most important activities to
On Wed, Sep 17, 2008 at 05:54:50PM -0300, Alejandro Fernandez wrote:
Hi!
Is there a way to delete all journal entries in a single step?
(maybe from the terminal tool?)
From the terminal or a console, this should do it:
mv ~olpc/.sugar/default/datastore ~olpc/.sugar/default/datastore.deleted
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2453
Changes in build 2453 from build: 2452
Size delta: 0.00M
-sugar-update-control 0.13-1
+sugar-update-control 0.14-1
--- Changes for sugar-update-control 0.14-1 from 0.13-1 ---
+ Trac #8502: clean up icon cruft in /tmp
+ Trac
On Wed, Sep 17, 2008 at 05:54:45PM -0400, Greg Smith wrote:
Hi All,
We need to pick the activities we ship with 8.2 when its manufactured
for G1G1 users.
[...]
What do you think are the most important activities to include?
Please pick up to 10 and put them in order of priority.
Going
On Thu, Sep 18, 2008 at 3:43 AM, Jeremy Katz [EMAIL PROTECTED] wrote:
How often are you actually getting to having fsck questions?
Hi Jeremy,
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in
Jeremy Katz wrote:
How often are you actually getting to having fsck questions? ext3
partitions should be set up by default to not run fsck unless it's
really really needed.
[Some dd'ing and pulling plugs later] Yes, it does seem so. I may
have been mis-conditioned by certain fsck-happy
hi Joshua,
Just to clarify:
Most of them
will be in locations with unreliable power - so they will switch off
when power gets cut.
I have run servers like this for a few years with ext3. I was surprised
how well it worked. I never got anything resembling file system
corruption. ext3
hi Greg
How do you tell what XS version you have installed? Someone tried the
usual way but it only gives me the Fedora version.
[EMAIL PROTECTED] ~]# cat /etc/redhat-release
Fedora release 7 (Moonshine)
Good question. Part of the answer is that that will work in 0.5 and onwards:
[EMAIL
On Thu, Sep 18, 2008 at 7:13 AM, Tarun Pondicherry
[EMAIL PROTECTED] wrote:
Really sorry for the newb mistakes. This is my first time on a project
where the repository is actually significant. I'll be sure to pay close
attention to my commits in the future.
Hey - no problem.
The Moodle I
On Thu, Sep 18, 2008 at 11:53 AM, Martin Langhoff
[EMAIL PROTECTED] wrote:
Anyway, I believe I should be cleaning up the messes I create, so I'll try
to write two patches based on the current moodle-r2 code in catalyst (1-
enable tinyMCE, 2-integrate the Sugar theme). With some luck I should
On Thu, Sep 18, 2008 at 9:56 AM, Greg Smith [EMAIL PROTECTED] wrote:
How do you tell what XS version you have installed? Someone tried the
usual way but it only gives me the Fedora version.
Douglas has the answer for 0.5 onwards. For earlier releases,
rpm -qa xs-config
and match it with the
On Thu, Sep 18, 2008 at 3:43 AM, Jeremy Katz [EMAIL PROTECTED] wrote:
How often are you actually getting to having fsck questions?
Hi Jeremy,
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in
On Thu, Sep 18, 2008 at 12:49:22PM +1200, Martin Langhoff wrote:
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in locations with unreliable power - so they will switch off
when power gets
On Thu, Sep 18, 2008 at 12:49:22PM +1200, Martin Langhoff wrote:
good question. In the field, the XS machines never get switched off -
they are headless, and set in the bios to auto-switch-on. Most of them
will be in locations with unreliable power - so they will switch off
when power gets
On Thu, Sep 18, 2008 at 1:46 PM, Joshua N Pritikin [EMAIL PROTECTED] wrote:
I have run servers like this for a few years with ext3. I was surprised
how well it worked. I never got anything resembling file system
corruption. ext3 worked like a charm.
Good to hear!
What tended to fail was the
44 matches
Mail list logo
