From: Pavel Machek <pma@sysgo.com>
To: kernel list <linux-kernel@vger.kernel.org>,
horms@verge.net.au, vgoyal@redhat.com, akpm@linux-foundation.org
Cc: randy.dunlap@oracle.com
Subject: kexec documentation missing, bad links in kdump.txt
Date: Thu, 18 Nov 2010 10:50:15 +0100 [thread overview]
Message-ID: <20101118095015.GA12071@pma.sysgo.com> (raw)
Hi!
Where can one get kexec documentation?
(In particular, we are trying to get it to boot on ARM board, and
wonder if something like CONFIG_RELOCATABLE_KERNEL is needed.)
Unfortunately, only pieces mentioning kexec are kdump pieces
(Documentation/kdump/kdump.txt), and links there, such as
http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/kexec-tools.tar.gz
http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/README.html
http://www.kernel.org/git/?p=linux/kernel/git/horms/kexec-tools.git
are no longer valid :-(.
Pavel
next reply other threads:[~2010-11-18 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 9:50 Pavel Machek [this message]
2010-11-18 10:17 ` kexec documentation missing, bad links in kdump.txt Américo Wang
2010-11-18 14:23 ` Vivek Goyal
2010-11-18 18:06 ` Randy Dunlap
2010-11-18 22:19 ` Simon Horman
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=20101118095015.GA12071@pma.sysgo.com \
--to=pma@sysgo.com \
--cc=akpm@linux-foundation.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=vgoyal@redhat.com \
/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