PATH update

nedzer · 12-08-2008, 08:20 AM

Hi,

installing a qtjambi package and the following message appears

[root@moran qtjambi-linux32-gpl-4.4.3_01]# ./qtjambi.sh
Qt Jambi requires Java version 1.5.0 or higher to be preinstalled
to work. If Java is installed then make sure that the 'java' executable
is available in the PATH environment.

I've looked up the Sun site to get this advice ""

"% /home/myuser/jwsdp-2.0/jwsdp-shared/bin/startup.sh
It's useful to set the PATH permanently so it will persist after rebooting. To set the PATH permanently, add the full path of the bin directory in the Java WSDP installation directory to the beginning of your PATH variable. Typically this full path looks something like /home/myuser/jwsdp-2.0/jwsdp-shared/bin."

I don't have any 'jwsdp-2.0' I presume this is an older version of java?

my java is at
/usr/java/jre1.6.0_10/bin

firefox version is 3.0.4

I don't have a notion what the Java WSDP is. is it jre1.6.0_10?

Where can I set the PATH variable?

Thanks in advance

onebuck · 12-08-2008, 08:30 AM

Hi,

I like to setup my '.bashrc' and '.bash_profile' to reflect my needs.

Code:

:~$ cat .bash_profile
# .bash_profile
#08-30-06 12:18 copied loki:/home/gws

# Source .bashrc
if [ -f ~/.bashrc ]; then
        . ~/.bashrc
fi

Code:

~$ cat .bashrc
#.bashrc
#08-30-06 12:17 gws copied loki:/home/gws
# Add bin to path
export PATH="$PATH:$HOME/bin"

# Dynamic resizing
shopt -s checkwinsize

# Custom prompt
#
PS1='\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '

#08-29-06 11:40 gws

#if [ `id -un` = root ]; then
#  PS1='\[\033[1;31m\]\h:\w\$\[\033[0m\] '
# else
#  PS1='\[\033[1;32m\]\h:\w\$\[\033[0m\] '
#fi
# Add color
eval `dircolors -b`

# User defined aliases
alias cls='clear'
alias clls='clear; ls'
alias ll='ls -l'
alias lsa='ls -A'
alias lsg='ls | grep'
alias na='nano'
alias web='links -g -download-dir ~/ www.google.com'

#08-29-06 11:45 gws
#To clean this up and cover your tracks once you log off

#Depending on your version of BASH, you might have to use
# the other form of this command
  trap "rm -f ~$LOGNAME/.bash_history" 0

#The older KSH-style form
#  trap 0 rm -f ~$LOGNAME/.bash_history

You can adapt or change the PATH in the '.bashrc' to reflect your needs for a user. Setting up other conditions can assist the needs of a user that will use the 'cli'. Alias is a good thing to assist one when they are working from the 'cli' with repeated commands.