Now, it would arguably make sense to switch to. If you look into /usr/share/man/man1/, for instance, you'll see a lot of files similar to mv.1.gz, if not all of them are compressed. One thing that popped into my mind recently: man pages are routinely compressed with gzip. So, what you should or should not use, is what makes the most sense to you and the people interacting with your data. It's often used on systems where it's more important to quickly compress something with little power and computing space. I couldn't say it's not widely used, though. Just as a counter example, lzop is a fast and resource saving compressor, which is often used on spacecraft, but it otherwise not very efficient. tar.gz option being there, because it has been "around forever", and it's a good fall-back measure on any sort of device, no matter how minimal or old. ![]() ![]() Even though xz and LZMA2 has been around for years, people still consider compressing with gz as fall-back for compatibility reasons. What you should or should not use, depends on what you need your data for. It's not such a great decision for stream compression - at least not all that often, because LZMA2 isn't exactly light on resources, when compressing.īut I'd like to comment on one other statement of yours: "should". So it's great for things like archiving, or backing up (generally speaking, files that get decompressed a lot, but where data isn't compressed all the time, or changed, etc.). I personally use it for pretty much anything, where computational encoding speed is not an issue ( xz decompresses much faster than compressing, it's actually one of its design targets). The LZMA2 compression algorithm xz uses, is exceptionally efficient with text (and "text-like") data. If the command line options necessary for gunzip are different than unzip, you may have to modify the atool source (perl) itself.Xz has become a bit of a standard when it comes to package management in recent years. See the man page for the complete list of possible variables you can put in this config file, of which there are a lot. With the correct path to your gunzip program. and to use gunzip instead":Įdit the atool config file ~/.atoolrc and add the line: path_unzip /usr/bin/gunzip plausibly, most modern distributions.Īnswer for Updated Question "How can I configure something like atool to not use unzip to extract zip files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |