bootlocal.sh and kmap persistancy

[alu]

as I want to boot tc with my kmap (de_CH-latin1.kmap) I have written a line in the bootlocal.sh file, which looks like this:

#!/bin/sh
# put other system startup command here
/opt/ath0.sh &
loadkmap < /usr/share/kmap/de_CH-latin1.kmap

Each time when I reboot (with backup), and open a term and want to modprobe my ath_pci, it appears that my kmap is us. Looking into the bootlocal.sh, I see that the line "loadkmap..." is no more there. I am sure that I am making something wrong, but what.
Thanks for help and congrats for this excellent distro.

[^thehatsrule^]

Did the backup succeed?  Look for mydata.tgz, and see what opt/bootlocal.sh contains in there.
Did the (subsequent) boot restore?

[roberts]

And if you are using a slow device, like a pendrive, you will likely need the boot option waitusb=5

[alu]

I have the waitusb=5 line, but it seems that the problem was in the bootlocal.sh file backed up.

So from the beginning on: I run tc, and I open bootlocal.sh (emelfm-->edit); I read:

#!/bin/sh
# put other system startup command here
/opt/ath0.sh &
loadkmap < /usr/share/kmap/de_CH-latin1.kmap

But in the bootlocal.sh backed up, I read:

#!/bin/sh
# put other system startup command here
loadkmap < /usr/share/kmap/de_CH-latin1.kmap/opt/ath0.sh &

I removed the file in my backup, and edit a new one with the following lines:

#!/bin/sh
# put other system startup command here
loadkmap < /usr/share/kmap/de_CH-latin1.kmap
/opt/ath0.sh &

I shut down TC and backup my files. I run TC again and now, the persistancy works both for my kmap and for wireless.