From owner-freebsd-questions Mon Jan 7 4:23:32 2002 Delivered-To: freebsd-questions@freebsd.org Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by hub.freebsd.org (Postfix) with ESMTP id 4C42B37B422 for ; Mon, 7 Jan 2002 04:23:25 -0800 (PST) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Mon, 7 Jan 2002 12:23:16 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 16NYlX-0003Z9-00; Mon, 07 Jan 2002 12:20:35 +0000 Date: Mon, 7 Jan 2002 12:20:35 +0000 (GMT) From: Jan Grant X-X-Sender: To: Charles Burns Cc: questions Subject: Re: The only way I have ever found to crash FreeBSD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 7 Jan 2002, Charles Burns wrote: > The only way that I have found to crash FreeBSD is to run a Linux program > with statically linked binaries. Am am curious as to why this happens, if it > still does as I have not tried since 4.4-Release, and I am wondering if > there is a way to prevent this from occuring if the Linux executable's > library linkage is not known. Ensure the executable is appropriately branded. If this problem is repeatable, then you should file a PR (userland programs shouldn't be able to crash the machine). Include the name of the linux binary you're using. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk ...You're visualising the _duck_ taped over my _mouth_..? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message