The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: chet.ramey@case.edu
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Question about BSD disklabel history
Date: Tue, 2 Jan 2024 15:07:45 -0500	[thread overview]
Message-ID: <CAC20D2Oa9X0LX545Hu-Zi_re6+j5Gymj67=O25m8gNikpEdHng@mail.gmail.com> (raw)
In-Reply-To: <798cf2fb-68b7-44b2-96ec-eb164c5b2a5c@case.edu>

[-- Attachment #1: Type: text/plain, Size: 1691 bytes --]

On Tue, Jan 2, 2024 at 2:31 PM Chet Ramey <chet.ramey@case.edu> wrote:

> On 1/2/24 1:49 PM, Warner Losh wrote:
>
> >     Right, this is all of the MK0, CSRG, and Sun connection via Fred,
> Bill,
> >     and Sam.  At a minimum, they knew what the other was doing/had done,
> >     and some of it definitely migrated.
> >
> >
> > What's MK0? Is that the group at DEC that did Unix?
>
DEC Merrimack NH Site - where Telephone Industries Group (TIG) and Custom
Special Systems (CSS) were located. It was originally the site dedicated to
supporting DEC's largest customer - AT & T.  Bill Munson originally ran TIG.
Armando, Jean, Shannon, Cantor, *et al.* worked in TIG.  Those folks
eventually moved to ZK03 - Spit Brook Road, in Nashua, with the other OS
teams when Ultrix was created.

Sorry, old habits are hard to change.  Except for the Mill itself, many, if
not most, of us from the old days still refer to the different DEC sites
(particularly the original New Englands) by their site code.  For instance,
my old offices were in MR02 (Marlboro, MA) and ZK03.

Years later, the compiler team (in ZK02) was sold twice, and they never
moved their desk. Hence, when I later joined Intel, my desk was placed in
ZK02 with the compiler folks like Paul W. In fact, when Intel finally moved
us out, we realized that folks like Steve Hobbs had not moved his desk in
30 years.

I don't know what MK0 is either, but Bill Shannon and Sam Leffler had been
> friends since they were both grad students here at CWRU, so I would assume
> they kept in touch about what they were doing.
>
Indeed, and having been friends with them both, I can verify that they did.
ᐧ

[-- Attachment #2: Type: text/html, Size: 3650 bytes --]

  reply	other threads:[~2024-01-02 20:08 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-31 17:30 [TUHS] " Grant Taylor via TUHS
2023-12-31 17:38 ` [TUHS] " arnold
2023-12-31 20:07   ` Warner Losh
2024-01-01  0:13     ` Bakul Shah
2023-12-31 20:27   ` Phil Budne
2023-12-31 21:02     ` Warner Losh
2024-01-01  0:26   ` Grant Taylor via TUHS
2024-01-01  2:22     ` Warner Losh
2024-01-01  3:24       ` Grant Taylor via TUHS
2023-12-31 21:31 ` Clem Cole
2023-12-31 22:07   ` Warner Losh
2024-01-01 16:00     ` Clem Cole
2024-01-02 18:49       ` Warner Losh
2024-01-02 19:30         ` Chet Ramey
2024-01-02 20:07           ` Clem Cole [this message]
2024-01-02 19:50         ` Dan Cross
2024-01-02 19:55           ` Jim Capp
2024-01-02 20:11             ` Dan Cross
2024-01-02 20:30           ` Dan Cross
2024-01-02 20:50             ` Clem Cole
2024-01-02 21:04               ` Dan Cross
2023-12-31 22:46   ` G. Branden Robinson
2023-12-31 23:06     ` Larry McVoy
2023-12-31 23:37       ` Al Kossow
2023-12-31 23:41       ` Alec Muffett
2024-01-02 20:48       ` Dan Cross
2024-01-02 21:17         ` John Cowan
2024-01-03  3:33         ` Theodore Ts'o
2024-01-03  3:57           ` Warner Losh
2024-01-03  4:03             ` Warner Losh
2024-01-03  4:30             ` Theodore Ts'o
2024-01-03  5:10               ` Warner Losh
2024-01-03 15:56                 ` Dan Cross
2024-01-03 16:37                   ` Theodore Ts'o
2024-01-03 16:41                     ` Dan Cross
2024-01-04  8:42                     ` arnold
2024-01-04 18:26                       ` Kevin Bowling
2024-01-03 14:39           ` Dan Cross
2023-12-31 23:08     ` Phil Budne
2023-12-31 23:37       ` G. Branden Robinson
2023-12-31 23:59         ` Warner Losh
2023-12-31 23:50     ` G. Branden Robinson
2024-01-01  0:09       ` Al Kossow
2023-12-31 21:55 Norman Wilson

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='CAC20D2Oa9X0LX545Hu-Zi_re6+j5Gymj67=O25m8gNikpEdHng@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=chet.ramey@case.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).