When you boot the Network Security Toolkit CDROM, it assumes that you will be using a us style keyboard and uses the default font from your computer's BIOS (I admit that I'm guessing a bit on the font statement).

If you don't have a "us" keyboard, you will find this quite aggravating as some keys that you press will not yield the desired results. For example, the '@' and '"' characters appear to be swapped on a "uk" keyboard.

To fix the keyboard problem, you will want to run the loadkeys utility.

[root@probe root]# loadkeys uk
Loading //lib/kbd/keymaps/i386/qwerty/uk.map.gz
[root@probe root]# 

Knowing that the loadkeys and setfont utilities are available on the system is useful. However, knowing what choices are available can be a bit tricky. The following command can be used to list the available keyboard maps:

[root@probe root]# (cd /lib/kbd/keymaps/i386; find . -name "*.map.gz") | less
./azerty/azerty.map.gz
./azerty/be-latin1.map.gz
./azerty/fr-latin1.map.gz
./azerty/fr-latin9.map.gz
./azerty/fr.map.gz
./azerty/fr-pc.map.gz
./azerty/wangbe2.map.gz
./azerty/wangbe.map.gz
./dvorak/ANSI-dvorak.map.gz
./dvorak/dvorak-l.map.gz
./dvorak/dvorak.map.gz
./dvorak/dvorak-r.map.gz
./fgGIod/trf.map.gz
./fgGIod/tr_f-latin5.map.gz
./include/applkey.map.gz
./include/backspace.map.gz
./include/ctrl.map.gz
./include/euro1.map.gz
./include/euro2.map.gz
./include/euro.map.gz
./include/keypad.map.gz
./include/unicode.map.gz
./include/windowkeys.map.gz
:q
[root@probe root]# 

You should be able to specify key map files that are NOT in the include directory. For example, "loadkeys wangbe" should work (and load the keyboard map file ./azerty/wangbe.map.gz shown above). However, "loadkeys ctrl" will not work as the ctrl.map.gz file resides in the include directory.