From: "Jakob Østergaard" <jakob@unthought.net>
To: Michael Miller <michaelm@mjmm.org>
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: curedump configuration additions
Date: Sat, 5 May 2001 22:18:08 +0200 [thread overview]
Message-ID: <20010505221808.C22425@unthought.net> (raw)
In-Reply-To: <200105051955.f45JtAD02315@mjmm.org>
In-Reply-To: <200105051955.f45JtAD02315@mjmm.org>; from michaelm@mjmm.org on Sat, May 05, 2001 at 08:55:09PM +0100
On Sat, May 05, 2001 at 08:55:09PM +0100, Michael Miller wrote:
> Hi,
>
> I have added some configuration options to the coredump abilities of the
> kernel. Please can this patch be considered for addition to the kernel.
Hi, just wanted to recommend that this goes in, in one form or another - it
would help a lot around here. Today we have to manually "fix" the kernel
source to get proper core.[executable] naming of core dumps.
I haven't looked at the patch though. I don't know if it meets the standards,
but the functionaly it provides (or was meant to provide) would definitely be a
life-saver for me. And it would put an end to the quarrels about core dump
naming :)
Thanks,
--
................................................................
: jakob@unthought.net : And I see the elder races, :
:.........................: putrid forms of man :
: Jakob Østergaard : See him rise and claim the earth, :
: OZ9ABN : his downfall is at hand. :
:.........................:............{Konkhra}...............:
next prev parent reply other threads:[~2001-05-05 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-05 19:55 curedump configuration additions Michael Miller
2001-05-05 20:18 ` Jakob Østergaard [this message]
2001-05-06 7:03 ` Albert D. Cahalan
2001-05-06 11:38 ` Chris Wedgwood
2001-05-06 17:00 ` Szabolcs Szakacsits
2001-05-07 23:12 ` Michael Miller
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=20010505221808.C22425@unthought.net \
--to=jakob@unthought.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=michaelm@mjmm.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