On 2020-07-24 at 09:50, tomas@tuxteam.de wrote: > > On Fri, Jul 24, 2020 at 09:42:24AM -0400, The Wanderer wrote: > >> On 2020-07-24 at 09:22, tomas@tuxteam.de wrote: >>> Nitpick: the directory entry is the one carrying the name. >> >> I had the impression that even a directory is stored in/as >> something that is at least analogous to an inode. Is there a >> different term that's more appropriate for the on-disk structure >> which holds a directory, vs. 'inode' for the one that holds a >> file? > > That's right: the directory is at the same time a file, and thus, > represented by the inode. But the name itself is in the content of > the directory, whithin the directory entry. Since writing that, I've had occasion to remember the term 'dirent', which I think is more the in-memory representation of a directory than the on-disk representation, but might be borrow-able for the purpose. >> It does seem to suggest that, but when I run >> >> $ /sbin/e2fsck /tmp/testfs >> >> on the tiny filesystem created as in my previous mail, it doesn't >> report finding any problems and seem to change anything. > > Hm. You gave it the -f option? Otherwise, if the file system is > marked "clean", e2fsck might choose the lazy option :-) Indeed I hadn't, and you're right, with that I get lengthier output and the file's timestamp does get updated (which previously it hadn't). However, when I examine the file with vbindiff afterwards, the slash is still there. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
Attachment:
signature.asc
Description: OpenPGP digital signature