D
Deleted member 67440
Guest
I would like to issue a friendly challenge for those interested in backups.
I apologize, but on the other hand I realize that it is difficult to "trust".
Try at least one time my fork of a program already in ports (archivers\paq), which has remained in very old version.
It is an opensource program, 7z or RAR style to understand, with the ability to maintain a sort of "snapshot" of the data.
At every run only data changed since the last execution will be added, creating a new version (just like a snapshot).
It is then possible to restore the data @ the single version
It shouldn't be difficult to understand its enormous potential, especially for those used to snapshots (by zfs or virtual machines).
Who did that?
One of the world's leading scientists in compression (Matt Mahoney, the inventor of PAQs for those who know this area).
This guy http://mattmahoney.net/dc/
en.wikipedia.org
When?
From 2009 to 2016.
Where?
On a Russian compression forum, one of the most famous, but obviously super-niche
Why is it not known as 7z or RAR, despite being enormously superior?
Because lack of users who ... try it!
Who are you?
A user (and a developer) who has proposed and made various improvements that have been implemented over the years.
When the author left the project, I took charge of it, to insert the functions I need as a data storage manager.
Why it is not in the BSD ports?
I'm trying, but frankly I'm not very practical, that's why I joined this forum
If you give me a hand I'll be happy to submit it!
Why is it no longer developed? Why should I use your fork?
Because mr. Mahoney is now retired and no longer supports it (he... run!)
Why should I trust? It will be one of 1000 other programs that silently fail and give problems
As the Russians say, trust me, but check.
How can I do?
This is my first try to make a port, it's not the last version, but should work
How can I get the last version? I want to see with my eyes and compile myself, just to be sure!
Get this (yes, a single file)
github.com
And compile straight with
Archiving data requires safety. How can I be sure that I can then extract them without problems?
It is precisely the portion of the program that I have evolved, implementing a barrage of controls up to the paranoid level, and more.
I don't think to talk about it now (too long, I should put the link to the Russian forum), but let's say there are verification mechanisms which you have probably never seen.
I do not trust you, but I am becoming curious. So?
You can try to build the port (of paq, inside archivers) but it is very, very, very old (2014).
You can download the original version (7.15 of 2016) directly from the author's website, and compile it, or get the original from github.
In this case be careful, because the source is divided into 3 source files, but nothing difficult for the compilation.
OK, let's assume I want to try it out. How?
Try this
(a backup of /home and /etc into /tmp/test.zpaq, of course you need enough space!)
This is the first version
Do something into home (copy file, edit, etc). Duplicate a directory.
Edit something into /etc
Then run again (same command), this is the second.
Do something more into home (delete file, copy, edit etc).
The run again (same command) the third version
After that we'll talk about it
And trust me, you never believed it was true, if you didn't do it yourself.
I apologize, but on the other hand I realize that it is difficult to "trust".
Try at least one time my fork of a program already in ports (archivers\paq), which has remained in very old version.
It is an opensource program, 7z or RAR style to understand, with the ability to maintain a sort of "snapshot" of the data.
At every run only data changed since the last execution will be added, creating a new version (just like a snapshot).
It is then possible to restore the data @ the single version
It shouldn't be difficult to understand its enormous potential, especially for those used to snapshots (by zfs or virtual machines).
Who did that?
One of the world's leading scientists in compression (Matt Mahoney, the inventor of PAQs for those who know this area).
This guy http://mattmahoney.net/dc/
ZPAQ - Wikipedia
When?
From 2009 to 2016.
Where?
On a Russian compression forum, one of the most famous, but obviously super-niche
Why is it not known as 7z or RAR, despite being enormously superior?
Because lack of users who ... try it!
Who are you?
A user (and a developer) who has proposed and made various improvements that have been implemented over the years.
When the author left the project, I took charge of it, to insert the functions I need as a data storage manager.
Why it is not in the BSD ports?
I'm trying, but frankly I'm not very practical, that's why I joined this forum
If you give me a hand I'll be happy to submit it!
Why is it no longer developed? Why should I use your fork?
Because mr. Mahoney is now retired and no longer supports it (he... run!)
Why should I trust? It will be one of 1000 other programs that silently fail and give problems
As the Russians say, trust me, but check.
How can I do?
This is my first try to make a port, it's not the last version, but should work
Code:
mkdir /tmp/testme
cd /tmp/testme
wget http://www.francocorbelli.it/zpaqfranz/ports-51.10.tar.gz
tar -xvf ports-51.10.tar.gz
make install cleanHow can I get the last version? I want to see with my eyes and compile myself, just to be sure!
Get this (yes, a single file)
zpaqfranz/zpaqfranz.cpp at main · fcorbelli/zpaqfranz
Deduplicating archiver with encryption and paranoid-level tests. Swiss army knife for the serious backup and disaster recovery manager. Ransomware neutralizer. Win/Linux/Unix - fcorbelli/zpaqfranz
github.com
Code:
Windows 64 (g++ 7.3.0)
g++ -O3 zpaqfranz.cpp -o zpaqfranz
Windows 32 (g++ 7.3.0 64 bit)
c:\mingw32\bin\g++ -m32 -O3 zpaqfranz.cpp -o zpaqfranz32 -pthread -static
FreeBSD (11.x) gcc 7
gcc7 -O3 -march=native -Dunix zpaqfranz.cpp -static -lstdc++ -pthread -o zpaqfranz -static -lm
FreeBSD (12.1) gcc 9.3.0
g++ -O3 -march=native -Dunix zpaqfranz.cpp -pthread -o zpaqfranz -static-libstdc++ -static-libgcc
FreeBSD (11.4) gcc 10.2.0
g++ -O3 -march=native -Dunix zpaqfranz.cpp -pthread -o zpaqfranz -static-libstdc++ -static-libgcc -Wno-stringop-overflow
FreeBSD (11.3) clang 6.0.0
clang++ -march=native -Dunix zpaqfranz.cpp -pthread -o zpaqfranz -static
Debian Linux (10/11) gcc 8.3.0
g++ -O3 -Dunix zpaqfranz.cpp -pthread -o zpaqfranz -static
QNAP NAS TS-431P3 (Annapurna AL314) gcc 7.4.0
g++ -Dunix zpaqfranz.cpp -pthread -o zpaqfranz -Wno-psabiArchiving data requires safety. How can I be sure that I can then extract them without problems?
It is precisely the portion of the program that I have evolved, implementing a barrage of controls up to the paranoid level, and more.
I don't think to talk about it now (too long, I should put the link to the Russian forum), but let's say there are verification mechanisms which you have probably never seen.
I do not trust you, but I am becoming curious. So?
You can try to build the port (of paq, inside archivers) but it is very, very, very old (2014).
You can download the original version (7.15 of 2016) directly from the author's website, and compile it, or get the original from github.
In this case be careful, because the source is divided into 3 source files, but nothing difficult for the compilation.
OK, let's assume I want to try it out. How?
Try this
Code:
zpaqfranz a /tmp/test.zpaq /home /etcThis is the first version
Do something into home (copy file, edit, etc). Duplicate a directory.
Edit something into /etc
Then run again (same command), this is the second.
Do something more into home (delete file, copy, edit etc).
The run again (same command) the third version
After that we'll talk about it
And trust me, you never believed it was true, if you didn't do it yourself.
)