On Sat, 2016-02-13 at 18:11 +0900, Roger Shimizu wrote: > On Sat, Feb 13, 2016 at 3:21 AM, Ben Hutchings <ben@decadent.org.uk> wrote: > > Control: found -1 4.3.5-1 > > > > On Sat, 2016-02-13 at 02:25 +0900, Roger Shimizu wrote: > > > Package: src:linux > > > Version: 3.16.7-ckt20-1+deb8u3 > > > Severity: wishlist > > > X-Debbugs-Cc: rogershimizu@gmail.com > > > > > > Dear Maintainer, > > > > > > Please enable TTY_PRINTK as module. > > > It's also requested in lists: > > > - https://lists.debian.org/debian-kernel/2016/02/msg00034.html > > > > This isn't suitable for jessie, but please go ahead with this change on > > the master branch. > > Thanks for your feedback! > Understand. I just type "reportbug" command on my stable PC. > > > In fact, let's make it built-in - it's tiny, and I think we should use > > it by default in the initramfs which means everyone will have it loaded > > anyway. > > I supposed this debugging feature is mainly for embedded or VM, so > module is more flexible. > You can include this module when MODULES=most in initramfs-tools, and > load this module together with netconsole. > If netconsole kmod is not loaded or in other limited special cases, > IMHO TTY_PRINTK is not so useful. I was thinking that we could use it to print to the console and also ensure that output goes into the system log later. But, having taken a closer look at what ttyprintk does, I think you're right and we couldn't use it by default. Ben. -- Ben Hutchings Sturgeon's Law: Ninety percent of everything is crap.
Attachment:
signature.asc
Description: This is a digitally signed message part