This (quite long) article has been written by me for two primary reasons: One, to hopefully save someone else the time and hassle associated with trying out various Linux distributions, and two, to promote some discussion and feedback regarding what a modern Linux distribution should be, and of course to contrast this with what is currently available. I am exploring the offerings of MS Windows, BeOS and MacOSX, and then taking on a number of well-known Linux distributions.
For a while now I’ve been an “OS Junkie”. I like to keep up to date on what’s happening in the OS world, and I spend way too much time researching and trying out alternative OS’s. I use a computer for everything from video editing and music production to accounting, web development, and graphic design, so my Dream OS has to be up to the challenge of handling most, if not all of these chores.
In short, I probably fall into the “Power User” category, and am constantly looking into how I can improve both my productivity and my user environment, either through software or OS changes. To that end, I’ve used quite a few different OS’s, on quite a few different platforms. My current desktop system’s based around a 1.2Ghz Athlon, 512 megs of DDR ram, 2 video cards (an older ATI All-In-One-Pro, and a Sis 300 based card), a SB Live video card, and about 200Gb of drive space. I also have a large assortment of add-ons used with this particular box… Everything from scanners to drawing tablets, and even a digital postage scale that hooks into the serial port.
My goals are lofty: To try and find the ideal OS for my own personal usage, which will allow me to work the way I want to, while not shorting me when it comes down to the tools and features that I need in order to “get the job done”, no matter what that job might be. And yes, it has to look good too! Eye candy might not be a concern for you, and there’s very many good arguments against eye candy (with the number one concern being that eye candy often just equals wasted CPU cycles), but for me, I want to work in an environment that’s not only functional, but also one that looks good.
I’m not a huge gamer, but the ability to play the odd game would also be nice, as would the ability to handle all of my non-gaming activities, from Web development to Graphic design and video editing.
Before we get into the Linux distributions specifically, let’s look at some of the non-Linux alternatives. This will hopefully provide some background on what I don’t want, while providing us with some hard data about what I do want. We’ll start with the biggest list, Windows and then work our way down.
Obviously the Windows family of OS’s is going to factor in here. There’s been arguably more work done on the Windows platform than on any other modern Operating System, and it shows! Windows owns the world, as far as consumer Operating Systems go, and they’re very well known, so without further ado, here’s some things I do and don’t like about Windows (oh, and by the way, unless noted, most of the Windows references refer specifically to Windows XP âMany of the issues I will note are present in other Windows versions as well, but since XP’s the latest Windows version, this is the one we will focus on):
- There’s a plethora of software’s available: Just about everything’s available for Windows, from music sequencers to cad programs, there’s an app out there for Windows that will do the job. Similarly, there are drivers out there for virtually all hardware I’m ever likely to run on my PC. Software support is definitely not a problem when using Windows!
- Keyboard Shortcuts: Windows has a keyboard shortcut for virtually every function, and if it doesn’t have it, there’s any number of add-on programs that will provide such features to you.
Similarly, if you want to, or have to due to hardware issues, you can set the more modern versions of Windows up with an included utility which will let you substitute keyboard commands for mouse actions. This functionality is a huge bonus to Windows as it allows one to flip between programs knowing that these shortcuts are common from one program to another.
- Customization: Sure, all OS’s allow you to customize it’s look and/or feel to a certain extent, but it’s the degree with which one can modify his or her environment that really interests me, and Windows is up near the top of this category both with it’s features, and with the ease at which you can customize them (although arguably, many of these features are either hidden away, or are accessible only with the aid of 3rd party software).
With the appropriate tools, I can change the look of Windows to virtually anything I can dream up, and that’s saying something!
- Common Look and Feel: This kind of ties in with the Keyboard shortcuts as there are a number of Windows elements that help to tie 3rd party applications together and make them operate and appear similarly to all users. Much of this can be attributed to the GUI of Windows, which provides a common, and somewhat skin-able/theme-able GUI for all apps to run under.
This allows one to jump from one Windows application to another without having to learn a new interface. This Common Interface is a big plus when it comes to being productive, and it’s one of the many strengths to the Windows Operating System.
- Quick and Responsive: Well it should be as most companies tend to optimize everything for Windows! Windows, at least when just using one or two apps, is very snappy on my machine. Granted, when I have multiple apps open (which is virtually every time I’m on the computer, mind you), the system can bog down somewhat, but for the most part Windows is “The” desktop by which others are judged by most people, as far as responsiveness is concerned.
- It can be slow: As mentioned above, Windows can bog down when many apps are open simultaneously. True, a dual CPU machine would help immensely with this (XP is SMP-capable!), but we’re looking specifically at the operating side here. Multiple CPU’s will also help to speed up my Linux box when and if they’re added (although Linux would of course require that I build an SMP-capable kernel). Ideally, I’d like an OS that allows me to switch my focus between apps without noticeably slowing down, or taking awhile for the CPU’s focus to shift gears (as can happen when burning a CD-ROM and typing a letter, for instance).
- Built in GUI capabilities are limiting: As mentioned above, I can customize virtually every aspect of Windows I want to, from the GUI itself, to how keyboard shortcuts are received and handled. However much of this customization is handled only by 3rd party apps. Windows has came a long ways as far as what it allows the user to do, but to still get the most from a Windows system, you have to typically use a 3rd party program. This often requires additional $$, and it often adds another application to those already running in the system tray. This in turn results in more CPU cycles and memory going towards a feature which I for one feel should be included with the OS itself. Virtual Desktops under Windows is an excellent example of this, in that if you want Virtual Desktops, similar to Linux and BeOS, you must run a 3rd party application to provide this functionality.
- Stability: Windows XP goes a long way towards making Windows a stable platform. It’s much more stable than Windows 98, and arguably more stable than NT ever was, but it is by no means perfect. I’ve gotten everything from the dreaded “Blue Screen of Death” to popups saying that Windows can no longer find a valid license on my machine thanks to the bugs in XP!
Don’t get me wrong, XP is a nice OS, and it’s fairly reliable. But for someone like myself who’s always “pushing the limits” of what a machine can do, XP is a long way from perfect. The ultimate example of the problems this can cause is how XP reconfigures itself without asking. Allow me to explain…
I do a fair amount of music composition and recording on my PC, and as such, I strongly feel that a PC should be seen and not heard. I don’t need my PC going “beep” in the middle of a recording session just to let me know that an update’s available (or for any other reason for that matter!). So I typically turn all the system sounds off on my PC and save that scheme as my default.
So you can imagine how upset I get when I boot up Windows and hear Windows default opening sounds play. This is my cue that something has changed within Windows, and that Windows in its infinite wisdom has reconfigured itself again without asking me. This problem is a great example of why I want off the Windows platform: I want an OS that works great and one that remains configured as I set it. I don’t need or want an OS guessing at what’s best for me, and then making changes without my approval. A first-time computer buyer might appreciate such features, but I for one loathe them.
- Security: It’s Windows… It’s full of holes, and more are discovered every day. Enough said.
- Can’t optimize core system: By this I’m referring to the fact that Windows is a closed-source system. The users don’t have the access necessary to do such things as optimize the kernel for a particular platform. This isn’t a major problem, but when you consider all of the legacy applications that Windows supports, you naturally have to wonder how fast and responsive it could be if it was optimized and targeted at modern PC’s. Rather than have a kernel that runs on everything, it would be nice to strip out the things that don’t apply to my setup and optimize it for the hardware I do have. On the other hand, this is one of Linux’s strong points!
The BeOS system is still around in several forms, but it is no longer actively maintained (As much as I like them, Hobby releases of BeOS, and promises of Zeta do not have the same affect as a company collectively making all of the decisions relevant to building a cohesive OS). I used it for a while, and still do on occasion, but the lack of support for modern technologies has kept me from staying in BeOS for too long. BeOS still has some features I’d love to see in my dream OS though.
- It’s fast! Very fast!! In fact BeOS is the speed by which others are still based in my case. I figure that if an unsupported OS on unsupported hardware can be this fast, that there really isn’t an excuse for other GUI’s to crawl on this same system.
- Meta-Data: BeOS’s meta-data is still talked about in geek circles. I never used it to the extent that others have, but it was always nice to know that I could tag any file with any meta-data I wanted to, knowing that I could quickly query for the file later via BeOS’s built in search/query capabilities.
- The ability to quickly drill down to files: With the BeOS, you could simply right click any folder, whether it was on your desktop, or in Tracker, and a popup menu would appear allowing you to both browse, and drill down into the folders contents. No other OS has achieved this level of integration yet, and this is one of the things I miss most about the OS.
- Resolutions specific to virtual desktops: This one is one of those features, which I loved. As a Web Developer, I need to not only test my code on different machines, and operating systems, but also at different resolutions on those machines. In Windows, this requires a trip into settings to change my display mode, and every time I do this, I end up resizing my desktop, and the icon placements on that desktop.
With most OS’s, it’s a similar process: Switch resolutions system-wide, and then deal with the ramifications.
With BeOS though, one can assign resolutions to specific desktops. So when clicking “Virtual Desk #3”, for instance, I can work on a 800×600 screen, whereas “Virtual Desktop #2” might give me a 1280×960 resolution, and “Virtual Desktop #1” might provide me with a 1024×768 setup. It couldn’t be easier, and I really wish this feature were supported on more OS’s.
- Lack of modern features: This kind of ties in with my previous point about web support. Quite simply, PC hardware is still moving forward at quite a fast pace. However the BeOS is stuck in 1997, give or take a year. There are 3rd party drivers and apps popping up here and there, but in general, as you upgrade your PC, you’re more and more likely to be adding a piece of equipment which the BeOS simply won’t recognize.
I am glad to see that some independent developers are adding new drivers, but this by no means something that one can rely upon. I don’t really care if there’s no parent company behind an OS, but building my dream system around an outdated, and un-supported OS would be kind of stupid on my part. I plan on this system growing with my PC as new hardware’s added and old components are upgraded. I’d hate to be in a situation in a year where I souped up my computing capabilities, only to find out that I can no longer use my OS due to the upgrade, and unfortunately that’s what would happen with the BeOS in its current incarnation. I really hope that some of the open source attempts at building a BeOS clone succeed, but even then, I have to wonder if such efforts will always be playing “catch up”, as far as hardware and drivers is concerned.
I’ve played with OSX a bit, and I must say that it has a lot of impressive features. Unfortunately, the first things that come to mind when I think of OSX is “Mmmm… Eye Candy”, rather than “What an outstanding OS. I can see this growing and maturing with me and my development environment”.
I’m sure that a lot of this impression is due to me not owning or having 24-hour access to OSX, hence my knowledge of it is more from reading, and the odd “doodling” while in my local Mac resellers. With that said, I would love to have an OSX box around, and based on my limited experiences, I feel that OSX would have the potential to become my main machine. However… I don’t have such access, and I certainly can’t afford one currently. Let’s delve into the pluses and minus’s I’ve perceived, as they apply to my dream system.
- Eye Candy: I’ve touched on this before, but eye candy is important to me. OSX has lots of it! Behind the superficial though is a robust, very stable Unix backend. I’ve not spent any time on dedicated Unix boxes, but I have spent considerable amounts of time on Linux systems, so I can appreciate many of the features that a Unix based OS would provide me with. In short, OSX looks and feels “cool”, It’s fun to use, and it really reminds me of how a computer can look and feel when it’s entirely produced according to one company’s plans and recommendations.
- Easy to use: Apple doesn’t appear to have “dumbed down” OSX to the extreme that Microsoft has its Windows XP release, but OSX is undeniably easy and intuitive to use. It’s software uses common controls and looks to create a truly unified, “all-in-one” computer system that’s easy-to-use, while being capable of everything from audio and video editing, to such simple pleasures as browsing the web and checking email.
- Excellent multimedia capabilities. OSX is an excellent candidate for graphical work, as well as sound and video editing. Its low latency and high quality inputs show that it was made with multimedia uses in mind.
- Unix backend: Unlike previous versions of Apple operating systems, OSX is built on a Unix kernel (FreeBSD actually), and as such it’s as rock solid and powerful as you’d expect. Similar to Linux, I’m told it’s virtually impossible to kill the underlying OSX system. This reliability, in addition to the fact that it makes it much easier to use Linux and Unix apps under OSX, is a very big plus for this operating system. I like the fact that it’s both pretty and easy to use, in addition to built on a rock-solid base.
- Cost: Lets face it, Apples are very expensive, and for the money they’re underpowered. I won’t get into the usual arguments about Apples quality nor about how PPC systems can outperform similar x86 systems, but the facts are that you can purchase a very powerful x86 based PC for the same money that it would cost you to purchase a modest Apple machine. I can appreciate that quality costs money, but I can’t justify Apples prices no matter how “pretty” their machines look. In my opinion, you can build an equally capable, and sharp looking Linux machine for a fraction of the cost of an Apple.
Additionally, unless I want to run my Windows apps under Virtual PC (which also costs $$), I have to purchase all new versions of my software in order to run them natively under OSX. When you add the price of the PC together with the cost associated with purchasing all new software, it gets very expensive very quickly.
- That damn mouse: Here’s an argument that’s been around for as long as the Mac itself has. It goes something like this:
x86 User: I can’t stand the fact that the Mac only has one mouse button. I need at least two to be really productive!
Mac User: You can do everything you can with 2 buttons just as easy, if not easier on a Mac with just one button. Anyway, if you really need a mouse with more buttons, you can buy them and add them to your system.
x86 User: But that’s adding even more cost to an already expensive system. For the money I’d spend on a Mac, it should come “ready to use” out of the box!
And so on.
For my needs, I recently purchased a 7 button MS Intellimouse, and I’d find it very difficult to use anything but now. The ability to assign different tasks to the extra buttons dependant upon the program you’re using, is a huge plus to using both Windows and Linux. Yes, you can probably get an Intellimouse up and running under OSX, but I agree that for the money you’re spending, having to immediately replace your expensive mouse is indeed a pain in the you-know-what! Even such simple things as surfing the web are made that much easier if you can just hit the side buttons of your mouse to move forward or backwards. Similarly, coding is much easier being able to use the mouse’s buttons to copy and paste. Suffice it to say that I need that Intellimouse to work with my dream system!
- Future’s unclear: Not to turn myself into a swami, but if you follow the news, Apple’s future is very much in flux right now. No, I’m not one of those people who think that Apple’s going to go away, but they’re definitely going to be changing something as far as their architecture goes.
While much of this is speculation, it’s fairly well known that Apple’s about fed up with Motorola’s inability to produce faster chips in a timely manner. Just the other day Adobe released a report stating that an x86 PC is preferable over an Apple box for graphic design work simply because the raw computing power in an Apple is so far behind it’s x86 counterparts. This is pretty powerful stuff considering that Apple’s crown jewel has always been Photoshop, and it’s users are generally artistic-type people who swear by Adobe.
What remains to be seen is how Apple will deal with this setback. Rumors indicate that it can go one of 4 ways right now:
- Apple switches over to x86 chips.
- Apple switches over to AMD’s forthcoming 64bit x86 compatible chip (The infamous Opteron we’ve all been hearing about)
- Apple switches over to IBM’s forthcoming PPC chip, which is miles ahead of Motorolas offerings (supposedly… These aren’t even in production yet).
- Or Apple chooses to stay with Motorola and tries to increase their market share through other methods besides raw computing power.
If anything other than number 4 happens, Apple will have to re-tool OSX for use with the new CPU, and this will more than likely mean that all existing OSX software will have to be re-coded to work with the new systems.
I don’t know about you, but I’d hate to spend $5000.00 on new Apple hardware and OSX software only to find out six months later that my system and software are now obsolete, and that if I want updates and such, I’ll have to upgrade to the new platform. This is unacceptable to me, and it’s really unfortunate that Apple is in such a position. They’re still trying to woo developers over to OSX, and just as they’re staring to make some headway, they must make a decision which would essentially send them back to square one in the game.
So now that we’ve identified the 3 biggies in the OS world (Well, 2 biggies, and one “also ran”), let’s look at what this article’s supposed to be about: Linux!
To be fair, I’m going to do a quick plus/minus review of Linux also before we delve into the various Linux distributions. As much as I like it, Linux isn’t any more perfect than the other OS’s we’ve discussed (Well… Maybe it’s “more perfect” than some of these, but it’s not perfect itself!).
Linux is such a generic thing these days. When you say “Windows”, you naturally think “Microsoft”. When you think “OSX”, you think “Apple”. But when you think of Linux, what do you think of?
It could be Redhat, Suse, Mandrake, Gentoo, Sorcerer, Slackware, Free, Open Source, or just about any other common Linux company or term (How many of you thought of Linus Torvolds when you thought about Linux?). Linux is simply a kernel when you get right down to it. It’s the applications that run on top of that kernel and how they’re configured which make all of the difference! With that in mind, here’s some of the plus’s and minus’s I see, as far as creating a proficient and enjoyable Linux experience:
- Cost: One of the first things that comes to mind as a big plus for Linux is its cost. This is kind of a double-edged sword for those who want to make money, but Linux is for the most part a free operating system. Yes, you need money to build or buy the hardware on which you’ll run Linux, but the chances are that you already own hardware which will do the job, be it a PPC based machine, or an x86 one.
Let me put forth this friendly piece of advice though: Support whichever distribution you choose to use. Without support, the companies that are really pushing Linux to the desktop will disappear, and we really don’t want that, do we? Whether you pay for your distribution of choice is totally up to you, but I would recommend giving something back in some form, be it through programming, volunteer work, or simply by paying for your software and/or distribution. Many independent developers now take donations also via Paypal. Put simply, the economic model for Linux is really aimed at giving the consumer the benefit since you can try and use most things for free. It’s only once you’ve evaluated and settled on a package or distribution that you should then consider what you’ve got, and what that’s worth to you.
Ok… My brief “Come on guys” speech is over. Back to the analysis!
- Flexibility: This is a big one when it comes to Linux! While it is true that Linux is known for it’s reliability as a server OS, Linux on the Desktop is just starting to take off and I expect to see a lot of action in this area over the next several years. By “flexible”, I’m referring to the fact that you can make Linux into virtually anything you want to!
For example, it’s a given that Linux is an efficient, proven, and reliable platform for servers and server development. The desktop is a different field entirely though in that you want the users interaction (the mouse movements and keyboard entries) to take precedence over any services and programs running in the background. If you had to wait for your quickly typed verbiage to appear in a Word Processor simply because Linux is busy FTPing something in the background, you’d probably quickly tire of it as a desktop OS.
But Linux is a beast of many faces, and as such you can “tune” it to be anything you want. If you’re using it for a server, you want those background processes to take precedence as they’re serving out content (or whatever) to your users. A servers highest priority should be to serve its users equally, and as fast as possible.
For a desktop machine though, we want it to only serve one person: You! As such, the kernel has to be tweaked and told to not dedicate so much attention to those background processes, and to pay more attention to things like video and input speed. You can do this with Linux. You can’t do it so easily with OSX, Windows, or many of the other desktop OS’s (You can use virtually any OS as a basic server, but the performance will not be anywhere near that of a dedicated server system).
If you’re “in the know”, you’ll know that Windows offers different versions of its OS for server usage. Similarly, OSX has a dedicated server version. And while server-specific versions of Linux are springing up here and there, the core systems are still more or less just like the desktop versions of Linux. Their kernels are just tweaked differently, and the apps that are included are usually different and pertinent to the task at hand. You probably don’t need an advanced network packet sniffer on a desktop OS (but you might… I certainly don’t!), but in the same sense, you don’t need a fast and flashy GUI for a server OS. A desktop system’s for using every day, while a server system’s generally meant to be setup, and then just left alone to serve out content as needed.
And it doesn’t end there! There’s all kind of patches and tweaks available to tune your kernel for real-time responsiveness, pre-emptive multi-tasking, and many others. It’s truly “your system”, and as such it’s up to you to decide what “your system” is.
- Support: Linux is widely supported, both by its users, and also by the companies that have chosen to market it. You can find dozens, and perhaps hundreds of books on Linux these days, and you can find even more websites dedicated to the usage and administration of Linux.
In fact when I install a new version of Linux these days, I usually opt to not install any of the included documentation as I can quickly “Google” for the details I need as I need them. Usenet’s another great source for Linux support and help. In short, there are more sources for Linux information than I’ll ever need, and it’s only growing by the day as more people make the switch.
- Lots of software: I have a love hate relationship with the amount of software that’s available for Linux. You can go to freshmeat.com or sourceforge.com and find literally hundreds of programs, and that’s just the tip of the iceberg, so-to-speak.
My only problem with all of this software is that much of it’s a work in progress. This is largely due to Linux being an “up and coming” OS, and while I can often find a new and unique tool to do the task at hand, I also am often questioning why something looks or acts the way that it does.
I guess the best way to sum it up is this: With Linux you’ll spend more time finding the software that you’re looking for, but what you’ll end up with is likely to be “just what you need”, as opposed to being something that’ll get the job done, but leaves a lot to be desired as many Windows programs do.
The time spent evaluating all of the packages available can be fun, but it can also get rather tedious at times. It really depends on how you look at it, but to me, there are a lot of tools available that function at a professional level. The fact that you must wade through a number of “wannabe” apps to find the gem you need is just something that comes with the territory right now. As Linux matures, and coding practices and tools standardize, I expect this problem to decrease.
- Stable and fast: These two items are grouped together simply because the two don’t always go hand-in-hand when we’re referring to other operating systems. In this case they are a major plus when it comes to Linux.
Don’t get me wrong, you can crash individual applications, and such, but seldom have I seen the entire system freeze up. And the speed is really amazing! The overhead requirements of Linux are very modest, and once you start increasing CPU speeds and memory, you can really build yourself a system that just flies! In fact there’s several companies looking at tweaking Linux out for usage as a real time operating system (RTOS), so speed and stability are definitely not an issue!
Similarly, Linux disk access, both for serving and reading, is as fast as anything Redmond’s released. Suffice it to say that Linux is ready for competition!
- One word, “Wine”: Wine, which stands for “Wine is not an emulator”, allows Linux users to run many Windows apps directly within the Linux GUI (Not via an emulated computer ala VMWare!). Wine has came a long ways since I first tried it several years ago, and nowadays, it’s easily one of the biggest strengths in the Linux arena, as far as getting existing Windows users to convert.
I won’t go as far as to say that Wine can run any and all Windows apps, as it can’t. But for most of the applications one would run under Linux, it works acceptably well, and in some cases the programs actually run faster than they do under Windows!
I personally use the Codeweavers distribution of Wine myself, and I have to say that it’s one of the best investments I’ve ever made, from a software perspective at least. I certainly wouldn’t run all Windows applications under Linux; If all you want is Windows software, stick with window, but for those specialized applications that just aren’t available in Linux yet, Wine is a godsend!
- Linux finally looks good: This is not so much a strength of Linux per se, but it’s worth noting as until recently Linux UI’s didn’t look that nice. We take such things as anti-aliased fonts and true color displays for granted in today’s Windows world, but until recently Linux users had to make due with regular, “bitmappish” looking fonts. Similarly, video performance was not always as snappy as it is these days.
But as the number of Linux users increase, and as more companies put their dollars behind Linux development, Linux is looking very nice indeed. KDE 3.1 is, in my opinion, going to be the UI that finally pushes Linux into the desktop arena, and to me, it offers everything Windows does, plus some!
Like all things, there is a downside to everything. Linux’s minus’s aren’t too many from my point of view, but I’ll cover some here in order to show that I don’t consider Linux to be absolutely perfect (despite what some of the above might indicate!).
- Steep Learning Curve: Linux, like Unix, is inherently more difficult to learn than say Windows or OSX. Many people might argue that this is a good thing for one reason or another (“It’s more configurable” is a common reply to this point), but either way you go, if you’re coming from a Windows world to a Unix or Linux world, you’re going to have to basically toss out everything you’ve learned and start over.
Miss your C: and D: drive? Tough! You’re C: drive is more commonly known as /dev/hda1 now, and D: might be /dev/hda2 or it could just as easily be /dev/hdb1.
How about the registry? Well, if you liked the registry, then you’ll hate the hundreds of little configuration files laying around your Linux system waiting to be tweaked.
Did you hate the command prompt? Well, then you’ll hate the Linux console! But you’d better get used to it because as far as Linux’s GUI configuration tools have come, you’ll still end up in a console a lot of the time.
These points aren’t to indicate that one shouldn’t switch to Linux by any means. It just means that if you have a “Windows or bust” mentality, then you should probably stick with Windows. The command line interface that is the terminal, or “console window” isn’t still around because old timers love it; It’s there because you can often be far more productive in a console than you can with a GUI interface.
To contrast this statement, I certainly wouldn’t say that a console based image viewer would be easier than a GUI one, but for more file-oriented work and data-based work, a console can often do a lot more with a lot less effort than a GUI based system. If you walk into Linux with this fact in the back of your mind, you’ll probably pick it up a lot faster than someone who thinks that command line interfaces are outdated and purposefully difficult.
- You define your world: No, this isn’t some Zen saying… What I mean by this is that Linux doesn’t dumb everything down the way Microsoft does. It assumes that you, the user, know what’s best for you, and Linux doesn’t try and guess what you want as Windows tends to do.
This puts a little more pressure on you, the user, as you have to be aware of how you want things to function, and you have to learn how to make that happen. The biggest difference between Windows and Linux (and I’m focusing on Windows here as that’s where most people considering a switch are coming from) is that there’s not a GUI for everything.
This is changing rapidly, but for the foreseeable future, you will have to delve into text-based configuration files on occasion. It’s not a big deal, and it’s really a lot easier than it sounds, but be prepared to have some patience as you learn to use the console, and learn what files are used for specific purposes. It gets a lot easier once you realize that when you are using a GUI to configure Linux, it’s just changing these text-based files for you.
- Vendors will not talk Linux with you: Ok… So some will, but generally speaking, unless the company in question specifically states “We support Linux!”, you’re not going to get much help from them. In fact you’re more likely to have them refuse to help you as soon as you tell them you’re using Linux and not Windows!
I’ll give you an example:
I have a DSL connection to the Internet, and I share that connection to the rest of the PC’s in my house via a LAN network I’ve setup. Whenever I’ve had to call my DSL provider for details on their network (DNS address, News server address’s, etc.), I quickly found that if I mentioned anything other than Windows, they’d stop being helpful, and immediately switch to their “I’m sorry, but we don’t support that” mode.
>From a support standpoint, I understand this. It’s hard enough to train everyone how to troubleshoot Windows questions, but once you throw Linux in the mix, terms and programs are no longer the same. You need new concepts and new verbiage to describe the same problem from a Linux perspective, and quite frankly, most companies aren’t taking that extra step right now. They will… Linux is young, and as more people start using it, these companies will be forced to support it, but right now, Linux is not widely supported by most hardware manufacturers.
>From a users point of view, my opinion is “It doesn’t matter what OS I’m using; Just answer my questions!”. Linux uses the same information that Windows does in most cases, it just is inserted and handled differently. For example, in Windows your DNS entries go into a nice little GUI-based entry form under “DNS Server addresses”. Under Linux however, such entries are made in the “resolv.conf” file, which is located in the “/etc/” folder. My point is that they both use a DNS IP address in these areas, you just don’t enter this data the same way you would in Windows.
My advice is this: When speaking with Vendors and/or troubleshooting items with service reps, remember to talk in Windows terms when talking to “Windows people”.
- Programs still don’t share data equally: By this I’m referring to the fact that Linux apps are still maturing, and as such, they don’t always play nicely together. A great example of this is copying and pasting text between apps. Sometimes you can (more often than not these days!), but every now and then you’ll run across an app that just won’t “talk” to the other apps on your system.
In fact I’ve ran into this recently with Adobes’ Linux version of their Acrobat Reader program. Like its Windows counterparts, you can select and copy text out of the PDF’s with the viewer, but if you then try to paste that verbiage into say a KDE-based editor, the copied verbiage will not appear.
This problem is getting better as the UI developers begin to work towards a set of common standards, but the fact that you still will run across applications that don’t want to talk to one another is evidence of the fact that Linux is still a maturing OS. It’s not yet quite as refined as the Windows line of products in some ways, and it can be frustrating when you come across an example of this fact. As I pointed out earlier, this problem is decreasing rapidly, but it’s still likely to be a problem, albeit a small one, for the next couple of years.
Goals: My goal when I set out was to end up with the best Linux distribution I could find, and then customize it to compliment my personal work style and habits. Once done, I should end up with a highly usable system that looks cools, and is rock-solid from a stability point of view.
As such I began reviewing Linux distributions about 3-4 months ago to come up with this “Windows killer” system. For me this meant that I wanted the most modern versions of programs I could get, while maintaining compatibility with my existing Linux apps, and of course I required that KDE 3.1 (or the newer 3.1.1) be present as my GUI interface.
I also have a short list of “must have” items that I wanted to make sure were either included with the distribution or were easily added on at my discretion. Among the list of items that were on this “must have list” are:
- Ximian’s Evolution email client
- Mozilla or Phoenix (both are web browsers)
- Wine capable
- Xfree system capable of driving my dual monitor displays
- Anti-aliased fonts
It’s worth noting at this point that none of the Linux distributions I tried were successful at setting up my dual-headed system. It seems that every installer naturally assumes you only have one display (even though Xfree’s been dual-head capable for quite some time now!), and thus only configures one card (the card it configures is apparently based off which card your bios is set to boot from). In most cases, this resulted in me booting into a one-monitor display the first time, and then manually configuring my XF86Config-4 file in order to get both displays working. I quickly found that it pays to keep a working copy of this file around which can then be copied over and modified as needed, rather than starting from scratch with each distribution.
This isn’t to scare you away from having a dual headed system, but rather to let you know that if you do run such a system, you’d better be prepared to edit some text! Hopefully future Linux distro’s will have the ability to correctly sense and setup a dual headed display in much the same manner Windows currently handles it. For now though, it’s more of a manual process to set this up.
Ok, with that out of the way, let’s start with the first distribution that was considered for use as my desktop OS, Yoper.
Yoper is a relatively new Linux distribution coming out of New Zealand. It’s one of a number of new distributions that seem to build off a Slackware base, and then optimize the system for both newer processors (Yoper’s optimized for i686 CPU’s), and for KDE 3.1 as it’s only interface. Yoper has only recently hit version 1.0 of its software, and as such, all of my work and my impression of Yoper are based off several release candidates (RC’s) that they released.
Yoper aims to have a small footprint (The amount of space necessary for the installation of the OS and all of it’s necessary files) of highly stable, integrated apps, and to be fast. And for the most part Yoper succeeds in all areas!
Yoper looks great, with smooth anti-aliased fonts, it’s fast, and thanks to its Slackware heritage, it’s fairly intuitive to navigate and find the items you’re looking for. Their target market is business’s that want to migrate off competitors’ products (i.e., Windows), and they apparently have rather a successful business converting companies over to Yoper-based systems in their homeland of New Zealand.
The only real problems I experienced with Yoper were with its implementation of the Xfree86 display drivers. The aforementioned Xfree86-4 display file had to be changed and tweaked for each release, and it never was as stable or easy to get running as any of the other Linux distributions I’ve tried. With the exception of RC4 however, once I had managed to get the displays working, Yoper performed admirably. RC4, the last release before their official release, was unstable no matter what I did though. It looked and performed great, but on occasion would just crash hard, dropping the user out of the Xfree environment, and leaving them with a console prompt.
This was where my real problems with Yoper began. Without getting into all the details (this is a comparison, not a complaint summary), it quickly became apparent that Yoper was only in the game for Yopers benefit. They did manage to build an impressive distribution (RC4 being the exception), but their support left a lot to be desired. They’ve deleted their knowledge base and message forums no less than 3 times in the last couple of months, and when I did run into a problem, they refused to respond or answer my questions (and with the message forums deleted, I didn’t have the option of turning to that as a resource). Similar complaints began to pop up on both their forums, and on other sites, to which the company responded with insults and diatribe, referring to anyone who voiced an opinion as a “Slashdotter” and refusing to acknowledge anyone’s issues.
Perhaps this situation has changed, but just recently they posted a long message on their site claiming that anyone who complained about the quality and/or treatment we received was simply a Slashdotter (among other things), and that they didn’t want to service us “geeks”. Instead they claimed that they were very successful in the New Zealand market, and that they didn’t need or want users like us.
Easy enough… I deleted the Yoper releases, pocketed the money I’d set aside to purchase Yoper with, and moved on. At this point, I hope they’re out of business soon. They’re a very misleading company, and rather than providing a service, or acknowledging any problems, they insult their users, appropriate any hints or workarounds their users have offered, and then delete any references to problems rather than deal with the issues. Enough said.
Summary: Stay away from Yoper. There are many other companies with equal or better releases who want to work with their users to develop a better product rather than just take their money and run.
Additionally, Yoper is extremely high priced when compared to other Linux distributions. They’ll charge you just under $100 to get a Yoper install CD, and they’ve already said that additional money will be needed if and when you upgrade to a newer version. Evidently that $100.00 is only good for the initial purchase plus a year of support. I myself don’t see anyone spending $100.00 a year just to ensure that they can get software and support from an arrogant company who has already stated that they don’t need my business.
Redhat’s latest offering, which was just release, is very impressive! My review’s based off the release candidate, Phoebe, which is supposedly very similar to the final 9.0 release version.
In addition to getting all of the experience and support that comes with the worlds most successful Linux distributor, you also end up with a very fast, and well-built Linux system. Phoebe looks great, and KDE 3.1 simply smokes on it. It’s a very fast system! Some of this speed might be due to Redhats new threading processes (due to be included with the forthcoming 2.6 kernel thanks to Linus Torvolds appreciation for the technology!) which impacts how programs talk to the kernel, but either way, Redhat’s performance is top notch, and certainly among the best I’ve seen. Particularly when you consider that Redhat’s i386 compatible and not highly optimized for the Athlon CPU that is running my system.
Phoebe also offers one of the better-looking desktops thanks to their beautifully anti-aliased fonts, and the aforementioned KDE 3.1 UI. I played around with Gnome a bit, but it was too slow for my tastes. In addition, I couldn’t tweak out Gnome as easily as I can KDE. I expect some of this will be fixed with the final release, but for my needs, it doesn’t matter; I’m a KDE fan myself.
If the software you want isn’t included with Phoebe, there’s a ton of sites on the net that offer Redhat 8-specific packages. There’s also a lot of Redhat specific support available online in order to help you through any questions you might have.
I really only had a few negative impressions of Phoebe, one of those being it’s implementation of KDE. Redhat is notorious in some circles for “crippling” KDE in order to make it work better with Redhats favorite UI, Gnome. Although some people will tell you Redhat’s made it very hard to work with 3rd party KDE apps due to how they’ve changed KDE’s structures, for the most part, you won’t notice these changes during your day-to-day work.
They’ve done things like moving the KDE menus around, and installing KDE in a non-standard way, rather than using KDE’s defaults, and they’re totally in the right by doing so due to the way that KDE’s distributed (You can really do about anything you want with it). It does however make it harder to install certain applications since they’ll try to add their shortcuts and such to the default KDE locations. You’ll then have to manually move such items to the correct areas on your hard drive if you want them to work with your Redhat setup.
The other problem with Redhat isn’t really a Redhat specific problem, but rather one which is plaguing many of the “cutting edge” Linux distro’s, and that is that they’re including the latest glibc libraries (v2.3.2), and many existing apps have not been updated yet to work with this version. On top of that, Phoebe also sports an entirely new method of handling program threads, and while this new method does offer some dramatic speed increases for certain operations, like the updated glibc libraries, it also breaks compatibility with a number of existing applications.
Hence important utilities like Codeweavers Wine don’t run under Phoebe yet. Updates are in the works for both the aforementioned Codeweavers product, as well as for may other apps which aren’t currently compatible with this new release, but I want a system that works today. If I wait, it could be anywhere from a couple of weeks to several months before most applications are patched, which isn’t too encouraging.
Redhat includes a ton of software with their distro’s, and Phoebe is no exception here. It’s packed full of software to help you with everything from surfing to coding, and I like the fact that I don’t have to go hunting for what I need immediately upon getting my OS installed. On the other hand, this is specifically why Redhat’s known for adding bloat to their distributions! While I appreciate so many tools being available, I wish they weren’t all installed by default. I like a lean system, and knowing that space and CPU cycles aren’t being wasted on unnecessary services and programs. While Phoebe is extremely fast, even with all of these additional software packages and services installed, I would prefer knowing specifically what’s installed and why, without being forced to manually choose every single component as this is quite time consuming.
Summary: Redhat is a worthy purchase for any Linux “newbie”, and arguably a good candidate for most people who use Linux. The minuses for me are the bloat, the modified KDE installation, and the fact that I cannot run Codeweavers under it yet.
I can’t stress enough how easy this distribution was to setup and get running, but again, I’m not a newbie any longer (at least in my opinion. Others might argue), and Redhat’s handholding and “all-in-one” installation methods remind me just a bit of Microsoft’s ease-of-use efforts. It’s nice, and it’s powerful, but for my purposes, I want something a little more compatible with a 3rd party apps, and I’d also like a system I can currently run Codeweavers under. KDE 3.1 smokes under Phoebe, but this is also the case with many Linux distributions that are currently shipping it.
Additionally, the new threading model that Redhat sports is a nice perk, but it soon won’t be Redhat specific, so this is only a temporary plus. The upcoming 2.6 kernel will also contain the updated threading methods, so soon all distributions will benefit from this, so while this is nice, it’s not a “must have” reason to go with Redhat for my Linux system.
The software and support that’s available for Redhat is great, and I wouldn’t hesitate to recommend this for anyone just starting out on Linux, or anyone who just wants a system to work, and who’s not that interested in tailoring it too much.
Ok, I realize that as of this writing, Mandrake just released the final version of 9.1, but I haven’t been able to snag a copy off of the already over-congested mirrors. Hence my review’s based off of version 9.1 RC2, which I understand is virtually the same as the final release, with a few bug fixes.
Historically, Mandrake has always been my “backup Linux”, meaning that I keep a partition on my drive loaded with Mandrake in case something goes wrong on one of the other partitions (which include a couple of Windows installs, in addition to some other OS’s). Mandrake’s always been reliable, fast, and very well rounded, as far as the packages included with it go. Mandrake also drives my server/firewall setup, and has done so reliably for the last couple of years!
So it was a little disappointing that after I installed Mandrake 9.1 RC2, I realized that it ran noticeably slower than Redhat’s latest offering. At this point, I had done a basic install of Mandrake, and so I had a lot of extra programs and software installed that I didn’t necessarily need, similar to my Redhat experiences. After playing around with some of Mandrakes settings, I decided that perhaps these additional “pre-selected” applications were slowing my system down, so I decided to try a minimal install.
What I did was tell Mandrake that I wanted to custom pick all of my packages, and I then un-selected every choice in the install dialogue. I then chose just what I knew I wanted, and let Mandrake choose additional packages based on the dependencies in the packages that I chose.
This resulted in a much leaner installation, and one that runs notably faster than the older “all-in-one” install. My assumptions are that the additional programs and services that were being installed is what dragged my system’s performance down so much.
So how does Mandrake run now that I have it installed? Pretty damn nice! It’s noticeably quicker than Mandrake 9, and KDE 3.1 runs as fast as Redhats KDE 3.1 does. In fact, for the most part Mandrake runs and acts virtually the same as Redhat. There really isn’t much of a difference between the two from an operational point-of-view.
But Mandrake 9.1 also includes the new glibc libraries. Ideally this should mean that my Wine apps won’t run under it as with Phoebe, but I found that this wasn’t entirely true! Certain Wine apps will run under Mandrake, but certain ones don’t. It’s very hit or miss, and quite frankly, I’ve no idea why it wouldn’t be treated the same as my Redhat installation if indeed the glibc libraries are the cause of this problem (and I’m quite certain, at least in the case of Redhat, that glibc is the problem!).
I haven’t had a need to try Mandrakes more esoteric features such as ntfs partition resizing. I appreciate that it’s there, but I think I’ll still probably feel safer if I’m rebooting into Windows and Partition Magic if and when I need to play with my hard drives partitions. Not that I like to reboot, but since Linux in general doesn’t officially support writing to an NTFS partition, I’m a little leery about possibly trashing my drives by resizing them with it.
Another area that Mandrake reminds me of Redhat is how they’ve also messed with their KDE installation. Similar to Redhat, they’ve installed it and it’s menu’s in non-standard locations. Hence 3rd party applications may or may not install correctly. Since I want to build my workplace around a KDE 3.1 center, it’s very important to me that I can expect any KDE add-ons to install and be usable with a minimum of help from me. Mandrake, like Redhat, will require me to manually move files around it looks like. Not cool.
One more area that Mandrake rivals Redhat is in support and software being made available for it. As with Mandrake, there’s a ton of sites and programs that deal specifically with Mandrake. One that comes to mind is the PLF, which provides software essential for the desktop experience. My concern is more about non-specific software that I might compile from source.
Here’s a brief example of why: Mosfet is a fairly well known KDE developer, and has provided some fun bits of software for the community in the past. He’s also one of the more vocal opponents of Linux distributors who hack KDE up, and he’s written a fairly well rounded piece on his site explaining what they’ve done, and how this affects developers. While I’m not saying his word is the final word on the matter, I have tried to get some 3rd party KDE apps to work with both Mandrake and Redhat, and often Mosfet’s right in that I end up manually moving files and links around in order to get the application to work correctly.
Just because I know how to work around the problems doesn’t mean I necessarily want to though. I’d rather spend my time developing, or enhancing my system than I would tweaking new installs to work with my broken KDE system. In the past, this wasn’t so much a problem, but as I move forward and try to come up with “my desktop”, I don’t want to deal with this problem that much. This is a strike against Mandrake!
But my minimal install of Mandrake was enough for me to replace Phoebe with it! I was really impressed with Redhat’s speed, which again, I largely attribute to their new threading technologies, but my familiarity and fondness for Mandrake did, in the long run, win me over (but I’m still considering playing around some more with Redhat once I can get my hands on the final version!). And while I can appreciate the solidness of Mandrake 9.1 as a “backup system”, I really wanted something that’s more standards compliant for my main Linux desktop.
For now Mandrake’s back where it always has been on my system: A good back up system with a lot of tools in case I have problems elsewhere. As my primary desktop system, it falls in with Redhat’s Phoebe. It runs nice, it looks great, and as long as I don’t want to go outside the box they’ve built for me, it works great.
Mandrake as a company do leave a bit to be desired. It seems like they’re constantly releasing press releases indicating that if people don’t support them, they’ll be forced to go out of business. I hope this changes with the release of 9.1, but it is a concern right now. No one can say for certain that they’ll be here in a year to support their product, but I for one hope they are. Whereas Redhat’s just testing out the waters of cutting edge/desktop distributions, Mandrakes been doing this for some time, and it would be nice if they could keep doing this for awhile. Only time will tell though if 9.1 will be the release to push them away from the brink of bankruptcy. Let’s hope it is.
Summary: Mandrakes latest offering is a nice advancement over their previous one. As with Redhats Phoebe release, KDE 3.1 is what really makes the system for me, but like Redhat, Mandrakes implementation of KDE leaves me wanting as far as trying out new apps and compiling 3rd party add-ons. Mandrake’s reliable enough, and friendly enough to be a great backup or rescue system, but for my new desktop system, I’m going to continue my quest. I want a Linux desktop that both works out of the box, and one that plays nice with other peoples software. Mandrake and Redhat both excel at the first piece (working great out of the box), but they both have issues that could impact me down the road as far as compiling and using 3rd party applications.
Ark Linux is a project that’s been started by an ex-Redhat bigwig who goes by the name of Bernhard “Bero” Rosenkraenzer. While I admittedly don’t know a lot about Mr. Rosenkraenzer, I can appreciate his goal of making Linux easier for the masses, and so I decided to see what new ideas he was bringing to Linux with his Ark distribution. After downloading and burning the Ark Linux image, I booted up to find myself presented with a rather intimidating menu.
This menu gave me three options: Option 1 would allow Ark to basically “take over” my hard drive, destroying all data and formatting it for use with Ark Linux.
Option 2 indicated that Ark would locate and use all non-used space on my hard drive.
And Option 3 indicated that Ark would be installed parallel to an existing Windows partition.
Now let me say up front that this menu scared me! In the PC I’m using for my desktop, I have 3 hard drives with about 200GB between them, and one CD burner. Data files take up much of my hard drive space, and the remainder is taken up by a couple of Windows partitions (Win98 & XP), a couple of Linux partitions, and a BeOS partition. To be blunt, I didn’t want Ark messing with the wrong partitions as I literally had a lot to lose if it did!
So the lack of choice with these 3 menu items really made me nervous. I certainly don’t want Linux deleting my drives to make way for itself, and I didn’t have any unused/un-partitioned space for the second option. For that matter, the fact that I couldn’t choose which drive to use for the first two options was really annoying. I probably wouldn’t have been so nervous if I’d have at least known which drive Ark was going to try and install itself to. It seemed like the 3rd option (to install parallel to existing Windows partitions) was what I wanted, but whenever I’d select this option, Ark’s install process would immediately lock up.
I chalked this rather un-friendly installer up to the fact that Ark’s only in alpha stage at this point. After investigating the problem online and doing some experimenting, I found that if I deleted the partition that I wanted Linux to be installed on and chose option 2, Ark would find and use the un-partitioned space no matter which drive it was on. So finally I was off and installing Ark.
I quickly found out that Ark Linux’s installer doesn’t ask you anything after that initial 3 choice menu! I was expecting that as with most desktop-friendly distributions, the install process would ask and setup both my root password, and a user, but Ark never did. I assumed that this meant that as with some of the more geek oriented distributions, I’d boot into Linux as root without a password, and then would have to manually set both that up, in addition to my regular user, so I was a bit surprised when I booted into X-Windows as a user called of all things “arklinux”.
I also soon found out in the Ark Linux world, there really is no root password! Ark’s take is a unique one, but also a scary one for anyone who’s used Linux in the past. They presume that users don’t want to have to worry about different users, or having to keep track of passwords, and so they do away with both!
Specifically, this means that Ark sets up each machine as if it were a one-user machine, and they remove all need for su passwords and such. If you want to do a task as root, you can just open up a terminal, type “su”, and voila, you’re suddenly root! This is accomplished by a questionable user-rights management system in which you can define whether a user has su privileges or not, and by default those who do don’t not have to authorize themselves.
This is the complete opposite of any other Linux distribution! While I can appreciate what they’re trying to do (remove the complexity of a *nix system vs. a Windows system), I disagree with their methods. They have a blurb up on their website which indicates that to their knowledge, this doesn’t constitute a breach of security, largely because Ark’s not meant to be a server OS, and thus most security issues about not having a root password are irrelevant.
If you don’t like the convenience of having users setup this way (or if you have any common sense about PC security, and/or any experience with other Linux distro’s) you do have the option of setting up Ark with normal security and passwords. This does in essence break a lot of what’s setting Ark apart from other Linux distributions, but it is an option if you really want to use Ark, but you also want to have a somewhat secure method of controlling who your users are, and what they’re allowed to do. Why you’d choose to setup Ark for this purpose, instead of simply going with a different distribution is beyond me though! If you want security and functionality, simply choose a different distribution. Why waste all that time trying to use Ark in a different manner from which it’s designed to be used?
To be fair, Ark also includes a GUI configuration tool if you want to setup new users with the same privileges as that provided to the default “arklinux” user. So if one non-secured user’s to limiting to you, you can have entire groups of them! For my purposes however, even though I could see the convenience of not having to remember passwords, or the fact that there is such a thing as a root/su user in the Unix/Linux world, a password secured system is more preferable.
Ark also sports some very cool looking screens for configuring your system. They’re not so much custom tools as they are custom GUI environments for already existing KDE configuration components, but they do set Ark apart from most other distributions, and it shows that they are moving towards a simpler, more Windows like system than most Linux distributions are.
The other features of Ark are more or less standard for a desktop oriented distribution. You get a fairly lean install without all the bloat of say a Redhat system, and you get a rather basic KDE desktop on which to build your “dream system”.
Ark also lost points for their add-on CD that allows you to install a lot of popular software that isn’t included with the base distribution itself (such niceties as a media player and so on). Rather than use a package manager, or an apt-get method of installing these packages, as you would with most other Linux distributions, you have to pick what software you want to install from a menu on the aforementioned add-on CD. It works. That’s about all I can say about it though. Anyone who’s ever installed software on a Linux system before will probably hate blindly installing stuff as Ark Linux does. Perhaps newbies and the desktop crowd that Ark’s aiming at want such simplicity, but to me it was actually a step or two beyond the handholding that Microsoft is so infamous for. If Ark really wants to make Linux this simple for the end user, they should at least offer an option for the more experienced Linux users that doesn’t dumb it down so much.
Another item Ark has to improve on is their documentation. There simply isn’t any, and their website’s a joke. Both will likely be upgraded as Ark matures beyond its current “alpha” stage, but I’d focus on both right now before worrying about dumbing some more of Linux features down. As it is, Ark just makes me nervous. It doesn’t act like other Linux distributions (which could be a good or bad thing, depending upon your point of view), and it doesn’t tell you what it’s going to do before it does it.
For someone with a brand new one-drive system, this might be ok, but for someone with multiple partitions, multiple operating systems, and a ton of data to potentially lose, Ark is just too simplified for me to feel confident using it (I didn’t even mention how nice it was for Ark to overwrite my boot manager without asking, prompting me to have to fix this before I could see my other OS’s again!).
On the plus side, Ark looked nice once I got it setup, and it was fairly fast (Not Redhat8 fast, but very usable). Also, it comes optimized for i586 & i686 PC’s (How it’s optimized for both is unexplained though), which is always a nice thing to know. However it doesn’t appear to offer me any benefits over any other distributions, unless you consider the dumbing down of security and package installs features âI do not.
Summary: Ark has some potential, but at this stage it’s a big waste of time to me. Its security model is questionable at best, and I don’t think it’s too wise for them to post on their website that it’s not really a concern because Ark isn’t intended for use as a server. That’s just not an excuse for handling security in this manner, and I feel sorry for any newbie who chooses Ark as their first Linux distribution as once they use a real Linux distro., they’re going to be very confused by actual user and root management.
Similarly, Ark needs to accept the fact that their OS probably won’t be the first thing on someone’s hard drive, and they need to fix their install scripts to allow for this fact. Perhaps the 3rd install option would have handled this correctly, but since it locks up when chosen, I’ll never know. It shouldn’t even be presented as an option if it’s not going to work as having the installer lock up first thing doesn’t really inspire confidence in the OS you’re installing.
To me Ark Linux is a Linux distribution made by someone who really doesn’t understand the basics of a *nix system, and thus is trying to circumvent common methods and procedures in order to make it more Windows or BeOS like (from the install & package management methods at least). My recommendation is to not waste your time on it. Perhaps future versions will reinstate some of the missing security, but for now I look at Ark as being a poorly implemented concept.
Vector Linux is based off Slackware, and is 100% compatible with Slackware 8.1 or earlier I’m told. This is a good thing as Slackware’s notoriously stable and well thought out, however Slackware’s also notorious for being difficult to setup. Vector Linux gets around all of the problems of setting up a Slackware system, while providing some very well thought out, and appreciated extras. Vector Linux’s website advertises a 100% Slackware compatible system within 15 minutes, and it delivers on that by providing the user with a simple, yet informative install process.
Vector’s forte is that it offers a rock-solid and fast Linux environment, while not providing you with any bloat. Their theory is that the user should design and build their own system, and I agree 110% with that thought process. Vector installs all of the basics you’ll need, and a few that you don’t, and then allows the user to decide what to add on, and when.
And for me at least, Vectors default offerings are more or less what I’m looking for in a desktop environment! They’ve included my favorite email program, Evolution, as well as my favorite browser, Phoenix (which is a stripped down version of Mozilla for those of you not aware). They’ve also included such necessities as Gaim (multi-protocol instant messenger), and Open Office, not to mention K-Office, which is also installed.
Sure, there are a few things installed that I don’t need, but in general, Vector Linux out of the box provides me with most of the programs that I want. It doesn’t include much bloat, and in fact the installed system uses less than 500 Megs worth of drive space. Very nice indeed!
Let’s see what else we get with Vector…
As mentioned, Vector Linux is based off Slackware, and in fact is supposedly 100% compatible with older versions of Slackware (but not the newer 9.0 version which was just released). This is keeping with the trend of a lot of the newer Linux distro’s, which are built around a Slackware base (Yoper and College Linux are two distributions that also come to mind), so there must be something to the myth that Slackware’s inherently stable and standards compliant.
This is good because now we can also use Slackware packages and documentation to help maintain the system, rather than going with a totally new distribution that has little to no existing documentation or software available for it. This is a big plus for anyone putting together a desktop system, and it was one of the main plus’s for both of the Mandrake and Redhat releases that were reviewed above.
Vector Linus also includes three WM’s for you to choose from, and none of the choices is Gnome (although many of the back-end Gnome libraries are included so that Gnome-based apps like Evolution will run without complaints). To me this is a good move. I do like some of Gnomes features, but in general, KDE is just so much more advanced than Gnome at this time. It’s good to know that I’m not the only one who likes Gnome-based apps, but not Gnome itself!
The included WM’s are XFCE, IceWM, and KDE 3.1, and all three have been outfitted with gorgeous anti-aliased fonts, in addition to all three all containing well-fleshed out menus, containing all the apps included with the distribution. While KDE 3.1 is still my preference, I’ve always had a soft spot for XFCE, and quite often find myself using XFCE for my root desktop and KDE 3.1 for my users environment. Let me just say that as nice as KDE 3.1 is, all three of the included window managers are setup more professionally and logically than any of the WM’s I dealt with in any of the other distributions!
Additionally, all three WM’s are setup as their creators had intended, so 3rd party applications and add-ons act just as they should. This is so nice to deal with after having dealt with Redhat and Mandrakes customized menus and software installations. As I’ve stated, I understand why Mandrake and Redhat are doing what they are, but it sure is refreshing to see how the software was intended to be installed, and then to realize that they’re every bit as functional and logical (if not more so) than the Mandrake and Redhat hybridized menus.
In case you can’t tell, Vector impressed me very much! I was a bit leery about trying it as historically Vector Linux has been known for its backwards compatibility and it’s ability to “play nice” on older hardware. I had envisioned a distribution that was full of older, out-dated software, and that wouldn’t take advantage of my newer hardware. I’m glad to say that I couldn’t have been more wrong!
Vector is very cutting edge, and yet you get the feeling that the system was put together by someone who truly understands their users. Whereas most other distributions don’t appear understand their target audience, and thus install a ton of software in hopes that there will be something for everyone, Vector appears to “get it”. They put the best software in the install, made everything play nice together, and have come up with a desktop distro. for the masses IMHO.
But I can’t just end the review gushing now, can I? As a good reviewer I have to come up with some negatives, and Vector does have a couple of minor ones. Nothing that I would consider real problems, but certainly there are a few areas that could be improved.
The first thing I’d change is to update their website to reflect the power and “modern-ness” of their new distributions. The “Hints and Tips” section of their website, for instance, refers mainly to versions 1.0 â 2.0, and are admittedly outdated. Similarly, the “How To” section of their website refers specifically to Version 0.4, and is dated early 2000! These types of things are specifically what gave me my initial impression that Vector was not going to be a cutting edge desktop distro, and I’m sure that such items are misleading to other people researching what Vector has to offer.
Another area I’d like to see improved is an upgrade to Xfree 4.3. Xfree 4.2.1 is included, as is 3.3.6 for older hardware compatibility, and while 4.2 meets my needs, I can see some people wanting the benefits of a 4.3 display system. Iâm also aware that I can upgrade this component myself, but would like to see it come as part of the default distro.
I’d also like to see the VASM tool upgraded to be a little bit easier to use. VASM is Vector Linux’s system management tool, and is used to do everything from changing hardware and display settings, to User and package management. It’s very capable, but it’s not too intuitive to those of us not familiar with either Vector Linux or it’s parent, Slackware.
For instance, I am coming to terms with Slackware packages vs. RPM’s, URPMI, and apt-get, but VASM’s two package management options still confuse me. Why two choices instead of one more comprehensive choice?
One last item I’d love to see is the option to install an i686-optimized base instead of the i386 one. Not that it’d be much of a change (Vector absolutely smokes speed-wise, and is easily comparable to Yoper which is i686 optimized!), but it would provide that geeky feeling of satisfaction you get when you know your hardware’s being utilized to it’s maximum potential. I realize that this would be a niche market, but it would be a nice option to be able to choose from during the installation process.
But such items are minor compared to the strengths of Vector. It truly is one of the most impressive distributions I’ve had the pleasure of using.
Summary: Vector is an amazing distribution. It integrates some of the best software available into its base install, and it runs flawlessly. Whereas some of the other distro’s I’ve used tend to come off as either thrown together, or overly bloated, Vector comes through with shining colors, being neither bloated nor thrown together. It’s based off one of the oldest, and arguably most stable Linux distributions, Slackware, while providing the speed and software that today’s users demand from their systems.
There are some things that could be improved, but none of these really has any impact on the systems functionality, or it’s integration. I’d also like to point out that with the aforementioned exception of including Xfree 4.2.1, Vector includes some of the most up-to-date software available, and manages to integrate it all into one well thought out package. Vector Linux is truly nice!
At first glance, a source-based Linux system seems like it would be ideal for my needs. I could have everything optimized for my hardware, and I would only have the software that I specifically wanted on my system. Those are both very enticing reasons to go with Gentoo or one of the other source based systems as I’m very anal about both issues; I want an optimized system, and I don’t want a lot of programs that I’ll never use taking up space on my hard drive!
The biggest drawback to going with a source-based system though is the time associated with them. The fact that it’ll take me 24 hours or more to compile and setup a basic KDE 3.1 system with all of the necessary components (Xfree, Sound, etc.) is something that definitely makes me leery to going this route for my primary desktop system.
I’m someone who likes to try a lot of different programs in order to come up with something that best meets my needs, and the fact that I’d be faced with hours of compiling, just to try a program, is daunting to say the least. The reward would be a system totally defined by me, but the cost is the time necessary to set this up, and of course while my system’s compiling, I can’t use it!
And although Gentoo is by far the most popular source based system, it’s also fairly intimidating in that I have to do virtually everything manually. This is changing somewhat as Gentoo readies their 1.4 release, but generally speaking with Gentoo you have to manually setup everything from the boot process to the programs themselves. I wish that Gentoo had an installer similar to Sorcerer Linux, another source-based distribution.
I used Sorcerer a year or so ago, right before the notorious fallout between its users and its developer, Kyle Sallee. I won’t get into what happened (It’s documented elsewhere if you want to Google for it), but suffice to say that Sorcerer is still with us, although they did lose a lot of users and momentum during the fallout from back then.
Sorcerer, unlike Gentoo, uses a scripted, text-based menu for installing Sorcerer. It is amazing how powerful this simple menu is when you compare it to doing everything manually as with Gentoo. It’s one of Sorcerer’s main strengths, and it’s the main reason why I just can’t bring myself to use Gentoo.
I understand that Gentoo’s intimidating, but does it have to be so manual? Well no… Sorcerer’s proved to me it doesn’t have to be so manual. So why don’t I install Sorcerer than and use it for my dream system? Well, besides the time associated with compiling everything, which is the same as Gentoo, my fear is that I’ll again build up a nice robust source based distribution, only to have Kyle and his crew suffer another fallout and leave me stranded with a source based system that’s not easily updated.
I’ve waited for over a year, and while Sorcerer’s still around, they haven’t ever attained that level of confidence I feel I need for my primary system. Their website is… Well, amateurish at best, and their documentation leaves a lot to be desired. Additionally their use of such geek terms as “cast”, “dispel”, and “the Grimoire” don’t necessarily indicate a distribution that’s going to be around for too long. But they might still and I’m still keeping an eye on them as a possible side project for the future.
There are also other source-based distributions, including Lunar Linux (similar to Sorcerer), Source Mage (a fork of Sorcerer that was started during the aforementioned fallout with Kyle), and Rock, which I’ve no experience with.
The biggest problems the source-based distributions face, in addition to the time associated with compiling everything, and the need to manually configure your system, is the fact that you’re more or less reliant on its creators in order to keep the list of available software up-to-date. With the popularity of Gentoo, I don’t see that as being as big of an issue for them as it would be for Sorcerer or one of the other smaller Linux systems, but again Gentoo isn’t as friendly as Sorcerer showed me that source-based Linux distributions can be.
When Sorcerer had its troubles, one of the first things that happened was that their “Grimoire” (Which is basically a collection of pointers to the sources which Sorcerer recognizes, and can automatically download and compile for you) fell out of sync. This meant that we users at the time either had to learn how to update our Grimoirs manually, or we had to move to a different distribution if we wanted new software, and this is generally the reason for the fork to Source Mage.
Yes there were workarounds, but for a primary desktop system, we shouldn’t have to deal with workarounds.
I guess that my ideal source-based Linux system would be to tie in the support and user base of Gentoo with the ease of use that Sorcerer brings to the table. Sorcerer itself has the potential to be a Gentoo, but the lack of professionalism coupled with the stigma that Sorcerer has had since their “problems” means that this won’t likely happen anytime soon. For now, I’ll stick with pre-made bases, and then compile my way to the perfect system as needed.
Summary: Source based systems are great if you have an extra box lying around to use as your desktop until your compiled system is ready to go. If you’re using a source based system as your primary desktop, I’d recommend having a backup system to use just in case you do run into problems, or in case you need to do actual work while the compilation’s taking place.
Also be prepared to learn a lot about Linux if you go the source-based route! This is one of the main reasons that source-based advocates use when referring someone to such systems. And while I agree that everyone should know more about how their OS works, I can’t agree with forcing people to learn every myriad detail of a whole new architecture just to have a responsive, customized Linux system as their main OS.
I’ve used SUSE in the past and was always impressed with their configuration tools, but I did not include SUSE for the purposes of this review. Why? Primarily due to the fact that I wanted to evaluate different Linux distributions before spending my hard-earned cash, and Suse doesn’t offer a free version of their software to try.
Well… Not entirely, that is. If you dig around enough, you’ll find out that Suse does allow people to download and install directly from their FTP site, but I read several reports from people who have either done this, or tried to, and all of these pointed towards both slow download speeds and missing functionality as problems with installing via this method.
Again, I’m not saying that either’s true as I didn’t actually try and install via either method, but the issues I read about were indicative of how Suse presents itself: They’re here to sell you what is arguably one of the better Linux distributions available. They don’t advertise the fact that they offer downloadable versions of their software, even thought they apparently do, and they evidently don’t go out of the way to make such downloads as easy to use, or as easy to get as they do their retail versions.
Which is fine! That’s one of the great things about Linux is that you can more or less do with it what you want. As I said, I’ve both purchased and used Suse in the past, and while my memories revolve primarily around their Sax configuration tools, which even a couple of years ago were of very high quality, they were always good, well thought out distributions. For this project though, I want to definitely try before I buy, and after reading about others Suse download experiences, I decided to skip their latest release.
This isn’t to say that I’ve written Suse off, but merely to point out that their current marketing strategies didn’t make them good candidates for this evaluation.
So where does this leave me as far as my original goal goes? What system will meet most of my goals while providing a nice base on which to build for the future?
After a few months of experimenting and evaluating, in addition to irritating the hell out of my girlfriend (“I just don’t understand why you’re trying all of these different versions if they’re all Linux!”), I’d have to say that Vector Linux takes the cake!
Yoper probably would have won if they would have retained a Slackware-compliant backend, and if they’d have hired some people who understood their user base, but they didn’t do either, and as a result they alienated a lot of people with their tactics. Additionally, Yopers high price and subscription model both make a good argument for looking elsewhere.
Vector Linux is rock-solid, and mega-fast. Especially when you consider that it, like Redhat is an i386 optimized distribution! Vector gives me most of the programs that I would normally install anyway, and it gives them to me without complaining at all about dependencies. Add to that the fact that Vector looks good with its anti-aliased fonts and system-wide integration, and you’ve got a winner of a distribution!
I used to wonder why my wine-enabled apps ran so much faster under Yoper than Redhat, and I now have come to the conclusion that it’s something to do with its Slackware backend as Vector is easily as fast as Yoper with both Wine and regular apps. It just smokes!
Additionally you get great support from the Vector forums, and a huge archive of software with which to play thanks to its Slackware heritage. But don’t take my word for it: Get out there and download a copy and see for yourself.
About the Author:
I live in Michigan and am currently employed as a Web Developer. I’ve been involved in computing for the last 20 years, give or take, with my first experience having been an upgraded Atari 400 my father purchased for us for Christmas one year. My first PC was an Amiga 500, and I currently am planning my next box, which will be a dual-CPU AMD system. In addition to the countless hours I waste in front of a PC, I’m also a musician (primarily guitar as of late), I do graphic artwork (primarily computer graphics, but I’ve done more traditional artwork as well), and in addition to plants and horitculture, video editing is a growing hobby of mine.