Re: Impossible to set date in 11.3.0?

2012-08-27 Thread James Cameron
On Sat, Aug 25, 2012 at 01:07:35PM -0400, Samuel Greenfeld wrote:
 To the best of my knowledge this is an intentional omission for
 antitheft reasons.  Instructions on how to set the clock from OFW or
 the command line are at http://wiki.laptop.org/go/Fix_Clock .

I think the task of setting the clock should be split from the
problems that lead to it described in that page.  It is far too scary
looking.

 If using the date command is not sufficient to permanently store
 the change, hwclock --systohc or similar may also need to be used.

date followed by a successful normal shutdown should work, because a
normal shutdown runs hwclock ... but hwclock --systohc is handy in
case you aren't sure that a normal shutdown will happen next.

 In newer firmware builds (potentially newer than 11.3.0's), Open
 Firmware can log into a Open, WEP, or WPA-PSK secured access point
 and use NTP to set the time.  To do this use the essid command
 followed by the actual ESSID to set the ESSID, wep or wpa to set
 the password, and ntp-set-clock (without any parameters) to query
 a server from the public NTP pool and get the current time.

The firmware included with 11.3.0 can already do ntp-set-clock with
open wireless access points and USB Ethernet adapters.  More recent
firmware fixed WEP and WPA-PSK, if I recall correctly.

(Nothing to do with WEP and WPA-PSK in Linux though, you can stay on
older firmware for that.)

-- 
James Cameron
http://quozl.linux.org.au/
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Firmware issu

2012-08-27 Thread Kevin Gordon
On Mon, Aug 27, 2012 at 1:42 AM, James Cameron qu...@laptop.org wrote:

 Q2F12 added support for automatic power down if lid is closed while at
 ok prompt, per ticket #11095, svn 2991.  If you have been using
 previous firmware, you may never have seen this message.

 It has been a feature of XO-1.5 and XO-1.75 already.

 On XO-1, the lid switch is wired to the CS5536 companion chip, as well
 as to the the embedded controller.  Open Firmware is reading from the
 GPIO pin array in the CS5536.  Hal observed a confused embedded
 controller or battery error may trigger this issue.

 Kevin, Robert, please remove the external power, and the main battery,
 wait ten seconds, then reinsert both, and see if the problem persists.


Problem persists.

Just a reminder this lid message only appears upon entering firmware after
a reboot from linux.  Doesn't happen on entering reboot from firmware or
a cold start.  Noted one other symptom: when I do the reboot from
firmware, I do hear a little 'click' as the battery LED flashes, I don't
hear that click on the reboot from Linux.  It occurs whether doing a
restart from the GUI on Linux or entering reboot from terminal.


 If it does, please get to the ok prompt, type lid-off and press enter
 (to stop the timer), then test the lid switch like this:

 ok lid? . cr d# 500 ms many


After rebooting from Linux seeing the symptom and entering lid-off after
entering the above command, saw

fff
fff
fff
fff
.
.


After rebooting from firmware, and not seeing the symprom, and entering teh
above command, saw
0
0
0
0

At no time during this whole process was the lid ever closed.


 This will print  when the lid switch is considered closed, and
 0 when the lid switch is considered open.

 Waving a magnet against the front bezel above the microphone is a
 useful way to test the switch without having to close the laptop.  The
 switch works best with the north and south poles of the magnet
 pointing left-right or right-left.  You'll soon learn which way works;
 I don't have a labelled test magnet here, I just know it works only
 one way.


I'll search for a magnet; dont have one at my desk.

Cheers

KG


 The case magnet is to the left of the touchpad.  Drag a USB drive over
 there to find it; a typical USB connector will be attracted.

 --
 James Cameron
 http://quozl.linux.org.au/

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Firmware issu

2012-08-27 Thread Kevin Gordon
On Mon, Aug 27, 2012 at 8:21 AM, Kevin Gordon kgordon...@gmail.com wrote:



 On Mon, Aug 27, 2012 at 1:42 AM, James Cameron qu...@laptop.org wrote:

 Q2F12 added support for automatic power down if lid is closed while at
 ok prompt, per ticket #11095, svn 2991.  If you have been using
 previous firmware, you may never have seen this message.

 It has been a feature of XO-1.5 and XO-1.75 already.

 On XO-1, the lid switch is wired to the CS5536 companion chip, as well
 as to the the embedded controller.  Open Firmware is reading from the
 GPIO pin array in the CS5536.  Hal observed a confused embedded
 controller or battery error may trigger this issue.

 Kevin, Robert, please remove the external power, and the main battery,
 wait ten seconds, then reinsert both, and see if the problem persists.


 Problem persists.

 Just a reminder this lid message only appears upon entering firmware after
 a reboot from linux.  Doesn't happen on entering reboot from firmware or
 a cold start.  Noted one other symptom: when I do the reboot from
 firmware, I do hear a little 'click' as the battery LED flashes, I don't
 hear that click on the reboot from Linux.  It occurs whether doing a
 restart from the GUI on Linux or entering reboot from terminal.


 If it does, please get to the ok prompt, type lid-off and press enter
 (to stop the timer), then test the lid switch like this:

 ok lid? . cr d# 500 ms many


 After rebooting from Linux seeing the symptom and entering lid-off after
 entering the above command, saw

 fff
 fff
 fff
 fff
 .
 .


 After rebooting from firmware, and not seeing the symprom, and entering
 teh above command, saw
 0
 0
 0
 0

 At no time during this whole process was the lid ever closed.


 This will print  when the lid switch is considered closed, and
 0 when the lid switch is considered open.

 Waving a magnet against the front bezel above the microphone is a
 useful way to test the switch without having to close the laptop.  The
 switch works best with the north and south poles of the magnet
 pointing left-right or right-left.  You'll soon learn which way works;
 I don't have a labelled test magnet here, I just know it works only
 one way.


 I'll search for a magnet; dont have one at my desk.


At the risk of too much info.  I have also noticed that the lid-off message
when entering firmware does not ever happen on the XO 1.5.

Consistently on all machines, whether I do a shut-down or a restart from
Linux the screen goes to text console, (last message ; dcon freeze) then
goes to the warning screen, then goes blank.

Then on the 1.5 whether doing restart/reboot from Linux or doing a
shut-down, the power light blinks multiple times before strating up again.

However, on the XO 1.0 when doing a shut-down, the power light blinks
before turning completely off, but when doing a Linux restart, the power
light does not blink at any point in the restart process.

KG



 Cheers

 KG


 The case magnet is to the left of the touchpad.  Drag a USB drive over
 there to find it; a typical USB connector will be attracted.

 --
 James Cameron
 http://quozl.linux.org.au/



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Impossible to set date in 11.3.0?

2012-08-27 Thread Kevin Gordon
On Mon, Aug 27, 2012 at 4:43 AM, James Cameron qu...@laptop.org wrote:

 On Sat, Aug 25, 2012 at 01:07:35PM -0400, Samuel Greenfeld wrote:
  To the best of my knowledge this is an intentional omission for
  antitheft reasons.  Instructions on how to set the clock from OFW or
  the command line are at http://wiki.laptop.org/go/Fix_Clock .

 I think the task of setting the clock should be split from the
 problems that lead to it described in that page.  It is far too scary
 looking.

  If using the date command is not sufficient to permanently store
  the change, hwclock --systohc or similar may also need to be used.

 date followed by a successful normal shutdown should work, because a
 normal shutdown runs hwclock ... but hwclock --systohc is handy in
 case you aren't sure that a normal shutdown will happen next.


Here's a little set of instructions that we use to customize for the right
time-zone and current utc date.  We also save a script and it sits on all
of our builds, Unfortunately, we are either busy or lazy :-)  and we have
the deployments change the script and run as need be, and we haven't done a
UI. It extracts info from the wiki and summarizes some of what's here, but
this process adds the local time-zone too, in this example EST.  We cannot
guarantee internet connectivity, hence this less elegant method.


