this file lists +pros and -cons for the translucency linux kernel module

+works for recent linux kernel v2.4 (2.4.3-2.4.22 tested)
-compatibility for v2.2 has been lost (see old/transhack4.c for thus)

+transparent to user-space-processes
+no recompiling of statically linked binaries etc
+transparent to the kernel - thus all fs and medii should work
-has to be recompiled for every kernel and for every update
?-only for i386+alpha yet (segmentation issues) ?is this still true? Who tried?
-harder to debug
-can crash the machine
-needs more security-checks

+management and info per /proc/sys/translucency/*
+allows as many redirections and as many overlay-layers as you want
+creates dirs and devices when needed
+copies files on the fly
-sometimes too many ("touch file" must copy it)
-wastes some space since it is no versioning system
+does not try to copy devices/fifos/sockets or /proc/something
-symlinks are followed, but not yet redirected properly
?+avoids directory loops (implicitly) ?

+merges directory listings
+does not need special index or container files
+thus fast
-may break POSIX compliance
-can sometimes put files in wrong dir when upper layer is_subdir of lower layer or other way round (bug)