Groups | Search | Server Info | Login | Register
Groups > alt.os.linux.debian > #10587
| From | Lawrence D'Oliveiro <ldo@nz.invalid> |
|---|---|
| Newsgroups | comp.sys.raspberry-pi, alt.os.linux.debian |
| Subject | Re: Execution of setupcon at boot |
| Date | 2024-09-15 23:58 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <vc7sb9$2elg0$2@dont-email.me> (permalink) |
| References | <vc7j35$7jfe$1@paganini.bofh.team> |
Cross-posted to 2 groups.
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? ;)
Back to alt.os.linux.debian | Previous | Next — Previous in thread | Next in thread | Find similar
Execution of setupcon at boot Anton Shepelev <ant@tilde.culb> - 2024-09-15 21:20 +0000
Re: Execution of setupcon at boot Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-09-15 23:58 +0000
Re: Execution of setupcon at boot Anton Shepelev <ant@tilde.culb> - 2024-09-17 23:43 +0000
Re: Execution of setupcon at boot Chris Green <cl@isbd.net> - 2024-09-16 07:18 +0100
Re: Execution of setupcon at boot Anton Shepelev <ant@tilde.culb> - 2024-09-17 23:47 +0000
csiph-web