Re: ANN: 8.1.1 Candidate Build - candidate-708

[S Page]

Michael Stone wrote:
> Dear world,
>
> I'm pleased to announce that our first signed release candidate for the
> 8.1.1 bugfix release is now available for downloading and updating.
> Please help test it by

I did, it basically worked fine with some minor glitches (marked ==>
below).  Thanks!

>
>   1. Procuring activities if you need them. See the release notes for
>   details.

(I had updated my G1G1 to 703 a few weeks ago.  For some reason
installing the G1G1 activity pack from my USB flash drive didn't work
for me and I had used Bert's script to install.)

>   2a. olpc-update -f candidate-708 && reboot

D'oh, first time I didn't use the -f option.  `olpc-update
candidate-708` displayed

Trying irsync_pristine update from
rsync://updates.laptop.org/build-candidate-708
...
Verifying update.
Contents manifest failure at line 383
Last file examined: localtime

(Maybe that's why you said use -f.)

Then it went on to

Trying irsync_dirty update from
rsync://updates.laptop.org/build-candidate-708
  - Creating contents for existing tree.
Traceback (most recent call last):
   File "/usr/sbin/olpc-contents-create", line 90, in 
...
   File "/usr/lib/python2.5/ utils.py, line 100, in mkdirobject
entry['h'] = mkhashes (file(fullname), read())
MemoryError

so I pressed Ctrl-C.

Entering
   # free -m
printed
Mem: total 232, used 227, free 5, shared 0, buffers 0, cached 48

==> Should update instructions suggest that users first stop running
activities, or is this python "MemoryError" just an artifact of not
using the -f "skip incremental update attempt" flag?

Anyway, I retried using `olpc-update -f candidate-708` as instructed.
It printed:

   WARNING: You seem to be attempting to download an unsigned
development build, but you don't have a developer key.  This will
probably fail.

==> Is that warning expected since you said "signed release candidate" ?

but it updated fine anyway.

My laptop restarted three times, the last one brought me into Sugar.

Home view > little guy > About this XO displays
   Build update.1 708
   Firmware: Q2D16
   Serial Number: CSN748011C2


==> Maybe "About this XO" should say "8.1.1" and/or "candidate" instead
of "update.1" part, otherwise looks fine!

> please help update the 
>   http://wiki.laptop.org/go/OLPC_8.1.1_Software_Release_Notes

I reorganized it a bit to focus first on changes from Update.1, and
tweaked other referenced pages.

HTH, XO FTW, BBL,
--
=S Page

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

NM 0.7 D-Bus API Mini-Tutorial

[Michael Stone]

I got curious about how NM-0.7 works so I installed it on olpc3-17 by:

  sed -i -e '6s/enabled=0/enabled=1/' /etc/yum.repos.d/fedora.repo
  iwconfig eth0 mode managed essid 'media lab 802.11'
  killall dhclient 
  dhclient eth0
  yum -yt --nogpgcheck update NetworkManager
  /etc/init.d/NetworkManager restart

Then, with help from Michael Biebl and Rob McQueen, with two important
pieces of documentation

  http://debs.michaelbiebl.de/network-manager/spec.html
  
http://dbus.freedesktop.org/doc/dbus-specification.html#standard-interfaces-properties

and with the excellent interactive IPython shell, I was able to create a
silly script which uses the NM-0.7 interfaces to list visible access
points. I present it on the off chance that it might serve as a helpful
introduction for other people who would like to help us port the Sugar
UI to the new API (or who would like to change NM-0.7 to better support
our hardware and networking configuration.) The script is attached.

Regards,

Michael

NMI = 'org.freedesktop.NetworkManager'
NMD = 'org.freedesktop.NetworkManager.Device'
NMDW = 'org.freedesktop.NetworkManager.Device.Wireless'
NMA = 'org.freedesktop.NetworkManager.AccessPoint'
DBP = 'org.freedesktop.DBus.Properties'

def ii(o):
print o.Introspect(dbus_interface="org.freedesktop.DBus.Introspectable")

import dbus
bus = dbus.SystemBus()
nmo = bus.get_object(NMI, '/' + NMI.replace('.','/'))
ii(nmo)


nmi = dbus.Interface(nmo, NMI)
nmp = dbus.Interface(nmo, DBP)
nmp.Get(NMI, 'WirelessEnabled')
nmp.Get(NMI, 'WirelessHardwareEnabled')

for dev_pth in nmi.GetDevices():
devo = bus.get_object(NMI, dev_pth)
ii(devo)

devi = dbus.Interface(devo, NMD)
devw = dbus.Interface(devo, NMDW)
devp = dbus.Interface(devo, DBP)
devp.Get(NMD, 'DeviceType')
devp.Get(NMD, 'Managed')

for ap_pth in devw.GetAccessPoints():
apo = bus.get_object(NMI, ap_pth)
print ''.join([chr(x) for x in apo.Get(NMA, "Ssid", 
dbus_interface=DBP)])
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Upgrade G1G1 using autoreinstallation method

[David Leeming]

How can I upgrade G1G1 XO-1s using the auto-reinstallation method with a
flash drive? We have 100 to update here in PNG and it is impossible to use
olpc-update as the connectivity is so poor. We have a flash drive with the
new image 703 on it, and I successfully updated a B4. But when I try a G1G1
laptop, even with pressing the game keys it just boots normally without
updating. I know I have some gaps in my knowledge regarding the keys and
security for the G1G1 laptops, but unfortunately I need a quick answer. Much
appreciate any help.

 

David Leeming

Deploying in PNG

http://wiki.laptop.org/go/OLPC_Oceania

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Games depending on OpenGL and GLX - any way to test on XO with regular OLPC image?

[Daniel Monteiro Basso]

My apologies, that was not complete. I made the XVideo output code 
separated from the TinyGL, and now I attached it to this e-mail 
(xogltests.tgz). But even that is not the latest version, which it seems 
I lost... :\


I tried to run it on the XO, but since my upgrade to Ubuntu 8.04, there 
is a glibc version incompatibility.


[the world should come with a 'pause' button... I really would like to 
be more helpful, but I don't have much time available for this right now]


Daniel

Bert Freudenberg escreveu:
Ah, cool, this even includes binaries in the examples dir, so it is 
ready to try on the XO :)


I did not see any XV-based scaling though - anything I need to enable?

- Bert -

On 10.06.2008, at 17:42, Daniel Monteiro Basso wrote:




xogltests.tgz
Description: application/compressed-tar
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: thread summary: On Cerebro, Telepathy, yokes and whites

[Kim Quirk]

Nice summary Pol!

Kim

On Wed, Jun 11, 2008 at 2:22 PM, Polychronis Ypodimatopoulos <[EMAIL PROTECTED]>
wrote:

> This is a summary (a la Michael) of the cerebro/telepathy thread.
>
> Pol brought up the issue of how the collaboration stack is currently
> implemented, that there should be a dead-simple networking API for
> activity development and proposed someone taking the lead in
> implementing a connection manager for cerebro (which currently offers a
> D-Bus API).
> http://lists.laptop.org/pipermail/devel/2008-June/015238.html
>
> Ben suggested that there is no need to abstract telepathy further
> because it's an abstraction layer in itself. Instead, API changes should
> be proposed, if any exist.
> http://lists.laptop.org/pipermail/devel/2008-June/015239.html
>
> Ricardo suggested that there should be someone working on a cerebro
> connection manager in parallel with jabber.
> http://lists.laptop.org/pipermail/devel/2008-June/015248.html
>
> Marco and Tomeu agreed that there should be a cerebro connection
> manager, Marco conceded to getting cerebro in joyride, but disagreed
> with adding an abstraction layer between telepathy and sugar/activities
> on the basis that telepathy is abstraction layer in itself and we must
> live with what is currently available for lack of resources and because
> compromises are often made in large software projects.
> http://lists.laptop.org/pipermail/devel/2008-June/015226.html
> http://lists.laptop.org/pipermail/devel/2008-June/015254.html
>
> Scott brought up the issue of children invariably trying to develop a
> multi-player game on sugar and failing because of the complexity of the
> collaboration API. Marco agreed with this problem and recognized the
> need for a python layer above telepathy/cerebro that can be invoked
> without DBus, while a lower level DBus-based API will be used by
> non-python activities. Both Marco and Scott saw the need for extensive
> tutorials and examples on how to use any networking API for activity
> development.
> http://lists.laptop.org/pipermail/devel/2008-June/015255.html
>
> Kim would like to figure out how to make progress on cerebro.
> http://lists.laptop.org/pipermail/devel/2008-June/015261.html
>
> Robert characterized telepathy primarily as an API to a variety of
> functionality and different communication mechanisms, recognized some
> problems in the implementation and the need for cerebro as one of the
> plans to deal with those problems. He also went through the history of
> how D-Tubes and stream tubes came about and noted that the requirements
> were not really clear when their (D-Tubes and stream tubes)
> implementation started. He also recognized the need to hide some of the
> complexities of network programming by adding a simplifying layer on top
> of telepathy, or by extending the current telepathy API.
> http://lists.laptop.org/pipermail/devel/2008-June/015262.html
> http://lists.laptop.org/pipermail/devel/2008-June/015258.html
>
> Finally, Morgan went through the history of how the Presence Service was
> implemented, that it predates the use of telepathy and that it contains
> some "interesting", to put it politely, design aspects. He also went
> through his efforts to simplify the implementation of collaboration in
> activities by pushing the telepathy functionality from the activities
> into the PS where possible and his plans to simplify further
> collaboration in activities.
> http://lists.laptop.org/pipermail/devel/2008-June/015274.html
>
> Tomeu also suggested getting this summary together (thanks!) and that it
> may make sense to separate discussion on the API from discussion on the
> current implementation.
>
> I hope I captured the most important parts of this threads, feel free to
> blame me if I failed in any parts.
>
> Pol
>
>
> --
> Polychronis Ypodimatopoulos
> Graduate student
> Viral Communications
> MIT Media Lab
> Tel: +1 (617) 459-6058
> http://www.mit.edu/~ypod/ 
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New faster build 2032

[Build Announcer v2]

http://xs-dev.laptop.org/~cscott/olpc/streams/faster/build2032

Changes in build 2032 from build: 2029

Size delta: 0.00M

-olpcrd 0.41-0
+olpcrd 0.42-0
-libcdio 0.78.2-4.fc7
+libcdio 0.78.2-5.fc7

--- Changes for libcdio 0.78.2-5.fc7 from 0.78.2-4.fc7 ---
  + fixed security fix (was off by two)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/faster-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

New joyride build 2032

[Build Announcer v2]

http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2032

Changes in build 2032 from build: 2029

Size delta: 0.00M

-olpcrd 0.41-0
+olpcrd 0.42-0
-libcdio 0.78.2-4.fc7
+libcdio 0.78.2-5.fc7

--- Changes for libcdio 0.78.2-5.fc7 from 0.78.2-4.fc7 ---
  + fixed security fix (was off by two)

--
This mail was automatically generated
See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs
See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a 
comparison
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Additional slides from May 23, 2008 Country Meetings

[C. Scott Ananian]

I received a few more slides for talks given May 23, and posted them at:
   http://wiki.laptop.org/go/Presentations/May_2008_Country_Workshop

I also got slides from Mitchel Resnick's talk on May 20.

Enjoy!
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Questions about Customization Dirs

[Dafydd Harries]

Ar 10/06/2008 am 23:57, ysgrifennodd Michael Stone:
> 
> A while ago, Walter mentioned that we'd like to be able to customize things
> like keyboard and internationalization settings. These settings are loaded by 
> a
> program called 'olpc-session' maintained in the olpc-utils package.
> 
> Unfortunately, when I set out to implement support for this feature, I
> discovered two questions which I couldn't answer:
> 
>  1) What should we call the customizations directory?
> 
>~/customizations
>~/.customizations
>~/.envdir ?
>~/

I lean towards preferring .-prefixed names.

>  2) How should we process the contents?
> 
>At present, olpc-session _sources_ ~/.kbd and ~/.i18n. If we permit these
>files to be modified by customization key, then we have immediately offered
>any attacker a root-level shell injection attack available on the next
>reboot.
> 
>Can we force these files to match strict (safe) regular expressions? 

