Re: [Sugar-devel] New SoaS-on-XO-1 build done: soasxo57
On Fri, Aug 21, 2009 at 12:19:35PM +0530, Joshua N Pritikin wrote:
I downloaded soasxo57.tree.tar.lzma
This image does not have /boot/vmlinuz or /vmlinuz. There is only
/boot/vmlinuz-2.6.30.5-28.rc2.fc11.i586
Fixed in soasxo58. Two kernel packages are being installed by
kickstart/anaconda: OLPC's and stock Fedora's. OLPC's olpc-bootanim
does not provide /sbin/plymouth, which some standard dracut module(s)
require. The stock kernel is installed second, so when its %post
scripts try to create /boot/{vmlinuz,initrd.img}, they fail. The
/boot symlinks are left nonexistent.
For now I have worked around this by installing the OLPC kernel
_again_ in kickstart/anaconda's %post, but that's a nasty kludge.
Also, there is no initrd or olpcrd (that I could find).
Fixed in soasxo58 - same problem as above.
Thanks for trying it out. I would like to rig up a virtual machine
and some automated tests so that you don't have to find this out the
hard way.
Martin
pgpK3JWPnHpHJ.pgp
Description: PGP signature
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1 users in Uy
2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Yes, though if we manage to get the logs dir of a machine just after the DS was lost, there's lots of chances we are going to be able to The ones on the ramdisk? :-( m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1 users in Uy
On Fri, Aug 21, 2009 at 10:36:44AM +0200, Martin Langhoff wrote: 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: 2009/8/21 Martin Langhoff martin.langh...@gmail.com: 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Yes, though if we manage to get the logs dir of a machine just after the DS was lost, there's lots of chances we are going to be able to The ones on the ramdisk? :-( Is ~/.sugar/default/logs in the ramdisk? This would be the first time I hear about it. OLPC's builds (at least the F7/F9 based series) I understood they were on a ramdisk. Looking at it now, however, it seems that they aren't -- but a restart of X clears it out anyway. So by the time the problem is _seen_, *poof*, logs are gone. You sure that ~/.sugar/default/logs doesn't just get renamed to ~/.sugar/default/logs/N? That's what happens now, but perhaps not on older builds? m Martin pgp5v7mSfw7cF.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1 users in Uy
2009/8/21 Martin Langhoff martin.langh...@gmail.com: 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: 2009/8/21 Martin Langhoff martin.langh...@gmail.com: 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Yes, though if we manage to get the logs dir of a machine just after the DS was lost, there's lots of chances we are going to be able to The ones on the ramdisk? :-( Is ~/.sugar/default/logs in the ramdisk? This would be the first time I hear about it. OLPC's builds (at least the F7/F9 based series) I understood they were on a ramdisk. Looking at it now, however, it seems that they aren't -- but a restart of X clears it out anyway. So by the time the problem is _seen_, *poof*, logs are gone. Maybe something in the sugar startup clears it out. Dunno. Doesn't seem to be olpc-configure. Should be kept in a subdir in there, from: http://git.sugarlabs.org/projects/sugar/repos/mainline/blobs/cbd0509f4bcfe1b3e52f8898b1cb83d522337ab8/src/logsmanager.py#line25 But anyway, the failure to read the DS would be in the first boot where the journal appears empty, not in the boot where the DS index got corrupted. Regards, Tomeu m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1 users in Uy
2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Should be kept in a subdir in there, from: Damn! I wish I had known about this! So 3 old dirs are kept - excellent. But anyway, the failure to read the DS would be in the first boot where the journal appears empty, not in the boot where the DS index got corrupted. Well, if you can get your hands on the 'corrupt' datastore dir, doesn't it also contain the xapian DB? Just renaming it into 'datastore' should re-produce the error... Maybe not? m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1 users in Uy
2009/8/21 Martin Langhoff martin.langh...@gmail.com: 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Should be kept in a subdir in there, from: Damn! I wish I had known about this! So 3 old dirs are kept - excellent. But anyway, the failure to read the DS would be in the first boot where the journal appears empty, not in the boot where the DS index got corrupted. Well, if you can get your hands on the 'corrupt' datastore dir, doesn't it also contain the xapian DB? Just renaming it into 'datastore' should re-produce the error... Maybe not? I think it should if we know the exact build image on which to place it. So I would say whatever is easier for people to provide. Regards, Tomeu m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] trac problems
Hi, is anybody still having problems with dev.sugarlabs.org? Thanks, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1
On Thu, Aug 20, 2009 at 05:13:42PM -0500, Jim Simmons wrote: The way to reproduce the problem is to run the Sugar environment in Xephyr (sugar-emulator). Do some stuff, then instead of shutting down cleanly click on the close button on the Xephyr window. This happened a lot to me as well. The reason is that with an unclean shutdown (but no power cycle) some stuff, especially the data store, will keep running, but be inaccesible to the new session. So DBus starts a new data store process which can't lock the index... It will only happen if you do an unclean restart of X; a reboot / power cycle isn't a problem. CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] trac problems
It's slow (as usual), but it works for me. 2009/8/21 Tomeu Vizoso to...@sugarlabs.org: Hi, is anybody still having problems with dev.sugarlabs.org? Thanks, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] F11 for XO1 - Fonts
2009/8/18 Tomeu Vizoso to...@sugarlabs.org: On Mon, Aug 17, 2009 at 12:17, Daniel Draked...@laptop.org wrote: 2009/8/7 Tomeu Vizoso to...@sugarlabs.org: But not all text is rendered with that default font size. Do you have examples? No, but I find it highly unlikely that all activities are using sugar.graphics.style.FONT_NORMAL. then those activities are probably a bit naughty :) In most cases they should be basing their font selections around what sugar suggests, as this will now reflect the desires of the user. My ideas so-far including my thoughts on the above issue are here: http://wiki.sugarlabs.org/go/Features/Font_configuration Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFH - Journal corruption reports fom 8.2.1
On Fri, Aug 21, 2009 at 11:08, Sascha Silbesascha-ml-ui-sugar-de...@silbe.org wrote: On Thu, Aug 20, 2009 at 05:13:42PM -0500, Jim Simmons wrote: The way to reproduce the problem is to run the Sugar environment in Xephyr (sugar-emulator). Do some stuff, then instead of shutting down cleanly click on the close button on the Xephyr window. This happened a lot to me as well. The reason is that with an unclean shutdown (but no power cycle) some stuff, especially the data store, will keep running, but be inaccesible to the new session. So DBus starts a new data store process which can't lock the index... It will only happen if you do an unclean restart of X; a reboot / power cycle isn't a problem. That's interesting information, the dbus session daemon should finish when sugar-session ends, and sugar-session should be terminated by the lost X connection. The DS and the other DBus services like the PS, telepathy-*, etc should terminate when the dbus daemon dies. Would be good to have a ticket that entices someone to dig deeper and see why things aren't like they are supposed to be. Thanks, Tomeu CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEcBAEBAgAGBQJKjmP2AAoJELpz82VMF3DaYsgH/j/LYhJ7lOWrVreA3zImkh8w +BAT94io4D1Y/S9QE63CF8FgBJhQvpOeY42lc72TKU19365qIrcJ5YEekBGVkHYj /bi7E3kCUJebZIYHdFhpjGA86UdKdPQLPjmtlP6kRSvc8Ce2BOMH23ZS6vrAItib f71BIndBg7HmC/0d9jblGAr6I9NNzfp+TBSucGZ/2YNjVOXTsIC0O1CgUIkXPVAN jV/vS06lBHQPddNa/Xj1ZmZ1+/IP9jlVkPyadWWY+ssDupTGs62YGhZuu31DAJl2 zm8vgG6D4KxQsXTA+Qlxj+sx3K56uA9s0gAhttYfmgH/dqeGmPjTUMPuuN97jh0= =MK24 -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Accelerators: make Journal 'F5'
Hi, finally I pushed today the accelerators for the views. This means that the palettes of the zoom options in the frame show now: Neighbrhood F1 etc (see screenshot below). As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. Regards, Simon attachment: zoom.png___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
Hi Simon--that seems to make sense. Any feedback on the comps I sent? Let me know if there are any questions... I'll be traveling these next few days, but will be checking email occasionally. Thanks, Christian On Fri, Aug 21, 2009 at 5:58 AM, Simon Schampijer si...@schampijer.dewrote: Hi, finally I pushed today the accelerators for the views. This means that the palettes of the zoom options in the frame show now: Neighbrhood F1 etc (see screenshot below). As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. Regards, Simon -- anyth...@christianmarcschmidt.com http://www.christianmarcschmidt.com 917/ 575 0013 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
On Fri, Aug 21, 2009 at 11:58:05AM +0200, Simon Schampijer wrote: As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. On regular keyboards this makes sense, but on the XO-1 F5 is part of the slider keys. OTOH the keyboard mapping issue doesn't seem to be fixed in any distribution yet (how does SoaS handle it, BTW?), so not sure it will still be mapped this way in the future. CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
On Fri, Aug 21, 2009 at 12:17:25PM +0200, Sascha Silbe wrote: does SoaS [have the Search key mapped to the Journal]? F11-on-XO1 and SoaS-on-XO-1 have Journal mapped to the Search key correctly. CU Sascha Martin pgp9QVfPASnwV.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
On Fri, Aug 21, 2009 at 11:28:35AM +0100, Martin Dengler wrote: F11-on-XO1 and SoaS-on-XO-1 have Journal mapped to the Search key correctly. How do you set the key mapping? Which key mapping file do you use? CU Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: Digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] New SoaS-on-XO-1 build done: soasxo58
A new SoaS-on-XO-1 build soasxo58 is available. NAND size / change in size: 640.38M / +11144K ext3 size / change in size: 1305.54M / +16496K Package changes: --- soasxo57.tree.packages.txt 2009-08-20 15:20:38.0 + +++ soasxo58.tree.packages.txt 2009-08-20 22:18:47.0 + bind-utils-9.6.1-4.P1.fc11.i586 +binutils-2.19.51.0.14-1.fc11.i586 +bitfrost-1.0.1-1.fc11.i586 bitmap-fonts-0.3-7.fc11.noarch bootchart-0.9-10.fc11.i586 +bridge-utils-1.2-7.fc11.i586 bzip2-1.0.5-5.fc11.i586 dosfstools-3.0.1-4.fc11.i586 +dracut-0.8-1.fc11.i586 +dracut-modules-olpc-0.2.1-1.fc11.i586 dump-0.4-0.1.b42.fc11.i586 kbd-1.15-7.fc11.i586 -kernel-2.6.30.5-28.rc2.fc11.i586 -kernel-firmware-2.6.30.5-28.rc2.fc11.noarch +kernel-2.6.30_xo1-20090808.1740.1.olpc.a817f86.i586 +kernel-PAE-2.6.29.6-217.2.8.fc11.i686 +kernel-firmware-2.6.30_xo1-20090808.1740.1.olpc.a817f86.i586 kerneloops-0.12-5.fc11.i586 xorg-x11-font-utils-7.2-7.fc11.i586 -xorg-x11-server-Xorg-1.6.1.901-1.fc11.i586 -xorg-x11-server-common-1.6.1.901-1.fc11.i586 +xorg-x11-server-Xorg-1.6.3-4.fc11.i586 +xorg-x11-server-common-1.6.3-4.fc11.i586 xorg-x11-server-utils-7.4-7.fc11.i586 Download from http://people.sugarlabs.org/~mtd/soas-xo1 Caveats/Known Issues: - Camera doesn't work https://bugzilla.redhat.com/show_bug.cgi?id=498900 - SD boots sometimes fail (mount: unknown filesystem type: 'jffs2') https://bugzilla.redhat.com/show_bug.cgi?id=500196 - Power management is disabled (XO is configured not to sleep since rtcwake never wakes up) Please reply or comment on the Fedora/Redhat bug report if you see any of these. Before reporting bugs, it'd be nice if one could search the fedora bugzilla; start with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=461806 Installation instructions: http://people.sugarlabs.org/~mtd/soas-xo1/README.txt Files: soasxo58.iso - iso9990 file system (for use with livecd-iso-to-disk) soasxo58.tree.tar.lzma - for hacking soasxo58.img - for ... soasxo58.crc - ... copy-nand'ing soasxo58.plc - ... NANDblast'ing soasxo58.removable.img.tar.lzma - for: cat soasxo58.removable.tar.lzma | lzma -dc - | tar xf - -O - /dev/sdX Build date: Fri Aug 21 00:02:44 UTC 2009 pgpEd8uEj1Ta5.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Karma] Multiple pages in tutorials / exercises?
Hey, I was thinking about ways to integrate navigation for multiple pages (as also currently found in EPaath, see the attached screenshot) into Karma tutorials and exercises (I assume they're less likely to be used in games but I could be wrong). While looking at the Adding up to 10 lesson I realized that the lesson.html only contains a single div element with the rest of UI elements being handled by Javascript. So now the question is where and how a possible pages-element should be placed? I had originally thought that I could simply add it to the (lesson|exercise).html file but that wouldn't really work the the JS based Karma content, right? So now I'm thinking we'll have to add that bar to the JS file itself which however doesn't strike me as a particularly clean solution... :-/ Thoughts, suggestions? Christoph -- Christoph Derndorfer co-editor, olpcnews url: www.olpcnews.com e-mail: christ...@olpcnews.com attachment: lower_bar.png___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New SoaS-on-XO-1 build done: soasxo58
Hi Martin, Selon Martin Dengler mar...@martindengler.com: soasxo58.img - for ... soasxo58.crc - ... copy-nand'ing I just tried the installation with copy-nand. After rebooting, I got following error: Write protecting the kernel text: 268k Write protecting the kernel read-only data: 816k dracut: FATAL: Don't know how to handle root=mtd0' dracut: Refusing to continue Signal caught! Boot has failed, sleeping forever. I tried the copying installation procedure a 2nd time, but with the same result. FWIW, a prior build (soasxo51) worked fine on the same machine Best regards, Samy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New SoaS-on-XO-1 build done: soasxo57
martin wrote: soasxo57.removable.img.tar.lzma - for: cat soasxo57.removable.tar.lzma | lzma -dc - | tar xf - -O - /dev/sdX the above command is incorrect. the last hyphen is extraneous. (it tells tar to try and extract a file named '-' from the archive. but it does all the work of reading, and looks like it's doing something, and if you miss or ignore the error message, you won't realize anything's wrong until you figure out that the reason you can't boot the card is because nothing has been written to it. i'll never make that mistake three times again. :-) (btw, it's in README.txt too.) paul =- paul fox, p...@laptop.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New SoaS-on-XO-1 build done: soasxo57
On Fri, Aug 21, 2009 at 08:51:12AM -0400, Paul Fox wrote: martin wrote: soasxo57.removable.img.tar.lzma - for: cat soasxo57.removable.tar.lzma | lzma -dc - | tar xf - -O - /dev/sdX the above command is incorrect. the last hyphen is extraneous. Oops - corrected. It was correctly absent from my local shell script :). paul Martin pgpwqc2Mb39XT.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
Hi Simon, On 21 Aug 2009, at 10:58, Simon Schampijer wrote: finally I pushed today the accelerators for the views. This means that the palettes of the zoom options in the frame show now: Neighbrhood F1 etc (see screenshot below). Fab! :-) As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. I would love Journal to be on F5, but might be controversial: It would not be ideal for XO HW keyboard layout; HoboPrimate will likely bite you several times; it would clash with a key used by Develop Activity (not that I use it); maybe clash with another Activity (but none that I'm aware of)? But FWIW, a selfish +1 from me at least ;-) Regards, --Gary P.S. Oh if only Journal wasn't treated by the UI as an activity, but part of the shell. You could then just tap F4 and F5 to toggle back and forth between your current activity view, and the Journal. Oh the bliss. ;-b ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
On Aug 21, 2009, at 9:41 AM, Gary C Martin g...@garycmartin.com wrote: Hi Simon, On 21 Aug 2009, at 10:58, Simon Schampijer wrote: finally I pushed today the accelerators for the views. This means that the palettes of the zoom options in the frame show now: Neighbrhood F1 etc (see screenshot below). Fab! :-) As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. I would love Journal to be on F5, but might be controversial: It would not be ideal for XO HW keyboard layout; HoboPrimate will likely bite you several times; it would clash with a key used by Develop Activity (not that I use it); maybe clash with another Activity (but none that I'm aware of)? But FWIW, a selfish +1 from me at least ;-) Regards, --Gary P.S. Oh if only Journal wasn't treated by the UI as an activity, but part of the shell. You could then just tap F4 and F5 to toggle back and forth between your current activity view, and the Journal. Oh the bliss. ;-b That should be possible, even in the current configuration, no? Hitting F5 would switch immediately to the journal, while F4 toggles through all activities (including journal). Seems like a good solution to me... Christian ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Ad-hoc networks - New Icons
On Wed, Aug 19, 2009 at 11:59 AM, Sameer Vermasve...@sfsu.edu wrote: On Wed, Aug 19, 2009 at 5:38 AM, Benjamin M. Schwartzbmsch...@fas.harvard.edu wrote: Sameer Verma wrote: Hi Ben, So, you were referring to NM's inability to handle switching to hostap (making the wireless card act as an AP)? http://hostap.epitest.fi/ I'm aware of hostapd. In fact, I'm running it right now on an Athlon box in the living room, which acts as my apartment's access point. Yes, I did the same for many years...quite a learning experience. We used to run our college's network off a 133MHz Pentium laptop on RH 6 :-) I'm merely noting that hostapd (or equivalent) is not yet available via NetworkManager, so implementing AP mode in Sugar would require a significant restructuring of the networking code. Does the driver for Marvell chipset on the XO support hostapd (outside of NM of course)? I don't believe so. I remember hearing that there's not enough room in Flash on the XO1's Marvell chip for firmware that does both regular client/mesh as well as hostap. Bobby Sameer --Ben ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Accelerators: make Journal 'F5'
On 21 Aug 2009, at 14:52, Christian Marc Schmidt wrote: On Aug 21, 2009, at 9:41 AM, Gary C Martin g...@garycmartin.com wrote: Hi Simon, On 21 Aug 2009, at 10:58, Simon Schampijer wrote: finally I pushed today the accelerators for the views. This means that the palettes of the zoom options in the frame show now: Neighbrhood F1 etc (see screenshot below). Fab! :-) As most of the keyboards does not have a search key, should we make the Journal 'F5' ? This would be logic from the F(N) we have in the frame. I would love Journal to be on F5, but might be controversial: It would not be ideal for XO HW keyboard layout; HoboPrimate will likely bite you several times; it would clash with a key used by Develop Activity (not that I use it); maybe clash with another Activity (but none that I'm aware of)? But FWIW, a selfish +1 from me at least ;-) Regards, --Gary P.S. Oh if only Journal wasn't treated by the UI as an activity, but part of the shell. You could then just tap F4 and F5 to toggle back and forth between your current activity view, and the Journal. Oh the bliss. ;-b That should be possible, even in the current configuration, no? Hitting F5 would switch immediately to the journal, while F4 toggles through all activities (including journal). Seems like a good solution to me... +1! Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Ad-hoc network UI feedback
On Fri, Aug 21, 2009 at 1:45 PM, Gary C Marting...@garycmartin.com wrote: Sorry, late to this party, but I've finally got a recent build with Tomeu's Ad-hoc network support installed on 2 XO's here for testing (no luck with SoaS-on-XO-1 builds yet, but F11-for-XO-1 build 5 works well). OK... some quick screen grabs and discussion. Here's what it currently looks like for an XO: Hmmm... 2 grey circles... Hovering over both 'grey circles' shows this same palette: 1) Is it a bug that there are 2 'grey circles' showing the same Create new wireless network entry? 2) The empty secondary palette strips feels like a bug, like some text is missing. Should it be used to show the title describing the palette? Perhaps something like Wireless network\nInactive would be a good? 3) Showing grey device icons feels like the old NM bugs we used to get, and IMO is a bit of device icon design flaw going way back. Inactive/disabled network devices should be just simple white outlines, as per other devices when not in use. 4) Obviously a new icon for when in ad-hoc mode will help, I'll try to make a few mock-ups and see if any work out. Really great to see we have 'kids under a tree' scenario covered again in Sugar – big high five for Tomeu! :-) Looks like we might need to try to get some feature dispensation from Mr Release Manager to apply some polish now we are sliding into the feature freeze. We needs to stay away from feature freeze dispensations as much as possible. Release manager is a hard, thankless job! And Simon is doing a great job at it. If something does not make it this release, it can mature and make it into the next release. The challenge is that in a project like Sugar, the _only_ authority that a release manager has is the trust and respect he or she has earned in prior releases. That respect is earned though successfully balancing that needs of individual developers (and their feature) against the needs of the entire project. david Let's keep thinking about how to build the community, work flows, and processes which enable us to double the number of new features we can add each release! Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] SOAS and Terminal
Forwarding to sugar-devel@lists.sugarlabs.org in case someone can help Kim with her problem...perhaps it's a full disk? On Fri, Aug 21, 2009 at 02:06:52PM -0400, Kim Toufectis wrote: Martin-- If I seem a bit lost, forgive me, because I am lost... But I'm willing to keep trying. That said, your advice to use IRC to provide details rings hollow because I don't even know what the letters IRC mean, though from context I gather it's a chat program I've no idea how to access, so I'll stick to e-mail for now. If you recall, my problem was that SOAS-strawberry failed to reboot once I rpm'd Adobe Flash Player 10. I reformatted the stick and got back into SOAS on a Windows Vista PC. A complicating factor was the absence of the wget command in root, but your prior advice (sudo -y yum install wget) succeeded, so I tried following the OLPC wiki instructions for installing Adobe Flash Player again. This time it found the site, downloaded a bunch of things, and I couldn't keep up withe a scrolling screen but it got well along and suddenly stopped half way through an installation activity and told me I didn't have permission to install it, stopping dead. Stuck, I tried to start Browse to copy the terminal page into an e-mail to this list, but Browse pulsed indefinitely and didn't open. Meanwhile Terminal also crashed and also pulsed indefinitely when I tried to reopen it. So I shut down to get a fresh start, whereupon I'm back at the failure to boot with the same symptoms as the last time I rpm'd the flash player: the boot menu accepts my selecting the SOAS, switches to a screen that says Boot will begin in 1 second as ever, goes black, and ~30 seconds later it displays the following and hangs up for good: sd 6:0:0:0: [sdc] Assuming drive cache write through sd 6:0:0:0: [sdc] Assuming drive cache write through Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 Buffer I/O error on device dm-0, logical block 3 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 524272 Buffer I/O error on device dm-0, logical block 524272 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 I think the order of the numbers after logical block was different this time than the last, but otherwise the symptoms (and of course the result) are identical. This time the only thing I did after setting up my machine name and icon color was try to install Flash, so I' strongly suspect that installing Flash is indeed the cause of the failure. Any contrary views? Any workarounds? Thanks-- --Kim On Fri, Aug 21, 2009 at 11:58 AM, Martin Dengler mar...@martindengler.comwrote: On Fri, Aug 21, 2009 at 11:51:38AM -0400, Kim Toufectis wrote: Martin-- Thanks, I remembered I already installed it on my xo so I moved it over on a stick and tried to rpm it. Next I tried to reboot SOAS to test whether it worked, and since then it won't boot, so I'm back to square one. The failure might be unrelated to trying to install flash as I also added several Firefox add-ons during the same session; any thoughts? That doesn't sound scary enough to prevent booting. If you tell me (and the mailing list) more about the symptoms, or log in to IRC (#olpc-help or #sugar), perhaps we can assist more. --Kim Martin pgpGcinK2q7sO.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] New SoaS-on-XO-1 build done: soasxo57
On Fri, Aug 21, 2009 at 05:06:50PM -0400, Paul Fox wrote: martin wrote: - Power management is disabled (XO is configured not to sleep since rtcwake never wakes up) the failure of suspend/release in this distro seems to be directly related to the absence of a getty on the serial console. if the getty is present, everything works normally. if the getty is absent, the system won't resume. Confirmed. Thanks very much for finding this out. paul Martin pgp6vdaA3e7Vh.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Ad-hoc network UI feedback
On 21 Aug 2009, at 21:15, David Farning wrote: On Fri, Aug 21, 2009 at 1:45 PM, Gary C Marting...@garycmartin.com wrote: Sorry, late to this party, but I've finally got a recent build with Tomeu's Ad-hoc network support installed on 2 XO's here for testing (no luck with SoaS-on-XO-1 builds yet, but F11-for-XO-1 build 5 works well). OK... some quick screen grabs and discussion. Here's what it currently looks like for an XO: Hmmm... 2 grey circles... Hovering over both 'grey circles' shows this same palette: 1) Is it a bug that there are 2 'grey circles' showing the same Create new wireless network entry? 2) The empty secondary palette strips feels like a bug, like some text is missing. Should it be used to show the title describing the palette? Perhaps something like Wireless network\nInactive would be a good? 3) Showing grey device icons feels like the old NM bugs we used to get, and IMO is a bit of device icon design flaw going way back. Inactive/ disabled network devices should be just simple white outlines, as per other devices when not in use. 4) Obviously a new icon for when in ad-hoc mode will help, I'll try to make a few mock-ups and see if any work out. Really great to see we have 'kids under a tree' scenario covered again in Sugar – big high five for Tomeu! :-) Looks like we might need to try to get some feature dispensation from Mr Release Manager to apply some polish now we are sliding into the feature freeze. We needs to stay away from feature freeze dispensations as much as possible. +1, but if no one ever asks for a dispensations (and I most certainly haven't yet, as I don't have a formal proposal) then we live in an inflexible sausage software factory. All I raised here was the discussion of a potential of a change for some svg pixels and a (may be just XO HW) bug fix (likely an OLPC deployment issue we would need community feedback on) for potentially ~99.9% of our potential upgrading users. Release manager is a hard, thankless job! And Simon is doing a great job at it. +1! If something does not make it this release, it can mature and make it into the next release. No question, agreed. The challenge is that in a project like Sugar, the _only_ authority that a release manager has is the trust and respect he or she has earned in prior releases. That respect is earned though successfully balancing that needs of individual developers (and their feature) against the needs of the entire project. If a stable 0.86 is never shipped for XO users, then I guess we (or distro) avoid ever needing to fix this. I'm just trying to establish where the bug is (2x grey icons, Tomeu's screen shots only show 1). Let's keep thinking about how to build the community, work flows, and processes which enable us to double the number of new features we can add each release! Apologies if I ruffled feathers and hit a tender spot, but open communication is essential to community building, and not reporting feedback is so much worse than not bothering. Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] SOAS and Terminal
Kim, Martin may be on to something. Perhaps you did not set the Percent storage slider in the LiveISB utility? Mike On Fri, Aug 21, 2009 at 5:18 PM, Martin Dengler mar...@martindengler.comwrote: Forwarding to sugar-devel@lists.sugarlabs.org in case someone can help Kim with her problem...perhaps it's a full disk? On Fri, Aug 21, 2009 at 02:06:52PM -0400, Kim Toufectis wrote: Martin-- If I seem a bit lost, forgive me, because I am lost... But I'm willing to keep trying. That said, your advice to use IRC to provide details rings hollow because I don't even know what the letters IRC mean, though from context I gather it's a chat program I've no idea how to access, so I'll stick to e-mail for now. If you recall, my problem was that SOAS-strawberry failed to reboot once I rpm'd Adobe Flash Player 10. I reformatted the stick and got back into SOAS on a Windows Vista PC. A complicating factor was the absence of the wget command in root, but your prior advice (sudo -y yum install wget) succeeded, so I tried following the OLPC wiki instructions for installing Adobe Flash Player again. This time it found the site, downloaded a bunch of things, and I couldn't keep up withe a scrolling screen but it got well along and suddenly stopped half way through an installation activity and told me I didn't have permission to install it, stopping dead. Stuck, I tried to start Browse to copy the terminal page into an e-mail to this list, but Browse pulsed indefinitely and didn't open. Meanwhile Terminal also crashed and also pulsed indefinitely when I tried to reopen it. So I shut down to get a fresh start, whereupon I'm back at the failure to boot with the same symptoms as the last time I rpm'd the flash player: the boot menu accepts my selecting the SOAS, switches to a screen that says Boot will begin in 1 second as ever, goes black, and ~30 seconds later it displays the following and hangs up for good: sd 6:0:0:0: [sdc] Assuming drive cache write through sd 6:0:0:0: [sdc] Assuming drive cache write through Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 Buffer I/O error on device dm-0, logical block 3 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 524272 Buffer I/O error on device dm-0, logical block 524272 Buffer I/O error on device dm-0, logical block 0 Buffer I/O error on device dm-0, logical block 1 Buffer I/O error on device dm-0, logical block 2 I think the order of the numbers after logical block was different this time than the last, but otherwise the symptoms (and of course the result) are identical. This time the only thing I did after setting up my machine name and icon color was try to install Flash, so I' strongly suspect that installing Flash is indeed the cause of the failure. Any contrary views? Any workarounds? Thanks-- --Kim On Fri, Aug 21, 2009 at 11:58 AM, Martin Dengler mar...@martindengler.comwrote: On Fri, Aug 21, 2009 at 11:51:38AM -0400, Kim Toufectis wrote: Martin-- Thanks, I remembered I already installed it on my xo so I moved it over on a stick and tried to rpm it. Next I tried to reboot SOAS to test whether it worked, and since then it won't boot, so I'm back to square one. The failure might be unrelated to trying to install flash as I also added several Firefox add-ons during the same session; any thoughts? That doesn't sound scary enough to prevent booting. If you tell me (and the mailing list) more about the symptoms, or log in to IRC (#olpc-help or #sugar), perhaps we can assist more. --Kim Martin ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] always start the serial console to work around rtcwake never waking up
--- etc/event.d/ttyS0 |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/etc/event.d/ttyS0 b/etc/event.d/ttyS0 index 164d982..6b467e1 100644 --- a/etc/event.d/ttyS0 +++ b/etc/event.d/ttyS0 @@ -4,6 +4,7 @@ start on stopped rc2 start on stopped rc3 start on stopped rc4 start on started prefdm +start on runlevel [2345] stop on runlevel 0 stop on runlevel 1 -- 1.6.2.5 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Ad-hoc network UI feedback
On Fri, Aug 21, 2009 at 4:27 PM, Gary C Marting...@garycmartin.com wrote: On 21 Aug 2009, at 21:15, David Farning wrote: On Fri, Aug 21, 2009 at 1:45 PM, Gary C Marting...@garycmartin.com wrote: Sorry, late to this party, but I've finally got a recent build with Tomeu's Ad-hoc network support installed on 2 XO's here for testing (no luck with SoaS-on-XO-1 builds yet, but F11-for-XO-1 build 5 works well). OK... some quick screen grabs and discussion. Here's what it currently looks like for an XO: Hmmm... 2 grey circles... Hovering over both 'grey circles' shows this same palette: 1) Is it a bug that there are 2 'grey circles' showing the same Create new wireless network entry? 2) The empty secondary palette strips feels like a bug, like some text is missing. Should it be used to show the title describing the palette? Perhaps something like Wireless network\nInactive would be a good? 3) Showing grey device icons feels like the old NM bugs we used to get, and IMO is a bit of device icon design flaw going way back. Inactive/disabled network devices should be just simple white outlines, as per other devices when not in use. 4) Obviously a new icon for when in ad-hoc mode will help, I'll try to make a few mock-ups and see if any work out. Really great to see we have 'kids under a tree' scenario covered again in Sugar – big high five for Tomeu! :-) Looks like we might need to try to get some feature dispensation from Mr Release Manager to apply some polish now we are sliding into the feature freeze. We needs to stay away from feature freeze dispensations as much as possible. +1, but if no one ever asks for a dispensations (and I most certainly haven't yet, as I don't have a formal proposal) then we live in an inflexible sausage software factory. All I raised here was the discussion of a potential of a change for some svg pixels and a (may be just XO HW) bug fix (likely an OLPC deployment issue we would need community feedback on) for potentially ~99.9% of our potential upgrading users. Release manager is a hard, thankless job! And Simon is doing a great job at it. +1! If something does not make it this release, it can mature and make it into the next release. No question, agreed. The challenge is that in a project like Sugar, the _only_ authority that a release manager has is the trust and respect he or she has earned in prior releases. That respect is earned though successfully balancing that needs of individual developers (and their feature) against the needs of the entire project. If a stable 0.86 is never shipped for XO users, then I guess we (or distro) avoid ever needing to fix this. I'm just trying to establish where the bug is (2x grey icons, Tomeu's screen shots only show 1). Let's keep thinking about how to build the community, work flows, and processes which enable us to double the number of new features we can add each release! Apologies if I ruffled feathers and hit a tender spot, but open communication is essential to community building, and not reporting feedback is so much worse than not bothering. No ruffled feathers:) But, I am a firm believer in the 'no smiling before thanksgiving' rule david Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] always start the serial console to work around rtcwake never waking up
[that's a patch to olpc-utils] On Fri, Aug 21, 2009 at 11:57:45PM +0100, Martin Dengler wrote: --- etc/event.d/ttyS0 |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/etc/event.d/ttyS0 b/etc/event.d/ttyS0 index 164d982..6b467e1 100644 --- a/etc/event.d/ttyS0 +++ b/etc/event.d/ttyS0 @@ -4,6 +4,7 @@ start on stopped rc2 start on stopped rc3 start on stopped rc4 start on started prefdm +start on runlevel [2345] stop on runlevel 0 stop on runlevel 1 pgpwYBAnROwkP.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Karma] Multiple pages in tutorials / exercises?
On Fri, 2009-08-21 at 16:54 +0545, Christoph Derndorfer wrote: Hey, I was thinking about ways to integrate navigation for multiple pages (as also currently found in EPaath, see the attached screenshot) into Karma tutorials and exercises (I assume they're less likely to be used in games but I could be wrong). While looking at the Adding up to 10 lesson I realized that the lesson.html only contains a single div element with the rest of UI elements being handled by Javascript. So now the question is where and how a possible pages-element should be placed? I had originally thought that I could simply add it to the (lesson|exercise).html file but that wouldn't really work the the JS based Karma content, right? So now I'm thinking we'll have to add that bar to the JS file itself which however doesn't strike me as a particularly clean solution... :-/ Thoughts, suggestions? Christoph only the canvas element where drawing takes place should be w/in a div, all other markup, esp. stuff like the navigation bar should be in the markup. Right now, the adding_up_to_10 only has 1 div but it should actually have several elements and several canvases. The layout of a karma lesson, whenever possible, should be in html and not js -- Bryan W. Berry Technology Director OLE Nepal, http://www.olenepal.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Ad-hoc network UI feedback
2009/8/22 Gary C Martin g...@garycmartin.com: 1) Is it a bug that there are 2 'grey circles' showing the same Create new wireless network entry? It's acting as designed - showing the status of all the wireless devices it can find in the system. eth0 and msh0. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
