Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre (ie /usr/java/j2sdk1.4.0, /usr/java/j2re1.3.1, /usr/lib/j2re1.3.1, etc):

I put where I downloaded my j2sdk1.3.1-02b-FCS:

/usr/lib/j2sdk1.3.1

into my PATH in my .bash_profile (.bashrc will work, also):

export JAVA_HOME=/usr/lib/j2sdk1.3.1
export PATH=$JAVA_HOME/bin:$PATH

After doing that, I remove kaffe from my system but I have a dependency problem with my wizard packages. I do this command to keep that program around:

(If the above path is added to .bash_profile or .bashrc, you really won't have to remove kaffe if you reboot or logout and then login again before running the LimeWire Installer) This is necessary in order for the path changes can take effect. Depending on your setup, just opening another terminal will not use your new changes. Once the system is using your changes, you will not have to mess with them until you do a java vm upgrade.

Instructions for removing kaffe without breaking anything:

rpm -e kaffe --nodeps

This removes all instances of kaffe binaries from /usr/bin.

**Special Note**
rpm -e jdkgcj --nodeps

for those whom have this package installed on their system.
**End Special Note**


After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root. I don't know a way to install it system wide as root yet without making a script.):

./LimeWireLinux.bin

Installation works. Program installed, running, and functional. I discovered that I had to install the program as user instead of trying to set it systemwide as root.