[TUHS] Origin of the MOTD file?

[TUHS] Origin of the MOTD file?

[Dan Cross]

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?

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180315/d9912e94/attachment.html>

[TUHS] Origin of the MOTD file?

[Ron Natalie]

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

 

Ø  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?

 

It was certainly present in Version 6 UNIX, so it predates Berkeley.    While it being a “file” is very UNIX-ish, the concept of a settable sign on message doesn’t originate with UNIX.    I had used other systems that ran a user defined program on user login (sort of a compiled .profile) and it was common to put the system “news” in such.

 

One amusing thing to do with /etc/motd is to add the like “You might have mail.”    I thought it was a cute joke, but I never realized how much confusion it would cause.     I did it at BRL and had people sending me email asking why they didn’t have mail (it only said you MIGHT).


I told one of my student programmers working for me at Rutgers that if he put that in the motd on one of our systems I guaranteed within an hour someone will tell us they didn’t have mail.
It took about 15 minutes for one of my SENIOR systems programmers to come into the office and tell me that.

 

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

[TUHS] Origin of the MOTD file?

[Chet Ramey]

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

On 3/15/18 11:35 AM, Ron Natalie wrote:

> One amusing thing to do with /etc/motd is to add the like “You might have
> mail.”    I thought it was a cute joke, but I never realized how much
> confusion it would cause.     I did it at BRL and had people sending me
> email asking why they didn’t have mail (it only said you MIGHT).

Try adding "Segmentation Fault (core dumped)".


-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet at case.edu    http://tiswww.cwru.edu/~chet/

[TUHS] Origin of the MOTD file?

[Ron Natalie]

> Try adding "Segmentation Fault (core dumped)".

About the time  computers went from being a tool of the research geeks to operational use at BRL (we went from senior management saying "don't send us email, we don't read it" to management telling everybody "they must check their email regularly for important messages from them:"), the security officers found out about /etc/motd.    They would periodically put the same kind of "security rah rah" stuff we had posters all over the facility ("Strike up the band for safety.", etc...).    After a few months of this I started sneaking in slogans of my own.   The first few (things like "Security is good") escaped notice.    But they caught on the day I put up "Even the ears have walls."

[TUHS] Origin of the MOTD file?

[Dave Horsfall]

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

On Thu, 15 Mar 2018, Chet Ramey wrote:

>> One amusing thing to do with /etc/motd is to add the like “You might 
>> have mail.”  [...]
>
> Try adding "Segmentation Fault (core dumped)".

I've done both of those, along with "System down for disk crashing at 
...".  It was sort of true, as it was scheduled maintenance which involved 
removing the RK-05 disks, prising them open with something like a speculum 
(in the open air!), and running some sort of a deflection gauge along the 
platter to see how warped it was.  I think the DEC Field Circus 
Ginger-Beer also wiped the heads and replaced the NiCd battery...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."

[TUHS] Origin of the MOTD file?

[Warner Losh]

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

On Thu, Mar 15, 2018 at 2:20 PM, Dave Horsfall <dave at horsfall.org> wrote:

> On Thu, 15 Mar 2018, Chet Ramey wrote:
>
> One amusing thing to do with /etc/motd is to add the like “You might have
>>> mail.”  [...]
>>>
>>
>> Try adding "Segmentation Fault (core dumped)".
>>
>
> I've done both of those, along with "System down for disk crashing at
> ...".  It was sort of true, as it was scheduled maintenance which involved
> removing the RK-05 disks, prising them open with something like a speculum
> (in the open air!), and running some sort of a deflection gauge along the
> platter to see how warped it was.  I think the DEC Field Circus Ginger-Beer
> also wiped the heads and replaced the NiCd battery...


At school, one of the admins had in place, for a day or three, a cron job
that randomly changed /etc/motd every few minutes to append one of several
variations of Segmentation Fault (core dumped), but it was deviously
different. "Segretation Fault (core dumped)" "Segmentation Fault (core
duped)" "Bussing Error (cops deployed)" etc

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

[TUHS] Origin of the MOTD file?

[Clem Cole]

[-- 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>

[TUHS] Origin of the MOTD file?

[Clem Cole]

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

On Thu, Mar 15, 2018 at 11:51 AM, Clem Cole <clemc at ccc.com> wrote:

>
>
> ​I'm pretty sure it predates the #1 editions
>

​The numbered editions is what I was trying to say....​
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180315/524e0ba3/attachment.html>

[TUHS] Origin of the MOTD file?

[Ron Natalie]

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

One of the funniest I saw was logging into a Denelcor engineering machine.   Their company slogan was “Tomorrow’s computers…Today.”
I logged in to see the message “Tomorrow’s computers…some time next month.”



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

[TUHS] Origin of the MOTD file?

[Jeremy C. Reed]

(A similar question was asked a month ago here. From my response then 
...)

v1 has the concept "message of the day"
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V1/man/man7/login.7
but I don't find the code for it.

v2 login reads "/etc/motd"
http://minnie.tuhs.org/cgi-bin/utree.pl?file=V2/cmd/login.s

By the way, where is the code for the shell referenced in init.s for 
the earlier Unix? http://minnie.tuhs.org/cgi-bin/utree.pl?file=PDP7-Unix 

[TUHS] Origin of the MOTD file?

[Doug McIlroy]

> So what are its origins? Where did it first appear?

It was a direct copy from CTSS, which already had it
n 1965 when we BTL folk began to use it.

The greatest MOTD story of all time happened at CTSS.

To set the stage, the CTSS editor made a temp file,
always of the same name, in one's home directory.
The MOTD was posted by the administrator account.

The password file was plain text, maintained by
editing it.

And multiple people had access to the administrator
account.

It happened one day that one administrator was
working on the password file at the same time
another was posting MOTD. The result: the password
file (probably the most secret file on the system)
got posted as the MOTD (the most public).

Upon seeing the password file type out before him,
an alert user shut the machine down by writing
and running one line of assembly code:

	HERE	TRA *HERE

(The star is for indirect addressing, and indirection
was transitive.)

Doug

[TUHS] Origin of the MOTD file?

[Dave Horsfall]

On Thu, 15 Mar 2018, Doug McIlroy wrote:

> The greatest MOTD story of all time happened at CTSS.

[...]

Thanks for the real story; I keep seeing various versions of it.

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."