Telling Lies: ESR on Microsoft
At www.suntimes.com/output/tech/cst-fin-micro01.html, Steve Ballmer of Microsoft answered this question:
Q: Do you view Linux and the open-source movement as a threat to Microsoft?
A: “Yeah. It's good competition. It will force us to be innovative. It will force us to justify the prices and value that we deliver. And that's only healthy. The only thing we have a problem with is when the government funds open-source work. Government funding should be for work that is available to everybody. Open source is not available to commercial companies. The way the license is written, if you use any open-source software, you have to make the rest of your software open source. If the government wants to put something in the public domain, it should. Linux is not in the public domain. Linux is a cancer that attaches itself in an intellectual property sense to everything it touches. That's the way that the license works.”
Let's examine the key sentences:
* Open source is not available to commercial companies.
The last I checked, Red Hat Software, VA Linux Systems, IBM, SGI, and Hewlett-Packard were all “commercial companies”.
I wonder what the developers at Microsoft who based the Internet protocol code of Windows on the open-source Berkeley TCP/IP stack think of this assertion?
* The way the license is written, if you use any open-source software, you have to make the rest of your software open source.
60% of the world uses the open-source Apache program to serve their web pages. The next time you hear of Apache use forcing anybody's software open will be the first.
* If the government wants to put something in the public domain, it should. Linux is not in the public domain.
True. Of course, “the government” doesn't own Linux and has very little to do with Linux development, so it's hard to see what Ballmer is recommending here.
* Linux is a cancer that attaches itself in an intellectual property sense to everything it touches.
Lots of people have proprietary software and data on their Linux machines. The next time you hear of Linux “attaching” itself to any of this data and forcing it open will be the first.
* That's the way that the license works.
The GPL infects only derivative works of GPLed software -- you have to include part of the source code of a GPLed program in your program, or choose to link to a GPLed library, before the GPL applies to your code. You can use a Linux kernel and Linux-hosted programs all you like with never a worry about your intellectual property.
Other open-source licenses—such as the BSD license in the TCP/IP stack that Microsoft adapted for Windows—will never infect anybody's code or data, because they're designed not to. But Ballmer wants business people and the public to fear them all, because only if open source is general is discredited will Microsoft maintain its monopoly.
The Big Lie is a term originally coined to describe a characteristic form of Nazi (and later Soviet) propaganda. The essence of the Big Lie propaganda technique is that if you repeat the lie often enough over enough channels, people will soak it up through their pores and come to believe it as something “everybody knows”.
In the last three months, Jim Allchin and Craig Mundie and Steve Ballmer have launched a classic Big Lie campaign against open source. They have described it as “un-American”, “a destroyer”, and “a cancer”. They have deliberately confused the GPL with non-infectious open-source licenses, and they have deliberately confused active combination of code with passive aggregation of data. They have lied, and lied, and lied again.
Why? Because the most truthful thing Ballmer admitted in that interview is that yeah, Linux *is* a threat to Microsoft. It threatens to break Microsoft's 91% monopoly on personal-computer operating systems. It threatens to free consumers from proprietary lock-in, and to deliver better software and more choices at lower cost.
Two years ago, the Halloween Documents observed that in order to defeat the threat of open source, Microsoft must attack “a process, not a company”. That is exactly what Allchin and Mundie and Ballmer are doing now, attacking with a Big Lie software they know they cannot match in reliability, sophistication, security, and overall cost/benefit ratio.
In the open-source community, we have a favorite quote from Mohandas Gandhi: “First they ignore you. Then they laugh at you. Then they fight you. Then you win.”
Evidently, we're getting close to winning.
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
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Interview with Patrick Volkerding
- 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