SCO is Back, and This Time It's Personal
We all thought it was time to party, that the enemy was finally vanquished, that it was time for Champagne and cigars. We learned our lesson yesterday afternoon, though, when SCO smacked us all in the face with a hundred million dollars.
That's right, SCO suddenly has deep pockets, courtesy of their friend Stephen Norris, the uber-finance geek. Norris and his private equity firm — Stephen Norris Capital Partners, LLC — have decided to buy a stake in SCO, though the exact amount won't be clear until the Utah courts decide how much SCO has to pay IBM and Novell. What is clear is that they suddenly have a $95 million line-of-credit to pursue all the litigation their cold, black hearts desire. Others have pointed out that these guys are the biggest, baddest, beat-the-crap-out-of-anyone-in-their-way-ist, and won't have a moment's pause about coming after everyone in the Linux world, from IBM and Novell right down to us, the everyday users.
As the ever-vigilant White Knights over at Groklaw point out, there's still some hope — the all-powerful Bankruptcy court can quash them with the stroke of a pen, and the European Commission not to mention the SEC may well have a thing or two to say — but the outlook certainly isn't as rosy as it was on Wednesday.
Lord have mercy...
Justin Ryan is a Contributing Editor for Linux Journal.
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!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- 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