From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
linux-net@vger.kernel.org, netdev@oss.sgi.com,
jgarzik@mandrakesoft.com
Subject: Re: [patch] netconsole-2.4.10-C2
Date: Tue, 02 Oct 2001 18:09:42 -0700 [thread overview]
Message-ID: <3BBA6556.E27FC534@osdlab.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0109291146440.1715-100000@localhost.localdomain> <3BB77591.C1349C09@osdlab.org> <3BB77FD7.696CFC58@osdlab.org> <20010930220950.K930@turbolinux.com>
Andreas Dilger wrote:
>
> On Sep 30, 2001 13:25 -0700, Randy.Dunlap wrote:
> > I'm interested in using netconsole early (during boot).
> > Any problems doing that, other than getting module parameters
> > to it? I can fix that part.
>
> I was thinking about this as well. It should be relatively easy to allow
> a line line "console=eth0,XX:XX:XX:XX:XX:XX,a.b.c.d" or similar. The only
> slight problem might be in configuring the interface early enough in the
> boot process. AFAIK (which isn't much in this area) the serial console
> has special "console" code which allows it to be used very early in the
> boot process.
>
> You would obviously need to have the network driver compiled into the kernel
> and not a module. Maybe Ingo can hack something where it is possible
> to initialize the network code very early in the boot process?
Well, I have netconsole-in-kernel (+ AD patches + RD patches)
built and parsing parameters, but not getting active nearly
soon enough.
I'll continue to work on that...hints appreciated/accepted.
~Randy
next prev parent reply other threads:[~2001-10-03 1:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 20:04 [patch] netconsole - log kernel messages over the network. 2.4.10 Ingo Molnar
2001-09-26 19:36 ` Marcelo Tosatti
2001-09-26 21:15 ` jamal
2001-09-27 5:45 ` Ingo Molnar
2001-09-26 21:29 ` Andreas Dilger
2001-09-26 23:46 ` Andreas Dilger
2001-09-27 5:28 ` Ingo Molnar
2001-09-27 6:38 ` [patch] netconsole-2.4.10-B1 Ingo Molnar
2001-09-28 7:08 ` Andreas Dilger
2001-09-29 1:34 ` Randy.Dunlap
2001-09-29 9:52 ` Ingo Molnar
2001-09-29 16:32 ` John Alvord
2001-09-29 16:40 ` Pekka Savola
2001-09-29 22:37 ` Andreas Dilger
2001-09-30 3:38 ` Kenneth Johansson
2001-09-30 7:52 ` Rik van Riel
2001-09-30 10:40 ` Riley Williams
2001-09-30 10:48 ` Glynn Clements
2001-09-30 12:25 ` Richard Gooch
2001-10-01 7:35 ` Ingo Molnar
2001-10-01 14:55 ` Oliver Xymoron
2001-10-01 16:28 ` Richard Gooch
2001-10-01 8:47 ` Henning P. Schmiedehausen
2001-10-01 16:03 ` Andreas Dilger
2001-09-30 21:18 ` H. Peter Anvin
2001-09-30 16:00 ` Marcus Sundberg
2001-10-01 7:39 ` Ingo Molnar
2001-09-30 19:42 ` Randy.Dunlap
2001-09-30 20:25 ` Randy.Dunlap
2001-10-01 4:09 ` Andreas Dilger
2001-10-03 1:09 ` Randy.Dunlap [this message]
2001-10-01 16:58 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 2:53 [patch] netconsole - log kernel messages over the network. 2.4.10 Albert Cranford
2001-09-28 7:45 ` [patch] netconsole-2.4.10-C2 Ingo Molnar
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=3BBA6556.E27FC534@osdlab.org \
--to=rddunlap@osdlab.org \
--cc=adilger@turbolabs.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mingo@elte.hu \
--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