INTL 3:770/1 3:770/3   
   REPLYADDR ldo@nz.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  41bad01d   
   REPLY:  4892b697   
   PID: SoupGate-Win32 v1.05   
   XPost: alt.os.linux.debian   
      
   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? ;)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 10/0 1 90/1 103/705 105/81 106/201 124/5016 129/305 153/757   
   SEEN-BY: 153/7715 218/0 1 601 700 840 870 930 220/70 221/1 6 360 226/17   
   SEEN-BY: 226/30 100 227/114 229/110 111 114 200 206 300 317 400 426   
   SEEN-BY: 229/428 470 550 616 664 700 240/1120 266/512 267/800 282/1038   
   SEEN-BY: 291/111 292/854 301/1 113 812 310/31 320/219 322/757 335/364   
   SEEN-BY: 341/66 342/200 396/45 460/58 633/280 712/848 770/1 3 100   
   SEEN-BY: 770/330 340 772/210 220 230 5020/400 1042 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426