Seems like an entirely reasonable requirement...

>Should we write a careful parser for the intended values?

...therefore this should be doable.

-- 
Dafydd
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Connector spec for XO power connector

[Richard A. Smith]

Joshua Seal wrote:
> Please find the info you are after here.
> 
> http://wiki.laptop.org/go/Battery_and_power#Mechanical
> 
> http://wiki.laptop.org/go/Talk:Battery_and_power#Power_Input_Plug

Note that digikey

CP-014-ND

Does NOT work. Its not long enough.  I need to get it stricken from the 
wiki.

CP-2195-ND and CP-2195-ND both work but there is just enough slop in the 
outer barrel that if you pull sideways on the connector it can break 
contact.

A user has sent me mail claiming to have done a sweep of compatible 
connectors and that he was going to put it up for consumption somewhere 
I'll see if I can get him to send me his data.

-- 
Richard Smith  <[EMAIL PROTECTED]>
One Laptop Per Child
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

RE: Connector spec for XO power connector

[Joshua Seal]

Please find the info you are after here.

http://wiki.laptop.org/go/Battery_and_power#Mechanical

http://wiki.laptop.org/go/Talk:Battery_and_power#Power_Input_Plug

Kind regards,


Josh

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Marcus Leech
Sent: 11 June 2008 19:19
To: [EMAIL PROTECTED]
Subject: Connector spec for XO power connector

