lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 31 Mar 2014 11:18:33 +0100
From:	One Thousand Gnomes <>
To:	Andreas Schwab <>
Cc:	Struan Bartlett <>,
Subject: Re: Support for netconsole as default tty/console?

On Sat, 29 Mar 2014 15:54:24 +0100
Andreas Schwab <> wrote:

> Struan Bartlett <> writes:
> > Adding console=netconsole to the command line does not appear to have
> > the desired effect. I am not sure if this is because netconsole,
> > unlike the serial console, does not provide a tty. Can anyone advise
> > if this understanding is correct? If so, is there an independent
> > solution to this problem?
> It should not be hard to add a tty driver to netconsole, there are many
> examples to borrow from.

Samo Pogacnik added a generic solution a few years ago. The ttyprintk
driver provides you with a tty/console whose 'hardware' is printk and
thus whatever system log device you are using.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists