Language Selection

English French German Italian Portuguese Spanish

How to Perfectly Kill a Perfect Distribution

Filed under
PCLOS

PCLinuxOS was the perfect distribution in 2007. It had all the bells and whistles to be an excellent Windows XP alternative.

When a distribution is able to configure my hardware, is ultra stable, highly updated and provide me with almost all the required software then I think that is the distribution I am looking for. PCLOS had all these abilities and more. That's the reason it was called the distro-hopper stopper. People loved it and it rose to the pinnacle of Distrowatch Page hit rankings. Not only reached; it stayed there for a good 6 months. If we consider that the distribution PCLOS dethroned was mighty Ubuntu, that makes PCLOS achievement even more impressive. On one hand Ubuntu had the backing of Canonical - they were sending free CDs, had tieup with the likes of Dell, had dozens ( maybe more ) developers working; on other hand there was PCLOS which had a very small dev team and no corporate backing, no big computer assembler backing them.

Yet PCLOS rose to top on account of sheer merit. It had the novelty to generate interest and the quality to sustain it. Kudos to Textar and PCLOS 2007. It was almost perfect.

Alas! that was 2007, however, this is 2008 and almost end of 2008. A lot has changed since then.

More Here




re: Perfect Kill

This guy will be eating his hat in another two or three years when the 2007 respin is released.

fundamental misconcetion about pclos

My impression is that he doesn't fully understand the concept of rolling release. I am running PCLOS on a relatively recent Vaio, just like him, and have everything up to date, including the kernel.

Well, I'm happy

Like the author, I'm in a new country, new job, new computers, etc. After I moved I had Sabayon, Mandriva 2008 and Mint on my Comp but I went back to Pclos, namely Minime. It works fine on my new comp (Athlon 6.4, 4 gig ram and GF 8600) I configured it the way I want it and I'm not a bleeding edge kind of guy so if the apps work then they work for me. The only niggle has been the webcam but it didn't work under other distros (free from work so not bought for linux compatability). It seems quicker than the others and it is what I'm used to. As for some of the crits - the desktop?? Most users would customise it anyway. Auto login?? Isn't the pclos way better - new users should get used to the idea of security. It is easy to change anyway. I was never happy about the Ubuntu way of doing things anyway.
Pclos, IMO is still a great distro for converts from xp and those who don't need everything brand spanking new. It works and works well on new and old hardware. Us pclos users waited for 2007 and were happy with the rolling release. I still know some who are using Big Daddy. I'm happy waiting for 2008 as I have the distro set up the way I like it.

Re: Kill a Distro

PCLOS is a "garage distro", with a small number of devs, and is heavily dependent on 1 person for packaging and release.

Yes, the install iso 2007 should have been updated with a newer kernel with newer drivers earlier this year. Even for a rolling release distro, an occasional respin of the iso would make it possible to install it on newer hardware. For example, I couldn't get PCLOS 2007 to install on a system with an ASUS M2M-VM-DVI motherboard. Some experimentation indicates that an install with this particular motherboard requires kernel >= 2.6.25. Since my main box has PCLOS running under a newer kernel, I used "remasterme" to build my own updated ISO. Clearly, this is not a general purpose solution.

This kind of malaise often happens with small "garage distros" ... it's certainly happened with Mepis and slackware and others.

Texstar seems to be somewhat of a perfectionist, and releases slowly. But, if you want a distro that, once you get it installed and updated, works really well ... then PCLOS may be for you.

We all get impatient for the latest stuff. Indeed, I have Mandriva 2009 RC running on my experimental box, running all the latest stuff. But, to get real work done, I use my PCLOS box. It's still a wonderful distro (and I've tried dozens). And, I'm sure that the long delayed 2008 release will be too.

PCLinuxOS is top notch

