dCore Import Debian Packages to Mountable SCE extensions > dCore X86

Empty '.filetool.lst'

(1/6) > >>

sm8ps:
Could somebody please have a look at http://wiki.tinycorelinux.net/dcore:basic_desktop_installation?&#persistence? I have my doubts about the handling of an empty '.filetool.lst'.

The situation arises in the following scenario: I have set up the installation from scratch with persistent home and opt on a dedicated partition. At first boot, '.filetool.lst' does contain "home" and "opt". Since persistence for those directories is not needed, I clean out that list.

Issueing 'backup' terminates without error. The graphical log-out dialogue, however, complains and points to '/tmp/backup_status' which contains "tar: /opt/.filetool.lst: No such file or directory". The file does exist but is empty, which must mess up a command line in a script.

I tried 'filetool.sh -b' which throws "sed: /opt/.filetool.lst: No such file or directory" but then says "Backing up files to .../tce/mydata.tgz".

The graphical 'filetool' throws "dc: stack underflow" and "ash: invalid number ''" (that is an empty string between two apostrophes) when performing a dry-run. Asked to perform a backup, it throws "sed: /opt/.filetool.lst: No such file or directory" and "tar: /opt/.filetool.lst: No such file or directory".

There still is need for the backup mechanism as there may be configuration files outside '/home' or '/opt' that should be made persistent, so the norestore boot-code cannot be used.

Is there a better strategy than the one presented in the wiki which seems a bit round-about?

Maybe the tools should check for an empty '.filetool.lst' and act appropriately? (I have not studied the code yet, sorry!)

curaga:
Why would you run a backup without backing anything up?

sm8ps:
I see the point in your counterquestion. Though, I am approaching the issue from a different direction.
When setting up persistent home and opt an hard-disk, there is no need for backing up these folders. Thus one may clear out '.filetool.lst'. However that does not mean that one will not need to back up configuration files. In the course of setting up the system that need will eventually arise. So the backup mechanism should be left in place, albeit with an empty list in the beginning.
Of course, there are several ways to handle this situation. I am looking at it through the eyes of new-comers who are not acquainted with the nuts and bolts of *Core and I am seeking the simple-most way of setting up dCore.
IMHO the case of an empty '.filetool.lst' is valid. It might be easy to handle if the scripts included a check for an empty file. Though, I do not know if this might have any undesirable effects.

gerald_clark:
touch /opt/placeholder
Add opt/placeholder to .filetool.lst.

Rich:
Hi sm8ps

--- Quote ---It might be easy to handle if the scripts included a check for an empty file.
--- End quote ---
I think a check for an empty file would be a good idea.

--- Quote ---Though, I do not know if this might have any undesirable effects.
--- End quote ---
/opt/shutdown.sh  looks for a flag called  /tmp/backup_done  which is created after running a back up.

Navigation

[0] Message Index

[#] Next page