Oracle Delivers Friday the 13th Bad Luck to FOSS
Despite personal beliefs, everybody treads a bit more carefully on Friday the 13th. But no amount of precaution could protect the Open Source community from the wave of bad luck that fell last Friday. Oracle finally lived up to the fears many have been afraid to speak.
The day began with the news that Oracle filed a lawsuit against Google for using code that allegedly infringes upon patents related to Java in their Android operating system. Many speculate the purpose is to cash in on some of money that Google is apparently making from the popular mobile system. They are goading Google into a nice settlement check and who could deliver larger? Oracle has always been about making money and they didn't buy Sun's Open Source assets for nothing. Not that Sun was making that much from Java, but speculation is that Oracle lawyers must have seen future patent litigation as another source of income for the behemoth. Others think Oracle is rightfully defending Java GPL requirements. This wouldn't be the first time Google has tried to sidestep some Open Source compliance with Android.
On the very same day news leaked that Oracle had shut down OpenSolaris. In another blow to Open Source, Oracle decided that Solaris should be unique and providing a freely downloadable version negates that. OpenSolaris also just might represent competition as a few struggling businesses opt for OpenSolaris instead of Solaris during these continuing financially challenging times.
Experts knew there was trouble ahead with the news of Oracle's acquisition of Sun. Monty Widenius fought against it, but Oracle gobbled Sun MySQL up with the rest. He predicted future issues and began forking MySQL before the ink was dry on the contracts. Most recently, Garrett D'Amore et al. based a new system on OpenSolaris, and said a full fork may be necessary if Oracle shutdown OpenSolaris development. It appears necessary now.
One has to wonder what may be in store for MySQL and OpenOffice.org. These two major mainstays for Linux and Open Source would be sorely missed. MySQL is commercial, but Oracle could very well stop the free older version availability under the same premise as used in axing OpenSolaris. It's quite possible Oracle may very well kill MySQL as competition to the lucrative but shrinking Oracle database market. Oracle could just choose to stop funding OpenOffice.org as well, virtually signing the death warrant for a piece of software almost every Linux user requires.
No one is really surprised. Oracle has always been a proprietary company. But Oracle's actions of Friday the 13th come only days after offering up a keynote at LinuxCon. This hits after last year's promises of no major changes in Sun's open source community assets. Those hoping for a new soft and fuzzy Oracle are no doubt sorely disappointed. Experts have already stated Oracle could turn out to be more of threat to Linux and Open Source than either Microsoft or SCO ever was.
Susan Linton is a Linux writer and the owner of tuxmachines.org.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- SuperTuxKart 0.9.2 Released
- 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