adding to $PATH

Tarts · 08-25-2003, 07:05 AM

Quote:

Originally posted by digiot
And not-reading all over the place. I missed your profile tip the first time around. Thanks.

Yeah - so I still don't get the paths and permissions things. *sigh* I think that's the thing that gives me the most headaches.

You have over 1000 post's, and there anything you don't understand. :) :)
What have you been waisting the bandwidth on. :) Alot of people like to spend their time in the general forum i noticed, you must be there? You don't have to answer if you don't want to, i don't want to probe.

slakmagik · 08-25-2003, 11:41 AM

Well, it's a thousand posts of 'LQ Addict', not 'Guru' - I never claimed to be anything other than a digital idiot. I did get curious about where I hung out and came up with this from the front pages of the forums.

Code:

Software	212 4/208
Newbie		204 1/203
Linux General	161 4/157
Slackware	153 0/153
General		145 2/143
Hardware	51  2/49
Quest&Suggest	27  4/23

Plus a few dribbled in other forums.

I don't know. I know about 5% of the Linux I want to know, if that. But there's a lot of people who might know more or less but don't know the same things. So I post what little I do know or I often try my best guess if I think it might help and probably wouldn't hurt. And then, yeah, I guess I must waste some bandwidth in there. I like to talk computers. But I learn a lot from surfing here and I'm 'addicted' to posting when I can participate or contribute while I learn. Figure it'd be a bigger waste of bandwidth to just reload pages and learn from the site and not give anything back and, as money's often hard to come by, I give words instead of dollars. But, yeah, probably too many words.

And I'm soo off topic. We now return you to your regularly scheduled thread, already in progress.

linuxJaver · 08-26-2003, 12:12 AM

Most important thing I've learnt from cooking the profile/resource file is:

Make clear wut the different between login shell, interactive shell, non interactive shell (like those invoked by the tool "make"
.
One of them read ~/.bashrc, the other not. Non interactive shell doesn't rematch aliasing pattern ..

See: man bash for more details ..

The other tip is "Making PATH redudance free":

Supposed u gonna add ~/bin to the PATH variable say add:

export PATH=~/bin:$PATH in ~/.bashrc

After modification of : ~/.bashrc or ~/.bash_profile

To make the modification take effect need to do
# source ~/.bashrc or ~/.bash_profile

Then check the content of $PATH by
# env | grep PATH or # echo $PATH

u ll see the content of the PATH enviroment variable something like:

PATH=/root/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/opt/kde/bin

The next time u source ~/.bashrc again ur path will content twice of the previous content (redudance).

The Tip is:
/etc/profile is the absolute Initialization of the PATH variable. So just modify ur ~/.bashrc or ~/.bash_profile to source the /etc/profile inside the script.

Then u ll get the absolute Initialization of the PATH, extention like PATH=$PATH:newPath will be redudance free after often source ..