On Sun, Aug 26, 2012 at 12:32 PM, 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
>
p.s. One anti-theft thing that I forgot to mention in my previous list
serve response was that we label and ENGRAVE all the laptops with big bold
numbers and codes in various locations on the laptops so anyone can tell
exactly who they belong to. Its pretty obvious they are from a school or
organ
; >
> > 1. antitheft (Sameer Verma)
> > 2. Re: antitheft (Yannick Warnier)
> >
> >
> > --
> >
> > Message: 1
> > Date: Sat, 25 Aug 2012 12:41:43 -0500
> > From: Sameer Verm
2:41:43 -0500
From: Sameer Verma
To: XS Devel, "Devel's in the
Details"
Subject: [Server-devel] antitheft
Message-ID:
Content-Type: text/plain; charset=ISO-8859-1
Hello!
I'm looking to get a sense of how widely antitheft is being used and
to what level of succ
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 blo
We got around the need for antitheft measures with a community-based
approach. This may not work in all communities, but it has worked very
well for us.
BEFORE distributing any computers for student use, we held meetings with
all participants, including teachers, students, parents, and the
commun
Le samedi 25 août 2012 à 12:41 -0500, Sameer Verma a écrit :
> Hello!
>
> I'm looking to get a sense of how widely antitheft is being used and
> to what level of success. There was a post recently where Bruce Baikie
> came across 500 XO-1s in Ethiopia, that were locked, but the server
> was dead/g
K. Caron [mailto:reu...@laptop.org]
> Enviado el: lunes, 09 de julio de 2012 01:31 p.m.
> Para: Edward Lopez
> CC: server-devel; Elias Jacobo Castillo
> Asunto: Re: [Server-devel] Antitheft system failure
>
> Edward, Elias,
>
> Let's look at this in phases:
>
> -
Edward, Elias,
Let's look at this in phases:
-1: The XO has no lease and needs a lease to run. So using either method (a.
Standard Leases) or (b. Delegated Leases) you preload the XS with leases.
-2: You turn the XO and it the SD card, USB, and Open Wifi for a lease.
-3. It finds an open AP con
We have a small deployment of servers (ver 0.7), that we are planning to do
soon, but we have problems with the antitheft system: in a small test lab have
18 XOs just 6 appears included at the antitheft list in the Moodle and even
with the registered XOs we tested the "stolen" option and noting
On Mon, Aug 24, 2009 at 6:05 PM, Martin
Langhoff wrote:
> On Mon, Aug 24, 2009 at 11:45 PM, C. Scott Ananian wrote:
>> so you should probably return a
>> lease which is valid except for the fact that the signed string has an
>> randomly-chosen UUID
>
> Exactly my thoughts -- as you can see in the b
On Mon, Aug 24, 2009 at 11:45 PM, C. Scott Ananian wrote:
> so you should probably return a
> lease which is valid except for the fact that the signed string has an
> randomly-chosen UUID
Exactly my thoughts -- as you can see in the bug. Implementing that
goes beyond merely coding it -- it would m
On Mon, Aug 24, 2009 at 6:37 AM, Martin
Langhoff wrote:
> A while ago, Daniel fixed a bug in my changes to olpc-update, and that
> left me with a to-do item on the xs-activation side.
>
> Reviewed the situation on the OAT proto concept of always sending a
> stolen token, with the idea that xs-activ
A while ago, Daniel fixed a bug in my changes to olpc-update, and that
left me with a to-do item on the xs-activation side.
Reviewed the situation on the OAT proto concept of always sending a
stolen token, with the idea that xs-activation should do what the
protocol proposes: always send a 'stolen
14 matches
Mail list logo
