Date: 16 Dec 2001 18:51:08 -0500 From: Joe Clarke <marcus@marcuscom.com> To: hjs <hjs@thestof.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Strange Behaviour 'ls' Message-ID: <1008546669.9611.8.camel@shumai.marcuscom.com> In-Reply-To: <9vjbf8$ku7$1@news1.xs4all.nl> References: <9vjbf8$ku7$1@news1.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2001-12-16 at 18:41, hjs wrote: > Cliff, > > The commands you provided me produce the following output: > > bash-2.04$ type ls > ls is /bin/ls > bash-2.04$ file /bin/ls > /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), > dynamically linked, not stripped That's odd. Everything in /bin and /sbin should be statitcally linked since those tools are needed to boot or recover a system before /usr (and the linker and shared objects) are mounted. Have you replaced /bin/ls with something like gnuls or colorls? Has someone perhaps hacked your machine, and replaced ls with a malicious tool? My ls on 4.4-stable built last night looks like: # file /bin/ls /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped # cksum /bin/ls 2143685499 294300 /bin/ls From 4.4-RELEASE: # file /bin/ls /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped # cksum /bin/ls 3683638805 294300 /bin/ls Sorry, I don't have a 4.2 machine to compare for you. Have a look at your ls. If you have another working 4.2 box, compare the checksums. Joe > > > Thank you for your prompt response. > > Kind Regards, > Stof > > > "Cliff Sarginson" <cliff@raggedclown.NET> wrote in message > news:list.freebsd.questions#20011216231020.GA5431@raggedclown.net... > > On Sun, Dec 16, 2001 at 11:20:26PM +0100, hjs wrote: > > > Hi, > > > > > > For some reason ls is not behaving anymore as I am used to. > > > Whenever I run ls without any parameters all output is sent to one line > that > > > is wrapped at the edges of my screen. Whenever I provide parameters > > > (like -al) I don't get any output whatsoever. I can't even get it to > > > generate an error message by providing unused parameters. > > > > > > Does anyone have an idea on what I might have done to get my system to > > > behave like this and more important, how can I get ls to behave like the > out > > > of the box bhaviour again? > > > > > > I am running FreeBSD 4.2 and a bash shell. > > > > > Sounds like the "ls" you are running is not the real "ls". > > Send output from: > > > > type ls > > > > That tells you where ls, then get the output from the command > > > > file path_to_ls > > > > Where path_to_ls is what "type" tells you. > > and send that as well. > > > > > > -- > > Regards > > Cliff > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1008546669.9611.8.camel>