Language Selection

English French German Italian Portuguese Spanish

PCLinuxOS Preview-9

Filed under
PCLOS
Reviews
-s

PCLinuxOS is a binary-based Linux distribution that got its start during the summer of 2003 and was based at that time upon Mandrake 9.2 (now known as Mandriva). It's presented as a livecd, but one of its main features is its wonderful graphic harddrive installer that offers the user a beautiful fully functional complete desktop operating system. To call it a livecd is an injustice. However, Texstar, the main developer calls it just that on his site. To quote the legend, "PCLinuxOS Preview 9 is an English only self-booting live cd that runs entirely from a bootable CD without installing anything on your computer. Data on the CD is uncompressed on the fly allowing up to 2 GB of programs on one CD."

Preview 3 made it's short lived appearance in the early Fall of 2003 and was originally built upon Mandrake 9.2. Preview 4 was released in October 2003 and was mainly bug fixes and a few updates to Pre-3. However subsequent releases have been built upon the prior. At that time Mandrake was still using a 2.4 kernel, devfs, and XFree86. Texstar et al have since built an entirely new os upon its own structure and its own merit. It has evolved into its own right much the way Mandriva has evolved way beyond its Redhat beginnings. Texstar has developed PCLOS into a modern os utilizing a 2.6.11 kernel, xorg 6.8.2, and udev with hal and KDE 3.4.1. Again, it'd be better to quote the man himself from a post right here on tuxmachines, "PCLinuxOS Preview 4 was initally based on Linux Mandrake 9.2. PCLinuxOS Preview 5,6,7,8 and 9 have been built against the prior PCLinuxOS release. Thank you Mandriva for giving us a good base to work upon.

Preview 9 features Kernel 2.6.11-oci11 which has been patched and tested to work well with KDE 3.4.1. KDE 3.4.1 utilizes the Hal/dbus backend for autmounting removable media such as usbkeys, cdroms, cameras, scanners and other perpherials. We have tried to provide you with a complete out of box working experience."

Another advantage to livecds is their innate ability to allow the user to test a distribution before actually installing to their harddrive. I believe most modern Linux binary distributions will eventually go this way - or should. This method has so many advantages in addition to try-before-you-commit, such as having a fully functional computer while the install takes place. No more are the bored minutes watching a progress bar with anticipation. Read your email, surf the web, or play a game while the harddrive installer does its thing.

The harddrive install is a thing of beauty. Not only does it function well, but it does it in style. A gorgeous graphical interface walks the user through the install hiding the tendious innerworkings without limiting the users choices. It's so easy, click click click and you're in your nice new operating system ready to add any desired software and carry on with your work or play.

This is exactly what I did. When I booted up my new os, the first thing I did was fire up synaptic and effortlessly installed the kernel sources. Two or three clicks I believe was all it took.

I exited my session of kde and chose "console login" and was taken to the terminal. Here I mounted my archive partition and ran the nvidia graphic driver installer. Then I edited the xorg.conf with nano, changing nv to nvidia under the device section, and issued the command "startx". No fuss no muss. Can't ask for anything more! But that the key to PCLOS. With perhaps only a few exceptions, none I experienced personally, it just works. In less than 5 minutes from booting my fresh PCLOS install, I was enjoying gl screensavers and 3D games.

New versions in this release include:

  • kernel-pclos-i586-up-1GB-2.6.11.oci11.mdk-1-1oci

  • kdebase-3.4.1-4tex
  • xorg-x11-6.8.2-3tex
  • udev-057-1tex
  • gaim-1.3.0-2tex
  • fluxbox-0.9.12-1tex
  • Full List

Updates and newer versions of applications are continuously being offered. Seems almost as though Texstar works around the clock 24/7 to update, fix bugs, and fill requests. His synaptic (and apt-get) installable rpms are offered on mirrors all over the world and Preview 9 comes with some mirrors already configured. I needed only to say yes to the pop up suggesting I update the list. To help support development, Texstar et al also have a Premium server for those individuals who make donations. As explained by Texstar,

"To reward those who send development funds via paypal, we have established a premium access software server for PCLinuxOS. This repository provides unlimited bandwidth and storage. It is not a free server and is only available at this time to those who donate funds towards the development of PCLinuxOS. All new software packages appear on this server first then at a later date, the public server gets the packages."

