Problem with Terminal

[BorkoF]

I have problem with Terminal. When i poweron computer Terminal works perfect. After logOut and then logIN troubles with Terminal begins. This is an example of problem:

[borko@teky ~]$ gedit
[borko@teky ~]$ su -
Password:
-bash: id: command not found
bash: uname: command not found...
-bash: [: =: unary operator expected
bash: ls: command not found...
Similar command is: 'lz'
bash: tty: command not found...
Similar command is: 'tty'
[root@teky ~]# gedit
bash: gedit: command not found...
[root@teky ~]#

[sea]

Whats the output of:

# echo $PATH
# env
# dmesg | grep EE

The #'s indicate that the cmds should be executed as root.

Maybe either, roots .bashrc or even /etc/bashrc got invalid values in it, causing these issues.

[BorkoF]

I got this output:

[root@teky ~]# echo $PATH
/usr/local/sbin:/usr/sbin:/sbin:$PATH:"/usr/local/bin/apache-maven-2.2.1/bin":/root/bin:/opt/Java/jdk1.7.0_02/bin

[root@teky ~]# dmesg | grep EE
bash: grep: command not found...
bash: dmesg: command not found...
Similar command is: 'mesg'
[root@teky ~]#

[sea]

If i see this properly, you're PATH variable is missing /bin
For now, try this:

# PATH=$PATH:/bin
# export PATH

Then try again, ls, or the above commands.

[BorkoF]

[root@teky ~]# echo $PATH
/usr/local/sbin:/usr/sbin:/sbin:$PATH:"/usr/local/bin/apache-maven-2.2.1/bin":/root/bin:/opt/Java/jdk1.7.0_02/bin
[root@teky ~]# dmesg | grep EE
bash: dmesg: command not found...
Similar command is: 'mesg'
bash: grep: command not found...
[root@teky ~]#

I executed your commands but nothing changes. I will try again.

[root@teky ~]# PATH=$PATH:/bin
[root@teky ~]# export PATH
[root@teky ~]# echo $PATH
/usr/local/sbin:/usr/sbin:/sbin:$PATH:"/usr/local/bin/apache-maven-2.2.1/bin":/root/bin:/opt/Java/jdk1.7.0_02/bin:/bin
[root@teky ~]#

[sea]

It didnt add the /bin yet...

[root@nc210 collection]# PATH=$PATH:/bin
[root@nc210 collection]# export PATH

Try again

[BorkoF]

Same problem again

[sea]

Originally Posted by BorkoF

/usr/local/sbin:/usr/sbin:/sbin:$PATH:"/usr/local/bin/apache-maven-2.2.1/bin":/root/bin:/opt/Java/jdk1.7.0_02/bin:/bin

Now it had applied it... still issues?

If so, please show the output of:

# cat /etc/bashrc
# cat ~/.bashrc
---- if that doesnt work ----
# /bin/cat /etc/bashrc
# /bin/cat ~/.bashrc

Please post these outputs in "Go Advanced" and use the Code tag (the bold #)

---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------

Other question...
Open a new terminal, and just go su, without the -.

$ su

$ indicates the command to be run as normal user.
Do you have the same error?

[BorkoF]

[root@teky ~]# /bin/cat /etc/bashrc
# /etc/bashrc

# System wide functions and aliases
# Environment stuff goes in /etc/profile

# It's NOT a good idea to change this file unless you know what you
# are doing. It's much better to create a custom.sh shell script in
# /etc/profile.d/ to make custom changes to your environment, as this
# will prevent the need for merging in future updates.

# are we an interactive shell?
if [ "$PS1" ]; then
  if [ -z "$PROMPT_COMMAND" ]; then
    case $TERM in
    xterm*)
      if [ -e /etc/sysconfig/bash-prompt-xterm ]; then
          PROMPT_COMMAND=/etc/sysconfig/bash-prompt-xterm
      else
          PROMPT_COMMAND='printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
      fi
      ;;
    screen)
      if [ -e /etc/sysconfig/bash-prompt-screen ]; then
          PROMPT_COMMAND=/etc/sysconfig/bash-prompt-screen
      else
          PROMPT_COMMAND='printf "\033]0;%s@%s:%s\033\\" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/~}"'
      fi
      ;;
    *)
      [ -e /etc/sysconfig/bash-prompt-default ] && PROMPT_COMMAND=/etc/sysconfig/bash-prompt-default
      ;;
    esac
  fi
  # Turn on checkwinsize
  shopt -s checkwinsize
  [ "$PS1" = "\\s-\\v\\\$ " ] && PS1="[\u@\h \W]\\$ "
  # You might want to have e.g. tty in prompt (e.g. more virtual machines)
  # and console windows
  # If you want to do so, just add e.g.
  # if [ "$PS1" ]; then
  #   PS1="[\u@\h:\l \W]\\$ "
  # fi
  # to your custom modification shell script in /etc/profile.d/ directory
fi

