But, What Will We Do Without SCO?
The saga of SCO v. Linux, known variously as SCO v. Novell, SCO v. IBM, SCO v. Everybody and their Mother, may be coming to a close. Yes, we know this comes as a shock — if anyone needs a moment to compose themselves, or, you know, dig out a case of Dom, we'll wait — but it may well happen faster than any of us ever expected.
The reason for this startling pronouncement dates back to 2007, when on the eve of trial in the Novell litigation, SCO went running into bankruptcy court in Delaware in what was near-universally considered a last ditch effort to stave off their impending doom. It didn't work, however, as the bankruptcy court eventually lifted the automatic stay that prevented the Utah trial from taking place, and when Judge Kimball finally banged his gavel for the last time, SCO had its derrière handed to it to the tune of $2.5 million, plus interest.
Of course, Novell couldn't collect on the judgment, for two reasons. First, SCO appealed the decision, an appeal which was just heard by the Tenth Circuit Court of Appeals yesterday, and if its like any appeal we've ever seen, hairstyles will have changed before we see a ruling. The second reason is by far the stickier one: the bankruptcy. Bankruptcy courts have an almost alarming amount of authority and a reach that would make Stretch Armstrong jealous. Until the bankruptcy court finishes with SCO — and up to now they've been exceedingly lenient with them — nobody is getting anything out of them, except possibly more fabrications and false promises. That's not really true, though — their creditors aren't getting anything out of them, their attorneys, accountants, and heaven knows who else have picked up a cool $3.5 million since the bankruptcy began in 2007.
Why then all the wild pronouncements about SCO going to meet its maker? A certain valiant white knight called the United States Trustee. The trustee is something of the overseer in a bankruptcy case — the court has all the authority, but the trustee figures out how to use it. They generally file and oppose motions to do various things, and in general, watch to make sure everybody is getting a fair deal, both the creditors and the debtors. The U.S. Trustee in the SCO case is one Joseph J. McMahon, and on Tuesday, he filed a motion to convert SCO's Chapter 11 bankruptcy into a Chapter 7 proceeding. What's the difference? Chapter 11, for businesses, is much like a Chapter 13 for individuals — it places the debtor under the protection of the bankruptcy court, preventing their creditors from collecting on debts, judgments, etc. which would put the debtor out of business, for a period sufficient for the debtor to reorganize its affairs and implement a court-approved plan to emerge from the court's protection as a solvent enterprise.
A Chapter 7 is almost exactly the opposite: The court protects the debtor, but it does so not by holding off creditors while the debtor gets it together, but rather by taking possession of most of the debtor's assets, called the bankruptcy estate, liquidating them, and dividing the proceeds between the creditors. Once the dividing has been done — the trustee being the one who takes, sells, divides, and disburses — the debtor is given a discharge, a legally-binding order, valid everywhere in the United States, that all of the debtor's debts (with certain exceptions) have ceased to exist and preventing anyone from attempting to collect on any of these old debts.
For individuals, this in effect provides a fresh start, albeit with seriously damaged credit, for the debtor. Liquidating a business, however, doesn't generally involve a fresh start — it generally involves empty office space and nothing left to call a business. If the trustee is successful, and given the way the relevant law reads, he should be, everything SCO has so desperately been trying to sell in order to feed their litigation habit will instead be sold in order to pay off their creditors — a thought we're sure chills old Darl McBride's cold, black heart right to the core. SCO, of course, says they plan to oppose the motion and present a new reorganization plan, but given the success their previous plans have had, we suspect the effort will be a lot like stretching out chewing gum to stop a 747.
The hard-working guys at Groklaw, as always, have the text of the Trustee's motion along with commentary, as well as the whole lurid story for anyone who has managed to miss the three-ring circus.
Justin Ryan is a Contributing Editor for Linux Journal.
Practical Task Scheduling Deployment
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.View Now!
|The Firebird Project's Firebird Relational Database||Jul 29, 2016|
|Stunnel Security for Oracle||Jul 28, 2016|
|SUSE LLC's SUSE Manager||Jul 21, 2016|
|My +1 Sword of Productivity||Jul 20, 2016|
|Non-Linux FOSS: Caffeine!||Jul 19, 2016|
|Murat Yener and Onur Dundar's Expert Android Studio (Wrox)||Jul 18, 2016|
- Stunnel Security for Oracle
- The Firebird Project's Firebird Relational Database
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- SUSE LLC's SUSE Manager
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Doing for User Space What We Did for Kernel Space
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
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