[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <93b4c53a-9f15-4c35-965b-ac889b3061c8@sysprog.at>
Date: Wed, 9 Oct 2024 11:24:49 +0200
From: Bernd Petrovitsch <bernd@...prog.at>
To: nerdopolis <bluescreen_avenger@...izon.net>
Cc: pmladek@...e.com, rostedt@...dmis.org, linux-kernel@...r.kernel.org,
john.ogness@...utronix.de, gregkh@...uxfoundation.org,
tglx@...utronix.de, tony@...mide.com, senozhatsky@...omium.org
Subject: Re: VT-less kernels, and /dev/console on x86
Hi all!
On 18.08.24 02:09, nerdopolis wrote:
[...]
> I originally brought this up on linux-serial, but I think it makes more sense
> that it's part of how printk console device selection works. Without VTs, while
> most software is able to handle the situation, some userspace programs expect
> /dev/console to still be responsive. Namely systemd. It calls isatty() against
> /dev/console, and since /dev/console on VT-less systems currently defaults to
> /dev/ttyS0, and when /dev/ttyS0 is disconnected, the ioctl's fail, and it
> refuses to write log messages to it.
What's wrong with fixing systemd?
Kind regards,
Bernd
--
--
mobile: +43 664 4416156 http://www.sysprog.at/
Embedded Linux Software Development, Consulting and Services
Powered by blists - more mailing lists