The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] Origin of the MOTD file?
Date: Thu, 15 Mar 2018 11:51:59 -0400	[thread overview]
Message-ID: <CAC20D2MSuHUt_1c8ne-3L7_2=jaTSs856bvVRk3o+uyDz+aj4Q@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W49jx_hrNd11meGGJi00cZ+FDs9BtB_W7b2c=drujzNSA@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]

On Thu, Mar 15, 2018 at 11:29 AM, Dan Cross <crossd at gmail.com> wrote:

> One of the things that's always fascinated me about Unix is the community
> aspect; in particular, I imagine that in the early days when machines were
> multiplexed among many simultaneous users, I wonder whether there was a
> greater sense of knowing what others were up to, working on, or generally
> doing.
>
> I think of the /etc/motd file as being a part of this. It is, in some very
> real sense, a way to announce things to the entire user community.
>
> So what are its origins? Where did it first appear? I haven't dug into
> this, but I imagine it was at Berkeley. What was it used for early on at
> individual sites?
>

​I'm pretty sure it predates the #1 editions, if check the sources for the
login program on TUHS you can be sure. Steve Johnson and others have
pointed out that systems people (such as Dennis) were often night owls and
often added/changed things​ in the UNIX group or their own systems.   This
was no different than the way other systems (such as timesharing system
like TOPS or TSS worked).   System time in the day was expensive and if you
wanted to make a change the affected a lot of people, you did it 'off
hours.'

Remember, most people in those days were 'dialing in' or going to a
terminal room.   So you got a fresh log in session once or twice a day.
 So, I believe that the idea of motd was to have a standard place where
everyone could get messages that might affect them and be pretty sure you
saw it before you started your work.

For instance, two messages I can think of I put the EE/Mellon systems years
ago were on the order of:  *'New Pascal compiler installed, should fix the
core dump issue Tron was having - send me email if you are still having
issues.   Clem'*    Or  *'Klone and I just updated our RK07 disk driver to
add bad disk block support -- we think its working as far as we have been
able to test.   If you notice something strange, please check the console
log before you call either us..  Clem'*

You get the idea,
Clem

ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180315/eb168da5/attachment-0001.html>


  parent reply	other threads:[~2018-03-15 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-15 15:29 Dan Cross
2018-03-15 15:35 ` Ron Natalie
2018-03-15 15:36   ` Chet Ramey
2018-03-15 15:41     ` Ron Natalie
2018-03-15 20:20     ` Dave Horsfall
2018-03-15 20:25       ` Warner Losh
2018-03-15 15:51 ` Clem Cole [this message]
2018-03-15 15:53   ` Clem Cole
2018-03-15 16:55   ` Ron Natalie
2018-03-15 18:04 ` Jeremy C. Reed
2018-03-15 20:00 Doug McIlroy
2018-03-15 20:51 ` Dave Horsfall

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='CAC20D2MSuHUt_1c8ne-3L7_2=jaTSs856bvVRk3o+uyDz+aj4Q@mail.gmail.com' \
    --to=clemc@ccc.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).