Linux Lunacy in Alaska
Editors' Note: This article has been updated since its original posting.
Disclaimer: Linux Journal is a cosponsor of Linux Lunacy.
Doc Searls will fill you in on the social and networking opportunities available to attendees of the third annual Linux Lunacy cruise. And Holland America Lines certainly has the floating hospitality thing down. Think of the ms Amsterdam as a Las Vegas hotel with lifeboat drills.
But smoked salmon for breakfast, whales to the starboard and aurora borealis in clear skies are not exactly going to sell our more serious-minded readers or their management on the idea of sitting on a boat in Alaska for a Linux conference. More important is the content of the technical sessions. A lot of the prepared material seems to be on the introductory side, but the speakers have the depth of knowledge needed to give detailed answers to more complicated questions.
Linux Lunacy has two tracks going at once for most of the days at sea. School is out during port calls. Because there are more talks than one actually can attend, we missed the full day of "Introduction to the Linux Kernel" by Theodore Ts'o, which is an updated version of the tutorial we covered last year at the Usenix Technical Conference.
Ted also did a talk on "More than You Ever Wanted to Know about Filesystems", which balanced an overview of filesystem design with some practical advice for sysadmins who choose and maintain filesystems. Your best way to keep an ext2 or ext3 filesystem defragmented and running its best is not to fill it up all the way, or as Ted put it, "Overprovision like mad." Although it's difficult to come up with a benchmark that fairly measures the performance of a filesystem that has been in service for a while, the Postmark benchmark provides a good simulation of a running mail server, he said.
Mick Bauer, Linux Journal's security columnist, is another speaker on the cruise. If you've been reading Linux Journal for years, why go see Mick live? Because if you have questions about your own security situation, he's good at addressing them with, "That's a really interesting question" and hitting you with a detailed answer.
Mick's talk on "Paranoid Penguin's Choice: Outstanding Linux Security Tools" covered many of the same tools he has been writing about in his column, but he added more material and pointed out, of course, that Carrie-Anne Moss ran nmap in The Matrix Reloaded.
Besides the tool-oriented material he covers in his column, Mick covered more security policy issues in person. For example, you don't have to leave ports open willy-nilly to have a flexible security policy that lets users get their jobs done. Simply make sure that people who need a port open come to you, and open it if they need it. "If they haven't talked to me, I generally want to block it", he said.
And, the comment field in Firewall Builder is there for a reason. Remind yourself of the reason why you decided to allow something.
If you think you travel light, try comparing luggage with Bruce Perens. His goal is to keep everything he needs for a trip in his backpack, so that he can run to a meeting without having to drop baggage off at a hotel.
Bruce's enabling technology for world travelers includes a GSM phone and a tiny laptop. You can get your mail anywhere with GSM service, but there's a charge per kilobyte. If you're traveling only in the US, check out the unmetered service from Sprint.
Greg Haerr, author of Microwindows, did two talks on the C programming language, including one introduction and one, called "C Programming Tricks of the Trade", on good habits to develop when working on C projects.
Although Greg certainly was clear on the fundamental doctrine that you should write code to be clear and correct first, then come back and optimize critical sections if you have to, there are some decisions where both clarity and performance win. For example, a freestanding:
is sometimes faster than:
And, because they're equally easy to read, you might as well use the former.
If you know that a variable is never supposed to have a negative value, declaring it as unsigned keeps the compiler from having an excuse to do unnecessary sign extension before working with it.
Greg also covered effective debugging with assert and everyone's favorite debugging tool, printf.
Future events include the first public performance of the SCO version of "I Am the Very Model of a Modern Major General" and a talk by the self-proclaimed king of not preparing for talks, Linus Torvalds. And yes, there's a Linux Professional Institute certification track and more technical tracks, including dueling Perl and Python tutorials. Fundamentally, however, the Linux Lunacy cruise compares well to other Linux-oriented conferences.
Linux Lunacy doesn't have the diversity of speakers or topics of a large event such as the Usenix Technical Conference, but the percentage of technical content is as high as you want. Plus, not counting the cruise environment and the opportunity to meet speakers outside class, the small class size means that you have more time to ask questions.
Don Marti is Editor in Chief of Linux Journal.
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
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- Google's SwiftShader Released
- 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