From owner-freebsd-current Mon Oct 5 22:34:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08495 for freebsd-current-outgoing; Mon, 5 Oct 1998 22:34:54 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08439 for ; Mon, 5 Oct 1998 22:34:14 -0700 (PDT) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with SMTP id BAA02670 for ; Tue, 6 Oct 1998 01:35:38 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Tue, 6 Oct 1998 01:35:38 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: Re: lockups under 3.0 sorry In-Reply-To: <16575.907647721@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG maybe it was a devfs problem. i'm going to enable them on good faith, meaning i'll be sure to tell you on irc if it eats a different partition :P (i had devfs on both machines) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Mon, 5 Oct 1998, Jordan K. Hubbard wrote: > > 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