Even if you’re happy with the Linux desktop you currently use, you might want to check out some alternatives to see what you could be missing. Jack Wallen highlights 10 of the best desktops and explains what makes them stand out.

---

If you know Linux, you know there are tons of options on every level. To some, this might seem overwhelming at first. To others, it’s all about possibility. The desktop is certainly not without options. In fact, the Linux desktop might very well be the area where there are the most options. But for a lot of users, desktop selection doesn’t usually go beyond KDE or GNOME. With this article, I hope to help the average Linux user get beyond the standard fare.

Note: This information is also available as a PDF download.

#1: Enlightenment

I have to confess I put this at the top of the list because it is my favorite Linux desktop. This desktop is all about being full of eye candy, while at the same time being lightweight and fast. Enlightenment was created by Carston Haitzler (Raster) in 1996. He created Enlightenment to be a lightweight window manager that didn’t lack style. He succeeded (and then some).

Currently, Enlightenment is enjoying two releases: E16 and DR17. E16 is the current stable release and DR17 is the development release. The two releases are very different from one another. DR16 takes a far more minimalist approach to the desktop than DR17 does. Without Panels and Icons, the DR16 desktop is made up of three mouse menus (one for each button), an Iconbox (where windows are Iconified — or minimized), a Pager (to switch between desktops), and  the Dragbar (which allows you to have desktops layered on top of one another.)

The DR17 release removes the Iconbox and the Pager and adds Shelves, which are Panels that house application launchers, pagers, clocks, etc. Even with the creation of a more standard desktop, DR17 retains its uniqueness as well as its speed. If you’re looking to give DR16 a try, you can install it via the standard Linux installation methods. Your best bet for DR17 is to give the gOS Rocket or the EliveCD distributions a try. And you should… it’s that cool.

#2: AfterStep

This is another of my favorite Linux desktops. Or at least it was back in early days of Linux. This desktop attracted me because it was one of the first (back around 1998) to use transparency. AfterStep was actually a fork of FVWM rebuilt to resemble the NeXTSTEP desktop. Like FVWM, AfterStep is light, quick, and can be as minimalist (or not) as you like. The main features of AfterStep are a mouse menu, Pager, Wharf (a dock-like applet), and the Winlist (a panel showing active applications). AfterStep is highly configurable via flat text files (so configuration requires getting to know the layout of configuration files.)

Currently AfterStep is enjoying the 2.2.8 release and is headed up by Sasha Vasko. One of the best aspects of AfterStep is the ability to granularly configure the look and feel. From timing of auto-raising windows to placement of titlebars (titlebars can be placed along a horizontal or vertical plane), AfterStep can be configured to a much higher level than most other window managers. You can install AfterStep your usual way. For example, in Mandriva, run the command urpmi AfterStep to install.

#3: Fluxbox

Fluxbox is probably one of the lightest of the lightweight window managers for Linux. It’s lightening fast and incredibly stable. Fluxbox shines in bringing new life to old hardware. And Fluxbox is a gift for those who prefer a minimalist approach to the desktop. Fluxbox is a fork of the Blackbox window manager and was created out of a need to add more features to Blackbox.

The Fluxbox desktop contains a mouse menu, a toolbar, and the Slit. The Slit is a small dock where self-contained applets reside. All basic configurations are handled via flat text configuration files. This manual configuration includes everything from the theme to the menu. To give you an idea of the size of the Fluxbox window manager, the rpm installation file is 1,196 KB. To put this into perspective, the KDE 4 install base is 644.2 MB.

Installing Fluxbox is simple. You can either search for Fluxbox in your graphical installation application (such as Synaptic or Yumex) or you can install via command line (for example: urpmi fluxbox in Mandriva.) If you’re not into installing on your own, you can try the Ubuntu-based distribution, dedicated to Fluxbox, aptly named Fluxbuntu.

#4: XFCE

XFCE is quietly gaining ground on the Linux desktop with help from Zonbu, Mythbuntu, Slackware, and Gentoo. It’s another lightweight desktop that has a more traditional desktop approach, with icons, panels, start menus, and system trays. The XFCE desktop is far less configurable than many of its peers. XFCE was created to be very modular so you can install as much or as little as you want. XFCE is also separated into applications: XFWM (the XFCE window manager), Xfmedia (the XFCE media player), Orage (the XFCE calendaring application), and Thunar (the file management tool). It is interesting to note that Thunar is also now the file manager for Enlightenment DR17.

Installing XFCE is as simple as running urpmi xfce (in Mandriva) or opening up your graphical installation tool and searching for XFCE. If installing isn’t for you, you can download a number of distributions (Gentoo and Slackware for example.) The Mythbuntu Media Center distribution also relies on XFCE for a desktop.

#5: Compiz/Compiz Fusion

When you talk Compiz, you’re talking full-blown, eye-popping 3D desktop goodness. Compiz/Compiz Fusion (they are actually two different projects) is the one desktop to install when 1) you have the hardware for it and 2) you REALLY want to impress your friends and family. Compiz is the original 3D Linux desktop. Compiz Fusion is a merging of Compiz and the now-defunct Beryl Project. Both of these projects mimic some of the features of Apple’s cialis wiki OS X but take them to new places.

