user/drivers/fs_modules.dox

44 	  operation vector (\c fs_vnode_ops).
137 	the nodes's \link fs_vnode_ops::put_vnode put_vnode() \endlink
139 	\link fs_vnode_ops::remove_vnode remove_vnode() \endlink.
146 	\link fs_vnode_ops::lookup lookup() \endlink
151 	\link fs_vnode_ops::read_dir read_dir() \endlink and
162 	module, \c fs_volume_ops, and \c fs_vnode_ops structure). Some hooks are
169 	- \link fs_vnode_ops::lookup lookup() \endlink:
174 	  \link fs_vnode_ops::put_vnode put_vnode() \endlink:
178 	- \link fs_vnode_ops::read_stat read_stat() \endlink:
183 	- \link fs_vnode_ops::open open() \endlink,
184 	  \link fs_vnode_ops::close close() \endlink, and
185 	  \link fs_vnode_ops::free_cookie free_cookie() \endlink:
188 	- \link fs_vnode_ops::read read() \endlink:
193 	- \link fs_vnode_ops::open_dir open_dir() \endlink,
194 	  \link fs_vnode_ops::close_dir close_dir() \endlink, and
195 	  \link fs_vnode_ops::free_dir_cookie free_dir_cookie() \endlink:
199 	- \link fs_vnode_ops::read_dir read_dir() \endlink and
200 	  \link fs_vnode_ops::rewind_dir rewind_dir() \endlink:
212 	- \link fs_vnode_ops::read_symlink read_symlink() \endlink:
217 	- \link fs_vnode_ops::access access() \endlink:
225 	While there is the \link fs_vnode_ops::access access() \endlink hook
237 	  E.g. in fs_vnode_ops::read() or fs_vnode_ops::write() one only has to
241 	- The core of the fs_vnode_ops::access() hook can be moved into a private
302 	  a file cache for any of its files. The fs_vnode_ops::read() and
303 	  fs_vnode_ops::write() hooks can then simply be implemented by calling the
307 	  the fs_vnode_ops::io() hook.
312 	  the VFS will call the fs_vnode_ops::lookup() hook for each element of the
322 	  calls to fs_vnode_ops::lookup() for the missing entry will then be