ezk:
> rusty:
> > willy:
> > > What I'd like to do would be to stack a notification layer on top of
> > > a directory, which would actually just entail replacing its ->i_op
> > > with a shim which notified and then passed the call on.
...
> > If modules could easily replace ->i_op (preferably without stomping each
> > other), you could load modules which did whatever they wanted in response
> > to various operations on specific inodes
...
> What you're describing is called stackable file systems, which I've created
> under Linux. I have an encryption f/s, compression f/s, and several other
> samples---all built on top of "generic" stacking templates. See
>
> http://www.cs.columbia.edu/~ezk/research/fist/
Is there a way to wrap operations on a single file or directory without
affecting operations on other files in or below that directory? If I
understand correctly, you'd have to overlay mount your wrapfs-fs on the
file's directory, and on every subsequent operation on files under that
mount point, determine whether or not the operation was on the inode(s)
you were interested in. That's an improvement over the way imon works
now, and I will try it out, but I'd prefer it to work as willy described.
--Rusty
--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx
|