Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: hypersonic on October 19, 2011, 05:15:46 PM
-
Ok. I've installed Tiny Core on USB. I just lost all my backup, simply by restarting the computer. The first few times it happened, I thought it was just some wrong configuration. This should happen?
-
Funny, this time my .filetool.sh is intact... Here is my .filetool.sh:
# tiny core persistence
opt
# xorg persistence
etc/X11/xorg.conf
# root password persistence
etc/passwd
etc/shadow
etc/gshadow
# rails persistence
usr/local/lib/ruby
usr/local/bin
usr/local/bin/install
# fluxbox persistence
usr/local/share/fluxbox/styles/darkmatter
So: opt, usr/local/bin, usr/local/bin/install and usr/local/share/fluxbox/styles/darkmatter was totally restored. File /usr/local/lib/ruby was partially restored (miss site_ruby file). And the rest was not recovered.
-
.filetool.sh is meaningless.
The file should be .filetool.lst and it cannot contain comments.
-
Ops, its .filetool.lst... sorry. I removed comments, and I found a solution for another post. I suspected that this problem (about persistence) could be caused by backup files size (around 200 MB unpacked). Then by chance I found this wiki page: http://wiki.tinycorelinux.net/wiki:extension_for_settings (http://wiki.tinycorelinux.net/wiki:extension_for_settings), and created an extension TCZ for ruby folder. So I really don't know if this problem is caused by backup size or the comments...
If help someone, I put how I did a TCZ extension of ruby file on this post: http://forum.tinycorelinux.net/index.php/topic,11656.0.html (http://forum.tinycorelinux.net/index.php/topic,11656.0.html)
-
I was having this problem of backup loss before use comments in filetool.lst...
-
You have other problems with your .filetool.lst.
opt should not be included as a directory.
You have directories and their subdirectories included.
You are not running a standard configuration, as you have not included home.
You probably had errors in it then too.
-
I don't see any errors beside that I've related, but thanks for the tip. Home is not included on .filetool.lst because its already persistent by extlinux.conf
-
That's your problem. You don't see the errors even after they are pointed out to you.
-
I've seen the error in .filetool.lst, again, thanks for the tips. What I meant was that I did not see any errors that may compromise my normal use of the system. I'm no longer posting on this forum. Thanks all for everything
-
opt in .filetool.lst will cause you many problems, as a restore will overwrite dynamic system information.
You must list each individual file in /opt that you wish to backup.
-
Hi hypersonic
You probably should not be backing up /usr/local/bin. Any special reason you added that?
-
Since when are you supposed to put home in backup?
-
Hi hiro
If you have a non-persistent home, it should be in backup. In hypersonic's case, based on what
he wrote in another thread, he shouldn't.
-
I'm asking because I used to only put specific files/folders from my home folder in backup so that I don't have too much work putting all the others in .xfiletool.
-
Hi hiro
The stock .filetool.lst has home included and .xfiletool.lst contains certain exemptions. This
serves as a good starting point for new users with a non-persistent home which then can be
modified to suit ones needs.
-
Please do a man on the tar command. Specifcally the -T option and the -X option.
You can even use google, bing, duck duck go, yahoo. It is not rocket science. It is not unique to Tiny Core.
Hint. -T uses /opt/.filetool.lst -X uses /opt/.xfiletool.lst
Simple basic file managment. Static content should not be included in backup but should be a candidate for a personal extension or stored on other persistent store.
This procedure has been in public use for 8 years across two distributions and is covered in the Core Concepts document.
Persistent does not fail unless caused by user error in not understanding the basics involved.
-
Ok, I thought not having home in .filetool was "unsupported" when I read the sentence "That's your problem.". I'm happy to see this is not the case.