<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mono 2.2 Appliance</title>
	<atom:link href="http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/</link>
	<description>It&#039;s better than bad, it&#039;s good!</description>
	<lastBuildDate>Mon, 06 Feb 2012 23:49:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andrew Jorgensen</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-343</link>
		<dc:creator>Andrew Jorgensen</dc:creator>
		<pubDate>Sun, 15 Mar 2009 18:56:25 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-343</guid>
		<description>I assume you&#039;re referring to the LiveCD?  We use xsp on the LiveCD instead of apache and &lt;code&gt;MONO_IOMAP=all&lt;/code&gt; is not set for xsp in the 2.2 appliance.  This causes problems with applications that look for the wrong case of a file.

In the 2.4 appliance we set the variable, so that problem should go away.</description>
		<content:encoded><![CDATA[<p>I assume you&#8217;re referring to the LiveCD?  We use xsp on the LiveCD instead of apache and <code>MONO_IOMAP=all</code> is not set for xsp in the 2.2 appliance.  This causes problems with applications that look for the wrong case of a file.</p>
<p>In the 2.4 appliance we set the variable, so that problem should go away.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Flynn</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-339</link>
		<dc:creator>Martin Flynn</dc:creator>
		<pubDate>Sat, 14 Mar 2009 05:31:44 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-339</guid>
		<description>A lot of the asp.net applications only work on the front page.  The rest of the pages give a file not found error although the files are all there (I can view their sources.)</description>
		<content:encoded><![CDATA[<p>A lot of the asp.net applications only work on the front page.  The rest of the pages give a file not found error although the files are all there (I can view their sources.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sylvain</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-247</link>
		<dc:creator>Sylvain</dc:creator>
		<pubDate>Sun, 18 Jan 2009 11:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-247</guid>
		<description>I remember I tried the VMware way first thing with the last Mono LiveCD (2.0.1) and it failed miserably because of some HDD identity strings being messed up (I don&#039;t remember exactly to be honest, it just did not work out of the box). That&#039;s why I resorted to install from the LiveCD.

I followed your advice though, and gave the VMware thingy another shot with this new version and it seems to be working very well. So, all in all:

THANK YOU</description>
		<content:encoded><![CDATA[<p>I remember I tried the VMware way first thing with the last Mono LiveCD (2.0.1) and it failed miserably because of some HDD identity strings being messed up (I don&#8217;t remember exactly to be honest, it just did not work out of the box). That&#8217;s why I resorted to install from the LiveCD.</p>
<p>I followed your advice though, and gave the VMware thingy another shot with this new version and it seems to be working very well. So, all in all:</p>
<p>THANK YOU</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Jorgensen</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-246</link>
		<dc:creator>Andrew Jorgensen</dc:creator>
		<pubDate>Fri, 16 Jan 2009 17:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-246</guid>
		<description>@Sylvain
Actually the best way to create a VirtualBox machine is to download the VMware appliance and use the .vmdk from it as your disk in VirtualBox.  The appliance knows nothing specific to VMware until it&#039;s booted the first time and there is nothing special in the .vmx file that you would need to tell VirtualBox about.  Please try that method and let me know if it doesn&#039;t work.  I&#039;ve done it many times in the past and it worked very well for me.</description>
		<content:encoded><![CDATA[<p>@Sylvain<br />
Actually the best way to create a VirtualBox machine is to download the VMware appliance and use the .vmdk from it as your disk in VirtualBox.  The appliance knows nothing specific to VMware until it&#8217;s booted the first time and there is nothing special in the .vmx file that you would need to tell VirtualBox about.  Please try that method and let me know if it doesn&#8217;t work.  I&#8217;ve done it many times in the past and it worked very well for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Jorgensen</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-245</link>
		<dc:creator>Andrew Jorgensen</dc:creator>
		<pubDate>Fri, 16 Jan 2009 17:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-245</guid>
		<description>@Sylvain
We are considering adding the live installer again.  The main reasons it was removed on this release were that we didn&#039;t take time to test that feature and didn&#039;t have a lot of confidence in it and we would have to have those packages included on the LiveCD but not on the VMware appliance.  On this release there is actually only one difference between those two images: a single firstboot script that basically only adds a swap file to the VMware appliance and tunes a file system parameter.

In theory you should be able to just add the yast2-live-installer package and then run the installation.  I would be interested in hearing back from you if that works.</description>
		<content:encoded><![CDATA[<p>@Sylvain<br />
We are considering adding the live installer again.  The main reasons it was removed on this release were that we didn&#8217;t take time to test that feature and didn&#8217;t have a lot of confidence in it and we would have to have those packages included on the LiveCD but not on the VMware appliance.  On this release there is actually only one difference between those two images: a single firstboot script that basically only adds a swap file to the VMware appliance and tunes a file system parameter.</p>
<p>In theory you should be able to just add the yast2-live-installer package and then run the installation.  I would be interested in hearing back from you if that works.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Jorgensen</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-244</link>
		<dc:creator>Andrew Jorgensen</dc:creator>
		<pubDate>Fri, 16 Jan 2009 17:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-244</guid>
		<description>@Stifu
I&#039;ve been looking into that issue.  Apparently whatever method GNOME is using to detect the type of a mono executable is coming up with application/executable rather than anything more windows or .NET specific, so I haven&#039;t found a good way to open a mono executable from the file browser.  We could use the binfmt kernel module stuff to execute CLR executables, and openSUSE has discussed doing that, but it would have to be able to distinguish between something that should be executed with wine and something that should be executed with mono.  Some systems are able to execute Java .jar files this way, for instance.</description>
		<content:encoded><![CDATA[<p>@Stifu<br />
I&#8217;ve been looking into that issue.  Apparently whatever method GNOME is using to detect the type of a mono executable is coming up with application/executable rather than anything more windows or .NET specific, so I haven&#8217;t found a good way to open a mono executable from the file browser.  We could use the binfmt kernel module stuff to execute CLR executables, and openSUSE has discussed doing that, but it would have to be able to distinguish between something that should be executed with wine and something that should be executed with mono.  Some systems are able to execute Java .jar files this way, for instance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Morgan</title>
		<link>http://andrew.jorgensenfamily.us/2009/01/mono-22-appliance/comment-page-1/#comment-243</link>
		<dc:creator>Chris Morgan</dc:creator>
		<pubDate>Thu, 15 Jan 2009 22:43:43 +0000</pubDate>
		<guid isPermaLink="false">http://andrew.jorgensenfamily.us/?p=416#comment-243</guid>
		<description>Just wanted to mention that you may have difficulties with this new mono appliance. I downloaded it today and my mouse is stuck inside of the vmware window as if vmware tools isn&#039;t installed. I filed a bug and received some helpful feedback about why this is happening, https://bugzilla.novell.com/show_bug.cgi?id=466591   I&#039;ve tried the suggestions but it seems quite difficult to get the actual vmware-tools installed since I can&#039;t seem to actually remove the offending vmware open tools packages without prompting an install of other vmware  packages and xen etc.</description>
		<content:encoded><![CDATA[<p>Just wanted to mention that you may have difficulties with this new mono appliance. I downloaded it today and my mouse is stuck inside of the vmware window as if vmware tools isn&#8217;t installed. I filed a bug and received some helpful feedback about why this is happening, <a href="https://bugzilla.novell.com/show_bug.cgi?id=466591" rel="nofollow">https://bugzilla.novell.com/show_bug.cgi?id=466591</a>   I&#8217;ve tried the suggestions but it seems quite difficult to get the actual vmware-tools installed since I can&#8217;t seem to actually remove the offending vmware open tools packages without prompting an install of other vmware  packages and xen etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

