The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: John Cowan <cowan@ccil.org>
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, tuhs@tuhs.org
Subject: [TUHS] Re: Unix v7 icheck dup problem
Date: Fri, 3 Mar 2023 19:23:11 -0500	[thread overview]
Message-ID: <59d19eec-dca8-aed6-f9dc-ba8be6b648cf@case.edu> (raw)
In-Reply-To: <CAD2gp_R2=+vYgYLTVrHQ6GtwEGC9jgWDk7sK9x=sb4d6SEfSHQ@mail.gmail.com>

On 3/3/23 4:26 PM, John Cowan wrote:
> 
> 
> On Fri, Mar 3, 2023 at 2:25 PM Chet Ramey <chet.ramey@case.edu 
> <mailto:chet.ramey@case.edu>> wrote:
> 
>     A former CWRU president (very soon after the merger) used to tell freshmen
>     the same thing during his annual address to the incoming class.
> 
> 
> I remember being told that when I arrived at Case in 1976; sure enough, 
> within a year I was the one who had departed.  

That's Louis Toepfer. Also famous for the other line he was fond of:
"Learning is suffering."


> Two other things I remember from that speech were that Michelson was a 
> Casie and Morley was a Reservie,

Quite true. That distinction was more important back then, closer to the
merger. There were still "Casies" and "Reservies" when I went, but the
subsequent administrations have done a lot of work to unify the campus.

  and that (as the campus was completely
> covered with mud at the time), we were never to trust 100-year flood 
> estimates in the United States, as there was not enough evidence to go on, 
> and that in fact that was the third 100-year flood in Cleveland in the last 
> 16 years.

Doan Creek (buried and yet) still floods from time to time, most recently a
few years ago. It flooded the basement and parking garage of the building
where I work.

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


  reply	other threads:[~2023-03-04  0:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 18:22 Noel Chiappa
2023-03-03 19:25 ` Chet Ramey
2023-03-03 21:26   ` John Cowan
2023-03-04  0:23     ` Chet Ramey [this message]
2023-03-03 19:35 ` Clem Cole
2023-03-04  2:45   ` Jonathan Gray
2023-03-03 23:00 ` Jonathan Gray
2023-03-04  9:07 ` Jonathan Gray
2023-03-04 11:19   ` KenUnix
  -- strict thread matches above, loose matches on Subject: below --
2023-03-06  8:14 Noel Chiappa
2023-03-06  8:58 ` Jonathan Gray
2023-03-07  2:05   ` Kenneth Goodwin
2023-03-04 14:41 Noel Chiappa
2023-03-04 14:49 ` KenUnix
2023-03-02  1:59 Noel Chiappa
2023-03-02  2:11 ` Dan Cross
2023-03-02  1:36 Noel Chiappa
2023-03-02  1:56 ` John Cowan
2023-03-02  6:41   ` Lars Brinkhoff
2023-03-02  2:12 ` Bakul Shah
2023-03-02  2:46   ` Rich Salz
2023-03-01 21:29 Noel Chiappa
2023-03-01 21:54 ` KenUnix
2023-03-01 21:55 ` John Cowan
2023-03-01 22:15 ` Jon Forrest
2023-03-02  4:16 ` Jonathan Gray
2023-03-01 15:09 Noel Chiappa
2023-03-01 16:18 ` Ron Natalie
2023-03-01 16:45   ` KenUnix
2023-03-01 16:57 ` Theodore Ts'o
2023-03-01 20:52 ` Dave Horsfall
2023-03-02  1:46   ` Jonathan Gray
2023-03-02  3:05     ` Dave Horsfall
2023-03-02  7:56       ` John Cowan
2023-03-02  8:53         ` Steve Nickolas
2023-03-02  8:01       ` Jonathan Gray
2023-03-02  7:34   ` arnold

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=59d19eec-dca8-aed6-f9dc-ba8be6b648cf@case.edu \
    --to=chet.ramey@case.edu \
    --cc=cowan@ccil.org \
    --cc=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).