Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey, it finally worked this time and the correct path for me was -
export PATH=$PATH:/usr/java/j2sdk1.4.1_02/jre/bin
You guys are doing a great job here crashed_again. Without this help many people will just give up on linux.
thanks a bunch
I tried out the export PATH command, as i have also been having problems with java, but when i close the terminal window i have typed export in, the path no longer works. Is there a way to permanently set a path variable to a directory without it removing itself every time i close the terminal window? It is frustrating me intensely.
Add the export command line to your .bashrc (if you use bash) file. This should be in your users home directory. This will run every time a bash shell is started, including log-in.
I hadn't looked at this thread in a while. I did finally find out how to set the path to the java binary. I am glad to know I can add this to my .bashrc file to have it load up every time I open a terminal or session.
It should also be noted that it can be added to the .bashrc file in /etc/skel to be added to every user that you create. This way it won't have to be added to every user that needs the java vm.
i have the same problem and heres how i solved it
if you are a usr (not root) bring up a shell type mc
and go to your /home/yourname directory
look for a file called bash_profile then use the edit
function in mc you'll see a line something like
PATH=$path.....etc this is the one to edit after editing
your line should look something like this
PATH=/usr/java/j2re-1.4.1_02/bin
your supposed to type .$HOME/.bash_profile
to restart the file but it did'nt work for me i just
restarted my computer don't forget to save your edited
file before restarting after which limewire ran fine
i have the same problem and heres how i solved it
if you are a usr (not root) bring up a shell type mc
and go to your /home/yourname directory
look for a file called bash_profile then use the edit
function in mc you'll see a line something like
PATH=$path.....etc this is the one to edit after editing
your line should look something like this
PATH=/usr/java/j2re-1.4.1_02/bin
your supposed to type .$HOME/.bash_profile
to restart the file but it did'nt work for me i just
restarted my computer don't forget to save your edited
file before restarting after which limewire ran fine
6 hours of simlar forum queries, reading instructions, readmes etc.
but i think the problem is this:
you can set up the correct path to /usr/java/j2re1.4.2/bin/java
but (for some reason) one of the other java apps are being called.
thus:
- - -
so i did this on my machine running redhat 9.
downloaded j2re1.4.2 from sun.
executed the binary (sh (javafilename).bin) which turns it into a RPM.
as root: rpm -Uvh (javafilename).rpm
as root: pico /etc/profile
added the line PATH=$PATH:/usr/java/j2re1.4.2
right before this line export PATH USER LOGNAME MAIL HOSTNAME HISTSIZE INPUTRC
exit root
log out and back in
or type export PATH=$PATH:/usr/java/j2re1.4.2
(although this is mentioned everywhere in these forums goto your java directory and do a 'pwd' then type echo $PATH and compare and make sure they are the same)
((i also exported my LD_LIBRARY_PATH but i don't think this made a difference. if it did, i will write back and say so...))
---
ok,
now again, i haven't exhausted all possibilites of what might work,
but i do know what just worked for me moments ago after hours of messing about:
i didn't download the Limewire.bin file
instead i clicked on the link for 'other systems'
and downloaded a tgz file.
make sure you make a directory for that file before doing the 'tar zxvf filename.tgz' b/c it hasn't been done properly (nor has any faqs/installation help as far as i can see) and it will make a mess of whatever directory you untar/zip it...
followed directions in the README that came with it.
(i forget, but i don't think it was the usual ./configure, make, ((i use a program called chkrootkit which instead of 'make install' putting stuff all over your system and making it (heh heh) impossible to uninstall, this sweet app makes an RPM from a tar.gz, tgz , etc , file)) )
and the punch line?
this command,
which basically forces the use of the 'new' java, and the java program! sounds simple/logical enought but was more like magic when i typed it in.
/usr/java/j2re1.4.2/bin/java -jar RunLime.jar
(this b.t.w is stated in the README that comes with the tgz file. except it didn't have the path info. i chucked that in myself. now i'm so proud. ;/ um, no not really, but i am gonna go and see if this LimeWire thing is even any good.)
pps- i did get kazaa emulating under WINE in redhat 9.
that was the day before yesterday.
8 hours.
and it wasn't really worth it.
terrible slow an took up 90-99 % of my used PIII 600M poo computer.
Originally posted by Crashed_Again I think you have to add the /bin on the end of that because the java command is in the /bin directory:
export PATH=$PATH:/usr/java/jre-1.4.1_02/bin
Thanks for the information Crashed_Again. This will confirm that it fixed the installation problem and now works for me with Mandrake 10.1. Crashed_Again made a very good point that you may have more than one Java installation. If you set the path for only one Java version, but Limewire is looking for the other, LimeWire will not install.
TIP - I have two versions of Java installed
export PATH=$PATH:/usr/java/j2re1.4.1_02/bin
export PATH=$PATH:/usr/java/j2re1.4.2_05/bin
When I ran the command with only the first version, I received the same error messages. I needed to add the path for the second installed Java version. Then I could install LimeWire. If you run the command for both, and still receive the error message, you may have three or more Java versions.
Last edited by wpennington; 12-19-2004 at 07:40 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.