Language Selection

English French German Italian Portuguese Spanish

One Intel Inside Laptop Per Child

Filed under
OLPC

No matter how you feel about Teemu Leinonen's suggestion that One Laptop Per Child should use Participatory Design in developing a XO-2, it looks like Intel Corporation is already pre-participating in the next generation of OLPC products.

Just read their OLPC + Intel announcement closely:

Q: How will OLPC work with Intel technology?

A: Initially, OLPC is planning to add Intel Xeon processor based servers to their product offerings, taking advantage of world class performance, reliability and energy efficiency. In addition, Intel is developing a system board design for OLPC consideration in their next generation XO device.

We are also beginning to explore more wide ranging technology and product collaboration that will bring exciting new technology innovations to children around the world.

More Here




More in Tux Machines

Android Leftovers

Leftovers: OSS

Ubuntu 16.04 Review: What’s New for Desktop Users

Ubuntu is a tricky distribution. As much as I love it on my home server, my desktop is a different ballgame. In my experience, releases between LTS versions have many new technologies that may or may not survive in the next LTS. There were many technologies or features that Canonical thought were ambitious -- HUD, experimenting with menus, online dash search, Ubuntu Software Center, etc. -- but they were abandoned. So, if I were to use Ubuntu on my desktop, I would still choose LTS. Read more

Workflow and efficiency geek talks Drush and Drupal

I started using Drupal because I needed an open source content management system (CMS) to use in several community projects. One of the projects I was involved with was just getting started and had narrowed its CMS selection down to either Drupal or Joomla. At the time I was using a different framework, but I had considered Drupal in the past and knew that I liked it a lot better than Joomla. I convinced them to go with the new Drupal 6 release and converted all of my other projects for consistency. I started working with Drush because I wanted a unified mechanism to work with local and remote sites. My first major contribution to Drush was site aliases and sql-sync in Drush 3. Read more