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?

You can download the first release 0.7.0 at Google Code: http://code.google.com/p/fuzztester this should be considered a beta release as I currently have some people reviewing the release, and I will hopefully get some good feedback to improve the project and documentation.

FuzzTester is a JUnit 4 test runner that allows you to manage your test data in files instead of in your test code, this simplifies your test code, and decreases the feedback loop between writing tests and running tests.

Code less, Test more.

• Instant on, this is a killer feature if only the wifi synced as quickly as the iPad started
• no cables or power during regular use
• can perform a wide variety of simple tasks from the comfort of wherever, need I say more
• A great device for the gym, easy to read e-books while working out on the stair master, treadmill, etc.
• with the correct HDMI cable you can use it as a media player
• My wife finds it easy to use and uses it regularly
• Great for technical documentation, in particular PDF’s, also  dictionary searches in the application
• A portable interactive manual great for working on mechanical things without having to have a full blown computer near by

The negatives, and there area few…

• It could be lighter, but I expect that to be a future enhancement
• The wifi sync’ing can be slow at times
• typing in long passwords on all portable devices is highly annoying, this is true of every portable device
• A little too easy to cheat on the crossword

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)

Hopefully VMWare won’t be far behind, since this would simplify testing software on various versions of Mac OS X.

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’m impressed:

• very fast – reads are frightening
• small – but it’s hard to find 2.5″ to 3.5″ mounting brackets
• cool – no heat this is great for cramped cases
• clean – no exposed circuits, unlike a regular hard disk
• quiet – obviously but very welcome
• would fit the Mac Mini very nicely

The unit I have is an OCZ Vertex 120GB, which is sufficient space for my purposes. I dropped it into my Franken Mac and ran XBench so I could get some performance numbers with a common base, please note that these numbers were taken after a fresh install so the disk has not yet been heavily fragmented. I would also note that this isn’t the Mac version of this drive, and as such I found the drive was very unstable with mysterious hangs and failures, but it did run long enough to get some good numbers. I now have the drive installed in a Gateway GT5676 as the primary boot disk for Fedora Core 11 and it has been rock solid and running vmware like a champ, but time will tell.

I found this article very helpful: http://www.pcper.com/article.php?aid=736

Now the numbers:
OCZ Vertex

Results	180.94
	System Info
		Xbench Version		1.3
		System Version		10.5.6 (9G2030)
		Physical RAM		4096 MB
		Model		Macmini3,1
		Drive Type		OCZ-VERTEX

	Disk Test	182.95
		Sequential	136.65
			Uncached Write	188.04	115.46 MB/sec [4K blocks]
			Uncached Write	176.88	100.08 MB/sec [256K blocks]
			Uncached Read	79.05	23.14 MB/sec [4K blocks]
			Uncached Read	176.96	88.94 MB/sec [256K blocks]
		Random	276.72
			Uncached Write	112.99	11.96 MB/sec [4K blocks]
			Uncached Write	307.32	98.38 MB/sec [256K blocks]
			Uncached Read	1544.06	10.94 MB/sec [4K blocks]
			Uncached Read	587.24	108.97 MB/sec [256K blocks]

Western Digital Velociraptor 10,000 RPM

Results	161.56
	System Info
		Xbench Version		1.3
		System Version		10.5.6 (9G2030)
		Physical RAM		4096 MB
		Model		Macmini3,1
		Drive Type		WDC WD3000BLFS-01YBU0
	Disk Test	93.41
		Sequential	143.22
			Uncached Write	190.65	117.06 MB/sec [4K blocks]
			Uncached Write	163.74	92.64 MB/sec [256K blocks]
			Uncached Read	81.75	23.92 MB/sec [4K blocks]
			Uncached Read	230.15	115.67 MB/sec [256K blocks]
		Random	69.31
			Uncached Write	25.02	2.65 MB/sec [4K blocks]
			Uncached Write	193.45	61.93 MB/sec [256K blocks]
			Uncached Read	125.65	0.89 MB/sec [4K blocks]
			Uncached Read	216.22	40.12 MB/sec [256K blocks]

Standard Mac 5400 RPM

Results	130.85
	System Info
		Xbench Version		1.3
		System Version		10.5.6 (9G2030)
		Physical RAM		4096 MB
		Model		Macmini3,1
		Drive Type		FUJITSU MHZ2120BH G1
	Disk Test	46.65
		Sequential	64.41
			Uncached Write	91.99	56.48 MB/sec [4K blocks]
			Uncached Write	90.47	51.19 MB/sec [256K blocks]
			Uncached Read	32.45	9.50 MB/sec [4K blocks]
			Uncached Read	106.86	53.71 MB/sec [256K blocks]
		Random	36.57
			Uncached Write	13.38	1.42 MB/sec [4K blocks]
			Uncached Write	92.49	29.61 MB/sec [256K blocks]
			Uncached Read	67.95	0.48 MB/sec [4K blocks]
			Uncached Read	109.77	20.37 MB/sec [256K blocks]