As noted in the other thread, you can do a remaster to include ntfs-3g in the image.
Also, the in-kernel ntfs write support is practically useless:
"The only supported operation is overwriting existing files, without
changing the file length."
If I remaster with ntfs support and my usb stick has sdb1(ntfs) and sdb2(ext3) how would I specify at boot that my tce directory should live in sdb1 ?
With my original bzImage, my current grub.cfg is :
insmod ext2
set root='(hd0,2)'
linux /boot/bzImage tce=sdb2 opt=sdb2 home=sdb2 waitusb=5 laptop
initrd /boot/tinycore.gz
boot
I'm guessing that if I remaster tinycore.gz with ntfs I can just use :
insmod ext2
set root='(hd0,2)'
linux /boot/bzImage tce=sdb1/tinycore opt=sdb1/tinycore home=sdb1/tinycore waitusb=5 laptop
initrd /boot/tinycore.gz
boot
Would that be a valid grub.cfg?
I'm wondering if I can do the following :
insmod ext2
set root='(hd0,2)'
linux /boot/bzImage tcvd=sdb1/tinycore/tc.img tce=tcvd opt=tcvd home=tcvd waitusb=5 laptop
initrd /boot/tinycore.gz
boot
Is that okay? If I could do this it would be possible to keep my boot partition sdb1 hidden from windows, and still share my programs with a qemu install in sdb2.