fedora equivalent to setenv

preeteshbarretto · 02-22-2009, 10:57 AM

hi there is an application i am trying to install in fedora 10 , but i am getting an error saying that command does not exist .

this is the instruction that i am supposed to follow

Add the new directory to your path. If the directory, for example, is /home/tupac/codeploy, on tcsh, you execute the following commands:
setenv PATH /home/tupac/codeploy:$PATH
rehash

however the setenv doesnt seem to exist in the fedora library..so wats the alternative for this .??

and what do they mean by on tcsh ??

alan_ri · 02-22-2009, 11:11 AM

Tcsh is a shell,Linux distros use BASH shell by default.You can change shell in Linux with command;

Code:

$ chsh

or

Code:

$ ypchsh

Path to the shell is /bin/name _of _the_shell.

gergely89 · 02-22-2009, 09:24 PM

Writing in bash

Quote:

PATH=/home/tupac/codeploy:$PATH

should give the same result as tcsh's

Quote:

setenv PATH /home/tupac/codeploy:$PATH

linux

John VV · 02-22-2009, 10:41 PM

or in fedora open the file " .bash_profile " in your home folder and add /home/tupac/codeploy

Code:

# .bash_profile

# Get the aliases and functions
if [ -f ~/.bashrc ]; then
	. ~/.bashrc
fi

# User specific environment and startup programs
# --- edited for posting your path maybe different ---
PATH=$PATH:/sbin:/usr/bin:/usr/sbin:/home/tupac/codeploy:$HOME
export PATH

then logout and log back in

PTrenholme · 02-22-2009, 11:52 PM

Quote:

Originally Posted by John VV

... then logout and log back in

In case that wasn't clear, I think he means "Start a new terminal session," not "Reboot" or "Restart the X-server"

And the tcsh is available in the Fedora repositories. Try a sudo yum install tcsh and then you should be able to use that as your shell instead of bash. You can use the login manager to reset your default shell.

John VV · 02-23-2009, 12:44 AM

no I MEANT log out of gnome and log back in to gnome ( or restart x ) that way the .bash_profile will be READ again

PTrenholme · 02-23-2009, 10:29 AM

John, the .bash_profile is read when you start a bash shell, and the X-server is not a shell script. In any case the X-server is (usually) a root process so changes to ~/.bash_profile or ~/.bashrc in a user's directory would have no effect on the way the X-server works.

For what the OP want's to do, a local shell ("terminal session") needs to be opened, and that's when the changes to the PATH variable need to be implemented.

If you want system-wide PATH changes, you can add them to /etc/rc.d/rc.local or change /etc/profile. (There has been some "rumbling" amongst the Fedora developers about adding the sbin directories to the user PATH since most of the restricted commands behave appropriately when started by a user without "root" privileges, but that "most" seems to be a "show stopper.")

i92guboj · 02-23-2009, 10:41 AM

Quote:

Originally Posted by PTrenholme

John, the .bash_profile is read when you start a bash shell, and the X-server is not a shell script. In any case the X-server is (usually) a root process so changes to ~/.bash_profile or ~/.bashrc in a user's directory would have no effect on the way the X-server works.

It all comes down at how do you login. The contents of /etc/profile will be sourced after init comes into scene, and thus, inherited by the rest of the bash sessions regardless of the user.

But if you login on command line then ~/.bash_profile will be sourced since you started a interactive login shell. Hence, when you later do startx and open a given terminal in X these settings will also be inherited. Of course you can also just forget about this, use plain ~/.bashrc and that path will be present in your xterms and such.

It just depends on what exactly do you want to do. Either way, it's a good idea to mark it to be exported so the rest of the programs can see the variable correctly.

Code:

export PATH="$PATH:/whatever/else"

To the original poster, this is a shell thing, not related to Fedora or any other distro. To get a complete list of the different rc files that a given shell uses you should look at its man page. For example, for bash you can find this info in the INVOCATION section of the bash man page.