Re: Videochat - any status?
Le jeudi 11 septembre 2008 à 14:21 +1000, Pia Waugh a écrit : Hi all, I have a great need for the video chat application to use for remote speech pathology and other services to remote communities through chat. Does anyone know the status of this project: http://wiki.laptop.org/go/Video_Chat It looks like nothing has happened with it for several months. If there is anyone leading this, could they post a status of the project? Few months ago I posted this mail [1] explaining the current status of VideoChat. The situation didn't evolve since but I guess it should still be basically usable. G. [1] http://lists.laptop.org/pipermail/devel/2008-April/013227.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2418
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2418 Changes in build 2418 from build: 2417 Size delta: 0.00M -hulahop 0.4.5-2.olpc3 +hulahop 0.4.6-1.olpc3 -sugar 0.82.3-1.olpc3 +sugar 0.82.4-1.olpc3 -sugar-toolkit 0.82.5-1.olpc3 +sugar-toolkit 0.82.6-1.olpc3 -- 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: New joyride build 2413
Intentional? Marco On Wed, Sep 10, 2008 at 8:09 AM, Build Announcer v2 [EMAIL PROTECTED] wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2413 Changes in build 2413 from build: 2412 Size delta: -70.91M -olpc-library-core 1-26 -- 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 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
Martin, On Thu, Sep 11, 2008 at 12:44 AM, Martin Langhoff [EMAIL PROTECTED] wrote: On Thu, Sep 11, 2008 at 12:37 AM, Ricardo Carrano [EMAIL PROTECTED] wrote: The release notes can be acessed here: http://www.laptop.org/teamwiki/index.php/Tech:FW_8388_RELEASE_NOTES 22.p18 is the current version in joyride. Anything older than 22.p14 is not recommended at all (quite the opposite). Thanks for the link. There isn't much info on stability. - Which of those releases are considered usable? - Which one would be the lowest risk for the XS? - Is any of those releases known to work well with the stock F9 kernel? - Is any of those releases known to survive long periods of time working? (I am seeing a nightly lockup with the AA here, on little or no traffic - and people tell me that we have a usb bus reset on the XO to workaround a similar condition.) cheers, Fedora 9 ships with a 2.6.25 kernel with a new libertas driver. Because of the changes implemented in this driver, you should use the latest firmware (22.p18). Please, never use 2.6.25 kernel with older firmware. The result is the instability you see. In short, for everyone: Don't use anything different from 22.p14, 22.p17 or 22.p18. In kernel 2.6.25 use 22.p18. Cheers! Ricardo 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: New joyride build 2413
On Thu, Sep 11, 2008 at 7:22 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Intentional? yup, the monolithic library is being split into content bundles that can be added with a customization stick, or added to images for e.g. Peru or G1G1. bobby Marco On Wed, Sep 10, 2008 at 8:09 AM, Build Announcer v2 [EMAIL PROTECTED] wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2413 Changes in build 2413 from build: 2412 Size delta: -70.91M -olpc-library-core 1-26 -- 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 ___ 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: #7685 NORM 9.1.0: Alternate home layouts; fixed ring scaling; better modularization of layouts
I want to initiate some discussion on a similar topic to the one you
bring up here, regarding the extensibility of the layouts. What I'd
like to see is layout modules which provide translation from a set of
input coordinates to a set of output coordinates (eg,
_calculate_position), which are then fed to a smooth positioning
algorithm, making it possible to transition cleanly between layouts,
and to rearrange layouts via drag'n'drop.
Let me illustrate what I mean by way of an example. Consider the Ring
view you bring up. If we define our translation function to calculate
a radius based on the number of elements in the list, and then
calculate the radial ordering of the elements by calculating the angle
between the center of the ring and their input coordinates
(atan2(y,x)), we can then equally space them around a ring spatially
relative to their initial locations. The beauty of this idea is that
we get drag'n'drop reordering for free. If, every time new
coordinates are calculated, we animate the icons to their new target
positions, we can simply drop an icon anywhere we choose on the screen
and it will neatly slide into the nearest spot in the ring.
Of course, the translation function could do anything. It could force
things onto a grid, into a sunflower, into non-overlapping positions,
etc. All of these types of layouts require merely the list of
coordinates (since we assume equal size elements) as input.
We can make things more interesting, however, by offering further
information, both as input and output. If we define an object which
represents an element in the layout, giving it size, position,
orientation, name, tags, and other metadata, (all of these mutable by
the translation function) it's possible to create layouts that perform
logical grouping, create sortings (even in multiple dimensions),
filter the input, etc. The visualization space is much greater (and
think of how much fun it could be to create new layouts like this for
visualizing the neighborhood view.)
- Eben
PS. You could raise UnimplementedException, or you could simply
define the identity function in the base class.
On Thu, Sep 11, 2008 at 3:07 AM, Zarro Boogs per Child
[EMAIL PROTECTED] wrote:
#7685: Alternate home layouts; fixed ring scaling; better modularization of
layouts
-+--
Reporter: cscott | Owner: marco
Type: defect | Status: new
Priority: normal | Milestone: 9.1.0
Component: sugar | Version: not specified
Resolution: |Keywords: r?
Next_action: never set |Verified: 0
Blockedby: |Blocking:
-+--
Comment(by mtd):
I like the (sugar) patch (it's moved to
http://dev.laptop.org/git?p=users/cscott/sugar;a=summary ), especially the
modularization parts. Comments on the patch are 1) there are a few times
we do y = m*x+b instead of y = m * x + b that'd be nice to tidy up;
and 2) I wish the RingLayout class's name could better express that it
is suitable as a superclass to {Box,Triangle,Sunflower}Layout - perhaps
RingLayout should be renamed BaseLayout and its _calculate_position()
function should raise UnimplementedException, and then a new RingLayout
defined, which implements that function as the current RingLayout does.
If it were up to me it'd be r+ with those comments. I don't know when it
should land, though.
--
Ticket URL: http://dev.laptop.org/ticket/7685#comment:7
One Laptop Per Child http://laptop.org/
OLPC bug tracking system
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Expected date for 8.2.0
On Wed, Sep 10, 2008 at 6:21 PM, Douglas Bagnall [EMAIL PROTECTED] wrote: This might also focus the minds of prospective designers: rather than struggling to incorporate the letters X and S, try to make your logo look like a school. I've been wondering about this. My understanding is that it's called an XO because the X and O kind of look like a person. (And make it not language specific.) XS is language specific. Now I can't think of any letters you could use make a picture of a server (or even what a 'server' looks like), however, when the strictures of typography are eliminated why should X or S be there at all. I can't think of any of the XO Activities that use letters/words in their icons at all... Bill Bogstad P.S. I checked the Activities page: ABC Hangman, Epals, a couple of wiki related activities with stylized W, and C: for dos emulator. In those cases, using letters make sense. ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: Stability and Memory Pressure in 8.2
On Wed, Sep 10, 2008 at 8:13 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 2:05 PM, James Cameron [EMAIL PROTECTED] wrote: But I did notice one odd thing that I wasn't fully aware of until now ... the byte-code of the built-in modules was present, complete with doc strings ... for example; Yes, we are aware of this one and have a fix on the line: https://bugzilla.redhat.com/show_bug.cgi?id=460334 There has been a thread recently on devel or sugar ml about it. If you could help us quantify how much this could help, it would be much appreciated. Here's a quick reference to that previous thread: http://lists.laptop.org/pipermail/sugar/2008-August/007969.html I guess I meant to turn on -OO on joyride, but didn't quite get around to it; it would require patching/forking our numpy and python, and then tweaking the sugar-shell startup to use -OO. It looked like this would save ~6M, but I don't know yet how much extra NAND space it would take for the .pyo files. I might be able to experiment and make a build or two on the faster branch to quantify this. --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
License your bundles, please!
John Gilmore has been pushing us to get our licensing ducks in a row. The one remaining problem has been activities and content bundles: we can't legally distribute bundles that don't have a clear statement of license. I have added documentation to: http://wiki.laptop.org/go/Activity_bundles#.info_File_Format and http://wiki.laptop.org/go/Sample_library.info_file on a new 'license=' field in the activity.info and library.info files, closely modelled after the License: field in RPM packages. Now I need your help! Could you all look at any activity and content bundles you maintain, add an appropriate license statement if there isn't one already (comments at the top of source files, or a COPYING file, or a statement in the README, etc) and the add a 'license=' field to your activity.info or library.info documenting the license choice? Commenting on http://dev.laptop.org/ticket/8411 when you've done so will help me keep track of how we're doing. We will not be able to ship any activities in our G1G1 8.2 image which do not have appropriate license information -- since mstone's plan-of-the-moment is to make the first release candidate for this next week, the situation is pretty urgent. Also, we will probably need to remove any activity bundles hosted on the dev.laptop.org wiki which do not have statements of license at one point. Your help is appreciated! Thanks! --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Stability and Memory Pressure in 8.2
On Thu, Sep 11, 2008 at 5:30 PM, C. Scott Ananian [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 8:13 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 2:05 PM, James Cameron [EMAIL PROTECTED] wrote: But I did notice one odd thing that I wasn't fully aware of until now ... the byte-code of the built-in modules was present, complete with doc strings ... for example; Yes, we are aware of this one and have a fix on the line: https://bugzilla.redhat.com/show_bug.cgi?id=460334 There has been a thread recently on devel or sugar ml about it. If you could help us quantify how much this could help, it would be much appreciated. Here's a quick reference to that previous thread: http://lists.laptop.org/pipermail/sugar/2008-August/007969.html I guess I meant to turn on -OO on joyride, but didn't quite get around to it; it would require patching/forking our numpy and python, and then tweaking the sugar-shell startup to use -OO. It looked like this would save ~6M, but I don't know yet how much extra NAND space it would take for the .pyo files. I might be able to experiment and make a build or two on the faster branch to quantify this. Would be great if you could look into it. I guess we could drop the .pyc files and use the .pyo instead. Thanks, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Stability and Memory Pressure in 8.2
On Thu, Sep 11, 2008 at 6:51 PM, C. Scott Ananian [EMAIL PROTECTED] wrote: On Thu, Sep 11, 2008 at 12:16 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote: On Thu, Sep 11, 2008 at 5:30 PM, C. Scott Ananian [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 8:13 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 2:05 PM, James Cameron [EMAIL PROTECTED] wrote: But I did notice one odd thing that I wasn't fully aware of until now ... the byte-code of the built-in modules was present, complete with doc strings ... for example; Yes, we are aware of this one and have a fix on the line: https://bugzilla.redhat.com/show_bug.cgi?id=460334 There has been a thread recently on devel or sugar ml about it. If you could help us quantify how much this could help, it would be much appreciated. Here's a quick reference to that previous thread: http://lists.laptop.org/pipermail/sugar/2008-August/007969.html I guess I meant to turn on -OO on joyride, but didn't quite get around to it; it would require patching/forking our numpy and python, and then tweaking the sugar-shell startup to use -OO. It looked like this would save ~6M, but I don't know yet how much extra NAND space it would take for the .pyo files. I might be able to experiment and make a build or two on the faster branch to quantify this. Would be great if you could look into it. I guess we could drop the .pyc files and use the .pyo instead. http://dev.laptop.org/ticket/8431 now tracks the issue. I've started by putting appropriately patched versions of python and numpy into joyride, so you can experiment with -OO on a joyride image without having to worry about these particular bugs. I've confirmed that python 2.5.2 and numpy 1.2.0 already have/will have the relevant patches, so we probably won't need the fork by our next major release. --scott p.s. does anyone know why fedora isn't using python 2.5.2 yet? It was released in February '08; I'm surprised that it's not in F9 or F10. I think the plan is to get one 2.5.1 more in rawhide with some new patches (including the -OO fix) and then doing a 2.5.2 rpm. If 2.5.2 brings more trouble than what can be solved for F10, then we can go back to 2.5.1+patches. Regards, Tomeu ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 2420
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2420 Changes in build 2420 from build: 2418 Size delta: 0.00M -numpy 1.1.0-1.fc9 +numpy 1.1.1-1.olpc3.1 -python 2.5.1-26.fc9 +python 2.5.1-26.olpc3.1 -python-libs 2.5.1-26.fc9 +python-libs 2.5.1-26.olpc3.1 --- Changes for numpy 1.1.1-1.olpc3.1 from 1.1.0-1.fc9 --- + Fixes to 'python -OO' option, which ought to strip docstrings. + These patches have both been accepted upstream, in python 2.5.2 --- Changes for python 2.5.1-26.olpc3.1 from 2.5.1-26.fc9 --- + Fixes to 'python -OO' option, which ought to strip docstrings. + These patches have both been accepted upstream, in python 2.5.2 + Beta release of new API + fix bug with l10n categories files + Marco needs to write a real ChangeLog! + Marco needs to write a real ChangeLog! --- Changes for python-libs 2.5.1-26.olpc3.1 from 2.5.1-26.fc9 --- + Fixes to 'python -OO' option, which ought to strip docstrings. + These patches have both been accepted upstream, in python 2.5.2 -- 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: Bundle activity
Matt, Would this activity be modified easily to take files from within the Journal and move them back into the user's /home/, either compressed or uncompressed? Call it the File activity. Erik On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote: Hello all, I am one of the students who will be working on the Bundle activity suggested by Eben Eliason. I understand that the activity should be designed to manage a variety of archive formats (zip, tar, gz, etc.), and it should support both the extraction of files from an archive into the Journal as well as linking a set of entries from the Journal into a bundle. Also, I see a few additional details are provided in its wiki [ http://wiki.laptop.org/go/Bundle_(activity)]. Is this an active project right now? If not, our team would like to start working on it soon, but first we are looking for feedback on functionality, how it should integrate with the Journal, UI particulars, etc. If this project is not currently active, we are eager to hear any helpful input you might have. Thanks, Matt ___ 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: Bundle activity
That's not within the scope of this activity, no. This activity is strictly about viewing and creating bundles. - Eben On Thu, Sep 11, 2008 at 3:01 PM, Erik Garrison [EMAIL PROTECTED] wrote: Matt, Would this activity be modified easily to take files from within the Journal and move them back into the user's /home/, either compressed or uncompressed? Call it the File activity. Erik On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote: Hello all, I am one of the students who will be working on the Bundle activity suggested by Eben Eliason. I understand that the activity should be designed to manage a variety of archive formats (zip, tar, gz, etc.), and it should support both the extraction of files from an archive into the Journal as well as linking a set of entries from the Journal into a bundle. Also, I see a few additional details are provided in its wiki [ http://wiki.laptop.org/go/Bundle_(activity)]. Is this an active project right now? If not, our team would like to start working on it soon, but first we are looking for feedback on functionality, how it should integrate with the Journal, UI particulars, etc. If this project is not currently active, we are eager to hear any helpful input you might have. Thanks, Matt ___ 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: Bundle activity
Bundles are files. In this case they are compressed files. I'm just pointing out that if we're going to work with files of this kind we should think about working with files of the non-compressed kind. The overlap between the Bundle tool and a tool to allow the same operations on uncompressed files is pretty large. Note that bundle management is usually dealt with in other desktop environments through the file browser. Erik On Thu, Sep 11, 2008 at 03:57:12PM -0400, Eben Eliason wrote: That's not within the scope of this activity, no. This activity is strictly about viewing and creating bundles. - Eben On Thu, Sep 11, 2008 at 3:01 PM, Erik Garrison [EMAIL PROTECTED] wrote: Matt, Would this activity be modified easily to take files from within the Journal and move them back into the user's /home/, either compressed or uncompressed? Call it the File activity. Erik On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote: Hello all, I am one of the students who will be working on the Bundle activity suggested by Eben Eliason. I understand that the activity should be designed to manage a variety of archive formats (zip, tar, gz, etc.), and it should support both the extraction of files from an archive into the Journal as well as linking a set of entries from the Journal into a bundle. Also, I see a few additional details are provided in its wiki [ http://wiki.laptop.org/go/Bundle_(activity)]. Is this an active project right now? If not, our team would like to start working on it soon, but first we are looking for feedback on functionality, how it should integrate with the Journal, UI particulars, etc. If this project is not currently active, we are eager to hear any helpful input you might have. Thanks, Matt ___ 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: Bundle activity
IIUC the activity would not deal with files but with journal entries. So you can copy several journal entries into a zipped entry, and you can unzip entries from a zipped one. This has nothing to do with files in the home directory (besides, a regular activity cannot write to home, and read only some of it). - Bert - Am 11.09.2008 um 22:12 schrieb Erik Garrison: Bundles are files. In this case they are compressed files. I'm just pointing out that if we're going to work with files of this kind we should think about working with files of the non-compressed kind. The overlap between the Bundle tool and a tool to allow the same operations on uncompressed files is pretty large. Note that bundle management is usually dealt with in other desktop environments through the file browser. Erik On Thu, Sep 11, 2008 at 03:57:12PM -0400, Eben Eliason wrote: That's not within the scope of this activity, no. This activity is strictly about viewing and creating bundles. - Eben On Thu, Sep 11, 2008 at 3:01 PM, Erik Garrison [EMAIL PROTECTED] wrote: Matt, Would this activity be modified easily to take files from within the Journal and move them back into the user's /home/, either compressed or uncompressed? Call it the File activity. Erik On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote: Hello all, I am one of the students who will be working on the Bundle activity suggested by Eben Eliason. I understand that the activity should be designed to manage a variety of archive formats (zip, tar, gz, etc.), and it should support both the extraction of files from an archive into the Journal as well as linking a set of entries from the Journal into a bundle. Also, I see a few additional details are provided in its wiki [ http://wiki.laptop.org/go/Bundle_(activity)]. Is this an active project right now? If not, our team would like to start working on it soon, but first we are looking for feedback on functionality, how it should integrate with the Journal, UI particulars, etc. If this project is not currently active, we are eager to hear any helpful input you might have. Thanks, Matt ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] recover from broken yum transaction
On Sep 11, 2008, at 11:01 AM, Seth Vidal wrote: On Thu, 2008-09-11 at 17:42 +1200, Martin Langhoff wrote: On Thu, Sep 11, 2008 at 3:50 PM, Seth Vidal [EMAIL PROTECTED] wrote: When this happens you should run: yum-complete-transaction Interesting toy! I think you mentioned it at Fudcon Boston and I hadn't been able to recall the right name. Thinking of using it in the use case of the school server (very unreliable power, no sysadmins available, 100% unattended updates) - - Is it safe to run at boot time via an init script? as long as the network is up, it should be. I assume you mean as long as the server has an Internet connection to the yum repositories ?Or did you mean as long as the networking subsystem is up ? This may be a show stopper for us, as plenty of servers won't have a reliable network connection to the Internet. Thanks! wad ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: Bundle activity
Firstly, insofar as the hierarchical filesystem is a worldwide standard for human-computer interface, it is something which is useful to teach students. So it seems like a very useful activity. Secondly, from a utility perspective... Have you ever tried to move a file out of the Journal and onto a USB flash drive? Then change the name... Or maybe put such a file into a specific directory on the flash drive? If we don't want the journal to behave this way then perhaps the best place to put the functionality is in another activity. Bundle seems to have sensible overlap with this problem space. When I was in Uruguay more teachers asked me about issues with the Journal than anything else. I keep poking on this issue to remind people that it's not going away in the field. Erik On Thu, Sep 11, 2008 at 10:17:39PM +0200, Bert Freudenberg wrote: IIUC the activity would not deal with files but with journal entries. So you can copy several journal entries into a zipped entry, and you can unzip entries from a zipped one. This has nothing to do with files in the home directory (besides, a regular activity cannot write to home, and read only some of it). - Bert - Am 11.09.2008 um 22:12 schrieb Erik Garrison: Bundles are files. In this case they are compressed files. I'm just pointing out that if we're going to work with files of this kind we should think about working with files of the non-compressed kind. The overlap between the Bundle tool and a tool to allow the same operations on uncompressed files is pretty large. Note that bundle management is usually dealt with in other desktop environments through the file browser. Erik On Thu, Sep 11, 2008 at 03:57:12PM -0400, Eben Eliason wrote: That's not within the scope of this activity, no. This activity is strictly about viewing and creating bundles. - Eben On Thu, Sep 11, 2008 at 3:01 PM, Erik Garrison [EMAIL PROTECTED] wrote: Matt, Would this activity be modified easily to take files from within the Journal and move them back into the user's /home/, either compressed or uncompressed? Call it the File activity. Erik On Wed, Sep 10, 2008 at 12:49:03AM -0400, Matt Der wrote: Hello all, I am one of the students who will be working on the Bundle activity suggested by Eben Eliason. I understand that the activity should be designed to manage a variety of archive formats (zip, tar, gz, etc.), and it should support both the extraction of files from an archive into the Journal as well as linking a set of entries from the Journal into a bundle. Also, I see a few additional details are provided in its wiki [ http://wiki.laptop.org/go/Bundle_(activity)]. Is this an active project right now? If not, our team would like to start working on it soon, but first we are looking for feedback on functionality, how it should integrate with the Journal, UI particulars, etc. If this project is not currently active, we are eager to hear any helpful input you might have. Thanks, Matt ___ 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
New joyride build 2421
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2421 Changes in build 2421 from build: 2420 Size delta: 0.00M -libxml2-python 2.6.32-3.fc9 +libxml2-python 2.7.1-1.fc9 -yum 3.2.19-3.fc9 +yum 3.2.17-2.fc9 -libxml2 2.6.32-3.fc9 +libxml2 2.7.1-1.fc9 --- Changes for yum 3.2.17-2.fc9 from 3.2.19-3.fc9 --- + add patch to fix yum install name.arch matching + add patch to fix mash's parser use. + 3.2.19 + 3.2.18 --- Changes for libxml2 2.7.1-1.fc9 from 2.6.32-3.fc9 --- + upstream release of 2.7.1 + fix python serialization which was broken in 2.7.0 + upstream release of 2.7.0 + switch to XML 1.0 5th edition + switch to RFC 3986 for URI parsing + better entity handling + option to remove hardcoded limitations in the parser + more testing + a new API to allocate entity nodes + and lot of fixes and cleanups -- 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: q2e15 and a bricked BTest-2
Richard Smith wrote: All 'e' series firmware will brick any machine using a Geode GX (B1 B2) so e12 would have not have saved you. Right, it would be a good idea to mention this in http://wiki.laptop.org/go/Hardware_specification#Software_on_the_develop ment_systems It is pretty easy to miss it there, but it is the only place in the wiki where I saw a similar warning relating to the ATest boards. A short note here might be easier to find (but I don't know if it wold be out of place): http://wiki.laptop.org/go/Firmware B2's have been unsupported for quite a while now and we don't do any testing on them. Nor do we care to since we don't have the resources. That is to be expected. If you make and account on the developer program website and say you have a B2 that you want replaced we will send you a new MP machine. Make sure there is some sort of project listed with your request. I would actually like to stick with the B2 for now. It has a certain historical value. Its main use was to help illustrate the various talks I have given about OLPC. Between 500 and 700 people have had a chance to play a little with it, but that hasn't happened in months so it has probably outlived its usefulness in this regard. I am also interested in SqueakNOS and for that 64MB is quite enough, let alone 128MB. -- Jecel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 12:24 AM, Ricardo Carrano [EMAIL PROTECTED] wrote: Fedora 9 ships with a 2.6.25 kernel with a new libertas driver. Because of the changes implemented in this driver, you should use the latest firmware (22.p18). Please, never use 2.6.25 kernel with older firmware. Ok, however... The result is the instability you see. Sorry - I should have been clearer - the instability I was mentioning was pre-F9 upgrade. I haven't been running a F9 XS with AAs long enough... until yesterday it was reinstall/reboot/lather/rinse/repeat. In short, for everyone: Don't use anything different from 22.p14, 22.p17 or 22.p18. In kernel 2.6.25 use 22.p18. Right. It's not that simple however. Before switch to the versions you recommend I want to have the complete picture *including known bugs*. Can you help me with that? (That's what my earlier with my release manager hat on... hint was all about :-) ). In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast - There are odd bugs with WPA what else? Michails my best guess is that you'd be the owner for a current issues list like that. Is that correct? What known bugs do I buy into when I follow Ricardo's advise? 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: Scratch localization.
Hi, Erik. Apologies for the delay in responding. I was on vacation, then finishing the Scratch 1.3 release. Scratch remembers the last language set by the user in the Scratch.ini file. If that file is read-only, it fails gracefully. In older versions of Scratch (such as the current XO version), if no language was specified in the Scratch.ini file, Scratch would start up in English. However, it now uses the Squeak LocalePlugin to set the default language. So if the computer's locale is set to Spanish, Scratch should start up in Spanish. This feature has not yet been tested on Linux, but it does work on Mac OS and Windows. Many thanks to the Squeak folks for creating the LocalePlugin! So I think things may work fine as they are, once we've updated XO Scratch to the 1.3 release. (I'm working on that now, with help from Scott if he is willing). Scratch does not need to write persistent data to any other files. (It does need to write user projects somewhere, but Scott has solved that problem for now.) -- John On Aug 27, 2008, at 1:00 PM, Erik Garrison wrote: On Wed, Aug 27, 2008 at 06:54:18PM +0200, Bert Freudenberg wrote: Am 27.08.2008 um 18:38 schrieb C. Scott Ananian: Scratch appears to require manual editing of the Scratch.ini file in order to come up in a language other than English. Is there any way I can pass a command-line option in bin/scratch-activity to set the Language preference based on the value of $LANG? I'd prefer that we not have to ship a different Scratch bundle per-country. The Right Way to do it would be using the LocalePlugin, as Etoys does. If you need to patch up the bundle you could use the symlink trick again, the actual Scratch.ini would live in data/. Thus the language (and other settings possibly) that the user choses would persist. When running for the first time, the startup script could generate an initial Scratch.ini for the right language. What other persistent data beyond Scratch.ini does Scratch like to modify? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: recognizing a previous connection
Hi Pia, Robert, Mikus and team, I'm not sure this dictates the right design, but I am aware of several sites planning to use multiple access points. One in the US will have ~40! and I believe that another in the US (NYC) has many APs and a robust network. One school in Rwanda has recently been funded to install 10 x APs. That said, I think our biggest deployments in Peru and Uruguay have either 1 or none (perhaps Erik G can confirm). One of the reasons to have multiple APs and a school server is to scale the number of XOs that can collaborate. I'm told that when an AP and XS are used, the wireless uses unicast to the AP instead of multicast in a mesh allowing better optimization of the available BW. Then the XS Jabber server can connect them. In that case, I think it would be preferred to have a set of XOs consistently tied to the same AP. BTW the active antenna is not currently sold or deployed. It's likely to come back in the future but right now it is on hold. Thanks for the Niue URL. That's great detail! We are trying strenuously to get this kind of detail down to the AP type and model for all current or pending deployments. As soon as we have something verified to share, we will post it. Thanks, Greg S *** Date: Thu, 11 Sep 2008 07:45:13 +1000 From: Pia Waugh [EMAIL PROTECTED] Subject: Re: recognizing a previous connection To: [EMAIL PROTECTED] [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii Hi all, quote who=[EMAIL PROTECTED] It is my understanding that deployments with larger schools will be using WAPs and possibly some active antennas (currently a shortage of these). These large schools are more like the G1G1 situation as the pupil moves from one area of the school to another they may connect to another AP. I have informed a person involved with deployment at large schools of this thread (and the other thread). I am hoping they will respond with information about the wireless topography. Actually, you can overcome this in a large school by using a WDS network, or by simply giving all the access points the same name, then as the student moves around the campus they seamlessly switch from AP to AP, as it is effectively the same wireless network. I did this at two schools of ~200-250 students each with a WDS setup (as they didn't have ethernet to the classrooms), and it worked perfectly. If you have ethernet to the classrooms, then APs with the same ESSID would work even better. Details here: http://wiki.laptop.org/go/OLPC_Niue#Documentation Cheers, Pia ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Scratch localization.
John, In Peru the team is using the Scratch.ini file to set the language to spanish. There is a long delay between Scratch startup and the setting of the language, in which Scratch is in english. Does the LocalePlugin rectify this? What work needs to be done to update XO Scratch to Scratch 1.3? Erik On Thu, Sep 11, 2008 at 05:37:48PM -0400, John Maloney wrote: Hi, Erik. Apologies for the delay in responding. I was on vacation, then finishing the Scratch 1.3 release. Scratch remembers the last language set by the user in the Scratch.ini file. If that file is read-only, it fails gracefully. In older versions of Scratch (such as the current XO version), if no language was specified in the Scratch.ini file, Scratch would start up in English. However, it now uses the Squeak LocalePlugin to set the default language. So if the computer's locale is set to Spanish, Scratch should start up in Spanish. This feature has not yet been tested on Linux, but it does work on Mac OS and Windows. Many thanks to the Squeak folks for creating the LocalePlugin! So I think things may work fine as they are, once we've updated XO Scratch to the 1.3 release. (I'm working on that now, with help from Scott if he is willing). Scratch does not need to write persistent data to any other files. (It does need to write user projects somewhere, but Scott has solved that problem for now.) -- John On Aug 27, 2008, at 1:00 PM, Erik Garrison wrote: On Wed, Aug 27, 2008 at 06:54:18PM +0200, Bert Freudenberg wrote: Am 27.08.2008 um 18:38 schrieb C. Scott Ananian: Scratch appears to require manual editing of the Scratch.ini file in order to come up in a language other than English. Is there any way I can pass a command-line option in bin/scratch-activity to set the Language preference based on the value of $LANG? I'd prefer that we not have to ship a different Scratch bundle per-country. The Right Way to do it would be using the LocalePlugin, as Etoys does. If you need to patch up the bundle you could use the symlink trick again, the actual Scratch.ini would live in data/. Thus the language (and other settings possibly) that the user choses would persist. When running for the first time, the startup script could generate an initial Scratch.ini for the right language. What other persistent data beyond Scratch.ini does Scratch like to modify? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
re: 8.2.0 Release Criteria ECO Documentation (Michael Stone)
Hi Michael, I thought of one item we missed in making this checklist. We need to pick the set of activities which we will include in the factory G1G1 image. Can you add that to the check list so we are fully ready to produce this image when its done? If that decision can come out of synch with the blessing of the core image we can track it elsewhere. I just want to make sure we nail it down soon so we don't have a lot of latency between finalizing the image and getting it shipped on newly manufactured XOs. Thanks, Greg S *** Date: Wed, 10 Sep 2008 18:52:17 -0400 From: Michael Stone [EMAIL PROTECTED] Subject: 8.2.0 Release Criteria ECO Documentation To: devel@lists.laptop.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=us-ascii; format=flowed In preparation for shipping an 8.2.0 build to manufacturing, we need to agree on release criteria. To that end, I have stubbed out rough ECO documentation for 8.2.0 at http://wiki.laptop.org/go/ECO/8.2.0 http://wiki.laptop.org/go/ECO/8.2.0/Checklist Please review these pages and offer suggestions on their talk pages so that I can fold your comments into the pages over the next week. So far, the most important changes I have made include: * Stating some of the technical documentation that future stable releases should include and making space for us to try creating that documentation for 8.2.0 at our leisure. * Stating the list of locales and keyboards which I believe must be minimally qualified for 8.2.0. See http://wiki.laptop.org/go/User:Mstone/Notes/Localization_1 for notes on what I mean by 'release X is qualified for locale Y'. * Created a test item for documentation signoff on the manual and activities signoff on the derivative builds. * Created final test items for release criteria including: 1 week of community testing all recent bugs triaged no 8.2.0 blockers release notes signoff What have I missed? Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Scratch Sensor Board needs access to TTYUSB*
Hi, Jim. Claudia Urrea would like to get the Scratch Sensor Board working on the XO. There was a minor bug in the Scratch serial port support, which I've now fixed. The fix will be in the next Scratch activity bundle. But the other problem is that the USB port is not readable and writable by default. I've posted some instructions at http://wiki.laptop.org/go/Scratch#Scratch_Sensor_Board (also attached below). It would much better if XO users did not need to do this Unix black magic. Could we get this rule (or equivalent) into the standard build? Thanks! -- John -- NOTE: There is a bug in Scratch v7 and earlier that keeps the sensor board from working. I've fixed the bug and am working on updating the Scratch activity. But once the new activity is ready, the following should get the sensor board working. To use the Scratch Sensor Board or Pico Sensor Board (http://scratch.wik.is/Support/Sensor_Boards ), you must add a file to the folder: /etc/udev/rules.d This file should contain the single line: KERNEL==ttyUSB*, MODE=0666 Adding this file allows Scratch to read and write data to the sensor board. You will need to make yourself root using the su command in order to add a file to that folder. -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] recover from broken yum transaction
On Fri, Sep 12, 2008 at 3:01 AM, Seth Vidal [EMAIL PROTECTED] wrote: - Is it safe to run at boot time via an init script? as long as the network is up, it should be. That is not very useful for us. I don't worry so much about the machine being killed in the 'download stuff' part, bit AFAIK that's not part of the 'transaction'. When yum-complete-transaction is called, I am expecting it to work with the RPMs it has, and ensure anything it was trying to do gets done... WRT networking, in places like Peru my rule of thumb is that 50% of the servers will _not_ have internet. Package installations / upgrades are very likely to happen by sending out USB keys with a bunch of RPMs, and a GPG-signed script that triggers the yum process. yum supports -C... can yum-complete-transaction support -C as well? - Is there an easy way to check for pending transactions? yum-complete-transaction checks for them itself Yes, though it's useful to be able to check that for logging/reporting... - Does it have useful exit codes indicating whether it's done anything? If the results codes are not good enough we can fix that easily enough. I am asking because checking the manpage and reading the source did not give me any hints as to exit codes. Neither does 'man yum' talk about exit codes except for the check-update command. So I wonder what's the expected behaviour WRT exit codes for yum? Is that different from `package-cleanup --problems` ? --problems reports a different set of things - package conflicts and unresolved deps. A dupe is not, implicitly, a problem. it CAN be, but it is not always. Right - that's lower priority for my use cases. Thanks for the hint. 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: Scratch Sensor Board needs access to TTYUSB*
thanks -- filed as trac #8434. this is an issue for any USB serial adapter, not just the Scratch sensor board. paul john wrote: Hi, Jim. Claudia Urrea would like to get the Scratch Sensor Board working on the XO. There was a minor bug in the Scratch serial port support, which I've now fixed. The fix will be in the next Scratch activity bundle. But the other problem is that the USB port is not readable and writable by default. I've posted some instructions at http://wiki.laptop.org/go/Scratch#Scratch_Sensor_Board (also attached below). It would much better if XO users did not need to do this Unix black magic. Could we get this rule (or equivalent) into the standard build? Thanks! -- John -- NOTE: There is a bug in Scratch v7 and earlier that keeps the sensor board from working. I've fixed the bug and am working on updating the Scratch activity. But once the new activity is ready, the following should get the sensor board working. To use the Scratch Sensor Board or Pico Sensor Board (http://scratch.wik.is/Support/Sensor_Boards ), you must add a file to the folder: /etc/udev/rules.d This file should contain the single line: KERNEL==ttyUSB*, MODE=0666 Adding this file allows Scratch to read and write data to the sensor board. You will need to make yourself root using the su command in order to add a file to that folder. -- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel =- paul fox, [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Getting a path to SUGAR_ACTVITY_ROOT
Hi, Scott.
I wonder if you could give me a bit of guidance. The Scratch file
dialogs have shortcuts for common folders on Windows and Mac, such as
the desktop and the user's documents folder. Most of these shortcuts
make no sense on the XO, but I thought that perhaps the documents
shortcut could go to $SUGAR_ACTVITY_ROOT/data. But my first attempt to
lookup that environment variable did not seem to work (although I have
not tried it in the context of your new wrapper; maybe it does work
now).
Anyhow, the code I wrote to do this is:
char *s = NULL;
path[0] = 0; // a zero-length path indicates failure
s = getenv(SUGAR_ACTVITY_ROOT);
if (s != NULL) {
strncat(path, s, maxPath);
strncat(path, /data, maxPath);
}
where path is a C string passed in by the client that is supposed to
get filled in with the path to documents folder.
I'm not used to programming in Unix. Does this look okay to you?
-- John
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Getting a path to SUGAR_ACTVITY_ROOT
Am 12.09.2008 um 00:08 schrieb John Maloney: s = getenv(SUGAR_ACTVITY_ROOT); Try inserting an I there ;) - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Scratch localization.
Hi, Erik. Unfortunately, the LocalePlugin does not solve this problem. Scratch must still read the Spanish translation file and re-layout the UI. I've forward you an email I sent to Scott about updating XO Scratch to the 1.3 release. -- John On Sep 11, 2008, at 5:35 PM, Erik Garrison wrote: John, In Peru the team is using the Scratch.ini file to set the language to spanish. There is a long delay between Scratch startup and the setting of the language, in which Scratch is in english. Does the LocalePlugin rectify this? What work needs to be done to update XO Scratch to Scratch 1.3? Erik On Thu, Sep 11, 2008 at 05:37:48PM -0400, John Maloney wrote: Hi, Erik. Apologies for the delay in responding. I was on vacation, then finishing the Scratch 1.3 release. Scratch remembers the last language set by the user in the Scratch.ini file. If that file is read-only, it fails gracefully. In older versions of Scratch (such as the current XO version), if no language was specified in the Scratch.ini file, Scratch would start up in English. However, it now uses the Squeak LocalePlugin to set the default language. So if the computer's locale is set to Spanish, Scratch should start up in Spanish. This feature has not yet been tested on Linux, but it does work on Mac OS and Windows. Many thanks to the Squeak folks for creating the LocalePlugin! So I think things may work fine as they are, once we've updated XO Scratch to the 1.3 release. (I'm working on that now, with help from Scott if he is willing). Scratch does not need to write persistent data to any other files. (It does need to write user projects somewhere, but Scott has solved that problem for now.) -- John On Aug 27, 2008, at 1:00 PM, Erik Garrison wrote: On Wed, Aug 27, 2008 at 06:54:18PM +0200, Bert Freudenberg wrote: Am 27.08.2008 um 18:38 schrieb C. Scott Ananian: Scratch appears to require manual editing of the Scratch.ini file in order to come up in a language other than English. Is there any way I can pass a command-line option in bin/scratch-activity to set the Language preference based on the value of $LANG? I'd prefer that we not have to ship a different Scratch bundle per-country. The Right Way to do it would be using the LocalePlugin, as Etoys does. If you need to patch up the bundle you could use the symlink trick again, the actual Scratch.ini would live in data/. Thus the language (and other settings possibly) that the user choses would persist. When running for the first time, the startup script could generate an initial Scratch.ini for the right language. What other persistent data beyond Scratch.ini does Scratch like to modify? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Getting a path to SUGAR_ACTVITY_ROOT
john -- scott's not in the office right now, so i'll take a stab
at this. your code snippet looks fine, except for the typo in
SUGAR_ACTVITY_ROOT. i hope that's all it is.
paul
john wrote:
Hi, Scott.
I wonder if you could give me a bit of guidance. The Scratch file
dialogs have shortcuts for common folders on Windows and Mac, such as
the desktop and the user's documents folder. Most of these shortcuts
make no sense on the XO, but I thought that perhaps the documents
shortcut could go to $SUGAR_ACTVITY_ROOT/data. But my first attempt to
lookup that environment variable did not seem to work (although I have
not tried it in the context of your new wrapper; maybe it does work
now).
Anyhow, the code I wrote to do this is:
char *s = NULL;
path[0] = 0; // a zero-length path indicates failure
s = getenv(SUGAR_ACTVITY_ROOT);
if (s != NULL) {
strncat(path, s, maxPath);
strncat(path, /data, maxPath);
}
where path is a C string passed in by the client that is supposed to
get filled in with the path to documents folder.
I'm not used to programming in Unix. Does this look okay to you?
-- John
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
=-
paul fox, [EMAIL PROTECTED]
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Rainbow-daemon dialog in Browse?
I've never seen a rainbow-daemon dialog before, what is it supposed to do? It doesn't work anyway, I filed a ticket with screenshot: http://dev.laptop.org/ticket/8435 - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: recognizing a previous connection
On Fri, Sep 12, 2008 at 9:33 AM, Greg Smith [EMAIL PROTECTED] wrote:
I'm not sure this dictates the right design, but I am aware of several
sites planning to use multiple access points.
One in the US will have ~40! and I believe that another in the US (NYC)
has many APs and a robust network.
One school in Rwanda has recently been funded to install 10 x APs.
Concept mixup! To clarify: these sites are going to have multiple APs
but most likely to have a single ESSID, or perhaps a low number of
ESSIDs (ie: one per building or one per floor).
When you have a large infra with many APs all using the same ESSID
('name'), network manager and the rest of the wifi machinery in the XO
will do the right thing (that is: use the one with strongest signal).
All this 'recognise a previous connection' thread is about recognising
the same ESSID. It should not be a problem.
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
New joyride build 2422
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build2422 Changes in build 2422 from build: 2421 Size delta: 0.00M -PolicyKit 0.8-2.fc9 +PolicyKit 0.8-3.fc9 --- Changes for PolicyKit 0.8-3.fc9 from 0.8-2.fc9 --- + Upstream patch to allow root to read auths -- 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: Libertas firmware on F9 for the XS
On Thu, Sep 11, 2008 at 6:25 PM, Martin Langhoff [EMAIL PROTECTED] wrote: On Fri, Sep 12, 2008 at 12:24 AM, Ricardo Carrano [EMAIL PROTECTED] wrote: Fedora 9 ships with a 2.6.25 kernel with a new libertas driver. Because of the changes implemented in this driver, you should use the latest firmware (22.p18). Please, never use 2.6.25 kernel with older firmware. Ok, however... The result is the instability you see. Sorry - I should have been clearer - the instability I was mentioning was pre-F9 upgrade. I haven't been running a F9 XS with AAs long enough... until yesterday it was reinstall/reboot/lather/rinse/repeat. In short, for everyone: Don't use anything different from 22.p14, 22.p17 or 22.p18. In kernel 2.6.25 use 22.p18. Right. It's not that simple however. Before switch to the versions you recommend I want to have the complete picture *including known bugs*. Can you help me with that? (That's what my earlier with my release manager hat on... hint was all about :-) ). In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? - There are odd bugs with WPA In fact, we are fixing timing issues that prevent the XO to connect to certain WPA access points under certain conditions (timing in 802.11 is influenced by external conditions too, hence the randomness and intermittent behavior and the need of using certain) There are other possible hot areas that should not be a problem for the XS (as suspend/resume interactions with wireless and problems in some XO's wlan modules (do not enumerate - still not clear to me if this is related to the firmware) If there are other bugs (and there is always corner cases) they are bellow my radar now. what else? Michails my best guess is that you'd be the owner for a current issues list like that. Is that correct? What known bugs do I buy into when I follow Ricardo's advise? 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: Scratch Sensor Board needs access to TTYUSB*
Hello John, On Fri, Sep 12, 2008 at 7:20 AM, John Maloney [EMAIL PROTECTED] wrote: Claudia Urrea would like to get the Scratch Sensor Board working on the XO. Feel free to look at the code for my itch activity, which just displays the values from the scratch board. It doesn't have code to fix the issue you were having, but perhaps it will help for testing. http://dev.laptop.org/git?p=users/joel/itch-activity;a=summary I haven't tested it on an XO for a while, so ymmv. Joel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 1:49 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). - There are odd bugs with WPA In fact, we are fixing timing issues that prevent the XO to connect to certain WPA access points under certain conditions (timing in 802.11 is influenced by external conditions too, hence the randomness and intermittent behavior and the need of using certain) Offtopic datapoint: here in my NZ office all signals are WPA encoded, from various APs I don't control (but can use). Certain is unfortunately around 80-90% of the cases. There are other possible hot areas that should not be a problem for the XS (as suspend/resume interactions with wireless and problems in some XO's wlan modules (do not enumerate - still not clear to me if this is related to the firmware) If there are other bugs (and there is always corner cases) they are bellow my radar now. Is trac being used reasonably to track firmware issues? Checked earlier today - 'component = wireless' and 'summary contains libertas' kinda sorta give an overview. False matches and untriaged issues abound so it doesn't seem like anyone's looking at that view of the data. (Me, I only sleep when by this trac view tells me to: https://dev.laptop.org/query?group=statusmilestone=xs-0.5 ) Perhaps Michails has a spreadsheet or wikipage hiding somewhere? ;-) You guys have been doing a ton of development (both features, bugfixes) dealing with several moving parts -- notes of what works where and what clearly barfs must be collected somewhere. 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: Libertas firmware on F9 for the XS
Martin, I really miss the point of your tirade. Our advice is to use 5.110.22.p18 M. Martin Langhoff [EMAIL PROTECTED] 09/11/2008 10:15 PM To Ricardo Carrano [EMAIL PROTECTED] cc Michail Bletsas [EMAIL PROTECTED], OLPC Devel devel@lists.laptop.org, XS Devel [EMAIL PROTECTED] Subject Re: Libertas firmware on F9 for the XS On Fri, Sep 12, 2008 at 1:49 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). - There are odd bugs with WPA In fact, we are fixing timing issues that prevent the XO to connect to certain WPA access points under certain conditions (timing in 802.11 is influenced by external conditions too, hence the randomness and intermittent behavior and the need of using certain) Offtopic datapoint: here in my NZ office all signals are WPA encoded, from various APs I don't control (but can use). Certain is unfortunately around 80-90% of the cases. There are other possible hot areas that should not be a problem for the XS (as suspend/resume interactions with wireless and problems in some XO's wlan modules (do not enumerate - still not clear to me if this is related to the firmware) If there are other bugs (and there is always corner cases) they are bellow my radar now. Is trac being used reasonably to track firmware issues? Checked earlier today - 'component = wireless' and 'summary contains libertas' kinda sorta give an overview. False matches and untriaged issues abound so it doesn't seem like anyone's looking at that view of the data. (Me, I only sleep when by this trac view tells me to: https://dev.laptop.org/query?group=statusmilestone=xs-0.5 ) Perhaps Michails has a spreadsheet or wikipage hiding somewhere? ;-) You guys have been doing a ton of development (both features, bugfixes) dealing with several moving parts -- notes of what works where and what clearly barfs must be collected somewhere. 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: Scratch Sensor Board needs access to TTYUSB*
On Thu, Sep 11, 2008 at 5:50 PM, John Maloney [EMAIL PROTECTED] wrote: To use the Scratch Sensor Board or Pico Sensor Board (http://scratch.wik.is/Support/Sensor_Boards), you must add a file to the folder: /etc/udev/rules.d This file should contain the single line: KERNEL==ttyUSB*, MODE=0666 Adding this file allows Scratch to read and write data to the sensor board. You will need to make yourself root using the su command in order to add a file to that folder. Isn't the traditional thing to have the tty* devices owned by the serial group (uucp or dialout group if you're a real old-timer) and then set certain users to be members of that group? It seems like you really want scratch's UID to be a member of the 'serial' group. Michael? --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Scratch localization.
On Thu, Sep 11, 2008 at 5:37 PM, John Maloney [EMAIL PROTECTED] wrote: So I think things may work fine as they are, once we've updated XO Scratch to the 1.3 release. (I'm working on that now, with help from Scott if he is willing). I'm willing, but I seem to have missed your first email re this. Could you resend it to me, too? Thanks! --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 3:49 PM, Michail Bletsas [EMAIL PROTECTED] wrote: Our advice is to use 5.110.22.p18 Sorry if I am sounding difficult -- I am just trying to understand the upsides and downsides of 22.p18 Clearly, it fixes some bugs we knew about and we already know it introduces others. I assume someone is keeping track of that info -- I don't enjoy asking these questions, it's just something I need. Are you or anyone else tracking the issues opened/fixed? 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: Libertas firmware on F9 for the XS
Clearly, it fixes some bugs we knew about and we already know it introduces others. I assume someone is keeping track of that info -- What bugs does it introduce? M___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
On Sep 12 2008, at 14:12, Martin Langhoff was caught saying: On Fri, Sep 12, 2008 at 1:49 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). Some clarifcation. The issue is not the firmware, but the kernel driver itself as there are pieces from the 2.6.22 driver that never made it upstream. My suggestion is to run the same driver and firmware on both XS and XO so we do not have multiple variables to deal with. ~Deepak -- Deepak Saxena - Kernel Developer - [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 4:33 PM, Michail Bletsas [EMAIL PROTECTED] wrote: Clearly, it fixes some bugs we knew about and we already know it introduces others. I assume someone is keeping track of that info -- What bugs does it introduce? That is the info I am asking -- without being involved in the Libertas efforts I know of a few issues as discussed in this thread: - Deepak mentions it has an incompatibility with the F9 stock kernel wrt to multicast RX (#7319). - WPA timing issues which have been introduced relatively recently, though I don't know exactly when. I am assuming you do. - There is an old issue (seen with the 20.49p firmware and oldish driver) with the device getting locked up, which gets solved power-cycling the libertas device. Is it fixed in recent drivers / firmwares? Which ones? important part of email - feel free to ignore the rest I don't want to argue with anyone -- let's focus on the info I need. I am looking for a list that has the 3 items above with some status information (version it appeared / version fixed / etc) _plus_ others that I don't know about. This list should come from the team working on the libertas firmware and driver. Where is that list? Who has it? Who coordinates bugtracking for the libertas stuff? Can't be that much of a mistery. /important Anyway - this is a very odd conversation to be having. I'll blame it on it being late night in EST TZ, and hope for more info tomorrow. g'night! 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: Libertas firmware on F9 for the XS
Martin Langhoff [EMAIL PROTECTED] wrote on 09/12/2008 12:50:50 AM: What bugs does it introduce? That is the info I am asking -- without being involved in the Libertas efforts I know of a few issues as discussed in this thread: - Deepak mentions it has an incompatibility with the F9 stock kernel wrt to multicast RX (#7319). We do no test with the stock kernel. - WPA timing issues which have been introduced relatively recently, though I don't know exactly when. I am assuming you do. Driver issue (check #7825) - There is an old issue (seen with the 20.49p firmware and oldish driver) with the device getting locked up, which gets solved power-cycling the libertas device. Is it fixed in recent drivers / firmwares? Which ones? Many things have changed since 20.p49 Where is that list? Who has it? Who coordinates bugtracking for the libertas stuff? Can't be that much of a mistery. /important If that's a mystery to you after so many months of working for OLPC, I really don't want to spoil the suspense... ;-) M.___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 4:42 PM, Deepak Saxena [EMAIL PROTECTED] wrote: On Sep 12 2008, at 14:12, Martin Langhoff was caught saying: On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). Some clarifcation. The issue is not the firmware, but the kernel driver itself as there are pieces from the 2.6.22 driver that never made it upstream. Yup it's an incompatibility between the stock F9 kernel and the recent firmwares. My suggestion is to run the same driver and firmware on both XS and XO so we do not have multiple variables to deal with. I generally agree, but unfortunately, that adds significant work (of carrying custom-compiled drivers) to a tiny team of 2. We don't have a kernel maintainer in the XS team :-/ That is why I need good solid reasons to move off the stock F9 stuff. With an already overstretched team I cannot get into Libertas testing or custom kernels... unless I can point to specific bugs. If I have specific bugs to look at, then it can be triaged with the rest of the work I have on the table... 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: Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 5:10 PM, Michail Bletsas [EMAIL PROTECTED] wrote: Where is that list? Who has it? Who coordinates bugtracking for the libertas stuff? Can't be that much of a mistery. /important If that's a mystery to you after so many months of working for OLPC, I really don't want to spoil the suspense... ;-) I'm appreciate the humour. Now this thread has 20 msgs already, and I have a release to work towards. Straight answers please...? - There is an old issue (seen with the 20.49p firmware and oldish driver) with the device getting locked up, which gets solved power-cycling the libertas device. Is it fixed in recent drivers / firmwares? Which ones? Many things have changed since 20.p49 I am sure they have. Now, from the team that has been working on libertas day in and day out for the last N months... does it still reset overnight? Yes, no, dunno? 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] Patch fixing a problem with --kickstart-include
Martin Langhoff wrote: By naming the kickstart file as ks.cfg, anaconda would _always_ take it, regardless of kernel boot options. This is not what was expected - it is safer to give it a different name, and then use the boot menu item to select it. So what you're saying is that anaconda picks up the kickstart file and runs away with it, even when it has not been told it should do so? It probably shouldn't do that... but I'll have to check with the anaconda guys to see if it's maybe an intended change. Kind regards, Jeroen van Meeuwen -kanarip ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Libertas firmware on F9 for the XS
Hi Martin, On 9/9/08, Martin Langhoff [EMAIL PROTECTED] wrote: On Wed, Sep 10, 2008 at 1:40 PM, Michail Bletsas [EMAIL PROTECTED] wrote: - F9 libertas-usb8388-firmware-5.111.20.p49-1 - F9/XO (8.2-759) libertas-usb8388-firmware-5.111.22.p18-1 You are definitely better off using 5.110.22.p18 With my release-manager hat on: can I have more info to help me decide? I just checked and the firmware on the last F7-based build was 20.p49, same as F9, so staying with it means I am dealing with a known quantity... - is there a good changelog between 20.p49 and 22.p18 ? - with 20.p49 the AA dies overnight, does 22.p18 fix this? - any notes from stability testing done with 22.p18? cheers, The release notes can be acessed here: http://www.laptop.org/teamwiki/index.php/Tech:FW_8388_RELEASE_NOTES 22.p18 is the current version in joyride. Anything older than 22.p14 is not recommended at all (quite the opposite). Cheers! Ricardo ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Creating a spin - any mechanisms around $product-release, $product-release-notes, $product-logos packages...?
On Wed, 2008-09-10 at 21:42 +1200, Martin Langhoff wrote: My key question is: will anything in the Fedora machinery (anaconda, rpm, yum) be looking for a magic product name, and then try to use it to request $product-release? Nothing that I know of Jeremy ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Libertas firmware on F9 for the XS
On Sep 10 2008, at 11:04, Martin Langhoff was caught saying: Now that I have a F9-based XS build, I've dropped the custom-compiled driver and the firmware for Libertas, hoping to use the stock standard F9. But that might be a bit optimistic :-) After a quick check it looks like the XO images are shipping newer Libertas firmware as you can see below. The XO builds also have a few problems with the Firmware too, so I'm not entirely sure what to do... - F9 libertas-usb8388-firmware-5.111.20.p49-1 - F9/XO (8.2-759) libertas-usb8388-firmware-5.111.22.p18-1 The main question for Libertas experts from the POV of the XS is: what firmware is most stable? On the XS power consumption and sleep are not high priority. Stability and performance over long periods of time is. Also - should I look at replacing / recompiling the driver that F9 ships? (Hoping not...) If you say yes, be aware it is a major maintenance hassle for the already short-handed XS team, so I'll want to know what benefits it brings. I think for both FW and kernel driver, it depends on what features you need. For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). Firmware wise, .22 includes a fix for #7973. ~Deepak -- Deepak Saxena - Kernel Developer - [EMAIL PROTECTED] ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] recover from broken yum transaction
Trying rpm -Va, I am getting lots of these lines S.?./usr/bin/kblankscrn.kss S.?./usr/bin/kcminit S.?./usr/bin/kcminit_startup Basically, the size has changed, and the md5 check cannot be performed ?! I understand this is due to prelink, but that sux ! This effectively kills the rpm -V functionality. Is it not possible to prelink binaries on the server before wrapping them into rpms ? Any suggested solution around this ? On Thu, Sep 11, 2008 at 7:42 AM, Martin Langhoff [EMAIL PROTECTED]wrote: On Thu, Sep 11, 2008 at 3:50 PM, Seth Vidal [EMAIL PROTECTED] wrote: When this happens you should run: yum-complete-transaction Interesting toy! I think you mentioned it at Fudcon Boston and I hadn't been able to recall the right name. Thinking of using it in the use case of the school server (very unreliable power, no sysadmins available, 100% unattended updates) - - Is it safe to run at boot time via an init script? - Is there an easy way to check for pending transactions? - Does it have useful exit codes indicating whether it's done anything? I'd recommend package-cleanup --cleandupes Another good tool to add to the arsenal. then run: rpm -Va and look for problems in files in /usr/lib /lib/ /boot, and all of the bin dirs. Is that different from `package-cleanup --problems` ? 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 -- fedora-devel-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/fedora-devel-list ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] recover from broken yum transaction
On Thu, 2008-09-11 at 09:53 +0200, Ahmed Kamal wrote: Trying rpm -Va, I am getting lots of these lines S.?./usr/bin/kblankscrn.kss S.?./usr/bin/kcminit S.?./usr/bin/kcminit_startup Basically, the size has changed, and the md5 check cannot be performed ?! I understand this is due to prelink, but that sux ! This effectively kills the rpm -V functionality. Is it not possible to prelink binaries on the server before wrapping them into rpms ? Any suggested solution around this ? You might consider reinstalling kdebase-workspace yum reinstall kdebase-workspace see if that works for you. -sv ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] recover from broken yum transaction
Ahmed Kamal writes: Trying rpm -Va, I am getting lots of these lines S.?./usr/bin/kblankscrn.kss S.?./usr/bin/kcminit S.?./usr/bin/kcminit_startup Basically, the size has changed, and the md5 check cannot be performed ?! I understand this is due to prelink, but that sux ! This effectively kills the rpm -V functionality. Is it not possible to prelink binaries on the server before wrapping them into rpms ? Any suggested solution around this ? If you are getting these errors, it is not due to prelinking, but due to files having been updated but not properly registered with RPM. The suggestion to reinstall kdebase-workspace (and other packages which are reporting size changes) is a probable solution. rpm -V uses prelink --verify to check binaries and shared libraries that might be affected by prelinking: It is explained in the manpage for prelink -y --verify Verifies a prelinked binary or library. This option can be used only on a single binary or library. It first applies an --undo operation on the file, then prelinks just that file again and compares this with the original file. If both are identical, it prints the file after --undo operation on standard output and exits with zero status. Otherwise it exits with error status. Thus if --verify operation returns zero exit status and its standard output is equal to the content of the binary or library before prelinking, you can be sure that nobody modified the binaries or libraries after prelinking. Similarly with message digests and checksums (unless you trigger the improbable case of modified file and original file having the same digest or checksum). @alex -- mailto:[EMAIL PROTECTED] ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Revisor / yum oddity with package conflicts...
On Fri, Sep 12, 2008 at 3:11 AM, Jeroen van Meeuwen [EMAIL PROTECTED] wrote: Seth Vidal wrote: isn't fedora-logos being pulled in in @core in comps? that's why kickstart is pulling it in, I think. Very true, notting has just closed #456882, having removed fedora-logos from @core, but that is rawhide only. In help of Martin, add exclude=fedora-logos to the YUM configuration file for the model you are using (probably located in /etc/revisor/conf.d/). Jeroen, Seth, thanks a ton for the hints. Happy to see that it's getting smoother for F10, and extra happy that I have a workaround. Now, on to the 200 more things I got to do to get the school server out... 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] PostgreSQL mgmt on Fedora: pg_cluster-like tools?
I'm getting familiar with the Fedora tools around Pg, and wondering whether there is anything similar to the pg_cluster stuff that's available in Debian/Ubuntu. So far I've looked at the postgresql-* packages and rhdb-utils -- nothing I've found seems to fill that space. Is there a package I am missing, or a workflow that achieves the same goals? My goals: - Run Pg with custom options - I see the sysconfig/pgsql/$NAME trick in the init script, handy! - Major Pg upgrades will have to run 100% unattended, with a sane failover, so: install the new version of Pg, attempt a pg_dump|pg_restore data migration and only switch over if it was successful. the pg_cluster scripts and the wrappers around psql and friends simplify a lot of error-prone stuff when working in these upgrade scenarios. How do I handle it in Fedora-land? 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
Re: [Server-devel] Libertas firmware on F9 for the XS
On Thu, Sep 11, 2008 at 6:25 PM, Martin Langhoff [EMAIL PROTECTED] wrote: On Fri, Sep 12, 2008 at 12:24 AM, Ricardo Carrano [EMAIL PROTECTED] wrote: Fedora 9 ships with a 2.6.25 kernel with a new libertas driver. Because of the changes implemented in this driver, you should use the latest firmware (22.p18). Please, never use 2.6.25 kernel with older firmware. Ok, however... The result is the instability you see. Sorry - I should have been clearer - the instability I was mentioning was pre-F9 upgrade. I haven't been running a F9 XS with AAs long enough... until yesterday it was reinstall/reboot/lather/rinse/repeat. In short, for everyone: Don't use anything different from 22.p14, 22.p17 or 22.p18. In kernel 2.6.25 use 22.p18. Right. It's not that simple however. Before switch to the versions you recommend I want to have the complete picture *including known bugs*. Can you help me with that? (That's what my earlier with my release manager hat on... hint was all about :-) ). In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? - There are odd bugs with WPA In fact, we are fixing timing issues that prevent the XO to connect to certain WPA access points under certain conditions (timing in 802.11 is influenced by external conditions too, hence the randomness and intermittent behavior and the need of using certain) There are other possible hot areas that should not be a problem for the XS (as suspend/resume interactions with wireless and problems in some XO's wlan modules (do not enumerate - still not clear to me if this is related to the firmware) If there are other bugs (and there is always corner cases) they are bellow my radar now. what else? Michails my best guess is that you'd be the owner for a current issues list like that. Is that correct? What known bugs do I buy into when I follow Ricardo's advise? 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
Re: [Server-devel] recover from broken yum transaction
On Fri, 2008-09-12 at 09:54 +1200, Martin Langhoff wrote: That is not very useful for us. I don't worry so much about the machine being killed in the 'download stuff' part, bit AFAIK that's not part of the 'transaction'. When yum-complete-transaction is called, I am expecting it to work with the RPMs it has, and ensure anything it was trying to do gets done... The transaction file is written out after the pkgs are downloaded, so the transaction should complete just fine if the system hasn't changed state dramatically. WRT networking, in places like Peru my rule of thumb is that 50% of the servers will _not_ have internet. Package installations / upgrades are very likely to happen by sending out USB keys with a bunch of RPMs, and a GPG-signed script that triggers the yum process. Then that won't be an issue at all, you'll have a local repo on the usb key which yum can access. It won't even need -C b/c it will have connectivity to the local file:/// based repo. yum supports -C... can yum-complete-transaction support -C as well? it already does. - try it: yum-complete-transaction --help - Is there an easy way to check for pending transactions? yum-complete-transaction checks for them itself Yes, though it's useful to be able to check that for logging/reporting... You can check with one call: import yum.misc yum.misc.find_unfinished_transactions() if it returns a non-empty list then you have unfinished transactions. - Does it have useful exit codes indicating whether it's done anything? If the results codes are not good enough we can fix that easily enough. I am asking because checking the manpage and reading the source did not give me any hints as to exit codes. Neither does 'man yum' talk about exit codes except for the check-update command. at this point yum should be returning 0 for any non-erroring exit and 1 for any error condition. Including rpm scriptlet failures. That should also be true for yum-complete-transaction -sv ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] PostgreSQL mgmt on Fedora: pg_cluster-like tools?
On Fri, Sep 12, 2008 at 12:38 PM, Tom Lane [EMAIL PROTECTED] wrote: Hm, well, maybe I haven't been paying enough attention. I remember the cursing ;-) but not whether they'd gotten it sorted adequately. Cursing? When!? :-) -- anyway, from the don't do this, dummy department, a tiny patch, titled... initdb fails if the logfile is set to be inside the data directory. 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 pginit.patch Description: Binary data ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Libertas firmware on F9 for the XS
Martin, I really miss the point of your tirade. Our advice is to use 5.110.22.p18 M. Martin Langhoff [EMAIL PROTECTED] 09/11/2008 10:15 PM To Ricardo Carrano [EMAIL PROTECTED] cc Michail Bletsas [EMAIL PROTECTED], OLPC Devel [EMAIL PROTECTED], XS Devel server-devel@lists.laptop.org Subject Re: Libertas firmware on F9 for the XS On Fri, Sep 12, 2008 at 1:49 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). - There are odd bugs with WPA In fact, we are fixing timing issues that prevent the XO to connect to certain WPA access points under certain conditions (timing in 802.11 is influenced by external conditions too, hence the randomness and intermittent behavior and the need of using certain) Offtopic datapoint: here in my NZ office all signals are WPA encoded, from various APs I don't control (but can use). Certain is unfortunately around 80-90% of the cases. There are other possible hot areas that should not be a problem for the XS (as suspend/resume interactions with wireless and problems in some XO's wlan modules (do not enumerate - still not clear to me if this is related to the firmware) If there are other bugs (and there is always corner cases) they are bellow my radar now. Is trac being used reasonably to track firmware issues? Checked earlier today - 'component = wireless' and 'summary contains libertas' kinda sorta give an overview. False matches and untriaged issues abound so it doesn't seem like anyone's looking at that view of the data. (Me, I only sleep when by this trac view tells me to: https://dev.laptop.org/query?group=statusmilestone=xs-0.5 ) Perhaps Michails has a spreadsheet or wikipage hiding somewhere? ;-) You guys have been doing a ton of development (both features, bugfixes) dealing with several moving parts -- notes of what works where and what clearly barfs must be collected somewhere. 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
Re: [Server-devel] Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 3:49 PM, Michail Bletsas [EMAIL PROTECTED] wrote: Our advice is to use 5.110.22.p18 Sorry if I am sounding difficult -- I am just trying to understand the upsides and downsides of 22.p18 Clearly, it fixes some bugs we knew about and we already know it introduces others. I assume someone is keeping track of that info -- I don't enjoy asking these questions, it's just something I need. Are you or anyone else tracking the issues opened/fixed? m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Libertas firmware on F9 for the XS
On Sep 12 2008, at 14:12, Martin Langhoff was caught saying: On Fri, Sep 12, 2008 at 1:49 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: In short, I need an overview of what works and what doesn't with F9 stock kernel and 22.p18. So far: - Deepak mentions issues w/multicast I'm not sure exactly of what we're talking about here. Could you or Deepak clarify what are these issues? On this same thread, yesterday... Deepak Saxena [EMAIL PROTECTED] wrote: For the XO 8.2 kernel we had to pull forward some patches from the stable 2.6.22 branch that are not upstream to get multicast RX to work properly (#7319). Some clarifcation. The issue is not the firmware, but the kernel driver itself as there are pieces from the 2.6.22 driver that never made it upstream. My suggestion is to run the same driver and firmware on both XS and XO so we do not have multiple variables to deal with. ~Deepak -- Deepak Saxena - Kernel Developer - [EMAIL PROTECTED] ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Libertas firmware on F9 for the XS
On Fri, Sep 12, 2008 at 5:10 PM, Michail Bletsas [EMAIL PROTECTED] wrote: Where is that list? Who has it? Who coordinates bugtracking for the libertas stuff? Can't be that much of a mistery. /important If that's a mystery to you after so many months of working for OLPC, I really don't want to spoil the suspense... ;-) I'm appreciate the humour. Now this thread has 20 msgs already, and I have a release to work towards. Straight answers please...? - There is an old issue (seen with the 20.49p firmware and oldish driver) with the device getting locked up, which gets solved power-cycling the libertas device. Is it fixed in recent drivers / firmwares? Which ones? Many things have changed since 20.p49 I am sure they have. Now, from the team that has been working on libertas day in and day out for the last N months... does it still reset overnight? Yes, no, dunno? 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
Re: [Server-devel] PostgreSQL mgmt on Fedora: pg_cluster-like tools?
2008/9/12 Devrim GÜNDÜZ [EMAIL PROTECTED]: I am *very* against this one. It is not packager's job to run dump/reload: I agree with you in a normal rpm package. I am working to some very special requirements :-) * You may never be sure that it will work. We had this issue in 8.3 for example. Yes, I've overseen many 7.2/7.3/7.4/8.0/8.1/8.2 migrations and understand the pitfalls fairly well. * Upstream never ever gives such a guarantee that all apps will work on every PostgreSQL version. For example, some casts were removed in 8.3. Having been once the maintainer of the Pg compat layer in Moodle, I also have first-hand experience with this. When the casts removal was mentioned in pg-devel, who was there asking about backwards compat? ;-) So dumping/restoring should be a DBA work. So switch over if it was successful is really a bad idea, and *will* break things. We'll have ~5K school servers in rural schools just in Peru, a team of perhaps 10 sysadmins for them, most of the servers disconnected. OTOH, we know what apps talk to Pg, and we'll have tested them thoroughly. The failures could come from data that breaks during migration - so if an 8.3 to 8.4 migration fails to complete we keep running on Pg 8.3, and write a log. (This is assuming that 8.4 has improvements worth the migration risks. We'll probably defer until a version of Pg has significant benefits to actually do this...) quite a challenge - :-) 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
