Path: utzoo!utdoe!generic!pnet91!marekp
From: marekp@pnet91.cts.com (Marek Pawlowski)
Newsgroups: comp.sys.apple2
Subject: Re: Telnetting to IRC (Getting together)
Message-ID: <286@generic.UUCP>
Date: 16 Dec 90 14:50:12 GMT
Sender: root@generic.UUCP
Organization: People-Net [pnet91], Etobicoke, ON
Lines: 44

Wrong.

--

If your default shell is "sh" (aka the Bourne shell), the file called .profile
in your directory, will be the first one to be executed.

If your default shell is "csh" (ake the C-shell), the file called .login in
your directory, will be the first one executed.

The "path" or "PATH" shell variables, contains various directory names, which,
when a command is entered, will be searched through (in order of appearance)
for the specified binary.

Under sh, you would set it up like so:

PATH=/bin:/usr/bin:$HOME/bin:.          # set command search path

What this means, is that if the user types "ls", for example.  The system will
look in /bin first.  If "ls" is in there, it gets executed.  If not, it goes
on to /usr/bin, if not again, then it looks in the $HOME/bin directory.  And
if not, it will look in the current directory (=".") for this file.  If "ls"
wasn't found anywhere, you will be told so.

To add another path to this list (under the Bourne shell!) just add another
"field", separated from the rest with a colon.

Put that line in a file in your directory called .profile

For csh, it is a similar story:

set path = (/bin /usr/bin $home/bin .)  # execution search path

(BTW, anything following the number-sign, is a comment, and ignored).

Just two different ways of doing it.

I hope that helps!


/* Marek Pawlowski, marekp@{generic|pnet91|contact|bkj386|torag|aunix}.uucp */
/* President, Intelligent Twist Software, 250 Harding Blvd, PO BOX 32017    */
/* Richmond Hill, Ontario, L4C 9M7, CANADA.  An ideal route is as follows:  */
/* { Ph: (416) 884-4501 4-8pm EDT } generic!pnet91!marekp@zoo.toronto.edu   */