Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

$PWD



Thank you for replying. Is this a BASH shell feature?

Subba Rao
subb3 at ibm.net
==============================================================
Disclaimer - I question and speak for myself.

http://pws.prserv.net/truemax/
______________________________________________________________

On Wed, 28 Jul 1999 17:24:43 -0400 (EDT), Derek Martin wrote:

>On Wed, 28 Jul 1999, Subba Rao wrote:
>
>> Yet, I can excute the programs in the current directory. When I run "echo $PATH", the "."
>> does not appear in the list.
>
>There are several possibilities.  When bash starts, it sources
>$HOME/.bash_profile if it is a login shell, or $HOME/.profile if
>.bash_profile doesn't exist.  Also all interactive bash shells (login or
>not) source /etc/bashrc and $HOME/.bashrc whenever a new copy of bash
>starts.
>
>Check these files.  Also, many people do not realize that if the path
>statement ends in a colon, it has the same effect as including . in your
>path, i.e.
>
>PATH=/bin:
>
>is the same as 
>
>PATH=/bin:.
>
>
>
>
>Derek D. Martin           |  UNIX System Administrator
>d_martin at worldnet.att.net |  dmartin at lancity.com
>
>



-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org