Is there a pointer to (for example) a Digi-key part number for the DC 
power connector for the XO?

I think I want to clean up the power situation in the lab, and run a 
bunch of XOs off of one or more
  clean DC supplies


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

thread summary: On Cerebro, Telepathy, yokes and whites

[Polychronis Ypodimatopoulos]

This is a summary (a la Michael) of the cerebro/telepathy thread.

Pol brought up the issue of how the collaboration stack is currently 
implemented, that there should be a dead-simple networking API for 
activity development and proposed someone taking the lead in 
implementing a connection manager for cerebro (which currently offers a 
D-Bus API).
http://lists.laptop.org/pipermail/devel/2008-June/015238.html

Ben suggested that there is no need to abstract telepathy further 
because it's an abstraction layer in itself. Instead, API changes should 
be proposed, if any exist.
http://lists.laptop.org/pipermail/devel/2008-June/015239.html

Ricardo suggested that there should be someone working on a cerebro 
connection manager in parallel with jabber.
http://lists.laptop.org/pipermail/devel/2008-June/015248.html

Marco and Tomeu agreed that there should be a cerebro connection 
manager, Marco conceded to getting cerebro in joyride, but disagreed 
with adding an abstraction layer between telepathy and sugar/activities 
on the basis that telepathy is abstraction layer in itself and we must 
live with what is currently available for lack of resources and because 
compromises are often made in large software projects.
http://lists.laptop.org/pipermail/devel/2008-June/015226.html
http://lists.laptop.org/pipermail/devel/2008-June/015254.html

Scott brought up the issue of children invariably trying to develop a 
multi-player game on sugar and failing because of the complexity of the 
collaboration API. Marco agreed with this problem and recognized the 
need for a python layer above telepathy/cerebro that can be invoked 
without DBus, while a lower level DBus-based API will be used by 
non-python activities. Both Marco and Scott saw the need for extensive 
tutorials and examples on how to use any networking API for activity 
development.
http://lists.laptop.org/pipermail/devel/2008-June/015255.html

Kim would like to figure out how to make progress on cerebro.
http://lists.laptop.org/pipermail/devel/2008-June/015261.html

Robert characterized telepathy primarily as an API to a variety of 
functionality and different communication mechanisms, recognized some 
problems in the implementation and the need for cerebro as one of the 
plans to deal with those problems. He also went through the history of 
how D-Tubes and stream tubes came about and noted that the requirements 
were not really clear when their (D-Tubes and stream tubes) 
implementation started. He also recognized the need to hide some of the 
complexities of network programming by adding a simplifying layer on top 
of telepathy, or by extending the current telepathy API.
http://lists.laptop.org/pipermail/devel/2008-June/015262.html
http://lists.laptop.org/pipermail/devel/2008-June/015258.html

Finally, Morgan went through the history of how the Presence Service was 
implemented, that it predates the use of telepathy and that it contains 
some "interesting", to put it politely, design aspects. He also went 
through his efforts to simplify the implementation of collaboration in 
activities by pushing the telepathy functionality from the activities 
into the PS where possible and his plans to simplify further 
collaboration in activities.
http://lists.laptop.org/pipermail/devel/2008-June/015274.html

Tomeu also suggested getting this summary together (thanks!) and that it 
may make sense to separate discussion on the API from discussion on the 
current implementation.

I hope I captured the most important parts of this threads, feel free to 
blame me if I failed in any parts.

Pol


-- 
Polychronis Ypodimatopoulos
Graduate student
Viral Communications
MIT Media Lab
Tel: +1 (617) 459-6058
http://www.mit.edu/~ypod/

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Connector spec for XO power connector

[Marcus Leech]

Is there a pointer to (for example) a Digi-key part number for the DC 
power connector for the XO?

I think I want to clean up the power situation in the lab, and run a 
bunch of XOs off of one or more
  clean DC supplies


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Questions about Customization Dirs

[Hal Murray]

