Path: ...!3.eu.feeder.erje.net!2.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.sys.raspberry-pi,alt.os.linux.debian
Subject: Re: Execution of setupcon at boot
Date: Sun, 15 Sep 2024 23:58:34 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <vc7sb9$2elg0$2@dont-email.me>
References: <vc7j35$7jfe$1@paganini.bofh.team>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Mon, 16 Sep 2024 01:58:34 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="9f60c74fd4acdc7bec2c97436300fd05";
	logging-data="2577920"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/JEfm2EkoGlYhKL+rOo4pn"
User-Agent: Pan/0.160 (Toresk; )
Cancel-Lock: sha1:FfiLLxgzsOQVc/urvTMRvq3lDlo=
Bytes: 2024

On Sun, 15 Sep 2024 21:20:37 -0000 (UTC), Anton Shepelev wrote:

> 1. in that systemd services and init.d scripts do the same thing:
>      /etc/init.d:
>         console-setup.sh       -> /lib/console-setup/console-setup.sh
>         keyboard-setup.sh      -> /lib/console-setup/keyboard-setup.sh
> 
>      /usr/lib/systemd/system:
>         console-setup.service  -> /lib/console-setup/console-setup.sh
>         keyboard-setup.service -> /lib/console-setup/keyboard-setup.sh

Remember that systemd includes a high degree of backward compatibility 
with old sysvinit scripts. That would be why you see the exact same things 
showing up in both init.d and systemd. This way, “systemctl start/stop” is 
able to start/stop sysvinit scripts, without you having to know the 
difference.

> Therefore, I think that all this confusing complexity can be reduced to
> a very simple invocation that configures both keyboard and console:

Well, the only way to know for sure is to try it.

What have you got to lose? ;)