Hi,
Are you sure, that bot files, .bashrc and .bash_profile, contain the
lines? .bash_profile is only used when you log in. So if everything is
set there correctly, but you did not relog, it might be, that the
configuration is not active, unless you source it manually. So, does
this problem persist, after you logged out and in again?
wolf
> Hello gurus, I am having a problem with getting FSL to run from startup on Ubuntu 11.04 (although had similar problem with CentOS through VMWare)
> Here is my problem. I am able to follow the nice step by step for installing FSL in linux using the fsl_installer.sh script. No glitches. However
> when I enter command fsl in terminal, the command is not found. So first thought was the program was not sourced. So I sourced both
> the .bashrc and the .bash_profile file created during installation. Here are what the files both read ("code 1"):
>
> "code 1"
> # FSL Configuration
> FSLDIR=/usr/local/fsl
> . ${FSLDIR}/etc/fslconf/fsl.sh
> PATH=${FSLDIR}/bin:${PATH}
> export FSLDIR PATH
>
> And I checked to make sure that the path was correct and the file was present, which it is. I also sourced both files and exited terminal.
>
> When I reenter terminal and enter command fsl, command not found.
>
> So then I wanted to make sure fsl was working properly. So I navigate to the directory containing fsl, enter the code in "code 1" which sources
> fsl but only within that session. After sourcing it, then I entered command "fsl" and the program opens just fine.
> So I close the program, exit the terminal, reenter the terminal, enter command "fsl" and the command cannot be found.
>
> So it appears that the program is working fine, but the program is NOT properly sourced so a new session can access the program.
>
> Then I wanted to make sure the path was correct, so I entered echo $PATH and got the following output:
>
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
>
> So this makes it clear that the directory /usr/local/fsl is not being added to the $PATH, I think this is the problem, but based on the
> information placed in BOTH the .bashrc and .bash_profile files, it SHOULD be adding it. I know there is a fix for this, it's the same for
> AFNI, I just cannot for the life of me remember it or fix it.
>
> Hope this is enough information to help! Thanks so much!
>
> Justin Perry
|