> Why not
> ~/.olpc
> or
> ~/.olpcsession
> which would match the "olpc-session" program name? 

Matching the program name seems like a great idea to me.

I vote for including the "-" too, thus
  ~/.olpc-session

[The idea is to make it easier to track down who/what program/package a name 
is associated with.]


-- 
These are my opinions, not necessarily my employer's.  I hate spam.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: While we're on Cerebro, Telepathy, etc... Cerebro + bitfrost?

[Ivan Krstić]

On Jun 11, 2008, at 3:03 PM, Jameson Chema Quinn wrote:
> If Bert is right, and this is the unstated general plan, then great!

While not made explicit in the spec, this is indeed the design and the  
way it was discussed with the Collabora people.

--
Ivan Krstić <[EMAIL PROTECTED]> | http://radian.org

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Games depending on OpenGL and GLX - any way to test on XO with regular OLPC image?

[Bert Freudenberg]

Ah, cool, this even includes binaries in the examples dir, so it is  
ready to try on the XO :)

I did not see any XV-based scaling though - anything I need to enable?

- Bert -

On 10.06.2008, at 17:42, Daniel Monteiro Basso wrote:

>
> Ok, it's available at:
>
> http://www.inf.ufrgs.br/~dmbasso/TinyGL4XO.tgz
>
> I just packed my git repository, so you may check exactly what the
> changes were. Although I don't have time to work on it right now, I'll
> answer any questions you might have.
>
> Daniel
>
> Benjamin M. Schwartz escreveu:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Daniel Monteiro Basso wrote:
>> | I adapted TinyGL to render to an arbitrary sized framebuffer, later
>> | scaled to fullscreen with the xvideo extension. I currently don't  
>> have
>> | time to work on it, but if anyone is interested, I'll send the  
>> code.
>> |
>>
>> I can think of a number of people who might be interested in that  
>> code.
>> Please post it.
>>
>> Thank you,
>> Ben Schwartz
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkhN0osACgkQUJT6e6HFtqRWmwCggRddTctRrvj95bSblBjiIWFn
>> lcgAnjzkBfBKdRlCi2tiOxwv/jwLxO44
>> =IOdu
>> -END PGP SIGNATURE-
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Need advice to upgrade

[Kim Quirk]

We have been having similar problems in the office (tons of RF, if that
matters), where one laptop can successfully connect to a WPA client and
another one can't; or the same laptop might not be able to on a second or
third attempt.

If it worked once, it is likely that you can get it to work again... but
clearly this is a bug. I started a new trac item, 7257.

I am also experimenting with removing the config file:
/home/olpc/.sugar/default/nm/network.config and rebooting. This has worked
for me occasionally in the past. I'm still not sure if it is related to
removing the config file, rebooting, or just timing...

Others, please put your notes into this trac item.

Thanks,
Kim


On Wed, Jun 11, 2008 at 8:36 AM, Bert Freudenberg <[EMAIL PROTECTED]>
wrote:

> On 11.06.2008, at 14:05, Jim Gettys wrote:
>
> > My memory is that you may have one of the two known access point types
> > with which we have problems, due to the chip/firmware used in that
> > access point (note the pre-N designation).  Michailis will know for
> > sure, and it's probably recorded in our Trac system.
> >
> > Due to the very small population of those routers, (if my memory is
> > indeed correct) we're unlikely to explicitly try to fix it.
>
>
> Oh. I had the impression that the WPA problems are well known and so I
> did not bother to report anymore. Are you implying it *should* work?
>
> - Bert -
>
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Wednesday videos are up.

[C. Scott Ananian]

At long last, the videos for the 5-21 country workshop talks are up:
  http://wiki.laptop.org/go/Presentations/May_2008_Country_Workshop

It doesn't appear that we taped the initial 'Sugar' talk, and we
missed a bit of the beginning of Jim's 'Localization' talk, but we've
got complete talks on Connectivity, "the Uruguay experience", and the
school server for your education and enjoyment.

Note that these videos are much harder to watch because there was no
camera person!  Compare to the Tuesday videos, which did have a good
camera operator.  If you are local to the Boston area, I would love
help with future talks to ensure (a) that they are recorded & encoded,
and (b) that a camera operator makes them pleasant to watch!

Julia, are there videos of the Thursday and Friday sessions, or is this it?

SJ, Mako, and David Cavallo, I'm still waiting for your Friday slides...
 --scott

