El Wed, 07-07-2010 a las 01:58 -0400, Kevin Mark escribió:
On Tue, Jul 06, 2010 at 05:03:02PM -0400, Bernie Innocenti wrote:
PS: I just found yet another laptop which won't activate because the
clock was set to 15 July 2000 (not 2010!). Do you see many of these?
just a query as I dont
On Tue, Jul 6, 2010 at 10:14 PM, Bernie Innocenti ber...@codewiz.org wrote:
And that there are efforts to solve that in the future.
Oh, I was unaware of this. Who is working on it, and what's the exact
plan?
http://dev.laptop.org/ticket/9564
Now, folks, please be careful here with all the
On Tue, Jul 06, 2010 at 05:03:02PM -0400, Bernie Innocenti wrote:
PS: I just found yet another laptop which won't activate because the
clock was set to 15 July 2000 (not 2010!). Do you see many of these?
just a query as I dont know the details of activation: if the rtc is off by a
year or more
On Tue, Jul 06, 2010 at 04:36:55PM -0600, Daniel Drake wrote:
PS: I just found yet another laptop which won't activate because the
clock was set to 15 July 2000 (not 2010!). Do you see many of these?
This was probably a human error in the Fix_clock repair process that
happened on that
On Sat, Jul 3, 2010 at 9:54 AM, Bernie Innocenti ber...@codewiz.org wrote:
NetworkManager used to call ntpdate when it setup a connection. Was that an
OLPC addition?
Yes, although it's now present in litl's software builds as well.
We figured out that the ntp package has never been present
On Mon, 2010-07-05 at 08:22 -0600, Daniel Drake wrote:
On 3 July 2010 16:52, Bernie Innocenti ber...@codewiz.org wrote:
I checked: olpc-update-query only sets the clock if it's off by more
than 24hours, so it cannot serve as a replacement for ntpdate.
What's the requirement for
On 6 July 2010 10:10, Bernie Innocenti ber...@codewiz.org wrote:
Laptops with anti-theft enabled can get the time from the OATS server
when it's off by more than 24 hours. Unlocked laptops don't have a way
to synchronize the time at all.
All we need to fix it is a trivial shell script. Why
On Tue, 2010-07-06 at 11:21 -0600, Daniel Drake wrote:
I think it's fine that individual deployments can do it. But it
shouldn't be done globally because it weakens the security system.
Which security system, the theft deterrence?
Well, granting root access from the console already weakens it
On Sat, Jul 3, 2010 at 9:54 AM, Bernie Innocenti ber...@codewiz.org wrote:
Likely so, but the software should be able to compensate for it. After
discussing it on IRC, it seems that olpc-update-query should
automatically update the clock from the OATS server.
Do _not_ rely on this for accurate
On 6 July 2010 15:03, Bernie Innocenti ber...@codewiz.org wrote:
Well, granting root access from the console already weakens it to the
point of being useless. Who would bother to setup a fake DHCP, DNS and
NTP server when it takes 20 seconds to crack it from the console? :-)
Right. So with
On Tue, 2010-07-06 at 16:36 -0600, Daniel Drake wrote:
On 6 July 2010 15:03, Bernie Innocenti ber...@codewiz.org wrote:
Well, granting root access from the console already weakens it to the
point of being useless. Who would bother to setup a fake DHCP, DNS and
NTP server when it takes 20
On 3 July 2010 16:52, Bernie Innocenti ber...@codewiz.org wrote:
I checked: olpc-update-query only sets the clock if it's off by more
than 24hours, so it cannot serve as a replacement for ntpdate.
What's the requirement for super-accurate clocks on the XO?
Daniel
On Fri, Jul 02, 2010 at 08:15:38PM -0700, Hal Murray wrote:
Was: Subject: =?ISO-8859-1?Q?Caacup=E9?= war bullettin -- day 1
ber...@codewiz.org said:
* Date not being updated
One laptop booted with clock set to the Epoch.
Is that one of the old XOs that had troubles with the tiny battery
El Fri, 02-07-2010 a las 20:15 -0700, Hal Murray escribió:
Is that one of the old XOs that had troubles with the tiny battery feeding
the TOY/RTC clock when the main battery and wall power are both disconnected?
I forget the details, but I think there was a problem with the battery
El Sat, 03-07-2010 a las 09:54 -0400, Bernie Innocenti escribió:
Likely so, but the software should be able to compensate for it. After
discussing it on IRC, it seems that olpc-update-query should
automatically update the clock from the OATS server.
I checked: olpc-update-query only sets the
15 matches
Mail list logo
