MKZFTREE(1)

🎀 MKZFTREE(1) — mkzftree 🎀

okay so bestie, this is the mkzftree(1) page, and it’s literally all about turning a file tree into a compressed one. group-chat energy only, but the technical tea is exactly preserved. 💖

---

✨ NAME ✨

mkzftree — create a zisofs/RockRidge compressed file tree.

---

🦋 SYNOPSIS 🦋

mkzftree [OPTIONS]... INPUT OUTPUT

---

🌸 DESCRIPTION 🌸

So here’s the vibe: it takes an input file tree (INPUT) and creates a corresponding compressed file tree (OUTPUT) that can be used with an appropriately patched mkisofs(8) to create a transparent-compression ISO 9660/Rock Ridge filesystem using the "ZF" compression records. That’s the whole main-character mission. ✨

---

💅 OPTIONS 💅

• -f, --force — always compress all files, even if they get larger when compressed. yes, even the ones that balloon up. no cap.
• -z level, --level level — select compression level (1-9, default is 9). Lower compression levels are faster, but typically result in larger output. speed vs. size, the eternal group-chat dilemma.
• -u, --uncompress — uncompress an already compressed tree. This can be used to read a compressed filesystem on a system which cannot read them natively. iconic little rescue move.
• -p parallelism, --parallelism parallelism — compress in parallel. The parallelism value indicates how many compression threads are allowed to run. multithreading slay.
• -x, --one-filesystem — do not cross filesystem boundaries, but create directory stubs at mount points.
• -X, --strict-one-filesystem — do not cross filesystem boundaries, and do not create directory stubs at mount points.
• -C path, --crib-path path — steal ("crib") files from another directory if it looks (based on name, size, type and modification time) like they match entries in the new filesystem. The "crib tree" is usually the compressed version of an older version of the same workload; this thus allows for "incremental rebuilds" of a compressed filesystem tree. The files are hardlinked from the crib tree to the output tree, so if it is desirable to keep the link count correct the crib path should be deleted before running mkisofs. The crib tree must be on the same filesystem as the output tree. borrowed-with-purpose energy, but make it hardlinks. 💅
• -l, --local — do not recurse into subdirectories, but create the directories themselves.
• -L, --strict-local — do not recurse into subdirectories, and do not create directories.
• -F, --file — indicates that INPUT may not necessarily be a directory; this allows operation on a single file. Note especially that if -F is specified, and INPUT is a symlink, the symlink itself will be copied rather than whatever it happens to point to. read that again: the symlink itself, bestie.
• -s, --sloppy — treat file modes, times and ownership data as less than precious information and don’t abort if they cannot be set. This may be useful if running mkisofs on an input tree you do not own. lowkey forgiving mode.
• -v, --verbose — increase the program verbosity.
• -V value, --verbosity value — set the program verbosity to value.
• -q, --quiet — issue no messages whatsoever, including error messages. This is the same as specifying -V 0. absolute silence. not a peep. 🤫
• -h, --help — display a brief help message.
• -w, --version — display the release version.

---

💀 BUGS 💀

• Long options (beginning with --) may not work on all systems. See the message printed out by mkzftree -h to see if this applies to your system. iykyk, check your own system tea.
• Inode change times (ctimes) are not copied. This is a system limitation and applies to all file copy programs. not us, it’s the system.
• If using the parallel option (-z) the access times (atimes) on directories may or may not be copied. If it is important that the atimes on directories are copied exactly, avoid using -z. fr fr, if exact directory atimes matter, skip that.

---

👑 AUTHOR 👑

Written by H. Peter Anvin <hpa@zytor.com>. legend behavior. ✨

---

🌈 COPYRIGHT 🌈

Copyright © 2001-2002 H. Peter Anvin.

This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. like, zero warranty. none. periodt.

---

🔥 SEE ALSO 🔥

mkisofs(8)

---

alright bestie, that’s the whole page — source/version is zisofs-tools, dated 30 July 2001, manual MKZFTREE(1). mwah 💋✨🎀