| 1 |
What is it |
| 2 |
---------- |
| 3 |
Archivemount is a piece of glue code between libarchive <http://libarchive.org/> |
| 4 |
and FUSE <http://fuse.sourceforge.net>. It can be used to mount a (possibly compressed) |
| 5 |
archive (as in .tar.gz or .zip or .iso) and use it like an ordinary filesystem. |
| 6 |
|
| 7 |
Requirements |
| 8 |
------------ |
| 9 |
You will need GNU Make, libarchive-dev, libfuse3-dev/libfuse-dev, and pkgconf |
| 10 |
(or just the libraries and fix up c++ *.cpp manually). |
| 11 |
|
| 12 |
-ng |
| 13 |
------------ |
| 14 |
https://git.sr.ht/~nabijaczleweli/archivemount-ng |
| 15 |
https://todo.sr.ht/~nabijaczleweli/archivemount-ng (report at <mailto:~nabijaczleweli/[email protected]>) |
| 16 |
https://lists.sr.ht/~nabijaczleweli/archivemount-ng <mailto:~nabijaczleweli/[email protected]> |
| 17 |
https://builds.sr.ht/~nabijaczleweli/archivemount-ng |
| 18 |
|
| 19 |
The upstream author died irl in 2020 (cf. obituary in https://github.com/cybernoid/archivemount/issues/29). |
| 20 |
This encompasses the upstream tarballs and, at least, fixes the following issues. |
| 21 |
|
| 22 |
Debian bugs: |
| 23 |
[0.8.9] #799563: Failed to list correctly the files when parent directory name and child directory names are the same |
| 24 |
[lllll] #687710: cannot read ISO-9660 archives |
| 25 |
[xxxxx] #832823: new upstream version (0.8.7) |
| 26 |
[ 1 ] #838597: Unmount instructions in man page lead to "Permission denied" error. |
| 27 |
[xxxxx] #891749: New upstream version (0.8.9) |
| 28 |
[xxxxx] #974679: Wrong homepage + new version |
| 29 |
[0.8.4] #651442: does not handle compressed (single) files |
| 30 |
[?????] #857985: appears a kernel upgrade changed the ABI unexpectedly |
| 31 |
[lllll] #674231: Add 7zip support |
| 32 |
[ 1 ] #1073228: uthash is BSD-1-Clause, not BSD-2-Clause |
| 33 |
|
| 34 |
Upstream (https://github.com/cybernoid/archivemount) bugs: |
| 35 |
[0.8.9] #28: Chokes on CSRG ISO |
| 36 |
[ 1 ] #21: Quadratic complexity when reading large entries |
| 37 |
[ 1 ] #27: fuse.pc is fuse3.pc nowadays |
| 38 |
[xxxxx] #26: feature request: zstd support |
| 39 |
[xxxxx] #25: archivemount can't read .img.gz |
| 40 |
[lllll] #23: feature request: .xz compressed files support? |
| 41 |
[ ] #14: Create a table which shows supported formats && read / write support |
| 42 |
[ 1-1 ] #17: Update homepage in apt show archivemount |
| 43 |
PRs: |
| 44 |
[ 1 ] #22: Add support for fuse3 |
| 45 |
[ 1 ] #20: Add support for /dev/fd/%u mountpoints |
| 46 |
[ 1 ] #19: Don't fchdir at unmount when mounting read-only |
| 47 |
[ 1 ] #18: Honor raw archives' pathname |
| 48 |
|
| 49 |
x – fundamentally invalid; l – libarchive bug; ? – incoherent |
| 50 |
|
| 51 |
Write support |
| 52 |
------------- |
| 53 |
Writing to an archive with libarchive is unfortunately not possible. In |
| 54 |
order to provide write support thus the whole archive has to be recreated; |
| 55 |
this requires two things: space and time. To optimize at least the timely |
| 56 |
behaviour, archives are recreated only once: at the time of unmount. If there |
| 57 |
are any problems creating the new archive - bad luck, the changes are lost. Some |
| 58 |
checks are run when mounting the archive to determine if it can be mounted |
| 59 |
writeable, but there is no guarantee. |
| 60 |
Also note that unmounting a fuse filesystem is NOT necessarily completed when |
| 61 |
the unmount command returns. Although unmounting takes a long time already, |
| 62 |
fuse backgrounds the process and lets the unmount command return early. You |
| 63 |
can check on the real state of unmounting by checking the process list for |
| 64 |
archivemount. |
| 65 |
|
| 66 |
THERE IS ALSO NO GUARANTEE THAT DATA IS WRITTEN CORRECTLY. DO NOT TRUST THIS |
| 67 |
SOFTWARE! A backup is made of the original archive (with .orig appended to the |
| 68 |
name), but please understand that I, the author of archivemount, do not |
| 69 |
guarantee anything at all about the state of your data and I am not responsible |
| 70 |
if you lose vital information by using this software. YOU HAVE BEEN WARNED! |
| 71 |
|
| 72 |
Archive formats |
| 73 |
--------------- |
| 74 |
A note about archive and compression formats: libarchive supports a lot more |
| 75 |
formats for reading than it does for writing. Archivemount tries to do a |
| 76 |
sensible conversion here when writing the changed archive because I think most |
| 77 |
people do not care a lot about the exact version of tar used inside the .tgz |
| 78 |
file as long as their favourite archive tool can still cope with the file. |
| 79 |
|
| 80 |
Release signing |
| 81 |
--------------- |
| 82 |
Release tarballs are signed with [email protected] |
| 83 |
(pull with WKD, but 7D69 474E 8402 8C5C C0C4 4163 BCFD 0B01 8D26 58F1). |
| 84 |
аnd stored in git notes as-if via the example program provided at |
| 85 |
https://man.sr.ht/git.sr.ht/#signing-tags-tarballs |
| 86 |
and are thus available on the refs listing/tag page as .tar.gz.asc. |