From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: [TUHS] Retaining file-modified timestamps
Date: Thu, 4 Apr 2019 08:56:02 -0400 (EDT) [thread overview]
Message-ID: <20190404125602.5D34518C0F4@mercury.lcs.mit.edu> (raw)
So, a while back I mentioned that I'd done tweaked versions of 'cp', 'mv',
'chmod' etc for V6 which retained the original modified date of a file (when
the actual contents were not changed). I had some requests for those versions,
which I have finally got around to checking and uploading (along with 'mvall',
which for some reason V6 didn't have). I've added them to a couple of my V6
pages:
http://www.chiappa.net/~jnc/tech/V6Unix.html#mvall
http://www.chiappa.net/~jnc/tech/ImprovingV6.html#FileWrite
Note (per the page) that the latter group all require the smdate() system
call, which was commented out in 'vanilla' V6 (because using it confused the
backup system); the page gives instructions on how to turn it back on.
Noel
reply other threads:[~2019-04-04 13:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190404125602.5D34518C0F4@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).