Defamation is the “communication to third parties of false statements about a person that injure the reputation of, or deter others from associating with, that person.”
Unfortunately, under the law, you can't be sued for defaming a software license. If I could, I'd sue Microsoft for what it has said about the GPL. Their statements are false and are obviously intended to deter companies from associating with GPL-licensed software—specifically Linux.
The latest onslaught from Redmond came in the “Royalty-Free CIFS Technical Reference License Agreement”, under which Microsoft offers to license its CIFS technical specifications, along with certain of its patents necessary to implement those specifications, on a royalty-free basis. (Read it yourself at msdn.microsoft.com/library/default.asp?url=/library/en-us/dnkerb/html/Finalcifs_LicenseAgrmnt_032802.asp.)
At first I was thrilled to see that Microsoft was willing to license its patents on a royalty-free basis. Members of the Open Source community have long insisted on royalty-free patent licenses for any technology needed for interworking or other standard implementations. But there are so many exclusions and limitations to the CIFS license that this license is useless for anything except Microsoft's propaganda purposes; I can't imagine anyone who will want the CIFS technical specifications under those terms.
For example, the license is limited to implementations on “Non-Microsoft Platforms”. Whoopee! That's how Microsoft stops direct competition at the doorstep so that nobody can write better software to replace any of Microsoft's own software.
It was the insult in the CIFS license that really caught my eye. The CIFS technical specifications and patents are not available for use with software that is distributed under an “IPR Impairing License”. This term is defined as:
...the GNU General Public License, the GNU Lesser/Library General Public License, and any license that requires in any instance that other software distributed with software subject to such license (a) be disclosed and distributed in source code form; (b) be licensed for purposes of making derivative works; or (c) be redistributable at no charge.
So Microsoft again reveals that the only real competition it fears is from Linux and other open-source software.
The term IPR Impairing stands for intellectual property rights impairing. In Microsoft's confused lexicon, the GPL impairs intellectual property rights. Whose? How? Is the impairment good or bad?
There is nothing in the GPL that impairs anyone's intellectual property rights, and it is outrageous for Microsoft to assert otherwise. Anyone can use GPL-licensed software without any effect at all on his or her own intellectual property. For example, you don't have to publish your source code merely by running your software under Linux. You can even modify GPL-licensed code—including Linux—and as long as you don't distribute your modifications you incur no obligation whatsoever to distribute the source code to your modifications. (By way of contrast, don't you dare to reverse-engineer, much less modify, Microsoft code!)
You are not forced to license your software under the GPL and to distribute your source code—except in one rare situation: if you take GPL-licensed software, modify it and distribute your modified version, you must license your modified software under the GPL.
This reciprocity provision is based upon a legitimate bargain. In essence, the licensor is giving you broad rights to his or her software, including the right to create and distribute modifications, but only if you agree to reciprocate by returning your distributed modifications to the commons. You must pay for the right to create and distribute modified software, but the currency for your payment is not money—it is your improved software itself.
How does that differ in principle from the obligation to pay the asking price for Microsoft software?
The owner of GPL-licensed intellectual property is establishing a price for a license to his or her property. You are always free to decide not to make and distribute modifications to GPL-licensed software, but if you elect to do so, you must pay the price set by the owner of the original software. You received a benefit from the free software you modified to create your own software, and the price for that benefit is reciprocity.
That is simply capitalism at its finest. The GPL is not, despite Bill Gates' protestations to the contrary, the end of capitalism as we know it.
What can be far more serious challenges to capitalism are the monopolistic practices that Microsoft continues to engage in. That company pretends it is offering a royalty-free license to CIFS, but the license doesn't apply to implementations on either the Microsoft platform or on the major challenger to that platform, Linux.
Welcome to Microsoft's white elephant sale. I suggest you don't buy.
Legal advice must be provided in the course of an attorney-client relationship specifically with reference to all the facts of a particular situation and the law of your jurisdiction. Even though an attorney wrote this article, the information in this article must not be relied upon as a substitute for obtaining specific legal advice from a licensed attorney.
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Tech Tip: Really Simple HTTP Server with Python
- 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