Re: wiki.laptop.org upgrade
Sorry to comment on a older topic. But have 2 cents to offer. :) I wasn't active on the wiki around Dec 3rd. And didn't see several items mentioned previously. And certainly appreciate moving to 'openid' as an excellent idea (i was one of the proponents of it about 9 months ago)... But in my mind, simple solution for 'clear communication'. Simply picking a date for upgrade. Post a 'message of the day' with the details, on the wiki pages, at least one *week in advance*. Then on the day-of, point wiki to a backup copy of the db (in read-only mode), put up a 'motd' on the wiki pages Currently in read-only mode for software updates, but still have them up. Upgrade software/database in a test environment and point to the 'real' db. i.e. testwiki.laptop.org. And once running, do a swap of directories. (might also need to update URL references in config.php too) If backup-copy or testing environment is not available, then simply posting a single-page message during the downtime Wiki.laptop.org is currently not available for maintenence, return time approx 15:50 GMT (etc...) Allow only certain IPs to connect via login, everyone else gets the 'offline' message. (Simple IP filter in 'index.php'). Remove redirect when complete. My 2 cents. ;) -iXo On Fri, Dec 5, 2008 at 08:03, Michael Stone mich...@laptop.org wrote: On Fri, Dec 05, 2008 at 07:11:04AM -0500, Ed McNierney wrote: Michael - Thanks; welcome back! I have been working on the request you made last week, and on trying to have something out this week as I said I would. Good to hear. It's been important to me to ensure I'm reflecting OLPC's position as much as possible rather than simply my own personal opinion, and I've been having conversations to that effect. Absolutely! However, as David rightly points out, if it's going to be a joint statement then it needs to be developed jointly at some point. I'd like to see this happen by circulating a series of progressively better drafts until we're satisfied (or to until we give up). When can we expect a second draft from you? (I wrote a first draft last week and circulated it privately under 'distribute to anyone who should read this' terms.) Thanks again for the help. My (long-term) pleasure. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
Hi Bert, On Sun, Dec 21, 2008 at 6:03 PM, Bert Freudenberg b...@freudenbergs.de wrote: Feel free to post it anywhere you think it makes sense. Glad it's useful to some. I already got some feedback after posting to my blog, including the confirmation it indeed works on Windows: From Bert's Blog Update: Reportedly it does work in VMWare Player on Windows too (see comments). Maybe someone can make an appliance from that. I wonder what it would take for someone to create and distribute a standalone player of the 8.2 image for Windows? Would registration be necessary for distribution? http://www.vmware.com/products/player/player-reseller-registration.html This and the VMWare Fusion option would be great for letting non-XO owners try Sugar and participate in testing! What are first steps for this? Brian http://croquetweak.blogspot.com/2008/12/emulating-latest-stable-olpc-xo.html - Bert - On 21.12.2008, at 23:45, Brian Jordan wrote: Hi Bert, This is amazing, thanks! This would be great to have on http://wiki.laptop.org/go/Emulating_the_XO/Quick_Start/Mac Brian On Wed, Dec 3, 2008 at 11:43 AM, Bert Freudenberg b...@freudenbergs.de wrote: Hi everyone, even with XOs readily available now there are quite a lot of reasons why one would want to emulate it on another machine. One being to hook up a projector. Unfortunately there are quite a number of hoops (*) one has to jump through to make it work. Anyway, I made a virtual machine that allows me to emulate the XO on my Mac, running Sugar in the XO's native 1200x900 resolution, scaled down to a nice physical size in a window an my regular screen (fullscreen works too). Sound works (even Tam Tam), Browse works (so networking is good, although I don't see anyone in the neighborhood). Camera and mic are not working (Measure crashes, Record shows blank picture), and a Sugar restart does not actually restart Sugar, but apart from that it seems fully functional, and much nicer than the emulations I had used to date. These are live-sized screenshots (calibrated using the Ruler activity): http://dev.laptop.org/~bert/Ruler-emulated.png http://dev.laptop.org/~bert/Home-emulated.png http://dev.laptop.org/~bert/Journal-emulated.png http://dev.laptop.org/~bert/TamTamMini-emulated.png And here you can get that virtual machine (665 MB, 2 GB unzipped): http://dev.laptop.org/~bert/VMWare-Fusion-8.2-767-bf.zip This is for VMWare Fusion on the Mac, which I found to be much better at running Linux clients than Parallels (I had been using that for 2 years). Give it a try, it's free as in beer for 30 days. No I don't get paid if you buy it. If you extract the disk image from the zip file it might work in VMWare on Windows. Maybe someone can make an appliance from that. (*) Now to the hoops: * I started with the 767/ext3 image from http://download.laptop.org/xo-1/os/official/ * extended to 2 GB by appending /dev/zero (jffs2 compression gives roughly 2 GB too) * enlarged the partition to full 2 GB (using fdisk and ext2resize) * mounted that in a Fedora 10 virtual machine * copied over the F10 kernel, initrd, and modules (olpc kernel wanted AMD instructions) * edited grub.conf to use that kernel * and appended a root=/dev/sda1 kernel arg (the fedora kernel wants to use LVM otherwise) * unmounted * created new virtual machine (that disk, 1 CPU, 256 MB RAM, NAT networking) * booted into that new system * installed Perl (for vmware tools installer) * installed vmware tools (to get the X driver) (but none of the kernel modules, would need make/gcc/etc.) * deleted Perl (to restore the default sw environment) * copied the existing xorg-vmware.conf to xorg.conf (to get 1200x900 resolution w/ 200 dpi) * booted into Sugar (looks really nice so scaled down) * installed activities (took a long time, maybe it's my DSL) * tested a bit * rm -r ~olpc/.sugar (to remove my personal data) * should have deleted sshd host keys, too, but didn't * shut down * zip * upload * ... * ... * ... * still no profit? ;) Enjoy. And maybe remove some of the obstacles in future releases (a disk image with headroom and a standard kernel would be simple to do and go a long way). - 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: Emulating 8.2-767
On Mon, Jan 05, 2009 at 01:07:00PM -0500, Wade Brainerd wrote: I would love to convert my OLPC Installer for Windows over to VMWare. In my experience it provides a better experience on Windows. I'd also like to convert it over to using Bert's image rather than the stock 8.2.0 image. What would be even better would be for the OLPC guys to set up emulator builds which mirror the regular Joyride, Staging, etc. builds and apply Bert's customizations automatically. Wade, Is there something you need access to (e.g. an account?) that prevents you from doing this yourself? Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
Hi, I would love to convert my OLPC Installer for Windows over to VMWare. In my experience it provides a better experience on Windows. I'd also like to convert it over to using Bert's image rather than the stock 8.2.0 image. What would be even better would be for the OLPC guys to set up emulator builds which mirror the regular Joyride, Staging, etc. builds and apply Bert's customizations automatically. My attitude recently has been that Sugar wants to target all of these machines, so it's not necessary for people to emulate OLPC's builds anymore -- if someone on a Mac wants to run Sugar, they can install Fedora 10 in an emulator and run yum install sugar, for example. (There's also the Sugar on a Stick ISO, which saves the and then install Sugar part: http://sugarlabs.org/go/Sugar_on_a_Stick .) Do you think this approach is misguided? Or, maybe there's something that currently the OLPC builds offer that the other solution doesn't that we should try to move upstream? Thanks, - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
On Mon, Jan 5, 2009 at 1:16 PM, Michael Stone mich...@laptop.org wrote: On Mon, Jan 05, 2009 at 01:07:00PM -0500, Wade Brainerd wrote: I would love to convert my OLPC Installer for Windows over to VMWare. In my experience it provides a better experience on Windows. I'd also like to convert it over to using Bert's image rather than the stock 8.2.0 image. What would be even better would be for the OLPC guys to set up emulator builds which mirror the regular Joyride, Staging, etc. builds and apply Bert's customizations automatically. Wade, Is there something you need access to (e.g. an account?) that prevents you from doing this yourself? Knowledge and time. :) -Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
It's just a ton more work to find emulator software, pick an OS, set it up, and install everything. I'd like all my Windows and Mac loving game developer buddies to just have a one click download and launch into Sugar. -Wade On Mon, Jan 5, 2009 at 1:15 PM, Chris Ball c...@laptop.org wrote: Hi, I would love to convert my OLPC Installer for Windows over to VMWare. In my experience it provides a better experience on Windows. I'd also like to convert it over to using Bert's image rather than the stock 8.2.0 image. What would be even better would be for the OLPC guys to set up emulator builds which mirror the regular Joyride, Staging, etc. builds and apply Bert's customizations automatically. My attitude recently has been that Sugar wants to target all of these machines, so it's not necessary for people to emulate OLPC's builds anymore -- if someone on a Mac wants to run Sugar, they can install Fedora 10 in an emulator and run yum install sugar, for example. (There's also the Sugar on a Stick ISO, which saves the and then install Sugar part: http://sugarlabs.org/go/Sugar_on_a_Stick .) Do you think this approach is misguided? Or, maybe there's something that currently the OLPC builds offer that the other solution doesn't that we should try to move upstream? Thanks, - Chris. -- Chris Ball c...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Ticket #7785 - the big picture
Ticket #7785 was an example of a general situation which I believe can evoke dissatisfaction on the part of the user. The scenario: A. The user has a good working connection to the outside world B. That connection stops working (for whatever reason) C. What the system ends up doing does not satisfy the user D. The user specifies (perhaps restarts) the connection he wants The theoretical problem is providing (D). I'm assuming the user's choices for communicating with the outside world are: connecting via wifi, connecting via mesh, or connecting via wired. - To connect via wifi, there ought to be an icon in Neighborhood - To connect via mesh, I assume the user can use the icon in Frame [this is not yet working in Joyride] - To connect via wired, I currently know of no explicit icon [thus #7785: restarting wired might require rebooting ?] The practical problem is implementing (C). In the case of #7785, the current XO implementation was unable to automatically restart a previously existing wired connection. [I'm speculating that some of the reported difficulties with wireless might result if the current XO implementation were unable to immediately restart from an interruption to a previously existing wireless connection.] When (B) occurs, if the (C) implementation is able to provide a satisfactory new connection (e.g., change to an AP with better signal strength) -- well and good. But if the system's attempt to provide a replacement connection fails, the (C) implementation ought to give priority to re-establishing the connection (A) that existed. Then, user intervention (D) might be avoided. Thanks, mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
It may be feasible to do this on Fedora, but it is not yet feasible on Ubuntu. Sugar doesn't do anything interesting there because the networking is broken. (They are working on it and the problem might be solved in a test version, but it isn't feasible for someone who just wants to use standard means for installing packages to obtain and try out Sugar.) It is nice that, as packaged, it is offered as one of the window manager choices, so I believe it will soon be a good option. But with no convenient way to get the activities from the activity page, it isn't interesting yet. (I tried to put it on donated laptops I was setting up for use by teachers in a nearby school.) My attitude recently has been that Sugar wants to target all of these machines, so it's not necessary for people to emulate OLPC's builds anymore -- if someone on a Mac wants to run Sugar, they can install Fedora 10 in an emulator and run yum install sugar, for example. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [Testing] Please help test our pre-release build of 8.2.1
Greg Smith wrote: Hi Sugar team, Can you help clarify the right Browse version for 8.2.0 and 8.2.1 per the thread below? Latest version in Sucrose 0.82 of Browse was 99. Then for the 0.84 we used 100 and ongoing integer numbers. So there is one Browse activity 101 targeted at 0.84 which I released. Today we are at version 102 already, I have updated http://wiki.laptop.org/go/Activities/Joyride to reflect this. So even though not very clear, Sayamindu can go now and use 101 or 100 for his pdf-enable release. HTH, Simon I also left a related note on the 0.83 release notes discussion page: http://sugarlabs.org/go/Talk:DevelopmentTeam/Release/Releases/Sucrose/0.83.3 Thanks, Greg S ** Date: Sun, 04 Jan 2009 18:09:37 -0500 From: Mikus Grinbergs mi...@bga.com Subject: Re: [Testing] Please help test our pre-release build of 8.2.1 To: OLPC Devel Mailing List devel@lists.laptop.org, test...@lists.laptop.org Message-ID: 496141b1.9040...@bga.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Gary wrote: Browse-98 . . . . . . . x x Browse-101 needed for 8.2.1 PDF support I Tested Browse-101 using the staging-7 build: - Browse-101 listed on http://wiki.laptop.org/go/Activities/G1G1 (i.e., http://dev.laptop.org/~erikos/bundles/0.83/Browse-101.xo) is unacceptable to me -- it will not allow on-line user changes to the entries in about:config (I selected an entry and left-clicked, then clicked on 'modify' - nothing happened). [Besides, it copies PDFs to Journal, instead of showing them.] [Other wiki pages (Activities/G1G1/8.2) listed only Browse-98.] - http://dev.laptop.org/raw-attachment/ticket/9112/Browse-101.xo, built by Sayamindu, works - I *can* modify about:config Thus it appears there is Browse-101, and then there is Browse-101. mikus ___ Sugar-devel mailing list sugar-de...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Wine activity
Yeah, I was thinking along the lines of a WineLearning activity or similar, versus bundling stuff with the main Wine activity. Wade On Jan 4, 2009, at 11:32 PM, Vincent Povirk madewokherd+8...@gmail.com wrote: I'd prefer to avoid bundling in general because it adds to the disk space requirement. I can justify 7-zip and Firefox because they tend to be needed for doing anything useful. If there's a useful program that works very well on an XO running the Wine activity and has no native sugar equivalent, I may be willing to throw in a shortcut that downloads/installs it. For programs in that category, I may also consider helping the author create a stand-alone activity. Vincent Povirk ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
On Mon, Jan 05, 2009 at 01:18:53PM -0500, Wade Brainerd wrote: On Mon, Jan 5, 2009 at 1:16 PM, Michael Stone mich...@laptop.org wrote: On Mon, Jan 05, 2009 at 01:07:00PM -0500, Wade Brainerd wrote: I would love to convert my OLPC Installer for Windows over to VMWare. In my experience it provides a better experience on Windows. I'd also like to convert it over to using Bert's image rather than the stock 8.2.0 image. What would be even better would be for the OLPC guys to set up emulator builds which mirror the regular Joyride, Staging, etc. builds and apply Bert's customizations automatically. Wade, Is there something you need access to (e.g. an account?) that prevents you from doing this yourself? Knowledge and time. Well, just be aware that while I can't help much with the time part, I'm more than happy to help with the knowledge part in any way I can. Just let me know what works best for you. Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please help test our pre-release build of 8.2.1
On Fri, Jan 02, 2009 at 11:04:01PM +0100, Bert Freudenberg wrote: On 02.01.2009, at 17:09, Brian Pepple wrote: Hi All, A pre-release build of 8.2.1 is now available for testing. It has passed an initial smoke test and now needs broader testing. The build download and problem reporting instructions are here: http://wiki.laptop.org/go/Friends_in_testing#Current_status The very early draft release notes are here: http://wiki.laptop.org/go/Release_Notes/8.2.1 Please send a note to the list if you try this build even if you don't find anything interesting. We want to measure our test capacity. You should mention that you want people to test the latest staging build, not the latest 8.2.1 build (which is exactly the same as 8.2.0 at this point): http://dev.laptop.org/~bert/8.2.1-staging.html This is a significant change from previous release procedures (e.g., I was not even aware that staging builds were meant for testing). Bert, Here's the idea: (f10/olpc4)(f9/olpc3) | | v v joyride staging | | v v (9.1.0)8.2.1 \ \ available now. \ will be created eventually (This is the first time we've had two active integration streams.) Does this help clarify things? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Yay!, Bee, See (ABC) software
Such a system sounds great to me! If it's similar to the widget formats supported by the Mac OS X's Dashboard, Konfabulator, and/or Opera that would be even better, since it would tie into an existing library of useful software. Basically, those use ZIP files with various custom layouts, content-types and HTML. I have constructed a widget package which worked in both Opera and Mac OS X's Dashboard, and it was not too difficult (only the Content-Type varied, which I handled using symbolic link on my Apache server.) -Ben On Sun, Jan 4, 2009 at 7:28 PM, Wade Brainerd wad...@gmail.com wrote: BTW, this activity is a perfect example of what I was talking about with my 'web-activity' and sugar.activity.activity.WebActivity class proposals. You want a way to install it to the home screen, give it an icon, and have it launch seamlessly just like any other activity. As it is, I spent some time last month and ported Yay! Bee See to PyGTK so it would behave as a normal activity, but if we had the system I described in Sugar already, I wouldn't have done so. My link is http://dev.laptop.org/~wadeb/Yay!BeeSee-2.xo Best, Wade On Wed, Dec 10, 2008 at 4:39 PM, Ben Wiley Sittler bsitt...@gmail.com wrote: Hi, I've been playing around with this a bit, and I still can't figure out the xol files. When I download http://wiki.laptop.org/images/2/28/Yay-Bee-See-9.xol In Browse, it does get saved to the Journal, and when I start the xol file from the Journal it launches Browse with the main HTML file from the collection, and a subsequently launched vanilla Browse includes yay-bee-see in the images section of the Library. However, even after I keep both the .xol file and the Browse session, rebooting the machine causes yay-bee-see to disappear from the images section of the Library (and the kept Browse session to show a File Not Found message) until I open the .xol file again. Is this intended/expected behavior? Is there some way to keep user-installed Library Collections installed across reboots? Thanks, -Ben On Mon, Nov 24, 2008 at 9:08 PM, Samuel Klein meta...@gmail.com wrote: Yes, that's a fine baseline. As you point out, I had a hard time with the license field; enter what you like but please do include a full LICENSE file in the bundle that provides specific licenses (and attribution where required), image by image. If you download an xol file onto your xo from a webserver that has mimetypes set properly (such as w.l.o) it should automatically install itself into your Library/ directory. I don't know about that page not rendering properly on an XO; what version of Browse are you running? SJ On Mon, Nov 24, 2008 at 11:55 PM, Ben Wiley Sittler bsitt...@gmail.com wrote: Thanks! A few questions, though: 1. Is there any reason I shouldn't start with your version 2 .xol as my baseline? I'd like to update it to use the new lower-resolution, lower-quality images (which still look just fine on the XO-1 even in greyscale high-resolution mode zoomed out to the 1px = 1px scale.) 2. Is there some way to install the .xol more user-friendly than just unzipping it into the ~/Library directory? 3. I notice that in the description on the wiki for the bundle you wrote fdl text, pd, cc-by and cc-sa images. Some of the images are cc-by-sa and fdl, too. Also, the HTML text is actually pd (or at least it was in the version I released — of course you are welcome to license copyrighted derivative versions however you like.) 4. And finally, is there some reason the OLPC wiki does not work right when viewed from an XO-1? I had to go through URL-hacking contortions to open that page in Browse (it just said the page was empty otherwise.) Thanks, (and please pardon my ignorance!) -Ben On Mon, Nov 24, 2008 at 8:43 PM, Samuel Klein meta...@gmail.com wrote: Ben -- When you're zipping up the directory, if you add a metadata file in this subpath: library/library.info and give the resulting zip file the extension .xol, you'll have an XO library bundle. Here is a sample info file, with all required fields : http://wiki.laptop.org/go/Image:Yay-bee-see-library.info Note that the 'name' field in the info file should match the name of the root directory. Our standard is to increment the version # in the metadata every time you make a change; that allows tools like Sugar's software updater know when there are newer versions of packages available to install. SJ On Mon, Nov 24, 2008 at 7:31 PM, Ben Wiley Sittler bsitt...@gmail.com wrote: yeah, i added a 1200x900 version with more agressive JPEG compression which looks good both in color mode and in monochrome mode and is only 4 MiB or so: http://xent.com/~bsittler/yay-bee-see-olpc.zip hosted version: http://xent.com/~bsittler/yay-bee-see-olpc/index.html does that seem any faster? On Mon, Nov 24, 2008 at 3:26 PM,
Problem to use with USB VGA dongle
Hi all, I am trying to use a USB VGA dongle on a XO with release v8.2. The USB VGA dongle is a generic USB to VGA adapter listed in the wiki page: http://wiki.laptop.org/go/Peripherals/USB_to_VGA However, I can not get it work by following the instruction in http://wiki.laptop.org/go/Adding_USB_SVGA It is my setup: yum install xorg-x11-drv-sisusb wget http://downloads.openwrt.org/people/florian/olpc/sisusbvga.ko cp sisusbvga.ko /lib/modules/`uname -r`/kernel/drivers/usb/ sudo depmod -a And then edit /etc/X11/xorg.conf However , if I follow the instruction from wiki , and just add additional section of Monitor and Device. It don't load sisusb driver at all . Therefore, I have also added Screen section and modified the ServerLayout. This time it could load sisusb driver, but still not able to launch a X session on the USB VGA. Nothing was shown in the monitor attached to the USB VGA. The log and config file are attached in the email. Does anybody success to use USB VGA dongle on XO (v8.2)? And could share the experience with me? Thanks. xorg.conf Description: Binary data Xorg.0.log Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please help test our pre-release build of 8.2.1
On 05.01.2009, at 20:18, Michael Stone wrote: On Fri, Jan 02, 2009 at 11:04:01PM +0100, Bert Freudenberg wrote: On 02.01.2009, at 17:09, Brian Pepple wrote: Hi All, A pre-release build of 8.2.1 is now available for testing. It has passed an initial smoke test and now needs broader testing. The build download and problem reporting instructions are here: http://wiki.laptop.org/go/Friends_in_testing#Current_status The very early draft release notes are here: http://wiki.laptop.org/go/Release_Notes/8.2.1 Please send a note to the list if you try this build even if you don't find anything interesting. We want to measure our test capacity. You should mention that you want people to test the latest staging build, not the latest 8.2.1 build (which is exactly the same as 8.2.0 at this point): http://dev.laptop.org/~bert/8.2.1-staging.html This is a significant change from previous release procedures (e.g., I was not even aware that staging builds were meant for testing). Bert, Here's the idea: (f10/olpc4)(f9/olpc3) | | v v joyride staging | | v v (9.1.0)8.2.1 \ \ available now. \ will be created eventually (This is the first time we've had two active integration streams.) Does this help clarify things? That was already clear, my misunderstanding was just that I thought staging was just for, err, staging, then you would make an 8.2.1 release candidate, and that would get tested. - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Customized images
I have a fully customized XO and i need to take an image from it to be installed on several computers inside the project. The thing is i need it to be separated from the activity pack, like the ones you use to update via USB. Questions 1) When i take the image from this one and install it into another, will i have two computers wchi are exactly the same? 2) In order to do this process does it have to be into a unblocked XO or with developer key? Because if that's the case, i can't do it since these are the computers we're gonna use for deployment. 3) Out of the topic question but do you know how can i change the default page from the Browse activity? I did change the index.html file in /home/olpc/.library_pages/ and set it to redirect to the portal page, but i dont like this solution. Thanks for your repplies Carlos Dario Isaza Zamudio::ConTi Ingeniero Electronico Proyecto Todos @l Computador Celular (57) 300 814 9308 Universidad Nacional de Colombia - Sede Manizales GNU/Linux Registered User #465475 eSSuX - Usuarios y Desarrolladores GNU/Linux UNAL Manizales ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2614
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2614 Changes in build 2614 from build: 2613 Size delta: 0.00M -kernel 2.6.27-20081219.2.olpc.6ee9772cc1e8959 +kernel 2.6.27-20090104.1.olpc.48de97f1a90c0e4 -- 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
New staging build 8
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build8 Changes in build 8 from build: 7 Size delta: 0.00M -kernel 2.6.25-20080925.1.olpc.f10b654367d7065 +kernel 2.6.25-20081219.5.olpc.7e2ccbbc5144106 -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Emulating 8.2-767
It may be feasible to do this on Fedora, but it is not yet feasible on Ubuntu. Sugar doesn't do anything interesting there because the networking is broken. (They are working on it and the problem might be solved in a test version, but it isn't feasible for someone who just wants to use standard means for installing packages to obtain and try out Sugar.) From the networking perspective ubuntu 8.10 comes with a release of NM 0.7 so it should work when sugar works with NM 0.7 (I thought there were patches floating around to make sugar 0.82 work with NM 0.7) Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
olpcupdate in Fedora Mainline
Hi All, olpcupdate doesn't seem to be in Fedora mainline, and I don't see a review request for it either. Is there a reason for this? If so could the maintainer (or someone who knows) organise that to happen? I can then review the package and help to get it into Fedora 10 and it can be crossed off the non-mainline list (alone with the olpc-4 branch of olpc-utils as the only difference is its dependence on olpcupdate AFAICS). Cheers, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Wine activity
Wade, :) Any hope of just convincing you to port your program to python/sugar, so it runs the best under sugar? :) -Ixo 2009/1/4 Wade Brainerd wad...@gmail.com Has anyone considered doing a scan of download.com and similar sites for small, free educational software for Windows, and then bundling them with this Wine activity? I'm the author of CueCard, which is a flash card training program for Windows. I have tested and it works great under Vincent's Wine activity. I know there are lots of other free, simple educational programs for Windows and it would be great to be able to offer a 'Wine bundle' activity with a bunch of them pre-installed. I think deployments ought to consider this as well. They can think of it as Windows training for their students :) -Wade On Fri, Dec 12, 2008 at 4:24 PM, Samuel Klein meta...@gmail.com wrote: A popular program that has been requested a few times via Wine is Let's Go for english learning. This activity definitely needs its own section on wiki.laptop.org/go/Wine ... SJ On Wed, Dec 10, 2008 at 4:30 PM, Ben Wiley Sittler bsitt...@gmail.com wrote: That's awesome work! I was able to install Wine and use it, including firefox and a win32 application I had previously build using mingw32 under Linux on another PC and uploaded to a webserver, and then downloaded using firefox inside wine. However, I did notice the following oddities: 1. When I later resumed the activity from the journal, the wallpaper was gone and nothing worked, although the start-menu items for firefox were still there. 2. It was not clear to me how to save wine's state to the journal. 3. At some point the usual 'leave full-screen mode' icon appeared in the upper-right corner, but clicking it seemed to have no effect other than to make it disappear, i.e. no sugar UI appeared and the desktop size did not change. 4. Wine crashed when I used Firefox's download manager to open the location of a downloaded file (winefile appeared briefly, then the whole activity crashed.) I have no idea why yet, but perhaps there is some information left in a log file somewhere I will find. On the bright side, this means it's fairly trivial to run at least some windows-only software on the OLPC now, which is great when there's not yet a Sugar or Linux version. -Ben On Tue, Dec 9, 2008 at 12:02 PM, Vincent Povirk madewokherd+8...@gmail.com madewokherd%2b8...@gmail.com wrote: The Wine activity has advanced to the point where I think it's ready for testing by actual users. The current package, development history, and my todo list are at http://wiki.winehq.org/SugaredWine The intent of this project is to provide a shell that can be used to run Windows programs using Wine in the Sugar environment. It should be good enough that someone used to Windows can grab and install a Windows program without help, once the activity is installed. Ideally, the installer and software will both work fine in Wine and within the hardware limitations of an XO. In this ideal case, someone used to Windows should be able to operate it without help. If it does not live up to this ideal for platinum software (according to the Wine appdb) whose hardware requirements the XO meets, I want to know about it and hopefully fix it. Wine bugs and hardware limitations mean a lot of Windows programs won't work or won't work properly. On Linux, one can often push the compatibility much further than what works out of the box by looking at console messages (the log viewer works for this) and tweaking Wine. Don't expect everything to work perfectly, but don't give up if it doesn't. This is normal, even on Linux. Winehq.org has support channels for such cases (appdb, bugzilla, mailing lists, and the winehq irc channel). Most of the people there probably don't know anything about Sugared Wine, but collectively they should know more than I do about making Wine work in general. If a program doesn't work for you, you can go to any of those places for support. You can also email sugaredw...@codeweavers.com. That goes directly to me for now, but in the future (maybe the very near future) I may decide to send it somewhere public, like a mailing list, instead. Wine and the code that I developed for this project are licensed under the GNU LGPL. The entire package isn't quite LGPL because I included 7-zip. 7-zip is LGPL + unRAR restriction (you're not allowed to use the source code to create a RAR compressor). If you have a program that works well in this Wine package and would like to package it as a stand-alone .xo, please let me know. I already did most of the work for this so that I could include 7-zip and a firefox downloader/installer (and I could probably have included firefox itself if not for the fact that it would require uploading non-open-source code to repo.or.cz). Vincent Povirk
Re: Fedora Desktop on XO
Hi Chris, I would remove the old fc9 build from the olpc_development repo (or even have one for 8.2.0 and one for 9.1.0 so they don't get mixed up). Surely it should be pulling cyrus-sasl from the Fedora repos anyway? I've just pushed a patch to pilgrim's joyride branch to switch the baseurl that gets written out in /etc/yum.repos.d/olpc-development.repo from http://xs-dev.laptop.org/~cscott/repos/dist-olpc3-devel/ to http://kojipkgs.fedoraproject.org/static-repos/dist-olpc4-build-current/i386/ (olpc3 is our 8.2/F9 repo, and olpc4 is the 9.1/F10 repo, so Joyride should have been switched to write out the olpc4 baseurl when we created the new repo.) And, after the change, we don't have depsolving problems any more! Here's the list of packages to be downloaded -- the next question is going to be how to avoid many of these dependencies. Perhaps instead of trying the groupinstall, we should be hand-picking a smaller base of GNOME packages from this list? Well its the list up to the Installing for dependencies that is explicitly requested, all the below is pulled in for deps. I'm not sure how pilgrim builds the list but I think if it uses kickstart like the other fedora build systems do you should be able to do a specific -packagename and its removed from the list. A quick look through the list. if you remove tomboy you should loose all the mono deps, bluez-gnome and gnome-bluetooth should drop out all the bluetooth related stuff, nautilus-cd-burner and nautilus-sendto should drop various other non required deps (various CD burning stuff and pidgin etc), compiz* won't be required as I doubt the graphics adapter does cool whirly effects, How did you go with this? Did you have any luck? I also realised that if you drop gnome-user-share you'll drop all the httpd requirements. I was going through the list of stuff at http://wiki.laptop.org/go/Feature_roadmap/Run_Fedora_applications_on_XO and have a few comments on the points made. Some might be obvious, some not so much. * Must support camera, microphone, speakers, wifi 802.11 A/B/G, touchpad, Keyboard, USB interfaces, and SD interface. - being based on Fedora all of the above comes as standard. I presume with the wifi bit you mean support of the onboard wifi interface. * Does not need to make it easy to share files between Fedora and Sugar. - assuming its all running from the same base OS and just switching GUIs this should be OK except for stuff stored in the journal possibly. If its stored in the journal would it be possible to write a gio interface for the journal ? * Must fully support Yum. - This would come as standard. * Must come with applications on default install (will be chosen and will be a very minimal set). - this would be dependant on the choice of apps. we already have the base of quite a few installed from the gnome side of things (totem, abiword etc) in some cases its a matter of just adding the standard 'GUI' along with the sugar one. * Must boot as fast as Sugar. - in most cases its the other parts of the OS that take the time. Not sure how you'll switch between the two but in the case of a gnome gui it would be mostly the 'login time' difference. * Must support upgrading the Fedora version and the Sugar version in 9.2.0 and future releases. - Like yum support this would be automatic :-) * Must not keep two copies of any files or libraries. Any file which is exactly the same on both Sugar and Fedora images should be used by both and should not take twice the space. - The issue here would be forked libraries. The ones that come to mind specifically are abiword, totem, totem-pl-parser, telepathy and GConf2-dbus. In some cases where the gnome desktop requires evolution-data-server in other areas anyway there is suddenly very little need to keep the forked packages around. A gnome based desktop make some sense in the discussions as we already package so much of it already Cheers, Peter ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
