From: "J.A. Magallon" <jamagallon@able.es>
To: herbert@13thfloor.at
Cc: Peter Osterlund <petero2@telia.com>,
Matt Mackall <mpm@selenic.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Netconsole debugging tool for 2.6
Date: Wed, 27 Aug 2003 23:14:51 +0200 [thread overview]
Message-ID: <20030827211451.GA26595@werewolf.able.es> (raw)
In-Reply-To: <20030827210830.GF26817@www.13thfloor.at>; from herbert@13thfloor.at on Wed, Aug 27, 2003 at 23:08:30 +0200
On 08.27, Herbert Pötzl wrote:
> On Tue, Aug 26, 2003 at 10:57:28PM +0200, Peter Osterlund wrote:
> > Matt Mackall <mpm@selenic.com> writes:
> >
> > > I've decided to take a stab at resurrecting Ingo's netconsole patch.
> > >
> > > For those who missed it the first time around (for 2.4.10), this
> > > module is a "serial console over networks" which lets you catch kernel
> > > messages, oopses and so on that can't be caught by syslog.
>
> hmm, sounds somewhat familiar, could you give
> the location of the patches/tools/etc ...
>
I think it is included in -aa, so perhaps that is the most updated
source.
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.22-jam1m (gcc 3.3.1 (Mandrake Linux 9.2 3.3.1-1mdk))
next prev parent reply other threads:[~2003-08-27 21:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 8:55 [PATCH][RFC] Netconsole debugging tool for 2.6 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 [this message]
2003-08-28 12:38 ` Steffen Klassert
-- strict thread matches above, loose matches on Subject: below --
2003-08-12 14:13 Jon Burgess
2003-08-12 16:33 ` Matt Mackall
2003-08-12 17:09 ` Jeff Garzik
2003-08-12 17:39 ` Matt Mackall
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=20030827211451.GA26595@werewolf.able.es \
--to=jamagallon@able.es \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=petero2@telia.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.