Language Selection

English French German Italian Portuguese Spanish

Gunfight at the Linux Corral

Filed under
Linux
PCLOS

As I promised in my previous post, I've decided to write about how I test Linux distros. But before we get to the testing, I figured I'd update you on the laptop situation. After a month or so with PCLinuxOS 2009.2 running smoothly, I discovered one small glitch for me. I was having a bit of trouble installing and running some newer versions of my favorite software. At first it was just Firefox. Version 3.6 was not available in the repositories, so I did a manual download and install from the Firefox web site. This led me to conclude that I needed to look at upgrading already.

I had been running the PCLinuxOS 2010 beta in VMWare Player for a while, and update after update it just kept getting better and better. So much better in fact, I decided it was finally good enough to install on the laptop. As a general rule, I do not use beta software as my main OS, but in my opinion this beta was ready for prime time. In fact, it even performs better on this machine than it's predecessor, and so far, it is as solid as a rock. There are still a few cosmetic issues to iron out, but I can live with those. Such things are generally the last to be cleaned up before a final release. They do not affect performance or stability, so I really don't mind(note: As of now, PCLinuxOS 2010 has been officially released).

At any rate, on to testing. Well almost...




re: Gunfight at the Linux Corral

What a maroon! You don't suppose there's a reason that the developers spend months to insure that all the software in the repo works with as many system configs as possible and then loudly discourage installing software outside of the official repos, do you? Thinking

PCLinuxOS is NOT meant to be bleeding edge, it's meant to work out of the box and be an easy to use reliable distro. Which it does beautifully, btw.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

today's leftovers

'Turbo Boost Max 3.0' and Mesa 17.2.4

  • Turbo Boost Max 3.0 Support For Skylake Fixed With Linux 4.15
    The platform-drivers-x86 updates have been sent in for Linux 4.15 and include a range of improvements for Intel hardware support. One of the bigger items is support for Skylake CPUs with Turbo Boost Max 3.0.
  • Mesa 17.2.4 Graphics Stack Lands for Ubuntu 16.04 LTS and Ubuntu 17.10 Gamers
    Canonical's Timo Aaltonen reports on the availability of the Mesa 17.2.4 open-source graphics drivers stack on the X-SWAT updates PPA for Ubuntu 16.04 LTS and Ubuntu 17.10 systems. Ubuntu systems have always lagged behind the development of the Mesa 3D Graphics Library, the Linux graphics stack containing open-source drivers for Intel, AMD Radeon, and Nvidia GPUs, but they usually catch up with it through a specially crafted PPA (Personal Package Archive) repository that can be easily installed by users.

OSS Leftovers

  • The Future of Marketing Technology Is Headed for an Open-Source Revolution
  • Edging Closer – ODS Sydney
    Despite the fact that OpenStack’s mission statement has not fundamentally changed since the inception of the project in 2010, we have found many different interpretations of the technology through the years. One of them was that OpenStack would be an all-inclusive anything-as-a-service, in a striking parallel to the many different definitions the “cloud” assumed at the time. At the OpenStack Developer Summit in Sydney, we found a project that is returning to its roots: scalable Infrastructure-as-a-Service. It turns out, that resonates well with its user base.
  • Firefox Quantum Now Available on openSUSE Tumbleweed, Linux 4.14 Coming Soon
    Users of the openSUSE Tumbleweed rolling operating system can now update their computers to the latest and greatest Firefox Quantum web browser.
  • Short Delay with WordPress 4.9
    You may have heard WordPress 4.9 is out. While this seems a good improvement over 4.8, it has a new editor that uses codemirror.  So what’s the problem? Well, inside codemirror is jshint and this has that idiotic no evil license. I think this was added in by WordPress, not codemirror itself. So basically WordPress 4.9 has a file, or actually a tiny part of a file that is non-free.  I’ll now have to delay the update of WordPress to hack that piece out, which probably means removing the javascript linter. Not ideal but that’s the way things go.

Red Hat and Fedora Leftovers