File level action protocol
File level action protocol
- Subject: File level action protocol
- From: Thomas Tempelmann <email@hidden>
- Date: Tue, 5 Jul 2005 22:17:23 +0200
Since there seem to be a few people here knowing enough about file
systems and BSD, I like to ask this rather general question:
Consider I'd want to write a service that logs the time and path (or node
ID) of any file that got written.
Does Tiger now provide some API that I can use from outside the kernel or
would I still have to write a kext that hooks into the file system stack?
I have experience writing file system level software, though (been
writing DirectCD/Mac and a Joliet File System as well, both for Mac OS
9), just don't know much about the BSD stuff yet.
I don't have plans to work on this right now but would rather know if
this is feasible at all in Tiger, and how difficult it would be.
For said logging service, I'd have to have some way to store the
information, i.e. eventually writing it to a file. If I'd have to write a
kext - would I then be able to call the file systems below me to write to
a file? If not, do I have at least virtual, dynamic, memory (i.e. a
memory mapped file) so that I can at least save the data to "RAM" until a
non-kernel service can pull the data out and save it "properly"?
Thomas
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden