Linux Users: Why Did You Switch?
As a Linux Journal editor, I'd love to claim that in my college years I realized the oppression stemming from proprietary operating systems. I'd love to confess that Linux was the natural choice amongst a sea of other options. Heck, I'd even like to say back then Linux was my first choice. For me, however, the story played out a bit differently.
I was just plain old poor. In 1994, I started a computer repair business. I had failed Econ the previous semester at Michigan Tech, so you can imagine how successful my computer business was. It turns out, I didn't like charging people to help them with their problems. Much of my "profit" contained chocolate chips, and for some reason, I'd take people's old broken computers instead of charging labor. (Again, "PowerNet Computer Services" didn't last very long)
So the next year, I enrolled into a local community college. This was both because it was close to my "business", and because university was too expensive. It was during this time I started building computers from all the parts I'd taken as payment. It was also this time that I started using Linux. The price was right, and my Unix experience made Linux a viable option. I fell in love very quickly, and what started as merely a cheap way to learn about *nix developed into skills that would form my future career on several fronts. Thanks Linux!
So now it's your turn. Why are you a Linux user?
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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SourceClear Open
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Google's SwiftShader Released
- Parsing an RSS News Feed with a Bash Script
- Non-Linux FOSS: Caffeine!
- 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