IBM Lets Sun Set
Reports surfaced late this evening that computing giant IBM — which has been in talks for some time to buy Sun Microsystems — has pulled its $7 billion offer to buy the struggling company.
According to reports, IBM withdrew the offer after Sun's Board of Directors made "onerous" requests following IBM's decision to lower its offer for the firm. IBM initially offered $9.55 per share, but dropped that offer to $9.40 — less than a $1.00 premium on Sun's current stock price — due in part, it says, to the discovery that far more senior employees than originally expected are covered by "change of control" contracts. Such agreements cover senior executives — who often face replacement on acquisition — should the company be bought or otherwise come under the control of someone other than its Board.
Sun's Board, according to anonymous sources close to the negotiations, was worried about parts of the deal that would limit IBM's ability to pull out of the agreement — presumably, these concerns were the "onerous" guarantees which led to the breakdown. However, IBM's decision to walk — which terminates a contract between the two stipulating that no other deal would be pursued during the course of their talks — may prove a benefit for Sun, as it is now able to seek out deals with other companies, including IBM's rivals.
It is possible that IBM's decision is merely a tactical move, intended to scare Sun's Board into agreeing to the deal without any "onerous" provisos. If Sun seizes the opportunity to offer itself to IBM's arch-rivals, however, it may well be IBM that is scared into agreement, for fear of what its competitors would do should they acquire Sun instead. Indeed, the tactic may work doubly, initially motivating IBM's rivals to pursue a purchase — at a much better premium, of course — in the desire to prevent IBM from doing so, before forcing IBM back to the table.
Of course, it's also entirely possible that IBM has genuinely lost interest, and it could prove devastating to Sun if it turns out those IBM rivals never had any interest to begin with.
Justin Ryan is a Contributing Editor for 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!
- Stunnel Security for Oracle
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- My +1 Sword of Productivity
- SUSE LLC's SUSE Manager
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- SuperTuxKart 0.9.2 Released
- Google's SwiftShader Released
- Non-Linux FOSS: Caffeine!
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