Re: Font problems (affecting Java and others?)
Alan, Thanks very much for the detailed writeup of your findings (and for your efforts make OLPC's software distribution more friendly to people who like Java). I can't personally resolve any of the questions which you raise with any authority but I can direct you toward the people who might be able to -- those people tend to live in #fedora-devel and on [EMAIL PROTECTED] might. (In particular, you'll find the Fedora OpenJDK packagers among them.) Regards, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] Notes on replacing bridging with bonding
Read http://www.linuxfoundation.org/en/Net:Bonding in depth - excellent docs! - and performed some tests on one of my XS sample machines, replacing br0 with bond0. It works and I will attempt the switchover. We'll need quite a bit of testing to feel confident with this though... This is roughly what I am doing: # mark the device as a bonding device # - for some reason TYPE does not work # cat /etc/modprobe.d/xs-bonding alias bond0 bonding # cat ifcfg-msh0 DEVICE=msh0 TYPE=Ethernet MASTER=bond0 SLAVE=yes # Will be brought up by wlanX ONBOOT=no IPV6INIT=no HOTPLUG=yes NM_CONTROLLED=no LINKDELAY=0 # this replaces the bridge - all the bonding opts # I can see are for actually bonded devices - any # useful options we should use...? # cat ifcfg-bond0 DEVICE=bond0 BOOTPROTO=static # BONDING_OPTS= IPADDR=$XS_BR0_IPADDR NETMASK=255.255.254.0 NETWORK=$XS_BR0_NETWORK BROADCAST=$XS_BR0_BROADCAST IPV6INIT=no ONBOOT=yes cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Help activity content
Hello, the deadline for the Help activity content was yesterday. http://dev.laptop.org/ticket/7526#comment:9 Is it available? If not, what should we do? Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
RE: Terminal Text Fragment Drop Support Patch
- original message - From: Cortland Setlow [EMAIL PROTECTED] I am looking for suggestions on how to upload patches from Sugar. I use copy-to-journal (olpc-support-scripts) on the git-format-patch/diff output to get things in the journal. I wonder how hard it'd be to teach Web/Browse to try the journal entry title as the filename, rather than the datastore ID. A way for people to share Sugar patches would be great (and has been mentioned before). Perhaps an add-on to Pippy...but only a few applications can escalate privileges to write to /usr...perhaps...OTTOMH...1) an activity to browse sugar code, edit it, store diffs in Journal; 2) a control panel patch-applier... Martin ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Short circuting USB port?
G'day Timothy, Thanks for getting back to me. Pardon me for being fascinated, but it's one of my pet topics. The key to understanding this symptom might be the low voltage cutoff. which is independent of the capacity indicator. The red battery light is based on a calculation. The calculation has several sources of error, it is not perfect, and cannot be. It's only pretty good. ;-) But the low voltage cutoff is quite definite. It happens if the voltage drops below a certain point. This can happen when the battery voltage falls due to heavy load, if the battery connection falters, or if the battery is removed. Based on your new data, that AC was not plugged in when the symptom happened, and you haven't been able to reproduce it, I think it is very likely that the symptom was the low voltage cutoff triggering. Had you said AC was plugged in, I could almost certainly exclude the low voltage cutoff. That leaves the question ... why didn't the laptop tell you that the battery was approaching that cutoff? The battery state of charge recorded in the battery management chip is not consistent with the actual state of charge. My guess as to the causes: 1. a battery that is faulty, 2. a charge and discharge cycle that was unusual, 3. a USB device that is faulty, in that it draws more current than it ought to do, 4. dirt on the battery connector, or loose contacts due to lots of removal and insertion of the battery in the laptop, 5. not locking the battery fully into the laptop, 6. battery management firmware that is faulty (we had some early software faults ... but I don't know which faults might be in the version you have) The support team has a battery charge monitoring script, if I recall correctly. -- James Cameronmailto:[EMAIL PROTECTED] http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Short circuting USB port?
First off, thank you for the fast reply. I did a backup today, and I could not reproduce the problem either with AC or on a full charge battery. I don't believe that my AC was plugged in when this problem occurred last night. I had been working outside for 3 hours outside before I ran into this issue(though the red battery light was not on) so that would match with your hypothesis. I don't know what else to add this doesn't seem like a critical or easily fixable issue so thank you for your help. Timothy On Sun, Sep 7, 2008 at 5:55 PM, James Cameron [EMAIL PROTECTED] wrote: G'day Timothy, The symptoms you describe are also consistent with battery voltage falling below the critical threshold as a result of the powering up of the host-powered hub, keyboard and mouse. But only if there was no AC adaptor connected. Was there one connected at the time? -- James Cameronmailto:[EMAIL PROTECTED] http://quozl.netrek.org/ -- - Tim [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Font problems (affecting Java and others?)
Michael Stone wrote: Alan, Thanks very much for the detailed writeup of your findings (and for your efforts make OLPC's software distribution more friendly to people who like Java). I can't personally resolve any of the questions which you raise with any authority but I can direct you toward the people who might be able to -- those people tend to live in #fedora-devel and on [EMAIL PROTECTED] might. (In particular, you'll find the Fedora OpenJDK packagers among them.) Thanks for the suggestions. So is all RPM packaging done by the Red Hat team? Do we have any control about what shows up in those repositories? That is, if we have a patch specific to the OLPC, are we dependent on Red Hat to approve/reject it and get it incorporated? I'll also pose a few related questions that pertain to OLPC philosophy, and not Red Hat philosophy: 1.) Is the OLPC expected to contain at least one font containing a glyph for all Unicode characters? Right now, I'm not sure we even have one complete font, even if we pick and choose between fonts. This affects many Activities; I tried to show people one of my web pages (using the Browse activity) that tests your recognition of Chinese numbers, and none of the glyphs for the Chinese characters appeared, indicating that we have font problems even in the Browse utility. See http://futureboy.us/fsp/chinesenumbers.fsp and http://futureboy.us/fsp/ChineseWorksheetGenerator.fsp And I know Firefox tries *hard* to find fonts with glyphs for each character it displays, and succeeds well on most operating systems. It would seem that a world-friendly OS should contain at least one font with glyphs for the majority of Unicode codepoints, or at least a bunch of fonts that can be searched for a glyph. This affects language learning and makes or breaks applications. 2.) If internationalized applications like Java or GTK or Browse have pointers to font files that are missing, is it considered an OLPC bug that we forgot to distribute those files? Or considered a bug in that Java distribution that needs to point at the fonts we already have? What if they're incomplete? Or is it a space-saving consideration? Or a free font availability consideration? If it's one of the latter, do we declare that we won't fully internationalize so platforms like Java and internationalized applications (like Browse) will be forever broken? 3.) Should it be considered a bug if an existing, central application like Browse or Firefox can't find a glyph for many Unicode codepoints, and thus fails to display many languages? Or do we just ship the fonts most used in our customer countries? (The latter seems a bit cynical... :) ) By the way, I've made a major rewrite to the Java page of the Wiki, hoping to bring it up to date, and provide links to Java-blocking bugs, Java issues, benefits of Java, and my own research into improving Java footprint and usability. Updates or discussion are highly welcomed. See http://wiki.laptop.org/go/Java -- Alan Eliasen | Furious activity is no substitute [EMAIL PROTECTED]|for understanding. http://futureboy.us/ | --H.H. Williams -- Alan Eliasen | Furious activity is no substitute [EMAIL PROTECTED]|for understanding. http://futureboy.us/ | --H.H. Williams ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Terminal Text Fragment Drop Support Patch
2008/9/8 Cortland Setlow [EMAIL PROTECTED]: Hi, Terminal really should support dropping dev key commands, I think. Here's a patch to make it do so. Could we update the devkey page to explain frame-based cut and paste? The current devkey hassles should be resolved in 9.1, when we will add a Security module to the control panel, including a section for dev keys. This new interface will explain what a key is, offer a 'Request key button, indicate progress, and automatically handle the installation of the new key when complete. This patch still sounds useful in general, though...every activity should support drag'n'drop copy and paste from the clipboard. Does yours do both directions? - Eben Also, I am looking for suggestions on how to upload patches from Sugar. To upload this one I created a Write document, quit Write, and used vi to edit the newly-created datastore object. Then the Web file picker could choose it. -- The world is quiet here. ___ 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: 8.2-759 Running 'Software update' to upgrade from Measure 17 to Measure 19 restarts sugar.
On 7 Sep 2008, at 07:07, [EMAIL PROTECTED] wrote: Running Software update indicates that there is an update from Measure 17 to Measure 19. When I click Install selected Sugar restarts. Then when I try Software update again and attempt to install Measure 19 it just refreshes but never successfully does the install. I can loop over and over clicking Install selected in this secenario. Yea was annoying me too, especially as v17 does not work on current dev builds... Anyway after a little poking I: a) Noticed that the Measure wiki page is full of HUGE images shown a teeny tiny thumbnails, so huge and numerous are they that it will bomb out Browse if you try to visit with an XO (machine locks up for ~5min and then something finally explodes causing an X reboot). b) Noticed that Measure-19.xo is available, but was actually pointing to Measure-17.xo from the wiki.laptop.org/go/Activities main page. Having corrected the wiki links for b) the auto updater now correctly installs v19 :-) And even better than that Measure-v19 is now working again on dev builds :-D Still thinking about fixing the Measure wiki images a) now, but just wanted to point out the issue as I've seen a bunch of other wiki pages that have huge images pretending to be little thumbnails, the XO's and their small memory footprints are not happy with such things - actually the page renders pretty roughly on a 1.5Ghz with 2Gb Ram so I'm not surprised the XO has trouble. Hmmm... I wonder if Browse should add back a very old school idea with a button to disable image downloading, would at least allow an overly image rich wiki page to be corrected by an XO only user, and might help in bandwidth restrictive deployment scenarios. --Gary ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: AC not present?
I know I've said this before, but I really want to get some UI polish into this part of the system. Instead of the cryptic AC not present we should be displaying a fullscreen graphic picturing the power cord (in the style of the shutdown warnings) to make it blatantly obvious what's needed. There are certainly other cases outside the sugar environment which probably need similar treatment. - Eben PS. I know this is low priority, but I don't want it to be forgotten. Perhaps if we can elaborate on the pieces which could use some UI polish early on in the release cycle we can actually make some improvements for 9.1. On Mon, Sep 1, 2008 at 6:47 PM, Bastien [EMAIL PROTECTED] wrote: Martin Langhoff [EMAIL PROTECTED] writes: n Tue, Sep 2, 2008 at 10:41 AM, Bastien [EMAIL PROTECTED] wrote: | AC not present Plug it to power to complete the firmware upgrade step... AArghh! Thanks. For me AC/DC has never meant anything else than classical music. -- 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: AC not present?
Well, even spelling it external power required is better than the cryptic AC not present. - Bert - Am 08.09.2008 um 17:25 schrieb Eben Eliason: I know I've said this before, but I really want to get some UI polish into this part of the system. Instead of the cryptic AC not present we should be displaying a fullscreen graphic picturing the power cord (in the style of the shutdown warnings) to make it blatantly obvious what's needed. There are certainly other cases outside the sugar environment which probably need similar treatment. - Eben PS. I know this is low priority, but I don't want it to be forgotten. Perhaps if we can elaborate on the pieces which could use some UI polish early on in the release cycle we can actually make some improvements for 9.1. On Mon, Sep 1, 2008 at 6:47 PM, Bastien [EMAIL PROTECTED] wrote: Martin Langhoff [EMAIL PROTECTED] writes: n Tue, Sep 2, 2008 at 10:41 AM, Bastien [EMAIL PROTECTED] wrote: | AC not present Plug it to power to complete the firmware upgrade step... AArghh! Thanks. For me AC/DC has never meant anything else than classical music. -- 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: AC not present?
Bert Freudenberg [EMAIL PROTECTED] writes: Well, even spelling it external power required is better than the cryptic AC not present. +1 -- Bastien ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Short circuting USB port?
James Cameron wrote: 1. a battery that is faulty, Very likely. See: http://wiki.laptop.org/go/XO_LiFePO4_Recovery_Procedure For diagnostic and repair. 3. a USB device that is faulty, in that it draws more current than it ought to do, The ports are limited to a max of 1A summed across all ports. I've tested this repeatedly. I often put a 5 ohm load on the usb power lines to discharge batteries faster. A sudden 1A draw would cause a bit of a dip on the battery voltage so if the battery is already really low this might be the cause. The support team has a battery charge monitoring script, if I recall correctly. 'olpc-pwr-log' Its in all new builds See here: http://wiki.laptop.org/go/LX_Power_Measurements#olpc-pwr-log -- Richard Smith [EMAIL PROTECTED] One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Font problems (affecting Java and others?)
Thanks for the suggestions. So is all RPM packaging done by the Red Hat team? OLPC and some of its friends help maintain several packages important to OLPC in Fedora. RedHat employees assist other Fedora volunteers in the same task. (Understand that Fedora and RedHat are related but distinct; think of Fedora as the community-owned distro from which RedHat pulls packages it likes.) Do we have any control about what shows up in those repositories? Yes. A moderate number of packages have OLPC-specific forks inside the Fedora build system and a smaller number have OLPC-specific forks outside of that build-system. That is, if we have a patch specific to the OLPC, are we dependent on Red Hat to approve/reject it and get it incorporated? Ultimately no, though in practice, we negotiate constantly with other Fedora maintainers because forks are expensive to maintain. 1.) Is the OLPC expected to contain at least one font containing a glyph for all Unicode characters? Right now, I'm not sure we even have one complete font, even if we pick and choose between fonts. Fonts (and other localization data) can be very big and we are very pressed for space. We would rather improve our customization technology to encompass fonts so that individual deployments can more easily choose the fonts which are appropriate for them. It would seem that a world-friendly OS should contain at least one font with glyphs for the majority of Unicode codepoints, or at least a bunch of fonts that can be searched for a glyph. This affects language learning and makes or breaks applications. Given network access, can such fonts be pulled on-demand based on need? 2.) If internationalized applications like Java or GTK or Browse have pointers to font files that are missing, is it considered an OLPC bug that we forgot to distribute those files? Or considered a bug in that Java distribution that needs to point at the fonts we already have? No policy exists. Can you suggest some of the pro's and con's you see in each approach? What if they're incomplete? Or is it a space-saving consideration? Or a free font availability consideration? All of the above plus inconsistent testing. If it's one of the latter, do we declare that we won't fully internationalize so platforms like Java and internationalized applications (like Browse) will be forever broken? No, we declare that we need help from the outside world in order to qualify a release X for locale Y, we hit up friends we know who care about locale Y, we seek out new friends, and, if necessary, we negotiate the qualification of a release for locale Y individually as a part of appropriate deployment contracts. By qualify release X for locale Y, I mean the stuff described at http://wiki.laptop.org/go/User:Mstone/Notes/Localization_1 Please help me extend that list if I've missed anything. 3.) Should it be considered a bug if an existing, central application like Browse or Firefox can't find a glyph for many Unicode codepoints, and thus fails to display many languages? Certainly, though it may not be a very high priority one for _OLPC_ to fix. (Our software is free; other people are welcome and encouraged to fix bugs which matter to them regardless of OLPC's priorities.) Or do we just ship the fonts most used in our customer countries? (The latter seems a bit cynical... :) ) We have a scarce physical resource -- NAND flash -- to try to economize. Consequently, we try to ship something like the things we consider to necessary to implement our educational vision plus a few other things to help meet other demonstrated deployment needs. As I suggested before, better customization technology would be welcome. By the way, I've made a major rewrite to the Java page of the Wiki, hoping to bring it up to date, and provide links to Java-blocking bugs, Java issues, benefits of Java, and my own research into improving Java footprint and usability. Updates or discussion are highly welcomed. See http://wiki.laptop.org/go/Java Thanks! Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Notes on replacing bridging with bonding
Jerry Vonau wrote: Jerry Vonau wrote: Martin Langhoff wrote: On Mon, Sep 8, 2008 at 7:43 PM, Alexander Dupuy [EMAIL PROTECTED] wrote: I have placed TYPE=Bonding in the ifcfg-bond0 config files, but this is not needed for Fedora 7 or later (it doesn't hurt to have it, though) well, I grepped network-functions and ifup-eth and none of the TYPE checks are for bonding anything. The check is done against the output of modprobe. So if it's going to be ignored, I'll save the corresponding bytes (and potential confusion later). ifup does a check for type=Bridge Bonding can be handled via VLAN=yes and PHYDEV=msh0 in the ifcfg files for the bond device, ifup uses those values to setup the bonding in a hotplug environment. The slave (msh0) should have SLAVE=yes MASTER=bond0 in its file. Hotplug works also, bond0 doesn't need to have its slave present to become active, plug the slave in, becomes active and bonding does the right thing. Bye, bye dummy interface. # cat /etc/modprobe.d/xs-bonding alias bond0 bonding A modprobe.d/ directory - that's a nice trick! I wasn't aware of this, so just added some lines to the /etc/modprobe.conf file: that's what the most modern doco could find suggested. And the ifup-eth src is clearly looking at the output of modprobe, so there's something to it... well, udev loads the modules on boot, for configured devices. network checks to see if the required module for the nic is loaded, if missing loads it. Think we can just dump a file in /etc/modprobe.d/ with the bonding options needed. I've been using bonding mode=active-backup miimon=100 to test with, any idea what we may be using here? Better yet just add BONDING_OPTS= it the ifcfg file. Since the docs are hard to find without the kernel source rpm, here are all the docs from a kernel 2.6.25 source rpm for networking. See bonding.txt http://members.shaw.ca/jvonau/pub/network Jerry ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: AC not present?
Bert Freudenberg wrote: Well, even spelling it external power required is better than the cryptic AC not present. The message was changed to No external power in release Q2D14 . - Bert - Am 08.09.2008 um 17:25 schrieb Eben Eliason: I know I've said this before, but I really want to get some UI polish into this part of the system. Instead of the cryptic AC not present we should be displaying a fullscreen graphic picturing the power cord (in the style of the shutdown warnings) to make it blatantly obvious what's needed. There are certainly other cases outside the sugar environment which probably need similar treatment. - Eben PS. I know this is low priority, but I don't want it to be forgotten. Perhaps if we can elaborate on the pieces which could use some UI polish early on in the release cycle we can actually make some improvements for 9.1. On Mon, Sep 1, 2008 at 6:47 PM, Bastien [EMAIL PROTECTED] wrote: Martin Langhoff [EMAIL PROTECTED] writes: n Tue, Sep 2, 2008 at 10:41 AM, Bastien [EMAIL PROTECTED] wrote: | AC not present Plug it to power to complete the firmware upgrade step... AArghh! Thanks. For me AC/DC has never meant anything else than classical music. -- 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Terminal Text Fragment Drop Support Patch
The current devkey hassles should be resolved in 9.1, when we will add a Security module to the control panel, including a section for dev keys. This new interface will explain what a key is, offer a 'Request key button, indicate progress, and automatically handle the installation of the new key when complete. In your concentration on the control panel, PLEASE keep in mind customers with non-standard connectivity. I myself am unable to use the control panel 'update' facility from home -- because my internet connection at home is through a proxy, and I have no way to tell the control panel session to use a proxy to route its server requests. [I *can* use the CLI control panel commands from Terminal - since my Terminal session *is* (manually) set up to use my proxy.] mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: AC not present?
Eben Eliason wrote: I know I've said this before, but I really want to get some UI polish into this part of the system. Instead of the cryptic AC not present we should be displaying a fullscreen graphic picturing the power cord (in the style of the shutdown warnings) to make it blatantly obvious what's needed. I find it amusing that the shutdown warnings are mentioned in the same sentence as blatantly obvious. There are certainly other cases outside the sugar environment which probably need similar treatment. - Eben PS. I know this is low priority, but I don't want it to be forgotten. Perhaps if we can elaborate on the pieces which could use some UI polish early on in the release cycle we can actually make some improvements for 9.1. On Mon, Sep 1, 2008 at 6:47 PM, Bastien [EMAIL PROTECTED] wrote: Martin Langhoff [EMAIL PROTECTED] writes: n Tue, Sep 2, 2008 at 10:41 AM, Bastien [EMAIL PROTECTED] wrote: | AC not present Plug it to power to complete the firmware upgrade step... AArghh! Thanks. For me AC/DC has never meant anything else than classical music. -- 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: Help activity content
There's a bundle posted at [[Help (activity)]] you can test, but it doesn't have the latest bits. Seth may have an update - there was a lot of activity over the weekend. SJ On Mon, Sep 8, 2008 at 4:07 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Hello, the deadline for the Help activity content was yesterday. http://dev.laptop.org/ticket/7526#comment:9 Is it available? If not, what should we do? Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: #8240 NORM 9.1.0: Implement a dynamic tabbing stack, to allow ping-pong shortcut
On Mon, Sep 8, 2008 at 2:57 PM, Zarro Boogs per Child [EMAIL PROTECTED] wrote: #8240: Implement a dynamic tabbing stack, to allow ping-pong shortcut +--- Reporter: mikus | Owner: Eben Type: enhancement | Status: new Priority: normal| Milestone: 9.1.0 Component: interface-design | Version: not specified Resolution:|Keywords: Next_action: design|Verified: 0 Blockedby:|Blocking: +--- Comment(by mikus): Having, through repetition and experience, learned what alt-tab does (cycle predictably through the open sessions) I personally don't want to have to learn something different about alt-tab. That is why I proposed a *new* sequence for my ping-pong enhancement. I actually disagree, as I find it unnecessary to add yet another way to switch activities. I think having alt-tab for cycling all activities and alt-backtick for cycling all instances of a given activity type is enough. It's better in my mind to create a model which covers as many use cases as possible than to add more models. And I disagree with putting 'dynamic tabbing stack' into the ticket #8240 summary description. Going back to where I came from is a concept I can understand. Having a __dynamic__ stack, which one has to inspect to determine which (baseball) runner has now advanced to second base, goes beyond my understanding (and methinks, that of a kid). Well, I can understand what you mean. However, I'm surprised then that you didn't complain when the first Sugar alt-tab behavior used a fixed stack. ;) I'm pretty sure that the dynamic stack I mention here is used in most other desktops; you just might not realize it, since it's a convenience feature. The ping-pong behavior you mention is, as I see it, a subset of this tabbing behavior, and not logically separate from it. It puts things I'm likely to care more about closer to me (fewer keystrokes away). - Eben -- Ticket URL: http://dev.laptop.org/ticket/8240#comment:3 One Laptop Per Child http://laptop.org/ OLPC bug tracking system ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
#6930 shipped activities need to be audited for licensing information
Does anyone have advice on how to deal with this blocking ticket? Some questions I would have: - which activities do we ship? - do we *require* or just encourage that such activities add COPYING files before 8.2 is released? - where do we document the procedure for new activities to ensure licensing information is clear? Thanks, Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2402
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2402 Changes in build 2402 from build: 2401 Size delta: 0.00M -olpc-licenses 3-1.fc9 +olpc-licenses 8.2.0.0-1.olpc3 --- Changes for olpc-licenses 8.2.0.0-1.olpc3 from 3-1.fc9 --- + Updates from John Gilmore + Add spanish license translations -- 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: #6930 shipped activities need to be audited for licensing information
Daniel Drake wrote: - which activities do we ship? In Browse, clicking activities finding activities from the OLPC Library main page links to an Activity and Library Bundles web page from November 2007 in /usr/share/activities/bundle-archive/ that still offers links to the following installable activity bundles in its bundles subdirectory: Analyze-5.xo (in Joyride Software update) Gmail-2.xo Implode-2.xo (now at v4 according to Activities wiki page) LogViewer-6.xo(at v14 now, in Joyride Software update) Poll-16.xo(at v17 now) Simcity-4.xo (in Joyride Software update) SliderPuzzle-3.xo (at v5 now) StopWatchActivity-1.xo Terminal-9.xo (at v 15 now, in Joyride Software update) wikihow-4.xol (not an activity, I'm not sure if it's out-of-date) In addition, bundle-archive/bundles also contains JigsawPuzzle-1_20071030.xo (at v3 now) This is the case in 8.2-759 on my upgraded XO. These files are also in xo-1-olpc-stream-joyride-build-2338-20080825_2034-devel_ext3-tree that I unpacked. * Trac bug #8029 is that these old activities should be removed (sj marked it fixed). * There's also bug #8145 that the Activity and Library Bundles document links to the wrong release notes (marked fixed, but it isn't). * Also bug #7898 the Activity and Library Bundles document links to an poorly-formatted sugar-handbook.pdf. I don't fully understand how these files appear in Browse, git, or the build, I apologize if I'm missing something. Weeding out stuff that seems out-of-date is good gardening practice. -- =S Page user:skierpage ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Notes on replacing bridging with bonding
Jerry Vonau wrote: Jerry Vonau wrote: Jerry Vonau wrote: Martin Langhoff wrote: On Mon, Sep 8, 2008 at 7:43 PM, Alexander Dupuy [EMAIL PROTECTED] wrote: I have placed TYPE=Bonding in the ifcfg-bond0 config files, but this is not needed for Fedora 7 or later (it doesn't hurt to have it, though) well, I grepped network-functions and ifup-eth and none of the TYPE checks are for bonding anything. The check is done against the output of modprobe. So if it's going to be ignored, I'll save the corresponding bytes (and potential confusion later). ifup does a check for type=Bridge Bonding can be handled via VLAN=yes and PHYDEV=msh0 in the ifcfg files for the bond device, ifup uses those values to setup the bonding in a hotplug environment. The slave (msh0) should have SLAVE=yes MASTER=bond0 in its file. Hotplug works also, bond0 doesn't need to have its slave present to become active, plug the slave in, becomes active and bonding does the right thing. Bye, bye dummy interface. In order to have the hotplug work and enable the bond device without an AA/nic present, the device name must be bondX, that is what ifup keys in on, ifup uses VLAN=yes as the trigger to exit if the device is not present. # OLPC School server # This is an active antenna wireless mesh interface, # infrastructure mode side # (this device also appears as msh0) DEVICE=wlan0 TYPE=Wireless MODE=ad-hoc CHANNEL=1 ESSID=school-mesh-0 ONBOOT=yes #ALIAS=usb8xxx BOOTPROTO=none IPV6INIT=no HOTPLUG=yes NM_CONTROLLED=no SLAVE=yes MASTER=msh0 # Marvell mesh network module, mesh side # (this device also appears as ethN+2) DEVICE=msh0 TYPE=Ethernet ONBOOT=no NM_CONTROLLED=no HOTPLUG=yes SLAVE=yes MASTER=bond0 # OLPC School server # This is a bridge serving a single mesh interface, msh0 # (which may come and go as it is an external USB device). DEVICE=bond0 #TYPE=Bonding IPV6INIT=no ONBOOT=yes BOOTPROTO=none IPADDR=172.18.10.1 NETMASK=255.255.254.0 NETWORK=172.18.10.0 BROADCAST=172.18.11.255 NM_CONTROLLED=no ALIAS=bonding PHYSDEV=msh0 VLAN=yes BONDING_OPTS=mode=mode=active-backup miimon=100 repeat for bond[12] The /sbin/ifup-local can go away, the chain loading is in the config files now. make bond3 for the eth1, the aliases work. ifup parses the files in alpha order, bondXs comes up first, then eth0. # cat /etc/modprobe.d/xs-bonding alias bond0 bonding A modprobe.d/ directory - that's a nice trick! I wasn't aware of this, so just added some lines to the /etc/modprobe.conf file: that's what the most modern doco could find suggested. And the ifup-eth src is clearly looking at the output of modprobe, so there's something to it... well, udev loads the modules on boot, for configured devices. network checks to see if the required module for the nic is loaded, if missing loads it. Think we can just dump a file in /etc/modprobe.d/ with the bonding options needed. I've been using bonding mode=active-backup miimon=100 to test with, any idea what we may be using here? Better yet just add BONDING_OPTS= it the ifcfg file. I covered my but with both modprobe and in the ifcfg files alias bond0 bonding alias bond1 bonding alias bond2 bonding alias bond3 bonding options bond0 mode=mode=active-backup miimon=100 options bond1 mode=mode=active-backup miimon=100 options bond2 mode=mode=active-backup miimon=100 options bond3 mode=mode=active-backup miimon=100 Think it all works, got to have by buddy with a laptop drop by. Jerry ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Combined Sugar/XO manual outline
Hi all,
What follows is the flow of chapters (devised by Seth, Adam, Cynthia
and myself) for the Sugar / XO manual to (hopefully) be included on
the XO for G1G1.
Make all reviews, edits and contributions to these sections as soon as possible!
XO - Introduction
http://en.flossmanuals.net/bin/view/XO/Introduction
XO - About One Laptop per Child
http://en.flossmanuals.net/bin/view/XO/AboutOLPC
XO - About Computers
http://en.flossmanuals.net/bin/view/XO/AboutComputers
XO - How to Volunteer
http://en.flossmanuals.net/bin/view/XO/HowToVolunteer
XO - Getting Started
http://en.flossmanuals.net/bin/view/XO/GettingStarted
XO - Opening the XO
http://en.flossmanuals.net/bin/view/XO/OpeningTheXO
XO - Ports [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Ports
XO - Charging the Battery
http://en.flossmanuals.net/bin/view/XO/ChargingBattery
XO - Starting the XO
http://en.flossmanuals.net/bin/view/XO/Starting
XO - Screen and Speakers
http://en.flossmanuals.net/bin/view/XO/Screen
XO - Keyboard [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Keyboard
Sugar - The Sugar User Interface
http://en.flossmanuals.net/bin/view/Sugar/Interface
Sugar - Home View
http://en.flossmanuals.net/bin/view/Sugar/HomeView
Sugar - Activity View
http://en.flossmanuals.net/bin/view/Sugar/ActivityView
Sugar - Neighborhood View
http://en.flossmanuals.net/bin/view/Sugar/NeighbourhoodView
Sugar - Group View
http://en.flossmanuals.net/bin/view/Sugar/GroupView
Sugar - The Frame
http://en.flossmanuals.net/bin/view/Sugar/TheFrame
Sugar - The Journal
http://en.flossmanuals.net/bin/view/Sugar/TheJournal
Sugar - WHAT IS AN ACTIVITY?
http://en.flossmanuals.net/bin/view/Sugar/WhatIsAnActivity
Sugar - Launching Activities
http://en.flossmanuals.net/bin/view/Sugar/LaunchingActivities
Sugar - Collaborating
http://en.flossmanuals.net/bin/view/Sugar/Collaborating
Sugar - Switching Activities
http://en.flossmanuals.net/bin/view/Sugar/SwitichingActivities
Sugar - Exiting Activities
http://en.flossmanuals.net/bin/view/Sugar/ExitingActivities
Sugar - Installing Activities
http://en.flossmanuals.net/bin/view/Sugar/InstallingActivities
Sugar - Activities Sampler
http://en.flossmanuals.net/bin/view/Sugar/FindingActivities
XO - About Networks and the Internet [ overly technical ? ]
http://en.flossmanuals.net/bin/view/XO/AboutNetworksAndTheInternet
{Sugar - Getting Connected
http://en.flossmanuals.net/bin/view/Sugar/ConnectingNetwork
XO - Give Me the Internet, Please} merge
http://en.flossmanuals.net/bin/view/XO/GiveMeTheInternet
{XO - External Hardware
http://en.flossmanuals.net/bin/view/XO/ExternalHardware
XO - Which wireless devices may work well with my XO?} merge
http://en.flossmanuals.net/bin/view/XO/RouterTable
XO - Troubleshooting Connectivity
http://en.flossmanuals.net/bin/view/XO/Troubleshooting
(and the activities listed at http://en.flossmanuals.net/ )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [sugar] Combined Sugar/XO manual outline
What about the Activity manuals?
-walter
On Mon, Sep 8, 2008 at 5:31 PM, Brian Jordan [EMAIL PROTECTED] wrote:
Hi all,
What follows is the flow of chapters (devised by Seth, Adam, Cynthia
and myself) for the Sugar / XO manual to (hopefully) be included on
the XO for G1G1.
Make all reviews, edits and contributions to these sections as soon as
possible!
XO - Introduction
http://en.flossmanuals.net/bin/view/XO/Introduction
XO - About One Laptop per Child
http://en.flossmanuals.net/bin/view/XO/AboutOLPC
XO - About Computers
http://en.flossmanuals.net/bin/view/XO/AboutComputers
XO - How to Volunteer
http://en.flossmanuals.net/bin/view/XO/HowToVolunteer
XO - Getting Started
http://en.flossmanuals.net/bin/view/XO/GettingStarted
XO - Opening the XO
http://en.flossmanuals.net/bin/view/XO/OpeningTheXO
XO - Ports [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Ports
XO - Charging the Battery
http://en.flossmanuals.net/bin/view/XO/ChargingBattery
XO - Starting the XO
http://en.flossmanuals.net/bin/view/XO/Starting
XO - Screen and Speakers
http://en.flossmanuals.net/bin/view/XO/Screen
XO - Keyboard [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Keyboard
Sugar - The Sugar User Interface
http://en.flossmanuals.net/bin/view/Sugar/Interface
Sugar - Home View
http://en.flossmanuals.net/bin/view/Sugar/HomeView
Sugar - Activity View
http://en.flossmanuals.net/bin/view/Sugar/ActivityView
Sugar - Neighborhood View
http://en.flossmanuals.net/bin/view/Sugar/NeighbourhoodView
Sugar - Group View
http://en.flossmanuals.net/bin/view/Sugar/GroupView
Sugar - The Frame
http://en.flossmanuals.net/bin/view/Sugar/TheFrame
Sugar - The Journal
http://en.flossmanuals.net/bin/view/Sugar/TheJournal
Sugar - WHAT IS AN ACTIVITY?
http://en.flossmanuals.net/bin/view/Sugar/WhatIsAnActivity
Sugar - Launching Activities
http://en.flossmanuals.net/bin/view/Sugar/LaunchingActivities
Sugar - Collaborating
http://en.flossmanuals.net/bin/view/Sugar/Collaborating
Sugar - Switching Activities
http://en.flossmanuals.net/bin/view/Sugar/SwitichingActivities
Sugar - Exiting Activities
http://en.flossmanuals.net/bin/view/Sugar/ExitingActivities
Sugar - Installing Activities
http://en.flossmanuals.net/bin/view/Sugar/InstallingActivities
Sugar - Activities Sampler
http://en.flossmanuals.net/bin/view/Sugar/FindingActivities
XO - About Networks and the Internet [ overly technical ? ]
http://en.flossmanuals.net/bin/view/XO/AboutNetworksAndTheInternet
{Sugar - Getting Connected
http://en.flossmanuals.net/bin/view/Sugar/ConnectingNetwork
XO - Give Me the Internet, Please} merge
http://en.flossmanuals.net/bin/view/XO/GiveMeTheInternet
{XO - External Hardware
http://en.flossmanuals.net/bin/view/XO/ExternalHardware
XO - Which wireless devices may work well with my XO?} merge
http://en.flossmanuals.net/bin/view/XO/RouterTable
XO - Troubleshooting Connectivity
http://en.flossmanuals.net/bin/view/XO/Troubleshooting
(and the activities listed at http://en.flossmanuals.net/ )
___
Sugar mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/sugar
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Expected date for 8.2.0
Hi all, Is the expected release date for 8.2.0 still September 17th? I have a trial that depends on this coming out (for various functionality, mainly the software updates and flash) so I just wanted to see whether it was still looking likely to be released then. Thanks all! The joyrides are looking great! Cheers, Pia -- Software Freedom Dayhttp://softwarefreedomday.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xen and XS.... development
On Mon, Sep 8, 2008 at 3:12 PM, Tom Mitchell [EMAIL PROTECTED] wrote: I recently learned that xen was hobbled on a fedora9 host with older processors. Yes, I've seen all that. It's the Xen upstream not supporting current kernels. I'm mainly using Qemu a bit (assigning usb devices is useful), but it's not my main test target. I test on real hw. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: Expected date for 8.2.0
Pia, The final weeks of September seem more likely to me at the moment. If you want to stay up to date, please watch http://wiki.laptop.org/go/8.2.0 Then you'll receive instant notifications. :) Also, will you be able to help test our next release candidate(s)? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New update.1 build 713
http://pilgrim.laptop.org/~pilgrim/olpc/streams/update.1/build713 Changes in build 713 from build: 712 Size delta: 0.00M -bootfw q2e12-1.olpc2.unsigned +bootfw q2e15-1.olpc2.unsigned --- Changes for bootfw q2e15-1.olpc2.unsigned from q2e12-1.olpc2.unsigned --- + q2e15 this is an unsigned image + trac 8216 - Override persistent devkey when game-button-X is pressed, so you can run customization keys on a system with the dk tag. + New OFW font + Fix trac 8143 where suspend detection was broken after an auto power up reboot (ie a firmware reflash) + Fix typo in reading MAIN_ON pin. + q2e14 this is an unsigned image + New EC code version e14 - faster command processing + trac #8089 - turn on AES unit when starting the OS + trac #1339 - enable SD card insert/remove interrupts + trac #8052 - enable AC97 audio unit when starting the OS + fixed a configuration variable problem + fixed a zero-page problem that caused problems with Linux 2.6.26 + fixed chopped-up text in graphics mode 12 (applies to Windows XP) + trac #7880 - fixed partition numbering glitches in NAND partioning + Include the frame buffer in the high-address map area to make sysrq to OFW work + trac #7774 - support some USB mass storage devices that used to fail + trac #7725 - fixed SD command/data timeouts + trac #7702 - fixed random hang with SD cards 4 GB + Added ls-r command for recursive directory listing - useful for NAND-full analysis + trac #7572 - security files can be in a separate partition + trac #6967 - don't fail to boot if external device contains developer key for a different machine + Windows XP suspend/resume support -- This mail was automatically generated See http://dev.laptop.org/~rwh/announcer/update.1-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: [OLPC library] [sugar] Combined Sugar/XO manual outline
wowsa...looks good to me and certainly makes all that work worthwhile :)
can u give us some dates? i would like to be ready for the roll out, and
also for any PR that you will send out. It will be important to be
especially attentive to incoming requests at those times.
adam
On Mon, 2008-09-08 at 17:48 -0400, Brian Jordan wrote:
On Mon, Sep 8, 2008 at 5:36 PM, Walter Bender [EMAIL PROTECTED] wrote:
What about the Activity manuals?
Ah, that was just me being lazy... I put at the end of my last email:
(and the activities listed at http://en.flossmanuals.net/ )
But for the sake of making it easier for others to find:
http://en.flossmanuals.net/write_activity
http://en.flossmanuals.net/terminal
http://en.flossmanuals.net/chat
http://en.flossmanuals.net/browse
http://en.flossmanuals.net/record
http://en.flossmanuals.net/turtleart
(not linking to individual chapters like with Sugar/XO because the
activity manuals are pretty stand-alone and their chapters shouldn't
need remixing)
-walter
On Mon, Sep 8, 2008 at 5:31 PM, Brian Jordan [EMAIL PROTECTED] wrote:
Hi all,
What follows is the flow of chapters (devised by Seth, Adam, Cynthia
and myself) for the Sugar / XO manual to (hopefully) be included on
the XO for G1G1.
Make all reviews, edits and contributions to these sections as soon as
possible!
XO - Introduction
http://en.flossmanuals.net/bin/view/XO/Introduction
XO - About One Laptop per Child
http://en.flossmanuals.net/bin/view/XO/AboutOLPC
XO - About Computers
http://en.flossmanuals.net/bin/view/XO/AboutComputers
XO - How to Volunteer
http://en.flossmanuals.net/bin/view/XO/HowToVolunteer
XO - Getting Started
http://en.flossmanuals.net/bin/view/XO/GettingStarted
XO - Opening the XO
http://en.flossmanuals.net/bin/view/XO/OpeningTheXO
XO - Ports [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Ports
XO - Charging the Battery
http://en.flossmanuals.net/bin/view/XO/ChargingBattery
XO - Starting the XO
http://en.flossmanuals.net/bin/view/XO/Starting
XO - Screen and Speakers
http://en.flossmanuals.net/bin/view/XO/Screen
XO - Keyboard [ to be made ]
http://en.flossmanuals.net/bin/view/XO/Keyboard
Sugar - The Sugar User Interface
http://en.flossmanuals.net/bin/view/Sugar/Interface
Sugar - Home View
http://en.flossmanuals.net/bin/view/Sugar/HomeView
Sugar - Activity View
http://en.flossmanuals.net/bin/view/Sugar/ActivityView
Sugar - Neighborhood View
http://en.flossmanuals.net/bin/view/Sugar/NeighbourhoodView
Sugar - Group View
http://en.flossmanuals.net/bin/view/Sugar/GroupView
Sugar - The Frame
http://en.flossmanuals.net/bin/view/Sugar/TheFrame
Sugar - The Journal
http://en.flossmanuals.net/bin/view/Sugar/TheJournal
Sugar - WHAT IS AN ACTIVITY?
http://en.flossmanuals.net/bin/view/Sugar/WhatIsAnActivity
Sugar - Launching Activities
http://en.flossmanuals.net/bin/view/Sugar/LaunchingActivities
Sugar - Collaborating
http://en.flossmanuals.net/bin/view/Sugar/Collaborating
Sugar - Switching Activities
http://en.flossmanuals.net/bin/view/Sugar/SwitichingActivities
Sugar - Exiting Activities
http://en.flossmanuals.net/bin/view/Sugar/ExitingActivities
Sugar - Installing Activities
http://en.flossmanuals.net/bin/view/Sugar/InstallingActivities
Sugar - Activities Sampler
http://en.flossmanuals.net/bin/view/Sugar/FindingActivities
XO - About Networks and the Internet [ overly technical ? ]
http://en.flossmanuals.net/bin/view/XO/AboutNetworksAndTheInternet
{Sugar - Getting Connected
http://en.flossmanuals.net/bin/view/Sugar/ConnectingNetwork
XO - Give Me the Internet, Please} merge
http://en.flossmanuals.net/bin/view/XO/GiveMeTheInternet
{XO - External Hardware
http://en.flossmanuals.net/bin/view/XO/ExternalHardware
XO - Which wireless devices may work well with my XO?} merge
http://en.flossmanuals.net/bin/view/XO/RouterTable
XO - Troubleshooting Connectivity
http://en.flossmanuals.net/bin/view/XO/Troubleshooting
(and the activities listed at http://en.flossmanuals.net/ )
___
Sugar mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/sugar
___
Library mailing list
[EMAIL PROTECTED]
http://lists.laptop.org/listinfo/library
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
New joyride build 2403
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2403 Changes in build 2403 from build: 2402 Size delta: 0.00M -etoys 3.0.2126-1 +etoys 3.0.2139-1 --- Changes for etoys 3.0.2139-1 from 3.0.2126-1 --- + Updated translations: de + Fix saving projects with non-ascii names (#8212) + Fix buddy flap showing more buddies (#7749) -- 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 joyride build 2404
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2404 Changes in build 2404 from build: 2403 Size delta: 0.00M -kernel 2.6.25-20080905.1.olpc.e31284e8bd4c73a +kernel 2.6.25-20080908.1.olpc.63579b21df15ab7 -- 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
Stability and Memory Pressure in 8.2
Dear devel@, Kim, Greg, and I have concluded that the instability we experience under memory-pressure in 8.2-759 and similar is the single hard issue that we wish to _attempt_ to address before releasing 8.2 on current timeframes. (We recognize that there are several other issues marked as blocking the release but we are confident that they will be resolved satisfactorily or are, in a few cases, beyond help.) Since most other aspects of the release seem to be running smoothly, Kim asked me to take a more direct role in organizing our efforts produce a release which avoids memory pressure when possible and which is better-behaved when it strikes. To that end, I would like to ask for your assistance with the following questions and tasks: * We need to determine why we encounter low-memory and out-of-memory situations more frequently than in previous releases. - This means that we need to measure how our memory consumption profile has changed since our previous releases. (cscott observes that we were unable to attack the F-9 image size issues until we were able to quantify the effect of changes we had made or were considering making. Consequently, he suggests that we will be unable to attack our current space consumption problems until we are able to generate good numbers (and displays).) - We need to think carefully about (or measure) whether our memory-consumption patterns have changed. I am particularly skeptical of our widespread use of tmpfsen since the pages consumed by files stored on tmpfsen are permanently dirty (and are perhaps accounted for differently than pages mapped into process' address spaces?) - We need to check the configuration of applications like Browse which have configurable caching behavior. (Search for cache or capacity in about:config; check for important compile-time configuration flags.) - We need to test in a variety of different network configurations in order to determine to what extent the network/presence environment affects memory consumption. * We need to check carefully for memory-leaks. Three mechanisms which occur to me include: 1) running the system for a period of time, then scanning for anomalies either manually or in some automated fashion from userland, kernel-land, or OFW (via SysRq or SMM). 2) setting rlimits various processes and noting what dies 3) using debugging tools like the python garbage collection module, guppy/heapy, gdb+macros, valgrind, efence, purify, etc. looking for trouble. * We need to find out why the oom-killer is not killing things fast enough. Based on our results, we might consider configuring /proc/$pid/oom_adj to preferentially kill some processes (e.g., the foreground [or background?] activities.) * We need to determine whether the oom-killer is killing the right processes. (sysctl's vm.oom_dump_tasks can be set to 1 in order to get more verbosity from the oom-killer when it fires). * We ought to ponder whether there are any additional dirty hacks we can experiment with in order to reduce memory consumption; for example, running the Shell and Journal (and DS?) in one process or making use of the compressed-caching code published on this list some months ago. * Random other stuff to think about: - rlimits, cgroups, and the memory resource controller - the warnings in the ramfs and tmpfs code about the deadlocks that tmpfsen can generate under low- or no-memory conditions. - whether our kernel overcommits when allocation requests are made? - whether we can get Browse to behave intelligently when it receives BadAlloc errors from X? - how to run bootchart on the XO - how to generate decent statistics and graphics (preferably in an automated fashion) concerning memory usage as part of our test suite - system-tap's kmalloc2.stp example In conclusion, more to come once I have some actual data; _please_ feel free to assist in collecting it! (though be aware that I may 'volunteer' you if I need your help. (That means you, Tomeu, Riccardo, Deepak, ...)). Regards, Michael P.S. - Thanks to cscott and cjb for their advice during our brief planning session. P.P.S. - Please follow up if you think I missed any avenues that might be worth pursuing in order to address this rather large and fuzzy problem space -- there's plenty of room left for good ideas that didn't occur to me, Scott, or Chris. ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Does anyone care about beecrypt on the XS?
On xs-0.4 and earlier we have beecrypt. On the F9 builds yum gets its panties in a knot over beecrypt while building the Pungi or revisor imgs. I can't understand it, help is not forthcoming, and I have, hmmm, other priorities in mind. - Do you use beecrypt or plan to use it for something? - On the XS? In the meantime http://dev.laptop.org/ticket/8363 cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Notes on replacing bridging with bonding
Martin Langhoff escribió: This is roughly what I am doing: # mark the device as a bonding device # - for some reason TYPE does not work I have placed TYPE=Bonding in the ifcfg-bond0 config files, but this is not needed for Fedora 7 or later (it doesn't hurt to have it, though) # cat /etc/modprobe.d/xs-bonding alias bond0 bonding A modprobe.d/ directory - that's a nice trick! I wasn't aware of this, so just added some lines to the /etc/modprobe.conf file: alias bond0 bonding options bond0 miimon=100 mode=3 downdelay=1000 updelay=1000 As far as I know, these options are pretty much the same as the ones which can be specified with BONDING_OPTS - I guess it is probably better to do that there (this feature was added since Fedora Core 5, when I set mine up). As for the specifics of what might be appropriate for a bonded channel with only one interface expected to be enslaved, I would suggest something along the lines of: # use active backup mode, allowing primary slave to be specified mode=1 # set multicast only on primary multicast=1 # set primary slave primary=wlan1 # set status monitoring to 1000msec miimon=1000 I'm not 100% sure about the last one. I believe that if there is no monitoring, the link status of the bond interface won't reflect the link status of the underlying device, but I haven't confirmed this (or, for that matter, that the link status of the bond device will reflect the underlying device(s) if monitoring is enabled). There is presumably some overhead to this, but at once a second or even tenth of a second, it is negligible. Thinking about this more, since these are wireless devices (active antenna via USB) I don't even know if there is a link status - for those you might want to omit this option. It could theoretically be useful for the wired Ethernet interfaces, though. Other than these options, which aren't strictly necessary (your setup with the defaults should work fine) everything you have looks perfectly reasonable. The only advantage to specifying the active backup mode is a little bit of misconfiguration protection, so that if somehow a second interface gets enslaved to a bond, it won't be used for transmission (packets will still be received on it, however). Explicitly specifying the primary slave in the BONDING_OPTS of the master duplicates some of the configuration which introduces the possibility of inconsistency - I'm not sure what your feelings on that are. If the primary slave is not explicitly specified, the first enslaved device is the primary. @alex -- mailto:[EMAIL PROTECTED] ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] A few F9 upgrade things I need help with...
As part of the XS upgrade, I've ended up caught with a number of F9 oddities -- none of them a complete blocker, but definitely rought edges... - Cannot include beecrypt in Pungi/Revisor build - this is probably a bug worthy of filing in BZ but needs a bit of diagnosys. http://dev.laptop.org/ticket/8363 - Anaconda conflicts with xs-config - Filed as BZ 461550 http://dev.laptop.org/ticket/8366 - Anaconda crash during install with USB-disk-based ks.cfg BZ 461453 - this probably affects all USB-disk based installs. - Anaconda: Install from USB disk: only ISO picked up BZ 461548 - Anaconda: Install from USB disk: Awkward to provide a ks.cfg BZ 461549 All of these are - I think - worthwhile to whack for the ease-of-install experience with Fedora and the XS... cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] F9 XS - Take it for a spin...
with some caveats... this is a developer preview, lots of things are b0rken, but still... - download all 759MB of iso here http://xs-dev.laptop.org/xs/other/Fedora-0.5.dev2-i386.iso - Burn it to a DVD (see notes below on using USB sticks) - Install it on a new machine - use the kickstart-driven default menu option - After install 1 - login as root 2 - cd /etc make -f xs-config.make earlyset reboot - If you have 2 NICs and F9 got them the wrong way around, just invoke xs-swapnics and reboot Other installation notes... - Upgrades... for some reason, Anaconda isn't realising that it is supposed to be upgrading... working on that... - From a USB device! Ah, well, mildly annoying - - grab mkusbinstall from here http://dev.laptop.org/git?p=projects/xs-livecd;a=tree;f=util;h=202b31c7ef280036e3edd99ef68871e3d0815295;hb=HEAD - use it like you'd use livecd-iso-to-disk - Anaconda will fail to kind the ks file - fix the path to be 'hd:sdb1:/ks.cfg' - assuming your USB disk is mounted as sdb1. It may require waiting a few seconds until sdb1 is mounted. - Anaconda will need to be told where the ISO is. Pick Hard Drive install, sdb1, and the path is 'iso' What's not there yet - idmgr won't start due to sqlalchemy. Douglas is working on some sqlalchemy surgery. - fakechroot doesn't play well with rsync. Waiting on upstream to nod at the patches, though they look good to me, and we do have an RPM for it. - ejabberd is the wrong version - got to fix that. cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
