On Wed, May 18, 2016 at 01:33:06PM -0300, Felipe Sateler wrote: > > Ok. I see that the rules file appears to invoke the scripts in /etc > directly. Is this intended
Yes. The keyboard is configured by /lib/console-setup/keyboard-setup.sh and the font by the scripts in /etc. Notice that /lib/console-setup/console-setup.sh does not run the scripts in /etc at all. If necessary it runs setupcon. > (IOW, shouldn't they invoke the wrappers at /lib/console-setup)? Although setupcon is an universal and reliable tool, this cames at a price --- it is slow. Many people have complained that console-setup slows down the boot and thats the only reason I decided to use scripts in /etc instead of setupcon. By the way, the only thing /lib/console-setup/console-setup.sh does in addition to the scripts in /etc is to rebuild the scripts in /etc if necessary. And it is necessary to rebuild these scripts only if the sysadmin modifies the console configuration by hand and doesn't run `setupcon --save-only` afterwards. In this case the wrapper will rebuild the scripts in /etc during the first reboot. > But upstream systemd and udev have pushed for mounting /usr in the > initramfs for a long time, Is there a place where one can learn about such things? > Note that because it has no WantedBy line, this service will not be > actually executed during boot. If the service should run as part of > normal system boot, it should have either WantedBy=sysinit.target or > WantedBy=multi-user.target. > Services WantedBy=sysinit.target will be pulled in both single user > and multi user boots. Services in multi-user.target will only be > pulled in multi user boots. OK, then it has to be WantedBy=multi-user.target. Rebuilding the scripts in /etc is not something we want in single user mode. Anton Zinoviev