You can attach to a Chirp filesystems by using the FUSE package to attach Chirp as a kernel filesystem module. Unlike parrot(1), this requires superuser privileges to install the FUSE package, but will likely work more reliably on a larger number of programs and environments. Using FUSE allows for transparent access to a Chirp server via the local filesystem. This allows user applications to use a Chirp store unmodified.
Once you have installed and permissions to use FUSE, simply run chirp_fuse with the name of a directory on which the filesystem should be mounted.
For complete details with examples, see the Chirp User's Manual.
|Require this authentication mode.|
|Block size for network I/O. (default is 65536s)|
|Enable debugging for this subsystem.|
|-D, --no-optimize||Disable small file optimizations such as recursive delete.|
|-f, --foreground||Run in foreground for debugging.|
|Comma-delimited list of tickets to use for authentication.|
|Pass mount option to FUSE. Can be specified multiple times.|
|Send debugging output to this file.|
|Timeout for network operations. (default is 60s)|
|-v, --version||Show program version.|
|-h, --help||Give help information.|
% chirp_fuse /tmp/chirp-fuse & % cd /tmp/chirp-fuse % ls % cd host:port % cat foo/bar % exit