-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[photorec] Feature: Only create report.xml #17
Comments
I can probably write this myself, but it might take me a while to get acquainted enough with the code. Could you please give me pointers where to look? Conversely, maybe it's so simple that it's easier for you to do it yourself? Thanks a lot! |
Without writing the file to the disk, it's not possible to do all checks. |
Thanks! |
Coming next, I'm planning to write a lib which parses this xml and makes it available via fusermount. I don't think it fits here, but I will update anyway, for future seekers. |
When recovering from a large disk, one might want to omit some files which are too big, or known to exist elsewhere, etc. Conversely, one might want to compare recoveries with different parameters, different tools, etc.
Currently, one still needs to have enough free disk space to have all these redundant files, or to have all versions of recovery. I suggest to have an option where photorec performs all the analysis, but doesn't actually write the recovered data to disk. It is simple enough, afterwards, to recover the actual files one wants by reading the xml, and most likely much less time consumptive than the original analysis. (Of course, there can also be a feature for processing a report.xml and recovering by its spec, so one can simply delete the items which are unwanted, but I assume this is a much larger feature.)
The text was updated successfully, but these errors were encountered: