Messages in this thread | | | From | Adrian McMenamin <> | Subject | Re: inode values in file system driver | Date | Wed, 14 May 2003 19:31:02 +0100 |
| |
On Tuesday 13 May 2003 15:56, Andreas Schwab wrote: > Nikita Danilov <Nikita@Namesys.COM> writes:
> |> In other words, readdir(3) will not return dirent for inode with ino 0. > > I stand corrected. I was thinking of getdirentries, which does not have > this problem. But this is traditional Unix behaviour. >
OK. I've worked round this in my driver. It will now list the file, and does so with inode 0 (I have not tinkered with anything outside my driver, so this won't have any impact on any other fs). Is this A Bad Thing?
Adrian
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |