mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Feb. 07 2007,11:40 |
 |
Well..... coffee is still on its way down the gullet, so I'm not fully understanding your situation, but I'm going to guess that it comes from removing EVERYTHING except /etc/shadow. The backup/restore system itself needs some specific files to remain persistent in order to work. In your case, you will at least need opt/.backup_device
Another possible problem is that you might be running with a previous backup that is restoring /home/dsl/.filetool.lst and other files in home, which is overwriting your persistent home files. If this is the case, delete your old backup.tar.gz, make the changes to /home/dsl/.filetool.lst, make sure you have the proper partition specified to backup, and then do the backup.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|