UNIX for Dummies Questions & Answers

That's good.

Stupid question - if you do ls in your directory.. what do you see?

PN

If I type ls it lists all the scripts in the directory, including the Installs script.

I've made some progress. I created a .cshrc file in my home directory with the following contents copied off the solaris box (where the script works):

setenv run export/home/jack/run
source $run/case/scripts/Setup


I changed the run directory to match that on my open solaris VM. I then dumped out of the terminal and reloaded it (to source the .cshrc file). I then went from thr bash shell (which it starts in by default) to the c shell.
Now it recognises the script, but gives me the following error:

Code:

%Install
exec: tclsh: cannot execute [Exec format error]

Ben.

Ben,

This is strange. Exec format error usually means that the executable was compiled for a different hardware architecture. Like you try to execute file compiled for x86 on SPARC.

Since you can start tclsh successfully and the Tcl script is nothing but a text file the problem should not be in Tcl itself.

1. If you have a chance to play with this box you can try to run install directly from tclsh with use of source command.

Code:

$ tclsh
% source Install
.. ....  whatever the install does

2. Your script uses Bourne shell anyway since it starts with #!/bin/sh so you may change .bash_profile to reflect the same changes you did for .cshrc

To answer you original question where can you switch default command interpreter from bash to csh it's in /etc/passwd file. It is the last parameter in your user record.

Cheers,
PN.

Hello everyone, could it be related to a permissions issue?
I am on RHEL now and I see that, if a file has no execute permissions, it will not be auto-completed when pressing TAB.
touch filename generated filename with permissions 644 (RW-R--R--)
Changing the permissions to (e.g. 755, from 644, thus resulting in RWX-R-XR-X) allowed the file to be auto-completed when pressing TAB.

Please make sure that current directory "./" is part of your $PATH variable which set in the ~/.profile file.
If it is not, then:
1) add it at the beginning of the $PATH
2) execute .profile (in order to new environment to take effect)
3) try to run your script again.