linux-kernel - Re: [PATCH] vt: Do not clear UTF when resetting console

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1175561612.7267.22.camel@daplas>
Date:	Tue, 03 Apr 2007 08:53:32 +0800
From:	"Antonino A. Daplas" <adaplas@...il.com>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	"H. Peter Anvin" <hpa@...or.com>, Andrew Morton <akpm@...l.org>,
	Linux Kernel Development <linux-kernel@...r.kernel.org>,
	Paul LeoNerd Evans <leonerd@...nerd.org.uk>
Subject: Re: [PATCH] vt: Do not clear UTF when resetting console

On Tue, 2007-04-03 at 02:23 +0200, Jan Engelhardt wrote:
> On Apr 3 2007 08:16, Antonino A. Daplas wrote:
> >
> >That would be the cleanest and purest behavior. But it's possible to set
> >one console to UTF-8 and another to legacy mode.
> 
> The question would be: why would you want to have mixed consoles?
> Switching to UTF8 IMO does not take away any characters, and I mean
> no-framebuffer 80x25 that is limited to 256 glyphs.

As long as we provide the users the capability to support mixed
encodings, the why is not important, it will happen. If we want to be
more restrictive, I guess, we can remove support for

echo -e '\033%G' and '\033%@'

Tony


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/