From owner-freebsd-current@FreeBSD.ORG  Mon Sep  1 22:36:13 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4AFD016A4BF
	for <freebsd-current@freebsd.org>;
	Mon,  1 Sep 2003 22:36:13 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1AC5943FBD
	for <freebsd-current@freebsd.org>;
	Mon,  1 Sep 2003 22:36:12 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h825a4i8041077;
	Tue, 2 Sep 2003 07:36:05 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: "Aaron Wohl" <freebsd@soith.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Mon, 01 Sep 2003 23:01:45 MDT."
             <20030902050145.E314A3A71E@www.fastmail.fm> 
Date: Tue, 02 Sep 2003 07:36:04 +0200
Message-ID: <41076.1062480964@critter.freebsd.dk>
cc: freebsd-current@freebsd.org
Subject: Re: swapon vs savecore dilemma 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Sep 2003 05:36:13 -0000

In message <20030902050145.E314A3A71E@www.fastmail.fm>, "Aaron Wohl" writes:
>I usualy have a number of swap partitions since the max size of  a swap
>partition is kind of limited.  I was thinking of changing it to do swapon
>twice.  The first time early in the boot would skip mounting any swap
>areas that had kernel core dumps.  Then after the savecore it could do
>swapon again to mount the rest of the swap areas.   Either that or have
>swaping start to allocate space at the oposite end of the swap space than
>savecore uses.  

Hmm, that was an unfortunate side effect.

The writing is only needed for marking the dump as "read", the same
effect could be had much cleaner by writing the signature of the dump
to a file in /var/ somewhere and not reading dumps already in that
file.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.