LinuxQuestions.org - [SOLVED] how to resetting PATH in ubuntu 10.10

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - how to resetting PATH in ubuntu 10.10 (https://www.linuxquestions.org/questions/linux-general-1/how-to-resetting-path-in-ubuntu-10-10-a-4175423612/)

how to resetting PATH in ubuntu 10.10

Friends,

Recently I installed texlive2012 in home directory. Upon finish installing, I executed "texhash" command. After running this command, I can not execute any commands such as sed, awk, ls, or any other commands from my terminal. Even If I open new terminal the same result. (I also restarted this machine few time adn still the problem exist).

For example, if I execute "ls" I get message as below:

Quote:

vijay@glycomod:~$ ls
Command 'ls' is available in '/bin/ls'
The command could not be located because '/bin' is not included in the PATH environment variable.
ls: command not found
vijay@glycomod:~$

I can understand the path setting are missing but I do not know how to fix this.
Can anyone help to fix this?

Thank you.

Do you modify the path in .bashrc? If so please post this:

Code:

/bin/cat .bashrc

this is my .bashrc file

Code:



# ~/.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 -l'

#alias ll='ls -alF'

alias la='ls -A'

alias l='ls -CF'



# Add an "alert" alias for long running commands.  Use like so:

#  sleep 10; alert

alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"'



# 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



#########################################333

# AMBER installation



AMBERHOME=/usr/local/amber9

export AMBERHOME 



PATH=$PATH:$AMBERHOME/exe

export PATH





# For NAMD

# NAMD=/home/vijay/NAMD/NAMD_2.8_Source/Linux-x86_64-g++

NAMD=/usr/local/NAMD_2.8_Source/Linux-x86_64-g++

export NAMD



PATH=$PATH:$NAMD

export PATH



# for texlive2012



PATH=/home/vijay/.texlive2012-install/texlive/2012/texmf/doc/man  #to MANPATH, if not dynamically determined.

PATH=/home/vijay/.texlive2012-install/texlive/2012/texmf/doc/info #to INFOPATH.

PATH=/home/vijay/.texlive2012-install/texlive/2012/bin/x86_64-linux





##PATH=/usr/local/texlive/2012/bin/i386-linux:$PATH 

#PATH=/usr/local/texlive/2012/texmf/doc/man:$PATH  # to MANPATH.

#PATH=/usr/local/texlive/2012/texmf/doc/info:$PATH # to INFOPATH.

#PATH=/usr/local/texlive/2012/bin/x86_64-linux:$PATH

Quote:

Originally Posted by vjramana (Post 4762273)

PATH=/home/vijay/.texlive2012-install/texlive/2012/texmf/doc/man #to MANPATH, if not dynamically determined.
PATH=/home/vijay/.texlive2012-install/texlive/2012/texmf/doc/info #to INFOPATH.
PATH=/home/vijay/.texlive2012-install/texlive/2012/bin/x86_64-linux

These lines overwrite the PATH variable, try commenting them out to see if that fixes the problem

I have tried comment those lines but the problem still remains.

Post:

Code:

/bin/echo $PATH

Hi,

you won't really be able to do much until you reset your path. After that you can fix your .bashrc so that the path will be ok in new shells. Do the following in a terminal

Code:

echo $PATH

PATH="/usr/bin:/bin"

echo $PATH

Please post the output of the above so that we can see what is going on.

Now in the same terminal you can open your .bashrc in an editor and replace the texlive2012 lines with the following

Code:

export MANPATH=$HOME/.texlive2012-install/texlive/2012/texmf/doc/man #to MANPATH, if not dynamically determined.

export INFOPATH=$HOME/.texlive2012-install/texlive/2012/texmf/doc/info #to INFOPATH.

PATH="$PATH:$HOME/.texlive2012-install/texlive/2012/bin/x86_64-linux"

Now try opening an new terminal and check your path

Code:

echo $PATH

Evo2.

Hi,

Quote:

Originally Posted by byannoni (Post 4762606)

Post:

Code:

/bin/echo $PATH

while /bin/echo may exist, it is also a shell builtin so "echo $PATH" should work regardless of what PATH is set to.

Evo2.

Quote:

Originally Posted by evo2 (Post 4762646)

Hi,

while /bin/echo may exist, it is also a shell builtin so "echo $PATH" should work regardless of what PATH is set to.

Evo2.

Oh, that's good to know, thanks.