Backing up changes
ReSling is a useful script if you want an easy way for backing up files you have modified. It saves all files which are in the /unslung/ directory and puts them in a .tar.gz file. The file is saved on the first data partition it finds.
Its also possible to save files or directories which are not in /unslung by adding them to the file /unslung/.files (one file or dir per line!)
extracts the resling.tar.gz file to the root filesys.
deletes the resling.tar.gz on the first data partition.
extracts the resling.tar.gz file to the root filesys and lists the extracted files.
lists all files and dirs which are saved in the resling.tar.gz file on the the first data partition.
backups the files and dirs in the /unslung dir and everything which is in the .files file and puts it in the file resling.tar.gz on the the first data partition.
sample file /unslung/.files
Finding changed files on the root file system
If you have not installed Busybox 1.0, you can install
If you have unsling'ed to a hard drive, my suggestion (which is a huge hack that will make me enemies across the globe) is that you do in fact install Busybox 1.0, but mark it as not installed in the ipkg status file (just delete the Busybox 1.0 section in
which will produce a list of all changed files and directories on the root/flash file system since the last modification of the resling file list. If you haven't created the
Just bring it into your editor and remove irrelevant changes to the flash file system, leaving the files you want to resling. Finally you add them to your
btw: the ipkg-load script helps to reinstall all your packages.
A handy hint so you don't get caught out like I did... Double check where the saved resling.tar.gz gets sent to. It defaults to /share/flash/data if you don't have one already in /share/hdd/data, which gets lost on reboot if this filesystem isn't mounted. So when you run "resling save" copy the file to the mounted filesystem you want to, then future reslings will work correctly.