% setfont (anything in /usr/share/kbd/consolefonts/ ) works from console

Replacing the line FONT=!lat9w-16 in boot@ module has no effect

Why is this?
for each tty set at TTY=, the system-fontnkey service do: 
sh -c "setfont ${FONT_MAP:+-m $FONT_MAP} ${FONT_UNIMAP:+-u $FONT_UNIMAP} $FONT -C /dev/tty${index}"
I don't see anything in this command which can cause issue :/.
Then why isn't font changing when you change it in the module. The module should provide the variable for that service, correct? The same for all of the ttys I assume unless you individually configure them with a separate service file?

In any case both on hard and vm it is not changing.
From console the same font specified by setfont changes it
% sudo 66-inservice -v3 -p3 tty-rc@ tty1
Name                  : tty-rc@ tty1
Version               : 2.2.1
In tree               : boot
Status                : enabled, up (pid 929) 38962 seconds
Type                  : longrun
Description           : Launch tty1
Source                : /usr/lib/66/service/boot@ sys/service@ /tty-rc@ tty1
Live                  : /run/66/tree/0/boot/servicedirs/tty-rc@ tty1
Dependencies          : All
External dependencies : None
Optional dependencies : None
Start script          :  execl-cmdline -s { agetty ${cmd_args} tty1 } 
Stop script           : None
Environment source    : /etc/66/conf/boot@ sys/2.2.1/tty-rc@ tty1/2.2.1
Environment file      : cmd_args=!-J 38400
Log name              : None
Log destination       : None
Log file              : None

% sudo 66-inservice -v3 -p3 boot@ sys   
Name                  : boot@ sys
..
Environment file      : HOSTNAME=!bubba
                        TZ=Europe/Belgrade
                        TTY=!2
                        KEYMAP=!us
                        FONT=!sun12x22.psfu
                        .
                        .
                        .

% setfont sun12x22.psfu
good question :/. It should change it mostly when the service do not report any error...
I need to make test to see if it happens only for you or not.
18 days later
Many thanks for remember me this. Also, this bug do not depend of 66 at all but come from the boot@ -66serv service. I'm currently working on a new version and i will try to solve this issue in the same time.
13 days later
!Eureka! (!εύρηκα)!!!

Substitute in your module: 
FONT=sun12x22
# FONT=!lat9w-16

66-enable -t boot -F boot@ modulename
reboot

!!! Eureka
2 months later
Not solved, ever since the dreadful 6.1 release this sloppy fix is messed up again, among other things.
works on my end: 
# # Console font to load, see setfont(8).

FONT=Lat2-Terminus16
had to cp .boot@ <something> to boot@ <something> and since the latest update. unless im missing something.
@ fungalnet
As i said at post # 5 i can make many many release of 66, this will not solve the issue. The issue is a part of boot@ -66serv :).
@ negative
If you want to avoid the copy of the file manually, just run 66-env <service>. If the copy doesn't exist, it will create it for you :)
But the dirty solution worked with the 1st interim 0.6.0 edition, then 6.1 broke the dirty solution too, so editing again and adding the ! wouldn't change it either.

Unfortunately, for me to test things that broke with 0.6.1 0.5 doesn't exist in the obarchive :| and I have no cache left :(
I am cacheless .... disabled, done, finished ... :) F..reaking docker only in vm from now on, docker in container.
it's on the Archives now

Powered by Obarun