From: Jeff Garzik <jgarzik@pobox.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Jon Burgess <mplayer@jburgess.uklinux.net>,
linux kernel <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: [PATCH][RFC] Netconsole debugging tool for 2.6
Date: Tue, 12 Aug 2003 13:09:20 -0400 [thread overview]
Message-ID: <20030812170920.GB24774@gtf.org> (raw)
In-Reply-To: <20030812163311.GL31810@waste.org>
On Tue, Aug 12, 2003 at 11:33:11AM -0500, Matt Mackall wrote:
> On Tue, Aug 12, 2003 at 03:13:00PM +0100, Jon Burgess wrote:
> > Matt Mackall wrote:
> > > I've decided to take a stab at resurrecting Ingo's netconsole patch.
> >
> > Is this different from the netdump patch which RedHat include in their
> > kernel?
> >
> > The RH kernel patch is at
> > http://www.kernelnewbies.org/kernels/rh9/SOURCES/linux-2.4.18-netdump.patch
>
> Ahh, so that's what's become of it.
>
> Theirs:
> - does crashdumps
> - does syslog without levels
> - has hooks for receive
>
> Mine:
> - works in 2.6
> - has non-appalling configuration
> - works as a built-in and is available earlier in boot
> - does syslog with levels (haven't posted this though)
netconsole does syslog with levels, too. I agree netdump/netconsole
have complete awful configuration. I was thinking netlink would be a
good configurator.
The kernel printk <foo> prefixes map into syslog quite nicely.
In any case, there is my own active effort into cleaning up netdump to
be less x86-specific, and get it ready for mainline.
Maybe we can start discussing converging all these implementations on
netdev@oss.sgi.com? (that's where the networking developers live)
Jeff
next prev parent reply other threads:[~2003-08-12 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 14:13 Jon Burgess
2003-08-12 16:33 ` Matt Mackall
2003-08-12 17:09 ` Jeff Garzik [this message]
2003-08-12 17:39 ` Matt Mackall
-- strict thread matches above, loose matches on Subject: below --
2003-08-11 8:55 Matt Mackall
2003-08-26 20:57 ` Peter Osterlund
2003-08-27 21:08 ` Herbert Pötzl
2003-08-27 21:14 ` J.A. Magallon
2003-08-28 12:38 ` Steffen Klassert
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=20030812170920.GB24774@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mplayer@jburgess.uklinux.net \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.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
all inboxes | Powered by JetHome®