Re: F-10 joyride vs 8.2 - getting fixes upstream.
also notice that the Size delta on the 8.2 vs joyride build is reporting 0meg difference which is clearly rubbish :-) Can someone fix it for me please. The URL I'm referring to is http://dev.laptop.org/~rwh/announcer/joyride_vs_8.2.html This one works: http://dev.laptop.org/~bert/8.2-joyride.html I should get more time on Wednesday to continue through the list. I'll be adding any bugs I file against the tracker bug which can be found here https://bugzilla.redhat.com/show_bug.cgi?id=462625 I am planning on working on repeating a few forks that I made during the F9 cycle to fix bugs and reduce dependencies. All of these changes are not easy to fix upstream or in F10. I agree with Jeremy on this one. And I don't necessarily agree that in all cases that they aren't easy to fix upstream. I've been through most of the forks from Fedora 9 to OLPC 8.2 and the vast majority of them are actually pretty easy fixes. Some of them are things like splitting functionality out into sub packages. Some I have already filed bugs against. For example, totem-pl-parser pulling in evolution-data-server and libgnome and ... There is already a (closed) bug about this blocking the one you mentioned: #456113 Is that sufficient for your tracking, or should I reopen it, or create a new one? If we do need to fork I personally would like it done on existing bugs because it allows for easy history tracking. I guess I will have to create another branch request to carry this out.. should I make that bug block FedoraOLPCDelta? Any bugs should block the OLPC Delta. Looking at the increase in size from 8.2 to the current 2550 joyride I suspect the 90 odd meg of bloat falls into a couple of categories. Perl being the first which probably accounts for nearly half of that, then there's new core OS package additions like plymouth, and then the dependency chains that have bloated again like libgnome, e-d-s etc. Alot of the later should be quite simple to fix, especially as libgnome etc are starting to ramp up in their disappearing act. The perl dependency should be fairly easy to get rid of, I suspect that there's only 2-3 packages such as abiword and ghostscript that are pulling it in, and I think I have bugs for both of those. That will cut down the size delta considerably and give us some breathing space to deal with the rest of them. Gstreamer is I know is pulling in some new dependencies some of which might be wanted (wav support) and others not (cd ripping support) which should be able to be separated out into a sub package. If you can give me a bit of time to get some traction on this I should in the next couple of days be able to get a better idea on where we sit. Then an email to the fedora-olpc list for some help and I think the vast majority of the problems will be gone. The likes of totem-pl-parser might take a bit longer so we might have to in the short term fork but the less we have to do now, the less pain we have in the future. And by using mainline packages it also allows us to monitor closely through joyride any of the dependency bloat and jump on mainline before it becomes an issue. Thoughts? Regards, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
On Tue, Nov 18, 2008 at 2:12 AM, Jeremy Katz [EMAIL PROTECTED] wrote: And you've managed to make it so that if anyone else writes an app using totem-pl-parser and expecting that the podcast bits will work will utterly fail. Last time around, I tested my patch with podcasts and they worked OK. The dates didn't come up right, but that's what I was expecting. The functionality itself was fine. Perhaps something has changed? And as you start running more than just your closed world of apps (eg, the efforts to be able to run normal X apps on the XO within Sugar), this is going to get more common or likely. Breaking the expectations of functionality publically exported from libraries really isn't the way to save space... Agreed, those efforts are quite far off though, and I believe that saving the disk space is really more important for OLPC. I think you're right though, it's too early in the release cycle to take shortcuts like this. So I'll leave it for now, and if it doesn't get fixed within the next 3 months or so someone will probably take the shortcut, but let's give people time to think about the real solutions. Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Wacom Bamboo with XO?
robert -- [EMAIL PROTECTED] wrote: Paul, Are you using the driver code from http://linuxwacom.sourceforge.net/ ? no -- i just built the driver that's in the kernel tree. paul I had intended on trying this but have been too busy to get the time set up the correct environment or follow all the steps involved for the initial setup http://linuxwacom.sourceforge.net/index.php/doc If you get something you think is workable let me know and I can test it with one of my Wacom Intuos 2 tablets. Note there is also a mouse as well as a pen with this tablet so the mouse code needs to be compiled as well. thanks for all the good work!! /Robert On Nov 17, 2008, at 8:37 AM, [EMAIL PROTECTED] wrote: building and insmod'ing wacom.ko lets the Sapphire tablet move the mouse cursor. i confess i've never used a tablet, so i don't know whether the button on the stylus doesn't behave as a mouse button is expected or not. also, the motion i get when moving the stylus on the pad is relative, not absolute. there are no module parameters, so any tuning must be via some other mechanism. i can supply the driver module to anyone who would like to try it. i'm probably not the right guy to pursue this further, but i've added a mention of tablet support to #7326, which is a tracker for requested modules. paul wade wrote: If you guys can get a driver working and expose the API, I'll add support to Colors!. It already has support for pressure sensitivity (variable brush size and/or opacity) in the painting engine. -Wade On Mon, Nov 17, 2008 at 8:04 AM, [EMAIL PROTECTED] wrote: chris wrote: Has anyone had any success getting a Wacom USB tablet working with the XO? The new Bamboo series is affordable ($79 US), about the same size active area as the XO display, and could be a substitute for the deprecated/soon to be abandoned pressure sensitive touchpad on the original XOs. we have a wacom tablet (Sapphire, whatever that represents) here at 1cc, which we can test. the XO doesn't include the wacom.ko module which it seems to want. i can try building the module to see if it works. i'll leave it to you to figure out whether the same driver support will work for the Bamboo series. paul =- paul fox, [EMAIL PROTECTED] give one laptop, get one laptop --- http://www.amazon.com/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, [EMAIL PROTECTED] give one laptop, get one laptop --- http://www.amazon.com/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, [EMAIL PROTECTED] give one laptop, get one laptop --- http://www.amazon.com/xo ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2551
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2551 Changes in build 2551 from build: 2550 Size delta: 0.00M -plymouth 0.6.0-0.2008.11.12.4.fc10 +plymouth 0.6.0-0.2008.11.17.3.fc10 -plymouth-libs 0.6.0-0.2008.11.12.4.fc10 +plymouth-libs 0.6.0-0.2008.11.17.3.fc10 -plymouth-scripts 0.6.0-0.2008.11.12.4.fc10 +plymouth-scripts 0.6.0-0.2008.11.17.3.fc10 -xorg-x11-server-Xorg 1.5.2-12.fc10 +xorg-x11-server-Xorg 1.5.3-5.olpc4.1 -xorg-x11-server-common 1.5.2-12.fc10 +xorg-x11-server-common 1.5.3-5.olpc4.1 --- Changes for xorg-x11-server-Xorg 1.5.3-5.olpc4.1 from 1.5.2-12.fc10 --- + Experimental patch exclusion to fix glyph truncation --- Changes for xorg-x11-server-common 1.5.3-5.olpc4.1 from 1.5.2-12.fc10 --- + Experimental patch exclusion to fix glyph truncation -- 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: Differents behaviours of my application
Hi Aleix, On 18 Nov 2008, at 17:13, Aleix Palet wrote: To do this, I've reading the wiki (which is a bit confusing) and I learned that I have to play with the read_file and write_file options. What I've done is what I write next (with the consequent problems): Wiki baptism by fire :-) I think the best effort is: http://wiki.laptop.org/go/Sugar_Almanac - in the init method of my app, I do the the acticity.Activity.__init__ and then I create the filechooser, I choose the file and then load, I guess i shouldn't do it like this, because when my app is executed through the read_file method, first this __init__ method is called, showing me the filechooser which I don't want! OK. I made some slightly naughty timing trick, after hitting the same problem (Moon activity). After asking the list Tomeu suggested the less naught trick is to see if you are offered a Journal object_id. I've been deflected by localisation/Pootle since then (my excuse), so I've not implemented this yet. It should go something like this: from sugar.datastore import datastore ... ... ... ... dataStore = datastore.get(self.handle.object_id) if dataStore == None: # I'm a journal virgin else: # resumed --Gary - another problem is that the read_file filename parameter, gives me the path of the journal file copy, which is not a .jclic,zip file, then is not the file that I want. So my questions are: - how to organize my code to get the behabiour that I want? - how to get the real path? And finally, I've got another problem which is not as important as the ones before, but if I get an asnwer I would really grateful. When I open the filechooser which is made with and wx.app, which it also has an wx.frame, then I choose the file, but I don't get the window closed and the execution returned to the main app. The window stays opened without showing anything (a grey window). Thank you for everything, maybe the questions are a bit basic, but as I said, is really hard to find some documentation in the olpc wiki. Bye! ___ 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: Differents behaviours of my application
On 18 Nov 2008, at 17:55, Gary C Martin wrote: Hi Aleix, On 18 Nov 2008, at 17:13, Aleix Palet wrote: To do this, I've reading the wiki (which is a bit confusing) and I learned that I have to play with the read_file and write_file options. What I've done is what I write next (with the consequent problems): Wiki baptism by fire :-) I think the best effort is: http://wiki.laptop.org/go/Sugar_Almanac - in the init method of my app, I do the the acticity.Activity.__init__ and then I create the filechooser, I choose the file and then load, I guess i shouldn't do it like this, because when my app is executed through the read_file method, first this __init__ method is called, showing me the filechooser which I don't want! OK. I made some slightly naughty timing trick, after hitting the same problem (Moon activity). After asking the list Tomeu suggested the less naught trick is to see if you are offered a Journal object_id. I've been deflected by localisation/Pootle since then (my excuse), so I've not implemented this yet. It should go something like this: from sugar.datastore import datastore ... ... ... ... dataStore = datastore.get(self.handle.object_id) if dataStore == None: # I'm a journal virgin else: # resumed --Gary OK. Serves me right for copy pasting, I of course actually meant to write the much simpler (and working): def __init__(self, handle): if handle.object_id == None: print I'm a journal virgin else: print I was resumed :-) --Gary - another problem is that the read_file filename parameter, gives me the path of the journal file copy, which is not a .jclic,zip file, then is not the file that I want. So my questions are: - how to organize my code to get the behabiour that I want? - how to get the real path? And finally, I've got another problem which is not as important as the ones before, but if I get an asnwer I would really grateful. When I open the filechooser which is made with and wx.app, which it also has an wx.frame, then I choose the file, but I don't get the window closed and the execution returned to the main app. The window stays opened without showing anything (a grey window). Thank you for everything, maybe the questions are a bit basic, but as I said, is really hard to find some documentation in the olpc wiki. Bye! ___ 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO deployment count?
On Mon, 17 Nov 2008, C. Scott Ananian wrote: On Mon, Nov 17, 2008 at 9:18 PM, [EMAIL PROTECTED] wrote: On Mon, 17 Nov 2008, Eben Eliason wrote: As an asset on our main website, it aims to be as authoritative as possible. The current numbers were populated via the wiki (http://wiki.laptop.org/go/Deployments), which I believe is kept mostly up to date (but I could be wrong). A few of the numbers have been adjusted or added since the initial population of the map via the wiki (Ghana, for instance). If these numbers are low, or deployments are missing, please let me know! What other sources have you found? on the olpc wiki I've seen links to the New York deployment in the past currently one of the links on the front page of the wiki points at http://www.technologyreview.com/blog/editors/22041/ (March 2008) which states that 400k laptops are going to peru also on that same front page there is a link to http://radian.org/notebook/astounded-in-arahuay (also march 2008) which states 260 odd thousand laptops. I may be smoking crack, but I believe that our contracts typically have options for extension attached. I believe the 190,000 machines in my slides are the completely paid for machines[*] while the larger numbers you quoted are sizes of the order if some/all options are exercised.[**] Naturally, the stories immediately following a contract being signed concentrate on the potential size of the order. But even the actually paid for numbers are impressive (IMO). I've learned that it's a long and rocky road from initial announcement to actual delivered machines, which is why I view new announcements (for example, the Portugal Classmate deal) as highly suspect until actual machines start arriving in people's hands. In countries all over the world, XOs are *actually arriving in children's hands*. --scott [*] roughly means there are lots of minor details I'm omitting; Peru has some dispute with its shipping company, for example, and there are some lawsuits pending over exactly who is paying what to whom, and some number of the manufactured XOs are currently stuck in a warehouse in Shanghai because they were brought out of a free trade zone they were never supposed to leave. I'm glad I'm not actually working on the business side of OLPC! [**] Disclaimer, if needed: don't take this an an authoritative statement, this is just a rough guess based on the casual conversations I've had. Like I said, I'm not terribly interested in the business details; I'm happy just working on software. I can put you in touch with real people if you actually want/need a definitive answer -- but they all seem pretty stressed busy this week. rough numbers are good enough for answering critics who claim that OLPC is a failure, the only thing is that if different people give vastly different numbers we end up looking like idiots. the deployments page mentioned above is not linked to from the main page of the wiki (this is one of my gripes about most wikis, they end up having lots of information in them, but the linking structure is frequently so bad that you would never know it, which leads to multiple pages being maintained by different people, with conflicting information) if you could pass this along to the folks on the business side. they need to realize that we are part of their sales/marketing force. David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
On Mon, Nov 17, 2008 at 11:58 PM, Peter Robinson [EMAIL PROTECTED] wrote: I've started looking through the various packages that have been pulled into joyride as part of the upgrade to Fedora-10 and reviewing packages to see what differs from upstream, 8.2 and various other olpcX packages. I'm aware of a number of packages that have been pulled in due to differences in the packages between the old olpc3 branch and upstream So what's your view on how we should handle this? You already detailed your views on packages where we actually modify the upstream code, such as totem-pl-parser: we should time (maybe a lot of it) trying to fix the upstream code so that they accept our change. I don't know how this will fly for already-overworked OLPC employees, but for me, I can work with that. What about when we just change the dependencies? For example, SDL_mixer. Dennis already forked it, but let's pretend he didn't. What would be the ideal process for us to go through while working with Fedora? By the way, one of the original aims of OLPC was to get the OS down to 100mb (compressed). So this is going to be a painful, ongoing battle. But thanks a lot for your help :) Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
On Tue, Nov 18, 2008 at 7:39 PM, Daniel Drake [EMAIL PROTECTED] wrote: I don't know how this will fly for already-overworked OLPC employees, but for me, I can work with that. It seem like Peter and the other Fedora guys are offering to help us poor overworked OLPC developers :) Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
And this is a very important priority for those poor overworked OLPC developers! We need a continued effort and commitment to push OLPC code upstream, including the recruitment of as many helpful volunteers as possible. One way to help keep those volunteers on board is to make it clear that we're taking this commitment seriously as an ongoing project, not just an interesting exercise for a month or two. - Ed On Nov 18, 2008, at 1:52 PM, Marco Pesenti Gritti wrote: On Tue, Nov 18, 2008 at 7:39 PM, Daniel Drake [EMAIL PROTECTED] wrote: I don't know how this will fly for already-overworked OLPC employees, but for me, I can work with that. It seem like Peter and the other Fedora guys are offering to help us poor overworked OLPC developers :) Marco ___ 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: F-10 joyride vs 8.2 - getting fixes upstream.
I've started looking through the various packages that have been pulled into joyride as part of the upgrade to Fedora-10 and reviewing packages to see what differs from upstream, 8.2 and various other olpcX packages. I'm aware of a number of packages that have been pulled in due to differences in the packages between the old olpc3 branch and upstream So what's your view on how we should handle this? Inlined below but the problem we have at the moment with things pretty locked down in preparation for Fedora-10 final the changes and fixes we get in are being held in the updates queue (like the ones I fixed yesterday). A large chunk of the differences are already upstream in Fedora 10. The rest I'm prepared to run with as much as possible and I'm sure gregdek, jkatz and others on the fedora-olpc are there to help me out, plus of course the no doubt copious advice from this list ;-) The reason I propose this while might be a bit more work now it means that overall fedora mainline will end up assisting in the majority of the work. You already detailed your views on packages where we actually modify the upstream code, such as totem-pl-parser: we should time (maybe a lot of it) trying to fix the upstream code so that they accept our change. I don't know how this will fly for already-overworked OLPC employees, but for me, I can work with that. The totem-pl-parser is the harder style to deal with as we need upstream totem project. These are the ones that are going to take longer to deal with and we'll probably have to fork for this release cycle. What about when we just change the dependencies? For example, SDL_mixer. Dennis already forked it, but let's pretend he didn't. What would be the ideal process for us to go through while working with Fedora? These ones are much much easier to fix as its within the Fedora project. We'll issues we'll have is with the more unresponsive developers but there are ways to deal with those. I'm quite happy to deal with these ones, log bugs, and even make the changes required in conjunction with the package maintainers. There's a couple of ways it can be dealt with. Someone can file a bug an link it against the tracker bug so I can chase. Or to flag them to me and I'll file the bug and chase. I already have done some of these. By the way, one of the original aims of OLPC was to get the OS down to 100mb (compressed). So this is going to be a painful, ongoing battle. But thanks a lot for your help :) I figured there would be some sort of aim like this. Where are we on this aim of the 100 meg with say the 8.2 release? Looking at the correlation between the different releases below it looks like the 8.2 release was the smallest and as we stand we're not that much bigger than update_1. But I suspect that is the sizing is based of a bunch of rpms as opposed to install size. Remove just perl I we'll be below update_1, from there I think it should be achievable to get the size down to 8.2 in a pretty reasonable time. http://dev.laptop.org/~bert/8.2-pkgs.html BTW is there a live-cd or VM image download of joyride? I would like to run one up on a VM environment where I can run some RPM dep hacky scripts against the rpm install. Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
On Tue, Nov 18, 2008 at 9:09 PM, Peter Robinson [EMAIL PROTECTED] wrote: Inlined below but the problem we have at the moment with things pretty locked down in preparation for Fedora-10 final the changes and fixes we get in are being held in the updates queue (like the ones I fixed yesterday). Don't let this slow you down. Tag your packages as dist-olpc4. I just did these for the 3 you have already done (thanks!). They will appear in joyride later tonight. A large chunk of the differences are already upstream in Fedora 10. The rest I'm prepared to run with as much as possible and I'm sure gregdek, jkatz and others on the fedora-olpc are there to help me out, plus of course the no doubt copious advice from this list ;-) Thanks. With the Fedora 9 upgrade, we found it really useful to have a wiki page listing the outstanding regressions that were related to upgrade fallout. I created one here: http://wiki.laptop.org/go/OLPC-4 and populated it with the parts from Distro_version_migration_nastiness that I think need to be fixed for F10/9.1. Feel free to update and modify as you see fit, or ignore if you think it is useless :) The reason I propose this while might be a bit more work now it means that overall fedora mainline will end up assisting in the majority of the work. Agreed, and now is the right time in the cycle. These ones are much much easier to fix as its within the Fedora project. We'll issues we'll have is with the more unresponsive developers but there are ways to deal with those. I'm quite happy to deal with these ones, log bugs, and even make the changes required in conjunction with the package maintainers. Sounds good. I think you will find that some are harder to fix, even though they are entirely Fedora, because OLPC has different requirements from your normal desktop users. Let's see how we get on :) There's a couple of ways it can be dealt with. Someone can file a bug an link it against the tracker bug so I can chase. Or to flag them to me and I'll file the bug and chase. I already have done some of these. OK. I want to help with some of this, I did a lot of the work for F9 so know what to look for and how to address these things. Expect some bugs coming from my end :) I figured there would be some sort of aim like this. Where are we on this aim of the 100 meg with say the 8.2 release? Looking at the correlation between the different releases below it looks like the 8.2 release was the smallest and as we stand we're not that much bigger than update_1. But I suspect that is the sizing is based of a bunch of rpms as opposed to install size. Remove just perl I we'll be below update_1, from there I think it should be achievable to get the size down to 8.2 in a pretty reasonable time. http://dev.laptop.org/~bert/8.2-pkgs.html Our smallest release by far was ship2. The above pages show it as bigger than 8.2, but actually ship2 includes activities and library content (over 100mb, I think) which we exclude from later builds and install separately. ship2 including activities and library is 279mb. 8.2-g1g1-767 including activities and library is 450mb. Not a fair comparison because 8.2 includes more activities, including the 100mb WikipediaEN, but the point is there: we are continually getting bigger and it is a difficult battle to keep things the same size, never mind making them get smaller. BTW is there a live-cd or VM image download of joyride? I would like to run one up on a VM environment where I can run some RPM dep hacky scripts against the rpm install. I think you can run the joyride images in emulation. I also think its about time we got you an XO. Submit an application here: http://projectdb.olpc.at/ Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
debxo 0.4 release
Hi, I just tagged DebXO 0.4 release. This release looks much much nicer, thanks to a new Xorg driver. There's also a jffs2 fix which should make bootup from NAND quite a bit faster. The release can be found here: http://lunge.mit.edu/~dilinger/debxo-latest/images/ Note that there's a known bug when running DebXO off the NAND; every once in a while during boot, a race will be encountered whereby the machine kernel will loop infinitely with CRC Node errors. It's not critical, and a reboot should fix it. It's been there all along, as some people have already seen. CHANGES: - Gnome improvements: the battery applet shows up properly, GUI apps that require root access (ie, the stuff in System-Administration) should launch properly despite lack of a password, auto-mounting of SD and USB keys is now enabled. - A new geode Xorg driver (2.11) is included. This fixes font issues with a number of applications, and things simply look better. With 0.3, the default fonts in LXDE looked terrible; in 0.4, this is no longer the case. Applications like NetSurf (where font size cannot be overridden) are now usable. - Better hardware support; the MIC LED no longer is on by default, the ALSA driver saw a bunch of updates, and the gamekeys now work. I've mapped the gamekeys to scroll on the right, and support pageup/pagedown on the left. This could change later on, depending upon feedback and what HAL ends up accepting upstream. The brightness and sound adjustment keys on the keyboard now work. Those are just user-visible changes. Other changes can be seen at: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary INSTALLATION ONTO NAND FLASH: To install onto the XO's NAND flash, download the jffs2/$DESKTOP.dat and jffs2/$DESKTOP.img to a USB or SD stick (where $DESKTOP is one of the various desktops - gnome, kde, lxde, sugar, base, or awesome). Boot into OFW (make sure your XO is unlocked!), and run update-nand disk:\$DESKTOP.img or update-nand sd:\$DESKTOP.img (depending upon whether you downloaded to an SD or USB disk). If update-nand spits out any errors, make sure you're running an appropriately up-to-date version of OFW. The q2d* series do not support update-nand, and versions q2e18 and q2e19 are known to be buggy with partitions. Firmware and instructions for upgrading can be found here: http://wiki.laptop.org/go/Firmware INSTALLATION ONTO SD/USB: To install onto an SD or USB device, download the ext3/debxo-$DESKTOP.ext3.img.gz file, and run zcat debxo-$DESKTOP.ext3.img.gz /dev/mmcblk0 or zcat debxo-$DESKTOP.ext3.img.gz /dev/sdX (depending upon whether you're writing to an SD or USB disk). Note that this will overwrite any data that is on the SD or USB disk. USAGE: By default, a user 'olpc' is created (with no password, and sudo access). Some desktops automatically start a display manager and log you in; some do not. The root password is disabled by default. This is a stock Debian Lenny system with only a few modifications, so it can obviously be tailored. HACKING: xodist is the name of the collection of scripts that are used to produce DebXO. The git repository can be downloaded via: git clone git://lunge.mit.edu/git/xodist There's also a web interface to that: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary Help is always appreciated. The roadmap for future releases can be found here: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=blob;f=TODO CREDITS: Thanks to James Cameron and Erik Garrison for various patches/tweaks/fixes, and to the various people who tested and provided feedback. Enjoy! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: debxo 0.4 release
Hi, Hi, I just tagged DebXO 0.4 release. This release looks much much nicer, thanks to a new Xorg driver. There's also a jffs2 fix which should make bootup from NAND quite a bit faster. Is the JFFS2 patch in the OLPC kernel too? (If so, got a link to it?) Thanks, - Chris. -- Chris Ball [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: debxo 0.4 release
On Tue, 18 Nov 2008 17:09:29 -0500 Chris Ball [EMAIL PROTECTED] wrote: Hi, Hi, I just tagged DebXO 0.4 release. This release looks much much nicer, thanks to a new Xorg driver. There's also a jffs2 fix which should make bootup from NAND quite a bit faster. Is the JFFS2 patch in the OLPC kernel too? (If so, got a link to it?) Thanks, - Chris. It's the same patch I sent upstream (http://lkml.org/lkml/2008/11/2/115). I've got it committed locally to testing and master, but I'm assuming that it's not desired in testing, and I need to rebase master (I broke it) before pushing. I'll do that tonight. The ALSA stuff is also the same stuff I sent upstream (http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=shortlog;h=topic/cs5535audio), but I was planning on letting this flow into master via upstrea. OLPC currently works around the issues I fixed in userspace, so it's not pressing. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Devel Digest, Vol 33, Issue 54
Aleix, I think the simplest thing to do might be to give your Activity a Toolbar, and let the user click a button on the toolbar to open the File Open dialog. That way your Activity maybe could work with more than one file before the user exits it. So you could resume an existing Journal entry, create a new entry, or select an entry using the dialog. read_file gives the path to a copy of your file. It might not have a .zip suffix (but in my own experience it generally does) but it is a copy of your file. There are ways in Python to check if a given file is a Zip file without knowing its file name. It would help if we knew what your Activity does. James Simmons Date: Tue, 18 Nov 2008 18:13:56 +0100 From: Aleix Palet [EMAIL PROTECTED] Subject: Differents behaviours of my application To: devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Hi, I'm developing an application for sugar, and the problem is that I want different behaviours depending on the execution of my app: - when my app is opened through the icon of lower menu, I want a filechooser to appear, so I can choose which file to open. - when somebody downloads a .jclic.zip file, and clicks in the option resume with my app (I have made my app appear as an option to resume using mime _types), I don't want the filechooser, I want my app to open directly that file To do this, I've reading the wiki (which is a bit confusing) and I learned that I have to play with the read_file and write_file options. What I've done is what I write next (with the consequent problems): - in the init method of my app, I do the the acticity.Activity.__init__ and then I create the filechooser, I choose the file and then load, I guess i shouldn't do it like this, because when my app is executed through the read_file method, first this __init__ method is called, showing me the filechooser which I don't want! - another problem is that the read_file filename parameter, gives me the path of the journal file copy, which is not a .jclic,zip file, then is not the file that I want. So my questions are: - how to organize my code to get the behabiour that I want? - how to get the real path? And finally, I've got another problem which is not as important as the ones before, but if I get an asnwer I would really grateful. When I open the filechooser which is made with and wx.app, which it also has an wx.frame, then I choose the file, but I don't get the window closed and the execution returned to the main app. The window stays opened without showing anything (a grey window). Thank you for everything, maybe the questions are a bit basic, but as I said, is really hard to find some documentation in the olpc wiki. Bye! -- next part -- An HTML attachment was scrubbed... URL: http://lists.laptop.org/pipermail/devel/attachments/20081118/21820603/attachment-0001.htm ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
Inlined below but the problem we have at the moment with things pretty locked down in preparation for Fedora-10 final the changes and fixes we get in are being held in the updates queue (like the ones I fixed yesterday). Don't let this slow you down. Tag your packages as dist-olpc4. I just did these for the 3 you have already done (thanks!). They will appear in joyride later tonight. Cool. A large chunk of the differences are already upstream in Fedora 10. The rest I'm prepared to run with as much as possible and I'm sure gregdek, jkatz and others on the fedora-olpc are there to help me out, plus of course the no doubt copious advice from this list ;-) Thanks. With the Fedora 9 upgrade, we found it really useful to have a wiki page listing the outstanding regressions that were related to upgrade fallout. I created one here: http://wiki.laptop.org/go/OLPC-4 and populated it with the parts from Distro_version_migration_nastiness that I think need to be fixed for F10/9.1. Feel free to update and modify as you see fit, or ignore if you think it is useless :) Nope, I like central locations for documentation, it makes it lower entry level for others :-) The reason I propose this while might be a bit more work now it means that overall fedora mainline will end up assisting in the majority of the work. Agreed, and now is the right time in the cycle. These ones are much much easier to fix as its within the Fedora project. We'll issues we'll have is with the more unresponsive developers but there are ways to deal with those. I'm quite happy to deal with these ones, log bugs, and even make the changes required in conjunction with the package maintainers. Sounds good. I think you will find that some are harder to fix, even though they are entirely Fedora, because OLPC has different requirements from your normal desktop users. Let's see how we get on :) I have no doubt it will be difficult to get it all upstream, but its not all that different. I like small and fast on my NetBook, and servers. Gives me more resources to do the things I buy the machines for :-) There's a couple of ways it can be dealt with. Someone can file a bug an link it against the tracker bug so I can chase. Or to flag them to me and I'll file the bug and chase. I already have done some of these. OK. I want to help with some of this, I did a lot of the work for F9 so know what to look for and how to address these things. Expect some bugs coming from my end :) I figured there would be some sort of aim like this. Where are we on this aim of the 100 meg with say the 8.2 release? Looking at the correlation between the different releases below it looks like the 8.2 release was the smallest and as we stand we're not that much bigger than update_1. But I suspect that is the sizing is based of a bunch of rpms as opposed to install size. Remove just perl I we'll be below update_1, from there I think it should be achievable to get the size down to 8.2 in a pretty reasonable time. http://dev.laptop.org/~bert/8.2-pkgs.html Our smallest release by far was ship2. The above pages show it as bigger than 8.2, but actually ship2 includes activities and library content (over 100mb, I think) which we exclude from later builds and install separately. ship2 including activities and library is 279mb. 8.2-g1g1-767 including activities and library is 450mb. Not a fair comparison because 8.2 includes more activities, including the 100mb WikipediaEN, but the point is there: we are continually getting bigger and it is a difficult battle to keep things the same size, never mind making them get smaller. Would be nice to have some sort of comparison of the core OS so we have some sort of gauge of how we're going. BTW is there a live-cd or VM image download of joyride? I would like to run one up on a VM environment where I can run some RPM dep hacky scripts against the rpm install. I think you can run the joyride images in emulation. I also think its about time we got you an XO. Submit an application here: http://projectdb.olpc.at/ Already have after gregdek suggested I did, its been approved and I'm just awaiting for delivery. Project is called Fedora Mainline Cheers, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: F-10 joyride vs 8.2 - getting fixes upstream.
Inlined below but the problem we have at the moment with things pretty locked down in preparation for Fedora-10 final the changes and fixes we get in are being held in the updates queue (like the ones I fixed yesterday). Don't let this slow you down. Tag your packages as dist-olpc4. I just did these for the 3 you have already done (thanks!). They will appear in joyride later tonight. A large chunk of the differences are already upstream in Fedora 10. The rest I'm prepared to run with as much as possible and I'm sure gregdek, jkatz and others on the fedora-olpc are there to help me out, plus of course the no doubt copious advice from this list ;-) Thanks. With the Fedora 9 upgrade, we found it really useful to have a wiki page listing the outstanding regressions that were related to upgrade fallout. I created one here: http://wiki.laptop.org/go/OLPC-4 and populated it with the parts from Distro_version_migration_nastiness that I think need to be fixed for F10/9.1. Feel free to update and modify as you see fit, or ignore if you think it is useless :) The reason I propose this while might be a bit more work now it means that overall fedora mainline will end up assisting in the majority of the work. Agreed, and now is the right time in the cycle. These ones are much much easier to fix as its within the Fedora project. We'll issues we'll have is with the more unresponsive developers but there are ways to deal with those. I'm quite happy to deal with these ones, log bugs, and even make the changes required in conjunction with the package maintainers. Sounds good. I think you will find that some are harder to fix, even though they are entirely Fedora, because OLPC has different requirements from your normal desktop users. Let's see how we get on :) There's a couple of ways it can be dealt with. Someone can file a bug an link it against the tracker bug so I can chase. Or to flag them to me and I'll file the bug and chase. I already have done some of these. OK. I want to help with some of this, I did a lot of the work for F9 so know what to look for and how to address these things. Expect some bugs coming from my end :) Looking through some of the totem and totem-pl-parser dependencies I think its going to one that in the short term at least it will probably be quicker to have our own branch initially as it seems it pulls in gnome-desktop which in turn pulls in alot of the themes etc that we don't need. If someone wants to request the cvs branches I can merge the differences from mainline and the old OLPC-3 branch build and tag it in the morning. Too late here in the UK for me to look at much else today. Cheers, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2553
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2553 Changes in build 2553 from build: 2552 Size delta: 0.39M -ohm 0.1.1-6.11.20080119git.fc7 +ohm 0.1.1-7.22.20080921git.fc10 -olpc-netutils 0.4-2.fc10 +olpc-netutils 0.7-2.fc10 -olpc-utils 0.89-4.olpc4 +olpc-utils 0.89-6.fc10 -pixman 0.12.0-1.fc10 +pixman 0.12.0-2.fc10 +tcpdump 14:3.9.8-6.fc10 --- Changes for ohm 0.1.1-7.22.20080921git.fc10 from 0.1.1-6.11.20080119git.fc7 --- + Add ExclusiveArch i386 so it builds for F-10 + Merge OLPC-3 branch into devel so all changes are in mainline + #8562: Correctly preserve user-set brightness. + #8062: Bugfix -- look for automaticpm, not automatic_pm. + #7981: Use more efficient EC mask setting. + #8062: Inherit automatic/extreme PM settings from the Sugar profile. + #8010: Fix battery status by handling the EC mask over idle suspends. + #7879: Power down wifi chip when lid is closed and mesh is off. + #7986: Close /ofw/model after reading it. + Inherit automatic_pm from the Sugar profile. + Avoid a race by triggering an idle timer reset when we connect to X. + Support setting DCON freeze/mode values; the OHM side of #7357. + EC wakeup mask now decides wakeup logic, removing OHM's temporary wakeups. + Move xauthority from /home/olpc to /var/tmp/olpc-auth. + Implement the OHM side of the sugar control panel power section. + Fix OLPC Trac #7359, segfault due to uninitialized use of X display. + BR intltool --- Changes for olpc-utils 0.89-6.fc10 from 0.89-4.olpc4 --- + Actually commit patch to cvs + Merge OLPC-3 branch into devel + Marco Pesenti Gritti (1): + Marco Pesenti Gritti (1): + Marco Pesenti Gritti (1): + Chris Ball (2): + Chris Ball (1): + Chris Ball (1): + Guillaume Desmottes (1): + Michael Stone (1): + Sayamindu Dasgupta (1): + Chris Ball (1): + C. Scott Ananian (1): + Richard Smith (1): + C. Scott Ananian (2): + Martin Dengler (1): + cscott: dlo#317: Set appropriate ICEAUTHORITY, XAUTHORITY, and XSERVERAUTH + sayamindu: dlo#7474: Choose the XIM method by default. + pgf: dlo#7537: Be more precise when assigning permissions to /home/olpc. + cscott: dlo#7495: Trigger activity update on base OS upgrade. + dsd: dlo#7211: Increase mouse sensitivity. + Bump revision number. + dlo#6432: local installation of RPMs on first boot. + dlo#7171: move network testing tools to olpc-netutils + add olpc-test-devkey script to verify a developer key. + mstone: + erikg: Reduce mouse acceleration. + dsd/marco: Properly initialize a ConsoleKit session. + ausil: + dlo#6945: Added workaround for typo in mfg-data for Ethiopian machines. + dlo#6767: Run make_index.py with a reasonable value of LANG. + dlo#6945: Export GTK_IM_MODULE so that other modules such as Amharic does not get picked up. + dlo#5746: Use a more precise udev ignore-me rule for msh* interfaces. + Substitute $olpc_usb_version for $olpc_home_version to fix a stupid mistake. + Teach olpc-configure about usb customization keys. + Import olpc-audit from Marcus + Import sudo from cscott + Drop become_root + Import olpc-netstatus 0.4 from Yanni + dlo#5746: Do not try to rename msh0. + dlo#5153: Fix sysfs path to rtap + Use GPLv2+ license tag as nothing in this package is GPLv2-only. + Make preview cleaner robust in the case of a missing datastore + Do not bother running journal cleaner on fresh installations (saves time on first boot) + Add a silly TODO list + Bump revision to 0.65 + Import olpc-netlog-0.3 and olpc-netstatus-0.3 + Add 'clean-previews' and incorporate it into olpc-configure. + 'become_root' script merged upstream. + Update License field to GPLv2 in order to match the COPYING file. + Install a simple 'become_root' script to ease dlo#5537. + Rename RPMDIST to DISTVER and DISTVAR to DIST + dlo#5626: Fix permissions in /home/bernie. + Insert extra spacing at the top for cosmetic reasons + Spacing fixes + Add missing cron job for olpc-pwr-prof + Power profile scripts + Construct Rainbow's spool dir if it doesn't exist - #5033 + Ensure /security has reasonable permissions. + Depend on /usr/bin/find + Remove files in $OLPC_HOME before creating them. + Add missing dependencies. + Use /ofw/openprom/model instead of olpc-bios-sig + Add more missing dependencies + Remove stray reference to olpc-bios-sig.c. + Pass absolute paths to rpmbuild + Add back sbin dirs to unprivileged users PATH + Invoke rainbow-replay-spool + Remove stupid 'exit 0' in zzz_olpc.sh that makes bash *exit* rather than skip the scriptlet + Depend on tcpdump for olpc-netcapture. + Fix version replacement in spec file + Merge olpc-netstatus 0.2 + Merge olpc-netlog 0.2 + Really bump revision + Add a couple of new languages + Add missing files + Ensure correct keyboard is loaded even on first boot + Don't create /root/.i18n as it makes us loose the boot time optimization + Add code to
Re: New joyride build 2553
2553: after I start Terminal, the keys along the top of the keyboard no longer work - not the Views, not Frame - nuthin'. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] Setting up XS-0.5 for testing
(Apologies as I haven't done extensive archive/wiki searching and i'm also a bit tired - Please point to RTFM) I'm looking at setting up a simple test rig for playing with the school server, and I have the following hardware for use: * An XO * A generic laptop with a wired a wireless interface and XS-0.5 installed * A generic wireless AP * (A NATTed dhcp'd network with external connectivity) Can I setup a test rig with that hardware - how would you go about it? With a basic XS install, the server seemed to connect to the external network fine, and also created a school-mesh-0 wireless network which was visible from my mac - but not seemingly from the XO. So the next thing I tried was connecting the WAP to the XS ethernet interface. However, on investigation I noticed that dhcpd was not running (and was asking for network_config and domain_config to be run). So I ensured network_config and domain_config were sorted and rebooted. After a reboot dhpcd started up - however, seemingly not giving out leases on the wired interface. I read that using xs-swapnics could sort this out for me - but I don't think it will work because I only have eth0. I can't see in the config where the interface to bind dhcpd and associated services to is specified - can anyone give me any pointers? cheers -- Dan Poltawski signature.asc Description: Digital signature ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Setting up XS-0.5 for testing
2008/11/18 Dan Poltawski [EMAIL PROTECTED]: I'm looking at setting up a simple test rig for playing with the school server, and I have the following hardware for use: * An XO * A generic laptop with a wired a wireless interface and XS-0.5 installed * A generic wireless AP * (A NATTed dhcp'd network with external connectivity) Can I setup a test rig with that hardware - how would you go about it? You are on the right track - the current XS configuration doesn't know what to do with the wireless interface the machine has, so it'll probably ignore it. And tyou can use xs-swapnics even on a single-nic machine, to set the only nic to be eth1. Some of it is documented in the README (README.networking perhaps) for the xs-config package. With a basic XS install, the server seemed to connect to the external network fine, and also created a school-mesh-0 wireless network which was visible from my mac - but not seemingly from the XO. school-mesh-0 probably came from the XO though, when it attempts to setup a mesh connection ot'll send frames that your machine may have interpreted erroneously as an AP. So the next thing I tried was connecting the WAP to the XS ethernet interface. However, on investigation I noticed that dhcpd was not running (and was asking for network_config and domain_config to be run). So I ensured network_config and domain_config were sorted and rebooted. Good step, combine with xs-swapnics and you'll be on the right track I think ... hope that helps! 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
Re: [Server-devel] Setting up XS-0.5 for testing
Martin Langhoff wrote: 2008/11/18 Dan Poltawski [EMAIL PROTECTED]: I'm looking at setting up a simple test rig for playing with the school server, and I have the following hardware for use: * An XO * A generic laptop with a wired a wireless interface and XS-0.5 installed * A generic wireless AP * (A NATTed dhcp'd network with external connectivity) Can I setup a test rig with that hardware - how would you go about it? You are on the right track - the current XS configuration doesn't know what to do with the wireless interface the machine has, so it'll probably ignore it. And tyou can use xs-swapnics even on a single-nic machine, to set the only nic to be eth1. Some of it is documented in the README (README.networking perhaps) for the xs-config package. With a basic XS install, the server seemed to connect to the external network fine, and also created a school-mesh-0 wireless network which was visible from my mac - but not seemingly from the XO. school-mesh-0 probably came from the XO though, when it attempts to setup a mesh connection ot'll send frames that your machine may have interpreted erroneously as an AP. So the next thing I tried was connecting the WAP to the XS ethernet interface. However, on investigation I noticed that dhcpd was not running (and was asking for network_config and domain_config to be run). So I ensured network_config and domain_config were sorted and rebooted. Good step, combine with xs-swapnics and you'll be on the right track I think That is what I saw earlier on firstboot, named assumes a default name and starts up without /etc/sysconfig/xs_domain_name, while dhcpd doesn't start because /etc/sysconfig/xs_domain_name is not set. Shouldn't dhcpd be setup with the same default server domain and role for firstboot? Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
