From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: jbglaw@lug-owl.de, dwmw2@infradead.org, arjanv@redhat.com,
Linus Torvalds <torvalds@osdl.org>,
jbglaw@lug-owl.de, matthew-lkml@newtoncomputing.co.uk
Subject: Re: [PATCH] Stop printk printing non-printable chars
Date: 20 Jun 2004 00:02:58 -0400 [thread overview]
Message-ID: <1087704177.8185.951.camel@cube> (raw)
>> It is dangerous to let the 0x9b character go out
>> to a serial console. It means the same as ESC [ does
>> when you have a normal 8-bit terminal.
>
> Get real: either you *want* to get those codes
> interpreted (think about full-blown ncurses apps
> being run over serial link), or you *don't* (think
> about simply recording serial console's output).
> You just have to choose the correct application
> for your task.
If there are full-blown ncurses apps being routed
through printk -- that is, the KERNEL log -- then
we have far bigger issues.
The 0x9b character must be blocked, at least when
a serial console is in use. (apps on such a console
may of course use 0x9b as desired -- just not printk)
next reply other threads:[~2004-06-20 6:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-20 4:02 Albert Cahalan [this message]
2004-06-20 8:38 ` [PATCH] Stop printk printing non-printable chars David Woodhouse
2004-06-20 8:49 ` Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 20:12 Albert Cahalan
2004-06-19 22:56 ` Jan-Benedict Glaw
2004-06-18 20:53 matthew-lkml
2004-06-18 21:08 ` Linus Torvalds
2004-06-18 22:44 ` Jesper Juhl
2004-06-18 23:52 ` matthew-lkml
2004-06-19 4:18 ` Willy Tarreau
2004-06-19 10:27 ` Matthias Urlichs
2004-06-19 23:00 ` Dave Jones
2004-06-19 1:23 ` Matthias Urlichs
2004-06-19 1:43 ` Jesper Juhl
2004-06-19 10:20 ` Matthias Urlichs
2004-06-18 21:32 ` Jan-Benedict Glaw
2004-06-18 21:58 ` Pekka Pietikainen
2004-06-19 0:03 ` matthew-lkml
2004-06-19 8:31 ` Jan-Benedict Glaw
2004-06-19 11:18 ` David Woodhouse
2004-06-19 15:49 ` matthew-lkml
2004-06-19 16:09 ` Arjan van de Ven
2004-06-20 2:19 ` Horst von Brand
2004-06-20 14:17 ` David Woodhouse
2004-06-20 20:06 ` Jeff Woods
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=1087704177.8185.951.camel@cube \
--to=albert@users.sf.net \
--cc=arjanv@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew-lkml@newtoncomputing.co.uk \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.