Language Selection

English French German Italian Portuguese Spanish

PCLinuxOS 2010.1 KDE4

Filed under
PCLOS

It's been a few weeks now that PCLinuxOS 2010.1 has been available. I have it installed on my 'old' laptop - a HP Compaq nx6325 - and this is my experience up to now.

A shock!

So, in went the CD and a few seconds later, the new PCLinuxOS boot screen came up, only to drop to a black screen after a few seconds. Gosh... this is odd. The download was fine, the checksum OK, burned at the lowest possible speed. I went to my desktop, popped the CD in and there everything was OK.

Back to the laptop. Try number 2. Again the same black frozen screen. Even after waiting several minutes, nothing moved. This was really a first. Never since I hopped over to PCLinuxOS (2007 TR1) had I encountered any problems of this kind on the laptop.

Happy Ending 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