Excerpts from C. Scott Ananian's message of Sun Mar 13 04:06:56 +0100 2011:
Last I knew we used standard Linux conventions for timezones and sugar
called the standard Linux commands (via sudo) to set the timezone.
Can you point me at that old code, please? (we currently use gconf [1],
so Sugar
sascha wrote:
Excerpts from C. Scott Ananian's message of Sun Mar 13 04:06:56 +0100 2011:
Last I knew we used standard Linux conventions for timezones and sugar
called the standard Linux commands (via sudo) to set the timezone.
Can you point me at that old code, please? (we
Excerpts from Paul Fox's message of Sun Mar 13 13:04:30 +0100 2011:
Can you point me at that old code, please? (we currently use gconf [1],
so Sugar is decoupled from the rest of the system w.r.t. time zone).
do you know why this is/was done? is it simply a matter of not
wanting the
On 03/13/2011 01:15 AM, Sridhar Dhanapalan wrote:
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run different
hardware tests. On this XO-1, I only get an array of square outlines.
The
On Sat, Mar 12, 2011 at 10:21 PM, Samuel Greenfeld greenf...@laptop.org wrote:
The XO image OLPC supplies defaults to UTC. Users can select a time
zone offset in Sugar if they want, but it is purely a numerical control
All correct AFAIK. For background on why deployments are not setting
the
On 13 March 2011 03:21, Samuel Greenfeld greenf...@laptop.org wrote:
Sugar reports only relative times in its core GUI, so I don't know how
common it is for deployments or other users to actually change this
setting. Setting a time zone other than UTC with 10.1.3 and prior may
also expose a
On 3/13/2011 8:09 AM, Richard A. Smith wrote:
On 03/13/2011 01:15 AM, Sridhar Dhanapalan wrote:
With firmware Q2E45 on an XO-1 (yes, I finally got it unlocked!), I
type 'menu' at the ok prompt.
On an XO-1.5, I get a very useful list of icons that run different
hardware tests. On this XO-1,
I apologize; I think the code that sets timezone correctly might
have been code I wrote for litl, not OLPC.
--scott
On Sunday, March 13, 2011, Daniel Drake d...@laptop.org wrote:
On 13 March 2011 03:21, Samuel Greenfeld greenf...@laptop.org wrote:
Sugar reports only relative times in its core
On 03/13/2011 11:15 AM, Daniel Drake wrote:
On 13 March 2011 03:21, Samuel Greenfeldgreenf...@laptop.org wrote:
Sugar reports only relative times in its core GUI, so I don't know how
common it is for deployments or other users to actually change this
setting. Setting a time zone other than
On 03/13/2011 11:21 AM, Mitch Bradley wrote:
Not expected but not surprising. The graphical hardware
tests/diagnostics were developed for the 1.5. In XO 1.0 we only had the
text based tests. I suspect that the 1.5 graphics stuff came along for
the ride when we started building newer XO-1
On 13 March 2011 15:49, Richard A. Smith rich...@laptop.org wrote:
Thanks for clearing that up. I've checked on build 860 and `date` reports
the timezone selected via the control panel. So that gives me what I need.
That only applies when you're in the sugar environment though.
If you're
On 03/13/2011 11:56 AM, Daniel Drake wrote:
On 13 March 2011 15:49, Richard A. Smithrich...@laptop.org wrote:
Thanks for clearing that up. I've checked on build 860 and `date` reports
the timezone selected via the control panel. So that gives me what I need.
That only applies when you're
On Sun, Mar 13, 2011 at 8:57 AM, Andrei Warkentin andr...@motorola.com wrote:
Sorry to butt in, I think I'm missing most of the context
herenevertheless... I'm curious, ignoring outer packaging and
product names, if you look at cards with the same CID (i.e. same
manfid/oemid/date/firmware
Excerpts from C. Scott Ananian's message of Sun Mar 13 16:41:36 +0100 2011:
I apologize; I think the code that sets timezone correctly might
have been code I wrote for litl, not OLPC.
No problem. Do you remember how it worked at Litl? Did you manipulate
/etc/timezone directly or using a distro
On Sun, Mar 13, 2011 at 1:00 PM, C. Scott Ananian csc...@laptop.org wrote:
On Sun, Mar 13, 2011 at 8:57 AM, Andrei Warkentin andr...@motorola.com
wrote:
Sorry to butt in, I think I'm missing most of the context
herenevertheless... I'm curious, ignoring outer packaging and
product names,
On Sun, Mar 13, 2011 at 1:04 PM, Sascha Silbe si...@activitycentral.com wrote:
Excerpts from C. Scott Ananian's message of Sun Mar 13 16:41:36 +0100 2011:
I apologize; I think the code that sets timezone correctly might
have been code I wrote for litl, not OLPC.
No problem. Do you remember
On Sunday 13 March 2011 02:01:22 C. Scott Ananian wrote:
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
and one unknown
Neat.
Cell phone technology?
http://www.wired.com/wiredscience/2011/03/diy-cellphone-microscope/
---
*Beth Santos*
Outreach Coordinator
Waveplace Foundation
Tel: +1 610 797 3100 x 44
Fax: +1 610 797 3199
Cell: +1 603 661 1273
http://www.waveplace.org
Waveplace on
On Sat, Mar 12, 2011 at 7:01 PM, C. Scott Ananian csc...@laptop.org wrote:
On Sat, Mar 12, 2011 at 5:51 PM, Arnd Bergmann a...@arndb.de wrote:
I've had four cards with a Sandisk label that had unusual characteristics
and manufacturer/OEM IDs that refer to other companies, three Samsung (SM)
On Fri, Mar 11, 2011 at 1:48 PM, Beth Santos b...@waveplace.org wrote:
Neat.
Cell phone technology?
http://www.wired.com/wiredscience/2011/03/diy-cellphone-microscope/
“It still amazes me how you can build near-research-grade instruments
with cheap consumer electronics,”
I guess people's idea
On 03/13/2011 01:21 PM, Arnd Bergmann wrote:
Do you have test results somewhere publically available? We are currently
discussing adding some tweaks to the linux mmc drivers to detect cards
with certain features, and to do some optimizations in the block layer
for common ones.
The tests have also helped expose other issues with things like sudden
power off. In one case a SPO during a write would corrupt the card so
badly it became useless. You could only recover them via a super secret
tool from the manufacturer.
Is there any sledgehammer process available to
It may well be the quality of the non-high-priced SD cards I use, but
with q2e42 and later OFW versions, when several specific XO-1s are
booted, OFW will occasionally (but not consistently) time out when
trying to read the developer key from the SD card. My usual bypass is
to unplug all external
G'day Mikus,
Fristly, use disable-security so that the developer key is not required
to be present. Is there a good reason for not disabling the security
system? However, if you are booting the laptop from the SD card this
may merely move the problem from developer key recognition to booting.
On Sat, Mar 12, 2011 at 03:46:02PM +1100, Sridhar Dhanapalan wrote:
There are three main questions raised by this process:
[...]
3. why must I wait 24 hours to get the developer key?
Presuming you are asking about an OLPC developer key rather than a
deployment developer key ... the delay
25 matches
Mail list logo
