I couldn't reply to the original topic and response by Fanthom so I'm transferring them here:
Just a issue for the clarity of newbies and Porteus beginners, is it possible for the .dat file saver to do a tally sum of all the files that would fill one's (minimum-sized) .dat file? It seems that one could only size a .dat file for one's particular set-up now by sheer guesswork, which invites gross overestimation or undersized .dat files that'll leave out files meant to save. It'd help demystify and de-geek the use of .dat files and make it more friendly for them to use.Postby fanthom » 25 Feb 2014, 03:48
how does one know whether it's large enough or too excessively large just to save what you need?
depends what you use Porteus for (downloading many youtube videos?). system itself should take about 50MB but mind that firefox files/kde thumbnail caches/etc will grow quickly so i would go with 1GB on start.
Can you "undersize" a savefile.dat and unwittingly omit files you hope to save?
save.dat manager offers an option to resize container so it should be possible to make it smaller. run 'df -h' and check how much free space aufs has. if it's few hundreds MB then you could make it smaller but mind above - caches will be growing so probably would be wise to disable them. go to /mnt/live/memory/changes and identify which apps produces biggest files -> search on google how to disable this.
On log-off or mid-session we wish to simultaneously create or update a savefile.dat file as a off HD backup while also still having the identical date saved as "normal" Porteus Changes files. Is there any script that permits this?
nothing i know about
Simultaneous normal and .dat savefiles saving is a top wish lister!
Jim In NYC