Messages in this thread | | | From | Nikita Danilov <> | Date | Tue, 13 May 2003 18:47:42 +0400 | Subject | Re: inode values in file system driver |
| |
Andreas Schwab writes: > Erik Mouw <J.A.K.Mouw@its.tudelft.nl> writes: > > |> On Sat, May 10, 2003 at 09:18:20PM +0100, Adrian McMenamin wrote: > |> > Am I allowed to assign the value 0 to an inode in a file system driver? I seem > |> > to be having problems with a file that is being assigned this inode value > |> > (its a FAT based filesystem so the inode values are totally artificial). > |> > |> Yes, you are. However, glibc thinks that inode 0 is special and won't > |> show it. > > BS. This has nothing at all to do with glibc.
from glibc-2.2.4/sysdeps/unix/readdir.c:
/* Skip deleted files. */ } while (dp->d_ino == 0);
In other words, readdir(3) will not return dirent for inode with ino 0.
> > Andreas. >
Nikita. - 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/
| |