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.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Keeping track of IP address
42 min 5 sec ago
- Roll your own dynamic dns
5 hours 55 min ago
- Please correct the URL for Salt Stack's web site
9 hours 6 min ago
- Android is Linux -- why no better inter-operation
11 hours 22 min ago
- Connecting Android device to desktop Linux via USB
11 hours 50 min ago
- Find new cell phone and tablet pc
12 hours 48 min ago
14 hours 17 min ago
- Automatically updating Guest Additions
15 hours 26 min ago
- I like your topic on android
16 hours 12 min ago
- This is the easiest tutorial
22 hours 48 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?