Re: [Sugar-devel] Jaunty up and running
Hi guys Yesterday I updated sugar and rebuilt after cleaning the install dir, the sugar now runs without my hack. Thanks Silbe. I dont know why it works, but it works. Hopefully, one day I will understand this. But for now, we will just believe in luck. I am working on integrating the debian packaging stuff directly into the sugar-jhbuild and will report back when I have sugar-base integration. thanks, mike ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Background Screen Color for SoaS Activity
On Tue, Jul 7, 2009 at 04:46, Art Hunkins wrote: > Tomeu, > > I've had no luck modifying background color for anything except buttons. > > No boxes, even when the box is completely empty. > > Does anyone know how to change the color of the entire screen, or of a box? I have done it routinely, can you share the whole code of your activity class? Regards, Tomeu > Art Hunkins > > - Original Message - From: "Tomeu Vizoso" > To: "Art Hunkins" > Cc: > Sent: Monday, July 06, 2009 4:26 AM > Subject: Re: [Sugar-devel] Background Screen Color for SoaS Activity > > >> On Mon, Jul 6, 2009 at 06:19, Art Hunkins wrote: >>> >>> The default color for the Sugar Activity screen seems to be set to light >>> gray. I'd like mine to be white. >>> >>> Is there any way to change this in my activity script? >> >> That looks good to me, perhaps ibox contains some other widget that is >> covering it completely? >> >> Regards, >> >> Tomeu >> >>> I tried: >>> >>> import gtk >>> >>> win = csndsugui.CsoundGUI(self) >>> ibox = win.box(False) >>> ibox.modify_bg(gtk.STATE_NORMAL, gtk.gdk.Color(0x, 0x, 0x)) >>> >>> where ibox = the entire screen. >>> >>> However this changed nothing. >>> >>> Anything fairly straightforward I could try? >>> >>> Art Hunkins >>> >>> ___ >>> 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] [Marketing] [Server-devel] [SoaS] The next Step: v2 Roadmap
On Sun, Jul 5, 2009 at 15:53, Rodolfo D. Arce S. wrote: > Hello all: > > I'm actually not working solely with Sugar, but with the OLPC > deployment and the XS.. > > The feature that i found to be more important is the re-installing of > the operative systrem, beacuse the whole platform is still a little > unstable, the OS reinstall is very usefull.. but the restore of the > journal is very VERY complicated > > Daniel Drake made a couple of scripts that were very usefull, which > restores a journal to a temp folder.. and when booting looks for that > temp folder in order to restore > > If i tryed to do it manually.. is very long and complicated process.. > do-able, but if i think of a 9 year old doing it.. well.. it could be > to hard > > So I think that is someting that we shloud be aiming at.. simple > journal backup and restore.. and not only in an OLPC, or XS > envoiroment for that matter.. so even in places without XS (for > backup) or where reinstall is a fast and easy way to get a system up > again.. the journal is the only place where all things are stored Hi Rodolfo, have you already thought about the ideal user experience for that? Thanks, Tomeu > cheers.. R > > On Sat, Jul 4, 2009 at 8:47 PM, Caroline Meeks wrote: >> Hi, >> I am going to try to answer this, or actually I hope start a brainstorming >> session that will get us towards a feature list. >> I am going to try to use the Customer Role of an Agile process. That means >> I'm going to try to talk as much about the result I want to see as I can and >> as little as I can about how to get to it. I do know that some of this is >> in the works. I also know that some of it will require the heavens to >> deliver us yet another genius programmer with a new skill set to accomplish >> by September. But the job of the role of Customer is my mind is to talk >> about what I'd like to see, what the business case for it is and what the >> priority is. I hope other people will join me in this role as i think its >> crucial information for the technical team to have. >> Solid Collaboration - Priority A for GPA Project. - Defining what this looks >> like and how we get there is an important discussion and i don't have all >> those answers. This encompasses local and jabber collaboration. >> Straightforward Teacher "Assignment" -> Student -> Teacher >> workflow. Priority B for GPA For example. Teacher creates a template >> to scaffold student writing. Students do the writing assignment and the >> teacher "collects" them. Maybe this happens with Moodle or maybe its done >> all in Sugar? >> Straightforward Sugarization - By this I mean that a programmer who has >> created a game for linux or the web could look at our documentation and >> examples and tell his/her boss, "yes I see how we can make this available >> for Sugar and it will be a better experience for kids in a classroom through >> Sugar." Sugarizing should not mean giving up aggregating data for the >> teacher. It should be a better user experience because: automatic saving, >> cooler collaboration, easier installation and more consistent performance, >> easier for teachers to find, available to the million kids with XOs. >> .Priority A for Sugar. >> Sugar on SoaS and Netbooks backs up and restores with XS - Priority A for >> GPA, >> Sugar Live CD - Boothelper - USB Creator all in one - Priority B for SoaS >> Sugar on a Stick works with a VM - Priority B for GPA - it still has to >> boot on its own also. >> A Sugar machine can also run a SoaS - Priority C - Use case. Say you are in >> a 1-1 Netbook deployment. Your netbook breaks and it'll be a week till its >> repaired. It would be cool to burn a Stick for that kid from the XS backup >> and they could then use a teacher's netbook or some kid who is in Gym that >> period's netbook and still get to participate in the lesson. >> Sugar works on preIntel Macs - Priority C for GPA, Priority B for Sugar. >> Sugar works on lesser hardware, say Pentium III 256M. - Priority C for SoaS >> Don't let the user keep opening activities until the machine crashes or is >> driven to its knees - Priority C for GPA >> Less cluttered, more consistent neighborhood view - Priority C for Sugar >> I am copying the Server list because I think many of the things I think are >> the most important next steps for Sugar require interfacing with, and >> improvements in the XS. >> Priorities are my current opinions and I tried to not bias them with how >> hard I think the tasks are. They are about how important I think they are, >> in my opinion, with my customer hat on, to either the GPA pilot, Sugar and >> its marketing, and partnerships and adoption, or the Sugar on a Stick >> project. I don't think for a second that things should be done in priority >> order. >> So I hope everyone else sticks their necks out and says what features they >> want, what the use cases are and what they think their relative importance >> are. Then we can narrow our focus back do
Re: [Sugar-devel] Good filesystem for USB flash with compression?
Sorry, I should've read the question more carefully. Perhaps JFFS2 works on USB flash after all? Besides btrfs which is very primitive ATM, I don't know other compressed FSs. 2009/7/7 Luke Faraone : > On Mon, Jul 6, 2009 at 21:00, Lucian Branescu > wrote: >> >> Basically any FS that works on all the OSes you need. ext2 is a good >> option. NTFS might be, but it's fiddly. > > I don't really care about compatibility, rather I need something that will > work on Linux systems, and something with compression. > > > > -- > Luke Faraone > http://luke.faraone.cc > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Backup and Restore Feature added to Wiki
Hi All, I created a Feature request for backup and restore here: http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore I'm still not sure how to "tie" it to GPA or a release or pile of pending feature requests. If anyone knows the right wiki markup to do that, please go ahead. I'll watch what you do and use it for the next one. I made myself the "owner" but it should probably be someone smarter than me and able to program, maybe Martin...? Any comments or questions on the feature are welcome. It occurred to me as I was writing it that this problem must have been solved already in Linux. If anyone knows a good solution there, lets take it! That will solve most of the problem leaving us with the special case of the DataStore/Journal. Comments on format and more accurate filling out of the template also appreciated. >From this list http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals, I'll work on "collaboration" next. That is such a tough nut that I may fill in a few priority B items too for practice. HTHs. Thanks, Greg S ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Background Screen Color for SoaS Activity
Hi Art,
On 7 Jul 2009, at 03:46, Art Hunkins wrote:
> Tomeu,
>
> I've had no luck modifying background color for anything except
> buttons.
>
> No boxes, even when the box is completely empty.
>
> Does anyone know how to change the color of the entire screen, or of
> a box?
I can remember hitting my head on this when first playing with gtk. I
wanted a black area to place a moon image in. The trick seems to be
using a gtk.EventBox(). Have a look in moon.py at about line #114:
http://git.sugarlabs.org/projects/moon/repos/mainline/trees/master
Just quickly scraped out the lines I think might be interesting, does
seem quite a bit for just a black screen :-)
# Create the main activity container
self.main_view = gtk.HBox()
# Blackness
self.event_box = gtk.EventBox()
colormap = gtk.gdk.colormap_get_system()
self.black_alloc_color = colormap.alloc_color('black')
self.event_box.modify_bg(gtk.STATE_NORMAL, self.black_alloc_color)
self.main_view.pack_end(self.event_box)
# Display everything
self.event_box.show()
self.main_view.show()
self.set_canvas(self.main_view)
self.show_all()
Regards,
--Gary
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SoAS Testing with XS
Hi Caroline et al, That helps. I noted four possible network configuration here: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals#Solid_Collaboration I have to warn you that this is very hard area. It reminds me of trying to catch minnows in Herring Pond with my son. You scoop the bucket in to a school of them but they always slip away by the time you pull it out of the water. Here's one of my previous attempts to snare the slippery fish: http://wiki.laptop.org/go/9.1.0_Collaboration_Requirements That said, taking out the wireless variable will really help! How about we write down a set of use cases from user, GUI interaction level. These can turn in to test cases. Here's one basic one: Environment: - 10 or fewer Sugar computers collaborating locally on a LAN no server (case 1 from Goals page). - LAN includes Hub (no switch?) Use case: - All computers boot up (any configurations/setting needed?) - All computers see each other in the network neighborhood - One computer starts the chat activity - Other computers see the chat in the network neighborhood and join - All 10 can chat at the same time. What other details is that case missing? SW version numbers and computer HW? If we write down a few simple cases which we can reproduce quickly that will help. To support the server cases, I think we need two test servers (one for in school and one on internet). We also need 1 - 3 adventurous sys admins to help manage them. I'll ask around but I don't know anyone for sure. Anyone on the list want to help? Doesn't have to be local to Boston but we could use ~10 hours/week and experience locking down/protecting public servers. The high level goal is to have test beds in support of GPA. Caroline is in charge of interaction with the school IT department and anything actually in the school. The additional servers and admins are to mirror that, run tests and validate configurations as needed. Sort of a tier two plus bleeding edge type support. Thanks, Greg S > > Caroline, The long term goal is that students at GPA can collaborate with each other from school and home. Thus long term we need a Jabber server and a machine connected to the internet. We could host it at Solution Grove or physically locate it at the school. I think learning about the tradeoffs between these approaches is one of our goals for the pilot. For this summer if we got collaboration working locally in the Computer Room we'd have a better experience then the current no collaboration. We have an extra computer we can use as an XS. I'll need to buy/scavange another network card. Does that help? Thanks, Caroline > > > Can you confirm the target implementation for GPA is SoAS computers > collaborating with each other via Jabber? > > There are so many sub-components to this section of SW that we will > need your help to focus on the right area. > > Will the Jabber server be in the school or over a WAN to a public > (internet IP addressable) place? > > I'll try to document your answers on the Wiki. > > HTHs. > > Thanks, > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Tue, Jul 7, 2009 at 16:05, Greg Smith wrote: > Hi All, > > I created a Feature request for backup and restore here: > http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore Shouldn't this be already working in SoaS 0.84 with XS 0.6? May be waiting for someone to give it a tray. CC'ing Martin and Dave who may have already tried it. Regards, Tomeu > I'm still not sure how to "tie" it to GPA or a release or pile of > pending feature requests. If anyone knows the right wiki markup to do > that, please go ahead. I'll watch what you do and use it for the next > one. > > I made myself the "owner" but it should probably be someone smarter > than me and able to program, maybe Martin...? > > Any comments or questions on the feature are welcome. It occurred to > me as I was writing it that this problem must have been solved already > in Linux. If anyone knows a good solution there, lets take it! That > will solve most of the problem leaving us with the special case of the > DataStore/Journal. > > Comments on format and more accurate filling out of the template also > appreciated. > > From this list http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals, > I'll work on "collaboration" next. That is such a tough nut that I may > fill in a few priority B items too for practice. > > HTHs. > > Thanks, > > Greg S > ___ > 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] Background Screen Color for SoaS Activity
Tomeu and Gary, Thanks for your advice and interest. I've attached my complete activity (OurMusic) in the form of an .xo archive. Note that it requires csndsugui.py (included), Victor Lazzarini's "Csound GUI toolkit." It's barely possible that the color issue lies therein (but unlikely). The background color issue is the only issue when the activity is run on OLPC; on SoaS, there is another as well: an "unavailable" csnd or _csnd module (from python 2.6). For the latter issue, Aleksey suggested a Scons-related fix (that I've yet to be able to implement, unfortunately, as my technical expertise is *highly* limited). If you manage to get an initial display on a white background, I'd be most grateful. If you do have/get a display, probably options 2 and 4 will work for you; they use only the ASCII keyboard, no MIDI controllers (unlike 1 and 3). I'd be delighted if these worked on SoaS. Gary, I'll be trying your code as well. I presume it should go near the beginning in my main loop? (Sorry, my grasp of both python and GTK -- OOP for that matter -- is so minimal.) Art Hunkins - Original Message - From: "Tomeu Vizoso" To: "Art Hunkins" Cc: Sent: Tuesday, July 07, 2009 4:55 AM Subject: Re: [Sugar-devel] Background Screen Color for SoaS Activity On Tue, Jul 7, 2009 at 04:46, Art Hunkins wrote: Tomeu, I've had no luck modifying background color for anything except buttons. No boxes, even when the box is completely empty. Does anyone know how to change the color of the entire screen, or of a box? I have done it routinely, can you share the whole code of your activity class? Regards, Tomeu Art Hunkins - Original Message - From: "Tomeu Vizoso" To: "Art Hunkins" Cc: Sent: Monday, July 06, 2009 4:26 AM Subject: Re: [Sugar-devel] Background Screen Color for SoaS Activity On Mon, Jul 6, 2009 at 06:19, Art Hunkins wrote: The default color for the Sugar Activity screen seems to be set to light gray. I'd like mine to be white. Is there any way to change this in my activity script? That looks good to me, perhaps ibox contains some other widget that is covering it completely? Regards, Tomeu I tried: import gtk win = csndsugui.CsoundGUI(self) ibox = win.box(False) ibox.modify_bg(gtk.STATE_NORMAL, gtk.gdk.Color(0x, 0x, 0x)) where ibox = the entire screen. However this changed nothing. Anything fairly straightforward I could try? Art Hunkins ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel OurMusic-1.xo Description: Binary data ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Tue, Jul 7, 2009 at 10:21 AM, Tomeu Vizoso wrote: > On Tue, Jul 7, 2009 at 16:05, Greg Smith wrote: >> Hi All, >> >> I created a Feature request for backup and restore here: >> http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore > > Shouldn't this be already working in SoaS 0.84 with XS 0.6? > > May be waiting for someone to give it a tray. CC'ing Martin and Dave > who may have already tried it. We need 1) changes to allow registering soas to an XS 2) ds-backup-client patched to work on soas 3) ds-backup-client installed on soas. I believe there are outstandings tickets for this. I guess these changed need to be made in the fedora packages so we can pull them into soas. Dave > > Regards, > > Tomeu > >> I'm still not sure how to "tie" it to GPA or a release or pile of >> pending feature requests. If anyone knows the right wiki markup to do >> that, please go ahead. I'll watch what you do and use it for the next >> one. >> >> I made myself the "owner" but it should probably be someone smarter >> than me and able to program, maybe Martin...? >> >> Any comments or questions on the feature are welcome. It occurred to >> me as I was writing it that this problem must have been solved already >> in Linux. If anyone knows a good solution there, lets take it! That >> will solve most of the problem leaving us with the special case of the >> DataStore/Journal. >> >> Comments on format and more accurate filling out of the template also >> appreciated. >> >> From this list http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals, >> I'll work on "collaboration" next. That is such a tough nut that I may >> fill in a few priority B items too for practice. >> >> HTHs. >> >> Thanks, >> >> Greg S >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Choosing to merge: a mockup
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mockup: http://dev.laptop.org/~bemasc/merge_share_selection_mockup.png Idea: If I resume an Activity session from my Journal, and there is already a session in progress with the same activity_id, and the Activity in question supports automerge, then Sugar will show me the above screen, asking me whether I want to merge my work with the shared session, or to work alone. This is enough to enable basic asynchronous collaboration. The screen simply has two buttons. One is the image of the shared session in question, identical to the one shown in the Neighborhood View. The other is an image of my XO icon. The text below each button explains its purpose, and also gives the name of the shared session and the local session, as these may have diverged. Knowing the names may help the user to decide whether or not to merge. As I understand it, the current activity architecture requires an activity to know if it is a joining a shared session as soon as initialization begins, so activity startup cannot proceed until the user makes a choice. A rounded-corner highlight box indicates the currently selected button, in a manner consistent with the rest of the UI, hopefully enabling simple keyboard shortcuts. The default selection may be based on a heuristic to predict whether the user is likely to join the shared session. For example, the default selection may be to merge if the local copy is the latest local version, and to remain separate if it is not. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkpTkBUACgkQUJT6e6HFtqT8XACbBAa91c6oIvZvQYfJQvmIe6ht LdIAoJfmeKU0VWvuK8gjeHvNbK8yKmur =8W9M -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
Dave Bauer wrote: > On Tue, Jul 7, 2009 at 10:21 AM, Tomeu Vizoso wrote: >> On Tue, Jul 7, 2009 at 16:05, Greg Smith wrote: >>> Hi All, >>> >>> I created a Feature request for backup and restore here: >>> http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore >> Shouldn't this be already working in SoaS 0.84 with XS 0.6? >> >> May be waiting for someone to give it a tray. CC'ing Martin and Dave >> who may have already tried it. > > We need 1) changes to allow registering soas to an XS > 2) ds-backup-client patched to work on soas > 3) ds-backup-client installed on soas. > > I believe there are outstandings tickets for this. I guess these > changed need to be made in the fedora packages so we can pull them > into soas. Yup, there's a ticket: #916 Well, the "problem" is that ds-backup-* hasn't been packaged for Fedora, yet. I discussed this with Martin Langhoff (adding to CC here) at LinuxTag lately, and it shouldn't be a big problem to get the patches from Hamilton (in the ticket) applied and then a new RPM uploaded to our SoaS yum repo. I guess we'd need people testing this once it's ready, though. --Sebastian > Dave >> Regards, >> >> Tomeu >> >>> I'm still not sure how to "tie" it to GPA or a release or pile of >>> pending feature requests. If anyone knows the right wiki markup to do >>> that, please go ahead. I'll watch what you do and use it for the next >>> one. >>> >>> I made myself the "owner" but it should probably be someone smarter >>> than me and able to program, maybe Martin...? >>> >>> Any comments or questions on the feature are welcome. It occurred to >>> me as I was writing it that this problem must have been solved already >>> in Linux. If anyone knows a good solution there, lets take it! That >>> will solve most of the problem leaving us with the special case of the >>> DataStore/Journal. >>> >>> Comments on format and more accurate filling out of the template also >>> appreciated. >>> >>> From this list http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals, >>> I'll work on "collaboration" next. That is such a tough nut that I may >>> fill in a few priority B items too for practice. >>> >>> HTHs. >>> >>> Thanks, >>> >>> Greg S >>> ___ >>> 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] [Cs-dev] Sugar on a Stick - and OLPCsound/Csound
Thanks, Mike. Please let me know how this develops. I'm really eager to get 5.10 working on SoaS. As it is, I gather, Csound is not available for use on SoaS, and only still works on the OLPC because they are at 5.08. I'm so much wanting 5.10 because it's the one that permits multiple MIDI controllers, and I've got to offer my Sugar activity either with *or* without this multiple. I'm betwixt and between currently, but since SoaS has already committed to 5.10 making Csound not work at all, I guess I'll just keep my patient hat on for a while. OTOH, do keep me appraised. I have joined the Sugar development list, and can perhaps help move things along on that side. Art Hunkins - Original Message - From: "Michael Gogins" To: "Art Hunkins" ; "Developer discussions" Sent: Tuesday, July 07, 2009 3:13 PM Subject: Re: [Cs-dev] Sugar on a Stick - and OLPCsound/Csound > He says SConstruct has a bug, which he has patched. I think he's > probably right, and I will patch SConstruct accordingly. > > The bug makes the installation not know the right name (soname) for > the csnd extension module shared library. > > Regards, > Mike > > On 7/6/09, Art Hunkins wrote: >> Victor and Mike G. (especially) - >> >> You're familiar with my problems getting Csound5.10 working on SoaS. >> >> Aleksey, one of the Sugar developers, sent me the "solution" (below) to >> this >> problem (a Scons issue apparently). >> >> I don't know what to do with it, and look to you for either >> implementation >> or explanation. >> >> I'm really interested to get 5.10 working with Sugar. >> >> Art Hunkins >> >> - Original Message - >> From: "Aleksey Lim" >> To: "Art Hunkins" >> Cc: ; ; >> >> Sent: Monday, July 06, 2009 3:37 AM >> Subject: Re: [Sugar-devel] Sugar on a Stick - and OLPCsound/Csound >> >> >>> looks like its a SConstruct issue >>> https://sourceforge.net/tracker/index.php?func=detail&aid=2817271&group_id=81968&atid=564599 >>> >>> this patch fixed "import csnd" in my case >>> http://git.sugarlabs.org/projects/jhconvert/repos/mainline/blobs/master/patches/csound-2817271-soname.patch >>> >>> On Sun, Jul 05, 2009 at 05:49:23PM -0400, Art Hunkins wrote: As mentioned by a member of the sugar-devel list, it seems that a csound (5.10) install (yum install csound), does not install several crucial site-specific and library packages (csnd, _csnd, libcsnd and perhaps libcsound). Having to erase olpcsound before installing csound deletes these files and they don't get restored/reinstalled. So, to the procedures described below, before erasing olpcsound, I saved the above-listed files (there were 5 or 6), and once csound was installed, added them back where they came from. This crude procedure didn't work, and the following error log is quite like the one I started with: /usr/lib/python2.6/site-packages/sugar/util.py:25: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Traceback (most recent call last): File "/usr/bin/sugar-activity", line 21, in main.main() File "/usr/lib/python2.6/site-packages/sugar/activity/main.py", line 105, in main module = __import__(module_name) File "/home/liveuser/Activities/OurMusic.activity/ourmusic.py", line 41, in import csndsugui File "/home/liveuser/Activities/OurMusic.activity/csndsugui.py", line 36, in import csnd File "/usr/lib/python2.6/site-packages/csnd.py", line 7, in import _csnd ImportError: /usr/lib/libcsnd.so.5.1: undefined symbol: csoundGetInputBuffer I'd appreciate any suggestions as to how to get this all working. Thanks. Art Hunkins - Original Message - From: Art Hunkins To: pbrobin...@gmail.com Cc: cso...@lists.bath.ac.uk ; sugar-devel@lists.sugarlabs.org Sent: Friday, July 03, 2009 7:57 PM Subject: Re: [Cs-dev] Sugar on a Stick - and OLPCsound I've just noted that the /usr/lib/python2.6/site-packages folder does not include csnd.py. That folder also contains many fewer files that the corresponding one in python2.5. As a matter of fact, python2.5 seems about a third the size of 2.6. Is all this correct? Art Hunkins - Original Message - From: Art Hunkins To: pbrobin...@gmail.com Sent: Friday, July 03, 2009 6:13 PM Subject: Fw: [Cs-dev] Sugar on a Stick - and OLPCsound Hello, Peter, Do you know what may be happening here? (Please see error log below.) I've no idea why the module referenced (csd.py) is not found. Please also compare the log at the very bottom of this mail; this latter log
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Wed, Jul 8, 2009 at 8:24 AM, Sebastian Dziallas wrote: > Yup, there's a ticket: #916 > > Well, the "problem" is that ds-backup-* hasn't been packaged for Fedora, > yet. I discussed this with Martin Langhoff (adding to CC here) at LinuxTag > lately, and it shouldn't be a big problem to get the patches from Hamilton > (in the ticket) applied and then a new RPM uploaded to our SoaS yum repo. I > guess we'd need people testing this once it's ready, though. I'll look at the patches and see about merging them in a ds-backup-client that works on both old and new Sugar. If it all works, I'll update the rpm packages. They won't be in Fedora repos, but I'm the maintainer of them. Sebastian seemed happy with such arrangement. IMHO, to make this work really well from a user PoV, we'd need a Sugar control panel that exposes: - when was last successful / complete backup - "backup in process" status - "start backup now" button - "full restore now" button (hooked up with dsd's scripts?) cheers, martin -- 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
[Sugar-devel] GPA XS Report
Today at the Gardner Pilot Academy we tried setting up an XS school server. We were able to install the software (version 0.5.2) using the cd image that's on the wiki. We then set the host name and enabled the ejabberd service so it would start automatically upon boot. When we checked the status of ejabbered it showed that ejabbered was running and everything seemed to be fine. We booted several computers with SoaS and changed the network settings from the default (jabber.sugarlabs.org) to the IP address on the XS. After doing this, the computers in the computer lab still would not recognize each other and there was no collaboration. However after running several commands on the the XS we were able to see that computers were able to connect to the server but were not able to see each other. Any ideas on what we can do to make this work as collaboration will really maximize the potential of Sugar. Caroline, please add any details I might have left out. Thanks, Anurag Goel -- Anurag Goel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Tue, Jul 7, 2009 at 5:31 PM, Martin Langhoff wrote: > On Wed, Jul 8, 2009 at 8:24 AM, Sebastian Dziallas wrote: >> Yup, there's a ticket: #916 >> >> Well, the "problem" is that ds-backup-* hasn't been packaged for Fedora, >> yet. I discussed this with Martin Langhoff (adding to CC here) at LinuxTag >> lately, and it shouldn't be a big problem to get the patches from Hamilton >> (in the ticket) applied and then a new RPM uploaded to our SoaS yum repo. I >> guess we'd need people testing this once it's ready, though. > > I'll look at the patches and see about merging them in a > ds-backup-client that works on both old and new Sugar. If it all > works, I'll update the rpm packages. They won't be in Fedora repos, > but I'm the maintainer of them. Sebastian seemed happy with such > arrangement. > Ok thanks for that information. That works for me. We will be ready to test it. > IMHO, to make this work really well from a user PoV, we'd need a Sugar > control panel that exposes: > > - when was last successful / complete backup > - "backup in process" status > - "start backup now" button > - "full restore now" button (hooked up with dsd's scripts?) Thanks for those ideas. I think that might be someplace I could learn Sugar development. Dave > > cheers, > > > > martin > -- > 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 > -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Tue, Jul 7, 2009 at 5:59 PM, Dave Bauer wrote: > On Tue, Jul 7, 2009 at 5:31 PM, Martin > Langhoff wrote: > > On Wed, Jul 8, 2009 at 8:24 AM, Sebastian Dziallas > wrote: > >> Yup, there's a ticket: #916 > >> > >> Well, the "problem" is that ds-backup-* hasn't been packaged for Fedora, > >> yet. I discussed this with Martin Langhoff (adding to CC here) at > LinuxTag > >> lately, and it shouldn't be a big problem to get the patches from > Hamilton > >> (in the ticket) applied and then a new RPM uploaded to our SoaS yum > repo. I > >> guess we'd need people testing this once it's ready, though. > > > > I'll look at the patches and see about merging them in a > > ds-backup-client that works on both old and new Sugar. If it all > > works, I'll update the rpm packages. They won't be in Fedora repos, > > but I'm the maintainer of them. Sebastian seemed happy with such > > arrangement. > > > > Ok thanks for that information. That works for me. We will be ready to test > it. > > > IMHO, to make this work really well from a user PoV, we'd need a Sugar > > control panel that exposes: > > > > - when was last successful / complete backup > > - "backup in process" status > > - "start backup now" button > > - "full restore now" button (hooked up with dsd's scripts?) > We should get this into a ticket on dev.sugarlabs.org > > > > Thanks for those ideas. I think that might be someplace I could learn > Sugar development. > > Dave > > > > cheers, > > > > > > > > martin > > -- > > 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 > > > > > > -- > Dave Bauer > d...@solutiongrove.com > http://www.solutiongrove.com > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA XS Report
To do this we took one of the donated computers and added a new network card. Anurag can you explain what each network card was connected to in our setup. We think that maybe part of the problem. What we are trying to accomplish is to get the computers in the computer lab to collaborate with minimal disruption to the existing computer lab. We can stick the schoolserver into the room and hook it into an extra ethernet cable. But we can't rewire the lab nor can we add another router I think. We certainly can't ask BPS to do anything with their DNS. Do we have any hope of the XS solving our collaboration problems? On Tue, Jul 7, 2009 at 5:46 PM, Anurag Goel wrote: > Today at the Gardner Pilot Academy we tried setting up an XS school server. > We were able to install the software (version 0.5.2) using the cd image > that's on the wiki. We then set the host name and enabled the ejabberd > service so it would start automatically upon boot. When we checked the > status of ejabbered it showed that ejabbered was running and everything > seemed to be fine. We booted several computers with SoaS and changed the > network settings from the default (jabber.sugarlabs.org) to the IP address > on the XS. After doing this, the computers in the computer lab still would > not recognize each other and there was no collaboration. However after > running several commands on the the XS we were able to see that computers > were able to connect to the server but were not able to see each other. Any > ideas on what we can do to make this work as collaboration will really > maximize the potential of Sugar. Caroline, please add any details I might > have left out. > > Thanks, > Anurag Goel > > > -- > Anurag Goel > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Backup and Restore Feature added to Wiki
On Tue, Jul 7, 2009 at 7:05 AM, Greg Smith wrote: > I created a Feature request for backup and restore here: > http://wiki.sugarlabs.org/go/Features/Back_Up_and_Restore > I'm still not sure how to "tie" it to GPA Add [[Category:Features requested by Gardner Pilot Academy]] to it. I've done so and documented the category. As you know, GPA's requests are also in http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Goals , but it makes more sense to "tag" feature pages with each deployment that wants it. You could even use subcategories like [[Category:Medium-priority requests from Gardner Pilot Academy]]. > or a release As I wrote yesterday, I think the 0.86/Roadmap page should explicitly link to specific features for that release. If you want to identify the connection on the feature page as well, then use one of the other approaches (use a category, rename the page, or install an extension). > or pile of pending feature requests. Someone put Category:FeaturePageIncomplete in the template, is that what you want? > Comments on format and more accurate filling out of the template also > appreciated. The =Feature Name= h1 heading is redundant with the page title, I removed it. -- =S Page ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Etoys 4.0.2229
== Sources == http://download.sugarlabs.org/sources/sucrose/glucose/etoys/etoys-4.0.2229.tar.gz http://download.sugarlabs.org/sources/sucrose/fructose/Etoys/Etoys-102.tar.gz == Packaged == http://etoys.laptop.org/rpms/etoys-4.0.2229-1.noarch.rpm http://etoys.laptop.org/rpms/Etoys-102.xo == News == * updated translations: bn, de, el, ko * fix demo project resolutions * add setup.py to please packagers * avoid black screen flashing when switching projects * set activity window title to project name * split over-long "geometry" category * better keyboard event handling in scripts * various fixes - Bert (for the Etoys team) - ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA XS Report
On Tue, Jul 7, 2009 at 7:17 PM, Caroline Meeks wrote: > To do this we took one of the donated computers and added a new network > card. Anurag can you explain what each network card was connected to in our > setup. We think that maybe part of the problem. > > What we are trying to accomplish is to get the computers in the computer lab > to collaborate with minimal disruption to the existing computer lab. We can > stick the schoolserver into the room and hook it into an extra ethernet > cable. But we can't rewire the lab nor can we add another router I think. > We certainly can't ask BPS to do anything with their DNS. Do we have any > hope of the XS solving our collaboration problems? > > On Tue, Jul 7, 2009 at 5:46 PM, Anurag Goel wrote: >> >> Today at the Gardner Pilot Academy we tried setting up an XS school >> server. We were able to install the software (version 0.5.2) using the cd >> image that's on the wiki. We then set the host name and enabled the ejabberd >> service so it would start automatically upon boot. When we checked the >> status of ejabbered it showed that ejabbered was running and everything >> seemed to be fine. We booted several computers with SoaS and changed the >> network settings from the default (jabber.sugarlabs.org) to the IP address >> on the XS. After doing this, the computers in the computer lab still would >> not recognize each other and there was no collaboration. However after >> running several commands on the the XS we were able to see that computers >> were able to connect to the server but were not able to see each other. Any >> ideas on what we can do to make this work as collaboration will really >> maximize the potential of Sugar. Caroline, please add any details I might >> have left out. >> >> Thanks, >> Anurag Goel >> >> >> -- >> Anurag Goel >> >> ___ >> Sugar-devel mailing list >> Sugar-devel@lists.sugarlabs.org >> http://lists.sugarlabs.org/listinfo/sugar-devel >> > > > > -- > Caroline Meeks > Solution Grove > carol...@solutiongrove.com > > 617-500-3488 - Office > 505-213-3268 - Fax > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > > First I think we should enabled debugging on the SoaS. To do that I edit ~/.Xclients to include this if [ -f ~/.sugar/debug ]; then . ~/.sugar/debug fi before eval \\\$(dbus-launch --sh-syntax --exit-with-session) Then we need to edit ~/.sugar/debug to fix a couple of typos: Missing space between exportGABBLE_LOGFILE and exportSALUTLOGFILE. It should be export GABBLE_LOGFILE... export SALUT_LOGFILE Then reboot the SoaS. This should provide debugging of telepathy on the client side. Dave -- Dave Bauer d...@solutiongrove.com http://www.solutiongrove.com ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [support-gang] Corps Deployment looking to fund Prog. Dev.
Paul - The sugar development list is a good place to look for someone with time to help. Extending Write to do what you have in mind may indeed be the best way to proceed - they had some developers interested in doing more work for the XO but lacking funds. SJ Seth Woodworth wrote: | Write is based on the GNU/linux program AbiWord, which does have | support for everything you mention, but not exactly easily done. But | all the same, you very well may be able to solve your problem by | creating a template in AbiWord/OpenOffice that Write may be able to | understand. | | I don't know, but I would look into at least exploring Write as a | basis for what you're working on. | | Also, I assume you've seen EduBlog? It's a project ran in part by | former-OLPC-er and Support-Ganger Greg Smith | | http://wiki.laptop.org/go/EduBlog_Instructions - Show quoted text - On Sun, Jul 5, 2009 at 1:53 PM, Paul Commons wrote: > Hi OLPC Community, > One of the Corps deployments is looking for a programmer from the OLPC > community who can put together a child-friendly newspaper activity where the > kids author the articles and design its template. If you're aware of any > such program available, I'd love to know. If not, the team has some > available funds if there's a quick turn around. If you're interested, please > contact me and we can discuss the specs. CC langgor...@gmail.com too. > Thanks! > Cheers, > Paul > > -- > Paul Commons > One Laptop per Child > (317) 523.9822 > > > > > > > > ___ > support-gang mailing list > support-g...@lists.laptop.org > http://lists.laptop.org/listinfo/support-gang > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA XS Report
On Wed, Jul 8, 2009 at 9:46 AM, Anurag Goel wrote: > We booted several computers with SoaS and changed the > network settings from the default (jabber.sugarlabs.org) to the IP address > on the XS. After doing this, the computers in the computer lab still would That is a workaround to the missing "register" button in SoaS, right? I suspect that part of the problem is that you are using the IP address. Sugar will see whatever DNS or IP addr you provide there and will try to connect to jabber and create an account as follows: - @ On XO hardware, machine-id is the serialnumber. On other hw, it creates a random string on first boot. The problem with the scheme is that jabber on the XS expects a very specific jabber servername for the account: its own name (as given to domain_config) prefixed with 'schoolserver.' If the name doesn't match that format, then it breaks. The workaround is to use "schoolserver." in the SoaS control panel. A more proper solution is probably to bring back 'registration' :-) hth, 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] GPA XS Report
On Tue, Jul 7, 2009 at 10:20 PM, Martin Langhoff wrote: > On Wed, Jul 8, 2009 at 9:46 AM, Anurag Goel wrote: > > We booted several computers with SoaS and changed the > > network settings from the default (jabber.sugarlabs.org) to the IP > address > > on the XS. After doing this, the computers in the computer lab still > would > > That is a workaround to the missing "register" button in SoaS, right? no, we are still just trying to get the machines in the lab to see the Jabber Server in the lab via the server setting in the control panel. I think some of your comments below may still be relevant but I don't entirely understand. > > > I suspect that part of the problem is that you are using the IP > address. Sugar will see whatever DNS or IP addr you provide there and > will try to connect to jabber and create an account as follows: > > - @ > > On XO hardware, machine-id is the serialnumber. On other hw, it > creates a random string on first boot. > > The problem with the scheme is that jabber on the XS expects a very > specific jabber servername for the account: its own name (as given to > domain_config) prefixed with 'schoolserver.' > > If the name doesn't match that format, then it breaks. > > The workaround is to use "schoolserver." in the SoaS control > panel. A more proper solution is probably to bring back 'registration' > :-) > > hth, > > > > 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 > -- Caroline Meeks Solution Grove carol...@solutiongrove.com 617-500-3488 - Office 505-213-3268 - Fax ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA XS Report
On Wed, Jul 8, 2009 at 2:27 PM, Caroline Meeks wrote:
> no, we are still just trying to get the machines in the lab to see the
> Jabber Server in the lab via the server setting in the control panel.
H. On Sugar 0.82 "Register" achieves exactly the same (plus 2 more
things) and is easier to use.
>From the PoV of Sugar for primary schoolers, "Register" is not ideal
(we could do some autodiscovery) but still a better UI than entering
the DNS name of a server.
> I think some of your comments below may still be relevant but I don't
> entirely understand.
I think they are :-) In brief: put the FQDN name in there, the one
that starts with 'schoolserver', instead of an IP address.
>From the "making SoaS and Sugar in general easy to get going in a
school infra" PoV, it'd be nice to at least get 'register' going
again.
DNS-SD based autodiscovery would be nicer ("look ma! automagic!"), but
is also more (and trickier) work.
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
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] GPA XS Report
So here is the current hardware set up: We have an ethernet cable from the main school access point that is connected to each individual computer in the lab as well as the XS. However, we are currently not using the second ethernet port on the XS. The wiki page suggests connecting a wireless access point to the second ethernet port on the XS. However the school will not allow us to bring in our own router/access point of some kind as it will disrupt their current set up. Hardwiring the computers to the XS is also not very practical. On Tue, Jul 7, 2009 at 10:27 PM, Caroline Meeks wrote: > > > On Tue, Jul 7, 2009 at 10:20 PM, Martin Langhoff < > martin.langh...@gmail.com> wrote: > >> On Wed, Jul 8, 2009 at 9:46 AM, Anurag Goel wrote: >> > We booted several computers with SoaS and changed the >> > network settings from the default (jabber.sugarlabs.org) to the IP >> address >> > on the XS. After doing this, the computers in the computer lab still >> would >> >> That is a workaround to the missing "register" button in SoaS, right? > > > no, we are still just trying to get the machines in the lab to see the > Jabber Server in the lab via the server setting in the control panel. > > I think some of your comments below may still be relevant but I don't > entirely understand. > >> >> >> I suspect that part of the problem is that you are using the IP >> address. Sugar will see whatever DNS or IP addr you provide there and >> will try to connect to jabber and create an account as follows: >> >> - @ >> >> On XO hardware, machine-id is the serialnumber. On other hw, it >> creates a random string on first boot. >> >> The problem with the scheme is that jabber on the XS expects a very >> specific jabber servername for the account: its own name (as given to >> domain_config) prefixed with 'schoolserver.' >> >> If the name doesn't match that format, then it breaks. >> >> The workaround is to use "schoolserver." in the SoaS control >> panel. A more proper solution is probably to bring back 'registration' >> :-) >> >> hth, >> >> >> >> 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 >> > > > > -- > Caroline Meeks > Solution Grove > carol...@solutiongrove.com > > 617-500-3488 - Office > 505-213-3268 - Fax > -- Anurag Goel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] poor man's mmap "sliding window" on Python 2.5.x
On Tue, Jul 7, 2009 at 9:23 AM, Martin Langhoff wrote: > Thanks for looking into this. I'll post the (trivial, really) repro > code I have later (I'm on a gruelling >35hr trip at the moment). Had some time to retest this on the plane, and I think it was mis-diagnosis. The original code I was testing is lost. In re-testing this I find that the problem is more nuanced, and I may have been wrong: looking at 'top', the kernel does not appear very eager to discard old mapped pages. The process is doing a linear read through the file, and is slow enough that it appears only to grow. But if I run another process that allocates a lot of memory, then the kernel does discard pages pages. A good way of monitoring this seems to be: watch --differences grep -A8 /proc//smaps So the mmap does the right thing. ACCESS_READ doesn't seem to make any difference. #!/usr/bin/python import mmap import sys def mmap_to_death(fpath): fh = open(fpath, 'r+') mm = mmap.mmap(fh.fileno(), 0, access=mmap.ACCESS_READ) l = len(mm) c = 0 buf = '' while c < l: buf = mm[c] c = c+1 mm.close() fh.close() mmap_to_death(sys.argv[1]) 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] Questions about GConf and ORBit.
Tomeu, I dug through the gconf, libbonobo, and orbit2 source code and discovered some interesting things. Most relevant for this discussion: * ORBit2, on Linux, defaults to sending messages over unix sockets in directories like /tmp/orbit-$USER* which it carefully creates with mode 0700. There are no configuration options for changing these permissions. * it's easy to get orbit2 to use other transports with either per-user or system-wide configuration. Just run something like cat >> $CHROOT/etc/orbitrc
[Sugar-devel] [RELEASE] Distance v16
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Download: http://dev.laptop.org/~bemasc/Distance-16.xo Changes: In addition to the usual crop of translation updates, this release adds a very simple "Calibration" feature. Its principal purpose is to improve support for non-XO laptops. Users can now determine the calibration offset for their own hardware, and for the point on their hardware from which they are measuring. - --Ben -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkpUDS8ACgkQUJT6e6HFtqRQ7QCfQ5kC8KN1Hy1n22juw/bMMMnr wi4AnjjLXftzveL3nHt2vyAXz7VFuQIw =ehyP -END PGP SIGNATURE- ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Soas on XO-1 vs activation
With respect to: http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Installation/OLPC I am considering options 2 & 3. Both these options ultimately involve copy-nand. Am I going to lose activation & my development key when I do this? In other words, do I need to prepare the XS activation server (or equivalent) prior to attempting the upgrade and keep a backup of my development key? -- American? Vote on the National Initiative for Democracy, http://votep2.us ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Soas on XO-1 vs activation
On Wed, Jul 8, 2009 at 3:52 PM, Joshua N Pritikin wrote: > I am considering options 2 & 3. Both these options ultimately involve > copy-nand. Am I going to lose activation & my development key when I do > this? In other words, do I need to prepare the XS activation server (or > equivalent) prior to attempting the upgrade and keep a backup of my > development key? - Yes, copy-nand will wipe /security directory, with any leases or devkeys there. - Always a good idea to keep a backup of your dev key. And the lease too (as it's useful for debugging some activtion cases). - With your devkey installed, use the 'disable-security' procedure. Once it's done, OFW remembers it and your XO is free as a bird, permanently. If you want to reenable it later (for testing antitheft features) you can. 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 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] custom value for ~/.sugar/default/config (Pilgrim)
Hi, I am using Pilgrim to make nexo images. I need to use a different timezone and change the default value for hot corners. Those settings are in the file /home/olpc/.sugar/default/config. What to do in Pilgrim so that the xos when flashed contains custom timezone and hot corners. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
