sudo loadkmap < /usr/share/kmap/qwerty/fi-latin9.kmap
but it doesn't change the symbolssude cp -f /sdb1/MPLUS1p-Medium.ttf /usr/share/fonts/
sudo loadkmap < /usr/share/kmap/qwerty/fi-latin9.kmap
startx
If the keyboard is to your liking, click on the Editor icon and add the following line to your /opt/bootsync.sh file:loadkmap < /usr/share/kmap/qwerty/fi-latin9.kmap
sudo loadkmap < /usr/share/kmap/qwerty/jp106.kmap
startx
loadkmap < /usr/share/kmap/qwerty/jp106.kmap
Saved the file.showbootcodes
cat /opt/,filetool.lst
cat /opt/bootlocal.sh
showbootcodes
gave meBOOT_IMAGE=/tce/boot/vmlinuz quiet waitusb=5:UUID="7fb56286-fb74-42a4-8761-c9f348a0e2d1" tce=UUID="7fb56286-fb74-42a4-8761-c9f348a0e2d1" initrd=/tce/boot/core.gz
cat /opt/.filetool.lst
gave meopt
home
cat /opt/bootlocal.sh
gave me#!/bin/sh
# put other system startup commands here
ifconfig wlan0 up
wpa_supplicant -iwlan0 -c/home/tc/wifi.cfg -Dwext -B
udhcpc -i wlan0 -t 10
loadkmap < /usr/share/kmap/qwerty/jp106.kmap
... However, if I click EXIT and EXIT TO PROMPT, I can type " with no problem. If I erase " and type STARTX, I can still type " with no problem. ...So, if I understand you correctly, just doing Exit to Prompt and then startx fixes it?
loadkmap < /usr/share/kmap/qwerty/jp106.kmap
from bootlocal.sh to bootsync.sh.loadkmap < /usr/share/kmap/qwerty/jp106.kmap
/opt/bootlocal.sh &
sudo chown tc:staff /opt/bootsync.sh
sudo chmod 775 /opt/bootsync.sh
1. bootsync.sh is launched almost at the end of tc-config.
2. bootsync.sh runs synchronously in the foreground effectively blocking tc-config from running until it completes.
3. The last line in bootsync.sh launches bootlocal.sh to run in the background. This allows tc-config to continue
executing in parallel with bootlocal.sh.
4. tc-config executes its last few commands and returns control to /etc/inittab.
5. /etc/inittab logs in the user which executes the contents ~/.profile which launches X
6. We now have a potential race between bootlocal.sh completing and X starting.
... Had a minor problem with a misspelling (wrote "loadmap" instead of "loadkmap"), but it was easily found and fixed. ...That was my fault. I copy/pasted your misspelling from another post. :) I will fix those posts.
sudo cp -f /sdb1/MPLUS1p-Medium.ttf /usr/share/fonts/
Back to the font problem.
tldr version: Put a new font in /usr/share/fonts/ but it disappears on reboot. ...
Most Linux distros have a persistent file system (/bin, /dev, /etc, /home, /lib, ..... ). When packages get installed, their files get copied
to /usr (/usr/local/bin, /usr/local/lib, ..... ).
Tinycore is different. The file system gets created from scratch every time you boot. This diagram may help:
http://distro.ibiblio.org/tinycorelinux/architecture.html
usr/share/fonts/MPLUS1p-Medium.ttf
Then run a backup.Some advice says put is in /usr/local/share/fonts/ ...That's the preferred location, unless an application is hard coded to look in /usr/share/fonts/.
Other advice says maybe put it in ~/.fonts ... but I don't know where that is.When you see ~/ its referring to your home directory (/home/tc/). A filename that begins with a period (.font) is a hidden file.
tce-load -wi squashfs-tools
mkdir -p pkg/usr/local/share/fonts
cp /sdb1/MPLUS1p-Medium.ttf pkg/usr/local/share/fonts/
mksquashfs pkg MPLUS1p-Medium.tcz
cp MPLUS1p-Medium.tcz /etc/sysconfig/tcedir/optional
echo MPLUS1p-Medium.tcz >> /etc/sysconfig/tcedir/onboot.lst
tce-load -i MPLUS1p-Medium.tcz
Your fonts should now be installed and will also get loaded when you boot.