ls * problem

[Will Mc Donald]

I really wouldn't recommend removing fileutils. It's not just ls that's in there.

It definately looks like it's the shell, not ls itself. I don't really know csh at all but are the profiles and rc files the same between the working and non working machines? Can you give us a listing of all the filenames returned by running "ls -al" using bash? 


----- Original Message ----- 
From: <Andrew.Bridgeman at corusgroup.com>
To: "Will Mc Donald" <wmcdonald at ntlworld.com>; "General Red Hat Linux discussion list" <redhat-list at redhat.com>
Sent: Tuesday, June 29, 2004 10:22 AM
Subject: Re: ls * problem


> 
> 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?
>