Once Linux has booted, login at a root terminal (e.g. press Ctrl+Alt+F2) or
perform as superuser:

date --utc --set=2012-08-26 18:30:40

cd /etc

ln -sf /usr/share/zoneinfo/EST localtime

/sbin/hwclock --systohc

shutdown

(Don't force a shutdown by holding down the power button, because then the
change won't be stored.)

===


Building an input UI for date and time-zone parms is on our list, just
never seems to bubble to the top.


KG


  In newer firmware builds (potentially newer than 11.3.0's), Open
  Firmware can log into a Open, WEP, or WPA-PSK secured access point
  and use NTP to set the time.  To do this use the essid command
  followed by the actual ESSID to set the ESSID, wep or wpa to set
  the password, and ntp-set-clock (without any parameters) to query
  a server from the public NTP pool and get the current time.

 The firmware included with 11.3.0 can already do ntp-set-clock with
 open wireless access points and USB Ethernet adapters.  More recent
 firmware fixed WEP and WPA-PSK, if I recall correctly.

 (Nothing to do with WEP and WPA-PSK in Linux though, you can stay on
 older firmware for that.)

 --
 James Cameron
 http://quozl.linux.org.au/
 ___
 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: Setting the time

2012-08-27 Thread Tony Anderson

Hi,

In a school deployment, it is desirable that all of the XOs have the 
same time. This time should be synchronized with/by the school server 
(even if the school server is wrong). It is not reasonable to base this 
capability on access to the internet.


Casio sells 'atomic' watches that synchronize to Ft. Collins by radio. 
Neat, but how does this work in Rwanda?


Tony

On 08/27/2012 03:19 PM, devel-requ...@lists.laptop.org wrote:

Send Devel mailing list submissions to
devel@lists.laptop.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.laptop.org/listinfo/devel
or, via email, send a message with subject or body 'help' to
devel-requ...@lists.laptop.org

You can reach the person managing the list at
devel-ow...@lists.laptop.org

When replying, please edit your Subject line so it is more specific
than Re: Contents of Devel digest...


Today's Topics:

1. Re: Impossible to set date in 11.3.0? (James Cameron)
2. Re: Firmware issu (Kevin Gordon)
3. Re: Firmware issu (Kevin Gordon)
4. Re: Impossible to set date in 11.3.0? (Kevin Gordon)


--

Message: 1
Date: Mon, 27 Aug 2012 18:43:39 +1000
From: James Cameronqu...@laptop.org
To: devel@lists.laptop.org
Subject: Re: Impossible to set date in 11.3.0?
Message-ID:20120827084339.gh7...@us.netrek.org
Content-Type: text/plain; charset=us-ascii

On Sat, Aug 25, 2012 at 01:07:35PM -0400, Samuel Greenfeld wrote:

To the best of my knowledge this is an intentional omission for
antitheft reasons.  Instructions on how to set the clock from OFW or
the command line are at http://wiki.laptop.org/go/Fix_Clock .


I think the task of setting the clock should be split from the
problems that lead to it described in that page.  It is far too scary
looking.


If using the date command is not sufficient to permanently store
the change, hwclock --systohc or similar may also need to be used.


date followed by a successful normal shutdown should work, because a
normal shutdown runs hwclock ... but hwclock --systohc is handy in
case you aren't sure that a normal shutdown will happen next.


In newer firmware builds (potentially newer than 11.3.0's), Open
Firmware can log into a Open, WEP, or WPA-PSK secured access point
and use NTP to set the time.  To do this use the essid command
followed by the actual ESSID to set the ESSID, wep or wpa to set
the password, and ntp-set-clock (without any parameters) to query
a server from the public NTP pool and get the current time.


The firmware included with 11.3.0 can already do ntp-set-clock with
open wireless access points and USB Ethernet adapters.  More recent
firmware fixed WEP and WPA-PSK, if I recall correctly.

(Nothing to do with WEP and WPA-PSK in Linux though, you can stay on
older firmware for that.)



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Setting the time

2012-08-27 Thread Samuel Greenfeld
If anti-theft is used with delegated leases (so the school server can give
leases for a few weeks at a time), the XOs will trust a signed timestamp
provided from the school server.   However olpc-update-query will only
reset the XO's clock if it is off by more than a day.

According to a comment in the code this is done to avoid messing with NTP,
except our OS builds don't currently have NTP in them.

School servers run NTP servers which NTP clients can connect to.  These are
not currently configured to support running without an external NTP source,
although they can be configured to do so.

If a locally accurate clock at the XS site is required and Internet is not
available, NTP can use a cheap USB or serial GPS unit as a time source.
Running gpsd or similar may be required depending on the GPS's supported
protocol(s).

In any case if OLPC or Sugarlabs wants to formally integrate NTP services
into our products, we should be polite and ask ntp.pool.org if we need our
own vendor subdomain.  These allow the NTP pool to shut off misbehaving
clients without affecting other users, and Fedora and CentOS already have
their own.


On Mon, Aug 27, 2012 at 9:39 AM, Tony Anderson tony_ander...@usa.netwrote:

 Hi,

 In a school deployment, it is desirable that all of the XOs have the same
 time. This time should be synchronized with/by the school server (even if
 the school server is wrong). It is not reasonable to base this capability
 on access to the internet.

 Casio sells 'atomic' watches that synchronize to Ft. Collins by radio.
 Neat, but how does this work in Rwanda?

 Tony

 On 08/27/2012 03:19 PM, devel-requ...@lists.laptop.org wrote:

 Send Devel mailing list submissions to
 devel@lists.laptop.org

 To subscribe or unsubscribe via the World Wide Web, visit
 
 http://lists.laptop.org/**listinfo/develhttp://lists.laptop.org/listinfo/devel
 or, via email, send a message with subject or body 'help' to
 devel-requ...@lists.laptop.org

 You can reach the person managing the list at
 devel-ow...@lists.laptop.org

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of Devel digest...


 Today's Topics:

 1. Re: Impossible to set date in 11.3.0? (James Cameron)
 2. Re: Firmware issu (Kevin Gordon)
 3. Re: Firmware issu (Kevin Gordon)
 4. Re: Impossible to set date in 11.3.0? (Kevin Gordon)


 --**--**
 --

 Message: 1
 Date: Mon, 27 Aug 2012 18:43:39 +1000
 From: James Cameronqu...@laptop.org
 To: devel@lists.laptop.org
 Subject: Re: Impossible to set date in 11.3.0?
 Message-ID:20120827084339.**gh7...@us.netrek.org20120827084339.gh7...@us.netrek.org
 
 Content-Type: text/plain; charset=us-ascii

 On Sat, Aug 25, 2012 at 01:07:35PM -0400, Samuel Greenfeld wrote:

 To the best of my knowledge this is an intentional omission for
 antitheft reasons.  Instructions on how to set the clock from OFW or
 the command line are at 
 http://wiki.laptop.org/go/Fix_**Clockhttp://wiki.laptop.org/go/Fix_Clock.


 I think the task of setting the clock should be split from the
 problems that lead to it described in that page.  It is far too scary
 looking.

  If using the date command is not sufficient to permanently store
 the change, hwclock --systohc or similar may also need to be used.


 date followed by a successful normal shutdown should work, because a
 normal shutdown runs hwclock ... but hwclock --systohc is handy in
 case you aren't sure that a normal shutdown will happen next.

  In newer firmware builds (potentially newer than 11.3.0's), Open
 Firmware can log into a Open, WEP, or WPA-PSK secured access point
 and use NTP to set the time.  To do this use the essid command
 followed by the actual ESSID to set the ESSID, wep or wpa to set
 the password, and ntp-set-clock (without any parameters) to query
 a server from the public NTP pool and get the current time.


 The firmware included with 11.3.0 can already do ntp-set-clock with
 open wireless access points and USB Ethernet adapters.  More recent
 firmware fixed WEP and WPA-PSK, if I recall correctly.

 (Nothing to do with WEP and WPA-PSK in Linux though, you can stay on
 older firmware for that.)


 __**_
 Devel mailing list
 Devel@lists.laptop.org
 http://lists.laptop.org/**listinfo/develhttp://lists.laptop.org/listinfo/devel

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Setting the time

2012-08-27 Thread C. Scott Ananian
On Mon, Aug 27, 2012 at 10:05 AM, Samuel Greenfeld greenf...@laptop.org wrote:
 In any case if OLPC or Sugarlabs wants to formally integrate NTP services
 into our products, we should be polite and ask ntp.pool.org if we need our
 own vendor subdomain.  These allow the NTP pool to shut off misbehaving
 clients without affecting other users, and Fedora and CentOS already have
 their own.

We already did this (the first time I fixed this bug, years ago).  I
believe we have olpc.ntp.pool.org, although I'll have to dig up the
email from my archive to double-check.  We also got permission to use
fedora's pool at the same time, because it was more suitable for the
upstreamed version of the patch.
  --scott

-- 
  ( http://cscott.net )
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Impossible to set date in 11.3.0?

2012-08-27 Thread Hal Murray

qu...@laptop.org said:
 date followed by a successful normal shutdown should work, because a
 normal shutdown runs hwclock ... but hwclock --systohc is handy in case
 you aren't sure that a normal shutdown will happen next. 

It used to do that on shutdown as part of /etc/rc.d/init.d/halt and friends, 
but I think it got dropped as part of the switch to systemd.   grep hwclock 
/etc -r doesn't find anything.

Does anybody know if it moved to someplace I haven't looked yet and/or if it 
was deliberately dropped or just fell through the cracks?


-- 
These are my opinions.  I hate spam.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: Setting the time

2012-08-27 Thread Hal Murray

 In a school deployment, it is desirable that all of the XOs have the  same
 time. This time should be synchronized with/by the school server  (even if
 the school server is wrong). It is not reasonable to base this  capability
 on access to the internet.

How closely do you need them to be synchronized?  1 second?  1 microsecond?  
1 minute?

It should be reasonably easy to setup ntpd on the school server and get the 
XOs to set their clocks when booted.

You may want/need a cron job to set the time occasionally.


 Casio sells 'atomic' watches that synchronize to Ft. Collins by radio.
 Neat, but how does this work in Rwanda? 

WWVB runs at 60 KHz.  There are several similar systems in other countries.  
I don't think any of them make it to Africa.  GPS does.

You can get USB GPS receivers for under $50.  The SiRF chip is the most 
popular in the low cost units.  It's crappy if you need ms level timing, but 
good enough if all you need is 1 second.



-- 
These are my opinions.  I hate spam.



___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


mainstream media take on linux desktops

2012-08-27 Thread Kevin Gordon
http://www.cnn.com/2012/08/27/tech/web/apple-linux-desktop/index.html
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [OLPC-AU] long-press touch actions in Sugar

2012-08-27 Thread Mikus Grinbergs

Sridhar wrote:

It appears that long-press is becoming part of the Sugar user
experience on touchscreens:


In my opinion the XO product is notably limited in that its front panel 
buttons will only register a 'press'.  The opportunities for use of 
the XO in e-book configuration would be greatly enhanced if those front 
panel buttons were able to register 'long press' as well as 'press'.


mikus

___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel


Re: [Server-devel] antitheft:: avoiding the need - cont.

2012-08-27 Thread Sameer Verma
On Sun, Aug 26, 2012 at 12:32 PM,  jbalc...@laptopstolesotho.org wrote:
 I plan to attend the OLPC conference in San Francisco in October.  I will
 be available there to anyone who wishes to discuss our Laptops to Lesotho
 model in more detail.

 You can see the Rules  Regulations, Contracts, and Fine Schedules written
 in December 2010 for Nohana Primary School on our blog at:
 http://olpc2010-lesotho.blogspot.com/p/2011-rules-regulations-contracts-fee.html

 Janissa Balcomb
 Laptops to Lesotho Inc.
 www.laptopstolesotho.org


 ___
 Server-devel mailing list
 Server-devel@lists.laptop.org
 http://lists.laptop.org/listinfo/server-devel



Excellent! Can you submit a proposal, if you haven't already, to
discuss such issues?

http://olpcsf.org/summit

cheers,
Sameer
-- 
Sameer Verma, Ph.D.
Professor, Information Systems
San Francisco State University
http://verma.sfsu.edu/
http://commons.sfsu.edu/
http://olpcsf.org/
http://olpcjamaica.org.jm/
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


[Server-devel] registering an xo for second time

2012-08-27 Thread vanessa ramos da cruz
 Halo!


I am Vanessa; I am working in Angola with this project. I am new on the project
so I have a little concern:

I had a server with XS 0.6, I registered on it some XO’s just for tests. Now
I have a new machine on witch I installed

the XS 0.7. I would like to register the XO‘s on this new Machine. How
ca I registered the
few XO’s I already registered before?

I don’t have the old Machine with the XS 0.6 installation any more…


Can you please help me?
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [OLPC-AU] Registering an XO for the second time

2012-08-27 Thread Sridhar Dhanapalan
On 27 August 2012 20:14, vanessa ramos da cruz v.ramosdac...@gmail.com wrote:
 Halo Martin,



 I am Vanessa; I am working in Angola with this project. I am new on the
 project so I have a little concern.



 I had a server with XS 0.6, I registered on it some XO’s just for tests. Now
 I have a new machine on witch I installed

 the XS 0.7. I would like to register the XO‘s on this new Machine. How ca I
 register the few XO’s I already registered before?

 I don’t have the old Machine with the XS 0.6 installation any more…



 Can you please help me?


Hi Vanessa,

You're better off asking these questions on the server-devel list:

http://lists.laptop.org/listinfo/server-devel

Regards,
Sridhar


Sridhar Dhanapalan
Engineering Manager
One Laptop per Child Australia
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] registering an xo for second time

2012-08-27 Thread Jerry Vonau
On Mon, 2012-08-27 at 15:48 +0100, vanessa ramos da cruz wrote:
  Halo!
 
 
 I am Vanessa; I am working in Angola with this project. I am new on
 the project so I have a little concern:
 
 I had a server with XS 0.6, I registered on it some XO’s just for
 tests. Now I have a new machine on witch I installed
 
 the XS 0.7. I would like to register the XO‘s on this new Machine. How
 ca I registered the few XO’s I already registered before?
 

Try entering this from sugar's terminal activity:

gconftool-2 --get /desktop/sugar/show_register

If false is returned, you could try toggling that setting with:

gconftool-2 --toggle /desktop/sugar/show_register

Hope that restores the right-click register option to the home view for
you.

Jerry



___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] registering an xo for second time

2012-08-27 Thread Samuel Greenfeld
If the OS/Sugar build is new enough, the Register option never disappears
from the Right click menu of the XO character in the home view, and
re-registration is possible with no editing required.

The Register option only appears on the screen which has the application
Circle/Spiral present, and not in the Network view or Friends view.  Given
shutdown  restart appear on all three screens, this is potentially a bug.

I believe 11.3.0 supports re-registration; 11.3.1  12.1.0 definitely do.
The exact ticket which enabled this behavior currently is eluding me.


On Mon, Aug 27, 2012 at 10:50 PM, Jerry Vonau jvo...@shaw.ca wrote:

 On Mon, 2012-08-27 at 15:48 +0100, vanessa ramos da cruz wrote:
   Halo!
 
 
  I am Vanessa; I am working in Angola with this project. I am new on
  the project so I have a little concern:
 
  I had a server with XS 0.6, I registered on it some XO’s just for
  tests. Now I have a new machine on witch I installed
 
  the XS 0.7. I would like to register the XO‘s on this new Machine. How
  ca I registered the few XO’s I already registered before?
 

 Try entering this from sugar's terminal activity:

 gconftool-2 --get /desktop/sugar/show_register

 If false is returned, you could try toggling that setting with:

 gconftool-2 --toggle /desktop/sugar/show_register

 Hope that restores the right-click register option to the home view for
 you.

 Jerry



 ___
 Server-devel mailing list
 Server-devel@lists.laptop.org
 http://lists.laptop.org/listinfo/server-devel

___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel