From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: surfing t <surf17@lycos.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Points to fs architecture
Date: Tue, 6 Jul 2004 11:34:45 -0700 [thread overview]
Message-ID: <20040706183445.GA28783@one-eyed-alien.net> (raw)
In-Reply-To: <20040705213858.2002086AE1@ws7-1.us4.outblaze.com>
[-- Attachment #1: Type: text/plain, Size: 2401 bytes --]
This sounds like a job for dazuko (www.dazuko.org) -- I know that utilities
like ClamAV use that to accomplish some very similar things to what you're
describing.
Matt
On Mon, Jul 05, 2004 at 04:38:58PM -0500, surfing t wrote:
> 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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
NYET! The evil stops here!
-- Pitr
User Friendly, 6/22/1998
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-07-06 18:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 21:38 surfing t
2004-07-05 22:53 ` Chris Wedgwood
2004-07-06 12:56 ` Horst von Brand
2004-07-06 18:34 ` Matthew Dharm [this message]
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=20040706183445.GA28783@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=linux-kernel@vger.kernel.org \
--cc=surf17@lycos.com \
/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®