1 |
Fuse version 0.05 |
2 |
================= |
3 |
|
4 |
This is a test release. It seems to work quite well. In fact, I can't |
5 |
find any problems with it whatsoever. If you do, I want to know. |
6 |
|
7 |
|
8 |
INSTALLATION |
9 |
|
10 |
To install this module type the standard commands as root: |
11 |
|
12 |
perl Makefile.PL |
13 |
make |
14 |
make test |
15 |
make install |
16 |
|
17 |
|
18 |
DEPENDENCIES |
19 |
|
20 |
This module requires the FUSE userspace library and the FUSE kernel module. |
21 |
See http://fuse.sourceforge.net/ |
22 |
|
23 |
|
24 |
COPYRIGHT AND LICENCE |
25 |
|
26 |
This is contributed to the FUSE project by Mark Glines <mark@glines.org>, |
27 |
and is therefore subject to the same license and copyright as FUSE itself. |
28 |
Please see the AUTHORS and COPYING files from the FUSE distribution for |
29 |
more information. |
30 |
|
31 |
|
32 |
EXAMPLES |
33 |
|
34 |
There are a few example scripts. You can find them in the examples/ |
35 |
subdirectory. These are: |
36 |
|
37 |
* example.pl, a simple "Hello world" type of script |
38 |
|
39 |
* loopback.pl, a filesystem loopback-device. like fusexmp from |
40 |
the main FUSE dist, it simply recurses file operations |
41 |
into the real filesystem. Unlike fusexmp, it only |
42 |
re-shares files under the /tmp/test directory. |
43 |
|
44 |
* rmount.pl, an NFS-workalike which tunnels through SSH. It requires |
45 |
an account on some ssh server (obviously), with public-key |
46 |
authentication enabled. (if you have to type in a password, |
47 |
you don't have this. man ssh_keygen.). Copy rmount_remote.pl |
48 |
to your home directory on the remote machine, and create a |
49 |
subdir somewhere, and then run it like: |
50 |
./rmount.pl host /remote/dir /local/dir |
51 |
|
52 |
* rmount_remote.pl, a ripoff of loopback.pl meant to be used as a backend |
53 |
for rmount.pl. |
54 |
|
55 |
|
56 |
BUGS |
57 |
|
58 |
I've begun to build a formal testing framework. Currently it can mount |
59 |
and unmount loopback.pl, and all of the base-level functions have test |
60 |
scripts. These need to be fleshed out as problems are noticed. |
61 |
|
62 |
The current test framework seems to work well, but the underlying mount/ |
63 |
unmount infrastructure is a crock. I am not pleased with that code. |
64 |
|
65 |
While most things work, I do still have a TODO list: |
66 |
* "du -sb" reports a couple orders of magnitude too large a size. |
67 |
* need to sort out cleaner mount semantics for the test framework |
68 |
* figure out how to un-linuxcentrify the statfs tests |
69 |
* test everything on other architectures and OS's |
70 |
|