Re: [Server-devel] Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-05 Thread Bryan Berry
Michailis, thanks for your quick reply small schools, the school server is all that you need. In the meantime, APs with controllable WDS behavior are recommended. I am not an expert on access points. Can you suggest a particular model that meets this criteria? The solution to that problem

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-05 Thread Sayamindu Dasgupta
On Tue, Mar 4, 2008 at 12:56 PM, Edward Cherlin [EMAIL PROTECTED] wrote: On Mon, Mar 3, 2008 at 10:41 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote: On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote: .snipped You're talking about testing the keyboard layout and fonts. What

Re: [Server-devel] Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-05 Thread Michail Bletsas
Bryan Berry [EMAIL PROTECTED] wrote on 03/05/2008 03:07:12 AM: Michailis, thanks for your quick reply small schools, the school server is all that you need. In the meantime, APs with controllable WDS behavior are recommended. I am not an expert on access points. Can you suggest a

Re: [Server-devel] Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Michail Bletsas
[EMAIL PROTECTED] wrote on 03/03/2008 02:38:00 AM: Questions: How many XO's can a single active antenna support? We only have two active antennas at the moment. The answer is always traffic depedent. Given the current status of the collaboration software on the XO and assuming that the

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Benjamin M. Schwartz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 John Gilmore wrote: | I recommend that once you have developer keys, you leave the machines | unlocked. You are going to be running a lot of unsigned builds in the | future -- you're customizing your builds. Eventually, there must be a way for

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Richard A. Smith
Bryan Berry wrote: Here is the Rough Test Plan I have in mind 1. Boot into firmware and run test-all Note that the current shipping firmware can sometimes report false positives for sticky keys in the keyboard test. So if you think you have sticky keys upgrade the firmware to Q2D13 and

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Edward Cherlin
On Sun, Mar 2, 2008 at 11:38 PM, Bryan Berry [EMAIL PROTECTED] wrote: Hey guys, Nepal should receive its shipment of 200 XO's in roughly 14 days from today. Here is the Rough Test Plan I have in mind 1. Boot into firmware and run test-all 2. Load customized image based on 656 build

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Bryan Berry
We need to do a lot of work on the localization, a lot. There hopefully will be a renewed effort on this from our team starting next week. There aren't 40 spare XO's. A chunk of those will go to the teachers (10-15) leaving some for spares and we may have a special class for kids not in the lucky

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Sayamindu Dasgupta
On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote: .snipped You're talking about testing the keyboard layout and fonts. What about localization of software? According to Pootle, except possibly for XO-Bundled (89%), the Nepali localization is not in good shape. The rest of the modules are

Re: Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-03 Thread Edward Cherlin
On Mon, Mar 3, 2008 at 10:41 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote: On 3/4/08, Edward Cherlin [EMAIL PROTECTED] wrote: .snipped You're talking about testing the keyboard layout and fonts. What about localization of software? According to Pootle, except possibly for

Testing 200 XO's in two weeks time for Nepal's pilot

2008-03-02 Thread Bryan Berry
Hey guys, Nepal should receive its shipment of 200 XO's in roughly 14 days from today. Here is the Rough Test Plan I have in mind 1. Boot into firmware and run test-all 2. Load customized image based on 656 build 3. Test localization on each XO (read Nepali, type in Nepali) 4. Test that basic