Why Novell Must Not Crash and Burn
Not since SCO has there been a company so reviled by the open source community as Novell following its deal with Microsoft. Already there are some clear signs of the negative effects of that anger: senior coders have left the company; Novell has posted a loss for the most recent quarter; and there are calls for a boycott of Novell products – to say nothing of imminent changes to the GNU GPL that might well nullify the entire Novell-Microsoft deal. Some people are rubbing their hands in glee at the thought of Novell crashing and burning completely, but such a development could actually turn out to be one of the worst things to happen to free software.
One reason why Novell has had so much vitriol heaped upon it is that until that deal with Microsoft, it seemed to be a company that really got open source. After clinging on too long to its fading NetWare product – and resisting open standards in the shape of TCP/IP – it started to get serious about open source. In August 2003 it bought Ximian, the company founded by Miguel de Icaza and Nat Friedman, and then the leading European distribution, SuSE, Red Hat's main rival. This seemed to establish Novell as one of the top two open source companies, with good prospects of profiting nicely from the burgeoning business use of free software.
Novell's finest hour was when SCO took the decision in March 2003 to sue IBM:
The SCO Group, the owner of the UNIX operating system, announced today that it has filed legal action against IBM in the State Court of Utah, for misappropriation of trade secrets, tortious interference, unfair competition and breach of contract. The complaint alleges that IBM made concentrated efforts to improperly destroy the economic value of UNIX, particularly UNIX on Intel, to benefit IBM's new Linux services business.
In 1995, SCO purchased the rights and ownership of UNIX and UnixWare that had been originally owned by AT&T. This included source code, source documentation, software development contracts, licenses and other intellectual property that pertained to UNIX-related business. SCO became the successor in interest to the UNIX software licenses originally licensed by AT&T Bell Laboratories to all UNIX distributors, including HP, IBM, Silicon Graphics, Sun Microsystems, and many others.
SCO's action was based on its purchase of “the rights and ownership of UNIX and UnixWare
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
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- 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