XPost: alt.os.linux.debian

In alt.os.linux.debian Chris Green <cl@isbd.net> wrote:

Anton Shepelev <ant@tilde.culb> wrote:

On RPi OS Bookworm, console and keyboard initialisation via
`setupcon' seem doubly duplicated (sic), and I am x-posting this to
.debian because it may not be speific to Pi OS:

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

2. in that /lib/console-setup/console-setup.sh includes both console
and keyboard setup, making keyboard-setup.sh redundant.

Isn't the init.d startup actually emulated by systemd when a system
uses systemd? The files still exist but the implementation is systemd.

Yes, but why the duplication? The emulation of init.d is there for
functonality that has not yet been migrated to systemd services, whereas
the console and keyboard setup are /already/ present and propser systemd services, and therefore no longer needed in init.d .

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)

XPost: alt.os.linux.debian

In alt.os.linux.debian Lawrence D'Oliveiro <ldo@nz.invalid> wrote:

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.

Of course, but I don't thinkg the duplication is required for that compatibitly: systemd executes everything from /etc/init.d /and/ also
from its service records. Therefore, each init service should be
implemented as /eiterh/ one or the other, but not as both.

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.

I the part you snipped, I write that I have done as I proposed, and it
works for me. Futhermore, the original Pi OS config does not work for
me, wherefore I asked (also snipped) if anybody else has been able to
use it as is.

--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)