Novell is loading Microsoft's gun
It is with regret that I urge all FOSS developers to treat anything Novell has contributed to the community as suspect, scrutinize any Novell contributions and purge them as deemed appropriate.
This threat is real, and it is not necessarily contingent upon whether or not Microsoft would actually sue customers for patent infringements. This is a classic case of posturing. Novell is leveraging its agreement with Microsoft in a way that harms all other Linux distributions and other FOSS projects. It is actively exploiting its unique position in ways that seem beneficial, but will pose risks to anyone but its own customers (and even their own customers are only protected for the next five years).
The agreement between Novell and Microsoft started with talks that began supposedly over six months ago. I do not find it coincidental that Novell recently contributed code to introduce Microsoft Excel VBA script compatibility in OpenOffice.org.
This is what I consider to be "loading the gun". With this, and possibly other contributions (especially with respect to but not limited to Mono), Novell is seeding projects with code that may cause anyone but its own customers to fear Microsoft legal action. I urge project leaders and FOSS developers to reject this code.
No doubt some customers will view Microsoft compatibility enhancements as a positive move for Linux. They are not considering the long term consequences of providing compatibility Novell's way. There are other ways to solve the same problems without inserting Microsoft IP into FOSS. A well designed automatic VBA translator would provide the same benefits to OpenOffice.org, for instance, as Novell's VBA patches. The difference is that a translator would not insert Microsoft IP into OpenOffice.org.
Bruce Perens wrote an open letter to Novell. Here is the open letter. I signed the Perens open letter with this comment:
Nicholas Petreley, Editor in Chief, Linux Journal, Freelance writer, analyst and consultant
Note from Nicholas Petreley: I urge everyone to purge their systems of anything related to Novell/SUSE. I also urge all FOSS developers to refuse to adopt anything contributed by Novell (such as the VBA compatibility code in OpenOffice.org). Now that Novell has a virtual license to adopt Microsoft intellectual property without risk to its customers, it is a reasonable fear to assume that everything Novell produces or contributes is potentially tainted with Microsoft intellectual property. This perpetuates a substantial risk to all but Novell customers for the next five years, and may pose a substantial risk to all current FOSS adoption once this current agreement expires. Novell must either reverse its agreement or provide some other acceptable remedy before its products and/or contributions will be anything less than suspect.
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
- Interview with Patrick Volkerding
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Tech Tip: Really Simple HTTP Server with Python
- SuperTuxKart 0.9.2 Released
- 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