SCO v. Novell is Final – For Now
Way back in July, the word rang out that SCO — the arch-villains bent on squeezing every dime they can out of Linux — had been vanquished by the valiant legal team at Novell to the tune of $2.5+ million. Now comes word that the victory is final — or at least, as final as can be expected.
The SCO v. Novell saga has been ongoing since 2002 — though we suspect most of the long-time Linux crowd would swear it's been forever — and was due to be wrapped up last year. Of course, that came screeching to a halt when SCO filed for bankruptcy — just days before trial — and all outstanding litigation was automatically stayed by the Bankruptcy Court. One cannot stay forever, though, and the bar was eventually lifted, allowing for the April/May showdown in Utah from which Judge Dale Kimball's July smackdown was to come.
The law is a funny thing, though, and courts are even funnier, particularly when there are this many jokers involved. SCO say they want to appeal, but you can't appeal judgment until you have a final order — and that's just what Judge Kimball handed down yesterday. It's an interesting read to be sure — as expected, the ruling handed down last August is incorporated, as is the decision from July, pre/post-judgment interest has been determined and the constructive trust settled. Also included, though, are voluntary dismissals by both sides: Novell agreed to drop certain claims for Slander of Title, Breach of Contract, and a request for Declaratory Relief, while SCO passed on Breach of Contract, Copyright Infringement, and Unfair Competition.
What's even more interesting, however, is the language used in the dismissal. In Novell's case, the court orders that the claims are voluntarily dismissed with the right to resurrect them if there is any further activity in the case. SCO's claims, however, are dismissed with prejudice, legalese — roughly equivalent to Monty Python's Dead Parrot sketch — meaning they're prevented from bringing the matter back up. Indeed, the judge even went so far as to spell it out for them: "are voluntarily dismissed with prejudice, without the possibility of renewal following appeal."
What does it all mean? If SCO appeals, they may get the whole thing sent back to Utah for another trial. If so, they can re-try whatever the Appeals Court says should be retried, but they won't be able to tack on the claims they agreed to dismiss this go-round. However, if Novell finds itself back in the courtroom — and it's important to note, only if it's part of this specific case — they can bring back all the claims they agreed to dismiss, something for SCO to think about when they're deciding where to go.
Of course, like everything in this case, it's all subject to change — the Appeals Court could, should they find a reason to, vacate the dismissal conditions, allowing SCO to bring them back anyway. They could, with cause, remand specific parts of the case for a new trial with the stipulation that no other aspects be heard, preventing Novell from resurrecting their claims. Once the appeals have been heard — don't forget, there's still another court above the Tenth Circuit, and any new trial would mean fresh fodder for a whole new round of appeals — there is still the Bankruptcy Court, which holds all the cards, and could spawn its own set of appeals to the District Court, the Third Circuit, and — heaven forbid — even the Supremes.
Final order? Yes. Final chapter? Not even close.
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
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- 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
- SourceClear Open
- 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