The problem is your familiarity with the subject. And, you are not alone in that. I see it as a normal progression of the mind in individuals who have spent so much time and effort being involved with something, they simply forget how to view the "product" through the eyes of a "newbie".rene wrote: ↑Sun Jan 13, 2019 3:19 pmI shall admit to having some trouble fathoming what exactly could not be immediately clear from the phrasing "creation (or birth) time". And that such is not a complaint either. Fascinating; my mind no doubt out of sheer familiarity seems to disallow me to connect synapses in any order in which such is not obvious.
"Creation (or birth) time"... For you to understand that phrase is a simple as getting up out of your chair, because you are familiar with LInux/Unix terms. Me? I'm not familiar with LInux/Unix phrases, so I don't know exactly what it means. And, it's normal.
I have an online friend in Scotland I regularly email with. Now, we both speak English. But I can't begin to tell you how many times I have to go to the web to figure out what he's trying to tell me. And this is no different.
"'Enlisted' in the filesystem is another phrase I've never heard in my life! But, I think we've got it... When I'm finished with a document, and save it to the HD when I close the document, the birth time is when I saved the document to the HD.rene wrote: ↑Sun Jan 13, 2019 3:19 pmIf at time N but not any earlier time a given file exist on a given file system, N is the creation time of said file on said file system. The moment of a file's non-existence morphing into existence. The (time of the) poof of creation. The time the file was "enlisted" in the filesystem for the first time. The old mtime would be a modification time, a time a file's content was modified, and as such more the "time a file is written to" [ ... ] as you put it.