fpart
libarchive
Our great sponsors
fpart | libarchive | |
---|---|---|
5 | 33 | |
213 | 2,861 | |
- | 3.8% | |
7.9 | 8.8 | |
2 months ago | 5 days ago | |
C | C | |
BSD 2-clause "Simplified" License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
fpart
-
Rsync extremely slow on two ZFS local pools
Native rsync is terrible for lots of small file as it copies each file one by one sequentially. If you have lots of cores to work with, use the fpsync utility that comes with the fpart command to run parallel rsync's. You can easily saturate a 10Gb link with multiple rsync processes in parallel
-
Am I crazy to expect 100gbps across the pacific ocean?
You should probably use something like fpsync and multiple rsync jobs to get the most bandwidth.
-
zfs replication vs multithreaded rsync
I've migrated data from our Isilon to zfs hostA using the fpsync tool that comes with the fpart utility. I get reasonably good throughput from this. 15TB in 5 and 1/2 hours
libarchive
-
Backdoor in upstream xz/liblzma leading to SSH server compromise
Potentially malicious commit by same author on libarchive: https://github.com/libarchive/libarchive/pull/1609
The PR is pretty devious.
JiaT75 claims is "Added the error text when printing out warning and errors in bsdtar when untaring. Previously, there were cryptic error messages" and cites this as fixing a previous issue.
https://github.com/libarchive/libarchive/pull/1609
However it doesn't actually do that. It literally removes a new line between 2 arguments on the first `safe_fprintf()` call, and converts the `safe_fprintf()` to unsafe direct calls to `fprintf()`. In all cases, the arguments to these functions are exactly the same! So it doesn't actually make ther error messages any different, it doesn't actually solve the issue it references. And the maintainer accepted it with no comments!
- WinRAR musste shady werden.
-
WinRAR zero-day exploited since April to hack trading accounts
I don't have a preview channel install handy to check, but apparently they're using libarchive so here's the full list assuming they expose everything it supports:
https://github.com/libarchive/libarchive/wiki/LibarchiveForm...
-
Thanks for everything, WinRAR: Windows is finally getting native RAR support
libarchive is an existing open source project. Replacing the older compression code with libarchive was probably not that complicated and they'll get bug fixes from that active open source project for free. I would not be surprised if the initial port to libarchive was done by one person in a single day.
-
28 years later, Windows finally supports RAR files
And well, if you took a second to read the libarchive documentation (supported file formats) you'd find the following bullet point:
Read-only support (via libarchive). You still need the WinRAR app to create new RAR archives.
-
Microsoft adding RAR, 7z, Gz and more to the native ZIP extractor, and finally having it use more than 1 CPU core.
Be the change you want to see in this world!
What are some alternatives?
ZLib - A massively spiffy yet delicately unobtrusive compression library.
7z - Because 7-zip source code was in a 7z archive [mirror]
p7zip - A new p7zip fork with additional codecs and improvements (forked from https://sourceforge.net/projects/sevenzip/ AND https://sourceforge.net/projects/p7zip/).
TDengine - TDengine is an open source, high-performance, cloud native time-series database optimized for Internet of Things (IoT), Connected Cars, Industrial IoT and DevOps.
pgBackRest - Reliable PostgreSQL Backup & Restore
Klib - A standalone and lightweight C library
criu - Checkpoint/Restore tool
pixz - Parallel, indexed xz compressor
ck - Concurrency primitives, safe memory reclamation mechanisms and non-blocking (including lock-free) data structures designed to aid in the research, design and implementation of high performance concurrent systems developed in C99+.
OpenSSL - TLS/SSL and crypto library
sanoid - These are policy-driven snapshot management and replication tools which use OpenZFS for underlying next-gen storage. (Btrfs support plans are shelved unless and until btrfs becomes reliable.)
net_skeleton - Async non-blocking multi-protocol networking library for C/C++