We were in certain situations still writing to locale.sh. While it would not have caused any harm, it was unintended and this removes it.
This change means that locale.sh will no longer load the consolemap. This would only be useful if it had been reset accidentally, and logging in again would then fix a potentially broken console. The issue is described in FS#18759. It is not clear to me if this is still an issue, or if it solved by our new utf8/non-utf8 handling. Either way, resetting the consolemap unconditionaly does not make much sense in case the user has changed it on purpose. It might make sense to factor out the vconsole initialization into a "setup/repair my console" script, similar to systemd's /lib/systemd/systemd-vconsole-setup, but that would have to wait for a future release. My locale setup is dreadfully boring, so it would be nice if someone with a non-ASCII-compatible locale could give their input... Reported-by: Dave Reisner <[email protected]> Cc: Роман Кирилич <[email protected]> Signed-off-by: Tom Gundersen <[email protected]> --- functions | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/functions b/functions index 8218d68..8f9a5d2 100644 --- a/functions +++ b/functions @@ -590,11 +590,6 @@ set_consolefont() { done if (( $? )); then stat_fail - elif [[ $CONSOLEMAP ]]; then - cat <<"EOF" >>/etc/profile.d/locale.sh -if [ "$CONSOLE" = "" -a "$TERM" = "linux" -a -t 1 ]; then printf "\033(K"; fi -EOF - stat_done else stat_done fi -- 1.7.7.3
