Two weeks ago, I heard that Progeny Linux Systems of Indianapolis had closed its doors for the last time. The end was a long time coming – in fact, six years longer than I predicted. All the same, I paused last week for a bit of nostalgia. Working for the company in 2000-01 gave me my first sense of my potential and gave me a sense of self-worth at a time when I badly needed it.
I first heard of Progeny through Bruce Perens. I was talking to him over the phone for a story I was doing for Maximum Linux. When our business was done and we were chatting, I happened to mention that I was looking for work. At the time, Perens (whom I'm calling by his last name so that this entry doesn't sound like a Monty Python skit littered with Bruces) was running a venture capital group that had just funded a startup run by Ian Murdock, the founder of the Debian GNU/Linux distribution and his partner John Hartman. Would I be interested in doing marketing and communications for the new company?
Somehow, I managed not to gibber incoherently with excitement, and told him I would. But I admit I danced around our townhouse when I got off the phone.
A phone interview and a week or so later, and I was on a plane to Indianapolis, unsure whether the job would work out. I was a bit worried about the cost, since I had quit Stormix Technologies a month previously, but determined to enjoy the adventure.
I was met at the airport by Ian and John and a couple of coders – John Goerzen and possibly Branden Robinson. They whisked me away to a Greek restaurant, where I quickly realized that these guys had serious chops. I had thought for a while that Stormix was the big time, but I realized that, in going to work for Progeny, I was jumping leagues.
Somehow, I convinced them that I would be an asset. I may not be able to write code for a “Hello, World
Bruce Byfield (nanday)
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!
- Google's SwiftShader Released
- SUSE LLC's SUSE Manager
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Tech Tip: Really Simple HTTP Server with Python
- Parsing an RSS News Feed with a Bash Script
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