-- 
 ( http://cscott.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Need advice to upgrade

[Gary Oberbrunner]

Bert Freudenberg wrote:
> On 11.06.2008, at 14:05, Jim Gettys wrote:
> 
>> My memory is that you may have one of the two known access point types
>> with which we have problems, due to the chip/firmware used in that
>> access point (note the pre-N designation).  Michailis will know for
>> sure, and it's probably recorded in our Trac system.
>>
>> Due to the very small population of those routers, (if my memory is
>> indeed correct) we're unlikely to explicitly try to fix it.
> 
> 
> Oh. I had the impression that the WPA problems are well known and so I  
> did not bother to report anymore. Are you implying it *should* work?

Ditto.  My stock WAP54G router with WPA/PSK still almost never works, as 
of faster builds of a month or so ago.  I stopped upgrading my XO when I 
thought the activities would all go away; need to get back to it -- but 
lack of wifi access slows things down.

-- 
Gary Oberbrunner
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Need advice to upgrade

[Michael Stone]

On Wed, Jun 11, 2008 at 02:36:11PM +0200, Bert Freudenberg wrote:
> On 11.06.2008, at 14:05, Jim Gettys wrote:
> 
> > My memory is that you may have one of the two known access point types
> > with which we have problems, due to the chip/firmware used in that
> > access point (note the pre-N designation).  Michailis will know for
> > sure, and it's probably recorded in our Trac system.
> >
> > Due to the very small population of those routers, (if my memory is
> > indeed correct) we're unlikely to explicitly try to fix it.
> 
> 
> Oh. I had the impression that the WPA problems are well known and so I  
> did not bother to report anymore. Are you implying it *should* work?

Depends on the build. See #7247 and #7253 for examples.

Michael
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: TWIN (tiny window manager) on XO.

[Bastien]

Bert Freudenberg <[EMAIL PROTECTED]> writes:

> On 11.06.2008, at 15:18, Bastien wrote:
>
>> Other question: when stuck with a graphical display that doesn't
>> take any keyboard/mouse event, how to come back to a tty?  Usual
>> GNU/Linux Alt-F1 and the like don't work.
>
> The usual shortcut is ctrl-alt-F1, and it works for me. If not, then you
> seriously hosed your system (iow, that should not happen).

Will test again with Ctrl-Alt-F1.  

No idea about what could be wrong with stumpwm?

-- 
Bastien
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Games depending on OpenGL and GLX - any way to test on XO with regular OLPC image?

[Bert Freudenberg]

Thanks.

I have not looked at it yet, but I noticed that when running Xubuntu  
on the XO, the OpenGL screen savers actually perform surprisingly well  
(gears, stoner, pipes). So if you only have a few objects with flat  
(maybe Gouraud) shading, then even Mesa is okay ...

- Bert -

On 10.06.2008, at 17:42, Daniel Monteiro Basso wrote:

>
> Ok, it's available at:
>
> http://www.inf.ufrgs.br/~dmbasso/TinyGL4XO.tgz
>
> I just packed my git repository, so you may check exactly what the
> changes were. Although I don't have time to work on it right now, I'll
> answer any questions you might have.
>
> Daniel
>
> Benjamin M. Schwartz escreveu:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Daniel Monteiro Basso wrote:
>> | I adapted TinyGL to render to an arbitrary sized framebuffer, later
>> | scaled to fullscreen with the xvideo extension. I currently don't  
>> have
>> | time to work on it, but if anyone is interested, I'll send the  
>> code.
>> |
>>
>> I can think of a number of people who might be interested in that  
>> code.
>> Please post it.
>>
>> Thank you,
>> Ben Schwartz
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.9 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>>
>> iEYEARECAAYFAkhN0osACgkQUJT6e6HFtqRWmwCggRddTctRrvj95bSblBjiIWFn
>> lcgAnjzkBfBKdRlCi2tiOxwv/jwLxO44
>> =IOdu
>> -END PGP SIGNATURE-
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: TWIN (tiny window manager) on XO.

[Bert Freudenberg]

On 11.06.2008, at 15:18, Bastien wrote:

> Other question: when stuck with a graphical display that doesn't
> take any keyboard/mouse event, how to come back to a tty?  Usual
> GNU/Linux Alt-F1 and the like don't work.

The usual shortcut is ctrl-alt-F1, and it works for me. If not, then  
you seriously hosed your system (iow, that should not happen).

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: EduBlog Project hosting application

[marcel r]

Any updates on this please ?
We are already started on the project and would like to use the git.

Marcel


On Mon, May 26, 2008 at 11:23 PM, marcel r <[EMAIL PROTECTED]> wrote:

> I attached the hosting application and 2 public key files.
> I read the discussion on rsa vs dsa, but are both methods supported ?
> If not I will attach de correct key.
>
> Thanks in advance!
>
> Marcel
>
>
>
>
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Fwd: TWIN (tiny window manager) on XO.

[Bastien]

While speaking about light window managers...  anyone tried to install
and run stumpwm?

http://www.nongnu.org/stumpwm

I've been able to install SBCL, then to compile stumpwm.  But when
calling the executable from ~/.xinitrc, the screen get blank and I
don't have any keyboard/mouse.

I tried this on a recent 703 build.

Other question: when stuck with a graphical display that doesn't 
take any keyboard/mouse event, how to come back to a tty?  Usual
GNU/Linux Alt-F1 and the like don't work.  

Thanks!

-- 
Bastien
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: TWIN (tiny window system) on XO.

[Arnd Bergmann]

On Wednesday 11 June 2008, Bert Freudenberg wrote:
> > It's currently using the X11 display, but there is also an SDL  
> > backend.
> 
> 
> Would be interesting to see on fbdev ...
> 
> While the XO actually has plenty of RAM, we're currently wasting a ton  
> of it. I'm glad to see experiments for reducing the footprint :)

It is being used by the 'petitboot' graphical boot loader on the
PlayStation 3, using fbdev, and works very well there.

The problem is mostly the lack of applications for it, to make it
really useful.

Arnd <><
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: While we're on Cerebro, Telepathy, etc... Cerebro + bitfrost?

[Jameson "Chema" Quinn]

On Wed, Jun 11, 2008 at 3:08 AM, Bert Freudenberg <[EMAIL PROTECTED]>
wrote:

> On 11.06.2008, at 03:37, Jameson Chema Quinn wrote:
>
>  Thus, there would be three kinds of activities:
>>
>> those with full network access, able to talk to arbitrary IP addresses
>> (browse is inescapably in this category);
>>
>> those with some kind of "telepathy-only" access, which would only let them
>> talk to IP addresses that correspond to a friend sharing the specific
>> activity instance (Chat might fit here; certainly, Write would);
>>
>> and those with no network permissions.
>>
>> The telepathy-only, middle security level would allow the last two "good"
>> use cases, while preventing the last two "bad" use cases. It could be
>> implemented by sugar giving them some kind of key, valid only for that
>> specific instance (and renewed when the instance is resumed) that they could
>> use to "unlock" access to a given IP. I understand that the middle security
>> level would not necessarily be perfect - a man-in-the-middle attack could
>> well subvert any gains, and, especially in early versions, it would be hard
>> to guarantee that any abstraction layer was 100% successful at keeping
>> malformed requests from getting some illicit control over a lower layer -
>> but it would drastically reduce the practicality of any large-scale
>> snoop-net or bot-net for your average shareable activity. Assuming that the
>> connection to friend X was compromised; an activity would still have to hope
>> it was started with an instance that had been shared with friend X in order
>> to leak any data.
>>
>
>
> Err, hasn't that been the plan all along? P_NETWORK is only given to
> activities needing full network access. It is independent of sharing. An
> activity wanting to share must use telepathy, period. Your "no network
> permissions" above case does not exist separately, it is the same as
> "telepathy-only".
>
> - Bert -
>


It is great to hear that this is not a new idea. Looking back at the
implementation speculation, m_stone's
http://cr.yp.to/unix/disablenetwork.html idea would, of course, not prevent
access to a service like Telepathy which is available over DBus. Still, from
my outsider perspective, it is not quite fair to say that it is "the plan
all along". Here's what I've seen of the plan: (the bitfrost spec, emphasis
mine):

