dCore Import Debian Packages to Mountable SCE extensions > dCore X86

Empty '.filetool.lst'

<< < (5/6) > >>

Jason W:
I remember long ago Robert saying that the entries in /opt/.filetool.lst had to not begin with a front slash and it was the user's responsibility to enter them that way.  They of course also need to be existing and the file not empty.

Thanks for having this in the wiki!

sm8ps:
It is mostly there already. Though, I intend to set up some pages about the basic functionality (sce-{load,import,remove}, .filetool.lst, seboot.lst etc.) that should provide the information in condensed form. The respective section is already put up on the welcome page. I yet have to master the subject for myself.  8)

sm8ps:
Upon second thought, I have decided against keeping '/opt/.filetool.lst' in the persistence mechanism. The problem is that this file may change quite often and if one should exit the system by 'reboot' then the changes would be lost. I shall rather be using some dummy file instead.
Sorry to revive this non-issue!

Rich:
Hi Jason W

--- Quote ---No clear way to distinguish between a file with spaces and one with text.
--- End quote ---
How about this:

--- Code: ---busybox grep -c "^$\|^\s" /opt/.filetool.lst
--- End code ---
If there are any blank lines or lines that start with a space, the count returned won't be zero. You could even flag leading slashes:

--- Code: ---busybox grep -c "^$\|^\s\|^/" /opt/.filetool.lst
--- End code ---

Jason W:
Thanks for the code, I will ponder putting it into a routine.

But blank lines existing in an otherwise correct .filetool.lst do not cause error.  So testing and exiting for a blank line existence will keep some folks who can backup without error from backing up.

Navigation

[0] Message Index

[#] Next page

[*] Previous page