Assuming the line was meant to read
[...] where in tc-config would i put a call to fbv [...]
I have currently no easy access to my Pi but I did add a boot animation using fbv which I think, apart from the fbv binary, is the exact same as on the laptop I'm typing on right now.
Here goes:
I edited /etc/init.d/rcS after the clear command to look like this
#!/bin/sh
# RC Script for Tiny Core Linux
# (c) Robert Shingledecker 2004-2012
# Mount /proc.
[ -f /proc/cmdline ] || /bin/mount /proc
# Remount rootfs rw.
/bin/mount -o remount,rw /
# Mount system devices from /etc/fstab.
/bin/mount -a
#clear
/etc/init.d/boot-anim.sh &
/etc/init.d/tc-config
/usr/bin/yes y | /bin/rm -rf /tmp/boot-anim
It's calling a script that I added (/etc/init.d/boot-anim.sh) before tc-config is called.
The scripts looks like this
#!/bin/sh
### Copyleft 2016 Misalf
ANIM_DIR="/tmp/boot-anim"
[ -d "$ANIM_DIR" ] || exit 0
cd "$ANIM_DIR"
OPTIONS=" -a -c -u -i -s -1 "
/usr/local/bin/fbv ${OPTIONS} "$(/bin/ls -1 | /usr/bin/head -1)" 2>/dev/null
ANIM_1="$(for i in *.png ; do [ ${i%*.png} -le 50 ] && echo "$i " ; done)"
ANIM_2="$(for i in *.png ; do [ ${i%*.png} -gt 50 ] && echo "$i " ; done)"
cd - >/dev/null 2>&1
sleep 0.6
for i in $ANIM_1 ; do [ -d "$ANIM_DIR" ] || break ; /usr/local/bin/fbv ${OPTIONS} "$ANIM_DIR"/$i 2>/dev/null ; sleep 0.04 ; done
while [ -d "$ANIM_DIR" ] ; do
for i in $ANIM_2 ; do [ -d "$ANIM_DIR" ] || break ; /usr/local/bin/fbv ${OPTIONS} "$ANIM_DIR"/$i 2>/dev/null ; sleep 0.05 ; done
done
/tmp/boot-anim is a directory containing a bunch of pictures that differ slightly to create an animation effect. It's already in the initrd but gets removed to free up RAM after tc-config has finished.
Also, at the very bottom of tc-config I added this line
[ -e /usr/local/bin/fbv ] && /usr/bin/killall -q fbv &