"Each program's network utilization can be constrained in the following
ways:

   - * Boolean network on/off restriction*
   - token-bucketed bandwidth throttling with burst allowance
   - connection rate limiting
   - * packet destination restrictions by host name, IP and port(s)*
   - time-of-day restrictions on network use
   - data transfer limit by hour or day
   - server restriction (can bind and listen on a socket), Boolean and
   per-port

Reasonable default rate and transfer limits will be imposed on all
non-signed programs. If necessary, different policies can apply to mesh and
access point traffic. Additional restrictions might be added to this list as
we complete our evaluation of network policy requirements. "
Neither of the relevant points makes any reference to poking holes in this
"firewall" for collaboration.

Also, there are some features in Telepathy/whatever that would be needed to
give it security characteristics

In order for an abstraction layer to have security characteristics, it would
probably need to:
-be in a separate process, communicating through DBus; done.
-Not allow an activity to do anything by itself that would be visible on the
network, except for maybe announcing its (un)willingness to share. The
network-visible name of the activity would be set by Glucose, sharing
partners would be set from Glucose (including any search, invitations, and
responses, as well as handling resuming shared instances). It is not my
impressiong that Telepathy worries about this kind of security; if I am
wrong, such thinking should certainly be documented.

...

I opened this thread to understand how people felt about this idea. If Bert
is right, and this is the unstated general plan, then great! I am not just
saying "you guys oughtta", I can start to look at this issue and post much
more specific bugs to continue the conversation on an implementation level.

Jameson
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Need advice to upgrade

[Bert Freudenberg]

On 11.06.2008, at 14:05, Jim Gettys wrote:

> My memory is that you may have one of the two known access point types
> with which we have problems, due to the chip/firmware used in that
> access point (note the pre-N designation).  Michailis will know for
> sure, and it's probably recorded in our Trac system.
>
> Due to the very small population of those routers, (if my memory is
> indeed correct) we're unlikely to explicitly try to fix it.


Oh. I had the impression that the WPA problems are well known and so I  
did not bother to report anymore. Are you implying it *should* work?

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Need advice to upgrade

[Jim Gettys]

My memory is that you may have one of the two known access point types
with which we have problems, due to the chip/firmware used in that
access point (note the pre-N designation).  Michailis will know for
sure, and it's probably recorded in our Trac system.

Due to the very small population of those routers, (if my memory is
indeed correct) we're unlikely to explicitly try to fix it.
- Jim


On Wed, 2008-06-11 at 10:09 +0200, NoiseEHC wrote:
> Hello,
> 
> I have just received my XO via the Developers Program. The machine is 
> working nicely, but there is a problem connecting to my wireless router 
> (Belkin Pre-N F5D8230-4) which uses WPA-PSK with AES encription. The XO 
> just asks for the password over and over again. The strange thing that 
> connecting did succeed several days ago so I could request a developer 
> key but since then nothing... (Today I have switched to channel 11 from 
> channel AUTO but no effect.)
> 
> 1. So my question is: do I need to upgade to some more recent FW/build? 
> Is it a known problem with build 656 (stream ship.2) which I have?
> 
> Normally I would not spam the devel list with this support request but I 
> have some more questions:
> 
> 2. I could not find anywhere what the LEDs do on the XO. It can be that 
> I am just stupid or blind but there is an option that it was so evident 
> for every 1CC employee that the explanation was missed somehow. The only 
> thing that I could find is this:
> http://wiki.laptop.org/go/Image:Drawing75c1.jpg
> I can deduce all the LEDs' meaning except the leftmost two:
> a. The lollipop LED is Wireless acquisition. What exactly does it mean?
> b. The tie-fighter LED is Wireless activity. Is it send or receive or 
> both? Is it the wireless chip or the TCP/IP stack or what?
> 
> 3. Some time ago cscott told me how to kill stuff if I want to measure 
> speed.
> telinit 3
> ifconfig msh0 down
> ifconfig eth0 down
> After that the lollipop and tie-figher are both blinking randomly (and I 
> got msh0: link becomes ready message to the console). Does it still 
> switches off things? If not what should I use?
> 
> 4. How is the rebasing on FC9 is going?
> I am just asking because sooner or later I will finish the Geode docu 
> and will start to develop drivers. Since I am not a Linux guru, I could 
> not setup my FC7 VirtualPC image to compile the kernel, I was able only 
> to write kernel modules with FC8. So if it is possible, I would avoid 
> fighting the kernel build process on FC6 or FC7 and so I would like to 
> know what to expect?
> 
> 5. What image should I upgrade to? What is that "faster build"?
> I currently only using the text-mode console so it is not a problem for 
> me if no activity works or something like that (if the wireless works).
> 
> Thank you!
> 
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
-- 
Jim Gettys <[EMAIL PROTECTED]>
One Laptop Per Child

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Request for Project Hosting: Listen and Spell

[Assim Deodia]

1. Project name  : Listen and Spell


2. Existing website, if any : http://wiki.laptop.org/go/Listen_and_Spell