One of the most amazing features of Compiz and Compiz Fusion is the Cube. The Cube takes the flat Linux pager metaphor (the ability to have multiple desktops) and folds the desktops into a three dimensional cube. With a click of the middle mouse button the desktop cube zooms out and you can rotate the cube to the cube face you want to work on. Add to this the ability to make the cube (and everything on the desktop) translucent and you have a very impressive desktop.

Installing Compiz isn’t for the faint of heart. It requires a number of pieces to be put together, a video card that supports AIGLX, and some patience. But the time and effort are very much rewarded with one of the coolest desktops to date. If you don’t want to take the time to install, you can give the latest Mandriva or the latest OpenSuSE a go. With the right hardware, you should have a working 3D desktop upon installation.

#6: IceWM

The developers of IceWM are proud of the fact that this lightweight window manager shares absolutely no code with any other window manager (written completely in C++). IceWM can be made compliant with GNOME and can use Imlib for graphics support. IceWM is a fairly straightforward window manager with few frills. The desktop is a panel, a start menu, a system tray, and a pager, and that’s it. IceWM is as configurable as any standard window manager but doesn’t boast the eye candy that Enlightenment or AfterStep does. But unlike Enlightenment DR16, IceWM does have a graphical control center for configurations. IceWM is easily installed via the command like (for example yum install icewm in Fedora).

#7: Windowmaker

Another NeXT-based window manager, Windowmaker took what NeXT did right and did not add FVWM on top. Windowmaker is yet another lightweight, super-fast, highly stable Linux window manager. It takes a minimalist approach but does support most image formats, and it has sliding application menus that can be torn off and pinned. (You can break off a submenu and anchor it to the desktop, leaving it open until you manually close it.) All configuration changes happen in real time. Windowmaker does have a dock where applications can be launched, but it’s not the shadowed, animated dock found in OS X. Windowmaker can be installed via command line, as in urpmi windowmaker in Mandriva, or it can be found in the package administration tools, such as Synaptic.

#8: Metacity

For one brief period, Metacity was the window manager used in the GNOME desktop. Eventually, Metacity broke out on its own. Created by Havoc Pennington (of Red Hat), Metacity uses the GTK+2 toolkit. Pennington has described Metacity as “intentionally boring” even without a logo. Metacity does not include numerous features. Instead, it glaringly boasts “good defaults.” One would describe Metacity as a typical old school UNIX-like window manager. In fact, it’s clean to the point of being almost sterile. But that doesn’t mean it is without merit.

Metacity is lightweight and fast. It is also very much a *NIX window manager, in that it can be installed in nearly all *NIX operating systems. Many distributions (such as Mandriva) install Metacity by default. If Metacity is not installed by default, it can be installed by command (such as yum install metacity) or it can be found in the package administration tool.

#9: FVWM

FVWM was, at one time, the dominant window manager for the Linux operating system. In fact, my first exposure to Linux was the FVWM window manager, and I distinctly remember how like Windows 98 it was — though not as “clean.” FVWM has an interesting history. Robert Nation was the creator back in 1993. He was tired of the limitations of one of the only UNIX window managers, TWM, during his work with the DoD. Nation had already created the rxvt terminal emulator and decided to bundle FVWM with a release of rxvt. He handed FVWM over to another developer a year after its release.

The current version of FVWM is 2.4.20, but interestingly enough, Nation’s last release, 1.24r, will still compile and run on modern Linux distributions. FVWM has a number of derivatives, including AfterStep, Enlightenment, and Windowmaker. To install FVWM, just run apt-get install fvwm and accept the dependencies.

#10: CDE

CDE isn’t really a Linux desktop, but it deserves mention because it heavily influenced so many Linux desktops. CDE (Common Desktop Environment) was created by a collaboration between Sunsoft, HP, IBM, and USL (a collaboration called The Open Group) in 1993. This new desktop was based on HP Visual User Environment and was derived from the Motif Window Manager. For a long period, CDE was the standard UNIX desktop environment. But in 2001, it was briefly phased out in favor of GNOME (until GNOME’s instability caused the return of CDE).

CDE is a fairly standard desktop consisting of a panel and start menu. Its biggest downfall is its antiquated UNIX-like look, lack of anti-alias font support, and confusing configuration. CDE is primarily a Solaris desktop but will install on AIX and HP-UX.

A world of options

And there you have it: 10 Linux desktops (well, nine, really, plus one UNIX) that are all very different, very usable, and very available. You may be happy with your current desktop, but if you really are a fan of Linux, you owe it to yourself to try out one or more of the ones described here. There are plenty more Linux desktops; but these are the best alternatives. Give them a try and report back here to let us know your favorite.

Author: Jack Wallen

Windows 7 may be generating some positive buzz, but Jack Wallen remains skeptical. In fact, he says it’s only a matter of time before Linux takes its rightful spot at the top of the OS heap.

