The Solution To All Install Problems
 

<center>
<blockquote>
ooooooooooooooooooooooooooooooooooooo
0 NOTE 0
ooooooooooooooooooooooooooooooooooooo
This is 100% guaranteed to work in a Bourne Again shell environment (bash or sh). Especially, if it is followed to the letter. Never Install LimeWire as ROOT!!! (Unless you are an experienced advanced linux user who is familiar with changing user ownership of files and directories).
So much work is going into making a detailed installer for all methods that I have a new idea.
I think a new modified installer is in order. One that will detect and configure your system properly with java. I will make a script that will do all the necessary magic. Goodness this is difficult to accomplish. Working out "bugs" currently between scripts for bash1.2, bash2, and ksh. Beta to be posted soon.
This has been updated Oct 19, 2003.
ooooooooooooooooooooooooooooooooooooo

Each Post will be categorialized by installation method in relation to packaging scheme (ie rpm, emerge, tarballs, and deb) Not in that exact order mind you. Let us begin with the RPM enthusiasts out there using Sun's Java VM:
.
</blockquote></center>

**Note**
This portion is for Sun Java VM instructions. Scroll further down for IBM and BlackDown Java VM Installation Instructions.
********

++++++++++++++++++++++++
BEGIN SUN RPM METHOD
++++++++++++++++++++++++

Mandrake Users: remove kaffe first. (rpm -e kaffe --nodeps)
RedHat Users: remove jdkgcj first. (rpm -e jdkgcj --nodeps)

**Note**
These examples are based on installation instructions for Sun's Java VM j2sdk-1.4.0. You will have to substitute my example's path (/usr/java/j2sdk1.4.0) with your installed java VM (/usr/java/j2re1.4.2_05 or equivalent) Instructions on discovering this is mentioned later when needed below.
**End Note**

Download from java.sun.com.

Your package will have the name similiar to this one:

j2sdk1_4_0-fcs-rpm.bin

Execute the file in order to agree and extract the file:

sh j2sdk1_4_0-fcs-rpm.bin
(Substitute j2sdk1_4_0-fcs-rpm.bin with your downloaded file)

This should extract an rpm package like:

j2sdk1-4-0_01.fcs.rpm

Install this like you will install any other rpm:

rpm -Uvh j2sdk1-4-0_01.fcs.rpm
(Substitute j2sdk1-4-0_01.fcs.rpm with your uncompressed file)

Then follow the rest of the instructions to the letter---

Since I had a prior installation I get this when I do:

java -version

<output>
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
</output>

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre:

The sun package j2sdk-1.4.0-fcs is located :

/usr/java/j2sdk1.4.0

