From owner-freebsd-questions Sun Dec 16 16:18:37 2001 Delivered-To: freebsd-questions@freebsd.org Received: from thestof.com (hjs.xs4all.nl [194.109.251.144]) by hub.freebsd.org (Postfix) with ESMTP id 6295337B405 for ; Sun, 16 Dec 2001 16:18:30 -0800 (PST) Received: from p417 (unknown [192.168.140.102]) by thestof.com (Postfix) with SMTP id BA3E030702; Mon, 17 Dec 2001 01:17:37 +0100 (CET) From: "Stofregen, H.J." To: "Joe Clarke" Cc: Subject: RE: Strange Behaviour 'ls' Date: Mon, 17 Dec 2001 01:18:28 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <1008548003.9611.12.camel@shumai.marcuscom.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Confirmed. Thank you for all your help. The system is working again. fyi, the info on a FreeBSD system on ls is as follows: su-2.04# file /bin/ls /bin/ls: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), statically linked, stripped su-2.04# cksum /bin/ls 32256214 292604 /bin/ls Kind Regards, Stof -----Original Message----- From: Joe Clarke [mailto:marcus@marcuscom.com] Sent: Monday, December 17, 2001 1:13 To: Stofregen, H.J. Cc: freebsd-questions@FreeBSD.ORG Subject: RE: Strange Behaviour 'ls' On Sun, 2001-12-16 at 19:01, Stofregen, H.J. wrote: > Joe, > > Unfortunately I don't have another 4.2 system. Would you have an idea on how > I would build a fresh ls? > > Should I go to /usr/src/bin/ls and do > make depend && make && make install That will work. Joe > > I found the following tree on my HDD: > /usr/src/bin/ls > /usr/src/bin/ls/Makefile > /usr/src/bin/ls/cmp.c > /usr/src/bin/ls/extern.h > /usr/src/bin/ls/ls.1 > /usr/src/bin/ls/ls.c > /usr/src/bin/ls/ls.h > /usr/src/bin/ls/print.c > /usr/src/bin/ls/util.c > > > Kind Regards, > Stof > > -----Original Message----- > From: Joe Clarke [mailto:marcus@marcuscom.com] > Sent: Monday, December 17, 2001 0:51 > To: hjs > Cc: freebsd-questions@FreeBSD.ORG > Subject: Re: Strange Behaviour 'ls' > > > 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" 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