From: Struan Bartlett <struan.bartlett@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, mpm@selenic.com
Cc: linux-kernel@vger.kernel.org, schwab@linux-m68k.org,
netdev@vger.kernel.org, davem@davemloft.net, nikolay@redhat.com,
andy.shevchenko@gmail.com, gregkh@linuxfoundation.org,
jiri@resnulli.us, joe@perches.com, alonid@postram.com
Subject: Re: [PATCH v2] netconsole: Add tty driver
Date: Wed, 2 Apr 2014 23:30:24 +0100 [thread overview]
Message-ID: <20140402223024.GA12627@NewsNow.co.uk> (raw)
In-Reply-To: <201404022116.HIB82683.FOJMFFHVStOLOQ@I-love.SAKURA.ne.jp>
On 02/04/2014 14:16, Tetsuo Handa wrote:
> Struan Bartlett wrote:
>> Adds tty driver to netconsole module. When module is loaded,
>> creates /dev/netcon0 device and enables support for console=netcon0
>> kernel cmdline option, causing /dev/console output to be sent to
>> /dev/netcon0. This allows startup/shutdown script output from
>> headless platforms to be logged over (secure) network.
>
> Excuse me, but I think that the netconsole logging can work only during network
> interfaces (e.g. eth0) are up. Did this patch description assume that the
> network interfaces are up before the startup script is started and the shutdown
> script is finished before the network interfaces are down?
Yes it did. I hope I have clarified that in the v3 patch description.
In practice, at least in a Debian environment: i) the netconsole module itself
is generally capable of raising the network interface when it is loaded by the
initramfs init script (which precedes all /etc/init.d/* scripts); ii) very
little of consequence tends to happens during shutdown after networking is
stopped; iii) equally, it is not usually problematic to disable the networking
shutdown script, since it runs on platforms about to be rebooted or powered off.
We do this by editing the Default-Stop LSB header in /etc/init.d/networking.
> By the way, I uploaded a logger specialized for receiving netconsole messages
> to http://sourceforge.jp/projects/akari/scm/svn/tree/head/branches/udplogger/ .
Thank you. I'll check it out.
prev parent reply other threads:[~2014-04-02 22:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 21:26 [PATCH v2] netconsole: Add tty driver Struan Bartlett
2014-04-01 21:37 ` David Miller
2014-04-02 12:16 ` Tetsuo Handa
2014-04-02 22:30 ` Struan Bartlett [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=20140402223024.GA12627@NewsNow.co.uk \
--to=struan.bartlett@gmail.com \
--cc=alonid@postram.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=schwab@linux-m68k.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).