Prerequisites:

• Fedora Core 14 (no updates)
• VMware-server-2.0.2-203138
• Radu Cotescu’s patch script
• Ramon de Carvalho Valle’s patch #2

Install Fedora, I use the Software Developer version with the Fedora Packager.

Unpack raducotescu-vmware-server-linux-2.6.3x-kernel-release-1.6-0-gbb26dce.zip, copy VMware-server-2.0.2-203138-update-2.patch into raducotescu-vmware-server-linux-2.6.3x-kernel-e26b34e, you can either overwrite the original vmware-server-2.0.2-203138-update.patch file or update vmware-server-2.0.x-kernel-2.6.3x-install.sh to use the patch-2 file.

Disable selinux

Update /etc/services so that 902 reads as follows:

vmware-authd    902/tcp

Create a link to the kernel headers:

ln -s "/usr/src/kernels/$(uname -r)" /usr/src/linux

Add UTS_RELEASE to /usr/src/linux/include/linux/version.h (see https://blog.tuinslak.org/vmware-server-and-kernel-2-6-33):

echo "#define UTS_RELEASE \"$(uname -r)\"" >> /usr/src/linux/include/linux/version.h

Finally run Radu’s script giving it the directory of your vmwarer server 2.0.2 archive.

./vmware-server-2.0.x-kernel-2.6.3x-install.sh /PATH/TO/VMware-server-2.0.2-203138.x86_64.tar.gz

If all goes well you will have completed your install without error.

A couple of final cleanup issues you will need to rename libxml2.so.2 for vmware to something else (see http://communities.vmware.com/message/1670144#1670144)

mv /usr/lib/vmware/lib/libxml2.so.2/libxml2.so.2 /usr/lib/vmware/lib/libxml2.so.2/SKIP.libxml2.so.2

And finally update /etc/init.d/vmware script so it starts after networking has properly started, the default configuration doesn’t do this on my machine.

Update the chkconfig line to read:

# chkconfig: 35 35 20

Make sure the init scripts are properly linked:

chkconfig --del vmware

chkconfig --add vmware

chkconfig --level 35 vmware on # for good measure

Reboot your machine.

Depending on your configuration you may also have to update your iptables rules.

The e-mail address for the sender (ABC@theYYYgroup.com) is internal to your organization and cannot be added to the Safe Senders list. E-mail from senders in your organization will never be treated as junk e-mail.

1. So the email from the internal sender was flagged as junk
2. And the sender cannot be added to the white list because the sender is internal
3. If the sender is internal and always trusted how did the email get flagged as junk.
4. Reductio ad absurdum

Doesn’t Microsoft test their software?

So the solution is to create two R.java files, one with your internal package name and the other with the package name of the release which comes from AndroidManifest.xml, at this point I would point out that you should probably generate your AndroidManifest.xml.

To generate the required R.java files, you must customize the Google Ant build scripts,  copy android_rules.xml from the SDK into your project. The second exec stanza generates the internal R.java which you specify with the property “package.internal”

<!-- Generates the R.java file for this project's resources. -->
 <target name="-resource-src" depends="-dirs">
 <echo>Generating R.java / Manifest.java from the resources for ${package.destination}</echo>
 <exec executable="${aapt}" failonerror="true">
 <arg value="package" />
 <arg line="${v.option}" />
 <arg value="-m" />
 <arg value="-J" />
 <arg path="${gen.absolute.dir}" />
 <arg value="-M" />
 <arg path="AndroidManifest.xml" />
 <arg value="-S" />
 <arg path="${resource.absolute.dir}" />
 <arg value="-I" />
 <arg path="${android.jar}" />
 <arg value="--custom-package" />
 <arg value="${package.destination}" />
 </exec>

 <echo>Generating R.java / Manifest.java from the resources for ${package.internal}</echo>
 <exec executable="${aapt}" failonerror="true">
 <arg value="package" />
 <arg line="${v.option}" />
 <arg value="-m" />
 <arg value="-J" />
 <arg path="${gen.absolute.dir}" />
 <arg value="-M" />
 <arg path="AndroidManifest.xml" />
 <arg value="-S" />
 <arg path="${resource.absolute.dir}" />
 <arg value="-I" />
 <arg path="${android.jar}" />
 <arg value="--custom-package" />
 <arg value="${package.internal}" />
 </exec>        
 </target>

In your build file, tweak the android setup as follows

<setup import="false" />
<import file="${basedir}/build/android_rules.xml"/>

import false says don’t use the standard android_rules and the following import references your custom rules.

A good reference, but didn’t go far enough: http://java.dzone.com/articles/building-two-versions-same?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed:+javalobby/frontpage+(Javalobby+/+Java+Zone)

The clear winner is Cobertura for the following reasons:

• Ant targets are easier to use and don’t generate errors in Intellij (a minor thing but highly annoying)
• It is much easier to exclude test classes
• The output generated is vastly superior if not more voluminous
• Better but still sparse documentation

Compared to some other heap analysis tools I’ve used VisualVM needs a lot of work. Having said that being able to take heap dumps as you manipulate a system in real-time is very useful, and then using another analysis tool seems like the best option (note I haven’t tried using another analyzer with visualVM’s heap dump.)

I also had the relevant addresses redirected to my server, so techdetails.blogmatrix.com -> techdetails.agwego.com, which posed an issue with respect to permalinks, so with a little Wordpress hacking I was able to write a pseudo BlogMatrix to Wordpress permalink converter so most links will now work as expected. I have a complete duplicate site setup at home replete with DNS for testing purposes.

I’m still getting use to Wordpress but so far it’s not too bad.

My other blog http://dinner.agwego.com/