calamares: Explicitly set /etc/vconsole.conf font #4770
Merged
+22
−17
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
silkeh
reviewed
Jan 9, 2025
packages/c/calamares/files/install/modules/shellprocess_postinstall.conf
Outdated
Show resolved
Hide resolved
|
@EbonJaeger @silkeh The wise move here is probably for the two of you to coordinate the landing of the CBM + Calamares stuff? Feel free to commandeer this PR. I only put it up in the spirit of showing my view on how we might approach the "make the boot-time experience for LUKS users and people troubleshooting a little more ergonomic." to Silke after the discussion the other day. |
silkeh
force-pushed
the
calamares-set-etc-vconsole.conf-font-by-default
branch
from
177b205 to
33832c7
Compare
|
Result on a clean install:
|
**Summary** As part of the CBM changes in [1], CBM will now parse the system `/etc/vconsole.conf` file and explicitly set the corresponding `rd.vconsole.font=(...) rd.vconsole.keymap=(...)` options on the kernel commandline, such that they are used in rescue initrd shells. [1]: getsolus/clr-boot-manager#7 To make it clearer and more discoverable to the user what these variables are currently set to in the root fs, the present change ensures that the Solus default font selection of the terminus 32px bold console font with unicode support (ter-v32b), will now also be explicitly listed on the kernel command line for troubleshooting/rescue purposes via CBM. This is primarily an ergonomics change meant to help Solus users understand how to influence these settings in the face of error modes that prevent them from logging in via their normal graphical session. The consensus seemed to be that this PR ought to be followed up by a Documentation PR on the help center, expanding on the options between which the user can choose in terms of font sizes, font styles, and keyboard mappings, should they need to change the settings for whatever reason. Signed-off-by: Rune Morling <[email protected]>
**Summary** Release notes can be found [here](https://github.com/getsolus/clr-boot-manager/releases/tag/solus-3.6.0).
silkeh
force-pushed
the
calamares-set-etc-vconsole.conf-font-by-default
branch
from
33832c7 to
c6cc84f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
As part of the CBM changes in CBM PR 7, CBM will now parse the system
/etc/vconsole.conffile and explicitly set the correspondingrd.vconsole.font=(...) rd.vconsole.keymap=(...)options on the kernel commandline, such that they are used in rescue initrd shells.
To make it clearer and more discoverable to the user what these variables are currently set to in the root fs, the present change ensures that, on new installs, the Solus default font selection of the terminus 32px bold console font with unicode support (ter-v32b), will now also be explicitly listed on the kernel command line for troubleshooting/rescue purposes via CBM.
This is primarily an ergonomics change meant to help Solus users understand how to influence these settings in the face of error modes that prevent them from logging in via their normal graphical session.
The consensus seemed to be that this PR ought to be followed up by a Documentation PR on the help center, expanding on the options between which the user can choose in terms of font sizes, font styles, and keyboard mappings, should they need to change the settings for whatever reason.
Test Plan
N/A (covered by CBM PR)
Checklist