--On 08 May 2000, 18:37 +0300 BenHanokh Gabriel <gabriel@SANgate.com> wrote:
> my module is extension to the ext2fs to allow alloaction of blocks for
> files without writting all those zeros to them.
Ah. How do you make sure the newly allocated blocks cannot ever
be read by an application until after they have been written to, then?
What do you need this facility for - some sort of kernel-level facility,
or an application?
> so yes i'm very dependet on the ext2 to work, but still i don;t succed
> calling its functions
Does it have to be ext2fs only, though?
> i do succed to call the vfs functions so it should be something with the
Personally, I'd add the raw functions necessary to ext2fs, then export it
via VFS, rather than hitting ext2fs directly. There are already several
replacements for ext2fs approaching inclusion in the kernel; if your
code is hardwired into the ext2fs code, you will have a lot of problems
later on, when you try to move to XFS, ReiserFS, ext3fs or whatever.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:11 EST