Tiny Core Linux

Tiny Core Base => Micro Core => Topic started by: jriker1 on January 09, 2017, 09:43:17 AM

Title: persistence
Post by: jriker1 on January 09, 2017, 09:43:17 AM
I assume "microcore" is the base core OS however I have installed Core (no GUI version) on a virtual machine, but looks like everytime I reboot or do something, not sure what yet, everything vanishes.  Looks like every single think I do shows up as some kind of device.  So after installing say a compiler and type "df" there are loads of devices with the names of all the installed packages.  Is there any way to make all of Core persistent?

Thanks.

JR
Title: Re: persistence
Post by: polikuo on January 09, 2017, 10:05:45 AM
Make sure you have tiny core installed on the drive, tiny core loads every thing in the RAM.
Do filetool.sh -bv to backup the system before you reboot.
You might find this helpful http://tinycorelinux.net/book.html (http://tinycorelinux.net/book.html)
Title: Re: persistence
Post by: coreplayer2 on January 09, 2017, 10:19:55 AM
Welcome jriker1

core (not microcore) is the base for a command line install


create a tce directory (/tce/optional) on the virtual drive to install extensions which are loop mounted on next boot.
As polikuo recommends, all the answers are in the book


Title: Re: persistence
Post by: Misalf on January 09, 2017, 10:21:06 AM
"Micro Core" is now just "Core".
If installed to hard disk, Core will  not  copy everything to RAM by default. Instead, extensions (installed applications) are loop mounted. That's what you see with  df .
Yes, you can make your customizations persistent.
However, your home directory and the root file system is in RAM by default, so each file you want to preserve needs to be explicitly specified in  /opt/.filetool.lst  and the  backup  command needs to be used before rebooting.
Title: Re: persistence
Post by: jriker1 on January 09, 2017, 11:35:42 AM
Thanks. Wow manually backing up to.  Missed that part.  Guess this OS isn't meant for frequent changes huh?  Which technically is part of my goal anyway once done.

JR
Title: Re: persistence
Post by: coreplayer2 on January 09, 2017, 11:51:29 AM
You can make as many changes as you like.  Just have to add changed files to the backup (if a backup is used).  iirc you can also simply type " backup "  after adding changed files

Title: Re: persistence
Post by: jriker1 on January 09, 2017, 12:22:14 PM
Just typing backup.  Does that backup the whole drive or just what's still in the filelist?
Title: Re: persistence
Post by: Misalf on January 09, 2017, 12:43:17 PM
Only entries from  /opt/.filetool.lst  are included in the backup file (/etc/sysconfig/tcedir/mydata.tgz).
Title: Re: persistence
Post by: bmarkus on January 09, 2017, 12:48:24 PM
Quote from: Misalf on January 09, 2017, 12:43:17 PM
Only entries from  /opt/.filetool.lst  are included in the backup file (/etc/sysconfig/tcedir/mydata.tgz).

Minus .xfiletool.lst
Title: Re: persistence
Post by: curaga on January 10, 2017, 04:41:14 AM
It's automatic when using the GUI, but on the command-line it's assumed people know what they're doing.
Title: Re: persistence
Post by: PDP-8 on May 26, 2019, 09:58:31 PM
Need more frequent saving of changes than at shutdown or just doing it manually?

Just put filetool.sh -bv into a cron job - say once an hour or whatever you feel comfortable with.

Boot with the cron cheatcode, or perhaps edit your boot stanza to make crond active at the start.