Re: Intercepting file system calls (read, write, open, close, etc)
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Nov 17, 2004, at 11:26 AM, darwin-dev-request@lists.apple.com wrote: Andrew Downs <andrew@downs.ws> wrote: On Nov 16, 2004, at 2:05 PM, Al Ameen Shah wrote: 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. 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. = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... 1. Try VFS Stacking ? Or over-riding V-node ops ? You don't want a stacking VFS module to intercept FS calls at the application level; it should be done in userland. If you want to catch Carbon at it, you need to sit on top of getattrlist, setattrlist and getdirentriesattr as well. This email sent to site_archiver@lists.apple.com
participants (1)
-
Mike Smith