Fwd: OLPC upgrades
-- Forwarded message -- From: Tiago Marques Date: Sat, Feb 7, 2009 at 1:46 AM Subject: Re: OLPC upgrades To: da...@lang.hm 2009/2/3 > On Tue, 3 Feb 2009, Tiago Marques wrote: > > On Tue, Feb 3, 2009 at 8:38 AM, Bobby Powers >> wrote: >> >> 2009/2/2 Tiago Marques : >>> On Thu, Jan 29, 2009 at 4:03 AM, Mitch Bradley wrote: >>> >>> The current dual mode touchpad hardware is being discontinued and new >>> machines are either currently, or will be in short order, being >>> produced with a 'standard' capacitive touchpad. IN FACT, the stylus >>> mode had been implemented and enabled in the driver in previous builds >>> (joyride, up to the beginning or middle of summer 08), but was >>> disabled and removed from the driver because having the device in dual >>> input mode made things worse for a large number of laptops. The dual >>> mode hardware is pretty flakey. >>> >>> I believe view source is implemented to some extent in Sugar 0.83 (the >>> current development branch). >>> >> >> Hmm ok. Is it possible/easy to use the whole touchpad as pointing >> device, instead of just the middle. Since the middle has no "bump" that >> could give some feeling of where it ends, enabling all would make it more >> usable. At least I, frequently, need to look at it to understand if it's >> going bonkers on me, or if I'm just trying to use it out of the it's >> limit. >> I don't see a practical use for all that wideness but it would just to be >> less error prone. >> > > only the center section is a touchpad, the sides are the stylus-only areas. > the new systems are not going to have the 'wide pad', only the center > section. > Ok. Guess I'll have to glue something in mine, so I have some sort of feedback. > > Have any experience with the kernel or suspend/resume issues? I'm >>> sure CJB would love some help here. >>> >> >> Not really, I just hacked a driver once to add AGP and IDE DMA support for >> a >> VIA chipset, just added the hardware IDs. >> > > as I understand it, the biggest problem right now is that the power savings > stuff is all done in a Sugar specific way. I've used Sugar with full power > savings enabled (backlight off) for light-duty tasks (e-book functions) and > had it last an 8-hour day with half the battery remaining. I've also had it > last 2-3 hours with power savings off and the backlight running I have some problems with automatic power management, which I've reported in tracker. Your measurements seem encouraging, I must say. Have toy with this some more then. > > > non-Sugar distros currently can't do any power management, so they are > stuck with the short battery life. As this gets fixed and the power > capabilities get standardized this should improve. > > they should, and that leaves the XO in a competitively bad position. And that's what you should also talk about, nowadays everyone knows they're ripped off in their laptops, iPhone, PSP, whatever battery, that's part >>> of a >>> good image that the project can benefit from, if retail availability ever comes. Python is killing the XO, what's being done in that regard? The $100 >>> laptop >>> will always be hardware limited, how can python be a benefit and not a *huge* burden? I for one can't get my head around that. >>> >>> The idea is to give kids as much transparency into the software stack >>> as possible, AND make it easy to hack on and easy to create new >>> activities for. Python is much more forgiving than C. Its killing >>> the XO? A personal pygtk based project launches in a few seconds on >>> my debXO install on an XO, but much much longer on 8.2. It is a >>> completely loaded statement to say that Python is killing the XO, and >>> didn't really deserve a response :) >>> >> >> That's my view on it, although I don't have any experience in Python >> programming. Launch time doesn't really bother me, memory consumption on a >> device with no swap and 256MB of RAM does. Is it just Sugar/Fedora/XO >> distro >> specific? >> Please elaborate on what you mean by 8.2 taking much longer to launch. >> That >> would be something I would be interested in looking at, although I don't >> think I have what it takes to "fix" Pyhton itself, if that's what's >> needed. >> > > the fact that KDE and GNOME (both desktops that are considered pigs on > normal machines) make a XO laptop seem snappy by comparison to Sugar (as of > December) means that there is a significant problem with Sugar. when people > ask about how to fix things, the answers that keep coming back all appear to > be python related. so it's not FUD to say that the dependance on Python is > hurting performance. > > David Lang > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > > Best regards, Tiago Marques ___ Devel mailing list
New staging build 30
http://xs-dev.laptop.org/~cscott/xo-1/streams/staging/build30 Changes in build 30 from build: 27 Size delta: 0.00M -olpcrd 0.50-0 +olpcrd 0.51-0 --- Changes for olpcrd 0.51-0 from 0.50-0 --- + Fix multiple activation key support + Fix multiple activation key support -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/staging-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2648
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2648 Changes in build 2648 from build: 2647 Size delta: 0.00M -olpcrd 0.50-0 +olpcrd 0.51-0 --- Changes for olpcrd 0.51-0 from 0.50-0 --- + Fix multiple activation key support + Fix multiple activation key support -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/joyride-pkgs.html for aggregate logs See http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html for a comparison ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Devel Digest, Vol 36, Issue 12
Hi all, I already mentioned an Acer One boots very fast from flash, like 5-10s to X server with window manager loaded. I remembered that I can do a TAR.BZ2 of the whole root of the SSD and put it online somewhere, if anyone cares to have a look to see what they have done at Linpus to speed up the boot of this particular Fedora flavour. We could supposedly download it from here: http://www.linpus.com/products_1.php# But, at least for me, it's not quite working. I volunteer for that effort but would like to have some help from Wade, since I've mostly used Gentoo since I became a penguin, and I don't known much else. Gentoo uses a different init system from most distros, so I never did do much init system hacking out of Gentoo. When I did do it(OpenSUSE and Ubuntu, mostly writing init scripts and toying with the boot process), it was something I didn't want to do again, I love Gentoo's baselayout too much - it's simple to work with and supports parallel init script startup for at least three years. Take a look at: http://www.youtube.com/watch?v=Mg_HBgwRZS4 to get an idea of how fast it is. It boots the X and window manager and then starts loading network and ACPI stuff in parallel, it still takes a while for everything to be up but it's generally quite fast, especially if you just want to access local stuff. Best regards, Tiago Marques On Tue, Feb 3, 2009 at 5:13 PM, Mitch Bradley wrote: > > > Date: Tue, 3 Feb 2009 07:57:02 -0500 > > From: Wade Brainerd > > Subject: Re: OLPC upgrades > > To: "C. Scott Ananian" > > Cc: OLPC Devel > > Message-ID: <377b4440-aad7-412c-b22b-16158d6f4...@gmail.com> > > Content-Type: text/plain; charset=us-ascii; format=flowed; > delsp=yes > > > > A patch isn't really appropriate but generally speaking I: > > > > - Followed Mitch Bradley's instructions for tar-ing /dev. > > - Replaced the initrd with a 3 liner using busybox that just mounts > > NAND and calls switch_root. This involved undoing all the version > > stuff in the filesystem. > > - Replaced rc.sysinit with a 30 line script that starts the services I > > want and mounts the required points. > > - Removed the entire SYSV runlevel system. > > > > I was learning about all this stuff as I did it, but it still didn't > > take that long. And I have a lot of plans to make it even faster. > > > > A few things don't work right, like I'm still trying to figure out why > > there are no network interfaces...But If anyone would like to see the > > scripts I'd be happy to share them. > > > > How about bundling them up and attaching them to the "Improve Startup > Speed" ticket http://dev.laptop.org/ticket/4349 . That way all the > research that nobody does anything about because it diverges too much > from the blessed Fedora will all be in one place. > > > ___ > 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: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
2009/2/6 Mikus Grinbergs : > I see. Something which is a SUBSTANTIAL improvement (being able to > view .pdf files without fetching them to Journal and separately > launching Read) will be available only to deployments which > explicitly ask for it - and not to general 8.2.1 users. It's available to everyone, just not through the software update mechanism. Feel free to start a new thread if you think this should be proposed as an automatic 8.2 update - I don't have a strong argument against it. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] Notes from an impromptu 8.2.1 Release Mtg.
>> Why didn't Software update install the newer Browse (v.101 ?) that >> according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes >> addresses >> ticket #9112 Enable Browse to embed PDF files in itself > > Because it is a bit of a hack, aimed at deployments only. I don't > think it will be presented as an update until the feature is properly > implemented in sugar. Feel free to brush up the release notes. I see. Something which is a SUBSTANTIAL improvement (being able to view .pdf files without fetching them to Journal and separately launching Read) will be available only to deployments which explicitly ask for it - and not to general 8.2.1 users. mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: staging-27 issues
> BUG: Software update did not find the 8.2.1 specific Etoys activity release at > http://etoys.laptop.org/xo/8.2.1 What is the proper Etoys activity .xo to use with staging-27 ? Etoys-99.xo (the latest; goes with etoys 4.0-2205-2 in staging-27) ? or Etoys+MP3-94.xo (added function for a country deployment) ? or Etoys-94.xo (came with 8.2.0) ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2647
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2647 Changes in build 2647 from build: 2644 Size delta: 0.00M -jasper-libs 1.900.1-8.fc9 +jasper-libs 1.900.1-9.fc10 -poppler 0.8.7-1.fc10 +poppler 0.8.7-5.fc10 -poppler-glib 0.8.7-1.fc10 +poppler-glib 0.8.7-5.fc10 -xulrunner 1.9.0.5-1.fc10 +xulrunner 1.9.0.6-1.fc10 -xulrunner-python 1.9.0.5-1.fc10 +xulrunner-python 1.9.0.6-1.fc10 -- 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: Please update etoys in 8.2.1
2009/2/6 : > sorry if I seem like a pest, and I definantly do appriciate the volunteers > here, but what I am trying to understand here are the plans of the olpc > orginiztion itself. it's one thing to transition the maintinance of the > Sugar UI to an outside orginization, it's something very different to > switch from Sugar the distro (or whatever you want to call it if not > Sugar) to Fedora with the Sugar UI running in it. > > among other things, this would signal the end of the rainbow security > approach in favor of standard linux (or possibly SElinux) security. > > It would end the dual image 'hit a button to boot the last image' approach > as standard distros don't do that. and probably several other things. > > I'm not even saying it's the wrong thing to do. I'm just trying to > understand what the plan is. I can only speak as a volunteer too, but I can speak as one who intends to continue contributing to development, and I have participated in the discussions: The "plan" makes more sense when you look at it from a high level. OLPC used to have a fairly significant development team, and a QA group. It did a lot of development and testing. Now, there are only a couple of developers and no QA team. It's not practical to continue developing as happened before. Now, imagine if we could use someone elses software, e.g. Fedora, with no modifications (ignoring any loss of features, or let's say that no features are lost). Fedora have a release cycle, a QA team, a big community-based development group, etc. OLPC can continue shipping the same kind of thing on the machines, progressing at a similar or faster rate than previously, and it can do this with only a few staffers. This would be a perfect solution to the current problem. It sounds great, but there are challenges: OLPC has historically diverted from upstream and developed technologies in-house which have not really been pushed at or adopted by other communities. e.g. olpc-update, rollback boot, ... OLPC has also made some hacks to packages to better meet the goals of the organisation, at the expense of maintainability of the OS. This cannot continue in such a model where no modifications are made. So, the community (and couple of devs at OLPC) now needs to work on taking each of those hacks and features and integrating them into upstream-upstream (by that I mean the actual real upstream codebases, not just Fedora upstream) in a non-hacky way. Then the rest of the world has the technology too, and more significantly, the rest of the world maintains the technology (not OLPC). Yes, this is hard, and F11 may regress some features such as the ones you mention. But, by the very nature of the system, anything that is *properly* integrated for F11 will *automatically* be present in F12, F13, etc. So, given the large amount of community interest, I am confident we'll get there given time. Maybe not F11, but after. Let's also not forget that OLPC's target is deployments.. Some of the features have not seen much adoption. For example, rollback boot... At least in the deployment scenarios I have been involved in, NAND space is a commodity and we cannot afford having 2 OSs there (they want many activities, wikipediaEN/ES, gcompris, a few hundred mb of textbooks, etc). Although it would be a shame to lose such a feature, it is not something that I would see blocking adoption by the majority of deployments. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Notes from an impromptu 8.2.1 Release Mtg.
2009/2/6 S Page : > In Sugar control panel > Language, "Swedish (Sweden)" was highlighted! > Sure enough, in the bash shell, LANG is set to sv_SE.utf8. I'm pretty > sure I never chose that, and other settings like Date & Time were > unchanged. Has anyone else noticed Language changing? If you did olpc-update then you can hold a game key to boot back into your 8.2.0 build and see if things were the same there. (if so, it makes sense for that preference to have been copied) > Why didn't Software update install the newer Browse (v.101 ?) that > according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes > addresses > ticket #9112 Enable Browse to embed PDF files in itself Because it is a bit of a hack, aimed at deployments only. I don't think it will be presented as an update until the feature is properly implemented in sugar. Feel free to brush up the release notes. Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: My first newbie question
2009/2/6 Tom Wilson : > Hi there. I'm trying to get set up for Sugar development/debugging to see if > maybe I can contribute. I saw in the wiki that there are difficulties with > Mac OS X 10.5 - is that the case? I have VMWare Fusion, so I can set up on > virtual Fedora or Ubuntu (I take it Fedora is the preferred OS?). I'd rather > do it in my native OS, so I thought I'd check with the group before > proceeding. > > Okay, I'll go back to lurking now (at least until I'm in a position to > actually do something :) Hi Tom, do you want to hack on the Sugar shell or only in a new activity of you? If the former, I recommend that you go the sugar-jhbuild way. Both Fedora 10 and Ubuntu Intrepid are well supported, but other recent distros also should work with more or less tweaking. If the later, just install Fedora 10 and then install the sugar packages. You can run sugar in sugar-emulator and code and test there your activities. And you are most welcome to join us in sugar-devel and the irc channel #sugar in Freenode. http://lists.sugarlabs.org/listinfo/sugar-devel Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
My first newbie question
Hi there. I'm trying to get set up for Sugar development/debugging to see if maybe I can contribute. I saw in the wiki that there are difficulties with Mac OS X 10.5 - is that the case? I have VMWare Fusion, so I can set up on virtual Fedora or Ubuntu (I take it Fedora is the preferred OS?). I'd rather do it in my native OS, so I thought I'd check with the group before proceeding. Okay, I'll go back to lurking now (at least until I'm in a position to actually do something :) -tom ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: wiki.l.o down?
Wiki is back. A cabling error caused our upstream connection to automatically shut off the entire 1CC network, and we had to wait until someone with the appropriate magic powers was available to reset it. - Ed On Feb 6, 2009, at 6:49 AM, Bastien wrote: > Yes, still down. > > -- > Bastien > ___ > 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: Video Playback
Hi Carlos, > I can run the mplayer from the shell and it works like a charm. But in > order to get it working with kids, the shell isnt exactly a solution. > > I want to try some codecs for totem, coz ive seen some sites with totem > compatibility but i just need to expand the codecs. > I don't have experience with codecs, we just tuned and sugarized mplayer some time ago, i don't know how to expand codecs. :/ regards.- -- Eduardo Silva http://edsiper.linuxchile.cl ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, Feb 06, 2009 at 02:53:03AM -0800, da...@lang.hm wrote: > I'm glad to hear it's been going on, I would have expected such things > here on the OLPC developer list. are the folks working on other distros > (debxo, ubuntu, gentoo that I know of) aware of the work happening on the > fedora-olpc list? debxo. No. Thanks for the heads-up. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: wiki.l.o down?
Yes, still down. -- Bastien ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 Thoughts
On Thu, Feb 05, 2009 at 07:03:08PM -0500, Chris Ball wrote: > The first useful test is "does the 767 version of the wireless driver > work with WPA with the new firmware", since that'll suggest to us > whether we have a bad driver or bad firmware. I've taken a unit with staging-26 and another with 767, and swapped the firmware files, then rebooted. I went through several cycles of connecting, suspending, resuming, rebooting. af642c0558e716e3cb4b3d449a938cd8 usb8388.bin.build-767 5e38f55719df3d0c58dd3bd02575a09c usb8388.bin.staging-26 The unit with staging-26 kernel and the build-767 wireless firmware did not change behaviour much. It still prompted for "Wireless Key Required" on boot, or on resume from suspend. But sometimes it would connect using the stored key if this dialog was dismissed and the connection retried. The unit with build-767 kernel and the staging-26 wireless firmware changed behaviour to become almost the same behaviour as a staging-26 system. It would only connect after reboot or suspend if the Discard network history button was used. Conclusion: symptom follows kernel *and* firmware? -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Life after 8.2.1 (was Re: Please update etoys in 8.2.1)
On Fri, Feb 6, 2009 at 4:15 PM, Bert Freudenberg wrote: > (changing subject ...) > > It would seem to me that deployments will get to choose which software > to install. > [like] Luke's XOOS (http://lukego.livejournal.com/tag/xoos) is immature but > cool Hah! Yes that would be cool indeed! Letting the children build up their own software stack, with their own, home grown, favourite programming paradigms in a fully interactive environment all the way down to the bottom. What's not to like about this approach! And it would be a great learning experience ;o) /Ties ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Life after 8.2.1 (was Re: Please update etoys in 8.2.1)
(changing subject ...) On 06.02.2009, at 11:13, da...@lang.hm wrote: > On Fri, 6 Feb 2009, Michael Stone wrote: > >>> so after the 8.2.1 release the plan is to just switch to standard >>> Linux >>> distros? >> >> Speaking entirely as a volunteer: the answer depends on who you ask. > > sorry if I seem like a pest, and I definantly do appriciate the > volunteers > here, but what I am trying to understand here are the plans of the > olpc > orginiztion itself. it's one thing to transition the maintinance of > the > Sugar UI to an outside orginization, it's something very different to > switch from Sugar the distro (or whatever you want to call it if not > Sugar) to Fedora with the Sugar UI running in it. > > among other things, this would signal the end of the rainbow security > approach in favor of standard linux (or possibly SElinux) security. > > It would end the dual image 'hit a button to boot the last image' > approach > as standard distros don't do that. and probably several other things. > > I'm not even saying it's the wrong thing to do. I'm just trying to > understand what the plan is. > > In many ways, switching the XO laptop from using one special distro to > being able to select which of several different distros you want > pre-loaded on the machine would be a very good thing. but it is a very > significant step. It would seem to me that deployments will get to choose which software to install. Competition for that is starting, with various contenders, like OLPC's 8.2.x series, Debian's DebXO, Fedora's v. 12, SugarLabs' Sugar-on-a-Stick, olpcfriends' community distro (championed by mstone), some Redmond company is working on an OS, Luke's XOOS (http://lukego.livejournal.com/tag/xoos ) is immature but cool, etc. The various Linux-based approaches seem to be the most promising, in particular since they can share improvements easily. OTOH those who do not want to get dragged into distro politics might join Michael, and produce the best-adapted OS for the XO hardware? I personally like that, but we'll see I guess. And in the end, maybe not being officially endorsed by OLPC is even a virtue? - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 8.2.1 wireless testing results #2
Comparing staging-26 against 8.2-767, using a NetComm NB600W (purchased 2007-12-13) configured for either open or WPA TKIP. Open works fine. Connection is automatically reestablished on reboot. WPA(TKIP): 8.2.0 reconnects on boot, staging-26 always fails to reconnect on boot, bringing up the password request dialog, repeatedly. On the fourth or fifth dialog retry, the icon for the access point disappears from view and reappears a minute or two later. When that happens, clicking on it successfully connects. Workaround: after a reboot, cancelling the password request dialog, then using the Control Panel, Network, Discard network history, allows immediate connection. Also, resuming from suspend on 8.2.0 requires connecting again, but there is no password prompt. Resuming on staging-26 produces the password prompt, and generates the same symptom as rebooting ... repeated prompts solved by Discard. Conclusion: the regressions reported by Daniel Drake are reproduced. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, 6 Feb 2009, Martin Langhoff wrote: > On Fri, Feb 6, 2009 at 11:16 PM, wrote: >> the first step is to track down the remaining XO only things > > that's what the 'fedora-olpc' mailing list has been all about for a while now. grumble grumble fedora centric US developers ;-) I'm glad to hear it's been going on, I would have expected such things here on the OLPC developer list. are the folks working on other distros (debxo, ubuntu, gentoo that I know of) aware of the work happening on the fedora-olpc list? David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
staging-27 issues (was Re: Notes from an impromptu 8.2.1 Release Mtg.)
On 06.02.2009, at 05:40, S Page wrote: > I updated from 8.2.0 build 767 to staging-27 with > `sudo -v -v -v olpc-update staging-27` > > and it all went very smoothly! Same here. > * Software update offered no new activities (I had ran it the day > before > on build 767). It had some for me, and even after updating there were two more bundles to be installed. I could not yet test again today since the wiki is down. BUG: It did not find the 8.2.1 specific Etoys activity release at http://etoys.laptop.org/xo/8.2.1 Possibly because /etc/olpc-release still says "8.2"? (not a severe issue for etoys since only minor changes happened in the activity vs. the rpm) > Build '27' is confusing, especially when "About my XO" doesn't show > your > release or stream (Trac 8260). I updated the "What release am I > running?" wiki page to mention this stream. > > In Sugar control panel > Language, "Swedish (Sweden)" was highlighted! > Sure enough, in the bash shell, LANG is set to sv_SE.utf8. I'm pretty > sure I never chose that, and other settings like Date & Time were > unchanged. Has anyone else noticed Language changing? Mine remained set to German as before the update. > Why didn't Software update install the newer Browse (v.101 ?) that > according to http://wiki.laptop.org/go/Release_notes/8.2.1#Bug_fixes > addresses > ticket #9112 Enable Browse to embed PDF files in itself > > > A few minor things > -- > I see a [Discard network history] button in the Network panel, I > didn't > notice this before but I think it was in 8.2.0. The 8.2.0 manual > http://www.laptop.org/8.2.0/manual/XO_Troubleshooting.html should > mention this. > > In the Home view ring view, when I hide the frame (by moving away > from a > corner or pressing the Frame key), the very edge of the frame flickers > white a few times. I didn't notice this before. > > Please please create Trac version "Build 767 (8.2.0)" (Trac bug 8904). > > Cheers, > -- > =S Page Overall in my brief testing so far I did not see issues, in particular the updated etoys packages appear to work as fine as usual ;) - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, Feb 6, 2009 at 11:16 PM, wrote: > the first step is to track down the remaining XO only things that's what the 'fedora-olpc' mailing list has been all about for a while now. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
wiki.l.o down?
- Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Fwd: Another Soas image for the XO
-- Forwarded message -- From: Marco Pesenti Gritti Date: Fri, Feb 6, 2009 at 10:29 AM Subject: Another Soas image for the XO To: Sugar-dev Devel Cc: Sebastian Dziallas , Gary C Martin Now with readable fonts :) http://download.sugarlabs.org/soas/xoimages/soas3.crc http://download.sugarlabs.org/soas/xoimages/soas3.img Next challenge will be to trim the size down. I think Sebastian has been working on that. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, 6 Feb 2009, Martin Langhoff wrote: > On Fri, Feb 6, 2009 at 6:02 PM, wrote: >> so after the 8.2.1 release the plan is to just switch to standard Linux >> distros? > > What follows is my understanding of what Ed and cjb mean when they > talk about future releases... > > Instead of a "9.1" done in the old way, staff and volunteers set their > eyes on Fedora 11, and ... > > - help ensure there is testing and polish of F-11 on the XO hw > - help ensure there is testing and polish on the packages we care > about (Sugar!) > - build images (and help others build images) based on a F-11 spin > - post-release fixes and polish are channeled via the Fedora updates stream > > it's very likely that the process will need some tiny bits of rigging > that don't belong to Fedora. Something similar happens with the XS. > Creating the 'olpc' user, setting gdm to boot straight into Sugar, > building the image in jffs2 or ubifs -- such steps of configuration > can be done in the %post script of a livecd or pungi kickstart. the first step is to track down the remaining XO only things (power management is the big one I can think of at the moment), and flush the remaining patches that are in the build for hardware functionality (there was a short thread right after the downsizing was announced where I asked some questions about this, but the people who had the answers were busy looking for other jobs) David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, 6 Feb 2009, Michael Stone wrote: >> so after the 8.2.1 release the plan is to just switch to standard Linux >> distros? > > Speaking entirely as a volunteer: the answer depends on who you ask. sorry if I seem like a pest, and I definantly do appriciate the volunteers here, but what I am trying to understand here are the plans of the olpc orginiztion itself. it's one thing to transition the maintinance of the Sugar UI to an outside orginization, it's something very different to switch from Sugar the distro (or whatever you want to call it if not Sugar) to Fedora with the Sugar UI running in it. among other things, this would signal the end of the rainbow security approach in favor of standard linux (or possibly SElinux) security. It would end the dual image 'hit a button to boot the last image' approach as standard distros don't do that. and probably several other things. I'm not even saying it's the wrong thing to do. I'm just trying to understand what the plan is. In many ways, switching the XO laptop from using one special distro to being able to select which of several different distros you want pre-loaded on the machine would be a very good thing. but it is a very significant step. David Lang > Since I think that 8.2.0 wasn't half bad, I'm currently trying to persuade > people who feel similarly to work with me to assemble an 8.2.2 with some > useful > bugfixes and software updates, because I think that > > a) it's the right thing to do > > b) it will complement various upstream efforts (both in Fedora, Sugar Labs, > and the wider FOSS community at large) by helping to concentrate > deployment-specific testing effort on the most relevant parts of > their work > c) that it's important to deliver a product which directly meets the needs > of > existing deployments even when those needs don't precisely match the > needs > and goals of the larger upstream communities. > > Does this help clarify the situation? > > Michael > > P.S. - My current ideal list of changes would include: > > * fix the memory stability issue > * ship the new gabble w/ support for out-of-band stream tubes > * ship the latest gnash > > and I'd be very happy to discuss shipping various sugar or platform updates > as > well; e.g. java. > > What do you want to see in a new release? > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
I would like to see a java update. On Fri, Feb 6, 2009 at 3:25 AM, Michael Stone wrote: >>so after the 8.2.1 release the plan is to just switch to standard Linux >>distros? > > Speaking entirely as a volunteer: the answer depends on who you ask. > > Since I think that 8.2.0 wasn't half bad, I'm currently trying to persuade > people who feel similarly to work with me to assemble an 8.2.2 with some > useful > bugfixes and software updates, because I think that > > a) it's the right thing to do > > b) it will complement various upstream efforts (both in Fedora, Sugar Labs, > and the wider FOSS community at large) by helping to concentrate > deployment-specific testing effort on the most relevant parts of > their work > > c) that it's important to deliver a product which directly meets the needs > of > existing deployments even when those needs don't precisely match the > needs > and goals of the larger upstream communities. > > Does this help clarify the situation? > > Michael > > P.S. - My current ideal list of changes would include: > > * fix the memory stability issue > * ship the new gabble w/ support for out-of-band stream tubes > * ship the latest gnash > > and I'd be very happy to discuss shipping various sugar or platform updates as > well; e.g. java. > > What do you want to see in a new release? > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
On Fri, Feb 6, 2009 at 6:02 PM, wrote: > so after the 8.2.1 release the plan is to just switch to standard Linux > distros? What follows is my understanding of what Ed and cjb mean when they talk about future releases... Instead of a "9.1" done in the old way, staff and volunteers set their eyes on Fedora 11, and ... - help ensure there is testing and polish of F-11 on the XO hw - help ensure there is testing and polish on the packages we care about (Sugar!) - build images (and help others build images) based on a F-11 spin - post-release fixes and polish are channeled via the Fedora updates stream it's very likely that the process will need some tiny bits of rigging that don't belong to Fedora. Something similar happens with the XS. Creating the 'olpc' user, setting gdm to boot straight into Sugar, building the image in jffs2 or ubifs -- such steps of configuration can be done in the %post script of a livecd or pungi kickstart. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Please update etoys in 8.2.1
>so after the 8.2.1 release the plan is to just switch to standard Linux >distros? Speaking entirely as a volunteer: the answer depends on who you ask. Since I think that 8.2.0 wasn't half bad, I'm currently trying to persuade people who feel similarly to work with me to assemble an 8.2.2 with some useful bugfixes and software updates, because I think that a) it's the right thing to do b) it will complement various upstream efforts (both in Fedora, Sugar Labs, and the wider FOSS community at large) by helping to concentrate deployment-specific testing effort on the most relevant parts of their work c) that it's important to deliver a product which directly meets the needs of existing deployments even when those needs don't precisely match the needs and goals of the larger upstream communities. Does this help clarify the situation? Michael P.S. - My current ideal list of changes would include: * fix the memory stability issue * ship the new gabble w/ support for out-of-band stream tubes * ship the latest gnash and I'd be very happy to discuss shipping various sugar or platform updates as well; e.g. java. What do you want to see in a new release? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Joyide on Fedora 11/rawhide
I wrote: > I've ported the patch to upstart's bzr trunk (it applies cleanly to > 0.5.0), and scratch-built some rpms: > https://koji.fedoraproject.org/koji/taskinfo?taskID=1106475 > > The patch is here, along with the srpm and spec file: > http://dev.laptop.org/~bobbyp/upstart/ > > Of note, I had to add dbus-devel to BuildRequries, as upstart seems > now to need it. I haven't had a chance to test the rpms, hopefully > tomorrow. so I've tested and updated the RPMs, spec file and patch, which are available at: http://dev.laptop.org/~bobbyp/upstart/ They don't work! First thing to notice is that I cut down the olpc-init patch a lot. The third section of the original patch was for a file that doesn't exist (and wasn't renamed as far as I can tell, I've greped a fair amount for its content). So I originally had left the first part in, but the image created with it gave the following error when init was first called: init: Unhandled Error: Address already in use Now, with just the pid snarfing part in main.c, Upstart seems to hang without giving any messages. None of the other Fedora patches have been applied (it seems as if the devel branch of upstart in Fedora CVS is a work in progress, to say the least), so unless anyone here has insight, getting them to apply seems like the next logical step. I can make my non-booting rawhide image available if anyone is interested. What I did was to run 'sudo make' on the puritan rawhide branch, wait for it to finish, chroot into $(CHROOT)/versions/pristine/767 and run 'rpm -Uvh http://dev.laptop.org/~bobbyp/upstart/upstart-0.5.0-1.fc11.i386.rpm', delete r/wrap*, then rerun 'sudo make'. Someone with more knowledge of sockets, upstart and Fedora's patches to it, and the init process might have better luck or be able to help me out :) If we can figure this out, I would be glad to help get as much of this as possible upstreamed (as well as into the F11 upstart package). yours, Bobby (I'll be out of town till Tuesday, so I probably won't be able to work on this again 'till then) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
