[no subject]
___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Greetings to all for the New Year, Paul Fox, pgf at laptop.org, Sat Dec 5 11:02:48 EST 2015, > the "game controller" is simply 4 separate electrical contacts ... > ... use 'xev' to check ... A "Hardware" section now in http://wiki.laptop.org/go/Game_controller . Corrections, criticisms and suggestions welcome. Can anyone tell where the nomenclature "KP_Up" and etc. originated? A mainframe console in the 1960s? Thanks,... Peter E. -- Telephone 1 360 639 0202 or +13606390202. Bcc: peter at easthope.ca http://easthope.ca/Shop.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Hello James, As you know, I have been building f20 + S0.102 images, using a XO4 with dnarvaez f20 image as building machine. Also, I am working on top your OOB branch. I was able to make these builds without much trouble, until today, when I started to get a glibc errors (please see attached files). The errors occur during or right after the RPMs are being installed in the image, and quite consistently, even after reboots. I reverted my changes in OOB, to the last commit I was able to complete the image, and I still get these errors, I did not change anything in my setup. Any ideas of what this could be? Refs: 1. https://github.com/OneEducation/olpc-os-builder/commits/au2a 1116 blocks *** Error in `/usr/bin/python': munmap_chunk(): invalid pointer: 0x086659b5 *** === Backtrace: = /lib/libc.so.6(+0x6c8b4)[0xb6ca18b4] /lib/libc.so.6(+0x731e8)[0xb6ca81e8] === Memory map: 8000-9000 r-xp b3:02 1587 /usr/bin/python2.7 0001-00011000 r--p b3:02 1587 /usr/bin/python2.7 00011000-00012000 rw-p 1000 b3:02 1587 /usr/bin/python2.7 00012000-086fa000 rw-p 00:00 0 [heap] b4393000-b46a6000 rw-p 00:00 0 b46a6000-b47e8000 rw-s 07:00 131120 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.003 b47e8000-b48e9000 rw-p 00:00 0 b49cb000-b49ff000 rw-s 07:00 131119 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.002 b49ff000-b4acb000 rw-s 07:00 131117 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.001 b4acb000-b4bf2000 rw-p 00:00 0 b4bf2000-b4d34000 rw-s 07:00 131120 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.003 b4d34000-b4e0 rw-s 07:00 131117 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.001 b4e0-b4e21000 rw-p 00:00 0 b4e21000-b4f0 ---p 00:00 0 b4f01000-b4f35000 rw-s 07:00 131119 /oob/james-olpc-os-builder/build/imgcreate-UMWlph/install_root/var/lib/rpm/__db.002 b4f35000-b4f3b000 r-xp b3:02 50367 /usr/lib/libnss_dns-2.18.so b4f3b000-b4f42000 ---p 6000 b3:02 50367 /usr/lib/libnss_dns-2.18.so b4f42000-b4f43000 r--p 5000 b3:02 50367 /usr/lib/libnss_dns-2.18.so b4f43000-b4f44000 rw-p 6000 b3:02 50367 /usr/lib/libnss_dns-2.18.so b4f44000-b4f45000 ---p 00:00 0 b4f45000-b5744000 rw-p 00:00 0 b5744000-b5748000 r-xp b3:02 2588 /usr/lib/libuuid.so.1.3.0 b5748000-b574f000 ---p 4000 b3:02 2588 /usr/lib/libuuid.so.1.3.0 b574f000-b575 r--p 3000 b3:02 2588 /usr/lib/libuuid.so.1.3.0 b575-b5751000 rw-p 4000 b3:02 2588 /usr/lib/libuuid.so.1.3.0 b5751000-b578e000 r-xp b3:02 6494 /usr/lib/libdbus-1.so.3.7.4 b578e000-b5795000 ---p 0003d000 b3:02 6494 /usr/lib/libdbus-1.so.3.7.4 b5795000-b5796000 r--p 0003c000 b3:02 6494 /usr/lib/libdbus-1.so.3.7.4 b5796000-b5797000 rw-p 0003d000 b3:02 6494 /usr/lib/libdbus-1.so.3.7.4 b5797000-b57ad000 r-xp b3:02 11348 /usr/lib/python2.7/site-packages/_dbus_bindings.so b57ad000-b57b4000 ---p 00016000 b3:02 11348 /usr/lib/python2.7/site-packages/_dbus_bindings.so b57b4000-b57b5000 r--p 00015000 b3:02 11348 /usr/lib/python2.7/site-packages/_dbus_bindings.so b57b5000-b57c rw-p 00016000 b3:02 11348 /usr/lib/python2.7/site-packages/_dbus_bindings.so b57c-b57c9000 r-xp b3:02 7751 /usr/lib/python2.7/lib-dynload/pyexpat.so b57c9000-b57d ---p 9000 b3:02 7751 /usr/lib/python2.7/lib-dynload/pyexpat.so b57d-b57d1000 r--p 8000 b3:02 7751 /usr/lib/python2.7/lib-dynload/pyexpat.so b57d1000-b57d2000 rw-p 9000 b3:02 7751 /usr/lib/python2.7/lib-dynload/pyexpat.so b57d2000-b57f2000 r-xp b3:02 11555 /usr/lib/libexpat.so.1.6.0 b57f2000-b57f9000 ---p 0002 b3:02 11555 /usr/lib/libexpat.so.1.6.0 b57f9000-b57fb000 r--p 0001f000 b3:02 11555 /usr/lib/libexpat.so.1.6.0 b57fb000-b57fc000 rw-p 00021000 b3:02 11555 /usr/lib/libexpat.so.1.6.0 b57fc000-b5805000 r-xp b3:02 7770 /usr/lib/python2.7/lib-dynload/_elementtree.so b5805000-b580c000 ---p 9000 b3:02 7770 /usr/lib/python2.7/lib-dynload/_elementtree.so b580c000-b580d000 r--p 8000 b3:02 7770 /usr/lib/python2.7/lib-dynload/_elementtree.so b580d000-b580e000 rw-p 9000 b3:02 7770 /usr/lib/python2.7/lib-dynload/_elementtree.so b580e000-b5937000 r-xp b3:02 6442 /usr/lib/libxml2.so.2.9.1 b5937000-b593f000 ---p 00129000 b3:02 6442 /usr/lib/libxml2.so.2.9.1 b593f000-b5943000 r--p 00129000 b3:02 6442 /usr/lib/libxml2.so.2.9.1 b5943000-b5944000 rw-p 0012d000 b3:02 6442 /usr/lib/libxml2.so.2.9.1 b5944000-b5945000 rw-p 00:00 0 b5945000-b5a54000 r-xp
[no subject]
http://www.orientalnetance.sk/components/com_contact/nbcnews.php___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] (no subject)
unsubsribe ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] (no subject)
Halo everyone! I am trying to import activities from an USB drive to the xs schoolserver. I am using server version 0.7. I've read http://dev.laptop.org/git/users/dbagnall/xs-activity-server.git/tree/README I have the activity bundles, the file cold manifest.sha1. I plug in the USB drive on the server, but it's not importing the xo activities from the USB stick. What can i do? Is that normal? Did not have that kind of issues with the 0.6 server version. Thankful, Vanessa ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[no subject]
http://bodyworks.ideasforhumans.com/wp-content/themes/feast/yahoolinksus.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
http://www.eadvancepayday.com/blog/wp-content/themes/BLANK-Theme/googlemail.html___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
http://vocediz.com.br/wp-content/themes/p2/rytj.html?ogh=z.gifosy=wog.jjgsnsbf=ojij ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
http://modellstudio.se/ofmgo.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
Just a heads up for those that are Fedora contributors with either a FAS password or SSH key. Peter -- Forwarded message -- From: Kevin Fenzi ke...@scrye.com Date: Wed, Oct 12, 2011 at 5:44 PM Subject: Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30 To: annou...@lists.fedoraproject.org, devel-annou...@lists.fedoraproject.org Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30 Summary: All existing users of the Fedora Account System (FAS) at https://admin.fedoraproject.org/accounts are required to change their password and upload a NEW ssh public key before 2011-11-30. Failure to do so may result in your account being marked inactive. Passwords changed and NEW ssh public keys uploaded after 2011-10-10 will meet this requirement. Backgound and reasoning: This change event has NOT been triggered by any specific compromise or vulnerability in Fedora Infrastructure. Rather, we believe, due to the large number of high profile sites with security breaches in recent months, that this is a great time for all Fedora contributors and users to review their security settings and move to best practices on their machines. Additionally, we are putting in place new rules for passwords to make them harder to guess. New Password Rules: * Nine or more characters with lower and upper case letters, digits and punctuation marks. * Ten or more characters with lower and upper case letters and digits. * Twelve or more characters with lower case letters and digits * Twenty or more characters with all lower case letters. * No maximum length. Some Do's and Don'ts: * NEVER store your ssh private key on a shared or public system. * ALWAYS use a strong passphrase on your ssh key. * If you must store passwords, use an application specifically for this purpose like revelation, gnome-keyring, seahorse, or keepassx. * Regularly apply your operating system's security related updates. * Only use ssh agent forwarding when needed ( .ssh/config: ForwardAgent no) * DO verify ssh host keys via dnssec protected dns. ( .ssh/config: VerifyHostKeyDNS yes) * DO consider a seperate ssh key for Fedora Infrastructure. * Work with and use security features like SELinux and iptables. * Review the Community Standard Infrastructure security document (link below) QA: Q: My password and ssh private key are fine and secure! Can't I just skip this change? No. We believe the new guidelines above provide an added measure of security compared to the previous requirements. We want all users of our infrastructure to follow the new guidelines to improve one aspect of security across the systems they share. Awareness is also an aspect of good security. By requiring these changes, we also hope to maintain and improve awareness of the process for changing passwords and keys. Q: Can I just change my password and re-upload my same ssh public key? Or upload a bogus ssh public key and then re-upload my old one? A: No. We've installed safeguards to ensure that your new ssh public key is different from your old one. Additionally, some of our contributors may have had accounts on compromised high profile Linux sites recently, and we want to make sure no ssh private keys or passwords used in Fedora Infrastructure were obtained via those incidents. Q: This is a hassle. How often is this going to happen? A: The last mass password change in Fedora was more than 3 years ago. Absent a triggering event, these mass changes will be infrequent. Q: The new password length requirements/rules are too strict. How will I remember passwords that are that long? A: You can employ a password storage application (see above), or use a method like diceware (see below), or construct a memorable sentence or phrase. Q: How do I generate a new ssh key? How do I use it for just Fedora hosts? A: See http://fedoraproject.org/wiki/Cryptography and use a ~/.ssh/config file to match fedoraproject.org hosts for that key. Q: I never uploaded a ssh key to the Fedora Account System, nor am I in a group that needs one, do I still have to upload a new one? A: No. If you don't have a ssh public key uploaded or desire to do so, you can just change your password. More reading: http://infrastructure.fedoraproject.org/csi/security-policy/en-US/html-single/ https://fedoraproject.org/wiki/Infrastructure_mass_password_update http://xkcd.com/936/ http://www.iusmentis.com/security/passphrasefaq/ http://world.std.com/~reinhold/diceware.html http://fedoraproject.org/wiki/Cryptography -- announce mailing list annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/announce signature.asc Description: PGP signature ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Hi SGers... I thought I might try helping test the F11 Build 10 on an XO-1. I have one that had a developer key way back in the summer of 2008. I have reflashed the machine numerous times as software updates have arrived... using the No-fail Update, which I thought was supposed to erase everything. Tonight, when I turned the machine on, I pressed the escape key just for fun to see what would happen. It went to the same ok prompt I get on the XO-1.5 O am testing. Did the developer key persist through the numerous reflashings the machine has endured in the past year or so or do I need to go pick it up again? Caryl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
[resend from subscribed address] last week i announced a daemon that would activate the grab keys on the XO keyboard. a day or two later there was a thread about how it would be nice if the action of the touchpad rotated with the screen (in much the same way that the dpad keys do). since my daemon was already looking at every input event, it seemed a natural place to implement the rotation feature. and after doing that, the name seemed like it should change. so, announcing olpc-kbdshim. source: http://dev.laptop.org/git?p=users/pgf/olpc-kbdshim rpm: http://dev.laptop.org/~pgf/rpms/olpc-kbdshim-1-1.i386.rpm after installing the rpm you need to fully reboot your laptop to get the plumbing set up properly. the rpm includes a new command olpc-rotate which takes care of all the mechanics of screen and touchpad rotation. since sugar (currently) handles this key binding, the rpm postinstall script patches /usr/share/sugar/shell/view/keyhandler.py so that it invokes os.system(olpc-rotate) _instead_ of its current builtin behavior. separating it out like this makes olpc-kbdshim and olpc-rotate more useful for non-sugar UIs. i wrote the sugar patch so that it won't break if you uninstall the olpc-kbdshim rpm -- sugar will take over the rotate function again. also, though i haven't tried it on today's brand-new sugar 0.84 (good work everyone!), a look at the current keyhandler.py says the patch should still apply correctly. the topic of ebook-mode touchpad usage came up the other day too. while i didn't create any visible UI support for it, the daemon will put the touchpad in and out of ebook-mode (which means, reflecting it on both x and y axes) using olpc-rotate -e/-n please let me know what you think... paul p.s. btw, the daemon isn't really very olpc-specific. i've been running it on my thinkpad all week, in order to get the use of the grab key scrolling. the thinkpad doesn't have Windows keys (which is what the XO grab keys are), but it turns out the blue Fn key in the corner can be used as a modifier, so that plus my trackstick gives 2D scrolling -- it came in very handy for looking at the bootchart images this morning. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
I would be thrilled to edit and develop educational tools - outside the bos - in exchange for an XO. S. Rivka Levy-Barbero, MSW another, BETTER E address is: srivkal...@comcast.net ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
~s missing shared library aliases I'm trying to build a static wxWidgets library on the XO (for use with the ucblogo project), and it works, except that certain shared libraries are (at least on my XO) missing aliases that exist on my office Linux PC. For example, I have a file named /usr/lib/libXxf86vm.so.1 but the linker is looking for /usr/lib/libXxf86vm.so which on my office machine is linked to the former. Other examples are libjpeg and libtiff. I solved the problem for my own XO by adding the missing links, but that won't work for a project distributed to the kiddies. Can someone tell me the right way to solve this problem? Thanks. ___ 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
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: 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
Re: Subject: Re: Inappropriate use of private meetings lists - Communication of Decisions
Hi NoiseEHC, I agree that the key problem is communication of decisions more than what decisions are being made. Several people have said that recently (e.g. localization team recently made the same point). I hope we can address this at the high level with an agreed process that include milestones for when and how we communicate release status. Scott suggested (ironically on an internal thread) that we use the Fedora process. I put his comment on the talk page of the process home: http://wiki.laptop.org/go/Talk:Release_Process_Home I'll try to flesh out the milestones and key communication steps ASAP. More comments on milestones and communication points welcome. However, that wont address your need for a more granular communication of technical design decisions. People could try to communicate all of those decisions here but that can be a flood of e-mail. The only other thing I can think of is for you to ask for a final call when you need an answer. Is that viable? Any other suggestions? We need to get better at settling threads to a conclusion. Sounds like this thread was discussed but never closed. I encourage people to ask for consensus and then record a decision. The most important aspect is to say what decision has been reached. If people still object strongly you can revise as needed or in the worst case objectors can decide not to participate. Regardless, we need to communicate the current working decisions so everyone is on the same page. HTHs. We could dig deeper in to this specific example if you think that will help teach everyone better communication strategies in the future. You have been a great contributor for many months. We need more people like you in the project so I hope we can keep you happy and show that others like you will be happy participating. Thanks, Greg S Date: Wed, 02 Jul 2008 09:19:52 +0200 From: NoiseEHC [EMAIL PROTECTED] Subject: Re: Inappropriate use of private meetings lists. To: OLPC Devel devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-2; format=flowecd There are top-down decisions being made by a few people that drive the direction of OLPC. These decisions are not waiting for consensus, and they are made by a small number of people. I don't believe this is going to change (at least not in the short term). I, personally, do not care who makes decisions, as long as he is smart and makes good decisions. The problem is that usually I am not notified of such decisions. For example, the move from 32 bit to 16 bit frame buffer just happened silently. One day people debated its merits on this list without reaching any conclusions. Some months later it was 16 bit. Nobody told it. A similar thing is that I am trying to get an answer to the question whether the XO image will be moved to LZO compression or not when we will be rebased to F9. The reason is that I am currently tuning the LZO decompression code and want to know whether this effort is moot or not. Most likely this was already decided by somebody, and frankly I am not qualified enough to debate this decision, I just want to know what it is. Note that I had to reply all to this message and then delete all recipients and then replace CC devel with TO devel. The reason is that this devel list is not set up that the reply-to would be the devel list, and if I do not delete others then the conversation often slips outside devel. See, even the main mailing list is configured wrong. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
Sent from my iPhone ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
They are running Q2D14, and their brethren (same box) are running 703, so there is a good chance that this is a new 703 based bug. wad On Apr 28, 2008, at 2:13 PM, Emiliano Pastorino wrote: Are you using a pendrive with the leases to activate the laptops? Or are you trying wireless? Which build are you using? You can try to search the SN of the laptops you're trying to activate in the lease.sig file to see if they're there... Emiliano On Mon, Apr 28, 2008 at 3:04 PM, John Watlington [EMAIL PROTECTED] wrote: I have two laptops here in Peru that refuse to activate. I have generated leases for (increasingly) 7 days, 3000 days, and 7999 days, and none work. I activated three other laptops using the same key/activation request and they work fine. They boot up and don't give any error messages. They just start flashing the SD, USB, and finally WiFi icons. When activating, they don't give any error message, they just say Powering off in 10 seconds. Any suggestions ? wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel -- Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 3724 int.: 469 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[no subject]
The question has come up from Peruvians who bought G1G1 machines: how can we get Sugar to use Spanish, while keeping an English keymap (because G1G1 machines have english keyboards) ? Please pardon my ignorance... wad ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[olpc-devel] re: no subject
Hi, it would be nice if we have always an additionally subject like [olpc-devel] inserted automaticaly from devel-bounces. I did it this time manually. Otherwise no subject looks like spam... @Mike: please define always a subject thanks, yokoy On Thu, 23 Aug 2007 12:14:45 +1200 Mike Usmar [EMAIL PROTECTED] wrote: OK, hopefully this is an easy question I want to upgrade to build 542, and have the downloaded and un zipped to a UDB drive in boot the olpc-auto.zip, and the latest OS image and .crc file, so in the boot directory I have 6 files q2c24.rom; os542.img; os542.crc; usbupgos.img, usbupgrd.img, and olpc.fth I power up the Laptop and get this message Noot devices /usb/disk:\boot\olpc.fth arguments: [EMAIL PROTECTED]:17:Tyuy_mask? Somebody tell me what I am doing wrong Mike U ___ 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
no subject
OK, hopefully this is an easy question I want to upgrade to build 542, and have the downloaded and un zipped to a UDB drive in boot the olpc-auto.zip, and the latest OS image and .crc file, so in the boot directory I have 6 files q2c24.rom; os542.img; os542.crc; usbupgos.img, usbupgrd.img, and olpc.fth I power up the Laptop and get this message Noot devices /usb/disk:\boot\olpc.fth arguments: [EMAIL PROTECTED]:17:Tyuy_mask? Somebody tell me what I am doing wrong Mike U ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: no subject
Mike Usmar wrote: OK, hopefully this is an easy question I want to upgrade to build 542, and have the downloaded and un zipped to a UDB drive in boot the olpc-auto.zip, and the latest OS image and .crc file, so in the boot directory I have 6 files q2c24.rom; os542.img; os542.crc; usbupgos.img, usbupgrd.img, and olpc.fth I power up the Laptop and get this message Noot devices /usb/disk:\boot\olpc.fth arguments: [EMAIL PROTECTED]:17:Tyuy_mask? Somebody tell me what I am doing wrong Mike U ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel What you didn't mention is the firmware version you are currently running. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: no subject
In any case, the recipe to fix it is to do the firmware upgrade first, manually: ok flash /usb/disk:\boot\q2c25.rom After that you will have up-to-date firmware and the rest of the installation will probably go smoothly. Mike Usmar wrote: OK, hopefully this is an easy question I want to upgrade to build 542, and have the downloaded and un zipped to a UDB drive in boot the olpc-auto.zip, and the latest OS image and .crc file, so in the boot directory I have 6 files q2c24.rom; os542.img; os542.crc; usbupgos.img, usbupgrd.img, and olpc.fth I power up the Laptop and get this message Noot devices /usb/disk:\boot\olpc.fth arguments: [EMAIL PROTECTED]:17:Tyuy_mask? Somebody tell me what I am doing wrong Mike U ___ 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
