Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Distribution: Red Hat Linux, Fedora Core, Knoppix, tomsrtbt
Posts: 37
Rep:
Sun Java
After some work, I finally managed to get Sun's J2SE 1.4.2_04 SDK installed. When I went to run Eclipse, I recieved an error that stated that a virtual machine could not be found in the ~/eclipse3.0M8/java/jre/bin directory or in the PATH.
After searching the boards, I ran across a thread that said that you should add the export statements to the /etc/rc.local script. I followed that advice and my /etc/rc.local file now reads:
Code:
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initilizatoin stuff in here if you don't
# want to do the full Sys V style init stuff.
touch /var/lock/subsys/local
export PATH=$PATH:/usr/java/j2sdk1.4.2_04/bin
export PATH=$PATH:/usr/java/j2sdk1.4.2_04/jre/bin
I then logged out and back in. In the terminal I checked the contents of the PATH variable. The output was:
Then I tryed rebooting my computer. When I checked the contents of the PATH variable, I got the exact same output. Why isn't my PATH variable being changed?
Distribution: Red Hat Linux, Fedora Core, Knoppix, tomsrtbt
Posts: 37
Original Poster
Rep:
I tryed making the symbolic link as you specified, but I kept getting an error message about the file or folder not being found. I tryed su, but was unsuccessful in that too.
I then tryed to put the PATH declerations in the profile file
Code:
USER=......
LOGIN=.....
MAIL=......
PATH=$PATH:/usr/java/j2sdk1.4.2_04/bin
PATH=$PATH:/usr/java/j2sdk1.4.2_04/jre/bin
export PATH USER LOGIN MAIL........
(The elipses (...) are included since I did not take down the full text of the file.)
Then I logged out and back in and checked PATH, but it was unchanged. I then rebooted the computer and loged in and checked PATH, but it was still unchanged.
Distribution: Red Hat Linux, Fedora Core, Knoppix, tomsrtbt
Posts: 37
Original Poster
Rep:
First, I am using FC 2. Second, I noticed that I had changed the KDE Konsole to use csh instead of bash (Stupid!). Anyway, I tried editing the csh.cshrc file by adding
Now whenever csh is started I gat an error message in the Konsole that says that there is an illegal operator (/). I have tried using parenthesis and the semicolon at the end of the line and using quotation marks, but none of them fix the error, and if anything, create new errors.
I have tried editing /etc/profile, but it seems to have no effect.
BTW, is there an easy way to check if my fix has worked without logging out and back in again or rebooting my computer? Does just typing csh at the prompt or changing to another shell and then bask to csh work?
Last edited by confidential007; 05-30-2004 at 12:44 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.