ls * problem

[Jurvis LaSalle]

On Jun 29, 2004, at 10:49 AM, Vidiot wrote:

>> Thanks for the reply. I have just checked the things you recommended 
>> the
>> text is below:
>>
>> echo $SHELL = tcsh
>> echo * = No Match
>> echo = no output at all
>> rpm -qf `which ls` = fileutils-4.1-10  ( when i run this on the 
>> machines
>> that work i get an output of "--color=tty: unknown option" )
>> md5sum `which ls` = 69ee580c4bd6afa63aed49076c535f62  /bin/ls (  when 
>> i run
>> this on the machines that works i get an output " md5sum:unrecognised
>> option `--color=tty`)
>>
>> I seem to get more errors as above with the machines that have not 
>> got this
>> "No Match" error problem.
>>
>> When i change to a bash shell and then run ls * it shows the files as
>> expected but when i change to csh i get the same "No Match" error.
>>
>> What would happen if i got rid of the fileutils package from the 
>> machines
>> that do not work currently, to see if this fixes the problem?
>>
>> Any more ideas?
>
> Ya, it sounds like you have the ls command alias'd, and alias'd wrong 
> to
> the point that the * wildcard isn't being passed correctly.
>
> What happens when you do "/bin/ls -l *"?
>
> If that works, you definately have an alias problem.  What happens when
> you enter "alias ls"?  Look in your .cshrc file an see if ls is 
> alias'd.
>
> MB
> -- 
> e-mail: vidiot at vidiot.com                                /~\ The ASCII
>                                                          \ / Ribbon 
> Campaign
> [So it's true, scythe matters.  Willow  5/12/03]          X  Against
> Visit - URL: http://vidiot.com/                          / \ HTML Email

I'm with Vidiot on this one.  To bypass aliased system commands in 
[t]csh escape the command with a dos-slash like so-

\ls *

hope this does it,
Jurvis LaSalle