From: "surfing t" <surf17@lycos.com>
To: linux-kernel@vger.kernel.org
Subject: Points to fs architecture
Date: Mon, 05 Jul 2004 16:38:58 -0500 [thread overview]
Message-ID: <20040705213858.2002086AE1@ws7-1.us4.outblaze.com> (raw)
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
next reply other threads:[~2004-07-05 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 21:38 surfing t [this message]
2004-07-05 22:53 ` Chris Wedgwood
2004-07-06 12:56 ` Horst von Brand
2004-07-06 18:34 ` Matthew Dharm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040705213858.2002086AE1@ws7-1.us4.outblaze.com \
--to=surf17@lycos.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®