02-23-2012
Thanks Corona688
Thank you, Corona688. I think your explanation covered every base I could expect to find in such a complicated concept. I will have to woodshed a bit at this point to truly understand what you said. Because you pointed me in the right directions as far as what to look at as well as the concept behind a very dynamic path variable, I will be able to eventually understand. Thanks!
---------- Post updated at 06:14 PM ---------- Previous update was at 05:57 PM ----------
Edit: I found what seems to be a comprehensive explanation of how PATH is constructed, at least in MAC OSX 10.5 and up. This link below explains that a script called path_helper located in /etc/profile looks at text files in /etc to construct the PATH and MANPATH variables.
softec.lu/site/DevelopersCorner/MasteringThePathHelper
Last edited by Alexander4444; 02-26-2012 at 06:19 PM..
Reason: help poster
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
I'm trying to add my bin directory to my path by editing the .bash_profile. I'm adding the following:
PATH=$HOME/bin
But then when I type in "echo $PATH" my bin directory is not added. Do I need to do something to make this take affect or am I going about this wrong. :confused: ... (9 Replies)
Discussion started by: Atama
9 Replies
2. UNIX for Dummies Questions & Answers
Dear experts,
I have installed Ruby in the following directory:
$ pwd
/home/ewijaya/.ruby
$ ls
bin lib share
And I have also stated the PATH in my bash_profile like this:
# .bash_profile
# Get the aliases and functions
if ; then
. ~/.bashrc (1 Reply)
Discussion started by: monkfan
1 Replies
3. Solaris
Hi all,
I downloaded a tarball of coreutils ....
extracted only to find out that i had to build it...
But when i executed ./configure, this is what i got
checking build system type... i386-pc-solaris2.11
checking host system type... i386-pc-solaris2.11
configure: autobuild project... GNU... (2 Replies)
Discussion started by: wrapster
2 Replies
4. Shell Programming and Scripting
Hi Guys,
I modified my .bash_profile script , and tried to change the prompt.
Following is the line of code in my .bash_profile script.
export PS1=" \W "
But I get the output as:
\W
This appears to be my prompt now.
Any idea what should be done..
Thanks! (0 Replies)
Discussion started by: nua7
0 Replies
5. Solaris
At work, I'm in a Solaris environment working with csh, and $PATH is populated with anywhere between 10 and 20 entries.
Last week, every command I issued (even "ls") took several seconds, if not an entire minute, to run. Once I moved "/home/sybase/bin" to the end of $PATH, certain commands... (2 Replies)
Discussion started by: acheong87
2 Replies
6. Solaris
When i configure apache(2.2.15) on solaris-8 server it producing following error
<configure: error: no acceptable ld found in $PATH
configure failed for srclib/apr >
please help me any to fix this error.
:confused:
---------- Post updated at 09:44 PM ---------- Previous update was... (0 Replies)
Discussion started by: kalpeer
0 Replies
7. UNIX for Advanced & Expert Users
Hi,
happy new year.
on AIX 6.1 , for user oracle , there are two files :
bash_profile and .profile
I do not know which one is executed when login ? How to know ,
More over in both of them we have :
in .profile :
ORACLE_HOME=/appli/oracle/product/10.2.0/db_1... (5 Replies)
Discussion started by: big123456
5 Replies
8. Solaris
Hi,
One of our Solaris servers was peviously zoned and connected to 2 seperate arrays, one HP and the other EMC. The server is now only connected to the EMC. The sever has x2 single port HBA's.
When running cfgadm I see the following:
root@qwicprod /dev/rdsk]# cfgadm -al
Ap_Id Type... (6 Replies)
Discussion started by: jamba1
6 Replies
9. UNIX for Dummies Questions & Answers
Hello everyone,
I'm trying to set my .bash_profile to change my primary prompt from this:
banbatchtest1v:MCPPRD:~>to this:
banbatchtest1v:MCPPRD:/home/rcarvall>
Here's what my .bash_profile looks like right now:
# .bash_profile
# Get the aliases and functions
if ; then
.... (2 Replies)
Discussion started by: galileo1
2 Replies
10. Programming
Hello,
I am always confused about adding library path for ./configure when compiling software under Linux Debian based OS. For example the README of the software tells
--with-boost=PATH specify directory for the boost header files
--with-mpi=PATH specify prefix directory for... (4 Replies)
Discussion started by: yifangt
4 Replies
LEARN ABOUT DEBIAN
envpath
ENVPATH(1p) User Contributed Perl Documentation ENVPATH(1p)
NAME
envpath - Advanced operations on path variables
SYNOPSIS
Run this script with the "-help" option for usage details.
DESCRIPTION
Parses the command line, modifies the specified path variable(s), and execs the remaining arguments. There are two modes, simple and
advanced:
SIMPLE MODE
Simple mode presents an alternative, platform-independent syntax for specifying paths wherein the path separator is "," and environment
variables can be expanded with @NAME@. For example
envpath PATH=@PATH@,/usr/ucb -- printenv PATH
appends "/usr/ucb" to $PATH and execs printenv PATH. The "--" is optional.
You can also specify prepending or appending by using "+=" or "=+" respectively:
# place /usr/ucb at the front
envpath PATH+=/usr/ucb -- printenv PATH
# place /usr/ucb at the back
envpath PATH=+/usr/ucb -- printenv PATH
Simple mode requires only this script; it does not require Env::Path to be installed.
ADVANCED MODE
Advanced mode basically provides command-line access to the features of Env::Path (see), which must be installed. The "-E" flag selects the
path variable to operate on and other flags specify operations on it. E.g.
envpath -E MANPATH -A /tmp -R /usr/share/man -N -U -- man ...
would take MANPATH, append /tmp to it, remove any references to "/usr/share/man", remove any dirs which don't exist ("-N") and remove
redundant entries ("-U") before running man.
The -Whence option allows patterns. Thus
envpath -W "cat*"
would find all programs on PATH which match cat*.
CLEARCASE WINKINS
A big part of the motivation for this script was for use with ClearCase builds; iff you know or care about ClearCase read on. Typically,
during builds (and not just with ClearCase), pathvars such as PATH, CLASSPATH, and LD_LIBRARY_PATH must be strictly controlled. One choice
is to force static values of these into the environment during the build process, another is to simply require/expect users to set their
paths appropriately. Each of these can lead to subtle build or runtime errors, however, and makes it hard for new users to get up to speed
since their personal environment must be just so.
Another common choice is to use only full pathnames within the Makefile, avoiding reliance on search paths at all. This is often the best
way to go but can suppress ClearCase winkins. For example, say you're generating ascii files of some type with a binary executable you
just built:
$(INCDIR)/foo.h: $(BINDIR)/foomaker $(BINDIR)/foomaker ...
The problem with this is that $(BINDIR) likely contains a platform part such as 'solaris' or 'hpux', which makes it impossible to wink in
the foo.h file on other platforms even though it's ascii. This same thing could come up even with a standard pre-built utility that's in
different places on different platforms; "yacc", for instance, is in /usr/bin on Linux and /usr/ccs/bin on Solaris.
You could modify the path on the fly:
$(INCDIR)/foo.h: $(BINDIR)/foomaker PATH=$(BINDIR)$(SEP)$$PATH foomaker ...
but this suffers from the same problem: since $(BINDIR) and $PATH are expanded literally within the build script they'll suppress winkins.
Here's a solution using envpath:
$(INCDIR)/foo.h: $(BINDIR)/foomaker envpath PATH=@BINDIR@,@PATH@ foomaker ...
This hides the evaluation of BINDIR and PATH such that clearmake never sees anything but the literals, thus clearing the field for winkins.
Of course envpath is capable of doing more than this, but it's the original reason it was written.
AUTHOR
David Boyce <dsbperl AT boyski.com>
COPYRIGHT
Copyright (c) 2000-2001 David Boyce. All rights reserved. This Perl program is free software; you may redistribute and/or modify it under
the same terms as Perl itself.
SEE ALSO
perl(1), "perldoc Env::Path"
perl v5.10.1 2003-10-10 ENVPATH(1p)