Barry,BarryK wrote:I'll try this fix.
Hope you can make Puppy work on the XO - that would be fantastic !
Best of luck - from a fellow Sandgroper
Barry,BarryK wrote:I'll try this fix.
I think Intel will have quite a way to catchup - the Classmate is so far behind the XO's design [1] that it's not even funny - just see the coolling vents (just to mention the most obvious thing) on the Classmate and think about the conditions these laptops are supposed to be designed for...Sage wrote: to prevent another walkover for Intel?
delphi wrote:
I think Intel will have quite a way to catchup - the Classmate is so far behind the XO's design [1] that it's not even funny - just see the coolling vents (just to mention the most obvious thing) on the Classmate and think about the conditions these laptops are supposed to be designed for...
I think this is what happens with a "mass-produce-now-test-later" model. A conservative but more professional R&D model for OLPC should have helped it prepare for these post-launch "storms".We have painfully discovered the limitations of the mesh and current collaborative software in Mongolia, where the convolution of the number of laptops with bugs #5335 (more mDNS traffic than expected) and #5007 (mesh repeats multicast too much) make the perfect storm, which prevents anybody from using the network. We will continue to improve the mesh performance..
Batteries: .. the batteries are not lasting as long as expected. The extreme cold was the first suspect..
Ive tried explaining this problem of Mesh networking to many folks who jumped on the Mesh networks bandwagon. In literature its called a "broadcast storm problem".raffy wrote:Quote from the OLPC list:I think this is what happens with a "mass-produce-now-test-later" model. A conservative but more professional R&D model for OLPC should have helped it prepare for these post-launch "storms".We have painfully discovered the limitations of the mesh and current collaborative software in Mongolia, where the convolution of the number of laptops with bugs #5335 (more mDNS traffic than expected) and #5007 (mesh repeats multicast too much) make the perfect storm, which prevents anybody from using the network. We will continue to improve the mesh performance..
Batteries: .. the batteries are not lasting as long as expected. The extreme cold was the first suspect..
(Speaking of mesh, I work only with two teachers on cellphone "mesh" and I guess I am now short of time for it. Imagine a mesh of 500, such as in Mongolia. )
iottmco wrote: Since then they've deployed 30 proof of concepts worldwide.
I'm sure they will. After all, they have no choice - their whole 'Wintel' model they have relied on for their massive profits for so many years, if $200 OLPC XO-like PCs were to become common, will be in question. I expect they will scramble to produce a low-powered CPU to match the one in the XO first. However, to match XO's brilliant dual-mode screen is another story. And the list goes on...iottmco wrote: So I think you can be sure Intel's progressed and learned.
Wi-Fi technology is inherently complex one and there will always be problems in 'real life' depending on a particular scenario - I should know as I rely on wi-fi not just for my home network connections but for the access to the Internet as well. A "conservative" and "more professional R&D model" (not to mention billions of dollars) will not alway prepare you for all the possible problems. Just ask Intel - who can forget their, regardless of the controlled conditions available, spectacularly failed WiMax demo:raffy wrote:A conservative but more professional R&D model...
It easy to switch from Sugar XO interface to something more standard - see my post above. If your kids love, for example, reading (e)Books you may find that the XO is actually a much better machine...mdd wrote: I think the OLPC software really stinks.
...
I also had two spare eeePCs laying around, so I gave the two eldest the choice between the OLPC or the eeePC. The eee won hands down. It wasn't even close. --MDD
Delphidelphi wrote:For those still waiting for Puppy on OLPC, in the meantime the following shows how easy it is to switch (ie without installing another Linux distribution) from default Sugar to a another desktop environment:
Bill Clementson's Blog - switching to Xfce on the XO
( http://bc.tech.coop/blog/080130.html )
You're welcomerrolsbe wrote:Thanks for the link to set up Xfce!
great links everyone. i've included puppy(currently firehydrant) in my free linux cd's stack at the local coffee shop for a year now, but have never had reason to use it extensivly. (fast fancy lappy with annoying braodcom wi-fi)delphi wrote:Yet another distro running on OLPC XO...
This time it's Ubuntu Mobile:
( http://eclecti.cc/olpc/ubuntu-mobile-on-an-olpc-xo )