Re: upgarde with olpc-update
On 27 May 2011 22:05, Yioryos Asprobounitis mavrot...@yahoo.com wrote: Is it possible to upgrade the XO-1 to 11.2.0 builds from 10.1.3 or earlier builds as the wiki page suggests? [1] Someone did try it and run into problems beyond the space limitation [2] Oops, I read this too quickly. It's not the space limitation, its a separate issue. Filed as http://dev.laptop.org/ticket/10929 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: stop sharing an activity
On Sat, May 28, 2011 at 08:25:57AM -0700, Yioryos Asprobounitis wrote: I could not find a way to stop sharing an activity even when no peers are connected or even present. Yes, intentional. sugar-toolkit.git/src/sugar/activity/widgets.py class ShareButton, method __update_share_cb, once the activity is shared the private and neighborhood (sic) buttons are marked insensitive. http://git.sugarlabs.org/sugar-toolkit/mainline/blobs/master/src/sugar/activity/widgets.py#line154 This was true in os860 and os20, XO-1 and XO-1.5 and activities like write and Turtle blocks. As it is a function of the toolkit, it will be true for all activities that use the toolkit, probably regardless of the activity version. (The toolkit provides the default behaviour. I see no reason why an activity could not implement a stop-sharing feature, but I have seen no such implementation yet.) For os860, which is Sugar 0.84, sugar-toolkit.git/src/sugar/activity.py class ActivityToolbar method _update_share() forces the button to be insensitive. http://git.sugarlabs.org/sugar-toolkit/mainline/blobs/sucrose-0.84/src/sugar/activity/activity.py#line159 The same is true in Sugar 0.82 used in OLPC OS 8.2.1 build os802. If this is indeed a feature and not a bug or something I miss, could someone point me to the relevant discussion and/or rational of once public, always public? I don't know where that discussion might be, but the concept follows the maxim that once information is released there's no going back. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
problem solved (Re: new OLPC slackware 13.37 released (fwd)
I just solved all problems exist in OLPC Slackware 13.37 below is content on my d/l at http://e-university.eu.org/OLPC/ Index of /OLPC * Parent Directory * 2.6.35.3.tgz * bzImage * howto.txt * initrd.gz * olpc.fth * olpc_slak13.37.tar.bz2 * slack13.37.hint.txt Actually reason KDE did not work under OLPC was written in slack13.37.hint.txt It need to put below config: Section Extensions Option Composite Disable EndSection in the file: /etc/X11/xorg.conf.d/disable-composite.conf I compile new OLPC kernel using exactly recent OLPC kernel You should replace /lib/modules with .tgz I gave on my d/l also cp olpc.fth I gave to your /boot Don't forget to replace with new bzImage and initrd.gz Regards, supat On Wed, 25 May 2011, da...@lang.hm wrote: so where do I get this slackware image for the OLPC from? David Lang On Sat, 21 May 2011, su...@supat.eu.org wrote: -- Forwarded message -- Date: Sat, 21 May 2011 20:47:55 +0700 (ICT) From: su...@supat.eu.org To: johnny nunez esmiwu...@gmail.com Subject: new OLPC slackware 13.37 released Features: 1. on USB with full slackware 13.37 will boot on OLPC 2. support all SW in slackware 13.3 plus open office and NX client 3. support KDE but OLPC 1.0 is too slow so fluxbox is a prefered WM 4. the same USB can boot on all pc in this world with all HW support as slackware 13.37 can do. Regards, supat On Mon, 11 Oct 2010, johnny nunez wrote: Hi Supat, Thank you for your time. I hope this attachments will help you to locate the image. Regards, J.N On 10/11/10, su...@supat.eu.org su...@supat.eu.org wrote: Dear johnny nunez, Sorry for late reply because your mail has no topic and I got a lot of junk mail. I mostly delete them w/o reading. Fortunately I hit the wrong key so I accidentally see your message below. I invent slackware OLPC in 2006. The last person who ask for it is 4 years ago because current support of OLPC is not in slackware. I think no one will interest it. I forget where I put those slackware OLPC in and I change servers several times in the past 4 years. I don't know how many servers I have. So, you have to inform me where did you get info from and what did it said. In original message it should have a clue where I put it. Or it can make me remember where is the imgage of it. Regards, supat On Sun, 10 Oct 2010, johnny nunez wrote: hi i want to find olpc slackware image ___ 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: stop sharing an activity
--- On Sun, 5/29/11, James Cameron qu...@laptop.org wrote: I don't know where that discussion might be, but the concept follows the maxim that once information is released there's no going back. Thanks for the detailed info. For sure once information is released there is no going back, but I do not think activity sharing/collaboration is anything close to that as a concept or practice. Today other collaboration tools allow not only collaboration to stop but also who and how to collaborate. I can see many scenarios in and out of a class that may need that feature and I'm actually surprised is not(?) brought up by any deployment yet. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: stop sharing an activity
On Sun, May 29, 2011 at 10:36:21PM -0700, Yioryos Asprobounitis wrote: For sure once information is released there is no going back, but I do not think activity sharing/collaboration is anything close to that as a concept or practice. Today other collaboration tools allow not only collaboration to stop but also who and how to collaborate. I can see many scenarios in and out of a class that may need that feature and I'm actually surprised is not(?) brought up by any deployment yet. No worries. Perhaps you might check for or create a ticket with Sugar Labs? Describe these other tools that allow collaboration to stop, why they do so, and the scenarios you envision. Perhaps it has been brought up by a deployment, but I don't have a comprehensive list of deployment feedback items. You might also check with your deployment contacts. -- James Cameron http://quozl.linux.org.au/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
