From owner-freebsd-questions Mon Jan 7 2:18:40 2002 Delivered-To: freebsd-questions@freebsd.org Received: from stereophonic.noops.org (adsl-63-195-97-84.dsl.snfc21.pacbell.net [63.195.97.84]) by hub.freebsd.org (Postfix) with SMTP id 606B937B417 for ; Mon, 7 Jan 2002 02:18:37 -0800 (PST) Received: (qmail 14115 invoked by uid 1000); 7 Jan 2002 10:18:37 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jan 2002 10:18:37 -0000 Date: Mon, 7 Jan 2002 02:18:37 -0800 (PST) From: Thomas Cannon To: Charles Burns Cc: Subject: Re: The only way I have ever found to crash FreeBSD In-Reply-To: Message-ID: <20020107021412.R13438-100000@stereophonic.noops.org> 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 I'd imagine (and freebsd-hackers could tell you better) that BSD is able to run linux binaries by using custom libraries, and when the linux program is compiled statically that there's a whole lot of resource problems as BSD tries to run code that it cannot (but believes that it can). It's sort of like drinking grapefruit juice thinking it's orange and spitting it all over the fridge. It still shouldn't crash the box running it as a normal user, though. Are you running these as a normal user? thomas 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. > I'm not complaining, as this hasn't been a problem for me, I am just > honestly curious as to what goes on that causes the system to reboot or > whatever it decides to do that day. > If that glitch were to be dealth with, perhaps by detecting whether libs are > statically compiled and refusing to run the program, FreeBSD would be 100% > unbcrashable as far as I can tell (short of doing things that are not the > fault of FreeBSD, like removing the CPU while the system is running or > compiling the kernel with the '-malign-double' option) > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.com > > > 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