From owner-freebsd-hackers@FreeBSD.ORG  Tue Nov  5 21:55:33 2013
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 165ABA47;
 Tue,  5 Nov 2013 21:55:33 +0000 (UTC)
 (envelope-from cjpugmed@gmail.com)
Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com
 [IPv6:2607:f8b0:400c:c02::232])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id B98852A05;
 Tue,  5 Nov 2013 21:55:32 +0000 (UTC)
Received: by mail-vb0-f50.google.com with SMTP id x16so2916397vbf.9
 for <multiple recipients>; Tue, 05 Nov 2013 13:55:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=wue4mHW8FmxuGoxeevZozKvkIH6fzGoSpgJzJLoGzOc=;
 b=qb4Ajtm2EvcWrJVxasMViTul8kIsh0YR3vuLkYMd3bLEdSDxXmtoQO6SEpS9eqO1eq
 O8EAUYlm3JeNREDVfUxFffFh950hokiQcICbWTspRnbQRAvkt7oLvCdMNUy9ku+rWEZY
 UoZcuaVoDETsY522pYGmDPzb6S4MQoMO00JOsOxqeWQd1BXLpUgnEx/88+nIj4RAHrLe
 OQsZ2a9hIxUAPn+eSOE3MYgkGyZfsrrN+pevj1MHFCRqQv5opV38ze5y42PdH6zeU+9Y
 dFkqIWjrBlgkz3r/iP+s2R17Ikr+xvs9UQbPIXmMJ6I0eme3moiySeGLj9RhR7Gxz7A/
 P9fA==
MIME-Version: 1.0
X-Received: by 10.52.120.78 with SMTP id la14mr14829161vdb.9.1383688531925;
 Tue, 05 Nov 2013 13:55:31 -0800 (PST)
Received: by 10.220.1.17 with HTTP; Tue, 5 Nov 2013 13:55:31 -0800 (PST)
In-Reply-To: <CAHHLbRNv2T2-arUXn7WDFHDOAOTQvVqe0nniOr5sVPcgob4QJQ@mail.gmail.com>
References: <CAHHLbRNv2T2-arUXn7WDFHDOAOTQvVqe0nniOr5sVPcgob4QJQ@mail.gmail.com>
Date: Tue, 5 Nov 2013 22:55:31 +0100
Message-ID: <CAHHLbRNGwP56Qq_FLZGvN7hORJtE1SUVAZKpJty_cN4+7mEEUA@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:55:33 -0000

Add missing thread related to Pawel's proposal [1]

[1] http://lists.freebsd.org/pipermail/freebsd-fs/2010-September/009256.html


2013/11/5 Carlos Jacobo Puga Medina <cjpugmed@gmail.com>

> 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
>