All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matt D. Robinson" <yakker@alacritech.com>
To: 64738 <schwung@rumms.uni-mannheim.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LKCD from SGI
Date: Wed, 22 Nov 2000 10:14:33 -0800	[thread overview]
Message-ID: <3A1C0D09.428F5398@alacritech.com> (raw)
In-Reply-To: <974906422.3a1be4369213b@rumms.uni-mannheim.de>

64738 wrote:
> 
> Hi.
> 
> I tried to find some information on whether the Linux Kernel Crash Dumps
> patches are going into 2.4 (or 2.5). Has there been any decision?

LKCD won't go into 2.4 (or 2.5) until I finish writing the direct
disk open/write functions that avoid going through the standard
IDE and SCSI drivers.  I'm working on it.

As far as work for 2.4 goes, we've got a version on SourceForge that
works well (for i386 and 95% for ia64).

As soon as the drivers are done, we'll hopefully get acceptance.

--Matt

P.S.  Any way we can standardize 'make install' in the kernel?  It's
      disturbing to have different install mechanisms per platform ...
      I can make the changes for a few platforms.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-22 18:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22 15:20 LKCD from SGI 64738
2000-11-22 18:14 ` Matt D. Robinson [this message]
2000-11-23  1:41   ` Peter Samuelson
2000-11-24 23:40     ` Eric W. Biederman
2000-11-25  1:58       ` Keith Owens
2000-11-25 13:18         ` J . A . Magallon
2000-11-25 13:23           ` Keith Owens
2000-11-25 13:49             ` J . A . Magallon
2000-11-25 13:44           ` Matthew Kirkwood
  -- strict thread matches above, loose matches on Subject: below --
2000-11-25 15:17 64738

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=3A1C0D09.428F5398@alacritech.com \
    --to=yakker@alacritech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwung@rumms.uni-mannheim.de \
    /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.