How Linux admins can avoid common pitfalls

• Tags:
• Command Line,
• Gui,
• Command,
• Commands

Jack Wallen

Published: 31 Dec 2008 12:44 GMT

• 
• 
• 
• 
• 

For many, migrating to Linux is a rite of passage that equates to a thing of joy. For others, it's a nightmare waiting to happen. It's wonderful when it's the former; it's a real show stopper when it's the latter.

But that nightmare doesn't have to happen, especially when you know, first hand, the most common mistakes new Linux administrators make. This article will help you avoid those mistakes by laying out the most typical Linux missteps.

1. Installing applications from various types
This might not seem like such a bad idea at first. You are running Ubuntu so you know the package-management system uses .deb packages. But there are a number of applications that you find only in source form. No big deal right? They install, they work. Why shouldn't you?

Simple — your package-management system can't keep track of what you have installed if it is installed from source. So what happens when package A (that you installed from source) depends upon package B (that was installed from a .deb binary) and package B is upgraded from the update manager? Package A might still work or it might not. But if both package A and B are installed from .debs, the chances of them both working are far higher. Also, updating packages is much easier when all packages are from the same binary type.

2. Neglecting updates
This one doesn't point out Linux as much as it does poor administration skills. But many admins get Linux up and running and think they have to do nothing more. It's solid, it's secure, it works.

But new updates can patch new exploits. Keeping up with your updates can make the difference between a compromised system and a secure one. And just because you can rest on the security of Linux doesn't mean you should. For security, for new features, for stability — the same reasons we have all grown accustomed to updating with Windows — you should always keep up with your Linux updates.

3. Poor root password choice
Repeat after me: 'The root password is the key to the kingdom.'

So why would you make the key to the kingdom simple to crack? Sure, make your standard user password something you can easily remember and/or type. But the root password — that is, the one that's protecting your enterprise database server — should be given a much higher difficulty level. Make that password one you might have to store, encrypted, on a USB key, requiring you to slide that USB key into the machine, mount it, decrypt the password, and use it.

4. Avoiding the command line
No-one wants to have to memorise a bunch of commands. And for the most part, the GUI takes care of a vast majority of them. But there are times when the command line is easier, faster, more secure and more reliable. Avoiding the command line should be considered a cardinal sin of Linux administration. You should at least have a solid understanding of how the command line works and a small arsenal of commands you can use without having to RTFM.

With a small selection of command-line tools on top of the GUI tools, you should be ready for just about anything.

5. Not keeping a working kernel installed
Let's face it, you don't need 12 kernels installed on one machine. But you do need to update your kernel, and the update process doesn't delete previous kernels. What do you do?

You keep at least the most recently working kernel at all times. Let's say you have 2.6.22 as your current working kernel...

• 
• 
• 
• 

• Share this article:
• Digg
• Slashdot
• Del.ici.ous
• Stumble
• Reddit

• Most Recent
• Most Popular