First, atangf, Suse started life as a fork of Slackware, but isn't based upon anything Slackware does. The same goes for Mandriva. It was originally Red Hat + KDE, but it's completely built and developed in-house. This is quite different from some other distros, like Ubuntu, that rely heavily on a parent distro, such as Debian. PCLinuxOS is sort of half and half. They get their initial base off of Mandriva, so they start with a lot of Mandriva SRPMs and compile them as PCLinuxOS packages with no modification at all. Then there are some packages such as Mandriva Control Center that get modified and packaged. And, there are other packages that don't come from Mandy at all, but from Suse, Fedora, or just source and get packaged. Once that happens, and the rebased ISO is released, all subsequent packages are built completely from original source. That's what happened with the original PCLinuxOS release and 2007. All subsequent releases use packages completely built by the development team from source. Those releases contain the original base's core packages such as gcc and development libraries, but everything else is totally in-house. Not moving to a newer gcc and libraries allows the distro to be a "rolling release" distro. That means PCLinuxOS 2007 is highly compatible with Mandriva 2007, but not later releases. This is quite different from distros that almost completely rely on a parent distro's development. Most Debian based distros rely heavily on Debian's work.

Now that that's cleared up, a new PCLinuxOS release is very, very near. I'm not a developer, so I don't know the inside story as to the holdup, but it's a small developer team and stability is first and foremost. I do know, however, with some inside knowledge, that a new release is very, very near. This should erase any problems the author encountered. But, since it is a rolling release, it's pretty much up-to-date if just updated regularly. There won't be a whole lot different, but it will hugely affect those that boot the CD with newer hardware.

The author had some really minor gripes, honestly. KDE 4.x is, by KDE's own admission, not ready for production systems. Those that run it are on the bleeding edge. It was determined by the developers and mostly agreed upon by the community, that KDE 4.x is not ready and shouldn't be the default desktop. I believe the new release will also still use KDE 3.5.9 as the default desktop. When KDE finally gets the feature set complete and becomes rock solid, then it will be included as the default environment. Most early users of KDE 4.x have done nothing but complain about it, even in the media.

KDM is in the LiveCD is because you can login as root to install it, or just log in as user to run it. Some people use the LiveCD to run on other computers, and some use it to just install it. It might be just a feasible to just login everyone as root, or just allow the installation from the user account, but why give people bad habits? New users should learn to become used to the user/administrator setup of Nix from the very beginning.

Unlike some distros that try to protect the users from themselves, PCLinuxOS allows the user to login as root if they have root access. This has been debated in the forum and the majority agrees that they like access to their root account via KDM. This is quite different from auto login, where your little brother could boot your system and be in your account, rummaging through your personal email or wreaking havoc on your system. I don't see the author's point on this one.

I could just keep going, but I'll stop here. It's a nothing but a difference in opinion here. Some people prefer the habits of Slackware over others, some Ubuntu, some Gentoo, some PCLinuxOS. This is why there are so many distros out there. PCLinuxOS takes a decidedly different course when it comes to your Linux experience than that of Ubuntu, where the user is much more control and there is absolutely no command line knowledge needed in PCLinuxOS. Ubuntu works most of the time, but when it doesn't, things have to be configured either by hacking a file or a command line entry. It's two roads to the same destination.

Like I said, we know PCLinuxOS 2007 is a little long in the tooth, but a new full release is very near, and hopefully will alleviate any problems anyone should encounter.

Comment viewing options

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

More in Tux Machines

Scrivener Writing Software has a Linux Version

In some ways, Scrivener is the very embodiment of anti-Linux, philosophically. Scrivener is a writing program, used by authors. In Linux, one strings together well developed and intensely tested tools on data streams to produce a result. So, to author a complex project, create files and edit them in a simple text editor, using some markdown. Keep the files organized in the file system and use file names carefully chosen to keep them in order in their respective directories. when it comes time to make project-wide modifications, use grep and sed to process all of the files at once or selected files. Eventually, run the files through LaTeX to produce beautiful output. Then, put the final product in a directory where people can find it on Gopher.

Gopher? Anyway …

On the other hand, emacs is the ultimate linux program. Emacs is a text editor that is so powerful and has so many community-contributed “modes” (like add-ins) that it can be used as a word processor, an email client, a calendar, a PIM, a web browser, an operating system, to make coffee, or to stop that table with the short leg from rocking back and forth. So, in this sense, a piece of software that does everything is also linux, philosophically.

And so, Scrivener, despite what I said above, is in a way the very embodiment of Linux, philosophically.

I’ve been using Scrivener on a Mac for some time now, and a while back I tried it on Linux. Scrivener for the Mac is a commercial product you must pay money for, though it is not expensive, but the Linux version, being highly experimental and probably unsafe, is free. But then again, this is Linux. We eat unsafe experimental free software for breakfast. So much that we usually skip lunch. Because we’re still fixing breakfast. As it were.

