From: Arun Dharankar <ADharankar@ATTBI.Com>
To: "Matt D. Robinson" <yakker@alacritech.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux kernel crash dumps (LKCD) and PowerPC ports.
Date: Tue, 8 Apr 2003 23:49:27 -0400 [thread overview]
Message-ID: <200304082349.27844.ADharankar@ATTBI.Com> (raw)
In-Reply-To: <1049843693.10620.34.camel@lambda.alacritech.com>
Matt, thanks for the pointers!
Looking at those sites, it appears that the development at
"http://lists.insecure.org/lists/linux-kernel/2003/Feb/0987.html."
which I had pointed is based on the SGI's dump scheme. Same
for the one you pointed to.
The other scheme I poinited to (from Mission Critical Linux/MCLX)
seems to have some strong points too. Any pointers to discussions
about why the LKCD work seems to more active than the
MCLX one?
Best regards,
-Arun.
On Tuesday 08 April 2003 07:14 pm, Matt D. Robinson wrote:
> Please look at the lkcd-devel mailing archives. There is
> at least one group working on a PPC port of LKCD
>
> http://sourceforge.net/mail/?group_id=2726
>
> --Matt
>
> On Tue, 2003-04-08 at 13:47, Arun Dharankar wrote:
> > Greetings.
> >
> > >From what I able to find from some searching around, the implementation
> >
> > by MCLX ("http://oss.missioncriticallinux.com/projects/mcore/") is being
> > carried on at
> > http://lists.insecure.org/lists/linux-kernel/2003/Feb/0987.html.
> >
> > Looking at these patches, I can only see x86 architecture support for
> > in memory kernel crash dump support. Is anyone actively working on the
> > PowerPC architecture?
> >
> > Best regards,
> > -Arun.
next prev parent reply other threads:[~2003-04-09 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 20:47 Linux kernel crash dumps (LKCD) and PowerPC ports Arun Dharankar
2003-04-08 23:14 ` Matt D. Robinson
2003-04-09 3:49 ` Arun Dharankar [this message]
2003-04-09 8:08 ` Piet Delaney
2003-04-09 12:26 ` Arun Dharankar
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=200304082349.27844.ADharankar@ATTBI.Com \
--to=adharankar@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yakker@alacritech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.