* mtime(1) vs deeply nested directories
@ 2019-12-10 1:54 sl
0 siblings, 0 replies; only message in thread
From: sl @ 2019-12-10 1:54 UTC (permalink / raw)
To: 9front
help:
file system is hjfs.
; date -m `{mtime 2019 | awk '{print $1}'}
Tue, 03 Dec 2019 21:55:01 -0500
; date -m `{mtime 2019/12 | awk '{print $1}'}
Thu, 05 Dec 2019 23:57:30 -0500
; date -m `{mtime 2019/12/03 | awk '{print $1}'}
Tue, 03 Dec 2019 21:55:01 -0500
; date -m `{mtime 2019/12/05 | awk '{print $1}'}
Thu, 05 Dec 2019 23:57:30 -0500
why does mtime(1) run against the top-level 2019/ directory show it
was modified at exactly the same time as 2019/12/03/, while 2019/12/
shows it was modified at exactly the same time as 2019/12/05/?
shouldn't 2019/ show it was modified at the same time as 2019/12/05/
(this was the last directory modified under 2019/)?
both directories 2019/ and 2019/12/ already existed before 2019/03/
and 2019/05/ were created.
sl
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-10 1:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-10 1:54 mtime(1) vs deeply nested directories sl
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).