From owner-freebsd-hackers Fri Sep 15 5:56:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id AC57E37B422 for ; Fri, 15 Sep 2000 05:56:28 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id QAA17273; Fri, 15 Sep 2000 16:56:19 +0400 (MSD) Message-Id: <200009151256.QAA17273@aaz.links.ru> Subject: Re: HELP: Disk/file-systems are loused up In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D78A6@l04.research.kpn.com> from "Koster, K.J." at "Sep 15, 0 08:48:04 am" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Fri, 15 Sep 2000 16:56:19 +0400 (MSD) Cc: gerald_stoller@hotmail.com, freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Koster, K.J. writes: > > I also think that the find program should be checked > > to see why it > > crashed and fix it to keep it from doing similarly in the > > future; I don't know whom to contact as yet. > No matter how broken, a program is unable to crash the OS (well, very, very > unlikely :). If you mount a broken filesystem, FreeBSD will die, find or no > find. I'll bet that you could 'cd' into the broken directory and do 'echo *' > to crash the box. It is very easy to crash the OS. ports/audio/dap for example. Or worst. try create 2 big slices of type 165 on one big (>10G?) disk. and write then read both labels. Yes, I understand that find program is not a key. -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message