I have an announcement. The error of Microsoft’s ways is finally catching up and will cause the once-invincible juggernaut to kneel before that which is Linux. How is this? Microsoft started a tiny snowball when it released Windows Me. That snowball did nothing but gain momentum. There have been ups and downs along the way (XP being an up, for sure). But for the most part, the court of public opinion has steady lost faith in what once was considered the heart of personal computing.

If you don’t believe me, read on.

Note: This article is also available as a PDF download.

1: Inconsistent Windows releases

One of the things you can always count on from Microsoft is that you can’t count on its new operating systems to be reliable. Let’s take a look at the individual releases:

With this in mind, what do we expect from Windows 7? Myself, not much.

2: Consistent Linux releases

Converse to number 1, you have the far more consistent releases of the various Linux distributions. Yes, there have been a few dips along the way (Fedora 9 being one of them). But for the most part, the climb for Linux has been steadily upward. Nearly every Linux distribution has improved with age. And this improvement isn’t limited to the kernel. Look at how desktops, end-user software, servers, security, admin tools, etc., have all improved over time. Once could easily argue that KDE 4 is an example of a sharp decrease in improvement. However, if you look at how quickly KDE 4 has improved from 4.0 to 4.3 you can see nothing but gains. This holds true with applications and systems across the board with Linux.

3. Continuing Windows price hikes

Recently, I have had a number of long-time Microsoft administrators asking my advice on solid replacements for Exchange. The reason? Microsoft changed its licensing for Exchange to a per-user seat. Now anyone who logs on to an Exchange server must have a license. You have 100 employees (including administrators) who need to log on to Exchange? Pony up! This gets serious when your company starts having to cough up the money for 500+ Exchange licenses. The very idea that Microsoft would make such a bold change to licenses is made even more ridiculous considering the current state of the economy. Companies worldwide are having to scale back. And like Exxon Mobile celebrating record profits amid the catastrophe known as Hurricane Katrina, Microsoft creating such a cost barrier while the globe is facing serious recession is irresponsible and reprehensible.

4. Stable Linux “prices”

Converse to number 3, the prices of open source software licenses have remained the same — $0.00. When those administrators come to me asking for open source replacements for Exchange I point them to eGroupware and Open-X-Change. Both are outstanding groupware tools that offer an even larger feature set than their Microsoft equivalent. Both are reliable, scalable, secure, and free. The only cost you will have with either is the hardware they are installed upon. And with both packages, there is no limit to the amount of users that can be set up. One user, 1,000 users — it’s all good with open source software.

5: Windows hardware incompatibility

Microsoft Vista was a nightmare when it came to hardware compatibility. Not only was Vista incompatible with numerous peripherals, it took supercomputer-level iron to run the operating system! Sure this was a boon to Intel, which stood to make a pretty shiny penny. Intel knew a good amount of the public would be shelling out for new hardware, and the new hardware would cost more because it had to be faster to run Vista in all its cialis pill cutter Aero glory. But even hardware that would run nearly any other OS with lightening-fast speed was brought to a slow, grinding halt with Vista.

6: Linux hardware compatibility

Converse to number 5, Linux continues to advance in the category of hardware compatibility. Take Xorg, for example. Recent developments with the star of Linux’ graphical desktops have the X Windows server running sans xorg.conf. This was done primarily because the system had grown so good at detecting hardware. And so long as there wasn’t a cheap KVM between your monitor and your PC, Xorg would easily find the mode for your display and run X properly. With new distributions (such as Fedora 10), X configuration is becoming a thing of the past. Most other pieces of hardware are finding the same level of recognition.

7: Windows promises

I wanted to save this for last, but seeing as how it is number 7… We’ve all heard the pundits proclaiming Windows 7 will be the resurrection of the Microsoft operating system. But I recall this same proclamation with nearly every release from Redmond. Windows Vista was going to revolutionize the way the user interfaced with the computer. Vista was going to be the operating system you would never notice. Instead, Vista refused to NOT let you notice. And Windows Me was going to take Windows 98 and make it far more simple for the average user. What did it really do? Remove nearly every actual functioning system in the operating system, leaving little more than a browser and an e-mail client.

Everyone is always fond of saying the next Windows release will redefine the personal computer. But the public has finally reached such a point of apathy for Microsoft’s up and coming, the majority doesn’t even realize something new is coming out. The media can continue to push Windows 7, but the public will continue using XP until Microsoft pries it from its cold, dead fingers. And of course no one really knows when Windows 7 will land. How many dates Microsoft announces vs. how many dates change will probably be a 1:1 ratio.

8: Linux transparency

Converse to 7… The next release of any Linux distribution is never shrouded in mystery. Because of the nature of open source, the release candidates are always available to the public (and not on a limited basis), and the timeline is always made available. Any user can know exactly when a feature-freeze happens for a release of any distribution. And all Linux distributions work under the “full disclosure” model. Because of this, there is little false advertising going on with Linux. And unlike with Microsoft, you will never hear of a distribution claiming that its next release will revolutionize computing. If you go to the Fedora Project Wiki, you can view all the proposed and accepted features that will be included in the next release. You can also view the completed release schedule, where you will see that Fedora 11 has set an alpha release of 02/03/09, a beta release of 03/24/09, and a final release of 05/26/09. These dates are fairly firm and almost always on target.