To find out for YOUR particular package, type this command (Please, please, please don't type "or". They are simply there to seperate commandline "options". Which mean use one of the following):

which -b java

or

rpm -ql j2sdk|more

or

rpm -ql j2re|more

and what it says in that first part is what you will have to add to your path statement:

(ie /usr/java/j2sdk1.4.0 in my case.)

You need to add a path statement in your .bash_profile:

**Note**
If you are in a graphical environment using KDE, Gnome, blackbox, and etc, Ignore the vi editor instructions and just type using kate, kwrite, or gedit instead.
**End Note**

(Using vi type:
vi .bash_profile
press "i" (eye) to insert/edit/add the following:)

export JAVA_HOME=/usr/java/j2sdk1.4.0
export PATH=$JAVA_HOME/bin:$PATH

(Hit "Esc" to end editing. Then type:
:wq
to save and quit).

Next type in your terminal or console to activate these changes and use them now in your current session:

souce .bash_profile

Otherwise, you might have to logout then back in to accept these changes.


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

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 (Red Hat Systems).
**End Special Note**

After doing that, I execute the LImeWireLinux.bin installer (do this as a regular user and not root.:

./LimeWireLinux.bin

+++++++++++++++++++++++++
END SUN RPM METHOD
+++++++++++++++++++++++++

BlackDown RPM Install
 

+++++++++++++++++++++
BEGIN BLACKDOWN METHOD
+++++++++++++++1+++++

I get this when I do:

java -version

<output>
java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build Blackdown-1.3.1-02b-FCS)
Java HotSpot(TM) Client VM (build Blackdown-1.3.1_02b-FCS, mixed mode)
</output>

Make the appropriate changes depending on where you installed your java installation whether it be sdk or jre:

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

/usr/lib/j2sdk1.3.1

You can find your path by typing this command:

which -b java

into my PATH in my .bash_profile:

(Using vi, a linux editor like windows "edit" program, type:

vi .bash_profile

press "i" (eye) to insert/edit/add the following.)


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

(Hit "Esc" to end editing. Then type:
:wq
to save and quit).

Next type in your terminal or console to activate these changes and use them now in your current session:

souce .bash_profile

Otherwise, you might have to logout then back in to accept these changes.

If you are in a graphical environment using KDE, Gnome, blackbox, etc use kate, kwrite, or gedit instead.

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:

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

I next create soft links to the /usr/bin directory but blackdown has most of all of it's java commands (ie java, javac, etc) as symbolic links. Some people´s configuration will not allow that many symlinks (That is a softlink pointing to another softlink)
the symlinks point to a "hidden" file called .java_wrapper. So I link this to my /usr/bin directory like so:

ln -s /usr/lib/j2sdk1.3.1/bin/.java_wrapper /usr/bin/java

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.

</snip>

Please let me know by leaving a comment or anything if you have any problems with my solution.

++++++++++++++++++++
END BLACKDOWN METHOD
++++++++++++++++++++

IBM Installation
 

Believe it or not, it is the exact mirror of the sun installation steps. I will post changes as they become available to me.

altoine

Re: I Have The Solution To All Install Problems
 

+++++++++++++++++++++++++
BEGIN TARBALL INSTALL METHOD
+++++++++++++++++++++++++

I need to add this for those without an rpm java install that is conflicting with another java program or you simply want to get rid of one.

To remove a tarball installed java package (tar.gz and tar.bz2).

First find them all:

which -b java

then remove the directory of the old java tarball path.

rm -fr /usr/local/java/j2sdk1.1.8

Make sure you have appropriate access privileges, but that part should go without saying. So it will be said, nevermore. (What a coincidence, I had just finished reading an edgar allen poe book!)

mkdir /usr/local/java

cd /usr/local/java

Let us assume that you downloaded your java package to the "/temp" directory.

ls /temp

should produce an output like:

j2re1.4.1.tar.gz

unpack the archive from your current directory; /usr/local/java:

tar -xzvpf /temp/j2re1.4.1.tar.gz

Java is now installed and now only needs to be configured to be "seen" by the rest of the system.

like in /etc/profile and ~/.bash_profile:

export JAVA_HOME="/usr/local/java/j2re1.4.1_01/"

Finished.

http://members.fortunecity.com/ndisc...ges/fluor1.jpg


++++++++++++++++++++++
END TARBALL INSTALL METHOD
++++++++++++++++++++++

Hopefully A Final Note
 

First, I just wanted to add for those whom have not installed LimeWire yet in their *nix environment that my suggestions were tested in a bash shell and are not guaranteed to work with any other shell environments.

Second, these suggestions that I have provided to fix installation issues are also the best proper way to install LimeWire with a near 100% success rate, which is what my methods are enjoying right now.

Third, I discovered that for anyone using gcc3.1 or higher as their primary and only compiler environement will not be able to install LimeWire using the Linux installer.Unless, you put a proper CLASSPATH into your.bash_profile.

(Do the following:

vi .bash_profile

<press "i" (eye) to begin inserting/editing/adding information>

export CLASSPATH=$CLASSPATH:

<press "Esc" to end editing>

Type the following:

:wq

<This you do to write and quit.>
For those in a graphical environment using KDE, Gnome, blackbox, etc use kate, kwrite, gedit instead.

Use the tarball (tar.gz) instead.

Lastly, feeling confident that this will solve primarily all problems in this forum thread regarding installation issues using a bash environment (I should be a pollitician because I sure know how to cover my @ztsets! LoL), I am marshalling all my time and energies to developing LimeWire from this point onwards. I have my profiles to receive message when anyone leaves a message anywhere I have been and so I will be able to help out even though I physically won't be checking the forums on a daily basis.

Best regards,
altoine

GREAT ! Working

Just wanted to say thanks for posting that here. It did solve my problems installin that app.

After making these changes the installer started and the prog is working.
I use Mandrake 8.2
So you can consider that platform tested and working

Your welcome. :D

altoine

Update
 

I am taking a temporary break from modifiying code in LimeWire to make some changes and fixes to the LimeWire Installer. More on this development soon.

works like a charm
 

It seems that all you have to do to get this to work is make the link to you java bin/.java_wrapper

I did it as root and it worked .

ln -s /my_java_location/bin/.java_wrapper /usr/bin/java

yeah that's all fine and dandy eccept for one thing...

it says i have no vm period now....

a.k.a help!