3. One-line description  : The idea is to develop an application
which would help children to
learn new words, improve their vocabulary and pronunciation of words.

4. Longer description :The activity would speak out a randomly
selected word from a predefined set of words

and the user is expected to spell the word correctly. This activity is
a part of Google Summer of Code 2008.

5. URLs of similar projects : http://wiki.laptop.org/go/Talkntype


6. Committer list
 Username   Full name SSH2 key URLE-mail
     - --
   #1 assimAssim Deodia
  [EMAIL PROTECTED]


   #2 dafDafydd Harries
 [EMAIL PROTECTED]

Both already have account.

7. Preferred development model

   [X] Central tree.

8. Set up a project mailing list:

   [X] No

9. Commit notifications

   [X] No commit notifications, please

10. Shell accounts

~No

11. Translation

   ~No required right now.

12. Notes/comments:

http://code.google.com/soc/2008/olpc/appinfo.html?csaid=F042B0319BC16F53


-- 
Regards
Assim Deodia



-- 
Regards
Assim Deodia | http://nsitonline.in/assim
Undergraduate Student, Netaji Shubhas Institute of Technology
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: Questions about Customization Dirs

[Bert Freudenberg]

On 11.06.2008, at 05:57, Michael Stone wrote:

>
> A while ago, Walter mentioned that we'd like to be able to customize  
> things
> like keyboard and internationalization settings. These settings are  
> loaded by a
> program called 'olpc-session' maintained in the olpc-utils package.
>
> Unfortunately, when I set out to implement support for this feature, I
> discovered two questions which I couldn't answer:
>
> 1) What should we call the customizations directory?
>
>   ~/customizations
>   ~/.customizations
>   ~/.envdir ?
>   ~/

Why not

~/.olpc

or

~/.olpcsession

which would match the "olpc-session" program name?


> 2) How should we process the contents?
>
>   At present, olpc-session _sources_ ~/.kbd and ~/.i18n. If we  
> permit these
>   files to be modified by customization key, then we have  
> immediately offered
>   any attacker a root-level shell injection attack available on the  
> next
>   reboot.
>
>   Can we force these files to match strict (safe) regular expressions?
>
>   Should we write a careful parser for the intended values?
>
>   Other options?


Good catch. Do we need anything more than setting variables? If not, a  
parser should be reasonably simple to write (and certainly someone has  
done so before).

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: On Cerebro, Telepathy, yokes and whites (was Re: cerebro in sugar)

[Morgan Collett]

On Tue, Jun 10, 2008 at 19:05, Polychronis Ypodimatopoulos <[EMAIL PROTECTED]> 
wrote:
> Like Michael pointed out, "there are few people at OLPC who understand
> and enjoy telepathy". I think this is an understatement. Personally, I
> think that Collabora was very pressed to get something working on the
> laptop and the resulting presence stack looks like one hack on top of
> another. For example, there are tons of abstraction layers, yet
> activities have visibility (while they shouldn't) on how telepathy works
> (since telepathy is only a dependency to sugar, this should not be the
> case). Also, the presence service needs to understand if it should
> switch from salut to gabble, but the broadcast storm caused by salut
> won't let XO get an IP address through DHCP, which would mean that
> there's a school server around and. you get the picture! The current
> plan to attack scalability problems is implementing gadget from scratch
> which, if I understand correctly, is a plug-in to jabber which already
> has many problems of its own. Are we sure we're investing our limited
> time in the right direction?

I started working for Collabora on the presence stack just over a year
ago. I'll try to give some context to the presence stack architecture
based on my experience since then.

Presence Service (PS) predates the use of Telepathy. When I started on
this, PS was maintained by Dan Williams (Redhat). It was then
maintained by Simon McVittie (Collabora) and then myself when Simon
switched projects. When I left Collabora, Guillaume Desmottes
(Collabora) took over as primary maintainer, although I continue to
contribute.

PS has a certain amount of cruft in the codebase from before Telepathy
was integrated. There are some design aspects that would be politely
considered "interesting", such as the fact that there are two entirely
different mechanisms for tracking who is in an activity (so we can
show the buddies clustered around the activity icon in Neighborhood
view) - before we join a shared activity we need to track who's in it
by their announcements of their activities, but when we are in a
shared activity, we can see the other participants directly. When
joining an activity, we switch from the one mechanism to the other.

For your interest, outside of Sugarland, the component in the
Telepathy architecture which is most directly equivalent to PS is
called Mission Control (see the diagram on
http://mission-control.sourceforge.net/).

When I started with Collabora, activities contained a lot of Telepathy
code. In fact, Connect was the only collaborative activity, and it was
our test case for the implementation. A fair amount of my efforts with
respect to the presence stack have been to simplify the API or
collaboration mechanisms available to activity authors. This has been
done by pushing the Telepathy functionality into PS where possible, or
sugar.presence which is the client to the PS D-Bus API for python
activities.

At this point, there remains code in activities to deal with the setup
of Tubes. In a further development cycle, after 8.2 / Sugar 0.82, I
plan to simplify that further so that all collaborative python
activities get a D-Tube set up automatically, and don't need any
boilerplate for that at all.

I hope this gives some explanation of why there is Telepathy code in
activities. Even with all the current boilerplate removed, it should
still be possible for activities to interact directly with Telepathy
should the activity author want to do something not provided by the
framework.

Regards
Morgan
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: TWIN (tiny window system) on XO.

[Bert Freudenberg]

Twin is NOT just a window manager (I changed the subject accordingly).

It is a *complete* graphics/windowing system, replacing X11+Cairo 
+Window manager with one *really* tiny package. At runtime it needs on  
the order of 100 KB (yes that, is *K* byte), making it suitable even  
for embedded systems. See

http://keithp.com/~keithp/talks/twin-ols2005/twin-ols2005www/

On 10.06.2008, at 15:55, Paul Schulz wrote:

> Greetings,
>
> It has been suggested that I send the following though. People might
> be interesed in the following screenshots :-)

Indeed!

> This software is pretty much Keith Packard's twin software (LGPL),  
> which
> I've imported into git.. and rearranged a little.

Nice :)

