this post was submitted on 01 Jul 2026
238 points (98.8% liked)
Not The Onion
21939 readers
1057 users here now
Welcome
We're not The Onion! Not affiliated with them in any way! Not operated by them in any way! All the news here is real!
The Rules
Posts must be:
- Links to news stories from...
- ...credible sources, with...
- ...their original headlines, that...
- ...would make people who see the headline think, “That has got to be a story from The Onion, America’s Finest News Source.”
Please also avoid duplicates.
Comments and post content must abide by the server rules for Lemmy.world and generally abstain from trollish, bigoted, ableist, or otherwise disruptive behavior that makes this community less fun for everyone.
And that’s basically it!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't understand how people can be using that garbage when
tarexiststar doesn't even provide compression. Which may be what you want. If you have a weak CPU and a big storage device why would you waste the cpu cycles? I know I've removed the compression step in AUR builds for example. But if you don't know what it does, maybe an all in one solution like 7zip or winrar might be a more attractive prospect.
Compressed tars suck anyway since you need to decompress them in order to get the list of files inside, unlike in any other sane archive format.
The pixz compressor provides parallized compression/decompression (desirable on modern CPUs), uses LZMA (like 7zip or
xz), and provides indexed access when used astar'scompressor. The last of these is what you want.https://github.com/vasi/pixz
pixzis packaged in Debian-family distros.I very rarely list the content of compressed files, so that doesn't bother me much.
Back in the day the trick to get better compression on zip files was to first make an uncompressed zip file, and then put that in a compressed zip file.
tardid that all by itself!I mean that's what GUI archivers do when you open the file.
So tar is only useful for some kind of automatic workflows where archives are processed automatically. Like what package managers do.
The only thing I've done with a GUI archiver for the past 20+ years is right click on a file and select "extract to here". But more commonly I just extract things on the command line, without any automatic processing.
The tar format doesn't, but the
tarcommand has command line flags for a number of compression algorithms, and if your algorithm of choice doesn't have a flag, you can just pipe it to the compression program.