Sujet : Re: Execution of setupcon at boot
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.sys.raspberry-pi alt.os.linux.debianDate : 16. Sep 2024, 00:58:34
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vc7sb9$2elg0$2@dont-email.me>
References : 1
User-Agent : Pan/0.160 (Toresk; )
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? ;)
Execution of setupcon at boot
Re: Execution of setupcon at boot