Re: inode values in file system driver

[Erik Mouw]

This is a MIME-formatted message.  If you see this text it means that your
E-mail software does not support MIME-formatted messages.

--=_courier-14592-1052834214-0001-2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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=20
> to be having problems with a file that is being assigned this inode value=
=20
> (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

--=20
Erik Mouw
[e-mail]  [e-mail]

--=_courier-14592-1052834214-0001-2
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+wPh2/PlVHJtIto0RAvGvAJ90nQlorRfZcXTO2Ln0YWuAbwvnzACfdEG1
2qsGueiHmtzMaUkwqb54LK8=
=Ajht
-----END PGP SIGNATURE-----

--=_courier-14592-1052834214-0001-2--