linux-kernel - Re: [PATCH] s390/sclp_vt220: Fix console name to match device

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:   Wed, 20 May 2020 09:07:43 +0200
From:   Valentin Vidić <vvidic@...entin-vidic.from.hr>
To:     Christian Borntraeger <borntraeger@...ibm.com>
Cc:     Heiko Carstens <heiko.carstens@...ibm.com>,
        Vasily Gorbik <gor@...ux.ibm.com>, linux-s390@...r.kernel.org,
        linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] s390/sclp_vt220: Fix console name to match device

On Wed, May 20, 2020 at 07:25:06AM +0200, Christian Borntraeger wrote:
> This is not as simple. ttyS1 is the the console name and ttysclp0 is the tty name.
> This has mostly historic reasons and it obviously causes problems.
> But there is  documentation out that that actually describes the use of 
> console=ttyS1 console=ttyS0.
> to have console output on both sclp consoles and there are probably scripts
> using ttyS1.
> 
> I am wondering. The tty for ttyS0 is named sclp_line0. Does this work in LPAR?

I ran into this problem with qemu-system-s390x, so not sure about LPAR.
Would changing the tty name also cause problems?

-- 
Valentin