Re: New 8.2 Stream
Am 11.07.2008 um 05:43 schrieb Bobby Powers: 2008/7/10 Dennis Gilmore [EMAIL PROTECTED]: in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. This sounds good. Can you please explain how this differs from joyride, both at the moment and in the future? Is this based off of Joyride 21XX, what kind of sync will there be, etc. for the momentary difference see http://dev.laptop.org/~bert/8.2-joyride.html I also added update.1-708 as 8.2-0 to see the initial differences: http://dev.laptop.org/~bert/8.2-pkgs.html - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2146
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2146 Changes in build 2146 from build: 2145 Size delta: 0.13M -kernel 2.6.25-20080710.8.olpc.ef6958ba170975d +kernel 2.6.25-20080711.9.olpc.e88ef08601d02cd -- 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: Easiest way to run the latest activities
Morgan Collett wrote: On Thu, Jul 10, 2008 at 11:35, Bert Freudenberg [EMAIL PROTECTED] wrote: Am 10.07.2008 um 10:44 schrieb Morgan Collett: On Wed, Jul 9, 2008 at 21:31, Bert Freudenberg [EMAIL PROTECTED] wrote: Am 09.07.2008 um 20:07 schrieb Sayamindu Dasgupta: On Wed, Jul 9, 2008 at 11:12 PM, Daniel Drake [EMAIL PROTECTED] wrote: On Wed, 2008-07-09 at 23:11 +0530, Sayamindu Dasgupta wrote: The easiest way, perhaps, to run the bleeding edge version of Sugar on an XO is to run the latest joyride. Is there a similar way to run the latest activities on an XO ? I use: http://dev.laptop.org/~bert/joyride-activities.py see http://wiki.laptop.org/go/Bert%27s_script Hmm.. for some activities http://dev.laptop.org/~erikos/sucrose-activities.py seem to provide more recent stuff. Really? That would mean the latest Sugar release is not in Joyride, which would be a problem. Bert's joyride-activities script seems to pull from http://xs-dev.laptop.org/~cscott/repos/joyride/, which is very out of date. For example, it has Chat-37 as the latest, but Chat-42 has been released. How do we get activity updates in there? By the normal Joyride procedure (put the .xo into your ~/public_rpms): http://wiki.laptop.org/go/Build_system#Instructions_for_Use Ah, since the activities were removed from the build images I stopped doing that. I'll do that again. Morgan Yeah until we have another way to update the activities I think the best is to update by the normal joyride procedure. To get a full list of the latest activities and not only the sucrose ones. I will do the ones I maintain now as well and encourage you to do so as well unless someone has a better idea. Best, Simon ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Easiest way to run the latest activities
Am 11.07.2008 um 12:20 schrieb Simon Schampijer: Morgan Collett wrote: On Thu, Jul 10, 2008 at 11:35, Bert Freudenberg [EMAIL PROTECTED] wrote: Am 10.07.2008 um 10:44 schrieb Morgan Collett: On Wed, Jul 9, 2008 at 21:31, Bert Freudenberg [EMAIL PROTECTED] wrote: Am 09.07.2008 um 20:07 schrieb Sayamindu Dasgupta: On Wed, Jul 9, 2008 at 11:12 PM, Daniel Drake [EMAIL PROTECTED] wrote: On Wed, 2008-07-09 at 23:11 +0530, Sayamindu Dasgupta wrote: The easiest way, perhaps, to run the bleeding edge version of Sugar on an XO is to run the latest joyride. Is there a similar way to run the latest activities on an XO ? I use: http://dev.laptop.org/~bert/joyride-activities.py see http://wiki.laptop.org/go/Bert%27s_script Hmm.. for some activities http://dev.laptop.org/~erikos/sucrose-activities.py seem to provide more recent stuff. Really? That would mean the latest Sugar release is not in Joyride, which would be a problem. Bert's joyride-activities script seems to pull from http://xs-dev.laptop.org/~cscott/repos/joyride/, which is very out of date. For example, it has Chat-37 as the latest, but Chat-42 has been released. How do we get activity updates in there? By the normal Joyride procedure (put the .xo into your ~/ public_rpms): http://wiki.laptop.org/go/Build_system#Instructions_for_Use Ah, since the activities were removed from the build images I stopped doing that. I'll do that again. Morgan Yeah until we have another way to update the activities I think the best is to update by the normal joyride procedure. To get a full list of the latest activities and not only the sucrose ones. I will do the ones I maintain now as well and encourage you to do so as well unless someone has a better idea. Best, Simon Heh, I just kept doing as part of my regular release procedure ;) - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Easiest way to run the latest activities
FYI, I believe there's also 'Xo-get' which contains a very frequently updated list of 'released' activities and activity packs. http://wiki.laptop.org/go/Xo-get -iXo On Wed, Jul 9, 2008 at 10:41, Sayamindu Dasgupta [EMAIL PROTECTED] wrote: Hi all, The easiest way, perhaps, to run the bleeding edge version of Sugar on an XO is to run the latest joyride. Is there a similar way to run the latest activities on an XO ? I am a bit concerned that many people who are playing with the latest joyrides still have older activities from a pack like the G1G1 one or the Peru installed, and consequently the latest activities are not getting as much exposure/testing as possible. Thanks, Sayamindu -- Sayamindu Dasgupta [http://sayamindu.randomink.org/ramblings] ___ 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: Easiest way to run the latest activities
On Fri, Jul 11, 2008 at 13:06, Bobby Powers [EMAIL PROTECTED] wrote: 2008/7/11 Ixo X oxI [EMAIL PROTECTED]: FYI, I believe there's also 'Xo-get' which contains a very frequently updated list of 'released' activities and activity packs. http://wiki.laptop.org/go/Xo-get yes I have used this, it is very good and in addition allows you to uninstall applications (from the command line). do you know who is responsible for it? how often are its updates? is it automatic or does someone toll around devel listening for updates? :) It has a repository: http://xo-get.olpc.at/repository/ - but the entry for Chat is out of date so I don't know where it syncs from. Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Subject: Re: New 8.2 Stream To: OLPC Devel
Hi Guys, Interesting links, especially the diffs! I posted these links on the 8.2.0 overview page in a new section: http://wiki.laptop.org/go/8.2.0#Latest_Build_and_Diffs_from_Previous_Builds Let me know if that is OK with you. Can you add a little more to the explanation for these on the wiki page? This looks like information which will be important for developers (e.g. does it tell you where to get the latest code to add your fixes to?) and possibly testers. However, I think it will be more useful with a little more explanation. Thanks, Greg S * Message: 11 Date: Fri, 11 Jul 2008 10:25:35 +0200 From: Bert Freudenberg [EMAIL PROTECTED] Subject: Re: New 8.2 Stream To: OLPC Devel devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Am 11.07.2008 um 05:43 schrieb Bobby Powers: 2008/7/10 Dennis Gilmore [EMAIL PROTECTED]: in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. This sounds good. Can you please explain how this differs from joyride, both at the moment and in the future? Is this based off of Joyride 21XX, what kind of sync will there be, etc. for the momentary difference see http://dev.laptop.org/~bert/8.2-joyride.html I also added update.1-708 as 8.2-0 to see the initial differences: http://dev.laptop.org/~bert/8.2-pkgs.html - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
low power actions?
a thread on irc from last evening prompts me to ask: where can i find a description of how the laptop behaves (LED behavior, powerdown behavior, etc) as the battery gets low? brief searching led me to http://wiki.laptop.org/go/Power_Management#Power_Management_Scenarios but this scenario (battery getting low/critical) doesn't seem to be covered. paul =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Subject: Re: New 8.2 Stream To: OLPC Devel
Am 11.07.2008 um 14:37 schrieb Greg Smith: Hi Guys, Interesting links, especially the diffs! I posted these links on the 8.2.0 overview page in a new section: http://wiki.laptop.org/go/8.2.0#Latest_Build_and_Diffs_from_Previous_Builds Let me know if that is OK with you. Certainly. Can you add a little more to the explanation for these on the wiki page? This looks like information which will be important for developers (e.g. does it tell you where to get the latest code to add your fixes to?) and possibly testers. However, I think it will be more useful with a little more explanation. I'm not sure what explanations would be helpful. My scripts simply analyze the build logs, extract the version info for each package, and then generate the HTML you see from the difference in packages. - Bert - Thanks, Greg S * Message: 11 Date: Fri, 11 Jul 2008 10:25:35 +0200 From: Bert Freudenberg [EMAIL PROTECTED] Subject: Re: New 8.2 Stream To: OLPC Devel devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Am 11.07.2008 um 05:43 schrieb Bobby Powers: 2008/7/10 Dennis Gilmore [EMAIL PROTECTED]: in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. This sounds good. Can you please explain how this differs from joyride, both at the moment and in the future? Is this based off of Joyride 21XX, what kind of sync will there be, etc. for the momentary difference see http://dev.laptop.org/~bert/8.2-joyride.html I also added update.1-708 as 8.2-0 to see the initial differences: http://dev.laptop.org/~bert/8.2-pkgs.html - 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
Re: New 8.2 Stream
On Thu, 2008-07-10 at 23:43 -0400, Bobby Powers wrote: 2008/7/10 Dennis Gilmore [EMAIL PROTECTED]: in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. This sounds good. Can you please explain how this differs from joyride, both at the moment and in the future? Is this based off of Joyride 21XX, what kind of sync will there be, etc. Thanks Dennis!! Some additional questions: Who or what triggers new 8.2 builds to be run? How do developers get packages included? Are we planning on the same kind of system for update1, where we'd push stuff into joyride then request that specific packages be tagged for the release stream? Any objections to me including olpc-netutils in pilgrim (so that we have olpc-netstatus)? I'll document your answers on Greg's 8.2.0 wiki page. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
[EMAIL PROTECTED] wrote: a thread on irc from last evening prompts me to ask: where can i find a description of how the laptop behaves (LED behavior, powerdown behavior, etc) as the battery gets low? EC wise: The EC turns on the red led when it thinks the battery is empty. This is by an SOC % dropping 15%. If the battery voltage depletes further to a level where cell damage will occur it turns the system off. Other than that I don't think anything else changes. -- Richard Smith [EMAIL PROTECTED] One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
fonts in Tk-inter problem (followup)
Answering my own question... I just upgraded to Joyride and this now works properly. I'm trying to get IDLE running on my XO, so that I can show Python development directly on it. IDLE needs Tk-inter to run. I've installed it, and IDLE runs. The font is very small. However I can't get tk to recognize fonts or size changes. If I open Options/Configure IDLE.../'Fonts/Tabs', I only see 'fixed' for a font, and size changes aren't honored. If I run tkFont.py in its demo mode the first line I get back contains 'family': 'fixed' when it should say 'family': 'times'. Also the size isn't honored in the dialog it opens. If I do a fc-list, it reports that I have a lot of fonts on the XO. Does anyone know where the ball is getting dropped, and what I can do about it? Bob ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
smith wrote: [EMAIL PROTECTED] wrote: a thread on irc from last evening prompts me to ask: where can i find a description of how the laptop behaves (LED behavior, powerdown behavior, etc) as the battery gets low? EC wise: The EC turns on the red led when it thinks the battery is empty. This is by an SOC % dropping 15%. If the battery voltage depletes further to a level where cell damage will occur it turns the system off. my interest was piqued by someone on irc asking about automatic clean shutdowns for low power. i was wondering whether we do that, and whether we do earlier user warnings (your battery should be charged now in order to keep it healthy), or perhaps forced suspends. paul =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
Hi, my interest was piqued by someone on irc asking about automatic clean shutdowns for low power. i was wondering whether we do that, and whether we do earlier user warnings (your battery should be charged now in order to keep it healthy), or perhaps forced suspends. Well, we shut off automatically in order to keep the battery healthy, so there's no user involvement needed there. I don't currently do anything in userspace on low power, but the feature of shutting down should save state is targeted at 8.2, and I think the Sugar side is done; I just need a way to trigger the state saving from OHM when power is low. I've added the request to #6014. Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Subject: Re: New 8.2 Stream To: OLPC Devel
For a 'change log' that is useful for both development and testing groups, I would like to ask that people please use the comments during check-in to add the trac item being fixed (when available) and a short description that would help others to know what to test or what feature has been added. We used to get these changelogs... and it was really helpful for the test groups. Kim On Fri, Jul 11, 2008 at 8:37 AM, Greg Smith [EMAIL PROTECTED] wrote: Hi Guys, Interesting links, especially the diffs! I posted these links on the 8.2.0 overview page in a new section: http://wiki.laptop.org/go/8.2.0#Latest_Build_and_Diffs_from_Previous_Builds Let me know if that is OK with you. Can you add a little more to the explanation for these on the wiki page? This looks like information which will be important for developers (e.g. does it tell you where to get the latest code to add your fixes to?) and possibly testers. However, I think it will be more useful with a little more explanation. Thanks, Greg S * Message: 11 Date: Fri, 11 Jul 2008 10:25:35 +0200 From: Bert Freudenberg [EMAIL PROTECTED] Subject: Re: New 8.2 Stream To: OLPC Devel devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Am 11.07.2008 um 05:43 schrieb Bobby Powers: 2008/7/10 Dennis Gilmore [EMAIL PROTECTED]: in preparation for 8.2 we have a new 8.2 stream it can be found at http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/http://pilgrim.laptop.org/%7Epilgrim/xo-1/streams/8.2/ Please test and file bugs against it. This is the stream intended for the 8.2 test builds. This sounds good. Can you please explain how this differs from joyride, both at the moment and in the future? Is this based off of Joyride 21XX, what kind of sync will there be, etc. for the momentary difference see http://dev.laptop.org/~bert/8.2-joyride.htmlhttp://dev.laptop.org/%7Ebert/8.2-joyride.html I also added update.1-708 as 8.2-0 to see the initial differences: http://dev.laptop.org/~bert/8.2-pkgs.htmlhttp://dev.laptop.org/%7Ebert/8.2-pkgs.html - 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
Heads up: dropping mkinitrd from joyride, might break stuff
Hi, mkinitrd is currently included in our builds but we don't need it. It brings in some other unneeded dependencies too, which have grown a bit for F9. We're going to try removing it. Apparently last time this was tried, several essential components fell out of the build, and I guess this might happen again. I'm in charge of fixing any breakage here - I'll readd the important stuff through pilgrim as quickly as I can, but there might be a broken joyride build or 2 today. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Heads up: dropping mkinitrd from joyride, might break stuff
Dan-- I'd like to thank you for your tireless XO-dieting this week in the WAR against dependencies. I'm in charge of fixing any breakage here - I'll readd the important stuff through pilgrim as quickly as I can, but there might be a broken joyride build or 2 today. Some broken joyride builds... a small price to pay, for INDEPENDENCE! We are with you, BROTHER IN ARMS! XO REVOLUTION! Brian OLPC Rally-crier, bell-toller On Fri, Jul 11, 2008 at 11:41 AM, Daniel Drake [EMAIL PROTECTED] wrote: Hi, mkinitrd is currently included in our builds but we don't need it. It brings in some other unneeded dependencies too, which have grown a bit for F9. We're going to try removing it. Apparently last time this was tried, several essential components fell out of the build, and I guess this might happen again. I'm in charge of fixing any breakage here - I'll readd the important stuff through pilgrim as quickly as I can, but there might be a broken joyride build or 2 today. Daniel ___ 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: low power actions?
chris wrote: Hi, my interest was piqued by someone on irc asking about automatic clean shutdowns for low power. i was wondering whether we do that, and whether we do earlier user warnings (your battery should be charged now in order to keep it healthy), or perhaps forced suspends. Well, we shut off automatically in order to keep the battery healthy, so there's no user involvement needed there. to clarify: shut off automatically == clean shutdown? I don't currently do anything in userspace on low power, but the feature of shutting down should save state is targeted at 8.2, and I think the Sugar side is done; I just need a way to trigger the state saving from OHM when power is low. I've added the request to #6014. heh. whatever happened to SIGTERM. :-) (only half joking) paul =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Localization] How do we manage translation effort in Release, process/roadmap?
Hi Sayamindu, Great work, thanks for taking up the gauntlet on this! One question for you, how much lead time do you need to do the translations? Assuming something like final test starts 15 days before the target release date, when do we need to tell the developers to freeze all of their strings? Possible dates are 90 days before target release day and 60 days before target release day. Let me know which of those you prefer or if you think a different lead time is warranted. Thanks, Greg S Sayamindu Dasgupta wrote: Hello Korakurider, Thanks for your input. I have put up a basic document at http://wiki.laptop.org/go/Localization/Workflow Comments and brickbats are welcome :-). Regarding you questions - please see inline :-) On Fri, Jul 4, 2008 at 5:51 PM, Korakurider [EMAIL PROTECTED] wrote: On Thu, Jul 3, 2008 at 8:38 PM, Greg Smith [EMAIL PROTECTED] wrote: Now, my turn to ask :-) I don't know who is the right one to ask though... (1) They say SugarLabs is upstream of Sugar software and OLPC is one of distro. Then, which POs are still owned by OLPC? (Packaging/Pootle/Activation Server/OLPC Web site projects are obvious :-) For Sugar. will commit from Pootle go to upstream(SugarLab) or distro(OLPC)? Which will POT come from ? My personal opinion (I am open to suggestions) that all translations should go directly upstream as much as possible. Distro specific efforts for translations (unless you are talking about distro specific tools, etc) have been badly bitten in the past. (2) SugarLabs have declared string freeze for 8.2. But I am not sure specifically which POT/POs are governed by their declaration. sugar.po/sugar-base.po/sugar-toolkit.po come to mind. And I think other activities in XO-Core (that are also included in their software stack as Demo activities) aren't governed. right? I think I answered this. * sugar-base * sugar-toolkit * sugar * chat-activity * web-activity * read-activity * log-activity * write-activity * calculate-activity * terminal-activity * pippy-activity * etoys-activity I will probably try to arrange the projects in our Pootle server at some point to reflect this. (3) OLPC have stopped to bundle activities with base software. Now release cycle for them doesn't have to be aligned to XO software from OLPC's point of view. But I think It would be still better to try to let them aligned for refreshing translations. Note that even if the package is enough mature, additional build would be needed to pull new translations (new languages for instance). Right now it is hard to know when my updated translations for some activities will be pulled into the packages :- For the sugar stuff - expect a following of the release cycles. For other stuff - there is really no way to know. However, I would like to request developers to announce releases a few days in advance in the localization list, so that translators can prioritize and/or commit appropriately. Thanks, Sayamindu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New 8.2 Stream
On Fri, 2008-07-11 at 11:35 -0500, Dennis Gilmore wrote: Its completely manual. it is designed for doing release candidate builds, much the same as update.1 builds were done. OK. When are you planning to trigger builds? (how often and/or on what conditions?) Any objections to me including olpc-netutils in pilgrim (so that we have olpc-netstatus)? Yes, It needs to be approved for inclusion by release engineering. without a trac ticket approved (most likely by Michael) I wont change anything. If anyone else changes pilgrim I will revert the changes. OK. What's the process? File a ticket, assign to who? Any special component or keywords? I made a commit to the 8.2 branch of pilgrim this morning. Just cherry picked your commit from update1 to setup tamtam symlinks. Hope that's OK, I'll file tickets before making any further changes. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
On 11 Jul 2008, at 16:20, Chris Ball wrote: Hi, my interest was piqued by someone on irc asking about automatic clean shutdowns for low power. i was wondering whether we do that, and whether we do earlier user warnings (your battery should be charged now in order to keep it healthy), or perhaps forced suspends. Well, we shut off automatically in order to keep the battery healthy, so there's no user involvement needed there. I don't currently do anything in userspace on low power, but the feature of shutting down should save state is targeted at 8.2, and I think the Sugar side is done; I just need a way to trigger the state saving from OHM when power is low. I've added the request to #6014. One concern I have with auto saving state before powering off is the potential corruption of journal data. How robust is the Journal if power off happens half way through an ongoing auto state save – do you loose both the new journal entry and the original entry you had resumed from (partially overwritten)? The worst case just now seems to be EToys, it's really great for tinkering, but creating even simple scripts seems to require a massive amount of time to save (example 5+min!! to close save a script with five polygon space invaders with 2 frames of animation and a few lines of movement code). Add to that that EToys seems to be almost as power intensive as video recording (my impression only, I've not power tested). I find I'm the habit of plugging into mains before I try and close an EToys instance I've made more than a few modifications to. --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Jumpy touch pad observation
Hi James, On 11 Jul 2008, at 00:59, James Cameron wrote: Have you another power supply you can try with? No, not at the moment (but I have a request in for MP XO HW). What sort of power supply are you using? Is it one of the B4 range with white label, a model number P018WA120J and a single screw? Or one of the XO branded ones with green label from Delta Electronics Inc. Or something different? It's a green label Delta Electronic Inc (S/N: 0705000814, REV: S2). Would you happen to have a ferrite toroid you could clamp on the end of the DC cable? Wrap the cable through the toroid as many times as you can, and this will help block RF interference from any radio sources nearby. If this solves the symptom, then you may be in an environment that has a lot of radiofrequency energy. I'll take a look, have some old junk electronic equipment kicking around and one might have a ferrite toroid I can dig out and use. (I've seen some strange things happen when I've used an amateur radio nearby, but the field strengths I've used are somewhat out of the ordinary). :-) The guys working on the touchpad driver changes could also have a lot to say ... but the B4 hardware isn't exactly an interesting thing since it isn't what is being made. Thanks for you suggestions! --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
What would it take to put in a journaling filesystem? On Fri, Jul 11, 2008 at 10:49 AM, Eben Eliason [EMAIL PROTECTED] wrote: On Fri, Jul 11, 2008 at 1:33 PM, Gary C Martin [EMAIL PROTECTED] wrote: One concern I have with auto saving state before powering off is the potential corruption of journal data. How robust is the Journal if power off happens half way through an ongoing auto state save – do you loose both the new journal entry and the original entry you had resumed from (partially overwritten)? Disclaimer: I'm not a technical expert on the DS, so others more familiar should probably correct me if I make claims below that are false. This is yet another problem that can be bypassed with the new DS. In one of our past meetings, we laid out requirements for the process by which activities save their state, and it included a means for activities to check in temporary saves if they wished to, optionally passing a flag to tell the Journal to actually create a new entry. This system was in place such that, if the Journal detected that a given activity crashed, it could automatically make a new Journal entry based on the last temporary save, as a form of auto-recovery. This approach could similarly be used after a power failure. Additionally, in the worst case a corrupt entry might wind up in the Journal, but that shouldn't be a problem because, at present, copies are stored so there is no loss of data, and in the future we'll have versions, and only one version of many would be corrupt. It should never be the case that the entry that was opened gets corrupted. Ideally the Journal would be able to recognize when a save transaction doesn't finish and either replace it with the most recent temporary state or remove the entry compeletely. - Eben ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Edward Cherlin End Poverty at a Profit by teaching children business http://www.EarthTreasury.org/ The best way to predict the future is to invent it.--Alan Kay ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
Hi, What would it take to put in a journaling filesystem? The j in jffs2 stands for journalling. - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low power actions?
chris wrote: Hi, What would it take to put in a journaling filesystem? The j in jffs2 stands for journalling. to expand -- i believe the shutdown-inspired corruption people are worried about is not filesystem corruption, but application corruption -- if the activity doesn't completely write its state before the system is shut down, no amount of filesystem protection will help. paul =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Jumpy touch pad observation
On Fri, 11 Jul 2008 19:43:33 +0100 Gary C Martin [EMAIL PROTECTED] wrote: [...] With the latest Joyride changes, it seems much clearer/easier to see when the driver is trying to re-calibrate as the pointer suddenly stops moving for a few seconds. In the persistent case (plugged in charged), leaving the touch pad alone to allow calibration to complete usually does not work, and the cursor continues to jump (or float when your finger is near but not touching the surface) when you try to use it again. Unplug the AC, and the auto re-calibration usually[2] succeeds. Wow, that's pretty bizarre. Given that I did most of my testing on the driver while plugged in, and I have yet to see it fail to recalibrate, I'd expect it to be the other way around. Either way when its jumpy please enable kern.* logging in /etc/ rsyslog.conf, route it to a file, and restart rsyslogd. Then echo 1 /sys/module/psmouse/parameters/tpdebug Then use the mouse jumpy for a while and send me, dilinger, or deepak the log file for us to look at. OK, will do. Thanks for you feedback. Even without debugging turned on, dmesg should show messages about recalibration and detection of jumpiness or spew. If you're seeing the cursor act strangely, but we're _not_ detecting it, I'm especially interested in those logs. If the recalibration is simply failing.. well, I'm not really sure what to do about that, short of power cycling (which will turn off the keyboard momentarily as well. It's ugly.) [1] The common case seems to be touching the pad in two places in quick succession, this is easily done when trying to use the left or right mouse buttons while moving the pointer as they are placed so near the touch surface. I often hit this when using the drag metaphor (probably what makes arranging activities on the new random home screen layout feel more frustrating than it should be). [2] I think the cases I've seen where it does not succeed are down to damp hands, greasy/wet smear somewhere on pad, perhaps nylon underpants (I'm joking!) Does going without underpants make a difference? Perhaps some aluminum foil underpants will help greatly with grounding issues. Richard, can we make clothing requirements for XO usage? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2149
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2149 Changes in build 2149 from build: 2146 Size delta: -0.13M -bootfw q2d16-1.olpc2.unsigned +bootfw q2e10-1.olpc3.unsigned --- Changes for bootfw q2e10-1.olpc3.unsigned from q2d16-1.olpc2.unsigned --- + Latest OFW firmware: q2e10 -- 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
Release Process Update
Hi All, I collected recent feedback and updated the Release Process Home: http://wiki.laptop.org/go/Release_Process_Home Finalization of this will take time. We should move ahead with 8.2.0 and learn from it and plan to use the new process for 8.2.1 and 9.1.0. I addressed as many comments as possible. Where there is no obvious consensus I put forth my best guess or left it out (e.g. synch to Fedora dates not mentioned because we don't have agreement). Special thanks to Sayamindu and Korakurider for making great progress on the localization work flow and process now included in the milestones and at: http://wiki.laptop.org/go/Localization/Workflow Send in your comments, questions and suggestions and speak up if you disagree with the way I addressed your previous input. The most useful inputs are specific suggestions for new text. Please post them here and/or add them to the talk page. Major changes are summarized as follows: - Updated the duration of support section. Now reads: second release following plus 2 months. Also includes how many releases we expect to support at once and defines when the support window starts. (Michael, Let me know if I addressed your comment about starting support only once the release is stable). - Extended the meaning of support section with details and added text from Kim and Scott. - Added a note on Major release names to explain that its OK to refer to release with a wild card in the third digit (hope that addresses Scott's comment) - Added a link to SW ECO process in Minor Release section to define criteria and process for Minor Releases. - Added a definition of new features in the Major Release section (adapted from Fedora process). I'm trying to drive a distinction between features (only available in major releases) and bugs (done in every major and minor release). - Updated the release schedule and milestones. Changed names of Milestones to Steam, Water, Ice. Included the translation milestones in the Steam, Water, and Ice steps. - Added code names in naming section (Thanks to Scott for the idea). 8.2.0 is too far along but we can pick a code name for 9.1.0. Maybe the name of a famous educational theorist? Choose a name and we'll see who gets the most votes. I have not taken on the question of how we fold activities in to the process/release. I will try to address that better next week. Comments, edits and concerns welcome. BTW I'm open to a White Knight (maybe with a Red Hat :-) riding in to help do the final edit and drive a consensus. Have a great weekend! Thanks, Greg S ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Activity Backward Compatibility (was re: Re: joyride 2128 smoketest)
Hi Guys, We should definitely have backward compatibility for activities! That is, activities that used to work (maybe starting at 656) must continue to work. If a new release requires that all activity authors have to recode some of their work, that will be a major deterrent to working with us. Its also a deterrent to deployments upgrading, assuming they find out their activities are broken before they upgrade. I understand that we do not have backward compatibility in 8.2.0 as it currently stands. Can we bound the test problem by saying that all well behaved activities will continue to work? If we can define well behaved and not test activities that meet that criteria it will save us a lot of test time. Any other suggestions on how to bound this test challenge appreciated! e.g. can we say that all activities not listed on this page: http://wiki.sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.81.4 will work the same in 8.2.0 as they did in previous releases? In the future if some piece of core code will cause previously supported activities to no longer work, I hope we can discuss and accept or reject that in advance (sorry if I missed that debate on this round). In the worst case we have to test as many activities as possible but its much better to ensure API changes are not breaking things from the OS level. On the other hand, newer activities can require a newer OS. That can be handled if we have good activity documentation on the download and activity pages. Sounds like we have a big activity test challenge ahead for 8.2.0... BTW is this the full list of all known activities? http://wiki.laptop.org/go/Activities Let's talk more about this on the Tuesday call. Thanks, Greg S Chris Ball wrote: Hi, On Wed, 2008-07-09 at 21:06 +0200, Morgan Collett wrote: My 2c worth here... There haven't been API breaks for activities. I've had to do nothing to my activities to keep them working from 8.1.0 to joyride current. Some external things have bitten us though. gtksourceview API change prevents Pippy-20 from launching (that's the version installed by Bert's script, even today) http://dev.laptop.org/ticket/3488 And an Sugar API change caused Pippy to stop being able to build activities: http://dev.laptop.org/ticket/7205 - Chris. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Jumpy touch pad observation
Re clothing ... with B1 keyboard static issues, I learned what clothing was unsuitable. Fur lined boots. Don't be surprised if you find clothing dependencies for B4 trackpad, in your specific case, since you might be influencing an RF field. -- James Cameronmailto:[EMAIL PROTECTED] http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Release status report delayed.
Folks, My present release status report isn't complete yet, so I'll send it tomorrow when I'm satisfied with it. Sorry for the delay! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] EduBlog: Teacher Review Options
Hi Tarun, That was my intention originally but I'm not sure its critical at this stage. I think its all right if the teacher can choose from many available blogs and just show one or two to the kids at a time. If the kids can choose from a menu of many blogs (frog, cricket, turtle, etc) that was my original intention but it may also be confusing. BTW I never meant to make a distinction between internal and external blogs in the first place. I think it would be helpful to know if the post will go public or just within the school or other restricted access network. If you only have the option to post to two different blogs, they could be totally different. e.g. internal blog has homework submissions and external has pictures of what the kids do for fun. Are you thinking that internal blog and external blog have the same content? The only blog post distinction I was thinking of was: post directly without teacher approval needed and send to teacher for approval before post. HTHs. On the review of current site, I have some HTML tweaks (e.g. image upload hot area is not exactly on t he image so its hard to hit) is that kind of comments relevant/useful or should I ask people to hold tweaks like that until next week when we hope to have new version posted on the new server? Just trying to set the right expectation before I send out this URL for review: http://olpc.betarun.com/dev/ui/student_sp.php Thanks, Greg S Tarun Pondicherry wrote: Hi Greg, Do the kids need to choose between different external blogs? So far, I've seen this as one local blog (OU Blog course1blog) tied to one remote blog (Blogger uruguay-xo-test). Will course1blog need the option to post to more than one remoteblog at the same time and let kids select that information? Thanks, Tarun Greg Smith wrote: Hi Tarun, That sounds OK in general but I have a few comments and clarifications. Make sure the kids know if their post is going to the teacher or directly to the blog. I think the internal vs. external or local vs. remote designations were meant to separate blogs which are on the local school server and only visible from within the school network vs. blogs that are on the internet and visible from anywhere on the internet. We can get rid of that concept and assume that the blog name will be familiar to the kids and they will know which posts go to the internet. The other separation is between blog posts which must be edited/approved by the teacher vs. those that get posted to the blog directly without further edit. That is what the teacher can select and what I hope the kids see from their blog entry page. Also, we still want the option to post to more than one blog (e.g. post to frog blog on Moodle or to turtle blog on blogger.com or to grade 1 blog on blogger etc.). The teacher should have the ability to enable one or the other blog for the kids. HTHs. Let me know if that input is not clear or doesn't answer your questions. Once we get a look at it (hopefully next week) I think it will become more clear. Thanks, Greg S ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] volunteer for offline Moodle
Hi Tony! welcome! Your analysis is good, and similar to one of the offline moodle projects that is already underway. Unfortunately - as an experienced moodle core programmer - I can see that building offline moodle that way has significant roadblocks, some of which are a deal-killer for the long term. So I have a slightly different plan :-) First of all - you will need a good familiarity with Moodle, how it is used, and how it works internally. I don't know how much you know Moodle - my notes below assume a reasonable knowledge of the internal APIs. The first stage of the plan is to work on the main course page - look into the topics course format. The first step is to make that course format AJAXy/Gears-y -- there is an AJAX version of it but I am not sure if it is any good. The goal is to make it cacheable -- this is the lesson plan that Bryan was talking about a few days ago. Other good things may come with it (better ajaxy editing for teachers for example) but that is candy on the side. The main thing that *must* work well is being able to load that page when disconnected. [I am not sure how to trigger that with GG - to hook into the browser and say if host X doesn't seem present, load up this HTML+JS we cached here, under the privilege scope of the site..] Together with the course format, we will want to make mod/resource gears-cacheable. That will give us 80% of the benefits for 20% of the effort - give or take some % there :-) We will want to be extra careful to make it in non-intrusive ways, so it is easy to incorporate upstream. 20% of the effort is still quite a bit of work - there are lots of details to work through. Once the above is done - we can tackle other modules, and perhaps some blocks, with better knowledge of what works well with GG and what doesn't. Some Moodle modules are a really bad fit for GG (mod/quiz), others will take some effort, but work great (mod/forum). The general model - as you can see - is one of caching locally, which simplifies things a lot. As you note, this will be a large long term effort, so we want to make sure that our work is not OLPC-specific. We might do things earlier than moodle.org but we sure want to have them helping with it mid-to-long term. As we are caching stuff, and will only have small amounts of local data we need to push up to the server (like action logs), the storage economy is quite simple - we discard old stuff as we have to - we might define a quota there, but I think GG sets that for us anyway. For authentication, I am not sure at the moment - we'll cross that bridge when we get to it :-) but for OLPC it is an easy bridge due to the 1:1 and the related auto-login assumptions. 7. I also assume that course development offline will not require special support. The teacher would prepare course materials as independent documents and then do course-building when he or she has access to server-side Moodle. Correct. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- 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-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
