From owner-freebsd-current Tue Jul 20 13:36:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 9D5E7153CC for ; Tue, 20 Jul 1999 13:36:35 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: (qmail 81206 invoked from network); 20 Jul 1999 20:36:22 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 20 Jul 1999 20:36:22 -0000 Date: Tue, 20 Jul 1999 15:36:22 -0500 (CDT) From: David Scheidt X-Sender: dscheidt@shell-3.enteract.com To: Matthew Dillon Cc: "Steven G. Kargl" , Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? In-Reply-To: <199907201849.LAA06381@apollo.backplane.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 On Tue, 20 Jul 1999, Matthew Dillon wrote: > > * make sure your swap partition is large enough to hold the crash > dump. If you have 256MB of ram, your swap partition must be > at least 256MB in size. Is there any reason that savecore(8) can't write compressed crashdumps? (Other than no one haveing ever written the the code, of course.) In other words, if I wrote this would it get committed? David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message