• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

CHANGELOGH A D27-Mar-20183.6 KiB6665

COPYINGH A D22-Feb-201824.7 KiB482399

Makefile.amH A D22-Feb-2018327 1311

Makefile.inH A D27-Mar-201829.4 KiB866766

READMEH A D16-Mar-20182.6 KiB5949

aclocal.m4H A D27-Mar-201851.2 KiB1,4291,294

archivecomp.hH A D22-Feb-2018504 149

archivemount.1H A D27-Mar-201810 KiB452404

archivemount.1.inH A D22-Feb-201810 KiB452404

archivemount.cH A D27-Mar-201869 KiB2,9122,374

compileH A D22-Feb-20187.2 KiB348258

config.h.inH A D27-Mar-20181.7 KiB6845

configureH A D27-Mar-2018172.7 KiB5,9504,909

configure.acH A D27-Mar-20181.9 KiB6346

depcompH A D22-Feb-201823 KiB792502

install-shH A D22-Feb-201814.8 KiB509329

missingH A D22-Feb-20186.7 KiB216143

uthash.hH A D22-Feb-201857.3 KiB905715

README

1What is it
2----------
3Archivemount is a piece of glue code between libarchive
4(http://people.freebsd.org/~kientzle/libarchive/) and FUSE
5(http://fuse.sourceforge.net). It can be used to mount a (possibly compressed)
6archive (as in .tar.gz or .tar.bz2) and use it like an ordinary filesystem.
7
8Requirements
9------------
10You will need autoconf, libarchive-dev and libfuse-dev for building
11archivemont, as well as GNU make and gcc of course.
12
13Installation
14------------
15From version 0.6.0 on archivemount uses autoconf, so just do the normal
16
17autoreconf -i
18./configure && make && sudo make install
19
20to build archivemount and install it to /usr/local. For building it,
21libfuse is needed in version 2.6 or higher, including its headerfiles
22of course (on most distributions those can be found in a package named
23something like libfuse-dev or so).
24
25Usage
26-----
27archivemount <options> <archive> <mountpoint>
28Options are the normal fuse mount options, nothing special supported yet.
29
30Write support
31-------------
32Writing to an archive with libarchive is unfortunately not possible. In
33order to provide write support thus the whole archive has to be recreated;
34this requires two things: space and time. To optimize at least the timely
35behaviour, archives are recreated only once: at the time of unmount. If there
36are any problems creating the new archive - bad luck, the changes are lost. Some
37checks are run when mounting the archive to determine if it can be mounted
38writeable, but there is no guarantee.
39Also note that unmounting a fuse filesystem is NOT necessarily completed when
40the unmount command returns. Although unmounting takes a long time already,
41fuse backgrounds the process and lets the unmount command return early. You
42can check on the real state of unmounting by checking the process list for
43archivemount.
44
45THERE IS ALSO NO GUARANTEE THAT DATA IS WRITTEN CORRECTLY. DO NOT TRUST THIS
46SOFTWARE! A backup is made of the original archive (with .orig appended to the
47name), but please understand that I, the author of archivemount, do not
48guarantee anything at all about the state of your data and I am not responsible
49if you lose vital information by using this software. YOU HAVE BEEN WARNED!
50
51Archive formats
52---------------
53A note about archive and compression formats: libarchive supports a lot more
54formats for reading than it does for writing. Archivemount tries to do a
55sensible conversion here when writing the changed archive because I think most
56people do not care a lot about the exact version of tar used inside the .tgz
57file as long as their favourite archive tool can still cope with the file.
58
59