Re: Intercepting file system calls (read, write, open, close, etc)
Re: Intercepting file system calls (read, write, open, close, etc)
- Subject: Re: Intercepting file system calls (read, write, open, close, etc)
- From: Mike Smith <email@hidden>
- Date: Wed, 17 Nov 2004 11:46:59 -0800
On Nov 17, 2004, at 11:26 AM, email@hidden wrote:
Andrew Downs <email@hidden> wrote:
On Nov 16, 2004, at 2:05 PM, Al Ameen Shah wrote:
1. Try VFS Stacking ? Or over-riding V-node ops ?
Was support for VFS stacking removed? I was warned of such a year or
two ago, and stopped my VFS efforts at that point (also trying to
intercept file system calls).
Stacking filesystems in the BSD model doesn't work very well. It gets
expensive very quickly, and locking can become a nightmare. It's also
often not really what you want; the above is a good example of that.
You don't want a stacking VFS module to intercept FS calls at the
application
level; it should be done in userland.
One problem was my module did not get
triggered when the user manipulated files in the Finder, which I wanted
to capture. But the BSD side worked okay.
If you want to catch Carbon at it, you need to sit on top of
getattrlist,
setattrlist and getdirentriesattr as well.
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden