Date: Tue, 21 Aug 2001 13:51:47 +0200 (CEST) From: Bernhard Wiedemann To: linux-kernel@vger.kernel.org Subject: translucency lkm in short: I wrote a (beta) linux-kernel-module that does translucency (virtually merging two directories to one) http://www.informatik.hu-berlin.de/~wiedeman/development/translucency.tgz the whole story: three months ago I began building a bootable (stand-alone) linux on CD but found it cumbersome to burn that CD(RW) again for any little change. I also wanted some way to change system-files permanently (e.g store them on disk or nfs) So I started thinking about overlaying/translucency (because I did not want to symlink any potentially writable file) asking google I found kernel mailing list archives at vger and other sites of interest having found several approaches - mostly at filesystem level (ovlfs, ifs) I got no working solution with recent kernels (2.2 or 2.4 series) so I followed a fellow student's advice to do some kernel-programming myself. Weeks of reading sources and examples passed (but I am no expert - so please do not chop my head off for not knowing everything - I will be glad if you help me to improve). I decided for a sys-call-redirecting approach that makes possible anything the user could do and avoids caring too much about permissions but instead introduces severe segment/memory and portability issues. Yet it works on i386 compatible platforms with 2.4.x kernel (about 80% of all features wanted). With some trickery I even got a kernel configured and compiled with this translucency module redirecting any output file to another directory. it is now about 700 lines of code and works stable (but not as secure as could be) It is released under the GPL and I hope that some of you (who read so far) will find it useful, do peer-review, send bugfixes or do something otherwise helpful. please note that I am not subscribed to the mailing list so please cc your answer to my email address yours sincerely Bernhard M. Wiedemann