9: Feature comparison

Let’s compare the feature lists of Windows 7 and Fedora 11.

If you look at those features in and of themselves, you could easily argue that either one could be the more impressive list (depends upon your bias). But understand that the Fedora 11 features are added on an already outstanding operating system, whereas the Windows 7 features are being added to a lesser operating system. And what Microsoft is proclaiming to be the biggest improvement (multi-touch) doesn’t actually improve the operating system and also requires, surprise, new hardware! To get the most out of Fedora 11, you’ll be good to go with what you already have.

10: Hardware requirements

Vista-lite? Out of the mouths of Microsoft comes the proclamation that Windows 7 will run on any hardware that would run Vista and even slightly less powerful hardware. Slightly less powerful? What exactly does that mean? Well for one, Windows 7 will have no luck in the netbook market. And since XP is dying, the netbook market will be owned by Linux. Netbooks are not gaining enough power to run anything from Windows but the watered-down version of XP. Netbooks are not going anywhere, and consumers (both home and corporate) have their limits on how many hardware upgrades they will make to fulfill an operating systems’ needs. As of Fedora 10, the minimum system requirements look like something out of the mid ’90s.

Your take

In your opinion, has the court of public opinion already condemned Microsoft to failure or will Windows 7 pull Microsoft out of the muck and mire created by Vista? Will Linux continue its climb above Microsoft?

Does Linux have what it takes to meet the needs of the corporate desktop? Jack Wallen thinks so. Here’s his list of office apps that can handle everything from word processing to project management to data backups.

---

Let’s face it: Without a good set of office applications, your workday will be a waste of time. Productivity requires the right tools, and contrary to what some people think, Linux has everything you need to get you through the day without a hitch. We’re going to look at applications that will satisfy everyone in the organization — from HR to marketing to the front office.

Note: This information is also available as a PDF download.

#1: OpenOffice

This one goes without saying, offering word processing, spreadsheets, presentations, database management, drawing, and Web page editing. Add to that the ability to read and write Microsoft Office files and export to PDF and Flash (among other formats), and you have a complete office suite that should meet every need your office has. The OpenOffice user interface has little to no learning curve, so users will hardly know the difference between Microsoft Office and OpenOffice. OpenOffice is also cross-platform capable, with installation binaries for Linux, Solaris, Windows, and OS X (both Intel and PPC).

#2: Evolution

This is the Linux version of Outlook. Another one-stop shop, only this time it’s all about the PIM. E-mail, calendar, contacts, tasks, advanced searching, desktop integration, shared vCards, junk filters, encryption, LDAP support, iCal support, and much more. And if your company uses an Exchange server, you’re in luck because the Evolution Connector will be able to keep you connected. Evolution tends to be the default e-mail client for the GNOME desktop, but that doesn’t mean you can’t enjoy Evolution on KDE (or any other window manager.)

#3: Scribus

This is desktop publishing at its open source finest. Scribus can do almost anything Adobe  Acrobat can do — minus draining your wallet. Scribus does layering, opacity, ICC color management, CMYK color separations, and versatile PDF creation. With this tool, your newsletters, press packets, fliers, books, manuals, etc., are done in-house and on the cheap. I have used Scribus on numerous projects ranging from simple fliers to complex books.

#4: Gnucash

Gnucash is one of the best accounting packages available for Linux. It uses double-entry bookkeeping and is a suitable replacement for individual accounting as well as a small business accounting. Gnucash is one of the only accounting packages that is available across most all platforms (Linux, Solaris, UNIX, OS X, and Windows).

#5: OpenProj

This is the open source replacement for Microsoft Project. OpenProj has an equivalent user interface and functionality similar to Project and is interoperable with Project. OpenProj is released under the CPAL (Common Public Attribution License) license and is available for Linux, OS X, 32-bit Windows, BSD, and UNIX-like operating systems. OpenProj does require Java.

#6: Meeting Room Booking System

MRBS is a Web-based booking system for meeting rooms but can be altered to suit your needs. Although I wanted to include only applications that could be installed locally, I felt it necessary to include this application simply because it’s so useful. For corporate environments that have multiple rooms to book, this small-footprint application is perfect. It can also be modified for use as an appointment book, too. MRBS can do repeated bookings, reports, DAY/WEEK/MONTH views, multiple authorization levels, and multiple language support. The installation is simple but requires both a Web server (Apache) and a database server (either MySQL or Postgres).

#7: GnoTime

Formerly GTT, GnoTime is a desktop application that tracks time spent on projects and offers time-based invoice generation. Numerous reports can be generated (Journal, Activity, Daily, Status, To Do, Invoices, Query, Primer, New Reports, Edit Reports), and the interface is simple to use. GnoTime also includes a diary entry editor for each project. With GnoTime you can embed simple SQL queries into report templates. In addition, GnoTime benefits from autosave. So in the rare event your Linux desktop crashes, your data is safe from loss. GnoTime runs on Linux, UNIX, and OS X.

#8: GIMP

