June 2014 Issue of Linux Journal: Networking
I tend to be a fairly funny guy. Well, at least I think I'm funny. My kids might disagree. The thing is, it's hard to find a group of people to understand obscure networking jokes. At a non-tech conference, for example, if I say to the person next to me, "Jeez, that speaker must have delivered his presentation with UDP packets, because he never stopped to see if any of us were getting what he was talking about!"—exactly zero people laugh. In fact, I usually get really weird looks. At a Linux conference, however, the same comment usually gets an eye-roll. (As a father of teenagers, I consider an eye-roll the equivalent to amusement.) That's why I love Linux Journal so much. This month, we're talking about Networking, and everyone in our little "room" understands what we're talking about! So let's peel this issue apart one OSI layer at a time.
Reuven M. Lerner starts us out with URLs. That ubiquitous string of text that takes you to a location (usually a Web site) is something we often take for granted. As the Internet matures, however, an understanding of how URLs work is vital. Reuven teaches us everything from protocol designations to URL fragments. If you've ever wondered about those seemingly out of place # characters in a URL, you'll want to read his column. Dave Taylor follows with a great look at the evolution of scripting. Just like we no longer have to hand-crank our car engine to get it running (mine doesn't even have a key anymore, just a button), shell scripting has changed through the years. Supporting legacy systems (or legacy code) is a problem we all need to deal with, as Dave shows us with one of his real-world experiences.
Kyle Rankin continues his theme this month and teaches how to encrypt our e-mail—specifically text-based Mutt e-mail. Kyle remains true to his command-line preferences, and rather than switch to a GUI e-mail app, he describes how to use GPG with Mutt. If you're a Mutt user like Kyle, or just want to learn about implementing GPG, don't miss his column. I follow Kyle with a continuation on last month's scripting basics article. Rather than leaving you with a simple set of tools, I tried to come up with some examples of using those tools in real-world situations. My scripts are basic and my techniques are simple, but that's the point. Don't be intimidated by the command line. It's powerful and not terribly difficult to master.
Any network user or administrator is familiar with firewalling tools. Most
of us, however, aren't nearly as familiar with Berkeley Packet Filters.
Valentine Sinitsyn walks through using BPF to do some very low-level
Like every issue of Linux Journal, this one is chock full of tech tips, product announcements and recommendations. The networking issue touches on so many disciplines and interest areas in the Linux community, that it's always one of our favorites. The large majority of folks still won't understand our networking jokes, but that's okay, they can sit around as bored as a teenager in a Faraday cage while we all enjoy this issue. (Thank you, thank you, I'll be here all night....)Watch the video overview for this issue:
Available to Subscribers: June 1
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
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