Current_Issue.tar.gz - Administrate Me
As a system administrator, one of my favorite things is to be ignored. No, it's not due to a latent social anxiety disorder or anything; it's just because when the sysadmin doesn't hear from anyone, it means things are working. In fact, if things are going really well, we can forward our phones and spend the afternoon on a beach somewhere. No one would ever miss us.
Sadly, that's not usually how things go. Call it job security, call it bad karma, or just blame Bill Gates—for whatever reason, computers break. Even when they don't break, they get old and wear out. In fact, for most of our workdays (and nights), we system administrators spend our lives in a paranoid state ready for the whole world to fall apart. When that happens, everyone suddenly remembers the sysadmin and suddenly is angry with him or her. That's where this issue of Linux Journal comes into play. With our system administration issue, we try to fortify your paranoia with redundancy, calm your nerves with best practices and teach the fine art of telling the future to determine when a failure is about to happen. If we do a really good job, you might even learn a few ways to prevent disaster before it strikes at all.
Mick Bauer ends his series on building a transparent firewall. The best offense against outside attack is a strong defense, and Mick will make you paranoid enough to make sure your firewall is top notch. Kyle Rankin gets into the networking act this month as well and shows how to bond Ethernet ports together for redundancy or speed. So many servers come with multiple Ethernet ports, it's a waste not to take advantage of them.
When you have a server with multiple bonded NICs, it certainly makes sense to add storage to it as well. Greg Bledsoe describes how to use AoE (ATA over Ethernet) to build your own SAN at a fraction of the cost of buying one. With hard drives connected directly to your network, it takes out a single point of failure and also allows a gradual expansion without the need for buying new chassis.
With Linux acting as a firewall, and Linux acting as a SAN, why not add one more possibility to the mix? Henry Van Styn not only shows us how to turn our Linux box into a switch, but also how to use VLANs in that switch. VLANs are a powerful way to secure network traffic, and with Linux acting as a switch, it also can use the security of VLANs in addition to its other abilities.
But, that's just the networking part of this issue. There's lots more to being a sysadmin than filtering a few packets. Michael J. Hammel shows how to manage KVM deployments with virt-manager. Hardware virtualization is a powerful tool, and thanks to virt-manager, those VMs can be configured with a nice GUI tool from any Linux computer that can access the VM host.
Sometimes it's not just virtual machines that need to be installed, however, and that's where Clonezilla comes in. Jeramiah Bowling demonstrates the ins and outs of Clonezilla, a powerful cloning tool that makes imaging new computers a breeze. When imaging, of course, it's important that your original image is exactly how you want it. Tony Kay's article on Linux swap space is something you'll want to read before creating your master image. We don't usually think much about swap space, but it's more than just a safety net if you happen to run out of RAM. And, of course, no system administrator would be caught dead without backups—lots and lots of backups. Petros Koutoupis explains how to take snapshots with LVM2, which is a neat way to take zero downtime snapshots of your Linux system.
We certainly haven't left out our non-sysadmins this month though. If you've been looking for a viable, open-source replacement for Microsoft Exchange, SOGo might be just the thing you're looking for. Sure, it takes some system administration to install it, but once it's going, SOGo is a tool for the end user. Ludovic Marcotte covers the features of this powerful groupware alternative. When you add to that our regular cast of programmers, like Dave Taylor scripting mortgage calculations and Reuven M. Lerner delving into HTML5, this issue is bound to please. For now, I'm going to take this issue and head to the beach. Don't worry; I'll forward my phones in case anything catastrophic happens. Otherwise, I doubt anyone will miss me.
Shawn Powers is the Associate Editor for Linux Journal. He's also the Gadget Guy for LinuxJournal.com, and he has an interesting collection of vintage Garfield coffee mugs. Don't let his silly hairdo fool you, he's a pretty ordinary guy and can be reached via e-mail at shawn@linuxjournal.com. Or, swing by the #linuxjournal IRC channel on Freenode.net.
Shawn Powers is an Associate Editor for Linux Journal. You might find him chatting on the IRC channel, or Twitter
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- Designing Electronics with Linux
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Dynamic DNS—an Object Lesson in Problem Solving
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Build a Skype Server for Your Home Phone System
- Validate an E-Mail Address with PHP, the Right Way
- Why Python?
- A Topic for Discussion - Open Source Feature-Richness?
- Tech Tip: Really Simple HTTP Server with Python
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




2 hours 39 min ago
2 hours 47 min ago
5 hours 1 min ago
7 hours 31 min ago
17 hours 34 min ago
22 hours 1 min ago
1 day 1 hour ago
1 day 2 hours ago
1 day 4 hours ago
1 day 4 hours ago