I realize that graphics software isn’t always included in lists of necessary office software — but if your office does any of its PR or marketing in-house, graphics tools are a necessity. And when using Linux, GIMP is the de facto standard for graphics creation and/or manipulation. GIMP is to Linux what Photoshop is to OS X and Windows. But GIMP goes Photoshop one better because it’s cross-platform ready. You can install GIMP on Linux, OS X, or Windows. It features a customizable interface, photo enhancement, digital retouching, cialis dosage side effects hardware support, a huge range of file format support, plug-in support, its own scripting language, filters, and a host of other outstanding features.

#9: Pidgen

Many corporate businesses have started regarding instant messaging as a legitimate form of interoffice (or inter-cubicle) communication. And Pidgin is one of the finest of the instant messaging clients. Pidgen works with nearly all of the instant messaging services and can have multiple accounts configured. It’s released under the GNU License, it’s free, and it works on Linux, UNIX, Windows, and OS X. Pidgen supports file transfer, typing notification, spell-check, buddy pouncing, away messages, etc.

#10: K3b

What office doesn’t back up data? None, if they employ safe business practices. And the CD offers one of the safest means of data backup. K3b makes backing up to CD simple. Not only can you do multiple backup types (audio, data cd, data dvd, copy cd, iso cd, iso dvd), you can save the backup information to a file. If you do the same backup regularly, all you need to do is open up the particular backup file and click burn. (No more having to drag and drop or hunt for particular files/folders to back up.) K3b can also blank CDR-Ws, retrieve TOCs, and write cue/bin files. K3b is available only for Linux and has been optimized for KDE.

This short list includes software that can easily handle much of your day-to-day office needs and do it on the Linux operating system. The software listed here is simple to use, reliable, (mostly) scalable, and business ready. Of course, this is a generalized list. Far more specialized office-type software is available on the Linux platform. One of the best places to look for such software is in your Install Software tool, such as Synaptic or Yumex. (The tool you have will depend upon the distribution you use.) Fire that tool up and look through the various categories (a good place to start is the “Office” category) to find what you need.

Linux is an outstanding platform for the office. It is flexible, cost-effective, reliable, secure, and enjoys a small learning curve. So if you’re doubting Linux can take over your office software needs, doubt no more!

Maybe the command line isn’t your favorite place to hang out, but to be an effective Linux admin, you need to be able to wield a few essential commands. Jack Wallen says these 10 are guaranteed to simplify your Linux admin life — and he explains why.

---

I understand that many of you don’t want to use the command line in Linux (or in any operating system, for that matter). But the truth is, to be a good administrator, you have to know the command line. Why? Well, with Windows there are times when the command line is the only thing that can save your skin. With Linux, the command line is vast, reliable, flexible, fast… I could go on and on.

And of the 2,119 possible commands from the /usr/bin directory (in Mandriva Spring 2008) and the 388 possible commands from /usr/sbin/, a few are indispensable. Here are 10 of them that might make your Linux admin life — or your introduction to Linux — a whole lot simpler.

I could make this easy and go with the most used commands (cd, ls, rm, etc — okay, etc isn’t a command, but you get the point). But instead, I am going to go with the most useful commands, and I’ll keep it as distribution-neutral as I can.

Note: This information is also available as a PDF download.

#1: top

I figured it was fitting to put the top command at the top. Although top is actually responsible for listing currently running tasks, it is also the first command Linux users turn to when they need to know what is using their memory (or even how much memory a system has). I often leave the top tool running on my desktop so I can keep track of what is going on at all times. Sometimes, I will even open up a terminal (usually aterm), place the window where I want it, and then hide the border of the window. Without a border, the terminal can’t be moved, so I always have quick access to the information I need.

Top is a real-time reporting system, so as a process changes, it will immediately be reflected in the terminal window. Top does have some helpful arguments (such as the -p argument, which will have top monitor only user-specified PIDs), but running default, top will give you all the information you need on running tasks.

#2: ln

To many administrators, links are an invaluable tool that not only make users lives simpler but also drastically reduce disk space usage. If you are unaware of how links can help you, let me pose this simple scenario: You have a number of users who have to access a large directory (filled with large files) on a drive throughout the day. The users are all on the same system, and you don’t want to have to copy the entire directory to each user’s ~/ directory. Instead, just create a link in each user’s ~/ directory to the target. You won’t consume space, and the users will have quick access. Of course when spanning drives, you cialis average age will have to use symlinks. Another outstanding use for links is linking various directories to the Apache doc root directory. Not only can this save space, it’s often advantageous from a security standpoint.

#3: tar/zip/gzip

Tar, zip, and gzip are archival/compression tools that make your administrator life far easier. I bundle these together because the tools can handle similar tasks yet do so with distinct differences (just not different enough to warrant their own entry in this article). Without these tools, installing from source would be less than easy. Without tar/zip/gzip, creating backups would require more space than you might often have.

One of the least used (but often most handy) features of these tools is the ability to extract single files from an archive. Now zip and gzip handle this more easily than tar. With tar, to extract a single file, you have to know the exact size of the file to be extracted. One area where tar/zip/gzip make administration simple is in creating shells scripts that automate a backup process. All three tools can be used with shell scripts and are, hands down, the best, most reliable backup tools you will find.

