Points to fs architecture

[surfing t]

Hello,

I want to create a utility that "hooks" into the the filesystem. What I want to do is to be able to review
all file system read/write/seek requests, most of the time without affecting file system operation (ie after
review the request is passed on to the entity that would have received it had my utility not been installed, however
some of the requests my driver should handle itself. My problem is that while I have first-hand experience on kernel
programming I have never done anything on a UNIX og Linux kernel and I only know its structure from a user-level
perspective. Where can I find documentation on how to code drivers for the Linux kernel and about how the entire
file system works (by "file system" I don't refer to ext3 or reiserfs or anything like that - I mean the architecture that allows all these things to co-exist). I want my driver to be at a level above things like ext3/reiserfs if possible. Basically I just want to "hijack" the system calls that applications use to access files and then pass them on to the original system call. Is this possible and how do I do it? Any help will be greatly appreciated and the utility I have in mind will benefit the entire community (I will GPL it of course) and I believe it could so some extent make Linux more popular. I am a bit secretive right now because I really want to implement this idea myself. I will give credit to those who responds to this message.

Thank you in advance!
-- 
_______________________________________________
Find what you are looking for with the Lycos Yellow Pages
http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/