Linux Install
 

How do I install LimeWire in Linux?

Tried sh ./LimeWireLinux.bin

Preparing to install...
The included VM could not be extracted. Please try to download
the installer again and make sure that you download using 'binary'
mode. Please do not attempt to install this currently downloaded copy.

Please Help Me!

Your linux system doesn't have the compress command installed. It is called something like ucompress or uncompress. Get that and it will work.

-greg

Ucompress , Uncompress
 

Can't find any of these (ucompress, uncompress). Anyone who knows were to find them and how to install them?

After I installed uncompress I get this message :
sh ./LimeWireLinux.bin

SIGSEGV received at bffff31c in /tmp/install.dir.5735/Linux/resource/jre/lib/linux/native_threads/libjava.so. Processing terminated
Writing stack trace to javacore6813.txt ... OK
./LimeWireLinux.bin: line 1: 6813 Segmenteringsfel /tmp/install.dir.5735/Linux/resource/jre/bin/jre -Djava.compiler= -noverify -cp "::/tmp/install.dir.5735/InstallerData:/tmp/install.dir.5735/InstallerData/installer.zip" com.zerog.lax.LAX "/tmp/install.dir.5735/temp.lax" /tmp/env.properties.5735

I had the same problem, now I've got a new one...
 

I've got the LimeWireLinux 1.4 .bin in my home dir.
I use Mandrake Linux 8.0, so I popped the CD in and installed the ncompress rpm (easy to do, mandrake even has a GUI for these sorts of things now).

But now, every time I run the bin, I get a long error message, and occasionally my entire system will lock up (which is very unusual for Linux)

It goes like this:

[user@name dir]$ ./LimeWireLinux.bin
Preparing to install...
SIGSEGV received at bffff31c in /tmp/install.dir.1441/Linux/resource/jre/lib/linux/native_threads/libjava.so Processing terminated
Writing stack trace to javacore2519.txt ... OK
./LimeWireLinux.bin: line 1: 2519 Segmentation fault /tmp/install.dir.1441/Linux/resource/jre/bin/jre -Djava.compiler= -noverify -cp "::/tmp/install.dir.1441/InstallerData:/tmp/install.dir.1441/InstallerData/installer.zip" com.zerog.lax.LAX "/tmp/install.dir.1441/temp.lax" /tmp/env.properties.1441


Then I get either a new prompt, or my linux system crashes, neither of which is good.

I'm pretty sure that this is the problem with the new linux kernel. When they rolled the latest linux kernel out, older Java versions didn't work with it. I think that this one will:

http://java.sun.com/j2se/1.3/jre/download-linux.html

-greg

That tends to bring up another problem...
 

I tried throwing up a java install of Limewire a few days ago, and in the process tried to d/l and install jre1.3 from Sun, but installing a new version of java such that the old one is replaced seems nightmarish due to the distro differences. The .bin will install fine wherever I tell it to, and will work from it's installed location, the problem is the o/s doesn't know that new version is there.

So, my question is, Sun displays a "Red Hat RPM" version, and I was tempted to download that as RPM's eliminate this problem. Don't RPM's essentially work no matter what distro you throw them on? Must I download the straight .bin install and tinker with environment variables until I replace the old java?

update on the situation...
 

I downloaded jre 1.3 AGAIN... installed it AGAIN to /usr/local/jre1.3.1/ This time I noticed the "control panel" application it comes with, and found an option in there that could be set to point to the new version at the location I just installed.

No go, any 'java -version' command at a $ prompt gives the old version. I've no clue how to ensure that Linux knows there's a new version of Java installed, there is no HOWTO on this and Sun's website is completely inadequate (it doesn't tell you more than "execute the bin", well DUH).

What's needed are specific instructions as to how to replace one's old version of Java on various distributions. Does anyone have ANY idea how to do this? It's quite annoying to not be able to use software over such simple impasses.

If you want to ensure that any version of a command is accessed from the command line then you make sure that the path to it occurs first in your PATH environment variable.

You have some kind of .profile (.bash_profile, .login, .kshrc, or whatever) in your login directory where you could specify this. You may need to set JAVA_HOME as well. i.e.
JAVA_HOME=/usr/local/jre1.3.1
PATH=$JAVA_HOME/bin:$PATH
export PATH JAVA_HOME
This depends on what shell you are using - likely bash (man bash)

-greg

Still not working
 

Greg, thanks for all the help. I managed to get the path updated, and the correct version number appears when I do a java -version...(thanks for the instruction on that too, always good to know where to go to manipulate environment variables) however I'm still getting that message above (the long one that was causing system lockups). I've tried it as root, as a user, from console/terminal, etc.. nothing seems to work.