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 for Android: free password hash cracker in your pocket

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

Message-ID: <20130722124047.GL4165@ZenIV.linux.org.uk>
Date:	Mon, 22 Jul 2013 13:40:47 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Ramkumar Ramachandra <artagnon@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Richard Weinberger <richard@....at>
Subject: Re: [PATCH] um: change defconfig to stop spawning xterm

On Mon, Jul 22, 2013 at 03:15:14PM +0530, Ramkumar Ramachandra wrote:
> 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?

Yes, you would be breaking existing users.  Starting with anybody with static
/dev.  Or a debian userland, for that matter.  Any systemd-free setup,
actually.

Changing device number assignments is not to be done lightly, whether
they should've been set that way back then or not.

As for Lennart's opinion...  *shrug*  He's free to do whatever he wants
in systemd.  It does not translate into having any kind of control over
the kernel.
--
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/