Hi Bert,
Thanks it's exactly what I'm looking for.
Best regards from France.
Lionel.
------------------------------
Date: Sat, 28 May 2011 12:25:43 +0200
From: Bert Freudenberg <[email protected]>
Subject: Re: Get serial number or XO name from command line or python
To: OLPC Devel <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
On 28.05.2011, at 08:55, LASKE, Lionel (C2S) wrote:
>
> Hi all,
>
> Thanks for all your answers. The serial was exactly what I expected. Great.
> About the "XO name", my question was not clear. What I'm looking for is the
> name in the Sugar Control Panel (Me).
> Any way to get it ?
Depends on the Sugar version, and is quite hard to make work universally.
In older versions, you could ask the PresenceService for the "ownerBuddy", and
access its nick. Or directly access the file:
${HOME}/.sugar/${$SUGAR_PROFILE}/config
In newer versions, it's stored in gconf:
gconftool-2 -g /desktop/sugar/user/nick
Both of these assume you are logged in as the Sugar user. If you are running
the script as root, you need to guess the user name. On an XO the user normally
is "olpc", on SoaS it typically is "liveuser". If all else fails you could look
for all user homes that have a ".sugar" directory. If there is only one you are
lucky, otherwise you should fail and ask for the right one.
Also, watch out for non-ascii nick names, and funny characters. Kids frequently
use them, unaware there may be problems in command line scripts.
- Bert -
------------------------------
Message: 5
Date: Sat, 28 May 2011 08:25:57 -0700 (PDT)
From: Yioryos Asprobounitis <[email protected]>
Subject: stop sharing an activity
To: OLPC Devel <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I could not find a way to stop sharing an activity even when no peers are
connected or even present.
This was true in os860 and os20, XO-1 and XO-1.5 and activities like write and
Turtle blocks.
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"?
Thx
------------------------------
_______________________________________________
Devel mailing list
[email protected]
http://lists.laptop.org/listinfo/devel
End of Devel Digest, Vol 63, Issue 54
*************************************
_______________________________________________
Devel mailing list
[email protected]
http://lists.laptop.org/listinfo/devel
