Geeks on Bikes: The SCO Group/Caldera Product Development Plan
Yesterday, I wrote about some initial reactions I had to the announcement that Caldera had changed its name to The SCO Group. Today, I'm going to explore some of the repercussions of the announcement.
The change by Caldera to leverage the SCO brand and SCO products has a sound foundation but some short-term problems. These problems revolve around the fact that neither Caldera nor device manufacturers are spending much in the way of resources to support SCO Open Server or UnixWare products. The bottom-line is it's an old OS. It's going to take time for the new SCO Group to re-assess and then come out with a new version of the main SCO products. So, what does a company do to get its channel re-invigorated and its house in order?
Well, if you are Darl McBride, the new CEO of The SCO Group, you use Harley-Davidson as a model. The famed maker of road bikes fell on hard times after being sold to AMF. H-D management and some of the old Harley family bought back the company in 1980, but they faced a tough battle to save the company and the brand.
Darl has adopted a business resurrection model similar in many ways to the one used by the H-D team: generate revenue from the brand, improve the core product and be more responsive to the needs of the people who sell your product and the people who buy your product. Simple concepts, but they're harder to do than they sound.
Harley launched their corporate resurrection with the surprising step of creative licensing and announced a brand name based primarily on clothing. The SCO Group does not have this type of opportunity, but they do have a significant wealth of intellectual property. McBride was at Novell when they purchased SCO/AT&T Unix for a little over a billion dollars. A few years later, Caldera purchased SCO from Novell for a little over $100 million. "In theory", stated McBride, "there should be some value to that property--somewhere between a million and a billion [dollars], right? I just wanted to know what real, tangible intellectual property value the company held."
The then-Caldera legal team was appointed the task of coming up with a review of the history of Caldera's intellectual properties and their status. The review turned up a stack of license agreements that had gone uncollected for years. To date (remember, McBride has been on board as CEO for only a few weeks), Caldera has already come to agreements with holders of these old licenses that will generate $600,000 in recurring revenue.
The intellectual property fishing expedition has provided The SCO Group with the legal due diligence to now lay claim to UNIX itself. According to Opinder Bawa, new Senior VP of Technology, "we own the source to UNIX; it's that simple. If we own the source, we are entitled to collect the agreed license fees."
To my fellow folk in the Linux community, you need not fear. I specifically asked if, in making that broad a statement about UNIX, The SCO Group was making any legal claim to Linux. According to McBride, "obviously Linux owes its heritage to UNIX, but not its code. We would not, nor will not, make such a claim."
So while the legal team is working on new intellectual property revenue streams, what is going with regards to improving the core product? That is a tougher subject, one that, like re-engineering the Harley motor, will take time. What does the new SCO Group intend to do in the meantime to pump up the troops? What else--they're starting a dot-com business.
This move both makes sense and is a huge gamble. The core of this new business is a service called SCO BIZ, a partnership with Vista.com and their e-commerce development platform. It will put a product into SCO dealers' hands that allows them to offer an ASP/VSP service to their clients and potential clients. The concept is the e-commerce engine is capable of harvesting data from an existing SCO Open Server product, allowing the dealer to sell a new service to an existing client. With the new version of SCO Open Server being released in the fourth quarter of 2002, the service will be an aid in selling new SCO products.
But are people even considering buying SCO as a new or replacement solution? According to financial information released this week, this past quarter was the first up-tick in sales for SCO in the last five quarters. So, yes, customers will buy new SCO products because of their reliability. But, the jury is still out regarding the numbers in which they will come to buy the product.
The risk is significant. Dozens, maybe hundreds, of ASP-style services already are selling very good e-commerce solutions on the Internet. Even with a high quality, already successful partner such as Vista.Com, it remains to be seen if this gamble will work or if it will dilute the existing efforts of their dealer group.
It should be noted that The SCO Group is not making this service offering without analysis. This kind of service is exactly what the channel partners have been asking for as a tool. The SCO channel must not have experienced (suffered from) the dot-com bust.
Jeff Gerhardt is the host of The Linux Show.
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
- Google's SwiftShader Released
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Interview with Patrick Volkerding
- Doing for User Space What We Did for Kernel Space
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