Skip to main content

IBM to Buy Red Hat, the Top Linux Distributor, for $34 Billion

IBM is making a big move to bring more software developers under its wing by acquiring Red Hat, the largest distributor of the popular open-source operating system Linux, for $34 billion.
The purchase, announced on Sunday afternoon, is the latest competitive step among large business-software companies seeking an edge in the fast-growing market for cloud computing.
In June, Microsoft acquired GitHub, a major code-sharing platform for software developers, for $7.5 billion.
With the deal for Red Hat, IBM is trying to position itself as a kind of corporate “Switzerland” in cloud computing — a trusted partner of businesses that are moving to the cloud, but are leery of becoming dependent on one major cloud supplier.
In the cloud model, software developers write applications that run on remote data centers. The advantage can be lower costs and faster development of new business software.
IBM is a champion of a hybrid approach to cloud computing. That means some crucial data and applications run on cloud technology inside a company’s data centers, while other computing tasks run on the clouds of tech companies.
The major third-party cloud platforms are Amazon, Microsoft and Google. Businesses complain that these cloud suppliers include proprietary technology that makes it difficult to switch from one cloud to another.
The IBM cloud strategy is to supply both hardware and software for companies to build their own private clouds, and it also has a third-party public cloud offering.
IBM, analysts say, cannot really compete broadly with so-called hyperscale cloud companies — Amazon, Microsoft and Google — which tap their deep coffers to spend many billions of dollars a year to build more giant data centers.
But IBM and Red Hat say they are well placed to be leaders in helping corporations make the transition to cloud computing without getting locked into the technology of an internet giant.
The two companies say they plan to offer the technology to link a company’s in-house cloud and multiple third-party clouds.
“Enterprises are moving to the cloud but 80 percent of them are not there yet,” said Arvind Krishna, an IBM senior vice president in charge of its hybrid cloud offerings. “We can provide a much easier path to manage and make secure both private clouds and links to multiple public clouds.”
Red Hat, founded in 1993 and based in Raleigh, N.C., has built a profitable business, with $2.4 billion in revenue last year, around open-source software, mainly Linux. Open-source code is distributed free, and can be modified by far-flung programmers, under certain rules.
Red Hat has expanded — and made money — by offering technical support, quality control, software tools and a forum for collaboration, charging subscription fees.
Linux is the preferred operating system for cloud computing. “For most corporations, hybrid cloud is the only practical way to the cloud,” said Paul Cormier, president for products and technologies at Red Hat.
The link with IBM, Mr. Cormier said, will accelerate Red Hat’s progress in the market for corporate cloud migrations.
Red Hat will join IBM’s cloud team, the companies said in a joint statement, but as a “distinct unit” to preserve its independence and neutrality in open-source development.
IBM’s offer of $190 a share in cash is more than a 60 percent premium over Red Hat’s closing price on Friday, $116.68 a share.
The hefty price tag, said one person close to the deal, who asked not be to identified because he was not authorized to speak publicly, is justified by Red Hat’s growth and strong cash flow.
IBM, he said, is paying about 30 times Red Hat’s free cash flow, well below the average for recent software company acquisitions, and it will help lift IBM’s growth and cash flow.
The boards of both companies approved the deal, and the sale is expected to close in the second half of next year. Goldman Sachs, JPMorgan Chase and Lazard advised IBM on the deal, and Guggenheim Partners and Morgan Stanley advised Red Hat.

Comments

Popular posts from this blog

OWASP Top 10 Threats and Mitigations Exam - Single Select

Last updated 4 Aug 11 Course Title: OWASP Top 10 Threats and Mitigation Exam Questions - Single Select 1) Which of the following consequences is most likely to occur due to an injection attack? Spoofing Cross-site request forgery Denial of service   Correct Insecure direct object references 2) Your application is created using a language that does not support a clear distinction between code and data. Which vulnerability is most likely to occur in your application? Injection   Correct Insecure direct object references Failure to restrict URL access Insufficient transport layer protection 3) Which of the following scenarios is most likely to cause an injection attack? Unvalidated input is embedded in an instruction stream.   Correct Unvalidated input can be distinguished from valid instructions. A Web application does not validate a client’s access to a resource. A Web action performs an operation on behalf of the user without checking a shared sec

CKA Simulator Kubernetes 1.22

  https://killer.sh Pre Setup Once you've gained access to your terminal it might be wise to spend ~1 minute to setup your environment. You could set these: alias k = kubectl                         # will already be pre-configured export do = "--dry-run=client -o yaml"     # k get pod x $do export now = "--force --grace-period 0"   # k delete pod x $now Vim To make vim use 2 spaces for a tab edit ~/.vimrc to contain: set tabstop=2 set expandtab set shiftwidth=2 More setup suggestions are in the tips section .     Question 1 | Contexts Task weight: 1%   You have access to multiple clusters from your main terminal through kubectl contexts. Write all those context names into /opt/course/1/contexts . Next write a command to display the current context into /opt/course/1/context_default_kubectl.sh , the command should use kubectl . Finally write a second command doing the same thing into /opt/course/1/context_default_no_kubectl.sh , but without the use of k

标 题: 关于Daniel Guo 律师

发信人: q123452017 (水天一色), 信区: I140 标  题: 关于Daniel Guo 律师 关键字: Daniel Guo 发信站: BBS 未名空间站 (Thu Apr 26 02:11:35 2018, 美东) 这些是lz根据亲身经历在 Immigration版上发的帖以及一些关于Daniel Guo 律师的回 帖,希望大家不要被一些马甲帖广告帖所骗,慎重考虑选择律师。 WG 和Guo两家律师对比 1. fully refund的合约上的区别 wegreened家是case不过只要第二次没有file就可以fully refund。郭家是要两次case 没过才给refund,而且只要第二次pl draft好律师就可以不退任何律师费。 2. 回信速度 wegreened家一般24小时内回信。郭律师是在可以快速回复的时候才回复很快,对于需 要时间回复或者是不愿意给出确切答复的时候就回复的比较慢。 比如:lz问过郭律师他们律所在nsc区域最近eb1a的通过率,大家也知道nsc现在杀手如 云,但是郭律师过了两天只回复说让秘书update最近的case然后去网页上查,但是上面 并没有写明tsc还是nsc。 lz还问过郭律师关于准备ps (他要求的文件)的一些问题,模版上有的东西不是很清 楚,但是他一般就是把模版上的东西再copy一遍发过来。 3. 材料区别 (推荐信) 因为我只收到郭律师写的推荐信,所以可以比下两家推荐信 wegreened家推荐信写的比较长,而且每封推荐信会用不同的语气和风格,会包含lz写 的research summary里面的某个方面 郭家四封推荐信都是一个格式,一种语气,连地址,信的称呼都是一样的,怎么看四封 推荐信都是同一个人写出来的。套路基本都是第一段目的,第二段介绍推荐人,第三段 某篇或几篇文章的abstract,最后结论 4. 前期材料准备 wegreened家要按照他们的模版准备一个十几页的research summary。 郭律师在签约之前说的是只需要准备五页左右的summary,但是在lz签完约收到推荐信 ,郭律师又发来一个很长的ps要lz自己填,而且和pl的格式基本差不多。 总结下来,申请自己上心最重要。但是如果选律师,lz更倾向于wegreened,