Messages in this thread | | | Date | Tue, 13 May 2003 15:51:50 +0200 | From | Erik Mouw <> | Subject | Re: inode values in file system driver |
| |
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.
Example: mount an NTFS filesystem with -o show_sys_files and do ls on the mountpoint. You won't see the file $MFT, but it is there when you copy it: cp /mountpoint/\$MFT /tmp .
Yes, this is a bug in glibc.
Erik
-- Erik Mouw J.A.K.Mouw@its.tudelft.nl mouw@nl.linux.org [unhandled content-type:application/pgp-signature] | |