I was just asked to run for a position on the board of directors for an organization of Technology Directors in Michigan. Being on the MAEDS board would be a great honor and all, but it reminds me that as Linux users, we are part of a diverse group of technology users.
In my peer group of educational technology folks, I'm known as, "The Linux Guy." Yeah, I know, pretty cool. I have to remind myself, however, that Pro-Linux is not the same as Anti-Microsoft. True confession? I use Mac OSX more often than I use Linux. It's what my job requires, and honestly, it fills a need very well. Granted, part of the reason I use OSX more often is because my Linux infrastructure needs less maintenance, but we all already know that.
So my point? It's easy to get angry and bitter in the face of companies like Apple and Microsoft. It's easy to trash talk the opposition, because let's face it, Linux is better at so much stuff!!! Like the old adage, "You catch more flies with honey," however, we need to remember to point out the strengths of Open Source software, not the weaknesses of others.
Oh, and vote for Shawn. ;o)
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!
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- LiveCode Ltd.'s LiveCode
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