#4: nano, vi, emacs

I wasn’t about to place just one text editor here, for fear of stoking the fires of the “vi vs. emacs” war. To top that off, I figured it was best to throw my favorite editor — nano — into the mix. Many people would argue that these aren’t so much commands as they are full-blown applications. But all these tools are used within the command line, so I call them “commands.” Without a good text editor, administering a Linux machine can become problematic.

Imagine having to attempt to edit /etc/fstab or /etc/samba/smb.conf with OpenOffice. Some might say this shouldn’t be a problem, but OpenOffice tends to add hidden end-of-line characters to text files, which can really fubar a configuration file. For the editing of configuration or bash files, the only way to go is with an editor such as nano, vi, or emacs.

#5: grep

Many people overlook this amazingly useful tool. Grep prints lines that match a user-specified pattern. Say, for instance, that you are looking at an httpd.conf file that’s more than 1,000 lines long, and you are searching for the “AccessFileName .htaccess” entry. You could comb through that file only to come across the entry at line 429, or you can issue the command grep -n “AccessFileName .htaccess” /etc/httpd/conf/http.conf. Upon issuing this command you will be returned “439:AccessFileName .htaccess” which tells you the entry you are looking for is on, surprise of all surprises, line 439.

The grep command is also useful for piping other commands to. An example of this is using grep with the ps command (which takes a snapshot of current running processes.) Suppose you want to know the PID of the currently crashed Firefox browser. You could issue ps aux and search through the entire output for the Firefox entry. Or you could issue the command ps aux|grep firefox, at which point you might see something like this:

Now you know the PIDs of every Firefox command running.

#6: chmod

Permissions anyone? Linux administration and security would be a tough job without the help of chmod. Imagine not being able to make a shell script executable with chmod u+x filename. Of course it’s not just about making a file executable. Many Web tools require certain permissions before they will even install. To this end, the command chmod -R 666 DIRECTORY/ is one very misused command. Many new users, when faced with permissions issues trying to install an application, will jump immediately to 666 instead of figuring out exactly what permissions a directory or folder should have.

Even though this tool is critical for administration, it should be studied before jumping in blindly. Make sure you understand the ins and outs of chmod before using it at will. Remember w=write, r=read, and x=execute. Also remember UGO or User, Group, and Other. UGO is a simple way to remember which permissions belong to whom. So permission rw- rw- rw- means User, Group, and Other all have read and write permissions. It is always best to keep Other highly restricted in their permissions.

#7: dmesg

Call me old-school if you want, but any time I plug a device into a Linux machine, the first thing I do is run the dmesg command. This command displays the messages from the kernel buffer. So, yeah, this is an important one. There is a lot of information to be garnered from the dmesg command. You can find out system architecture, gpu, network device, kernel boot options used, RAM totals, etc.

A nice trick is to pipe dmesg to tail to watch any message that comes to dmesg. To do this, issue the command dmesg | tail -f and the last few lines of dmesg will remain in your terminal. Every time a new entry arrives it will be at the bottom of the “tail.” Keep this window open when doing heavy duty system administration or debugging a system.

#8: kill/killall

One of the greatest benefits of Linux is its stability. But that stability doesn’t always apply to applications outside the kernel. Some applications can actually lock up. And when they do, you want to be able to get rid of them. The quickest way to get rid of locked up applications is with the kill/killall command. The difference between the two commands is that kill requires the PID (process ID number) and killall requires only the executable name.

Let’s say Firefox has locked up. To kill it with the kill command you would first need to locate the PID using the command ps aux|grep firefox command. Once you got the PID, you would issue kill PID (Where PID is the actual PID number). If you didn’t want to go through finding out the PID, you could issue the command killall firefox (although in some instances it will require killall firefox-bin). Of course, kill/killall do not apply (nor should apply) to daemons like Apache, Samba, etc.

#9: man

How many times have you seen “RTFM”? Many would say that acronym stands for “Read the Fine* Manual” (*This word is open for variation not suitable for publication.) In my opinion, it stands for “Read the Fine Manpage.” Manpages are there for a reason — to help you understand how to use a command. Manpages are generally written with the same format, so once you gain an understanding of the format, you will be able to read (and understand) them all. And don’t underestimate the value of the manpage. Even if you can’t completely grasp the information given, you can always scroll down to find out what each command argument does. And the best part of using manpages is that when someone says “RTFM” you can say I have “RTFMd.”

#10: mount/umount

Without these two commands, using removable media or adding external drives wouldn’t happen. The mount/umount command is used to mount a drive (often labeled like /dev/sda) to a directory in the Linux file structure. Both mount and umount take advantage of the /etc/fstab file, which makes using mount/umount much easier. For instance, if there is an entry in the /etc/fstab file for /dev/sda1 that maps it to /data, that drive can be mounted with the command mount /data. Typically mount/umount must have root privileges (unless fstab has an entry allowing standard users to mount and unmount the device). You can also issue the mount command without arguments and you will see all drives that are currently mounted and where they’re mapped to (as well as the type of file system and the permissions).