> It's currently using the X11 display, but there is also an SDL  
> backend.


Would be interesting to see on fbdev ...

While the XO actually has plenty of RAM, we're currently wasting a ton  
of it. I'm glad to see experiments for reducing the footprint :)

- Bert -


___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: While we're on Cerebro, Telepathy, etc... Cerebro + bitfrost?

[Bert Freudenberg]

On 11.06.2008, at 03:37, Jameson Chema Quinn wrote:

> Thus, there would be three kinds of activities:
>
> those with full network access, able to talk to arbitrary IP  
> addresses (browse is inescapably in this category);
>
> those with some kind of "telepathy-only" access, which would only  
> let them talk to IP addresses that correspond to a friend sharing  
> the specific activity instance (Chat might fit here; certainly,  
> Write would);
>
> and those with no network permissions.
>
> The telepathy-only, middle security level would allow the last two  
> "good" use cases, while preventing the last two "bad" use cases. It  
> could be implemented by sugar giving them some kind of key, valid  
> only for that specific instance (and renewed when the instance is  
> resumed) that they could use to "unlock" access to a given IP. I  
> understand that the middle security level would not necessarily be  
> perfect - a man-in-the-middle attack could well subvert any gains,  
> and, especially in early versions, it would be hard to guarantee  
> that any abstraction layer was 100% successful at keeping malformed  
> requests from getting some illicit control over a lower layer - but  
> it would drastically reduce the practicality of any large-scale  
> snoop-net or bot-net for your average shareable activity. Assuming  
> that the connection to friend X was compromised; an activity would  
> still have to hope it was started with an instance that had been  
> shared with friend X in order to leak any data.


Err, hasn't that been the plan all along? P_NETWORK is only given to  
activities needing full network access. It is independent of sharing.  
An activity wanting to share must use telepathy, period. Your "no  
network permissions" above case does not exist separately, it is the  
same as "telepathy-only".

- Bert -

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Re: On Cerebro, Telepathy, yokes and whites (was Re: cerebro in sugar)

[Marco Pesenti Gritti]

On Wed, Jun 11, 2008 at 2:01 AM, C. Scott Ananian <[EMAIL PROTECTED]> wrote:
> On Tue, Jun 10, 2008 at 7:51 PM, Marco Pesenti Gritti
> <[EMAIL PROTECTED]> wrote:
>> On Tue, Jun 10, 2008 at 7:05 PM, Polychronis Ypodimatopoulos
>> <[EMAIL PROTECTED]> wrote:
>> * The abstraction layer needs to be accessible to non-python
>> activities. Unless you want to expose it through DBus, you will have
>> to write it in C (with python bindings). And if I'm not mistake
>> Cerebro is written in python.
>
> So expose it through DBus.  This is done already, if I understand correctly.

I was talking about the additional abstraction layer over
telepathy/cerebro which Polychronis was requesting. But it's good to
know that Cerebro can be already access through DBus.

>> * I haven't seen any concrete technical argument against telepathy *API* so 
>> far.
>
> I've got a concrete non-technical objection: kids at gamejams
> invariably want to write a multiplayer game.  Almost none succeed.
> This tells me we need a better collaboration API.
>
> You can argue that this "simple" API should be *on top* of the
> lower-level telepathy (or cerebro) API, and I won't argue.  But we
> need *something* which a 12-year old can use.

Yeah I agree we need a 12-year-old-safe API. I tend to think it should
be a layer above telepathy/cerebro and most likely implemented in pure
python. DBus would make it too difficult to use and as long as we have
a low level API that non-python activities can access I think we are
fine. It would be great to see prototypes+tutorials of it before we
commit to ship one in the core...

Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel

Need advice to upgrade

[NoiseEHC]

Hello,

I have just received my XO via the Developers Program. The machine is 
working nicely, but there is a problem connecting to my wireless router 
(Belkin Pre-N F5D8230-4) which uses WPA-PSK with AES encription. The XO 
just asks for the password over and over again. The strange thing that 
connecting did succeed several days ago so I could request a developer 
key but since then nothing... (Today I have switched to channel 11 from 
channel AUTO but no effect.)

1. So my question is: do I need to upgade to some more recent FW/build? 
Is it a known problem with build 656 (stream ship.2) which I have?

Normally I would not spam the devel list with this support request but I 
have some more questions:

2. I could not find anywhere what the LEDs do on the XO. It can be that 
I am just stupid or blind but there is an option that it was so evident 
for every 1CC employee that the explanation was missed somehow. The only 
thing that I could find is this:
http://wiki.laptop.org/go/Image:Drawing75c1.jpg
I can deduce all the LEDs' meaning except the leftmost two:
a. The lollipop LED is Wireless acquisition. What exactly does it mean?
b. The tie-fighter LED is Wireless activity. Is it send or receive or 
both? Is it the wireless chip or the TCP/IP stack or what?

3. Some time ago cscott told me how to kill stuff if I want to measure 
speed.
telinit 3
ifconfig msh0 down
ifconfig eth0 down
After that the lollipop and tie-figher are both blinking randomly (and I 
got msh0: link becomes ready message to the console). Does it still 
switches off things? If not what should I use?

4. How is the rebasing on FC9 is going?
I am just asking because sooner or later I will finish the Geode docu 
and will start to develop drivers. Since I am not a Linux guru, I could 
not setup my FC7 VirtualPC image to compile the kernel, I was able only 
to write kernel modules with FC8. So if it is possible, I would avoid 
fighting the kernel build process on FC6 or FC7 and so I would like to 
know what to expect?

5. What image should I upgrade to? What is that "faster build"?
I currently only using the text-mode console so it is not a problem for 
me if no activity works or something like that (if the wireless works).

Thank you!

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel