Open Letter to Jack Powers, Conference Chairman, Enterprise IT Week
Dear Mr. Powers,
I see that you are scheduled to moderate a discussion at the Enterprise IT Week conference after Darl McBride speaks. Although there may be an interesting debate over the merits of free and proprietary software development models, Mr. McBride is hardly a strong representative of the proprietary side.
As Mark Twain's Huckleberry Finn said about King Henry VIII, "S'pose he opened his mouth -- what then? If he didn't shut it up powerful quick he'd lose a lie every time."
Lie: The Berkeley Packet Filter code in Linux is "obfuscated" SCO code.
Fact: Jay Schulist, who never had access to SCO code, implemented it from scratch.
Lie: SCO's 2002 UNIX source release was "non-commercial".
Fact: "The text of the letter, sent January 23, 2002, by Bill Broderick, Director of Licensing Services for Caldera [now SCO], in fact makes no mention of "non-commercial use" restrictions, does not include the words "non-commercial use" anywhere and specifically mentions "32-bit 32V Unix" as well as the 16-bit versions."
Lie: SCO's expert witnesses are "MIT Mathematicians".
Fact: "The SCO Group of Utah has had to backtrack after saying that MIT mathematicians verified its claims that Linux, the center of the popular and freely-available GNU/Linux operating system, is an illegal knock-off."
Lie: SCO owns all rights to UNIX concepts and methods.
Fact: McBride cited parts of IBM's UNIX license out of context. The license also includes this text:
Nothing in this agreement shall prevent LICENSEE from developing or marketing products or services employing ideas, concepts, know-how or techniques relating to data processing embodied in SOFTWARE PRODUCTS subject to this Agreement, provided that LICENSEE shall not copy any code from such SOFTWARE PRODUCTS into any such product or in connection with such service and employees of LICENSEE shall not refer to the physical documents and materials comprising SOFTWARE PRODUCTS subject to this agreement when they are developing any such products or service or providing any such service.
Fact: "Obviously Linux owes its heritage to UNIX, but not its code."
Lie: "We would not, nor will not, make such a claim."
As is clear from the growing torrent of corporate purchase orders and investments flowing to Linux, Mr. McBride's outlandish claims are completely outside the mainstream of the IT industry. Mr. McBride's legal shenanigans have little to do with real-world software development and everything to do with making a quick exit from a failed company.
I would like to encourage you to read some of the background information on Mr. McBride's scheme located at sco.iwethey.org and groklaw.net. Both sites have extensive links to SEC filings, court papers and other primary sources.
If you would like a demonstration of how unlikely we in mainstream IT believe Mr. McBride is to succeed in his shakedown, I offer to walk on stage and sell you a copy of Linux for one dollar and give you a signed receipt, in front of Mr. McBride. Please let me know if you're interested.
Don Marti is Editor in Chief of 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!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Rogue Wave Software's Zend Server
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