Re:KMSCon – A Userspace System Console That Does Not Depend ...
by jchw on Tuesday December 27, 2022 @04:20PM
(#34153976)
Linux without kernel-level VTs seems like a good idea. As a long time user, it will be weird, but ultimately welcome. I think for most desktop setups, it'll be better if all of the weird old fbdev, text mode and VT garbage is cleared out; some of it may still be needed in the kernel codebase itself, but I don't think we need it in desktop kernels.
Luckily, it looks like 2023 might be our year. This Reddit post details an exploration earlier this year:
And came to the conclusion that everything was almost ready, with the notable exception of Plymouth, which handles the boot splash in most desktop distros.
So in theory, Plymouth, a recovery console, terminal emulators, and Wayland compositors are all able to work with CONFIG_VT=n, if the pieces are all put together. I think in this case, your logind implementation would handle the switching; it already handles switching resources when VTs are changed, so this makes enough sense.
I think there's a lot of anxiety around being able to build robust and dependable bits at the bottom layer, and it's pretty justified honestly. But if the Linux desktop stack is able to succeed at it, it seems like it could lift off a lot of legacy kernel code, offer improved internationalization and accessibility for terminal sessions, improve the seamlessness and integration of early boot and terminal sessions, and so forth.
There may never be a "year of the Linux Desktop" that meets everyone's criteria, but 2023 looks to be another year where long-standing efforts finally start to bear fruit more substantially. I'm looking forward to it.
Luckily, it looks like 2023 might be our year. This Reddit post details an exploration earlier this year:
https://www.reddit.com/r/linux/comments/sycbn0/showstoppers_...
And came to the conclusion that everything was almost ready, with the notable exception of Plymouth, which handles the boot splash in most desktop distros.
Well, it seems like that issue was fixed:
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/13...
So in theory, Plymouth, a recovery console, terminal emulators, and Wayland compositors are all able to work with CONFIG_VT=n, if the pieces are all put together. I think in this case, your logind implementation would handle the switching; it already handles switching resources when VTs are changed, so this makes enough sense.
I think there's a lot of anxiety around being able to build robust and dependable bits at the bottom layer, and it's pretty justified honestly. But if the Linux desktop stack is able to succeed at it, it seems like it could lift off a lot of legacy kernel code, offer improved internationalization and accessibility for terminal sessions, improve the seamlessness and integration of early boot and terminal sessions, and so forth.
There may never be a "year of the Linux Desktop" that meets everyone's criteria, but 2023 looks to be another year where long-standing efforts finally start to bear fruit more substantially. I'm looking forward to it.