Sun Leaves License Behind
One of the biggest headaches in the Open Source world is the myriad of licenses available , many of which are incompatible with one another. These incompatibilities are troublesome enough between two separate projects, but when multiple licenses are used within the same software, the difficulties grow exponentially. Yesterday was a blow against multiplicity, as Sun decided to do something about it.
The Open Source Initiative lists no less than sixty five licenses certified as Open Source through the Initiative's license review process. These include the ubiquitous GPL and its family of variants, the Apache License, at least BSD licenses, the Mozilla Public License, the MIT license, and a host of lesser-known but nonetheless complicating licenses. The list does not, of course, list the wide range of licenses that have not been reviewed. Attempting to work one's way through them all requires a machete, Tenzing Norgay, and an advance reservation for a padded room.
One project with a proliferation of licenses — though thankfully compatible — is X.org. We count some seventy-six separate licenses in the xorg/xserver's COPYING file, most of which are derivatives of the "standard" license, itself an MIT license. Most derivatives bear roughly the same language along with a single distinguishing feature:
...and that the name of [the copyright holder] not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
That file will soon have one less license, however, as Sun Microsystems' Alan Coopersmith announced yesterday that the company will begin licensing its contributions under the "standard" license, which does not bear the advertising/publicity provision. Further, Sun will re-license all of its prior contributions — some twenty-one years of substantial contribution — under the "standard" licenses, ridding the code entirely of its derivative license.
Coopersmith indicated that more than five hundred files will require editing. He noted, however, that contributors not affiliated with Sun should not change these notices, as the changelogs serve as an official record of the actions taken. In having specifically authorized Sun representatives make the changes, a paper trail of sorts is created, ensuring that any future issues regarding the licensing can be resolved quickly. He went on to say that if anyone has a pressing need for a particular file to be re-licensed posthaste, he can be contacted and will see that it is.
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!
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Interview with Patrick Volkerding
- Parsing an RSS News Feed with a Bash Script
- 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