public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Justin <jlec@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] kdump
Date: Wed, 27 Mar 2013 12:54:15 +0100	[thread overview]
Message-ID: <5152DDE7.9060005@gentoo.org> (raw)
In-Reply-To: <CAGfcS_=3EPCoZbZ23ZL_-qfU6kdcK0DBoUxDDF7FBdbNQnaYYA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]

On 27/03/13 12:40, Rich Freeman wrote:
> On Wed, Mar 27, 2013 at 7:27 AM, Justin <jlec@gentoo.org> wrote:
>>
>> if someone is interested in implementing any infrastructure for a more
>> advanced usage of kdump for gentoo, please contact me.
>>
> 
> I've blogged a bit about this and wrote the wiki page.  However, the
> last time I actually tried to use kdump it wasn't working.  I don't
> remember the details.  I know I could boot another kernel immediately,
> but if I loaded a crash kernel it wouldn't actually boot on a panic.
> 
> It would be nice to have a more official solution for this on Gentoo.
> I don't mind messing around with it.  I don't have a ton of time but
> if you want to take the lead I can try to pitch in a bit.
> 
> Rich
> 

Hi,

Actually I don't need kdump that's why I asked for some input.

During the version bump today, I saw that fedora is providing lots of
script and services for it. So I thought someone might be interested and
port that to gentoo.

kexec itself is working fine on gentoo.

Justin


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

  reply	other threads:[~2013-03-27 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-27 11:27 [gentoo-dev] kdump Justin
2013-03-27 11:40 ` Rich Freeman
2013-03-27 11:54   ` Justin [this message]
2013-03-27 13:55     ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5152DDE7.9060005@gentoo.org \
    --to=jlec@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox