Hello, I want to write a fs, that caches the content of another fs to disc, so the final fs should work with two discs. The drive, that contains the cached data is considered private to my fs, so I like to mount/unmount it. The other drive, that should be cached is considered a user disk, so it will be mounted from outside the module stuff.
I already have a working environment as well as a running skeleton, but I don't understand the workflow yet, so I don't know, which part I should modify to get my dreams to reality. As the caching should be transparent/invisible to client-apps, I thought, writing a new fs would be right. But from inside a module, I don't have any knowledge about the whole path, so I don't know, when and how to change it. - Who breaks the path from open() into single directory-lookups? - If I have the inode of a directory from one drive, how can I find the inode with the same path (relative to the mountpoint) on another drive (from inside a module - of cause)? I read anything, I could find about filesystems, but I think, things are a bit complicated, to get into it - alone. So any help is appreciated. kind regards Santiago -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [EMAIL PROTECTED] Please read the FAQ at http://kernelnewbies.org/FAQ
