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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
to edit your path:
export $PATH=$PATH:/home/usr/bin (which adds the last entry to your original path).
Now for these others, I'm not sure what you're trying to do....you see, some program has to actually *use* these environments you'd be setting. You can just about export anything, but its pointless unless you use it. So, check the scripts to determine what variables are being used and work from there. Also, if you're making your own scripts, you dont need to export variables on the command line, but instead in the script.
maybe you could tell us the context that this came up under...
ok, all i want to do is like this.
i want to setup a java environment for my linux redhat...
i have downloaded and installed the java standard development kit 18.104.22.168.1 from www.java.sun.com. then, i want to set some environment variables like JAVA_HOME,... and etc. to the system. (i did that in windows 98). so, does ur solution hits my need?
if so, thanks, else, what should be then?
Distribution: Emacs and linux is its device driver(Slackware,redhat)
you have to create a sym link if you are using gnome and kde find the file you want to link and right click it then choose create link or some think like that i am not using both so i am not sure the name but i know there is a entry like that then drag and drop it where you want to link it
1. If this is a program that you're running, you can create an alias in ~/.bashrc
2. But I think what you are doing is trying to change the default paths/or variables for already made scripts. See my earlier post: these names dont do much unless you know what they are exactly (for example your JAVA_HOME).
now, there are 2 ways:
you can try a
"export $JAVA_HOME=whatever this is supposed to be"
or try locating the oiginal/universal copy:
"grep JAVA_HOME /etc/"
then just edit the config file grep finds.
3. If there is no config file found, maybe variables like "JAVA_HOME" (again...I dont know how hava works) is set during install. then you'll ether have to go back to 2, or even more-so you may have to install from source, editing the make file before you compile.