我应该编辑其中的哪一个文件来为我的普通用户和 root 定义 PATH 变量?
我已经以普通用户和 root 身份添加了它,但出现了如下所示的错误。
我在一个 Ubuntu 环境站点上看到现在可以使用 pam_environment。但是如何使用它来添加 ns 2.35 和 OMNET++ 的路径?我已经编辑了其中的一些,但不起作用。
我应该使用
gedit ~/.profile
或者
gedit ~/.bashrc
或者
gedit ~/.pam_environment
当我尝试使用它们添加我的 ns 和 OMNET 的路径时,我似乎弄乱了其中的一些。这两个程序一周前都在运行,但现在出现了这个错误。我需要使用其中任何一个,我的 ns 2.35 出现了这个错误:
The program 'ns' is currently not installed. You can install it by typing:
sudo apt-get install ns2
Omnettpp 也出现同样的错误。
echo $PATH
运行后sudo su
给出:
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/sbin:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix:/root/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/sbin:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix
根据评论的要求输出:
root@MQMK-Lenovo-G555:/home/johna# gedit ~/.bashrc
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples
# If not running interactively, don't do anything
[ -z "$PS1" ] && return
# don't put duplicate lines in the history. See bash(1) for more options
# ... or force ignoredups and ignorespace
HISTCONTROL=ignoredups:ignorespace
# append to the history file, don't overwrite it
shopt -s histappend
# for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
HISTSIZE=1000
HISTFILESIZE=2000
# check the window size after each command and, if necessary,
# update the values of LINES and COLUMNS.
shopt -s checkwinsize
# make less more friendly for non-text input files, see lesspipe(1)
[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)"
# set variable identifying the chroot you work in (used in the prompt below)
if [ -z "$debian_chroot" ] && [ -r /etc/debian_chroot ]; then
debian_chroot=$(cat /etc/debian_chroot)
fi
# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color) color_prompt=yes;;
esac
# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes
if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi
if [ "$color_prompt" = yes ]; then
PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '
else
PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ '
fi
unset color_prompt force_color_prompt
# If this is an xterm set the title to user@host:dir
case "$TERM" in
xterm*|rxvt*)
PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1"
;;
*)
;;
esac
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
#alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
# some more ls aliases
alias ll='ls -alF'
alias la='ls -A'
alias l='ls -CF'
# Alias definitions.
# You may want to put all your additions into a separate file like
# ~/.bash_aliases, instead of adding them here directly.
# See /usr/share/doc/bash-doc/examples in the bash-doc package.
if [ -f ~/.bash_aliases ]; then
. ~/.bash_aliases
fi
# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then
. /etc/bash_completion
fi
export PATH=$PATH:$HOME/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/sbin:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix:/root/johna/omnetpp-4.2.2/bin:/root/johna/ns-allinone-2.35/bin:/root/johna/ns-allinone-2.35/tcl8.5.10/unix:/root/johna/ns-allinone-2.35/tk8.5.10/unix
export PATH=$PATH:$HOME/johna/omnetpp-4.2.2/bin
export TCL_LIBRARY=/usr/share/tcltk/tcl8.5
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/johna/omnetpp-4.2.2/lib
export LD_LIBRARY_PATH=/home/johna/omnetpp-4.2.2/lib
export PATH=$PATH:$HOME/johna/ns-allinone-2.35/bin
export PATH=$PATH:$HOME/johna/ns-allinone-2.35/tcl8.5.10/unix
export PATH=$PATH:$HOME/johna/ns-allinone-2.35/tk8.5.10/unix
export LD_LIBRARY_PATH=/home/johna/ns-allinone-2.35/lib
export LD_LIBRARY_PATH=/home/johna/ns-allinone-2.35/otcl-1.14
export TCL_LIBRARY=/home/johna/ns-allinone-2.35/tcl8.5.10/library
答案1
这取决于你想达到什么目的。
profile
文件在您登录 shell 时执行(例如,当您登录 tty1 或通过 SSH 时),而bashrc
文件仅在启动交互式 shell(例如,打开一个新终端)时执行,并且仅由 bash(默认 shell)读取。
因此,如果您要在本地和交互式终端(“终端”应用程序)中使用这些应用程序,则可以在 bashrc 中设置 $PATH。
还请注意,.bashrc
/.profile
仅由当前用户使用。因此,如果您使用,sudo
您将获得正确的行为,但如果您使用其他用户,则 PATH 不会被修改:
➜ sudo -i
[sudo] password for <username>:
root@Salem:~# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
如果您希望在系统范围内添加该内容(在每个用户的 PATH 中),则要编辑的正确文件应该是/etc/profile
和/etc/bash.bashrc
。
希望能帮助到你。