Current_Issue.tar.gz - Kentucky Fried Linux
For most people, the word kernel inspires visions of corn, wheat or possibly fried chicken. Here in the Linux world, although we still might appreciate The Colonel's 11 herbs and spices, kernel means something much more profound. The kernel is Linux. Sure we add lots of fancy programs, interfaces and command-line tools, but in the end, Linux is the kernel. This month, we focus on it.
Do you ever smugly brag about the uptime of your Linux machines to your Windows friends? I don't know about you, but every time I do, either the power goes out or I have to reboot due to a kernel upgrade. Thankfully, Waseem Daher shows us a bit about Ksplice. Using Ksplice, software updates can be applied without rebooting the Linux machine. Add to that a battery backup, and we can all brag to our friends about uptimes. Unless, that is, we're running an old kernel and they come over 498 days after we first started. (Uptime wraparound hasn't been a problem for a while, but most of us still remember it.)
One of the jobs the kernel has is to schedule CPU time for different processes. We have a few different looks at kernel schedulers: a real-time scheduler that Ankita Garg explains and a “Completely Fair” scheduler that Chandandeep Singh Pabla tells us about. One of the great strengths of the Linux kernel is its flexibility, and that should be fairly evident after reading this month's issue.
All Linux admins worth their salt know that a properly maintained Linux machine is a fairly secure beast. “Fairly secure” usually isn't satisfactory, however, and that's where people like Mick Bauer come into play. This month, he continues his series on setting up a secure proxy, but he also interviews Anthony Lineberry about /dev/mem rootkits. The best security specialist is a paranoid security specialist, and Mick does his best to worry us all a bit.
If all this kernel talk is beginning to worry you that this issue has nothing for you, fear not! I'd be lying if I claimed to do any work with the kernel anymore. In fact, not since the days of compiling Debian kernels for my PowerPC hardware have I even used anything but the stock kernel that comes with my distro. We realize you might fit into that boat as well, so we've stuffed a ton of other stuff between these covers just for you. (And maybe for me.)
Kyle Rankin shows us how to join the instant-messaging bandwagon without ever leaving the comfort of our IRC windows. With Bitlbee, you can pretend everyone on the planet uses IRC, even if they're using the dreaded MSN Messenger. To follow that up, Kyle and Bill Childers are back to their spatting. This time, they're arguing over the usefulness of Twitter. As a Twitter user myself, I think I lean toward Bill's side this month, but feel free to choose for yourself.
Dave Taylor takes us back to the command line as we dissect the English language a bit. Of course, we have the computer do the dirty work, but in the end, you'll learn a bit about scripting language and the English language. Reuven M. Lerner teaches us about Fixtures and Factories in your Rails projects. If you program in Rails and work with databases, you won't want to miss Reuven's column.
We didn't stop there. Marcel Gagné demonstrates eyeOS—an entire operating system you can control from a Web browser. You get to set up a little cloud computing system of your very own! Add to that our normal list of reviews, product announcements and regular columns, and this issue is bound to please even the most obscure Linux user. So go get your can of corn kernels, a bag of wheat kernels or even a bucket of chicken, and sit back to enjoy this issue of Linux Journal.
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 firstname.lastname@example.org. Or, swing by the #linuxjournal IRC channel on Freenode.net.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Tech Tip: Really Simple HTTP Server with Python
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide