Zisofs
From Just Solve the File Format Problem
(Difference between revisions)
m |
|||
| Line 10: | Line 10: | ||
For the apparent predecessor of zisofs, see [[Isofs transparent compression]]. | For the apparent predecessor of zisofs, see [[Isofs transparent compression]]. | ||
| + | |||
| + | == Identification == | ||
| + | Use of zisofs requires that [[System Use Sharing Protocol|SUSP]] and [[Rock Ridge]] be enabled (see [[System Use Sharing Protocol#Identification]]). Determining whether a volume actually uses zisofs would require scanning every directory. | ||
| + | |||
| + | zisofs-compressed files use a special format, with signature bytes {{magic|37 e4 53 96 c9 db d6 07}}. Files in this format could be visible if zisofs is not supported, or as part of some workflows for creating a zisofs volume. | ||
== Software == | == Software == | ||
| + | * [https://www.libarchive.org/ libarchive / bsdtar] | ||
| + | * Supported by [https://www.kernel.org/ Linux] filesystem drivers | ||
* [http://freshmeat.sourceforge.net/projects/zisofs-tools/ zisofs-tools] | * [http://freshmeat.sourceforge.net/projects/zisofs-tools/ zisofs-tools] | ||
Latest revision as of 14:24, 9 March 2019
zisofs is an extension of ISO 9660 format, which adds support for per-file compression.
It is designed as an extension of Rock Ridge. It specifies a new entry, with signature "ZF".
For the apparent predecessor of zisofs, see Isofs transparent compression.
[edit] Identification
Use of zisofs requires that SUSP and Rock Ridge be enabled (see System Use Sharing Protocol#Identification). Determining whether a volume actually uses zisofs would require scanning every directory.
zisofs-compressed files use a special format, with signature bytes 37 e4 53 96 c9 db d6 07. Files in this format could be visible if zisofs is not supported, or as part of some workflows for creating a zisofs volume.
[edit] Software
- libarchive / bsdtar
- Supported by Linux filesystem drivers
- zisofs-tools
