From: David Miller <davem@davemloft.net>
To: mpm@selenic.com
Cc: hollisb@us.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH 0 of 2] implement tty driver for netconsole
Date: Sat, 29 Nov 2008 21:39:47 -0800 (PST) [thread overview]
Message-ID: <20081129.213947.185052916.davem@davemloft.net> (raw)
In-Reply-To: <1227827385.3196.49.camel@calx>
From: Matt Mackall <mpm@selenic.com>
Date: Thu, 27 Nov 2008 17:09:45 -0600
> On Thu, 2008-11-27 at 15:11 -0600, Hollis Blanchard wrote:
> > I have a Kuro Box (a small NAS device running Linux), and it has no serial
> > console (nor any other console for that matter). The most convenient way to get
> > boot output is via the netconsole driver, which is what most Kuro owners do. (The u-boot
> > firmware even supports interactive netconsole allowing us to edit boot configuration.)
> >
> > However, once past kernel boot, userspace currently has no way of outputting data over
> > netconsole. These patches enable that, which is really useful for seeing init
> > script output and debugging ramdisks before they've brought up sshd.
>
> Awesome! I've been meaning to wire this up for ages. I'll try to look at
> it over the weekend.
Matt if your review goes OK please ACK this and I'll toss these
patches into net-next-2.6
Thanks
prev parent reply other threads:[~2008-11-30 5:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-27 21:11 [PATCH 0 of 2] implement tty driver for netconsole Hollis Blanchard
2008-11-27 21:11 ` [PATCH 1 of 2] netconsole: don't require struct console to send data Hollis Blanchard
2008-11-30 17:21 ` Matt Mackall
2008-11-27 21:11 ` [PATCH 2 of 2] netconsole: add write-only tty driver Hollis Blanchard
2008-11-27 21:47 ` Evgeniy Polyakov
2008-11-28 5:25 ` Hollis Blanchard
2008-11-30 17:28 ` Matt Mackall
2008-11-27 23:09 ` [PATCH 0 of 2] implement tty driver for netconsole Matt Mackall
2008-11-30 5:39 ` David Miller [this message]
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=20081129.213947.185052916.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hollisb@us.ibm.com \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).