<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.EmailStyle18
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</HEAD>
<BODY bgcolor=white lang=EN-US link=blue vlink=blue>
<DIV>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>If they’d been smart they’d
have done what Borland did after they bought dBaseII way back when and already
owned Paradox. They’d just issue updates to both products so they were
exactly alike. Doing it this way just annoys your install base who say to
themselves: “If I’ve got to migrate why migrate to something these
putzes make – might as well do something else.” Then again many
vendors will create a “migration path” before dumping stuff.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'> ale-bounces@ale.org [mailto:ale-bounces@ale.org] <b><span
style='font-weight:bold'>On Behalf Of </span></b>Brian Pitts<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, June 23, 2009 11:28
AM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">Atlanta
Linux Enthusiasts - Yes! We run Linux!</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [ale] Xen</span></font><font
color=black><span style='color:windowtext'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>On 06/23/2009 07:49 AM, <st1:PersonName w:st="on">Jeff
Lightner</st1:PersonName> wrote: <o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"><!--[if gte mso 9]><xml>
<u1:shapedefaults u2:ext="edit" spidmax="1026"/>
</xml><![endif]--><!--[if gte mso 9]><xml>
<u1:shapelayout u3:ext="edit">
<u1:idmap u3:ext="edit" data="1"/>
</u1:shapelayout>
</xml><![endif]-->Right but it goes on to say they’re folding it into
their own Oracle VM and that both were based on Xen.<u1:p></u1:p></span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><u1:p> </u1:p></span></font><o:p></o:p></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Since I never heard of Virtual Iron before
I can’t say much about it. If it was Open Source then they can only
quit supporting it themselves without killing it. However, I wonder
if the reason it is being killed isn’t because no one ever heard of it
and it had an uphill battle against VMWare, Xen and other options.</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><br>
</u1:smarttagtype></span></font>This thread was started by Jim posting old news
about Oracle buying Virtual Iron. It turned out that within a month of buying
them, Oracle fired almost everyone and discontinued the project. It seems like
a rather expensive way to get more customers for your own product.<br>
<br>
I am pretty curious to see what happens in the Sun xVM v Oracle VM fight.<br>
<br>
All the best,<br>
Brian Pitts<o:p></o:p></p>
</div>
</DIV>
<DIV> </DIV>
<DIV>
<FONT FACE="Arial" COLOR="green" SIZE="1"><EM>Please consider our environment before printing this e-mail or attachments.</EM></FONT>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Arial" SIZE="2">----------------------------------<BR>CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.<BR>----------------------------------<BR></FONT>
</DIV></BODY></HTML>