Slashdot Mirror
VMware Looks To Acquire Novell's SUSE Unit
minutetraders writes "According to the Wall Street Journal, VMware is attempting to acquire Novell's SUSE Linux operating system business. This move would give VMware a full stack of enterprise software and allow it to establish itself as a full-blown infrastructure and software vendor in direct competition with Red Hat."
The WSJ report is behind a paywall, but it's accessible in full through a Google search.
It won't be taken as seriously. You can *say* it's as good as an Enterprise Distro, it might even *be* as good. People that buy OSes for companies want to see a name they recognize. Right now those names are Red Hat (not available), SuSE, and to a less extent Canonical/Ubuntu (not available). Red Hat would probably be the one everyone wants to buy, but between being the market leader and being fairly profitable (not Microsoft or Apple levels of profitable, but plenty of money to keep everyone in kibble for sure), that's not much of an option.
I don't need a million points of light, just two points of multi-mode fiber and a 10 Gig-E router.
... does that mean we'd eventually see versions of vCenter Server and vCenter Client that run on something other than Windows? That would be nice.
Eviscerati.Org: All Hail the Eviscerati
Microsoft is giving away their shiny new hypervisor with their operating systems. What would be more fair than for VMWare to give away operating systems with their hypervisor?
Help stamp out iliturcy.
Really crud is it? Then Please tell me about: an equivalent open source piece of software that Encompasses all the features of :
Please do educate us ( at least me ) as to ready to install software that can duplicate or exceed the capabilities of each of those that does not have the Microsoft label. Because as it is I am ready to through Novell under the train, but not until I can do so without turning to The Empire.
Hey KID! Yeah you, get the fuck off my lawn!
Dude, whatever you are smoking can you please share it.
Gnome perpetrates Winhoze coding practices into the unix world. Just take any piece of gnome code and read it. Carefully. And follow the code design, not just the code "quality".
Let's just take ekiga as an example, though any gnome app will do.
The state machine is tightly coupled with the UI just like a Windows application. As a result making it use multiple CPUs properly or reusing the code for anything other than another Gnome application is impossible. Not surprisingly it triggers races in underlying (similarly badly coded) libraries like there is no tomorrow. Same for having the UI stripped away. This is impossible. And just do not get me started on the subject of trying to integrate something to a piece of gnome code. Because the apps state machines are built around the UI half of the key functions that should show up on dbus end up as inaccessible. Taking same ekiga as an example - call is exposed while hangup is not because it is so UI-tied up that there is no way in hell to expose it.
Baker's Law: Misery no longer loves company. Nowadays it insists on it
http://www.sigsegv.cx/
Let's just take ekiga as an example, though any gnome app will do.
The state machine is tightly coupled with the UI just like a Windows application. As a result making it use multiple CPUs properly or reusing the code for anything other than another Gnome application is impossible. Not surprisingly it triggers races in underlying (similarly badly coded) libraries like there is no tomorrow. Same for having the UI stripped away. This is impossible.
That's why GNOME has switched to Empathy, just another GNOME app but done right.
My exception safety is -fno-exceptions.