Date: Mon, 17 Dec 2001 00:41:25 +0100 From: "hjs" <hjs@thestof.com> To: freebsd-questions@freebsd.org Subject: Re: Strange Behaviour 'ls' Message-ID: <9vjbf8$ku7$1@news1.xs4all.nl> In-Reply-To: <20011216231020.GA5431@raggedclown.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9vjbf8$ku7$1>