From owner-freebsd-hackers@FreeBSD.ORG  Mon Jun 26 15:12:32 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8F08216A57E
	for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2006 15:12:32 +0000 (UTC)
	(envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org)
Received: from mired.org (vpn.mired.org [66.92.153.74])
	by mx1.FreeBSD.org (Postfix) with SMTP id EE0F044ADE
	for <freebsd-hackers@freebsd.org>; Mon, 26 Jun 2006 14:10:29 +0000 (GMT)
	(envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org)
Received: (qmail 92572 invoked by uid 1001); 26 Jun 2006 14:10:29 -0000
Received: by bhuda.mired.org (tmda-sendmail, from uid 1001);
	Mon, 26 Jun 2006 10:10:28 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17567.60116.599544.571163@bhuda.mired.org>
Date: Mon, 26 Jun 2006 10:10:28 -0400
To: Dmitry Morozovsky <marck@rinet.ru>
In-Reply-To: <20060626111208.P77513@woozle.rinet.ru>
References: <449D8616.5040306@tamara-b.org>
	<17565.37706.966913.737964@bhuda.mired.org>
	<20060626111208.P77513@woozle.rinet.ru>
X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid
X-Primary-Address: mwm@mired.org
X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;
	h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\
X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew)
From: Mike Meyer <mwm-keyword-freebsdhackers2.e313df@mired.org>
Cc: freebsd-hackers@freebsd.org, bob@tamara-b.org
Subject: Re: A New FreeBSD Server
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Jun 2006 15:12:32 -0000

In <20060626111208.P77513@woozle.rinet.ru>, Dmitry Morozovsky <marck@rinet.ru> typed:
> On Sat, 24 Jun 2006, Mike Meyer wrote:
> MM> The other constraint on swap is that if you want the system to save a
> MM> core dump if it panics, you need a device to dump on that's 64Kb
> MM> bigger than ram. That's one device, not all of swap.
> This is not quite true, as there always are some unused memory regions, hence 
> you need not add 64k to RAM size. At least, I had no trouble using swap == RAM 
> for last 5 years or so...

Or memory areas that aren't needed when doing the post mortem. The
question is, how do you guarantee that those are what's not going to
make it out to the dump device?

	<mike

-- 
Mike Meyer <mwm@mired.org>		http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.