The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross via TUHS <tuhs@tuhs.org>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] History of cal(1)?
Date: Thu, 18 Sep 2025 12:53:24 -0400	[thread overview]
Message-ID: <CAEoi9W6TMiCLLJ_DQq_rD2UJJjmL-KSQZQDm0qDy+yKWcik9XA@mail.gmail.com> (raw)

Over on the Multicians list, Jeffrey Johnson asked a question about
the Multics `calendar` program, which was written by Tom van Vleck in
Dec, 1973. Despite what some man pages say, the analogous Unix `cal`
program appears to have arrived in the 5th Edition (mid 1974).
Jeffrey's question was whether `cal` was inspired by `calendar`?

My suspicion is that it was not, and this is a case of parallel
invention: after all, a program that prints out a calendar is
obviously useful.  I also suspect that program, or something
substantially similar, had existed for quite a while before someone
tossed it into /usr/source/s1 in time for 5th Edition.  Does anyone
recall who wrote it, and when?

But this also rekindles my curiosity about something I've always
wondered: what _was_ the level of communication between the folks at
Bell Labs and the Multics people after 1969?  By all accounts,
individuals remained friendly and collegial with one another, but it
seems like communication (let alone collaboration) between the two
"camps" was minimal.  Is that accurate?

        - Dan C.

             reply	other threads:[~2025-09-18 16:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 16:53 Dan Cross via TUHS [this message]
2025-09-18 17:36 ` [TUHS] " Cameron Míċeál Tyre via TUHS
2025-09-18 18:31   ` Dan Cross via TUHS
2025-09-18 19:51 ` Clem Cole via TUHS
2025-09-19 19:57   ` Dan Cross via TUHS
2025-09-19 20:30     ` [TUHS] SOSP 1973 [was Multics<->Unix " Charles H Sauer (he/him) via TUHS
2025-09-20 20:35 ` [TUHS] " John Levine via TUHS
2025-09-22 14:51   ` Dan Cross via TUHS
2025-09-22 15:05     ` Jeff Johnson via TUHS
2025-09-22 18:18 [TUHS] " Douglas McIlroy via TUHS

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=CAEoi9W6TMiCLLJ_DQq_rD2UJJjmL-KSQZQDm0qDy+yKWcik9XA@mail.gmail.com \
    --to=tuhs@tuhs.org \
    --cc=crossd@gmail.com \
    /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).