Language Selection

English French German Italian Portuguese Spanish

ZaReason CEO Sounds Off on Linux, Hardware ‘Compatibility’

Filed under
Linux
Hardware

Canonical’s “Ubuntu Friendly” hardware-validation program, which officially debuts next month along with Ubuntu 11.10, should make life a little easier for people with computers that don’t get along so well with Linux. But what if your computer is designed from the ground up to run Linux flawlessly? I recently got a chance to speak with ZaReason CEO Cathy Malmrose, whose company has been shipping Linux PCs for years, about precisely that question.

With the exception of ZaReason and a handful of similar Linux-oriented vendors, such as System76, few OEMs give much thought to how well their hardware can run open source operating systems. That’s why the Ubuntu Friendly program, which encourages Ubuntu users to run simple tests to measure how well their computers work with Ubuntu and then upload their results to a public database, is a great move on Canonical’s part. It promises to make it easier to choose Ubuntu-friendly PCs before purchasing, or find solutions for compatibility problems on the hardware one already owns.

ZaReason’s Take




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