From owner-freebsd-current Mon Oct 5 21:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26964 for freebsd-current-outgoing; Mon, 5 Oct 1998 21:22:52 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26959 for ; Mon, 5 Oct 1998 21:22:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id VAA16579; Mon, 5 Oct 1998 21:22:01 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Alfred Perlstein cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: lockups under 3.0 sorry In-reply-to: Your message of "Mon, 05 Oct 1998 21:47:17 CDT." Date: Mon, 05 Oct 1998 21:22:01 -0700 Message-ID: <16575.907647721@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > not after the last time i enable crashdumps and mistook my /usr for my > swap partition. sorry this is my machine at work and can't rebuild it My crashdumps are all working fine, but of course you still have to not specify your /usr partition as a crashdump location. Doing that is bad juju. Aim gun at foot. Fire until magazine is empty. That kinda bad juju. Having always specified my swap partitions correctly, on the other hand, and I've never had a crashdump overwrite anything I didn't want overwritten. Not once. And I take a lot of crashdumps in my testing, on multiple machines, using the latest -current and -stable, so I'm inclined to blame the operator over the software in this series of incidents since I have absolutely no reason to believe otherwise given the evidence available for examination. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message