linux-kernel - Re: [PATCH] um: change defconfig to stop spawning xterm

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Mon, 22 Jul 2013 12:38:55 +0200
From:	Richard Weinberger <richard@....at>
To:	Ramkumar Ramachandra <artagnon@...il.com>
CC:	Al Viro <viro@...iv.linux.org.uk>,
	LKML <linux-kernel@...r.kernel.org>, lpoetter@...hat.com
Subject: Re: [PATCH] um: change defconfig to stop spawning xterm

CC'ing Lennart.

Am 22.07.2013 11:45, schrieb Ramkumar Ramachandra:
> Ramkumar Ramachandra wrote:
>> [1]: http://lists.freedesktop.org/archives/systemd-devel/2013-July/012152.html
> 
> ... and the patches were rejected.  Lennart says that UML providing
> /dev/tty* is wrong, and that UML should call them /dev/hvc* (or
> something).  Can we do something about the situation?  Can we remove
> /dev/tty*, and provide /dev/hvc*?  Will we be breaking existing users?
> 
> Thanks.
> 
> Lennart Poettering wrote:
>> UML shouldn't be penalized for not implementing some terminal emulation,
>> but it should be penalized for doing so under the label of "VT support",
>> which it simply is not providing.
>>
>> They can call their ttys any way they want. If the call them
>> /dev/tty[1..64] however, then they need to implement the VC
>> interfaces. All of them.

Lennart, can you please explain us why /dev/tty[1..64] is forced to
have virtual console support?

Thanks,
//richard
--
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/