Hi,
I'm trying to get started with my idea of recursive mtimes, which where
discussed a few days ago, but I'm stuck a little. Maybe someone with some
more knowlege about reiser4 could give me some hints?
The idea was to register each file for change monitoring and reset a special
mtime-attribu
Fred Schaettgen wrote:
Hi,
I'm trying to get started with my idea of recursive mtimes, which where
discussed a few days ago, but I'm stuck a little. Maybe someone with some
more knowlege about reiser4 could give me some hints?
The idea was to register each file for change monitoring and reset a
On Tuesday 11 January 2005 15:41, Edward Shishkin wrote:
> Fred Schaettgen wrote:
> >I'm trying to get started with my idea of recursive mtimes, which where
> >discussed a few days ago, but I'm stuck a little. Maybe someone with some
> >more knowlege about reiser4 could give me some hints?
> >
> >T
Fred Schaettgen wrote:
On Tuesday 11 January 2005 15:41, Edward Shishkin wrote:
Fred Schaettgen wrote:
I'm trying to get started with my idea of recursive mtimes, which where
discussed a few days ago, but I'm stuck a little. Maybe someone with some
more knowlege about reiser4 could give me
On Thursday 13 January 2005 14:15, you wrote:
> Fred Schaettgen wrote:
...
..
> >>There is a union (file_plugin_data) in struct reiser4_inode to keep
> >>features specific
> >>for file plugins.
> >
> >I can't use that union, since my plugin would call the methods of the
> > original file plugin of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fred Schaettgen wrote:
| On Thursday 13 January 2005 14:15, you wrote:
|
|>Fred Schaettgen wrote:
|
| ...
| ..
|
|>>>There is a union (file_plugin_data) in struct reiser4_inode to keep
|>>>features specif
Fred Schaettgen wrote:
On Thursday 13 January 2005 14:15, you wrote:
Fred Schaettgen wrote:
...
..
There is a union (file_plugin_data) in struct reiser4_inode to keep
features specific
for file plugins.
I can't use that union, since my plugin would call the methods of the
origin