Details with Screen Shots Here

Anyway, here’s what Scrivener does. It does everything. The full blown Mac version has more features than the Linux version, but both are feature rich. To me, the most important things are: A document is organised in “scenes” which can be willy nilly moved around in relation to each other in a linear or hierarchical system. The documents are recursive, so a document can hold other documents, and the default is to have only the text in the lower level document as part of the final product (though this is entirely optional). A document can be defined as a “folder” which is really just a document that has a file folder icon representing it to make you feel like it is a folder.

Associated with the project, and with each separate document, is a note taking area. So, you can jot notes project-wide as you work, like “Don’t forget to write the chapter where everyone dies at the end,” or you can write notes on a given document like “Is this where I should use the joke about the slushy in the bathroom at Target?” Each scene also has a number of attributes such as a “label” and a “status” and keywords. I think keywords may not be implemented in the Linux version yet.

Typically a project has one major folder that has all the actual writing distributed among scenes in it, and one or more additional folders in which you put stuff that is not in the product you are working on, but could be, or was but you pulled it out, or that includes research material.

You can work on one scene at a time. Scenes have meta-data and document notes.

The scenes, folders, and everything are all held together with a binder typically displayed on the left side of the Scrivener application window, showing the hierarchy. A number of templates come with the program to create pre-organized binder paradigms, or you can just create one from scratch. You can change the icons on the folders/scenes to remind you of what they are. When a scene is active in the central editing window, you can display an “inspector” on the right side, showing the card (I’ll get to that later) on top the meta data, and the document or project notes. In the Mac version you can create additional meta-data categories.

An individual scene can be displayed in the editing window. Or, scenes can be shown as a collection of scenes in what is known as “Scrivenings mode.” Scrivenings mode is more or less standard word processing mode where all the text is simply there to scroll through, though scene titles may or may not be shown (optional). A lot of people love the corkboard option. I remember when PZ Myers discovered Scrivener he raved about it. The corkboard is a corkboard (as you may have guessed) with 3 x 5 inch virtual index cards, one per scene, that you can move around and organize as though that was going to help you get your thoughts together. The corkboard has the scene title and some notes on what the scene is, which is yet another form of meta-data. I like the corkboard mode, but really, I don’t think it is the most useful features. Come for the corkboard, stay for the binder and the document and project notes!

Community chest: Storage firms need to pay open-source debts

Linux and *BSD have completely changed the storage market. They are the core of so many storage products, allowing startups and established vendors alike to bring new products to the market more rapidly than previously possible. Almost every vendor I talk to these days has built their system on top of these and then there are the number of vendors who are using Samba implementations for their NAS functionality. Sometimes they move on from Samba but almost all version 1 NAS boxen are built on top of it. Read more

Black Lab SDK 1.8 released

QT Creator - for QT 5 Gambas 3 - Visual Basic for Linux Ubuntu Quickly - Quick and dirty development tool for python emacs and Xemacs - Advanced Text Editor Anjuta and Glade - C++ RAD development tool for GTK Netbeans - Java development environment GNAT-GPS - IDE for the following programming languages. Ada, C, JavaScript, Pascal and Python Idle - IDE for Python Scite - Text Editor Read more

Did Red Hat’s CTO Walk – Or Was He Pushed?

He went on to say that some within Red Hat speculate that tensions between Stevens and Paul Cormier, Red Hat’s president of products and technologies, might be responsible, although there doesn’t appear to have been any current argument between the two. Cormier will take over Stevens’ duties until a replacement is found. Vaughan-Nichols also said that others at Red Hat had opined that Stevens might’ve left because he’d risen as high as he could within the company and with no new advancement opportunities open to him, he’d decided to move on. If this was the case, why did he leave so abruptly? Stevens had been at Red Hat for nearly ten years. If he was leaving merely because “I’ve done all I can here and it’s time to seek my fortune elsewhere,” we’d expect him to work out some kind of notice and stay on the job long enough for Red Hat to find a suitable replacement. Turning in a resignation that’s effective immediately is not the ideal way to walk out the door for the last time. It smells of burning bridges. Read more