From owner-freebsd-hackers@FreeBSD.ORG  Tue Nov  5 21:53:57 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id AB84A94C;
 Tue,  5 Nov 2013 21:53:57 +0000 (UTC)
 (envelope-from cjpugmed@gmail.com)
Received: from mail-vb0-x230.google.com (mail-vb0-x230.google.com
 [IPv6:2607:f8b0:400c:c02::230])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 32FC429EE;
 Tue,  5 Nov 2013 21:53:57 +0000 (UTC)
Received: by mail-vb0-f48.google.com with SMTP id o19so2768214vbm.7
 for <multiple recipients>; Tue, 05 Nov 2013 13:53:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=3RSWT7mJUBnNJ4Ji44MhEJNlme2P1yx3mN51qW/yT+s=;
 b=xLXHXji2kLgUbKx7Q7ylK2FFFMJChC8EbVvY+Q6g0OhvomMTevAGCzSnTkR6udXJZG
 r3IGEpLS1bZ5AysxIIIpA2rJXOjJ6NC92SbU+at0vm8b0ss0f7ritORvIg+3wTAlsfeC
 8nFL/JPsYhObdGob1SRdfVAkw/c59ObmXbC56EiJZW9c5I4+UNP2S1yEFP/Y26MA3aCx
 5E/MB275IeSdxq6PK71+lKMJIKkLlNlFl+cbfkywI8u08NJBgASgfn3CzpAmR/sEKNyG
 tpxOhMB9pfXER9T6uAguMLSz29QFToNfIBAqFbcOONFIHMCOWE9V8kZvrHNAK7y8VVe/
 j27Q==
MIME-Version: 1.0
X-Received: by 10.221.64.17 with SMTP id xg17mr17171606vcb.5.1383688436221;
 Tue, 05 Nov 2013 13:53:56 -0800 (PST)
Received: by 10.220.1.17 with HTTP; Tue, 5 Nov 2013 13:53:56 -0800 (PST)
Date: Tue, 5 Nov 2013 22:53:56 +0100
Message-ID: <CAHHLbRNv2T2-arUXn7WDFHDOAOTQvVqe0nniOr5sVPcgob4QJQ@mail.gmail.com>
Subject: Re: Automated submission of kernel panic reports: sysutils/panicmail
From: Carlos Jacobo Puga Medina <cjpugmed@gmail.com>
To: freebsd-hackers@freebsd.org, cperciva@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Tue, 05 Nov 2013 21:53:57 -0000

Seems that rc.d scripts order doesn't allow geli-encrypted swap and dumpdev
to cooperate together. For this reason, I wonder what happens in such
cases, is not possible to use panicmail unless Pawel's proposal [1] which
argued to obtain and save crash info in memory somewhere before we
configure swap and copy it to /var/crash/ once we mount it.

Is sustainable this proposal or is there yet another alternative to
consider for those who use an encrypted GELI swap?

--CJPM