if ! shopt -q login_shell ; then # We're not a login shell
    # Need to redefine pathmunge, it get's undefined at the end of /etc/profile
    pathmunge () {
        case ":${PATH}:" in
            *:"$1":*)
                ;;
            *)
                if [ "$2" = "after" ] ; then
                    PATH=$PATH:$1
                else
                    PATH=$1:$PATH
                fi
        esac
    }

    # By default, we want umask to get set. This sets it for non-login shell.
    # Current threshold for system reserved uid/gids is 200
    # You could check uidgid reservation validity in
    # /usr/share/doc/setup-*/uidgid file
    if [ $UID -gt 199 ] && [ "`id -gn`" = "`id -un`" ]; then
       umask 002
    else
       umask 022
    fi

    # Only display echos from profile.d scripts if we are no login shell
    # and interactive - otherwise just process them to set envvars
    for i in /etc/profile.d/*.sh; do
        if [ -r "$i" ]; then
            if [ "$PS1" ]; then
                . "$i"
            else
                . "$i" >/dev/null 2>&1
            fi
        fi
    done

    unset i
    unset pathmunge
fi
# vim:ts=4:sw=4

then

[root@teky ~]# /bin/cat ~/.bashrc
# .bashrc

# User specific aliases and functions

alias rm='rm -i'
alias cp='cp -i'
alias mv='mv -i'

# Source global definitions
if [ -f /etc/bashrc ]; then
	. /etc/bashrc
fi

[borko@teky ~]$ su
Password: 
bash: uname: command not found
bash: [: =: unary operator expected
bash: ls: command not found
bash: tty: command not found
[root@teky borko]#

[sea]

Weird, one last shot for you to try:

# echo "PATH=/bin:\$PATH" >> ~/.bashrc

Then close ALL open terminals, open a new one and log into su...
Sorry but i cant think of anything else beeing the cause for this.

[BorkoF]

Can you sugest me one god book for Linux OS? I recently used Windows but i want to migrate to Linux using Fedora 16.

I'm Sowtware Developer and i need to know advanced features, not only to deal witn basic thinks.

---------- Post added at 03:01 PM ---------- Previous post was at 02:58 PM ----------

[borko@teky ~]$ su
Password: 
bash: uname: command not found
bash: [: =: unary operator expected
bash: ls: command not found
bash: tty: command not found

Thanks man for helping me

[sea]

You're a dev?
My hint, give yourself 1 month, where you just break your linux system (by will), and set it up again.
I've learned quite a few things that way
IMHO the power of linux is the terminal, by that i mean bash and scripts


Either way, http://tldp.org/ is the only one i currently recall..
"man COMMAND" is also a very good resource, or
"COMMAND --help" as well.
Most things you'll use are located in:
/bin , /usr/bin
Root/admin things are located in:
/sbin , /usr/sbin


EDIT:
Sorry dude, i couldnt help solve it

[jpollard]

You can use almost any UNIX based book. for a bash introduction you can try:

http://tldp.org/LDP/Bash-Beginners-Guide/html/

Now, directly, your problem is in the environment variable PATH.

You show the value being:
/usr/local/sbin:/usr/sbin:/sbin:$PATH:"/usr/local/bin/apache-maven-2.2.1/bin":/root/bin:/opt/Java/jdk1.7.0_02/bin

The short answer is that it is incorrect.

I don't know where you modified an initialization script (.profile, .bashrc, or maybe /etc/profile).

The PATH environment variable is a list of directory paths to be used to locate a command. Each entry in the list is separated by a ":" character.

Your path has double quotes included, and invalid characters...
There is no path named $PATH.. This likely got included because of the use of single quotes somewhere that blocked the expansion of $PATH to be the existing path list.

There is also no path "/usr/local/bin/apache-maven-2.2.1/bin", as your entry starts with the double quote. That is not a directory name as it is a "special character". It likely got in there the same time as the $PATH portion as otherwise the double quotes might have been taken as meaning quote the value between the double quotes.

As a last ditch workaround (which will go away when you log out/close the terminal window, and is only good for the terminal/terminal window this is done):

PATH=/usr/bin:/bin:/usr/local/bin
export PATH

In the preceding samples, you were shown to put $PATH in the value of the assignment - don't do that.... In your case it will only include the errors at another level. You MIGHT be able to get around that by putting the $PATH at the end... but that would be because it never tries to use the entries.

This will set the path, and allow most of the commands you expect.

If you have goobered your root login at the same time (and with the same error), then it implies that you modified /etc/profile with the incorrect strings. The easiest way to fix that is to login through a console terminal (alt f2 through f6, one should present a login prompt) login as root, then rename /etc/profile to something like /etc/profile.save. You should now be able to switch back to a GUI and login with a MINIMAL path environment, and use a GUI based editor. You could edit the file immediately if you are familiar with a text/command line based editor (such as vi), and fix the problem immediately.

You can still use the commands you want, even without this - but you have to put the full path to the command.

Where the error is

[PabloTwo]

/bin/cp /etc/skel/.bash* /home/borko/

Then log out and log back in.
You clobbered up your $PATH environment pretty badly. Do it right the next time.

[BorkoF]

Ty all for helping me. I decided to reinstall fedora 16. So now is all ok

This help is usefull for future use of fedora. Ty all.