Language Selection

English French German Italian Portuguese Spanish

Fedora + Eee PC = Eeedora

Filed under
Linux

I am a fan of affordable technology. I like relatively cheap gadgets, and I like open source. When I heard about Asus’ Eee PC, I took it with a certain grain of salt. I thought that maybe it was just another company trying to take a piece of the pie from the One Laptop Per Child initiative.

Then the more I read about the OLPC, the more I realized that the two gadgets may have been created for different purposes. The OLPC is a non-profit, educational-social project, while the Eee PC is an affordable subnotebook being sold with the intent for profit.

The Eee PC’s price range varies from approximately $300 to $500; within that range you can get a configuration with a 2 GB, 4 GB, or 8 GB solid state drive, and for the 4 GB and 8 GB models, you can opt for an embedded webcam as well. All models come with 3 USB ports, 1 MMC/SD port, and a VGA port for an external display, which can display up to 1600×1280 resolution.

By default, the Eee PC comes with a slightly modified version of Xandros Linux with KDE as its window manager. Because the Eee PC is a full-blown Intel-based computer, there is absolutely nothing stopping us from installing other Linux distributions on it.

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