SCO Will Try Again
The internet is alive with the sound of screaming this week, as everyone and their brother rushes to announce the Tenth Circuit Court of Appeals ruling on SCO's appeal of the U.S. District Court's decision in its case against Novell. To hear some tell it, SCO has emerged triumphant, Novell is vanquished, darkness shall reign in the whole of the land, and male pattern baldness will engulf us all.
Reports of the Court of Appeals ruling have been wide and varied in their interpretations. While your editor is missing the hair on the back of his head, it is most surely not a result of mass SCO-ruling induced baldness, nor will anyone be forced to read this via candlelight due to the blackening out of the sun. While we've not yet had the opportunity to review the full decision in depth — it's fifty-four pages of beautiful legalese, if you're feeling adventurous and/or suicidal — there are a few things that are clear.
First, it is true: The Court of Appeals reversed some of the District Court's findings. They did not decide SCO was right, they did not rule that Novell was wrong, they didn't answer any of the material questions of the case, and they didn't sentence Judge Kimball to death. What they did do was to hold that certain issues the District Court ruled on should not have been decided by the Court on its own. Some background on the process is helpful in understanding just what went on.
One of the most important distinctions between courts in the United States (and many other countries as well) is the distinction between trial courts and appellate courts. While both are courts, and both are run by judges in black robes — or if they're really special, like the Supremes, Justices — they don't provide the same function. Trial courts take evidence, determine facts, and rule on points of law relevant to the matter at hand. Their scope is quite wide — they generally will hear and rule on any aspect of the case that presents itself, regardless of how it comes up.
Appellate courts don't take evidence — there are no witnesses when the Supreme Court sits — they don't determine facts, and they don't hear a wide scope of matters. The appellate court hears only questions of law specifically brought to it by the parties, and then only if it relates to a matter originally raised at trial. They base their decision entirely on the arguments presented by the parties in the form of legal briefs (and oral arguments, if there are any) and the certified record sent by the trial court. Their only function is to determine whether the law was correctly applied — they don't decide who was right or wrong, or whether or not Colonel Mustard was in the library with the candlestick, only whether the trial court followed the law and ensured that everyone else knew what it says.
Even more important than the distinction between trial and appellate courts is the distinction between judges and juries. Extremely simplified, there are three things taking place during trial (often they are enumerated as such in the court's orders): determining facts, drawing conclusions from the law, and issuing a judgment. Determining facts is the exclusive province of the jury: once the jury has determined a state of facts, it is binding on the court. The judge's responsibility is to determine matters of law, to properly instruct the jury in the applicable law, and once the jury has returned its findings, to issue a judgment in accordance with those findings and the law from which they flow. (The jury may be involved in the judgment process as well, by recommending a sentence or an amount for damages, but it is the judge's role to make the final decision.)
When there is no jury, then the judge becomes the finder of fact and the concluder of law. Additionally, if the court can be convinced that there is no reasonable chance for one side to successfully prevail on a matter of fact, it can issue a summary judgment that decides the issue without actually holding a trial or empaneling a jury. These decisions are highly popular and highly unpopular at the same time. The courts favor them because trials are expensive and take inordinate amounts of time, time that the overwhelmed court system just doesn't have. They are unpopular, however, particularly on appeal, because they bypass the trial process — having ones day in court — and if used where the facts are not overwhelmingly clear, deny the parties their right to a fair trial.
In SCO v. Novell, Judge Kimball issued a series of summary judgments determining various matters in contention before the trial took place. (In fact, it wasn't long after his ruling that SCO filed for bankruptcy.) Among the the matters decided by summary judgment was the issue of who owns the Unix copyrights that SCO claims it never sold to Novell. The court determined, without a trial and without a jury, that Novell owned the copyrights, and when the remainder of the matter was tried, it was tried in light of that determination. SCO, obviously, wasn't pleased, and appealed the matter to the Court of Appeals, arguing that the summary judgment was inappropriate.
Inappropriate is an important word here — if perhaps not the one the court itself would have used — because the Court of Appeals ruling did not decide that the judgment was incorrect in itself, that is, that Novell doesn't own the copyrights and SCO does. What the court decided was that it was inappropriate for Judge Kimball to issue a summary judgment on the matter — the Court of Appeals felt that, based on the record before it, that matter was too complex to meet the standard for a summary judgment. As such, the court reversed the summary judgment and remanded the matter — that is, they sent it back to the trial court with the order to hold a jury trial and let the jury decide who owns the copyrights.
That's it — no great victory, no sweeping darkness, no mass vanishing of follicles. Just the decision that Judge Kimball shouldn't have decided for himself and the instruction to ask a jury. Interestingly enough, the court upheld the other matter SCO appealed — the $2.5 million judgment against it. So, now all that remains is to hold that trial, and Big Bad Darl — McBride, CEO of SCO — is vowing to fight to the death against the "knock off of our Unix." Except...
Darl seems to have forgotten that he's a corporate eunuch at this point — his business card may say "C.E.O." but he lacks any P.O.W.E.R. That's because he and his cohorts thought the Bankruptcy Court system was a good way to avoid paying their creditors until they could come up with a new evil plan — unfortunately, while they they were working on their evil plan, they failed to come up with a reorganization plan, and landed themselves in hot water with the Bankruptcy Court. As we reported a few weeks ago, SCO's management is no longer in control of the company, as the Bankruptcy Court has ordered that a trustee be appointed to run SCO's affairs.
Having a trustee appointed isn't like getting a receptionist — he or she doesn't sit at the front door and answer your calls while you come up with new ways to destroy the company. The trustee becomes the management, and gets to decide how to run the company, including whether or not to continue suicidal suing. The Court of Appeals ruling says that a new trial should be held, but that is contingent on a) SCO (i.e., the trustee) pursing the matter, and b) the Bankruptcy Court allowing it. As those who have been following the SCO case for some time will remember, when a party is in bankruptcy, there is an automatic stay on all litigation — the only way any court can hear any matter related to the party is with permission of the Bankruptcy Court. No permission, no trial.
At this point, there are at least three significant bars to SCO seeing anything resembling a victory. First, the trustee will have to be convinced that the lawsuit a) actually has any merit to it whatsoever, and b) could actually be won. (All the Court of Appeals ruled was that a jury should make the decision, not that SCO has a chance of purple cows giving Pepsi.) The trustee's job isn't at all to do what SCO's management wants, and isn't just to do what's in the best interests of SCO actually emerging solvent from bankruptcy — it's also to protect the creditor's ability to recover what they are owed. That means the trustee won't be going on a fishing expedition with the Novell/IBM cases — if it's not got a good chance of winning, the trustee won't waste the estate's resources on it.
Second, the Bankruptcy Court will have to be convinced to lift the stay on the litigation. Even if SCO manages to drug, brainwash, and/or torture the trustee into going on with the cases, they'll have to talk the Bankruptcy Court judge into it too — a judge who has figured them out and is tired of their antics. Lifting the automatic stay on litigation is what might be termed an extraordinary remedy — the judge isn't going to do it just because he's grumpy that his cornflakes were soggy at breakfast.
Finally, the biggest hurdle for SCO is what the whole appeal was about: the jury. Twelve ordinary people, with little or no legal training, potentially without any understanding of technology at all, are going to have to be convinced that the hundreds and hundreds of pages of sale agreements don't include selling the Unix copyrights in question. Judge Kimball was described as having great trouble clarifying all the details, so getting it across to a jury isn't going to be easy. It'll be particularly difficult if, like last time, Darl swears things on the stand that other executives have denied — minutes before, under oath. And as we said almost a year ago, if it does go back to trial, Novell has a whole host of issues it can reinstate.
For now, we're firmly planted in our seats waiting to see what happens — though we may run out for a toupée at some point. As for the Court of Appeals ruling, to quote ourselves: Final order? Yes. Final chapter? Not even close.
Justin Ryan is a Contributing Editor for Linux Journal.
|Designing Electronics with Linux||May 22, 2013|
|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|
- New Products
- Linux Systems Administrator
- Senior Perl Developer
- Technical Support Rep
- UX Designer
- Designing Electronics with Linux
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Reply to comment | Linux Journal
3 hours 14 min ago
- Reply to comment | Linux Journal
3 hours 30 min ago
- Favorite (and easily brute-forced) pw's
5 hours 21 min ago
- Have you tried Boxen? It's a
11 hours 13 min ago
- seo services in india
15 hours 44 min ago
- For KDE install kio-mtp
15 hours 45 min ago
- Evernote is much more...
17 hours 45 min ago
- Reply to comment | Linux Journal
1 day 2 hours ago
- Dynamic DNS
1 day 3 hours ago
- Reply to comment | Linux Journal
1 day 4 hours 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?