Re: Notes from an impromptu 8.2.1 Release Mtg.
I updated from 8.2.0 build 767 to staging-27 with `sudo -v -v -v olpc-update staging-27` and it all went very smoothly! IMO, the expired http://wiki.laptop.org/go/Friends_in_testing/banner should be updated to staging-27 from staging-25 Good stuff -- * Restart from Home view worked (sometimes I have to go into a console and press keys to complete shutdown, but not this time) * Two startup chimes (I assume one was installing the new firmware) * By the time I allowed Software update to run I was connected to my wireless access point (with WEP security). * Software update offered no new activities (I had ran it the day before on build 767). Build : 27 Firmware : CL1 Q2E30 Q2E Libertas : 5.110.22.p23 Medium serious bugs --- Build '27' is confusing, especially when "About my XO" doesn't show your release or stream (Trac 8260). I updated the "What release am I running?" wiki page to mention this stream. In Sugar control panel > Language, "Swedish (Sweden)" was highlighted! Sure enough, in the bash shell, LANG is set to sv_SE.utf8. I'm pretty sure I never chose that, and other settings like Date & Time were unchanged. Has anyone else noticed Language changing? Why didn't Software update install the newer Browse (v.101 ?) that according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes addresses ticket #9112 Enable Browse to embed PDF files in itself A few minor things -- I see a [Discard network history] button in the Network panel, I didn't notice this before but I think it was in 8.2.0. The 8.2.0 manual http://www.laptop.org/8.2.0/manual/XO_Troubleshooting.html should mention this. In the Home view ring view, when I hide the frame (by moving away from a corner or pressing the Frame key), the very edge of the frame flickers white a few times. I didn't notice this before. Please please create Trac version "Build 767 (8.2.0)" (Trac bug 8904). Cheers, -- =S Page ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Thu, 5 Feb 2009, Ed McNierney wrote: > The "9.1" release was a very specific release planned for the first half of > 2009 - see http://wiki.laptop.org/go/9.1.0 for one set of details - following > OLPC's stated plan of two major releases per calendar year. That specific > event is not going to happen. That's not at all the same thing as saying > "OLPC will never do another software release again". OLPC will not > undertake, on its own, another major release of the software package we > currently ship with each XO. Several things are happening, however: > > 1. An 8.2.1 release is nearing completion, and I expect OLPC will continue to > produce minor feature-driven point releases (8.2.2, 8.2.3) as needed to > support our deployments. This is in contrast to our previous plan of > schedule-driven major releases twice a year (of which 9.1 would be the next). > > 2. Several people are working actively with the Fedora community to ensure > that Fedora 11 works as well as possible on the XO. Sugar will be an > available desktop environment on F11 as it is in F10. Some users and/or > deployments may choose to use F11 on their machines instead of 8.2.1, > > 3. Other distributions (DebXO, Ubuntu, etc.) in various shapes and sizes are > available for the XO, and I haven't heard any sign that those activities will > end. I hope these will continue to offer additional alternative solutions > for XO users; one size does not fit all. > > The specific discussion about etoys is that originally 8.2.1 was planned as a > more limited bug-fix release, with a major release coming shortly afterwards, > so it made sense for major etoys updates to wait for the 9.1 release. Since > the contemplated 9.1 release will not happen, and since some of the original > customer-driven schedule pressure for 8.2.1 has gone away, it seems to now > make sense to include the planned etoys update in 8.2.1 instead in order to > make the update available to as many of our users as possible as quickly as > possible. so after the 8.2.1 release the plan is to just switch to standard Linux distros? it's one thing to skip the Q2 2009 release becouse you do a Q1 2009 release. saying that there is no replacement for it strongly implies that the Q4 2009 release (or future releases) are not expected to happen either (otherwise the next one planned would be the 'replacement' for the Q2 2009 release it's not even that I think it's necessarily a bad move to make (I've ranted frequently enough about my disappointment with the OLPC software stack), but I would have expected this sort of thing to make major news (unfortunantly, probably with headlines like 'OLPC halts linux development') is this the sort of thing that NN was alluding to when he announce the downsizing and future plans and emphisised the possibility of Sugar on Windows? David Lang > - Ed > > > On Feb 5, 2009, at 11:32 PM, da...@lang.hm wrote: > >> On Wed, 4 Feb 2009, Bert Freudenberg wrote: >> >>> Dear Release Manager, >>> >>> as we discussed on IRC today (and which I had not realized until >>> today) the 8.2.1 release will be pre-installed on XOs for much longer >>> than anticipated, since the 9.1 release has been canceled, and no >>> replacement is in sight. >> >> this is the first I've seen about 9.1 being canceled. >> >> if this is the case (and especially with no replacement planned), what is >> the plan for XO software going forward? >> >> David Lang >> ___ >> 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: Please update etoys in 8.2.1
David - The "9.1" release was a very specific release planned for the first half of 2009 - see http://wiki.laptop.org/go/9.1.0 for one set of details - following OLPC's stated plan of two major releases per calendar year. That specific event is not going to happen. That's not at all the same thing as saying "OLPC will never do another software release again". OLPC will not undertake, on its own, another major release of the software package we currently ship with each XO. Several things are happening, however: 1. An 8.2.1 release is nearing completion, and I expect OLPC will continue to produce minor feature-driven point releases (8.2.2, 8.2.3) as needed to support our deployments. This is in contrast to our previous plan of schedule-driven major releases twice a year (of which 9.1 would be the next). 2. Several people are working actively with the Fedora community to ensure that Fedora 11 works as well as possible on the XO. Sugar will be an available desktop environment on F11 as it is in F10. Some users and/or deployments may choose to use F11 on their machines instead of 8.2.1, 3. Other distributions (DebXO, Ubuntu, etc.) in various shapes and sizes are available for the XO, and I haven't heard any sign that those activities will end. I hope these will continue to offer additional alternative solutions for XO users; one size does not fit all. The specific discussion about etoys is that originally 8.2.1 was planned as a more limited bug-fix release, with a major release coming shortly afterwards, so it made sense for major etoys updates to wait for the 9.1 release. Since the contemplated 9.1 release will not happen, and since some of the original customer-driven schedule pressure for 8.2.1 has gone away, it seems to now make sense to include the planned etoys update in 8.2.1 instead in order to make the update available to as many of our users as possible as quickly as possible. - Ed On Feb 5, 2009, at 11:32 PM, da...@lang.hm wrote: > On Wed, 4 Feb 2009, Bert Freudenberg wrote: > >> Dear Release Manager, >> >> as we discussed on IRC today (and which I had not realized until >> today) the 8.2.1 release will be pre-installed on XOs for much longer >> than anticipated, since the 9.1 release has been canceled, and no >> replacement is in sight. > > this is the first I've seen about 9.1 being canceled. > > if this is the case (and especially with no replacement planned), > what is > the plan for XO software going forward? > > David Lang > ___ > 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: Please update etoys in 8.2.1
On Wed, 4 Feb 2009, Bert Freudenberg wrote: > Dear Release Manager, > > as we discussed on IRC today (and which I had not realized until > today) the 8.2.1 release will be pre-installed on XOs for much longer > than anticipated, since the 9.1 release has been canceled, and no > replacement is in sight. this is the first I've seen about 9.1 being canceled. if this is the case (and especially with no replacement planned), what is the plan for XO software going forward? David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Network addressing for activation-over-IBSS
2009/2/5 Martin Langhoff : > Sure can do, and there is a related change other people have asked for > (free addresses for the APs themselves, so that the telnet or webbased > config UIs can be used). Great. Can you pick a range so that I can make the assignment locally too? > BTW, I am not against having a usable IPv6 setup _as well as_ IPv4. It > is just not high priority for me; none of the deployments we're eyeing > stretches the IPv4 limits, and I cannot drop IPv4 infra either. Not to > mention the rough edges in IPv6 support. OK. Activation over IPv6 is nice and easy though, see my other mail, I hope you'll consider it as an initial step :) ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] XS-0.5.1 is all go.
On Wed, Jan 28, 2009 at 7:08 PM, Martin Langhoff wrote: > It's a bit of a non-event, the code has been "there" for quite a > while. So I am just making it official: 0.5.1 is the XS image to use. > Grab it at http://xs-dev.laptop.org/xs/ Quick heads up: I just fixed the yum repo fpr tje 0.5 "stable" branch of XS. Two packages were a revision behind: ejabberd-xs and xs-release. The (now correct) ejabberd-xs package has the desired fixes to presence. xs-release is just cosmetic. This _only_ affects people who instaled 0.5 and then did yum update. The 0.5.1 iso is 100% correct. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: 8.2.1 Thoughts
On Fri, Feb 6, 2009 at 1:03 PM, Chris Ball wrote: > This commit¹ is known to break WPA until this fix², so I'd recommend > testing either neither or both of these commits. I don't know how far they are from eachother. You can tell git bisect to avoid them... but they may mask the problem commit. It's possible to synthesize a history that removes that known WPA breakage and lets you do a clean bisect. Overkill though. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Thoughts
On Thu, 5 Feb 2009, Chris Ball wrote: > > Hi James, > > > Briefly, how is this done? Where can I get the current kernel source as > > a bisectable repository > > http://dev.laptop.org/git?p=olpc-2.6;a=shortlog;h=testing > > (git clone git://dev.laptop.org/olpc-2.6 && cd olpc-2.6 && > git checkout -b testing origin/testing) > > > and is it as simple as reverting a patch, make, scp the kernel to a > > unit, then reboot and attempt to reproduce? > > Yes -- in fact, you could just scp the libertas.ko/usb8xxx.ko modules > over, after "make modules M=drivers/net/wireless/libertas". > > The changes we're interested in occurred between the 767 tag, which is > commit f10b654367d7065d50e7d5e3649933453cea3102, and HEAD. it's actually easier than that. here's a LWN article that talks about automating the bisect, but it covers the basics as well. http://lwn.net/SubscriberLink/317154/d3d710e2a6d5e97e/ David Lang > This commit? is known to break WPA until this fix?, so I'd recommend > testing either neither or both of these commits. > > The first useful test is "does the 767 version of the wireless driver > work with WPA with the new firmware", since that'll suggest to us > whether we have a bad driver or bad firmware. > > Thanks very much! > > - Chris. > > ?: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=b0a7455f0b > ?: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=a3e1b6fe88 > -- > Chris Ball > ___ > 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: [Server-devel] Network addressing for activation-over-IBSS
On Fri, Feb 6, 2009 at 1:11 AM, Daniel Drake wrote: > Can I persuade you to add a new range for the IBSS-STA XOs that are > requesting leases over IPv4? 126 addresses is not many when XOs will > be assigning them randomly, we will have kids arriving at school at > the same time, and many laptops expiring on the same day. Sure can do, and there is a related change other people have asked for (free addresses for the APs themselves, so that the telnet or webbased config UIs can be used). BTW, I am not against having a usable IPv6 setup _as well as_ IPv4. It is just not high priority for me; none of the deployments we're eyeing stretches the IPv4 limits, and I cannot drop IPv4 infra either. Not to mention the rough edges in IPv6 support. If anyone is keen on seeing IPv6 on the XS... it would be fantastic to get you involved. Each step is very small, bringing it to fruition has a lot of steps involved... and it is waiting for you :-) cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: Summary & Minutes from olpc-friends' Tuesday Deployment Meeting
Interesante discucion sobre el grado de avance del proyecto... Una pregunta ... algo gnorante el Plan CEIBAL tiene metricas sobre el despliegue del proyecto , claro aparte del numero de horas dictadas con la olpc y las estadisticas sobre estado de maquinas... 2009/1/29, David Van Assche : > > Enjoy: > > hpachas> _sj_, los temas de implementación pasan por 3 temas > importantes > > the implementation themes are split into 3 important ones: > > hpachas> _sj_, logistico, técnico y pedagógico > > logistics, technical and pedagogical > > hpachas> pienso que se deben agendar reuniones en base a los tres > grandes > temas >_sj_> hpachas, los tres! > > I think we should aggregate the meetings according to the big 3 themes > >_sj_> oh, right, logistics >_sj_> hpachas, absolutamente. logistics is its own Field >_sj_> as anyone who has every sat with hernan or fiorella can tell > you... > hpachas> _sj_, en la parte logistica, son muchos pasos que los demás > paises deben entender como realizarlo > > yes in the logistics part there are many steps that the other > countries could learn how to realize > > hpachas> _sj_, ahora a eso tenemos que añadir: distribución, > reparación, sustitución > > to that we now need to add distribution, repairs, and substitution > >_sj_> hpachas, que es sustitucion? >_sj_> support? > hpachas> _sj_, sustitución = reemplazo de un equipo por otro >_sj_> ah! interestante! > > substitution means replacing one machine for another > > hpachas> _sj_, son muchas cosas por las cuales nosotros ya hemos pasado > y > estamos pasando > > these are many aspects which we have already experienced and are > experiencing. > > hpachas> _sj_, ahora en el tema técnico, es otro mundo paralelo > > in the technical theme, it is a parallel world > > hpachas> _sj_, localización, activación, etc, etc > > localisation, activation, etc > >_sj_> hpachas, si, muchas muchas cosas importantes > > yes many important things > > hpachas> _sj_, tenemos q recordar que la parte técnica va en los > siguientes aspectos: XO, XS, AP, Swhti, Acceso a Internet > > we have to remember that the technical parts are split into the > following items: XO, XS, AP, Swhti, Internet Access > >_sj_> hpachas, puedes ayudar con los agendas de estos reuniones? > > can u help with the agenda of these meetings > >_sj_> tienes el gran parte de experiencia con estos > > u have the most experience with these items > >_sj_> temas, problemas, soluciones > > themes, problems, solutions > >_sj_> y la compartmentacion entre temas diferentes y paraleles > > and the compartimentisation between different parallel themes > > hpachas> _sj_, pienso que debemos hacer una evaluación de como se > encuentran en estos mometnos todos los paises OLPC > > I think we should evaluate how the OLPC countries find themselves right > now. > >_sj_> Swhti? > hpachas> _sj_, quizas tener un site que diga el grado de avance de cada > pais, ayudaría > > maybe have a site that shows the percentage of advancement of each > country would help > >_sj_> hpachas, estos discusiones son para los escuelas y paises > pequenos > > these discussions are for schools and smaller countries only > >_sj_> solamente >_sj_> pero hay paraleles > > but there are parallels > >_sj_> ah >_sj_> el mapo con "el grado de avance" es muy viejo > > the map with the percentage advance is very old > >_sj_> mapa* >_sj_> hmm > hpachas> ese mapa debe ser interactivo, editable a través de internte > > that map should be interactive and editable via the net. > >_sj_> hpachas, voy a ver. si... >_sj_> no tenemos cada uno >_sj_> pere sera valable > hpachas> _sj_, si colocamos el programa OLPC en linea de tiempo, diria > q > empieza por el tema logistico, técnico/pedagógico > > If we put the OLPC program in a linear timeline, we could say it > starts with the logistics, and then tecnical and pedagogical. > >_sj_> si. wikitimeline es interesante para eso... > > wikitimeline could be used for that. > >_sj_> http://www.mediawiki.org/wiki/Extension:EasyTimeline > > > On Thu, Jan 29, 2009 at 5:42 PM, Michael Stone wrote: > > Folks, > > > > We had an awesome deployment meeting this Tuesday at 2000 UTC on > > #olpc-deployment on irc.freenode.net. Almost 30 people came, with > knowledge of > > 10 different deployments! > > > > Summary and minutes are now available at > > > > http://wiki.laptop.org/go/Deployment_meetings/20090127#Summary > > http://wiki.laptop.org/go/Deployment_meetings/20090127 > > > > Enjoy, and please join us next Tuesday at 2000 UTC or Wednesday at 0500 > UTC. > > Also, please feel free to add items to the next meetings'
Re: 8.2.1 Thoughts
Hi James, > Briefly, how is this done? Where can I get the current kernel source as > a bisectable repository http://dev.laptop.org/git?p=olpc-2.6;a=shortlog;h=testing (git clone git://dev.laptop.org/olpc-2.6 && cd olpc-2.6 && git checkout -b testing origin/testing) > and is it as simple as reverting a patch, make, scp the kernel to a > unit, then reboot and attempt to reproduce? Yes -- in fact, you could just scp the libertas.ko/usb8xxx.ko modules over, after "make modules M=drivers/net/wireless/libertas". The changes we're interested in occurred between the 767 tag, which is commit f10b654367d7065d50e7d5e3649933453cea3102, and HEAD. This commit¹ is known to break WPA until this fix², so I'd recommend testing either neither or both of these commits. The first useful test is "does the 767 version of the wireless driver work with WPA with the new firmware", since that'll suggest to us whether we have a bad driver or bad firmware. Thanks very much! - Chris. ¹: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=b0a7455f0b ²: http://dev.laptop.org/git?p=olpc-2.6;a=commit;h=a3e1b6fe88 -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] updates
On Thu, 2009-01-29 at 08:48 +1300, Martin Langhoff wrote: > On Thu, Jan 29, 2009 at 5:24 AM, Jerry Vonau wrote: > > Next, find a regular PC that is capable of reading SD cards. We're using > > Oh, good point. I thought that the XO SD reader was handled by the > same kernel module as conventional SD readers. I'm going to back-port the minihal.py (index 6d4e6de..8ab93d4 100644) fix to what I have going on here. Providing that you don't use lvm on the cf card, this should be almost be good to go, just have to write a post part in the kickstart file to setup the olpc.fth file. The trick to getting this all working is to plug in the external drive in after anaconda loads up to the language screen, keeps from messing with OFW's and the kernel's drive ordering. An external hard drive could be boot-able if you set up the olpc.fth file on the first partition as long as it is not lvm, so this opens up that avenue also. I used that method to load the stock updated os on to the XO. I've add the need modules and firmware to support the cf card and the on-board wireless into anaconda's build routine. I get prompted to configure the on-board wireless lan now..(yet to be tested). Guess I should bz that one too. Should this be successful, live updates at install time could be possible. Then how would we like the on-board interface to come up as? Part of the mesh, or let it be available to be configured for internet access by default? I should have an updated patch set later this weekend. Jerry ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: 8.2.1 Thoughts
On Thu, Feb 05, 2009 at 06:53:44PM -0500, Michael Stone wrote: > > 1) Daniel Drake discovered some annoying wifi regressions (#9235). > > We need to find root cause here, e.g. by bisecting the kernel patches > added > since 8.2.0 and testing each resulting kernel with both the new and the > old > firmware. Briefly, how is this done? Where can I get the current kernel source as a bisectable repository, and is it as simple as reverting a patch, make, scp the kernel to a unit, then reboot and attempt to reproduce? -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
8.2.1 Thoughts
Hey folks, Here are some more unofficial thoughts on how 8.2.1 is progressing: 1) Daniel Drake discovered some annoying wifi regressions (#9235). We need to find root cause here, e.g. by bisecting the kernel patches added since 8.2.0 and testing each resulting kernel with both the new and the old firmware. 2) The firmware looks awesome! Daniel and I both spent some time testing the new features of OFW q2e30 and we liked them so much that we worked together with Scott to implement some new initramfs features that make them easier to use. However, since they affect security critical code, they could always use more eyes. If you'd like to learn about how these components work, then please help test and review the patches! 3) More smoke testing, please! TJB did a full smoke test on staging-25, which went well modulo some wifi and collaboration concerns, but more exploratory testing is still needed. Consequently, we expect to announce a new build within the next day or two for you to help test. (The new build will feature an exciting Etoys update that missed 8.2.0 by a hair and which has been ripening ever since.) I'll announce this new image both by email and on http://wiki.laptop.org/go/Friends_in_testing as soon as it's ready. In conclusion, "so far so good"! Regards, Michael P.S. - A couple of people have asked about the possibility of future releases beyond 8.2.1, e.g. to offer access to new versions of gnash, telepathy, cerebro, etc. and to motivate folks to help fix long-standing 8.2.0 bugs like the memory stability issues. I'll just mention in passing that I'd be quite interested in facilitating an 8.2.2 release containing these updates, assuming the continued interest of the folks whose help is needed to actually do the integration, do the testing, and fix the bugs... Interested? (as a warm-up round toward bigger things?) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc-update broken
Hi, >> When I try to fetch this with 'olpc-update', I get: >> "I don't think the requested build number exists." > I get the same error for staging-27 Thanks; it was out of disk space. - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
olpc-update broken
On 05.02.2009, at 15:40, Mikus Grinbergs wrote: > When I try to fetch this with 'olpc-update', I get: > "I don't think the requested build number exists." I get the same error for staging-27 - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New staging build 27
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build27 Changes in build 27 from build: 26 Size delta: -0.39M -etoys 3.0.2153-1 +etoys 4.0.2205-2 -squeak-vm 3.10-3olpc10 +squeak-vm 3.10-3olpc11 --- Changes for etoys 4.0.2205-2 from 3.0.2153-1 --- + update version string on startup + include icons for mimetypes --- Changes for squeak-vm 3.10-3olpc11 from 3.10-3olpc10 --- + fix pgUp/pgDown keys (#8536) + fix view-source key (#8700) -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-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
Re: Is it possible to disable "sharing" for an Activity?
On Thu, Feb 5, 2009 at 3:17 PM, John Gilmore wrote: >> I think that the addition of a new property in the activity.info file >> would be logical here. Make it an integer indicating the maximum >> number of supported participants. "Unshared" activities would report >> '1', activities like video chat (with technical limitations) or chess >> (with obvious player limits) might specify 2, and others could specify >> another cap based on resource requirements and/or a constant to >> indicate an unbounded number. > > If robust activity sharing is ever going to make it past the Sugar GUI > barrier, adding sharing properties to a Sugar-specific config file > will just create an issue that needs cleaning up later. Wouldn't it > be better to add a function or argument to the sharing API, that an > application can use to limit the number of participants sharing the > application? > > The world and the kids would be better off with e.g. a GNU Chess/ > XBoard that's able to share on any platform, rather than a "Chess > Activity" that only shares under Sugar. +1. And if and when sharing is maintained upstream from Sugar, we all win... until then, we need to keep pounding away at the Sugar bits. >John > > http://www.tim-mann.org/xboard.html > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2644
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2644 Changes in build 2644 from build: 2643 Size delta: -0.13M -olpcrd 0.49-0 +olpcrd 0.50-0 --- Changes for olpcrd 0.50-0 from 0.49-0 --- + Implement multiple key support -- 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
Re: Is it possible to disable "sharing" for an Activity?
> I think that the addition of a new property in the activity.info file > would be logical here. Make it an integer indicating the maximum > number of supported participants. "Unshared" activities would report > '1', activities like video chat (with technical limitations) or chess > (with obvious player limits) might specify 2, and others could specify > another cap based on resource requirements and/or a constant to > indicate an unbounded number. If robust activity sharing is ever going to make it past the Sugar GUI barrier, adding sharing properties to a Sugar-specific config file will just create an issue that needs cleaning up later. Wouldn't it be better to add a function or argument to the sharing API, that an application can use to limit the number of participants sharing the application? The world and the kids would be better off with e.g. a GNU Chess/ XBoard that's able to share on any platform, rather than a "Chess Activity" that only shares under Sugar. John http://www.tim-mann.org/xboard.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
OLPC volunteers this Saturday Wellington - Upgrading
Hi Join us in welcoming back Martin Langhoff this Saturday after his XS work in Boston. The community is ready for testing 8.2.1 staging 25 so we can upgrade the XOs this weekend. Usual: 10.30am at The Cross, 35 Abel Smith St. Kind regards Tabitha Roder (64)21482229 Support OLPC G1G1 - laptop.org/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-activation-server over IPv6
2009/2/5 Jerry Vonau : > On Thu, 2009-02-05 at 11:04 -0300, Daniel Drake wrote: >> I have got xs-activation-server working over IPv6. It is quite simple. >> >> Firstly, the server must bind to a hardcoded address on the LAN. This >> can be done with this command: >> ip addr add fe80::abcd:ef01/64 dev lanbond0 >> >> Secondly, /etc/xinetd.d/xsactivation should be replaced with the attached >> file. >> >> >> Please can this be included for future XS releases? Also, where would >> be a suitable place for me to add the "ip addr add" command in our >> local 0.5.1 installations, which we will use for deployments? > > I'd think you might want to add the IPV6 network info to the > ifcfg-lanbond0 file, and let the network scripts do the work. Thanks. The modification required is in /etc/sysconfig/network-scripts/ifcfg-lanbond0 change: IPV6INIT=no to IPV6INIT=yes IPV6ADDR_SECONDARIES="fe80::abcd:ef01/64" Daniel ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
New staging build 26
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build26 Changes in build 26 from build: 25 Size delta: -0.13M -olpcrd 0.49-0 +olpcrd 0.50-0 --- Changes for olpcrd 0.50-0 from 0.49-0 --- + Implement multiple key support -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-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
Re: Please update etoys in 8.2.1
On 05.02.2009, at 18:46, Chris Ball wrote: > Hi Bert, > >> We have had fixed Etoys / Squeak-VM packages ready for many months >> now, they just did not make it into 8.2 by a few days, and 8.2.1 >> was scheduled to be only a major-bugs fixing release, so we were >> holding out for 9.1. Since that is not going to happen we would >> very much appreciate if the updated RPMs would get included in >> 8.2.1. > > Thanks, I'm willing to accept this change. It's headed for a staging > build now; can I ask for your help testing it once we release it in > our > first 8.2.1 candidate build? (Which should be later today or > tomorrow.) Of course. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
Hi Bert, > We have had fixed Etoys / Squeak-VM packages ready for many months > now, they just did not make it into 8.2 by a few days, and 8.2.1 > was scheduled to be only a major-bugs fixing release, so we were > holding out for 9.1. Since that is not going to happen we would > very much appreciate if the updated RPMs would get included in > 8.2.1. Thanks, I'm willing to accept this change. It's headed for a staging build now; can I ask for your help testing it once we release it in our first 8.2.1 candidate build? (Which should be later today or tomorrow.) - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-activation-server over IPv6
On Thu, 2009-02-05 at 11:04 -0300, Daniel Drake wrote: > I have got xs-activation-server working over IPv6. It is quite simple. > > Firstly, the server must bind to a hardcoded address on the LAN. This > can be done with this command: > ip addr add fe80::abcd:ef01/64 dev lanbond0 > > Secondly, /etc/xinetd.d/xsactivation should be replaced with the attached > file. > > > Please can this be included for future XS releases? Also, where would > be a suitable place for me to add the "ip addr add" command in our > local 0.5.1 installations, which we will use for deployments? I'd think you might want to add the IPV6 network info to the ifcfg-lanbond0 file, and let the network scripts do the work. >From /usr/share/doc/initscripts-*/sysconfig.txt IPV6ADDR=[/] Specify a primary static IPv6 address here Jerry ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: Video Playback
> > > 1) Any idea on the Mplayer activity development? I cant get it to work as > an activity, although i can make it happen through the console, which isnt > the best idea, since it's meant for the kids to watch some videos on it. > > Some time ago we did some work on that (we = Reynaldo Verdejo and I ) building an activity, the first version can be watched here: http://edsiper.linuxchile.cl/blog/?p=16 the trick is to reparent the mplayer window in a gtk drawingarea or similar, for that you need to call mplayer with: mplayer -wid PARENT_WINDOW_XID I don't have the code here at this moment but is not difficult to do it... cheers. -- Eduardo Silva http://edsiper.linuxchile.cl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Video Playback
Hi there 1) Any idea on the Mplayer activity development? I cant get it to work as an activity, although i can make it happen through the console, which isnt the best idea, since it's meant for the kids to watch some videos on it. 2) What codecs can i install on the built in totem? how can i install them, ive tried several things through terminal but there's no related package over there, or is there? Thanks Carlos Dario Isaza Zamudio::ConTi Ingeniero Electronico Proyecto Todos @l Computador Celular (57) 300 814 9308 Universidad Nacional de Colombia - Sede Manizales GNU/Linux Registered User #465475 eSSuX - Usuarios y Desarrolladores GNU/Linux UNAL Manizales ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Video Playback on the XO
Hi there 1) Any idea on the Mplayer activity development? I cant get it to work as an activity, although i can make it happen through the console, which isnt the best idea, since it's meant for the kids to watch some videos on it. 2) What codecs can i install on the built in totem? how can i install them, ive tried several things through terminal but there's no related package over there, or is there? Thanks Carlos Dario Isaza Zamudio::ConTi Ingeniero Electronico Proyecto Todos @l Computador Celular (57) 300 814 9308 Universidad Nacional de Colombia - Sede Manizales GNU/Linux Registered User #465475 eSSuX - Usuarios y Desarrolladores GNU/Linux UNAL Manizales ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: OLPC upgrades
wad wrote: > > Testing of UBIFS at 1CC ran into a bug which was patched and > has now been running for months without problems. > > See: http://wiki.laptop.org/go/UBIFS_on_XO is there an executive summary of your test results on the wiki? reading through the above, plus: http://wiki.laptop.org/go/UBIFS_initial_experiments http://wiki.laptop.org/go/NAND_Testing i see the major jffs2 bug fixed (#8615) and also had some big slowdown issues as the device filled (did i get that right?). i also see that there were some LBA nand failures -- did we ever hear anything from toshiba on those? were there other failures or hard lessons? and finally -- did we learn anything about ubifs performance, or other characteristics of its behavior that might be interesting? (great test writeups, btw.) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 2643
When I try to fetch this with 'olpc-update', I get: "I don't think the requested build number exists." mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Paraguay software deployment timeline
Hi Chris, Just wanted to note down our current situation and what we hope we can squeeze out of OLPC in the next few weeks: First the timing: 1. Laptops are arriving here on Feb 13th, we expect them to have cleared customs and reached our warehouse by approx February 17th. 2. We plan to handout laptops in schools on Feb 25th. Secondly, our "ideal" requirements which we need ready for February 17th (so that we can do the flashing): 1. An OLPC-signed firmware which will install custom Paraguayan deployment keys provided by me: activation lease key, OS key (so we can customise initramfs) and FS key (so that we can flash an image including our customisations: irfs and activities), and then flash a nandblaster capable fw. 2. A signed build of 8.2.1 (in the 8.2 release stream) to base our fs image from. (the WPA regressions do not matter to us) Note that we do not need #9045 to be fixed, since we will be using throwing in our own modified initramfs anyway (I have patched it to acquire leases from the XS over open IBSS networks). We do need it to be built in the 8.2 stream so that the version numbers read correctly and so that the activity updater looks in the right place. Ideally this would actually be ready in advance of Feb 17th, so that we can do final testing. So, what we need from OLPC: 1. An 8.2.1 candidate build in the 8.2 stream 2. A firmware release which does what is described here: http://wiki.laptop.org/go/Firmware_security#Procedures_for_Adding_Deployment_Keys_En_Masse What are your thoughts? Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] xs-activation-server over IPv6
I have got xs-activation-server working over IPv6. It is quite simple. Firstly, the server must bind to a hardcoded address on the LAN. This can be done with this command: ip addr add fe80::abcd:ef01/64 dev lanbond0 Secondly, /etc/xinetd.d/xsactivation should be replaced with the attached file. Please can this be included for future XS releases? Also, where would be a suitable place for me to add the "ip addr add" command in our local 0.5.1 installations, which we will use for deployments? Thanks, Daniel xsactivation Description: Binary data ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: Mesh support very likely to miss Sugar 0.84
> I'm not sure completely sure about deployments but how much are they > actually used? "Two kids under a tree" don't technically need a mesh > to collaborate (as cool as it sounds). Concentrating on deployments risks "disrespecting" G1G1 purchasers. In Sugar 0.84, will mesh at least be disabled, from the point of view of Ohm and the kernel, so that the WiFi chip can be powered down when it's not in use for WiFi? >> >> The language in the above quote implies that 'mesh' is disposable. >> With help from this list, I've been successful in using a (manually >> initiated) mesh between XOs running Joyride 2633. PLEASE do not >> take away my ability to do this !! > > I'm not sure about mesh as such but I wonder how much the mesh is > actually used in large deployments (I believe in at least one large > deployment the network function was essentially nor used) or > deployments generally but on the other side of things Fedora 10 and > the associated NetworkMager 0.7 on which the non kernel side of OLPC > networking is based supports also by default the sharing of wifi. My point is that in 2008 I had (with mesh) a working environment for collaborating in locations where there was no wifi access. My post was a plea to "not throw out something that already works". > If there's issues with mesh would is be possible to add a "sharte my > network" checkbox which automagically uses the network sharing options > included in NM 0.7 to allow "Two kids under a tree" to collaborate > without the mesh (unless they're both looking over the shoulders of > each other anyway :-) But mesh worked on the hardware I have, and can still (manually) be made to work with Joyride 2633. Until I can (without replacing my XOs) see "network sharing options" working at Bald Cypress Mountain (far from civilization), to me that option does seem like vaporware. Yes, two kids under a tree can communicate verbally. But if they are cooperating on something tangible (text, images) - I seem to recall OLPC/Sugar saying there are advantages to "sharing" input entry and output journaling. > My thoughts would be to have this a whole lot automated as why > would/should some random "kid" care about what "wifi" and "mesh" mean. I believe that if collaboration *is* important to the user, he will learn what the available tools can be used for (including any potential distinction between "interacting with peers under a tree" vs. "interacting with resources through wifi"). My thoughts regarding automation -- it's 'Mother knows best' (which is the opposite of 'please, Mother - I'd rather do it myself'). mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Network addressing for activation-over-IBSS
2009/2/4 Martin Langhoff : > Great -- I am not too conversant on the initrd code, probably makes > sense to repost it to devel@ where cscott and mstone lurk... Yes, but I would prefer to sort out the networking first. > The XS routing routes 172.18.16.xx the first active antenna (if > present). DHCP never assigns an IP address on that range. Ah. Doesn't work without an AA though. > According to Wad's original schema, where the plan was to scale out > aggressively, the 172.18.1.x range was for the main wired NIC of each > XS. My plan is to scale up before we scale out (farming out highly > integrated services without causing havoc and bottlenecks is > non-trivial), but I am keeping the same routing model as scaling out > is still a valid strategy. > > Still, the potential number of XSs in a network is very low. > > So a safe thing would be to pick a random IP address in > 172.18.1.128/25 when using a/b/g accesspoints, and 172.18.16.xx when > trying mesh channels. Can I persuade you to add a new range for the IBSS-STA XOs that are requesting leases over IPv4? 126 addresses is not many when XOs will be assigning them randomly, we will have kids arriving at school at the same time, and many laptops expiring on the same day. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2643
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2643 Changes in build 2643 from build: 2640 Size delta: 0.00M -xorg-x11-drv-keyboard 1.3.0-3.fc9 +xorg-x11-drv-keyboard 1.3.2-1.fc10 -yum 3.2.20-5.fc10 +yum 3.2.21-2.fc10 -alsa-lib 1.0.19-1.fc10 +alsa-lib 1.0.19-2.fc10 -libedit 2.11-1.20080712cvs.fc10 +libedit 2.11-2.20080712cvs.fc10 -libiec61883 1.1.0-5.fc10 +libiec61883 1.2.0-1.fc10 -libpng 2:1.2.33-1.fc10 +libpng 2:1.2.34-1.fc10 -nss 3.12.2.0-3.fc10 +nss 3.12.2.0-4.fc10 -sqlite 3.5.9-2.fc10 +sqlite 3.5.9-3.fc10 -xorg-x11-drv-evdev 2.1.0-1.fc10 +xorg-x11-drv-evdev 2.1.1-1.fc10 --- Changes for xorg-x11-drv-keyboard 1.3.2-1.fc10 from 1.3.0-3.fc9 --- + keyboard 1.3.2 + keyboard 1.3.1 -- 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