If you would like to make a donation and receive your PASS to the premium server, please consult this page for details.

In conclusion, this release, much like its predecessors, was the most gorgeous operating system I'd ever seen. But beyond that it was still the most stable, fully functioning and complete OS I'd had the pleasure of testing. I found it fast in operation, a feast for the eyes, and unsurpassed in ease of use. It just gets better and better each release.

Besides the sneak peek shots showing the absolute beauty of PCLOS, I have posted some of the final depicting some of the functionality that can be yours. Please see my Sneak Peek for more details on some of the new features included as well.

Bittorrent available here. It was coming in as fast as my dsl could handle earlier today.

More in Tux Machines

GitLab Web IDE

  • GitLab Web IDE Goes GA and Open-Source in GitLab 10.7
    GitLab Web IDE, aimed to simplify the workflow of accepting merge requests, is generally available in GitLab 10.7, along with other features aimed to improve C++ and Go code security and improve Kubernets integration. The GitLab Web IDE was initially released as a beta in GitLab 10.4 Ultimate with the goal of streamlining the workflow to contribute small fixes and to resolve merge requests without requiring the developer to stash their changes and switch to a new branch locally, then back. This could be of particular interest to developers who have a significant number of PRs to review, as well as to developers starting their journey with Git.
  • GitLab open sources its Web IDE
    GitLab has announced its Web IDE is now generally available and open sourced as part of the GitLab 10.7 release. The Web IDE was first introduced in GitLab Ultimate 10.4. It is designed to enable developers to change multiple files, preview Markdown, review changes and commit directly within a browser. “At GitLab, we want everyone to be able to contribute, whether you are working on your first commit and getting familiar with git, or an experienced developer reviewing a stack of changes. Setting up a local development environment, or needing to stash changes and switch branches locally, can add friction to the development process,” Joshua Lambert, senior product manager of monitoring and distribution at GitLab, wrote in a post.

Record Terminal Activity For Ubuntu 16.04 LTS Server

At times system administrators and developers need to use many, complex and lengthy commands in order to perform a critical task. Most of the users will copy those commands and output generated by those respective commands in a text file for review or future reference. Of course, “history” feature of the shell will help you in getting the list of commands used in the past but it won’t help in getting the output generated for those commands. Read
more

Linux Kernel Maintainer Statistics

As part of preparing my last two talks at LCA on the kernel community, “Burning Down the Castle” and “Maintainers Don’t Scale”, I have looked into how the Kernel’s maintainer structure can be measured. One very interesting approach is looking at the pull request flows, for example done in the LWN article “How 4.4’s patches got to the mainline”. Note that in the linux kernel process, pull requests are only used to submit development from entire subsystems, not individual contributions. What I’m trying to work out here isn’t so much the overall patch flow, but focusing on how maintainers work, and how that’s different in different subsystems. Read more

Security: Updates, Trustjacking, Breach Detection

  • Security updates for Monday
  • iOS Trustjacking – A Dangerous New iOS Vulnerability
    An iPhone user's worst nightmare is to have someone gain persistent control over his/her device, including the ability to record and control all activity without even needing to be in the same room. In this blog post, we present a new vulnerability called “Trustjacking”, which allows an attacker to do exactly that. This vulnerability exploits an iOS feature called iTunes Wi-Fi sync, which allows a user to manage their iOS device without physically connecting it to their computer. A single tap by the iOS device owner when the two are connected to the same network allows an attacker to gain permanent control over the device. In addition, we will walk through past related vulnerabilities and show the changes that Apple has made in order to mitigate them, and why these are not enough to prevent similar attacks.
  • What Is ‘Trustjacking’? How This New iOS Vulnerability Allows Remote Hacking?
    This new vulnerability called trustjacking exploits a convenient WiFi feature, which allows iOS device owners to manage their devices and access data, even when they are not in the same location anymore.
  • Breach detection with Linux filesystem forensics
    Forensic analysis of a Linux disk image is often part of incident response to determine if a breach has occurred. Linux forensics is a different and fascinating world compared to Microsoft Windows forensics. In this article, I will analyze a disk image from a potentially compromised Linux system in order to determine the who, what, when, where, why, and how of the incident and create event and filesystem timelines. Finally, I will extract artifacts of interest from the disk image. In this tutorial, we will use some new tools and some old tools in creative, new ways to perform a forensic analysis of a disk image.