Re: Effect of `export PATH' not pemanent?

2006-05-12 Thread Clive Menzies
On (12/05/06 11:13), Rodolfo Medina wrote:
 Hi.
 
 I do:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 , then
 
 $ export PATH=$PATH:/sbin
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin
 
 and everything all right; but the effect of `export PATH'
 is not permanent: after a while, or in another terminal, again:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 . How to make the effect of `export PATH' permanent,
 and why is it not?

Check out .bashrc and .bash_profile in your home directory.  See man
bash

Regards

Clive

-- 
www.clivemenzies.co.uk ...
...strategies for business



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Effect of `export PATH' not pemanent?

2006-05-12 Thread Digby Tarvin
On Fri, May 12, 2006 at 11:13:15AM +0200, Rodolfo Medina wrote:
 Hi.
 
 I do:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 , then
 
 $ export PATH=$PATH:/sbin
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin
 
 and everything all right; but the effect of `export PATH'
 is not permanent: after a while, or in another terminal, again:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 . How to make the effect of `export PATH' permanent,
 and why is it not?

You are making a change to the shell's environment which will
effect all of its subsequent descendants, but not processes
started either before the change or by ancestors (such as your
window manager..) - and certainly not for a different login
session.

To make it permanent and apply to all of your shells, you need
to modify the command files that are executed when you login or
when each new shell starts. Check the man page appropriate for
your chosen shell for details.

Regards,
DigbyT
-- 
Digby R. S. Tarvin  digbyt(at)digbyt.com
http://www.digbyt.com


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Effect of `export PATH' not pemanent?

2006-05-12 Thread Adam Funk
On 2006-05-12, Rodolfo Medina [EMAIL PROTECTED] wrote:

 $ export PATH=$PATH:/sbin
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin

 and everything all right; but the effect of `export PATH'
 is not permanent: after a while, or in another terminal, again:

 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games

 . How to make the effect of `export PATH' permanent,
 and why is it not?

Put

export PATH=$PATH:/sbin

in your ~/.bashrc file.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Effect of `export PATH' not pemanent?

2006-05-12 Thread Ron Johnson
On Fri, 2006-05-12 at 11:13 +0200, Rodolfo Medina wrote:
 Hi.
 
 I do:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 , then
 
 $ export PATH=$PATH:/sbin
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin
 
 and everything all right; but the effect of `export PATH'
 is not permanent: after a while, or in another terminal, again:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 . How to make the effect of `export PATH' permanent,
 and why is it not?

You are confusing permanent with spanning processes.  Unix (or
is it Shell?) won't let you affect other process' symbol space.

As others have written, each shell instance must export PATH.

-- 
-
Ron Johnson, Jr.
Jefferson, LA USA

HELP: The feature that assists in generating more questions.
When the Help feature is used correctly, users are able to
navigate through a series of Help screens and end up where they
started from without learning a damn thing.
Computer Definitions


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: Effect of `export PATH' not pemanent?

2006-05-12 Thread Rodolfo Medina
Rodolfo Medina wrote:

 I do:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 , then
 
 $ export PATH=$PATH:/sbin
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games:/sbin
 
 and everything all right; but the effect of `export PATH'
 is not permanent: after a while, or in another terminal, again:
 
 $ echo $PATH
 /usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games
 
 . How to make the effect of `export PATH' permanent,
 and why is it not?



Clive Menzies wrote:

 Check out .bashrc and .bash_profile in your home directory.  See man
 bash



Digby R. S. Tarvin wrote:

 You are making a change to the shell's environment which will
 effect all of its subsequent descendants, but not processes
 started either before the change or by ancestors (such as your
 window manager..) - and certainly not for a different login
 session.

 To make it permanent and apply to all of your shells, you need
 to modify the command files that are executed when you login or
 when each new shell starts. Check the man page appropriate for
 your chosen shell for details.


Adam Funk [EMAIL PROTECTED] writes:

 Put

 export PATH=$PATH:/sbin

 in your ~/.bashrc file.


Ron Johnson [EMAIL PROTECTED] writes:

 You are confusing permanent with spanning processes.  Unix (or
 is it Shell?) won't let you affect other process' symbol space.

 As others have written, each shell instance must export PATH.



Thanks to all for your help.
Cheers,
Rodolfo


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]