Where Does Tiny Core Linux Store Backups and Settings?
Tiny Core persists settings through /opt/.filetool.lst into mydata.tgz, keeps extensions in the tce directory, and optionally binds home and opt persistently via boot codes.
Last updated
Tiny Core runs in RAM, so nothing persists unless you arrange it. The backup list at /opt/.filetool.lst names what gets saved, and filetool packs it into mydata.tgz at shutdown. Miss a file in the list and it vanishes on reboot by design.
Extensions live separately in the tce directory, which keeps the base system tiny. For heavier use, persistent home and opt bind those trees to disk with boot codes and bypass the archive. Check the backup device file first whenever settings mysteriously fail to survive a reboot.
Where Tiny Core Linux stores this, by platform
/opt/.filetool.lst
The include list for backups, paths relative to root without leading slash. Edit with sudo editor. Never remove the filetool.lst entry itself. Exclusions go in /opt/.xfiletool.lst beside it.
mydata.tgz
Find its device with cat /opt/.backup_device. Create manually with filetool.sh -b and list contents with filetool.sh -d. Rename via the mydata boot code if needed.
Frequently asked questions
Where is mydata.tgz stored?
Run cat /opt/.backup_device to see where it goes. Set it at boot with restore=hdXY or after boot from the Control Panel Backup Restore tool. Without a restore code Tiny Core searches available drives for mydata.tgz at startup.
How do I make home persistent instead of using backup?
Add home=sda1 and opt=sda1 (with your real device) to the bootloader, then remove home and opt from /opt/.filetool.lst so they are not double stored. Persistent mode skips the backup archive for those trees and writes straight to disk.
Notice an outdated path? Let us know.