Yeah - timeline runs like this. April 13th...(in your article) "For a long time, it was thought that we'd just merge the Xen patches as-is and be happy. But then, Linux would only run on Xen," Morton said. Instead, VMware programmers suggested a documented, stable interface between the kernel and the hypervisor--and they're preparing one, he said."
"From a high-level design perspective, I think that VMware's point is a good one, and that a general kernel-to-virtual machine interface is a better thing than a Xen-only one," Morton said.
XenSource and VMware both are fine with the change, but VMware gets a place at the table it lacked before. "
July 18th - XenSource and MS announce a partnership.
August 1st - Big discussion on/. about how XenSource and VMware are butting heads.
I don't see where VMware getting antsy about it's two main competitors in the field getting together isn't an issue?
Maybe the reason that VMware is so peeved over this is that XenSource and Microsoft have forged a strategic alliance, so this would be yet another blow against VM, helping them out of the door of the virtualisation market.
XenSource doesn't have a business to protect? That'll be why Frank Artale is the vice president of business development at XenSource. That'll also be why Microsoft and XenSource have joined forces to aid server virtualization, will it? (FTA - http://www.eweek.com/article2/0,1895,1990366,00.as p )
Seriously people, this is computer software we're talking about, not Israel and Hezbollah. I think they can come to a compromise pretty soon here.
You think? What we have here is two companies that are effectively competing to make theirs the best-case solution to the problem. It gets adopted, maintenance/support contracts come their way. They're not in it for the kudos, they're in it for the money.
Weeeelll.....if you're diving on pure O2 then if you go much below 2 metres, then you're greatly increasing your risk of going into CNS shock, having what is broadly similar in appearance to an epilleptic fit underwater and drowning. If you're staying above 2m then you shouldn't have too much of a problem reaching the surface. The lower the proportion of O2 in the gas mix, the deeper you can dive. Therefore the difference is from divers who forget to check how much O2 they have in their gas mix before they dive (too late once you're wet!).
Now I've got the anal point out of the way, and will assume that you meant checking how much *air* they have before they dive....the problem is more if you forget to check it whilst you're actually underwater! If you run out of air, then you have to head for the surface, and depending on your dive profile possibly miss a decompression stop and run the risk of DCI (the bends). Kinda like running out of fuel in an aircraft. You might survive, but if you do there's always the chance that you'll never walk again!
Of course, if you're diving beyond recreational dive limits, necessitation decompression stops, then you should damned well know about checking your equipment before you get in the water!
I think you'll find it's meant to be funny - a paraphrasing of Tom Watson Sr. (ex-chairman of IBM) who famously said in 1943 - "I think there is a world market for maybe five computers."
Ever heard of vertex shaders, pixel shaders, SLI? Hardware-accelerated physics (e.g. http://www.aegia.com/)? All examples of parallelism going on inside your modern PC. Stuff is getting shipped out by your CPU to different bits of you renderfarm all the time, so it can precisely spend it's own time predicting what's going on in advance. This is, in fact, one of the main reasons why a game *does* feel good - because the CPU has been freed up by outsourcing the T&L pipeline.
Slashdot Mirror
Yeah - timeline runs like this. April 13th...(in your article)
/. about how XenSource and VMware are butting heads.
"For a long time, it was thought that we'd just merge the Xen patches as-is and be happy. But then, Linux would only run on Xen," Morton said. Instead, VMware programmers suggested a documented, stable interface between the kernel and the hypervisor--and they're preparing one, he said."
"From a high-level design perspective, I think that VMware's point is a good one, and that a general kernel-to-virtual machine interface is a better thing than a Xen-only one," Morton said.
XenSource and VMware both are fine with the change, but VMware gets a place at the table it lacked before. "
July 18th - XenSource and MS announce a partnership.
August 1st - Big discussion on
I don't see where VMware getting antsy about it's two main competitors in the field getting together isn't an issue?
Maybe the reason that VMware is so peeved over this is that XenSource and Microsoft have forged a strategic alliance, so this would be yet another blow against VM, helping them out of the door of the virtualisation market.
They are - FTA http://www.eweek.com/article2/0,1895,1990366,00.as p
XenSource doesn't have a business to protect?s p )
That'll be why Frank Artale is the vice president of business development at XenSource.
That'll also be why Microsoft and XenSource have joined forces to aid server virtualization, will it?
(FTA - http://www.eweek.com/article2/0,1895,1990366,00.a
Seriously people, this is computer software we're talking about, not Israel and Hezbollah. I think they can come to a compromise pretty soon here.
You think? What we have here is two companies that are effectively competing to make theirs the best-case solution to the problem. It gets adopted, maintenance/support contracts come their way. They're not in it for the kudos, they're in it for the money.
Weeeelll.....if you're diving on pure O2 then if you go much below 2 metres, then you're greatly increasing your risk of going into CNS shock, having what is broadly similar in appearance to an epilleptic fit underwater and drowning. If you're staying above 2m then you shouldn't have too much of a problem reaching the surface. The lower the proportion of O2 in the gas mix, the deeper you can dive. Therefore the difference is from divers who forget to check how much O2 they have in their gas mix before they dive (too late once you're wet!).
Now I've got the anal point out of the way, and will assume that you meant checking how much *air* they have before they dive....the problem is more if you forget to check it whilst you're actually underwater! If you run out of air, then you have to head for the surface, and depending on your dive profile possibly miss a decompression stop and run the risk of DCI (the bends). Kinda like running out of fuel in an aircraft. You might survive, but if you do there's always the chance that you'll never walk again!
Of course, if you're diving beyond recreational dive limits, necessitation decompression stops, then you should damned well know about checking your equipment before you get in the water!
.....welcome our Radioactive Scorpion Overlords.
(oblig.)
Unique - that'll be like the ringtone site you're pimping in your sig, eh?
A visiting what? C'mon - I mean seriously.....this *is* slashdot!
I would love to take it with a grain of salt - unfortunately I had some chitosan earlier and I'm not really hungry at the moment.
......will it run linux??
I think you'll find it's meant to be funny - a paraphrasing of Tom Watson Sr. (ex-chairman of IBM) who famously said in 1943 - "I think there is a world market for maybe five computers."
Ever heard of vertex shaders, pixel shaders, SLI? Hardware-accelerated physics (e.g. http://www.aegia.com/)? All examples of parallelism going on inside your modern PC. Stuff is getting shipped out by your CPU to different bits of you renderfarm all the time, so it can precisely spend it's own time predicting what's going on in advance. This is, in fact, one of the main reasons why a game *does* feel good - because the CPU has been freed up by outsourcing the T&L pipeline.
Not sure 'bout that - can we make it 640K to be on the safe side?