I have raised a bug because the current system back in yast only offers an incremental backup - so if you loose the first achieve your stuffed. The reply came back and described it as a Hugh code re-write within Yast and it was just a font end based on ---I forgot: I suggested that the new front end should be written around CPIO . The bug is now Assigned for a LATER status.. - Cross you fingers everyone Scott Carlos E. R. wrote:
The Friday 2007-02-23 at 12:39 -0000, David Bolt wrote:
What is par2? The home page describing it is here:
Interestingly, the distro has a "par" from that same page, but not "par". There isn't even a man page for "par". I guess from what you say that they are not the same. [...] I saw a link explaining the differences.
What would I need to compile - from sourceforge?
gpar2-0.3.tar.gz libpar2-0.2.tar.gz par2cmdline-0.4.tar.gz
Curiously, they have "par-v0.1alpha.tar.gz", when suse has "par-1.1-62" [...] AH! It is hidden as "older releases", "par-v1.1.tar.gz".
[...]
The make run (par2cmdline-0.4) fails...
reedsolomon.cpp:54: error: explicit specialization of bool ReedSolomon<Galois<8u, 285u, unsigned char> >::SetInput(const std::vector<bool, std::allocator<bool> >&) must be introduced by template <> reedsolomon.cpp:54: error: template-id SetInput<> for bool ReedSolomon<Galois<8u, 285u, unsigned char> >::SetInput(const std::vector<bool, std::allocator<bool> >&) does not match any template declaration reedsolomon.cpp:54: error: invalid function declaration
And a lot more.
...
With the values I use, I should be able to recreate upto 5 missing files, or significantly more files if dd can copy most of the data.
Interesting :-)
What are you using, where did you get it from? Source code from sourceforge, patched it to handle GCC4, and then built an RPM for it. I keep copies of it built for multiple versions of SUSE here:
Ah! So you had to modify them...
But... that is version "par2-0.4-5". At <http://sourceforge.net/projects/parchive> I can only see release 0.3 (feb 2006). Where does the 0.4.5 comes from?
Now I wonder if the "dar" we have in the distro has that implemented [...] it seems it does. Dar may have PAR support built in but, since PAR2 hasn't been included in SUSE, I don't think it'll have PAR2 support. It may have but, since I haven't used dar, I've no idea.
No, it is "par" - form man dar:
This has of course its limitations, in particular when a data corruption occurs in the vital part of the backup, i.e. the few first bytes of each slice, and the last part of the archive (the catalogue). In case you need to store archive on a bad quality medium, you could protect each slice with a Parchive recovery file. (see NOTES for more information about Parchive, and how to transparently run Parchive from dar)