Can’t live without ‘em

These 10 Linux commands make Linux administration possible. There are other helpful commands, as well as commands that are used a lot more often than these. But the commands outlined here fall into the necessity category. I don’t know about you, but I don’t go a day without using at least half of them. Do you have a Linux command or two that you can’t live without? If so, let us know.

Before debating the relative merits and shortcomings of Linux and Windows, it helps to understand the real distinctions between them. Jack Wallen has distilled the key differences into one list.

---

I have been around the Linux community for more than 10 years now. From the very beginning, I have known that there are basic differences between Linux and Windows that will always set them apart. This is not, in the least, to say one is better than the other. It’s just to say that they are fundamentally different. Many people, looking from the view of one operating system or the other, don’t quite get the differences between these two powerhouses. So I decided it might serve the public well to list 10 of the primary differences between Linux and Windows.

Note: This information is also available as a PDF download.

#1: Full access vs. no access

Having access cialis 5mg side effects to the source code is probably the single most significant difference between Linux and Windows. The fact that Linux belongs to the GNU Public License ensures that users (of all sorts) can access (and alter) the code to the very kernel that serves as the foundation of the Linux operating system. You want to peer at the Windows code? Good luck. Unless you are a member of a very select (and elite, to many) group, you will never lay eyes on code making up the Windows operating system.

You can look at this from both sides of the fence. Some say giving the public access to the code opens the operating system (and the software that runs on top of it) to malicious developers who will take advantage of any weakness they find. Others say that having full access to the code helps bring about faster improvements and bug fixes to keep those malicious developers from being able to bring the system down. I have, on occasion, dipped into the code of one Linux application or another, and when all was said and done, was happy with the results. Could I have done that with a closed-source Windows application? No.

#2: Licensing freedom vs. licensing restrictions

Along with access comes the difference between the licenses. I’m sure that every IT professional could go on and on about licensing of PC software. But let’s just look at the key aspect of the licenses (without getting into legalese). With a Linux GPL-licensed operating system, you are free to modify that software and use and even republish or sell it (so long as you make the code available). Also, with the GPL, you can download a single copy of a Linux distribution (or application) and install it on as many machines as you like. With the Microsoft license, you can do none of the above. You are bound to the number of licenses you purchase, so if you purchase 10 licenses, you can legally install that operating system (or application) on only 10 machines.

#3: Online peer support vs. paid help-desk support

This is one issue where most companies turn their backs on Linux. But it’s really not necessary. With Linux, you have the support of a huge community via forums, online search, and plenty of dedicated Web sites. And of course, if you feel the need, you can purchase support contracts from some of the bigger Linux companies (Red Hat and Novell for instance).

However, when you use the peer support inherent in Linux, you do fall prey to time. You could have an issue with something, send out e-mail to a mailing list or post on a forum, and within 10 minutes be flooded with suggestions. Or these suggestions could take hours of days to come in. It seems all up to chance sometimes. Still, generally speaking, most problems with Linux have been encountered and documented. So chances are good you’ll find your solution fairly quickly.

On the other side of the coin is support for Windows. Yes, you can go the same route with Microsoft and depend upon your peers for solutions. There are just as many help sites/lists/forums for Windows as there are for Linux. And you can purchase support from Microsoft itself. Most corporate higher-ups easily fall victim to the safety net that having a support contract brings. But most higher-ups haven’t had to depend up on said support contract. Of the various people I know who have used either a Linux paid support contract or a Microsoft paid support contract, I can’t say one was more pleased than the other. This of course begs the question “Why do so many say that Microsoft support is superior to Linux paid support?”

#4: Full vs. partial hardware support

One issue that is slowly becoming nonexistent is hardware support. Years ago, if you wanted to install Linux on a machine you had to make sure you hand-picked each piece of hardware or your installation would not work 100 percent. I can remember, back in 1997-ish, trying to figure out why I couldn’t get Caldera Linux or Red Hat Linux to see my modem. After much looking around, I found I was the proud owner of a Winmodem. So I had to go out and purchase a US Robotics external modem because that was the one modem I knew would work. This is not so much the case now. You can grab a PC (or laptop) and most likely get one or more Linux distributions to install and work nearly 100 percent. But there are still some exceptions. For instance, hibernate/suspend remains a problem with many laptops, although it has come a long way.

With Windows, you know that most every piece of hardware will work with the operating system. Of course, there are times (and I have experienced this over and over) when you will wind up spending much of the day searching for the correct drivers for that piece of hardware you no longer have the install disk for. But you can go out and buy that 10-cent Ethernet card and know it’ll work on your machine (so long as you have, or can find, the drivers). You also can rest assured that when you purchase that insanely powerful graphics card, you will probably be able to take full advantage of its power.

#5: Command line vs. no command line

No matter how far the Linux operating system has come and how amazing the desktop environment becomes, the command line will always be an invaluable tool for administration purposes. Nothing will ever replace my favorite text-based editor, ssh, and any given command-line tool. I can’t imagine administering a Linux machine without the command line. But for the end user — not so much. You could use a Linux machine for years and never touch the command line. Same with Windows. You can still use the command line with Windows, but not nearly to the extent as with Linux. And Microsoft tends to obfuscate the command prompt from users. Without going to Run and entering cmd (or command, or whichever it is these days), the user won’t even know the command-line tool exists. And if a user does get the Windows command line up and running, how useful is it really?

#6: Centralized vs. noncentralized application installation

The heading for this point might have thrown you for a loop. But let’s think about this for a second. With Linux you have (with nearly every distribution) a centralized location where you can search for, add, or remove software. I’m talking about package management systems, such as Synaptic. With Synaptic, you can open up one tool, search for an application (or group of applications), and install that application without having to do any Web searching (or purchasing).

Windows has nothing like this. With Windows, you must know where to find the software you want to install, download the software (or put the CD into your machine), and run setup.exe or install.exe with a simple double-click. For many years, it was thought that installing applications on Windows was far easier than on Linux. And for many years, that thought was right on target. Not so much now. Installation under Linux is simple, painless, and centralized.

#7: Flexibility vs. rigidity

I always compare Linux (especially the desktop) and Windows to a room where the floor and ceiling are either movable or not. With Linux, you have a room where the floor and ceiling can be raised or lowered, at will, as high or low as you want to make them. With Windows, that floor and ceiling are immovable. You can’t go further than Microsoft has deemed it necessary to go.

Take, for instance, the desktop. Unless you are willing to pay for and install a third-party application that can alter the desktop appearance, with Windows you are stuck with what Microsoft has declared is the ideal desktop for you. With Linux, you can pretty much make your desktop look and feel exactly how you want/need. You can have as much or as little on your desktop as you want. From simple flat Fluxbox to a full-blown 3D Compiz experience, the Linux desktop is as flexible an environment as there is on a computer.

#8: Fanboys vs. corporate types

I wanted to add this because even though Linux has reached well beyond its school-project roots, Linux users tend to be soapbox-dwelling fanatics who are quick to spout off about why you should be choosing Linux over Windows. I am guilty of this on a daily basis (I try hard to recruit new fanboys/girls), and it’s a badge I wear proudly. Of course, this is seen as less than professional by some. After all, why would something worthy of a corporate environment have or need cheerleaders? Shouldn’t the software sell itself? Because of the open source nature of Linux, it has to make do without the help of the marketing budgets and deep pockets of Microsoft. With that comes the need for fans to help spread the word. And word of mouth is the best friend of Linux.

Some see the fanaticism as the same college-level hoorah that keeps Linux in the basements for LUG meetings and science projects. But I beg to differ. Another company, thanks to the phenomenon of a simple music player and phone, has fallen into the same fanboy fanaticism, and yet that company’s image has not been besmirched because of that fanaticism. Windows does not have these same fans. Instead, Windows has a league of paper-certified administrators who believe the hype when they hear the misrepresented market share numbers reassuring them they will be employable until the end of time.

#9: Automated vs. nonautomated removable media

I remember the days of old when you had to mount your floppy to use it and unmount it to remove it. Well, those times are drawing to a close — but not completely. One issue that plagues new Linux users is how removable media is used. The idea of having to manually “mount” a CD drive to access the contents of a CD is completely foreign to new users. There is a reason this is the way it is. Because Linux has always been a multiuser platform, it was thought that forcing a user to mount a media to use it would keep the user’s files from being overwritten by another user. Think about it: On a multiuser system, if everyone had instant access to a disk that had been inserted, what would stop them from deleting or overwriting a file you had just added to the media? Things have now evolved to the point where Linux subsystems are set up so that you can use a removable device in the same way you use them in Windows. But it’s not the norm. And besides, who doesn’t want to manually edit the /etc/fstab fle?

#10: Multilayered run levels vs. a single-layered run level

I couldn’t figure out how best to title this point, so I went with a description. What I’m talking about is Linux’ inherent ability to stop at different run levels. With this, you can work from either the command line (run level 3) or the GUI (run level 5). This can really save your socks when X Windows is fubared and you need to figure out the problem. You can do this by booting into run level 3, logging in as root, and finding/fixing the problem.

With Windows, you’re lucky to get to a command line via safe mode — and then you may or may not have the tools you need to fix the problem. In Linux, even in run level 3, you can still get and install a tool to help you out (hello apt-get install APPLICATION via the command line). Having different run levels is helpful in another way. Say the machine in question is a Web or mail server. You want to give it all the memory you have, so you don’t want the machine to boot into run level 5. However, there are times when you do want the GUI for administrative purposes (even though you can fully administer a Linux server from the command line). Because you can run the startx command from the command line at run level 3, you can still start up X Windows and have your GUI as well. With Windows, you are stuck at the Graphical run level unless you hit a serious problem.

Your call…

Those are 10 fundamental differences between Linux and Windows. You can decide for yourself whether you think those differences give the advantage to one operating system or the other. Me? Well I think my reputation (and opinion) precedes me, so I probably don’t need to say I feel strongly that the advantage leans toward Linux.