Re: power consumption after shutdown
Long ago I did some early measurements of the EC and it was consuming current while operating. The operating current has varied slightly according to the firmware version. There have been improvements, but I've not measured it recently. The symptom you describe is quite normal ... the battery has discharged, and the state of charge evaluated by the EC shows that charging would be of benefit. So it goes yellow. If you wish to avoid this draining by the EC, and instead rely only on draining by self-discharge of the battery pack, then remove the pack from the XO. Self-discharge rate has a dependency on storage temperature as well. If you wish to measure the EC current, a simple way to do it is to remove the battery pack, and place a current measuring device in series with the DC cable to the XO. This gives you a maximum. The actual current is smaller, because the DC socket path to the EC has more losses than the DC battery path. I did this just now, on a unit running Q2E27, and another running Q2E30, the current is 24mA at 12.9V powered from a large sealed lead acid battery with nothing else attached. Two days of this would be 1.15 amp hours (Ah). Three days would be 1.73 Ah. Assuming 3.1 Ah OLPC CL1 Li-Fe battery, two days should be enough to bring the state of charge down to about 63%, certainly time for a charge. -- James Cameronmailto:qu...@us.netrek.org http://quozl.netrek.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: power consumption after shutdown
Hi, > by default the wireless card remains alive to participate in a > potential mesh network, disabling wireless should give you a lot > more time. You're thinking of sleep mode, not the full shutdown that Mikus is doing. - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: power consumption after shutdown
On Fri, 13 Feb 2009, Chris Ball wrote: > Hi, > > > I take this to mean that *something* was draining some power for > > the two days the XO was sitting in its "shut down" state. > > The embedded controller was. Something needs to be watching for a power > button press in order to know when to turn on. by default the wireless card remains alive to participate in a potential mesh network, disabling wireless should give you a lot more time. David Lang ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: power consumption after shutdown
benjamin m. schwartz wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Mikus Grinbergs wrote: > > I take this to mean that *something* was draining some > > power for the two days the XO was sitting in its "shut down" state. > > All rechargeable batteries lose stored energy over time. The phenomenon > is called "self-discharge". It is sometimes modeled as a large (but not > infinite) resistance in parallel with the battery. but self-discharge takes place whether a battery is installed in the laptop or not. i suspect what mikus is seeing is the effect of the embedded controller (the "EC") needing a small amount of current in order to be able to observe the power button press, which tells it to turn the rest of the system on. mikus -- when you power up the system after two days, what does sugar, or olpc-pwr-log, tell you about the state of the battery? i suspect it's pretty close to full, but that it needs a small "top up". (which is why the light turns yellow.) (i'm sure richard has numbers for the power-off drain from the EC, and for the powered-off shelf life of a fully charged laptop.) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: power consumption after shutdown
Hi, > I take this to mean that *something* was draining some power for > the two days the XO was sitting in its "shut down" state. The embedded controller was. Something needs to be watching for a power button press in order to know when to turn on. - Chris. -- Chris Ball ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: power consumption after shutdown
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mikus Grinbergs wrote: > I take this to mean that *something* was draining some > power for the two days the XO was sitting in its "shut down" state. All rechargeable batteries lose stored energy over time. The phenomenon is called "self-discharge". It is sometimes modeled as a large (but not infinite) resistance in parallel with the battery. Just be glad the batteries aren't Li-Ion. Those can self-discharge totally in a month or less. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmWRtUACgkQUJT6e6HFtqRK1QCgnMJ2bhK9AXQ3/NAvlXMINRsB aMEAn1hr7kDpxwy6LoA+UYd4EXXUyP0T =hc5N -END PGP SIGNATURE- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
power consumption after shutdown
As far as I can tell, the battery in the XO-1 retains its charge quite well when taken out of the case. But in my experience, when I specify 'Shutdown' to the software, and close the XO lid after all its lights (including 'power') are extinguished -- then when two days later I insert the AC adapter into the (still closed) XO, after the 'power' light comes on, it goes yellow. [I've seen this both when I was running 'joyride' on the XO, and when I was running 'staging'.] I take this to mean that *something* was draining some power for the two days the XO was sitting in its "shut down" state. If I want to prolong the "shelf life electricity" of my shut-down XO, do I need to "turn off" some facilities before I click on the 'Shutdown' entry in the palette of the central icon in Home View ? mikus ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-activation-server over IPv6
On Fri, Feb 13, 2009 at 3:10 AM, Daniel Drake wrote: > Thanks, done! > New patch at http://dev.laptop.org/ticket/9246 > > Are your XS-side changes included in the latest 0.5.1 release, or is > this scheduled for later? Later. 0.5.2 or 0.6. If you need it in a formal release, let me know and I'll see about building a 0.5.2 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 ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Sat, Feb 14, 2009 at 9:11 AM, Simon Schampijer wrote:
> Please find attached the patch against master.
Looks good to me (but I know nothing of what's changed in master...)
> - i use the backup_url to see if we are associated with a schoolserver
> - why did you use the jabber server for this 'xs_fqdn = prof.jabber_server'?
Good question. Neither is the right one. In a XS driven net, both are
equal. In a XS-on-the-internet situation, the "public XS" may decide
to not offer backup service. Of the 3 (moodle/webapps, xmpp, backup),
backup is the most burdensome on the server.
So I think there is a (very marginal) advantage to using the jabber
server. But the most important hting is that 0.82.x and master use the
same, so whatever you do, both should use the same...
(The right fix is to have a 'schoolserver fqdn' entry in the
profile... but that's for the next Sugar dev cycle I guess...)
> - c.execute('''CREATE TABLE IF NOT EXISTS
> + moz_cookies
> + (id INTEGER PRIMARY KEY,
> + name TEXT,
> + value TEXT,
> + host TEXT,
> + path TEXT,
> + expiry INTEGER,
> + lastAccessed INTEGER,
> + isSecure INTEGER,
> + isHttpOnly INTEGER);''')
>
> - is the ';' correct here or a typo?
typo
> - i only except for sqlite3.Error
Is that the only thing that could go wrong? My thinking has been: if
we fail, let the startup succeed. This is a good feature, but not a
showstopper.
> - what bothers me a bit is that you don't get an error when the database
> does not exist - sqlite creates a new one actually - so we might return as
> well on 'if not os.path.exists(os.path.join(_profile_path,
> 'cookies.sqlite'))'
The DB does not exist on the first use of Browse. Actually, it does
not get created until the first website sets the first cookie, AFAICS.
That means that on the first use of Browse the user goes to the XS and
doesn't get autenticated. So if the DB doesn't exist, _we want to
create it_. It's not a failure, it's success.
> - the method could even be a function as it does not interact at all with
> the class itself, not sure what is nicer
I'd prefer a function, but it's not my codebase, so follow the style... :-)
m
--
martin.langh...@gmail.com
mar...@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Sat, Feb 14, 2009 at 12:31 PM, Jerry Vonau wrote: > I'm seeing the same errors in the install log as Sameer while installing > on an XO. openssl does not get installed, because uname returns as an > i586 while there is no openssl.586 in the repo just .686. Just to backup > my hunch note that a 586 kernel gets installed as recorded in the > install log. "yum repolist" returns the same error as mentioned in the > BZ on the XO. I see Sameer's confirmation. You struck gold with that diagnosis. On the XO OS we have the same problem, and a quick check reveals that we ship openssl i686 on the XS. The disk image build happens on xs-dev which reports i686 surely, but it runs on the XO. Can't find anything in the list archives on the matter. h. m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Fri, 2009-02-13 at 10:19 -0800, Sameer Verma wrote: > On Fri, Feb 13, 2009 at 2:57 AM, Jerry Vonau wrote: > > On Thu, 2009-02-12 at 23:30 -0800, Sameer Verma wrote: > >> On Wed, Feb 11, 2009 at 10:37 PM, Sameer Verma wrote: > >> > On Wed, Feb 11, 2009 at 8:42 PM, Martin Langhoff > >> > wrote: > >> >> On Thu, Feb 12, 2009 at 2:41 PM, Sameer Verma wrote: > >> >>> was with eth0 not showing up. It looks like I am the victim of the > >> >>> dreaded Realtek 8139 bug. It worked in XS 0.4 but in 0.5.1 it refuses > >> >>> to show up. > >> >> > >> >> Strange, but it does look like a driver problem. > >> >> > >> >> The links you provide show various different problems with that NIC. > >> >> In some cases, irqpoll in the kernel boot line fixes, in others some > >> >> fiddling with ethtool was needed... > >> >> > >> >> It'll be good to know which of the fixes helps you :-) > >> > > >> > appending irqpoll has fixed that problem. Now, I've hit another bug. > >> > This is yum broken with _sha256 as stated here. > >> > http://fedoraforum.org/forum/showthread.php?t=193507 > >> > > >> > I'm going to try the workaround. > >> > > >> >> > >> >> BTW, if you upgraded from XS-0.4, it might be a good idea to rm > >> >> /etc/udev/rules.d/70-persistent-net.rules > >> > > >> > No, this was a clean install. I'm running the server for testing only, > >> > so I can afford to wipe it clean. > >> > > >> > Sameer > >> > -- > >> > Dr. Sameer Verma, Ph.D. > >> > Associate Professor of Information Systems > >> > San Francisco State University > >> > San Francisco CA 94132 USA > >> > http://verma.sfsu.edu/ > >> > http://opensource.sfsu.edu/ > >> > > >> > >> > >> So, after mucking around last night and today, I wiped my XS box and > >> reformatted it to remove ALL traces of 0.4 I have a clean 0.5.1 > >> install on it. md5sum of the ISO is c0fde10b93cab3cb1a3bc3a42ceb5408 > >> > >> I've circumvented the realtek 8139 problem by appending irqpoll in > >> grub.conf That seems to work, although I have to bring up eth0 > >> manually and issuing dhcient eth0 > >> > >> I still hit the bug of _sha256 as mentioned here: > >> https://bugzilla.redhat.com/show_bug.cgi?id=454179 > >> > >> Note that I am not upgrading anything. Its a clean install. I believe > >> the appropriate word for this is: AARGH! > >> > >> I wish Fedora had LTS or "Stable" branch (it does...kinda...in > >> RHEL...are we allowed to say CentOS here?) but that's another thread > >> and another rant. It does remind me of why I don't run anything on > >> Fedora anymore. > >> > >> Anyway, this is getting in the way. Is anyone seeing this too? If so, > >> then its a significant barrier for 0.5.1 > >> > >> Suggestions? > > > > Can you post the /root/install.log and /root/anaconda.log or just send > > them to me. > > > > Jerry > > > > > > > > > > > > I've attached both. Note: anaconda.log was in /var/log/ and not in /root > > Sameer Martin: I'm seeing the same errors in the install log as Sameer while installing on an XO. openssl does not get installed, because uname returns as an i586 while there is no openssl.586 in the repo just .686. Just to backup my hunch note that a 586 kernel gets installed as recorded in the install log. "yum repolist" returns the same error as mentioned in the BZ on the XO. Sameer: What does "uname -a" return on this laptop? Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Thu, 2009-02-12 at 23:30 -0800, Sameer Verma wrote: > On Wed, Feb 11, 2009 at 10:37 PM, Sameer Verma wrote: > > On Wed, Feb 11, 2009 at 8:42 PM, Martin Langhoff > > wrote: > >> On Thu, Feb 12, 2009 at 2:41 PM, Sameer Verma wrote: > >>> was with eth0 not showing up. It looks like I am the victim of the > >>> dreaded Realtek 8139 bug. It worked in XS 0.4 but in 0.5.1 it refuses > >>> to show up. > >> > >> Strange, but it does look like a driver problem. > >> > >> The links you provide show various different problems with that NIC. > >> In some cases, irqpoll in the kernel boot line fixes, in others some > >> fiddling with ethtool was needed... > >> > >> It'll be good to know which of the fixes helps you :-) > > > > appending irqpoll has fixed that problem. Now, I've hit another bug. > > This is yum broken with _sha256 as stated here. > > http://fedoraforum.org/forum/showthread.php?t=193507 > > > > I'm going to try the workaround. > > > >> > >> BTW, if you upgraded from XS-0.4, it might be a good idea to rm > >> /etc/udev/rules.d/70-persistent-net.rules > > > > No, this was a clean install. I'm running the server for testing only, > > so I can afford to wipe it clean. > > > > Sameer > > -- > > Dr. Sameer Verma, Ph.D. > > Associate Professor of Information Systems > > San Francisco State University > > San Francisco CA 94132 USA > > http://verma.sfsu.edu/ > > http://opensource.sfsu.edu/ > > > > > So, after mucking around last night and today, I wiped my XS box and > reformatted it to remove ALL traces of 0.4 I have a clean 0.5.1 > install on it. md5sum of the ISO is c0fde10b93cab3cb1a3bc3a42ceb5408 > > I've circumvented the realtek 8139 problem by appending irqpoll in > grub.conf That seems to work, although I have to bring up eth0 > manually and issuing dhcient eth0 > > I still hit the bug of _sha256 as mentioned here: > https://bugzilla.redhat.com/show_bug.cgi?id=454179 > > Note that I am not upgrading anything. Its a clean install. I believe > the appropriate word for this is: AARGH! > > I wish Fedora had LTS or "Stable" branch (it does...kinda...in > RHEL...are we allowed to say CentOS here?) but that's another thread > and another rant. It does remind me of why I don't run anything on > Fedora anymore. > > Anyway, this is getting in the way. Is anyone seeing this too? If so, > then its a significant barrier for 0.5.1 > > Suggestions? Can you post the /root/install.log and /root/anaconda.log or just send them to me. Jerry ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Fri, Feb 13, 2009 at 3:31 PM, Jerry Vonau wrote: > On Fri, 2009-02-13 at 10:19 -0800, Sameer Verma wrote: >> On Fri, Feb 13, 2009 at 2:57 AM, Jerry Vonau wrote: >> > On Thu, 2009-02-12 at 23:30 -0800, Sameer Verma wrote: >> >> On Wed, Feb 11, 2009 at 10:37 PM, Sameer Verma wrote: >> >> > On Wed, Feb 11, 2009 at 8:42 PM, Martin Langhoff >> >> > wrote: >> >> >> On Thu, Feb 12, 2009 at 2:41 PM, Sameer Verma wrote: >> >> >>> was with eth0 not showing up. It looks like I am the victim of the >> >> >>> dreaded Realtek 8139 bug. It worked in XS 0.4 but in 0.5.1 it refuses >> >> >>> to show up. >> >> >> >> >> >> Strange, but it does look like a driver problem. >> >> >> >> >> >> The links you provide show various different problems with that NIC. >> >> >> In some cases, irqpoll in the kernel boot line fixes, in others some >> >> >> fiddling with ethtool was needed... >> >> >> >> >> >> It'll be good to know which of the fixes helps you :-) >> >> > >> >> > appending irqpoll has fixed that problem. Now, I've hit another bug. >> >> > This is yum broken with _sha256 as stated here. >> >> > http://fedoraforum.org/forum/showthread.php?t=193507 >> >> > >> >> > I'm going to try the workaround. >> >> > >> >> >> >> >> >> BTW, if you upgraded from XS-0.4, it might be a good idea to rm >> >> >> /etc/udev/rules.d/70-persistent-net.rules >> >> > >> >> > No, this was a clean install. I'm running the server for testing only, >> >> > so I can afford to wipe it clean. >> >> > >> >> > Sameer >> >> > -- >> >> > Dr. Sameer Verma, Ph.D. >> >> > Associate Professor of Information Systems >> >> > San Francisco State University >> >> > San Francisco CA 94132 USA >> >> > http://verma.sfsu.edu/ >> >> > http://opensource.sfsu.edu/ >> >> > >> >> >> >> >> >> So, after mucking around last night and today, I wiped my XS box and >> >> reformatted it to remove ALL traces of 0.4 I have a clean 0.5.1 >> >> install on it. md5sum of the ISO is c0fde10b93cab3cb1a3bc3a42ceb5408 >> >> >> >> I've circumvented the realtek 8139 problem by appending irqpoll in >> >> grub.conf That seems to work, although I have to bring up eth0 >> >> manually and issuing dhcient eth0 >> >> >> >> I still hit the bug of _sha256 as mentioned here: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=454179 >> >> >> >> Note that I am not upgrading anything. Its a clean install. I believe >> >> the appropriate word for this is: AARGH! >> >> >> >> I wish Fedora had LTS or "Stable" branch (it does...kinda...in >> >> RHEL...are we allowed to say CentOS here?) but that's another thread >> >> and another rant. It does remind me of why I don't run anything on >> >> Fedora anymore. >> >> >> >> Anyway, this is getting in the way. Is anyone seeing this too? If so, >> >> then its a significant barrier for 0.5.1 >> >> >> >> Suggestions? >> > >> > Can you post the /root/install.log and /root/anaconda.log or just send >> > them to me. >> > >> > Jerry >> > >> > >> > >> > >> > >> >> I've attached both. Note: anaconda.log was in /var/log/ and not in /root >> >> Sameer > > Martin: > > I'm seeing the same errors in the install log as Sameer while installing > on an XO. openssl does not get installed, because uname returns as an > i586 while there is no openssl.586 in the repo just .686. Just to backup > my hunch note that a 586 kernel gets installed as recorded in the > install log. "yum repolist" returns the same error as mentioned in the > BZ on the XO. > > Sameer: > What does "uname -a" return on this laptop? > > > Jerry > > > > uname -a on the fujitsu laptop returns: Linux localhost.localdomain 2.6.27.9-73.fc9.i586 #1 SMP Tue Dec 16 14:34:16 EST 2008 i586 i586 i386 GNU/Linux Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor of Information Systems San Francisco State University San Francisco CA 94132 USA http://verma.sfsu.edu/ http://opensource.sfsu.edu/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
DebXO 0.5 release
Hi, I've just built and tagged DebXO 0.5. I had to put this out sooner than I'd anticipated due to an OFW upgrade that broke things. It doesn't have some of the features I'd wanted to have in 0.5, so they'll have to come later. DebXO is a version of Debian (testing) that is customized for the XO-1 hardware. The release can be found here: http://lunge.mit.edu/~dilinger/debxo-latest/images/ CHANGES: - OFW q2e30+ freezes the DCON on boot, so DebXO's olpc.fth now unfreezes it. If you upgraded your machine to q2e30 and it looked like DebXO no longer worked.. this version of DebXO will work. Alternatively, you can just edit your /boot/olpc.fth to add the line "dcon-unfreeze" before the "boot" line. - The Sugar desktop has gotten an upgrade, from Sugar 0.81 to 0.82. - There's a new XFCE desktop, courtesy of Erik Garrison. - Desktops will now auto-start X. Gdm and Kdm have been dropped from the images. If you want them back, just 'apt-get remove autox' and 'apt-get install gdm' (or kdm). Other changes can be seen at: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary INSTALLATION ONTO NAND FLASH: To install onto the XO's NAND flash, download the jffs2/$DESKTOP.dat and jffs2/$DESKTOP.img to a USB or SD stick (where $DESKTOP is one of the various desktops - gnome, kde, lxde, sugar, base, or awesome). Boot into OFW (make sure your XO is unlocked!), and run update-nand disk:\$DESKTOP.img or update-nand sd:\$DESKTOP.img (depending upon whether you downloaded to an SD or USB disk). If update-nand spits out any errors, make sure you're running an appropriately up-to-date version of OFW. The q2d* series do not support update-nand, and versions q2e18 and q2e19 are known to be buggy with partitions. Firmware and instructions for upgrading can be found here: http://wiki.laptop.org/go/Firmware INSTALLATION ONTO SD/USB: To install onto an SD or USB device, download the ext3/debxo-$DESKTOP.ext3.img.gz file, and run zcat debxo-$DESKTOP.ext3.img.gz > /dev/mmcblk0 or zcat debxo-$DESKTOP.ext3.img.gz > /dev/sdX (depending upon whether you're writing to an SD or USB disk). Note that this will overwrite any data that is on the SD or USB disk. USAGE: By default, a user 'olpc' is created (with no password, and sudo access). Some desktops automatically start a display manager and log you in; some do not. The root password is disabled by default. This is a stock Debian Lenny system with only a few modifications, so it can obviously be tailored. HACKING: xodist is the name of the collection of scripts that are used to produce DebXO. The git repository can be downloaded via: git clone git://lunge.mit.edu/git/xodist There's also a web interface to that: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=summary Help is always appreciated. The roadmap for future releases can be found here: http://lunge.mit.edu/cgi-bin/gitweb.cgi?p=xodist;a=blob;f=TODO Enjoy! ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Thu, Feb 12, 2009 at 11:30 PM, Sameer Verma wrote: > On Wed, Feb 11, 2009 at 10:37 PM, Sameer Verma wrote: >> On Wed, Feb 11, 2009 at 8:42 PM, Martin Langhoff >> wrote: >>> On Thu, Feb 12, 2009 at 2:41 PM, Sameer Verma wrote: was with eth0 not showing up. It looks like I am the victim of the dreaded Realtek 8139 bug. It worked in XS 0.4 but in 0.5.1 it refuses to show up. >>> >>> Strange, but it does look like a driver problem. >>> >>> The links you provide show various different problems with that NIC. >>> In some cases, irqpoll in the kernel boot line fixes, in others some >>> fiddling with ethtool was needed... >>> >>> It'll be good to know which of the fixes helps you :-) >> >> appending irqpoll has fixed that problem. Now, I've hit another bug. >> This is yum broken with _sha256 as stated here. >> http://fedoraforum.org/forum/showthread.php?t=193507 >> >> I'm going to try the workaround. >> >>> >>> BTW, if you upgraded from XS-0.4, it might be a good idea to rm >>> /etc/udev/rules.d/70-persistent-net.rules >> >> No, this was a clean install. I'm running the server for testing only, >> so I can afford to wipe it clean. >> >> Sameer >> -- >> Dr. Sameer Verma, Ph.D. >> Associate Professor of Information Systems >> San Francisco State University >> San Francisco CA 94132 USA >> http://verma.sfsu.edu/ >> http://opensource.sfsu.edu/ >> > > > So, after mucking around last night and today, I wiped my XS box and > reformatted it to remove ALL traces of 0.4 I have a clean 0.5.1 > install on it. md5sum of the ISO is c0fde10b93cab3cb1a3bc3a42ceb5408 > > I've circumvented the realtek 8139 problem by appending irqpoll in > grub.conf That seems to work, although I have to bring up eth0 > manually and issuing dhcient eth0 > > I still hit the bug of _sha256 as mentioned here: > https://bugzilla.redhat.com/show_bug.cgi?id=454179 > > Note that I am not upgrading anything. Its a clean install. I believe > the appropriate word for this is: AARGH! > > I wish Fedora had LTS or "Stable" branch (it does...kinda...in > RHEL...are we allowed to say CentOS here?) but that's another thread > and another rant. It does remind me of why I don't run anything on > Fedora anymore. > > Anyway, this is getting in the way. Is anyone seeing this too? If so, > then its a significant barrier for 0.5.1 > > Suggestions? > > Sameer > -- > Dr. Sameer Verma, Ph.D. > Associate Professor of Information Systems > San Francisco State University > San Francisco CA 94132 USA > http://verma.sfsu.edu/ > http://opensource.sfsu.edu/ > Some more snooping around. I took the same CD and installed it on a desktop with one NIC. This time everything went as per plan. Everything! I have a XS-0.5.1 running in my office with one AA plugged into it and working as advertised. It works great, except that I don't want to lug desktops around to OLPC-SF meetings :-) We have a local school showing up tomorrow. I'm glad that i am able to get 0.5.1 running, so I can recommend it to them. Thanks for all the hard labor, Martin! I'll buy you a few beers if/when you come to SF for moodlemoot. I *strongly* suspect that the Fujitsu P2120 laptop problems as stated in this thread are related to Realtek 8139 driver not working properly during installation. Maybe I should append irqpoll to the grub lines *before* the install CD boots and see how that goes. Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor of Information Systems San Francisco State University San Francisco CA 94132 USA http://verma.sfsu.edu/ http://opensource.sfsu.edu/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[Server-devel] [xs-activity-server] Support .xol library bundles
Generalize into a a bundle superclass and create a Content subclass for
content bundles.
---
src/xs_activities.py | 250 +-
1 files changed, 146 insertions(+), 104 deletions(-)
diff --git a/src/xs_activities.py b/src/xs_activities.py
index 85d873f..186d41b 100644
--- a/src/xs_activities.py
+++ b/src/xs_activities.py
@@ -16,10 +16,6 @@ from cStringIO import StringIO
import syslog
from ConfigParser import SafeConfigParser
-#See http://wiki.laptop.org/go/Activity_bundles
-INFO_PATH = 'activity/activity.info'
-INFO_SECTION = 'Activity'
-
TEMPLATE_DIR = '/library/xs-activity-server/templates'
# how many versions before the latest are worth having around.
@@ -40,10 +36,97 @@ def log(msg, level=syslog.LOG_NOTICE):
syslog.syslog(level, msg)
syslog.closelog()
-class ActivityError(Exception):
+class BundleError(Exception):
pass
-class Activity:
+class Bundle(object):
+def __init__(self, bundle):
+self.linfo = {}
+self.zf = zipfile.ZipFile(bundle)
+# The activity path will be 'Something.activity/activity/activity.info'
+for p in self.zf.namelist():
+if p.endswith(self.INFO_PATH):
+self.raw_data = read_info_file(self.zf, p, self.INFO_SECTION)
+
+# the file name itself is needed for the URL
+self.url = os.path.basename(bundle)
+
+self.name = self.raw_data.get('name')
+self.license = self.raw_data.get('license', None)
+
+# child ctor should now call
+# _set_bundle_id
+# _set_version
+# _set_description
+def _set_bundle_id(self, id):
+if id is None:
+raise BundleError("bad bundle: No bundle ID")
+self.bundle_id = id
+if self.name is None:
+self.name = id
+
+def _set_version(self, version):
+self.version = version
+
+def _set_description(self, description):
+self.description = description
+
+def __cmp__(self, other):
+"""Alphabetical sort (locale dependant of course)"""
+if self.bundle_id == other.bundle_id:
+return cmp(self.version, other.version)
+return cmp(self.name, other.name)
+
+def set_older_versions(self, versions):
+"""Versions should be a list of (version number, version tuples)"""
+self.older_versions = ', '.join('%s' % (v.url,
v.version) for v in versions)
+
+def to_html(self, locale, template=None):
+"""Fill in the template with data approriate for the locale."""
+if template is None:
+template = read_template('activity', locale)
+
+d = {'older_versions': self.older_versions,
+ 'bundle_id': self.bundle_id,
+ 'activity_version':self.version,
+ 'bundle_url': self.url,
+ 'name':self.name,
+ 'description': self.description,
+ }
+
+d.update(self.linfo.get(locale, {}))
+
+if d['older_versions']:
+d['show_older_versions'] = 'inline'
+else:
+d['show_older_versions'] = 'none'
+
+return template % d
+
+def get_name(self, locale=None):
+return self.name
+
+class Content(Bundle):
+INFO_PATH = "library/library.info"
+INFO_SECTION = "Library"
+
+def __init__(self, bundle):
+super(Content, self).__init__(bundle)
+
+d = self.raw_data
+# bundle_id is often missing; service name is used instead.
+self._set_bundle_id(d.get('global_name', None))
+self._set_version(int(d.get('library_version', 1)))
+self._set_description(d.get('long_name', ''))
+
+def debug(self, force_recheck=False):
+# FIXME: implement debug checking for content bundles
+return {}
+
+class Activity(Bundle):
+INFO_PATH = "activity/activity.info"
+INFO_SECTION = "Activity"
+
#Activities appear to be looser than RFC3066, using e.g. _ in place of -.
linfo_re = re.compile(r'/locale/([A-Za-z]+[\w-]*)/activity.linfo$')
@@ -51,41 +134,23 @@ class Activity:
"""Takes a zipped .xo bundle name, returns a dictionary of its
activity info. Can raise a variety of exceptions, all of
which should indicate the bundle is invalid."""
-zf = zipfile.ZipFile(bundle)
-self.linfo = {}
-# The activity path will be 'Something.activity/activity/activity.info'
-# and locale info will be
Something.activity/locale/xx_XX/activity.linfo
-for p in zf.namelist():
+super(Activity, self).__init__(bundle)
+
+# The locale info will be
Something.activity/locale/xx_XX/activity.linfo
+for p in self.zf.namelist():
linfo = self.linfo_re.search(p)
if linfo:
lang = canonicalise(linfo.group(1))
-self.linfo[lang] = read_info_file(zf, p)
-elif p.endswith(INFO_PATH):
-
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
Martin Langhoff wrote:
On Fri, Feb 13, 2009 at 12:19 AM, Simon Schampijer wrote:
When thinking about it a bit more - the big plus with your approach that
it's only affects Browse - code wise, which is when back porting to 0.82 a
big plus, actually maybe the only way.
Bingo! I think you're starting to read my mind...
m
Please find attached the patch against master.
- i use the backup_url to see if we are associated with a schoolserver
- why did you use the jabber server for this 'xs_fqdn = prof.jabber_server'?
- c.execute('''CREATE TABLE IF NOT EXISTS
+ moz_cookies
+ (id INTEGER PRIMARY KEY,
+ name TEXT,
+ value TEXT,
+ host TEXT,
+ path TEXT,
+ expiry INTEGER,
+ lastAccessed INTEGER,
+ isSecure INTEGER,
+ isHttpOnly INTEGER);''')
- is the ';' correct here or a typo?
- i only except for sqlite3.Error
- what bothers me a bit is that you don't get an error when the database
does not exist - sqlite creates a new one actually - so we might return
as well on 'if not os.path.exists(os.path.join(_profile_path,
'cookies.sqlite'))'
- the method could even be a function as it does not interact at all
with the class itself, not sure what is nicer
Best,
Simon
diff --git a/webactivity.py b/webactivity.py
index f7f2459..e283cb5 100644
--- a/webactivity.py
+++ b/webactivity.py
@@ -26,7 +26,10 @@ import sha
import base64
import time
import shutil
-
+import sqlite3
+import cjson
+import gconf
+
from sugar.activity import activity
from sugar.graphics import style
import telepathy
@@ -96,6 +99,8 @@ class WebActivity(activity.Activity):
self._browser = Browser()
+self._seed_xs_cookie()
+
toolbox = activity.ActivityToolbox(self)
self._edit_toolbar = EditToolbar(self._browser)
@@ -465,3 +470,55 @@ class WebActivity(activity.Activity):
def get_document_path(self, async_cb, async_err_cb):
self._browser.get_source(async_cb, async_err_cb)
+def _seed_xs_cookie(self):
+''' Create a HTTP Cookie to authenticate with the Schoolserver
+'''
+client = gconf.client_get_default()
+backup_url = client.get_string('/desktop/sugar/backup_url')
+if not backup_url:
+_logger.debug('seed_xs_cookie: Not registered with Schoolserver')
+return
+
+pubkey = profile.get_profile().pubkey
+cookie_data = {'color': profile.get_color().to_string(),
+ 'pkey_hash': sha.new(pubkey).hexdigest()}
+
+db_path = os.path.join(_profile_path, 'cookies.sqlite')
+try:
+cookies_db = sqlite3.connect(db_path)
+c = cookies_db.cursor()
+
+c.execute('''CREATE TABLE IF NOT EXISTS
+ moz_cookies
+ (id INTEGER PRIMARY KEY,
+ name TEXT,
+ value TEXT,
+ host TEXT,
+ path TEXT,
+ expiry INTEGER,
+ lastAccessed INTEGER,
+ isSecure INTEGER,
+ isHttpOnly INTEGER)''')
+
+c.execute('''SELECT id
+ FROM moz_cookies
+ WHERE name=? AND host=? AND path=?''',
+ ('xoid', backup_url, '/'))
+
+if c.fetchone():
+_logger.debug('seed_xs_cookie: Cookie exists already')
+return
+
+expire = int(time.time()) + 10*365*24*60*60
+c.execute('''INSERT INTO moz_cookies (name, value, host,
+ path, expiry, lastAccessed,
+ isSecure, isHttpOnly)
+ VALUES(?,?,?,?,?,?,?,?)''',
+ ( 'xoid', cjson.encode(cookie_data), backup_url,
+'/', expire, 0, 0, 0 ))
+cookies_db.commit()
+cookies_db.close()
+except sqlite3.Error, e:
+_logger.error('seed_xs_cookie: %s' % e)
+else:
+_logger.debug('seed_xs_cookie: Updated cookie successfully')
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
[Server-devel] [xs-activity-server] Fix html output
The HTML output by the activity server is not understood by the sugar activity updater because the URL link is not nested inside the span. --- templates/DEFAULT/activity |2 +- templates/es/activity |2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/DEFAULT/activity b/templates/DEFAULT/activity index 0516776..b600053 100644 --- a/templates/DEFAULT/activity +++ b/templates/DEFAULT/activity @@ -4,7 +4,7 @@ Identifier: %(bundle_id)s Version: %(activity_version)s - URL: %(bundle_url)s + URL: %(bundle_url)s Older versions: %(older_versions)s diff --git a/templates/es/activity b/templates/es/activity index ff05253..37c99a5 100644 --- a/templates/es/activity +++ b/templates/es/activity @@ -4,7 +4,7 @@ Identificador: %(bundle_id)s Versión: %(activity_version)s - URL: %(bundle_url)s + URL: %(bundle_url)s Versiones anteriores: %(older_versions)s -- 1.6.1.3 ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: XO BW mode (was Re: Guidance sought on collaboration techniques)
Ohhh, gotcha. I have only tried turning the brightness to off in dark environments :) On Fri, Feb 13, 2009 at 1:27 PM, Gary C Martin wrote: > On 13 Feb 2009, at 17:28, Wade Brainerd wrote: > > On Fri, Feb 13, 2009 at 11:38 AM, Gary C Martin >> wrote: >> The below will switch to BW, but still leave the backlight on: >> >> su >> echo 1 > /sys/devices/platform/dcon/output >> >> And to kill backlight and go to BW mode all at once: >> >> su >> echo 0 > /sys/class/backlight/dcon-bl/brightness >> >> Hmmm, I wonder if there is dbus hooks for this for a less hacky solution. >> >> Oh, cool - thanks! Isn't there any button on the XO mapped to this? How >> is a normal user supposed to engage it? >> > > It simply engages BW/reflective mode when you dial down the brightness to > off. Alt-brightness up and Alt-brightness down on the XO get you to > reflective mode (and back) in one strike. In normal use, colour mode is > still quite usable (though not as crisp as BW) in bright sunlight, it's just > that the colours desaturate as the reflected light gets brighter. > > Note the backlight goes through the colour refractive screen magic, even in > BW mode, so it's not as sharp as with the backlight 100% off and just using > reflected light (though BW + backlight does still look slightly crisper than > colour mode, to my eye, like sub pixel sharpening tricks on conventional > screens). > > --Gary > > -Wade >> >> > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO BW mode (was Re: Guidance sought on collaboration techniques)
On 13 Feb 2009, at 17:28, Wade Brainerd wrote: > On Fri, Feb 13, 2009 at 11:38 AM, Gary C Martin > wrote: > The below will switch to BW, but still leave the backlight on: > >su >echo 1 > /sys/devices/platform/dcon/output > > And to kill backlight and go to BW mode all at once: > >su >echo 0 > /sys/class/backlight/dcon-bl/brightness > > Hmmm, I wonder if there is dbus hooks for this for a less hacky > solution. > > Oh, cool - thanks! Isn't there any button on the XO mapped to > this? How is a normal user supposed to engage it? It simply engages BW/reflective mode when you dial down the brightness to off. Alt-brightness up and Alt-brightness down on the XO get you to reflective mode (and back) in one strike. In normal use, colour mode is still quite usable (though not as crisp as BW) in bright sunlight, it's just that the colours desaturate as the reflected light gets brighter. Note the backlight goes through the colour refractive screen magic, even in BW mode, so it's not as sharp as with the backlight 100% off and just using reflected light (though BW + backlight does still look slightly crisper than colour mode, to my eye, like sub pixel sharpening tricks on conventional screens). --Gary > -Wade > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Fri, Feb 13, 2009 at 2:56 AM, Martin Langhoff wrote: > On Fri, Feb 13, 2009 at 8:30 PM, Sameer Verma wrote: >> I've circumvented the realtek 8139 problem by appending irqpoll in >> grub.conf That seems to work, although I have to bring up eth0 >> manually and issuing dhcient eth0 > > Good to hear irqpoll works. Strange that dhclient doesn't work on > network start... > Yeah. I'm going to have to figure out how to get eth0 to come up automatically (its been a while since I did anything RH). >> I still hit the bug of _sha256 as mentioned here: >> https://bugzilla.redhat.com/show_bug.cgi?id=454179 > > That bug is bizarre. I've installed 0.5.1 on several machines without > hitting this at all. No idea whatcould it be - package that reportedly > caused that bug has long been fixed... what versions of those pkgs > does rpm -qa say you have? > I'm attaching the output of rpm -qa Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor of Information Systems San Francisco State University San Francisco CA 94132 USA http://verma.sfsu.edu/ http://opensource.sfsu.edu/ rpmqa Description: Binary data ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
XO BW mode (was Re: Guidance sought on collaboration techniques)
On Fri, Feb 13, 2009 at 11:38 AM, Gary C Martin wrote: > The below will switch to BW, but still leave the backlight on: > >su >echo 1 > /sys/devices/platform/dcon/output > > And to kill backlight and go to BW mode all at once: > >su >echo 0 > /sys/class/backlight/dcon-bl/brightness > > Hmmm, I wonder if there is dbus hooks for this for a less hacky solution. Oh, cool - thanks! Isn't there any button on the XO mapped to this? How is a normal user supposed to engage it? -Wade ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Guidance sought on collaboration techniques
Wade, Thanks for pinpointing the code I should look at. I printed out the whole thing yesterday, and there's a lot to it. It does look better commented than the other stuff I've been struggling with. Just FYI its View Slides where I mean to put the collaboration stuff. Read Etexts currently works just like the Read activity for collaboration. When another user joins the activity he gets a complete copy of the book. This actually works better in Read Etexts than in Read, because text files are smaller than PDFs, and because my Activity actually saves the book in the Journal when you receive it, whereas when I last looked Read did not. Where I still have problems with Read Etexts in terms of collaboration is: 1). When the book is shared the person joining sees the title of the book. However when the book is saved to the Journal it is given the title Read Etexts, not the title of the book. I know how to change the title in the Journal entry, but not how to get the title of the book being shared. Read seems to get this from metadata in the PDF. 2). When I resume a book that I got from joining the book will be downloaded again if it is still being shared, even if there is no need to do so. Also, the book I am resuming will be shared, even if I don't want to do that. Once you start sharing there seems to be no way of turning it off. The interest in Read Etexts is for its text to speech feature, not sharing. With any luck I'll get them both working. Thanks, James Simmons Wade Brainerd wrote: Hey James, FYI here is the collaboration code in Colors! http://git.sugarlabs.org/projects/colors/repos/mainline/blobs/master/colors.py#line641 It's fairly well commented but let me know if you have any questions about how it works, or what you should do differently in Read Etexts. I totally agree that Etexts should be a killer app for the XO. As an aside, does anyone know if there is a manual way to force the XO screen into sunlight mode? -Wade On Thu, Feb 12, 2009 at 10:56 AM, James Simmons mailto:jim.simm...@walgreens.com>> wrote: Wade, I'll have to check out the code in Colors! What I really need is some sample code and some good docs on the APIs available. What I have now was copied from the Read activity, and not all of it is clear to me. If I understood what APIs were available that would be a big help. I will welcome feedback on my code once I have something good enough to criticize, but I'm not there yet. Thanks, James Simmons Wade Brainerd wrote: Hey James, I can help you out with this if you want. Your collaboration design sounds fine to me. I did something similar in Colors! where certain parts of the UI are disabled on the joining instances. What point are you at now? Do you need an example to get started with, or feedback about existing code, or just ideas about which APIs to use? Best, Wade On Wed, Feb 11, 2009 at 4:55 PM, James Simmons mailto:jim.simm...@walgreens.com>> wrote: Benjamin, I had been using two machines to develop my Activities. One ran Xubuntu and used the sugar packages provided with the Sugar Live CD that someone made up. These were not perfect, but it was a simpler way to set up a Sugar test environment than anything else available at the time. My second box was running openSUSE 10.2 and I attempted to install Sugar-jhbuild on it with middling success. I had both pointing to the Collabora server to test sharing, and what I found was the sharing through that server worked OK for small files (like Read Etexts used) but took forever for slideshows, and frequently ran out of gas in the middle of a transfer. As for collaboration between two instances of Sugar with no jabber server between them, that never worked at all, even a little bit. As of last night both machines have Fedora 10 with the Sugar RPMs installed, so this should eliminate lots of problems I had in the past. I don't expect it to make large file transfers through the jabber server any faster, though. Plus, in my opinion copying a file from one XO to another would be better done as a function of the Journal. It isn't my idea of what real collaboration should be. The VNC idea, while worthwhile, doesn't excite me either. As an XO user I have no use for collaboration. I have nobody to play with. I could strip the collaboration code out of both my Activities and have something more than adequate for my own use. My goal is to create Activities that will get other kids excited about using them. My idea is a modest step
Re: Guidance sought on collaboration techniques
On 13 Feb 2009, at 16:16, Wade Brainerd wrote: > Hey James, > > FYI here is the collaboration code in Colors! > > http://git.sugarlabs.org/projects/colors/repos/mainline/blobs/master/colors.py#line641 > > It's fairly well commented but let me know if you have any questions > about how it works, or what you should do differently in Read Etexts. > > I totally agree that Etexts should be a killer app for the XO. > > As an aside, does anyone know if there is a manual way to force the > XO screen into sunlight mode? The below will switch to BW, but still leave the backlight on: su echo 1 > /sys/devices/platform/dcon/output And to kill backlight and go to BW mode all at once: su echo 0 > /sys/class/backlight/dcon-bl/brightness Hmmm, I wonder if there is dbus hooks for this for a less hacky solution. --Gary > -Wade > > On Thu, Feb 12, 2009 at 10:56 AM, James Simmons > wrote: > Wade, > > I'll have to check out the code in Colors! What I really need is > some sample code and some good docs on the APIs available. What I > have now was copied from the Read activity, and not all of it is > clear to me. If I understood what APIs were available that would be > a big help. I will welcome feedback on my code once I have > something good enough to criticize, but I'm not there yet. > > Thanks, > > James Simmons > > > > Wade Brainerd wrote: >> >> Hey James, >> >> I can help you out with this if you want. >> >> Your collaboration design sounds fine to me. I did something >> similar in Colors! where certain parts of the UI are disabled on >> the joining instances. >> >> What point are you at now? Do you need an example to get started >> with, or feedback about existing code, or just ideas about which >> APIs to use? >> >> Best, >> Wade >> >> On Wed, Feb 11, 2009 at 4:55 PM, James Simmons > > wrote: >> Benjamin, >> >> I had been using two machines to develop my Activities. One ran >> Xubuntu >> and used the sugar packages provided with the Sugar Live CD that >> someone >> made up. These were not perfect, but it was a simpler way to set >> up a >> Sugar test environment than anything else available at the time. My >> second box was running openSUSE 10.2 and I attempted to install >> Sugar-jhbuild on it with middling success. I had both pointing to >> the >> Collabora server to test sharing, and what I found was the sharing >> through that server worked OK for small files (like Read Etexts used) >> but took forever for slideshows, and frequently ran out of gas in the >> middle of a transfer. As for collaboration between two instances of >> Sugar with no jabber server between them, that never worked at all, >> even >> a little bit. >> >> As of last night both machines have Fedora 10 with the Sugar RPMs >> installed, so this should eliminate lots of problems I had in the >> past. >> I don't expect it to make large file transfers through the jabber >> server >> any faster, though. Plus, in my opinion copying a file from one XO >> to >> another would be better done as a function of the Journal. It >> isn't my >> idea of what real collaboration should be. The VNC idea, while >> worthwhile, doesn't excite me either. >> >> As an XO user I have no use for collaboration. I have nobody to play >> with. I could strip the collaboration code out of both my Activities >> and have something more than adequate for my own use. My goal is to >> create Activities that will get other kids excited about using >> them. My >> idea is a modest step in that direction. If I get that much working >> other ideas may come. >> >> I would like to stick with API's that are currently available for a >> couple of reasons: >> >> 1). I want to use the Sugar environment in Fedora 10. Now that I >> finally have a robust test environment I don't want to lose it. >> 2). I want to make the Activity available to the largest number of >> users possible. >> >> I think telepathy might do the job for me if I just understood it >> better. All I'm asking it to do is send some messages to a list of >> buddies and have them initiate some file transfers. Chat is already >> doing the first part, I think, and the Read code might be persuaded >> to >> do the second. >> >> Thanks, >> >> James Simmons >> >> >> ___ >> 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: Guidance sought on collaboration techniques
Hey James, FYI here is the collaboration code in Colors! http://git.sugarlabs.org/projects/colors/repos/mainline/blobs/master/colors.py#line641 It's fairly well commented but let me know if you have any questions about how it works, or what you should do differently in Read Etexts. I totally agree that Etexts should be a killer app for the XO. As an aside, does anyone know if there is a manual way to force the XO screen into sunlight mode? -Wade On Thu, Feb 12, 2009 at 10:56 AM, James Simmons wrote: > Wade, > > I'll have to check out the code in Colors! What I really need is some > sample code and some good docs on the APIs available. What I have now was > copied from the Read activity, and not all of it is clear to me. If I > understood what APIs were available that would be a big help. I will > welcome feedback on my code once I have something good enough to criticize, > but I'm not there yet. > > Thanks, > > James Simmons > > > > Wade Brainerd wrote: > > Hey James, > I can help you out with this if you want. > > Your collaboration design sounds fine to me. I did something similar in > Colors! where certain parts of the UI are disabled on the joining instances. > > What point are you at now? Do you need an example to get started with, > or feedback about existing code, or just ideas about which APIs to use? > > Best, > Wade > > On Wed, Feb 11, 2009 at 4:55 PM, James Simmons > wrote: > >> Benjamin, >> >> I had been using two machines to develop my Activities. One ran Xubuntu >> and used the sugar packages provided with the Sugar Live CD that someone >> made up. These were not perfect, but it was a simpler way to set up a >> Sugar test environment than anything else available at the time. My >> second box was running openSUSE 10.2 and I attempted to install >> Sugar-jhbuild on it with middling success. I had both pointing to the >> Collabora server to test sharing, and what I found was the sharing >> through that server worked OK for small files (like Read Etexts used) >> but took forever for slideshows, and frequently ran out of gas in the >> middle of a transfer. As for collaboration between two instances of >> Sugar with no jabber server between them, that never worked at all, even >> a little bit. >> >> As of last night both machines have Fedora 10 with the Sugar RPMs >> installed, so this should eliminate lots of problems I had in the past. >> I don't expect it to make large file transfers through the jabber server >> any faster, though. Plus, in my opinion copying a file from one XO to >> another would be better done as a function of the Journal. It isn't my >> idea of what real collaboration should be. The VNC idea, while >> worthwhile, doesn't excite me either. >> >> As an XO user I have no use for collaboration. I have nobody to play >> with. I could strip the collaboration code out of both my Activities >> and have something more than adequate for my own use. My goal is to >> create Activities that will get other kids excited about using them. My >> idea is a modest step in that direction. If I get that much working >> other ideas may come. >> >> I would like to stick with API's that are currently available for a >> couple of reasons: >> >> 1). I want to use the Sugar environment in Fedora 10. Now that I >> finally have a robust test environment I don't want to lose it. >> 2). I want to make the Activity available to the largest number of >> users possible. >> >> I think telepathy might do the job for me if I just understood it >> better. All I'm asking it to do is send some messages to a list of >> buddies and have them initiate some file transfers. Chat is already >> doing the first part, I think, and the Read code might be persuaded to >> do the second. >> >> Thanks, >> >> James Simmons >> >> >> ___ >> 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: Speech-dispatcher, etextRead activity and espeak
Tony, Last night I was able to do a yum install of speech-dispatcher and speech-dispatcher-python in Fedora 10, so there is a good chance that the same thing would work on the XO. I have not tried it. The install will bring in festival-lite, at about 7 megabytes, which you shouldn't need and may be able to uninstall later. (On the other hand, if it works better than espeak it might be worth keeping). The configuration files are in the /etc/speech-dispatcher directory and they look mostly OK. They have an entry to load Festival which you should probably comment out since you won't have Festival installed. Unfortunately, when I tried starting it up with this command: speech-dispatcher -d it complained about ALSA not being able to connect to the sound device because of some issue with Pulse-Audio. It sounds kind of like the problem described here: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/213755 There is a page on the OLPC Wiki that mentions speech-dispatcher: http://wiki.laptop.org/go/Screen_Reader This page is out of date and it incorrectly suggests setting up espeak-generic, which does NOT support the callbacks needed for Karaoke highlighting. If I can figure out how to get SD working with Fedora 10 or the XO I will update this page. I'll also update the page for Read Etexts. Until then just be aware it's wrong. If you want to have a crack at solving this yourself, please go ahead. I don't have any special expertise for installing SD. Thanks, James Simmons Tony Anderson wrote: > Hi, > > The educational team at OLENepal would like a 'karaoke-style' text > reader above all other activities on the XO. This is primarily for > English. Looking at the activity code, it looks like the speech code > is there but disabled. > > Would it be possible to release a version that supports espeak without > the Speech-Dispatcher pending its implementation in Sugar? This would > give us a chance to experiment with creating 'read-aloud' stories. > > Tony > > > > > Thanks for your response. I never questioned that there was still > > interest in TTS on the XO. What I was wondering is if there was any > > progress made by Hemant Goyal or anyone else in getting the > > Speech-Dispatcher software included with the Sugar distribution, if the > > newer version of Python that resolved the power management issue was > > included, etc. I've sent a couple of emails to Hemant and haven't > heard > > back from him. I was wondering if he was still working on these > things, > > or if someone else had taken over his work, etc. He was making RPMs > for > > Fedora for installing speech-dispatcher. > > > > James Simmons > ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] XS 0.5.1 RC - Last round of testing...
On Fri, Feb 13, 2009 at 8:30 PM, Sameer Verma wrote: > I've circumvented the realtek 8139 problem by appending irqpoll in > grub.conf That seems to work, although I have to bring up eth0 > manually and issuing dhcient eth0 Good to hear irqpoll works. Strange that dhclient doesn't work on network start... > I still hit the bug of _sha256 as mentioned here: > https://bugzilla.redhat.com/show_bug.cgi?id=454179 That bug is bizarre. I've installed 0.5.1 on several machines without hitting this at all. No idea whatcould it be - package that reportedly caused that bug has long been fixed... what versions of those pkgs does rpm -qa say you have? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] [PATCH] webactivity: seed the XS cookie at startup
On Fri, Feb 13, 2009 at 7:07 AM, Carol Farlow Lerche wrote: > Martin, I want to understand what https traffic you are concerned will > affect performance and caching. As far as I understand the need for https, > it would only be used infrequently, when reauthenticating to the server. > I.e..: What you describe was the plan B in my earlier postings. It first does crypto, and then falls back to a totally MITM'able cleartext cookie. So the crypto is just a lot of programming work for a tiny gain. >From a security standpoint, we either do https with client side cert, or we relax and use plaintext cookies. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
