From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: dwmw2@infradead.org
Subject: Re: [PATCH] Stop printk printing non-printable chars
Date: 19 Jun 2004 16:12:00 -0400 [thread overview]
Message-ID: <1087675920.9831.941.camel@cube> (raw)
David Woodhouse writes:
> Please don't do that -- it makes printing UTF-8 impossible.
> While I'd not argue that now is the time to start outputting
> UTF-8 all over the place, I wouldn't accept that it's a good
> time to _prevent_ it either, as your patch would do.
>
> If you want to post-process printk output, don't do it in the kernel.
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.
Non-cannonical UTF-8 encoding for ESC and other
troublesome characters may also cause problems.
next reply other threads:[~2004-06-19 22:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 20:12 Albert Cahalan [this message]
2004-06-19 22:56 ` [PATCH] Stop printk printing non-printable chars Jan-Benedict Glaw
-- strict thread matches above, loose matches on Subject: below --
2004-06-20 4:02 Albert Cahalan
2004-06-20 8:38 ` David Woodhouse
2004-06-20 8:49 ` 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=1087675920.9831.941.camel@cube \
--to=albert@users.sf.net \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@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