Could you send us the output of the following command. Log onto your
CentOS 5 guest and type:
set | grep FSL
If you are sourcing (which means executing the commands in the current
shell) correctly then we should see a number of variables starting
with FSL.
Dave Flitney, IT Manager
University of Oxford, FMRIB Centre
JR Hospital, Oxford OX3 9DU
T: 01865 222713 F: 01865 222717
On 29 Jan 2010, at 18:03, Jeff Eriksen <[log in to unmask]> wrote:
> Rolf,
>
> Thanks for your help. Per your suggestion I am able to temporarily
> change the
> variable at the command line, see my other comments below.
>
> -Jeff
>
> On Wed, 27 Jan 2010 23:33:09 +0000, Rolf Heckemann
> <[log in to unmask]> wrote:
>
>> Hi Jeff
>>
>> It sounds like you are using bash on Linux. (It's generally useful
>> to
>> mention such things when asking for help.)
>>
> Sorry, I should described my environment: Windows XP host, VMware
> Player,
> CentOS5 guest OS. And that I am a Linux novice.
>>
>> Perhaps you aren't sourcing the file properly. In bash, this is
>> achieved with
>>
>> . ${FSLDIR}/etc/fsl/fsl.sh
>>
>> Note that this is "period space dollar" and the FSLDIR variable needs
>> to be correctly set -- otherwise replace the whole path expression
>> with the actual path name on your system. Sourcing the default
>> fsl.sh
>> also sources the one you've created in $HOME/.fslconf/
>>
> I do not understand what you mean by "source the file". I have seen
> the
> phrase a few times, but cannot quite get the concept. FSLDIR is
> correct
> based on echoing it, and the fact that fsl and the other tools run
> from
> anywhere.
>
>> As superuser, you should definitely be able to modify the file
>> (although it is not recommended). If you can't, there must be a
>> deeper problem with your FSL or system installation.
>
> Seems like it.
>
>> See how it goes and let us know if you need more input.
> It appears that I do.
>
