From owner-freebsd-hackers Sun Jun 27 19: 9:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id B827115269 for ; Sun, 27 Jun 1999 19:09:26 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id WAA22733 for ; Sun, 27 Jun 1999 22:09:56 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id WAA18393 for ; Sun, 27 Jun 1999 22:09:22 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id WAA76016 for freebsd-hackers@freebsd.org; Sun, 27 Jun 1999 22:09:22 -0400 (EDT) Date: Sun, 27 Jun 1999 22:09:22 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906280209.WAA76016@lakes.dignus.com> To: freebsd-hackers@freebsd.org Subject: setiathome crashes 3.2? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall seeing this someone (this may not be the right list.) But - I downloaded the 3.2 Seti@home and starting running it on a left-over 75mhz laptop I have. It seems to crash the laptop (silently lock it up, actually) fairly quickly. Did I recall someone else mentioning that? Would everyone agree that it's not a "good thing" for a user-mode program to be able to lock up the OS? - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message