The news caught everyone by surprise. Hewlett-Packard was buying Compaq for $25 billion (US) in stock. After both stocks were hit the next day, the deal was worth about $20 billion—even though the announcement boasted that the combined company “Will Have Number One Worldwide Positions In Servers, PCs and Hand-helds, and Imaging and Printing; Leading Positions In IT Services, Storage, Management Software.”
The numbers involved were staggering. Combined revenues exceeded $87 billion over the past four quarters, which would place the new HP second only to IBM ($90 billion) in size. The new behemoth would also have 145,000 employees in 160 countries—prior to staff cuts, which are sure to come mostly at Compaq's expense. If the deal goes through, Compaq as a company will only persist, in the manner of Netscape after AOL, as a “brand”. Together HP and Compaq brands account for about 70% of PC sales through retail outlets; but Dell now leads in sales overall, having moved ahead of both HP and Compaq. This, pundits mostly agreed, was clearly one strong motive for the deal.
Reviews in the mainstream media were mixed at best. Dan Gillmor of the San Jose Mercury News wrote, “It's hardly thrilling to be the leader in a market that is dull, nearly devoid of innovation and barely profitable.” In the UK, The Register wrote:
A braver choice for HP would have been to prise its way into new infrastructure partnerships, swallowing a Nokia or a Nortel. Or even an ARM. But instead of looking forward, HP has looked back and fallen on an acquisition target that looks agreeably like itself only financially weaker.
But in the Linux community, the mood was more upbeat. Linuxcare cofounder Dave Sifry said, “Gee, everyone said that there'd be consolidation in the Linux space, but this is a bit bigger than I expected!”
Dan Kusnetsky, VP System Software for International Data Corp. and one of the leading Linux analysts, says:
In the recent past both companies have been looking for ways to lower their overall software development costs by moving to high-volume, third-party software. This is quite reasonable. It is quite expensive to be a world-class supplier of operating systems.
He adds that the combined company would be supporting as many as eight different OSes, and offers these predictions: 1) since Tru64 UNIX is the lower-volume product and is tied to Alpha, the best features of Tru64 UNIX will be merged into HP-UX and Linux, and then Tru64 UNIX will be retired; 2) the best features of OpenVMS and MPE/ix will be merged into Windows and then one or both of those operating systems will be retired; and 3) the combined company will focus on HP-UX for high-end enterprise tasks, Windows for workgroup and desktop tasks, and Linux for Web-centric computing tasks.
Which isn't exactly bad news for Linux.
Doc Searls is Senior Editor of 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
- 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
- Interview with Patrick Volkerding
- Parsing an RSS News Feed with a Bash Script
- 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