From owner-freebsd-current Tue Jul 20 13:46:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 43699153FD for ; Tue, 20 Jul 1999 13:46:24 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA22118; Tue, 20 Jul 1999 22:42:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: David Scheidt Cc: Matthew Dillon , "Steven G. Kargl" , freebsd-current@FreeBSD.ORG Subject: Re: is dumpon/savecore broken? In-reply-to: Your message of "Tue, 20 Jul 1999 15:36:22 CDT." Date: Tue, 20 Jul 1999 22:42:47 +0200 Message-ID: <22116.932503367@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dav id Scheidt writes: >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? I'm pretty sure it would. I think the lack of libz has prevented it in the past. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message