The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Any Interdata war stories?
@ 2025-04-29  6:55 arnold
  2025-04-29  7:54 ` [TUHS] " Jonathan Gray
                   ` (3 more replies)
  0 siblings, 4 replies; 23+ messages in thread
From: arnold @ 2025-04-29  6:55 UTC (permalink / raw)
  To: tuhs

> From: Tom Lyon <pugs78@gmail.com>
>
> I was pleased to learn that the first port of S to UNIX was on the
> Interdata 8/32, which I had my part in enabling.

I would love to hear more about the Interdata port and what
happened with it afterwards. Interdata seems to have disappeared
into the dustbin of history.  And Unix on it apparently never
got out of Bell Labs; I don't think the code for it is in the
TUHS archives.

Was the Interdata system in use at Bell Labs for actual work once
the port was complete?

ISTR there was a meeting with Interdata about changes in the architecture
that Bell Labs wanted, that Interdata didn't want to make. What
was the full story?

Any other info would be welcome.

Thanks,

Arnold

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29  6:55 [TUHS] Any Interdata war stories? arnold
@ 2025-04-29  7:54 ` Jonathan Gray
  2025-04-30  7:08   ` arnold
  2025-04-29 17:00 ` Warner Losh
                   ` (2 subsequent siblings)
  3 siblings, 1 reply; 23+ messages in thread
From: Jonathan Gray @ 2025-04-29  7:54 UTC (permalink / raw)
  To: arnold; +Cc: tuhs

On Tue, Apr 29, 2025 at 12:55:05AM -0600, arnold@skeeve.com wrote:
> > From: Tom Lyon <pugs78@gmail.com>
> >
> > I was pleased to learn that the first port of S to UNIX was on the
> > Interdata 8/32, which I had my part in enabling.
> 
> I would love to hear more about the Interdata port and what
> happened with it afterwards. Interdata seems to have disappeared
> into the dustbin of history.  And Unix on it apparently never
> got out of Bell Labs; I don't think the code for it is in the
> TUHS archives.

Tom described some of the C portability problems in
Inter-UNIX Portability

https://archive.org/details/CLanguagePortability_Sept77/page/n15/mode/2up
https://akapugsblog.wordpress.com/wp-content/uploads/2018/05/inter-unix_portability.pdf

> 
> Was the Interdata system in use at Bell Labs for actual work once
> the port was complete?
> 
> ISTR there was a meeting with Interdata about changes in the architecture
> that Bell Labs wanted, that Interdata didn't want to make. What
> was the full story?

Steve Johnson on the hardware problems
https://www.tuhs.org/pipermail/coff/2023-August/001672.html

> 
> Any other info would be welcome.
> 
> Thanks,
> 
> Arnold
> 

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29  6:55 [TUHS] Any Interdata war stories? arnold
  2025-04-29  7:54 ` [TUHS] " Jonathan Gray
@ 2025-04-29 17:00 ` Warner Losh
  2025-04-29 17:18   ` Jon Forrest
                     ` (3 more replies)
  2025-04-30 21:17 ` Greg A. Woods
  2025-05-01  4:44 ` Tom Lyon
  3 siblings, 4 replies; 23+ messages in thread
From: Warner Losh @ 2025-04-29 17:00 UTC (permalink / raw)
  To: arnold; +Cc: tuhs

On Tue, Apr 29, 2025 at 12:55 AM <arnold@skeeve.com> wrote:
>
> > From: Tom Lyon <pugs78@gmail.com>
> >
> > I was pleased to learn that the first port of S to UNIX was on the
> > Interdata 8/32, which I had my part in enabling.
>
> I would love to hear more about the Interdata port and what
> happened with it afterwards. Interdata seems to have disappeared
> into the dustbin of history.  And Unix on it apparently never
> got out of Bell Labs; I don't think the code for it is in the
> TUHS archives.
>
> Was the Interdata system in use at Bell Labs for actual work once
> the port was complete?
>
> ISTR there was a meeting with Interdata about changes in the architecture
> that Bell Labs wanted, that Interdata didn't want to make. What
> was the full story?
>
> Any other info would be welcome.

So on the marketing side, the Interdata port wound up being sold in the US
by The Wollogong Group (TWG). They marketed it to Harris computer users
more generally. Tom and Steve were frustrated that they couldn't market this
in .au so effectively sold their rights to TWG who did market it.

And then they branched out, using their V6 license to do a number of other
things:
* Eunice for VMS (4BSD environment for VMS)
* TCP/IP for VMS (the TCP. from 4.2BSD (and later 4.3BSD) ported to VMS,
as extracted from Eunice, not to be confused with TVG's Multinet).
* TCP/IP for a bunch of other System V systems (mostly 3B2*'s) as well as
HP (both HPUX and non unix systems) and a few other early odd-balls
that my memory isn't responding well to.
* Unix internals training with the Lions Book, including AT&T and Wollgong
intellectual property markings (I wish I'd tried hard to snag a copy when
I worked there: I had to settle for an Nth generation copy from a coworker).
* Some other early porting work that may have just been marketing material
to compete with Unisoft / raise funding. I just saw this stuff once at the TWG
offices and was given some hand-wavey explanation that amounted to
"don't worry about testing this"...
* IP/TCP for DOS (though this was an independent thing, done at MIT,
the licensing material for this product, IIRC, included some kind of
unix permission that confused me at the time, but it may have just
been lawyering to CYA rather than including anything).

Warner

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:00 ` Warner Losh
@ 2025-04-29 17:18   ` Jon Forrest
  2025-04-29 17:25     ` Warner Losh
  2025-04-29 17:35   ` Al Kossow
                     ` (2 subsequent siblings)
  3 siblings, 1 reply; 23+ messages in thread
From: Jon Forrest @ 2025-04-29 17:18 UTC (permalink / raw)
  To: tuhs



On 4/29/25 10:00 AM, Warner Losh wrote:

> And then they branched out, using their V6 license to do a number of other
> things:
> * Eunice for VMS (4BSD environment for VMS)

Minor quible - Eunice was developed by David Kashtan at SRI, but
then maintained and marketed the The Wollongong Group.
(I used it on VMS at UCSB in the early 1980s).

Jon

P.S. A non-Unix Interdata memory. At UCSB we used 3 Interdata
machines as terminal switchers. You could connect from a terminal
in certain terminal rooms to any of a number of computers on campus that
had support for the switching protocol. The names of the Interdata
machines were "huey", "duey", and "louie". There was allegedly a
fourth machine called "kablooey" that was used as a backup.

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:18   ` Jon Forrest
@ 2025-04-29 17:25     ` Warner Losh
  0 siblings, 0 replies; 23+ messages in thread
From: Warner Losh @ 2025-04-29 17:25 UTC (permalink / raw)
  To: Jon Forrest; +Cc: tuhs

On Tue, Apr 29, 2025 at 11:18 AM Jon Forrest <nobozo@gmail.com> wrote:
>
>
>
> On 4/29/25 10:00 AM, Warner Losh wrote:
>
> > And then they branched out, using their V6 license to do a number of other
> > things:
> > * Eunice for VMS (4BSD environment for VMS)
>
> Minor quible - Eunice was developed by David Kashtan at SRI, but
> then maintained and marketed the The Wollongong Group.
> (I used it on VMS at UCSB in the early 1980s).

True, I mentioned it only because they used their V6 license which
had unusually favorable terms to do so... Which is an unanticipated
"long hand" of the interdata port into the late 80s and early 90s.

Warner

> Jon
>
> P.S. A non-Unix Interdata memory. At UCSB we used 3 Interdata
> machines as terminal switchers. You could connect from a terminal
> in certain terminal rooms to any of a number of computers on campus that
> had support for the switching protocol. The names of the Interdata
> machines were "huey", "duey", and "louie". There was allegedly a
> fourth machine called "kablooey" that was used as a backup.

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:00 ` Warner Losh
  2025-04-29 17:18   ` Jon Forrest
@ 2025-04-29 17:35   ` Al Kossow
  2025-04-30  7:21     ` arnold
  2025-04-29 17:58   ` Rich Salz
  2025-04-29 18:28   ` Chet Ramey via TUHS
  3 siblings, 1 reply; 23+ messages in thread
From: Al Kossow @ 2025-04-29 17:35 UTC (permalink / raw)
  To: tuhs

On 4/29/25 10:00 AM, Warner Losh wrote:
> On Tue, Apr 29, 2025 at 12:55 AM <arnold@skeeve.com> wrote:
>>
>>> From: Tom Lyon <pugs78@gmail.com>
>>>
>>> I was pleased to learn that the first port of S to UNIX was on the
>>> Interdata 8/32, which I had my part in enabling.
>>
>> I would love to hear more about the Interdata port and what
>> happened with it afterwards. Interdata seems to have disappeared
>> into the dustbin of history.  And Unix on it apparently never
>> got out of Bell Labs; I don't think the code for it is in the
>> TUHS archives.
>>

Two different ports.
TWG's port was written at the University of Wollongong, extensive
documentation and SIMH emulation survives.

No trace of the BTL port exists that I know of

Interdata was bought by Perkin-Elmer, Perkin-Elmer sold it to
Concurrent Computer Corp.



^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:00 ` Warner Losh
  2025-04-29 17:18   ` Jon Forrest
  2025-04-29 17:35   ` Al Kossow
@ 2025-04-29 17:58   ` Rich Salz
  2025-04-29 18:25     ` Clem Cole
  2025-04-29 18:28   ` Chet Ramey via TUHS
  3 siblings, 1 reply; 23+ messages in thread
From: Rich Salz @ 2025-04-29 17:58 UTC (permalink / raw)
  To: Warner Losh; +Cc: tuhs

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

On Tue, Apr 29, 2025 at 1:00 PM Warner Losh <imp@bsdimp.com> wrote:

> * IP/TCP for DOS (though this was an independent thing, done at MIT,
> the licensing material for this product, IIRC, included some kind of
> unix permission that confused me at the time, but it may have just
> been lawyering to CYA rather than including anything).
>

The PC/IP software from MIT included a port of the "Portable C Compiler" to
generate 8086-era code. It ran on a Unix machine and built binaries that
you downloaded to the PC. So you need an ATT source license to get the full
PCIP dev kit.

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:58   ` Rich Salz
@ 2025-04-29 18:25     ` Clem Cole
  2025-04-29 18:38       ` Warner Losh
  2025-04-29 18:46       ` Al Kossow
  0 siblings, 2 replies; 23+ messages in thread
From: Clem Cole @ 2025-04-29 18:25 UTC (permalink / raw)
  To: Rich Salz; +Cc: tuhs

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

Yes, that was one of the RTS compilers for the NU machine.  John Romkey may
have done it, as he was the primary person behind PCIP, but I can not claim
I remember who did the 8086 backend.  IIRC Jack Test did the 68K backend.
The RTS crew had the NU machine and NU bus that went with it.   Very tean
project Neat project.  Similar idea, in fact to what CMU was doing with the
Intel Mutlibus called the distributed front end (we had started with LSI-11
and cost reduced it to 8086 on a Intel Multibus).  Andy Bechtolsheim would
take with him to Stanford and rework with a 68K which became the
Stanford Network Terminal - which used the RTS's C compilers.   It's all
very mixed up. [ Don't tell me there was not an open source culture back in
the old days by the way].

Anyway the MIT RTS foilks made hardware and PCC back ends for the 68K,
Z8000 and 8086.  I believe that each had separate assemblers, tjt who
sometimes reads this list might know more, as he wrote the 68K assembler.
IIRC they had a common linker which is was rewrite/extension to the
original V7 linker or maybe the 4.1 linker.

Anyone with a V7 license could get it.   If you had a PC license you get
get the source to Romkey's PCIP.   If you did not a license, you could only
get a binary kit.
ᐧ

On Tue, Apr 29, 2025 at 1:59 PM Rich Salz <rich.salz@gmail.com> wrote:

>
>
> On Tue, Apr 29, 2025 at 1:00 PM Warner Losh <imp@bsdimp.com> wrote:
>
>> * IP/TCP for DOS (though this was an independent thing, done at MIT,
>> the licensing material for this product, IIRC, included some kind of
>> unix permission that confused me at the time, but it may have just
>> been lawyering to CYA rather than including anything).
>>
>
> The PC/IP software from MIT included a port of the "Portable C Compiler"
> to generate 8086-era code. It ran on a Unix machine and built binaries that
> you downloaded to the PC. So you need an ATT source license to get the full
> PCIP dev kit.
>
>

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:00 ` Warner Losh
                     ` (2 preceding siblings ...)
  2025-04-29 17:58   ` Rich Salz
@ 2025-04-29 18:28   ` Chet Ramey via TUHS
  2025-04-29 21:03     ` Henry Bent
  3 siblings, 1 reply; 23+ messages in thread
From: Chet Ramey via TUHS @ 2025-04-29 18:28 UTC (permalink / raw)
  To: Warner Losh, arnold; +Cc: tuhs

On 4/29/25 1:00 PM, Warner Losh wrote:

> And then they branched out, using their V6 license to do a number of other
> things:
> * Eunice for VMS (4BSD environment for VMS)

"Congratulations.  You aren't running Eunice."

-- 
``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/

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 18:25     ` Clem Cole
@ 2025-04-29 18:38       ` Warner Losh
  2025-04-29 18:46       ` Al Kossow
  1 sibling, 0 replies; 23+ messages in thread
From: Warner Losh @ 2025-04-29 18:38 UTC (permalink / raw)
  To: Clem Cole; +Cc: The Eunuchs Hysterical Society

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

On Tue, Apr 29, 2025, 12:26 PM Clem Cole <clemc@ccc.com> wrote:

> Yes, that was one of the RTS compilers for the NU machine.  John Romkey
> may have done it, as he was the primary person behind PCIP, but I can not
> claim I remember who did the 8086 backend.  IIRC Jack Test did the 68K
> backend.  The RTS crew had the NU machine and NU bus that went with it.
>  Very tean project Neat project.  Similar idea, in fact to what CMU was
> doing with the Intel Mutlibus called the distributed front end (we had
> started with LSI-11 and cost reduced it to 8086 on a Intel Multibus).  Andy
> Bechtolsheim would take with him to Stanford and rework with a 68K which
> became the Stanford Network Terminal - which used the RTS's C compilers.
>  It's all very mixed up. [ Don't tell me there was not an open source
> culture back in the old days by the way].
>
> Anyway the MIT RTS foilks made hardware and PCC back ends for the 68K,
> Z8000 and 8086.  I believe that each had separate assemblers, tjt who
> sometimes reads this list might know more, as he wrote the 68K assembler.
> IIRC they had a common linker which is was rewrite/extension to the
> original V7 linker or maybe the 4.1 linker.
>
> Anyone with a V7 license could get it.   If you had a PC license you get
> get the source to Romkey's PCIP.   If you did not a license, you could only
> get a binary kit.
> ᐧ
>
> On Tue, Apr 29, 2025 at 1:59 PM Rich Salz <rich.salz@gmail.com> wrote:
>
>>
>>
>> On Tue, Apr 29, 2025 at 1:00 PM Warner Losh <imp@bsdimp.com> wrote:
>>
>>> * IP/TCP for DOS (though this was an independent thing, done at MIT,
>>> the licensing material for this product, IIRC, included some kind of
>>> unix permission that confused me at the time, but it may have just
>>> been lawyering to CYA rather than including anything).
>>>
>>
>> The PC/IP software from MIT included a port of the "Portable C Compiler"
>> to generate 8086-era code. It ran on a Unix machine and built binaries that
>> you downloaded to the PC. So you need an ATT source license to get the full
>> PCIP dev kit.
>>
>
Yea. The MIT compiler was also shipped with Venix/86

Warner

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 18:25     ` Clem Cole
  2025-04-29 18:38       ` Warner Losh
@ 2025-04-29 18:46       ` Al Kossow
  2025-04-29 19:07         ` Al Kossow
  2025-04-29 23:27         ` Jonathan Gray
  1 sibling, 2 replies; 23+ messages in thread
From: Al Kossow @ 2025-04-29 18:46 UTC (permalink / raw)
  To: tuhs

On 4/29/25 11:25 AM, Clem Cole wrote:
> Yes, that was one of the RTS compilers for the NU machine.  John Romkey may have done it, as he was the primary person behind PCIP, but I 
> can not claim I remember who did the 8086 backend.  IIRC Jack Test did the 68K backend.  The RTS crew had the NU machine and NU bus that 
> went with it.   Very tean project Neat project.  Similar idea, in fact to what CMU was doing with the Intel Mutlibus called the distributed 
> front end (we had started with LSI-11 and cost reduced it to 8086 on a Intel Multibus).  Andy Bechtolsheim would take with him to Stanford 
> and rework with a 68K which became the Stanford Network Terminal - which used the RTS's C compilers.   It's all very mixed up. [ Don't tell 
> me there was not an open source culture back in the old days by the way].
> 
> Anyway the MIT RTS foilks made hardware and PCC back ends for the 68K, Z8000 and 8086.  I believe that each had separate assemblers, tjt who 
> sometimes reads this list might know more, as he wrote the 68K assembler.  IIRC they had a common linker which is was rewrite/extension to 
> the original V7 linker or maybe the 4.1 linker.
> 
> Anyone with a V7 license could get it.   If you had a PC license you get get the source to Romkey's PCIP.   If you did not a license, you 
> could only get a binary kit.

I have an image of the "MIT Compiler Tape" with a bunch of different PCC ports from a couple of different institutions.

On the Stanford side, SUMACC was a hack of the compiler to work with the Macintosh
I had the source for it at one point, but haven't been able to find it on any of my backups.


^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 18:46       ` Al Kossow
@ 2025-04-29 19:07         ` Al Kossow
  2025-04-29 19:10           ` Warner Losh
  2025-04-29 19:45           ` Clem Cole
  2025-04-29 23:27         ` Jonathan Gray
  1 sibling, 2 replies; 23+ messages in thread
From: Al Kossow @ 2025-04-29 19:07 UTC (permalink / raw)
  To: tuhs

On 4/29/25 11:46 AM, Al Kossow wrote:

> I have an image of the "MIT Compiler Tape" with a bunch of different PCC ports from a couple of different institutions.

I forgot I put this up a while ago
http://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape

I wish I had more information about what went on wrt Steve Ward's lab


^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 19:07         ` Al Kossow
@ 2025-04-29 19:10           ` Warner Losh
  2025-04-29 19:45           ` Clem Cole
  1 sibling, 0 replies; 23+ messages in thread
From: Warner Losh @ 2025-04-29 19:10 UTC (permalink / raw)
  To: Al Kossow; +Cc: tuhs

On Tue, Apr 29, 2025 at 1:07 PM Al Kossow <aek@bitsavers.org> wrote:
>
> On 4/29/25 11:46 AM, Al Kossow wrote:
>
> > I have an image of the "MIT Compiler Tape" with a bunch of different PCC ports from a couple of different institutions.
>
> I forgot I put this up a while ago
> http://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape
>
> I wish I had more information about what went on wrt Steve Ward's lab

I've tried building that for modern systems and the code is definitely
very K&R...
In one spot, IIRC, there's even a vax queue instruction.

Warner

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 19:07         ` Al Kossow
  2025-04-29 19:10           ` Warner Losh
@ 2025-04-29 19:45           ` Clem Cole
  2025-04-29 20:14             ` segaloco via TUHS
  1 sibling, 1 reply; 23+ messages in thread
From: Clem Cole @ 2025-04-29 19:45 UTC (permalink / raw)
  To: Al Kossow; +Cc: tuhs

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

Thanks for the refresh -- National chip (16032), not the Z8000 but right
idea.
ᐧ

On Tue, Apr 29, 2025 at 3:07 PM Al Kossow <aek@bitsavers.org> wrote:

> On 4/29/25 11:46 AM, Al Kossow wrote:
>
> > I have an image of the "MIT Compiler Tape" with a bunch of different PCC
> ports from a couple of different institutions.
>
> I forgot I put this up a while ago
> http://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape
>
> I wish I had more information about what went on wrt Steve Ward's lab
>
>

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 19:45           ` Clem Cole
@ 2025-04-29 20:14             ` segaloco via TUHS
  0 siblings, 0 replies; 23+ messages in thread
From: segaloco via TUHS @ 2025-04-29 20:14 UTC (permalink / raw)
  To: tuhs

On Tuesday, April 29th, 2025 at 12:45 PM, Clem Cole <clemc@ccc.com> wrote:

> Thanks for the refresh -- National chip (16032), not the Z8000 but right idea.
> ᐧ
> 
> On Tue, Apr 29, 2025 at 3:07 PM Al Kossow <aek@bitsavers.org> wrote:
> 
> > On 4/29/25 11:46 AM, Al Kossow wrote:
> > 
> > > I have an image of the "MIT Compiler Tape" with a bunch of different PCC ports from a couple of different institutions.
> > 
> > I forgot I put this up a while ago
> > http://bitsavers.org/bits/MIT/trix/MIT_Compiler_Tape
> > 
> > I wish I had more information about what went on wrt Steve Ward's lab

Just fyi, thread from a couple years back in which Steve Johnson offered some recollections of his time involved in the Interdata 8/32 work at BTL: https://tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/thread/WH4IEMFZEZEDPG5VQHDWKTS6UTRMTRLL/

His recollections above touch on the microcode bug that prevented the Interdata port from being viable beyond porting exercises.

- Matt G.

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 18:28   ` Chet Ramey via TUHS
@ 2025-04-29 21:03     ` Henry Bent
  0 siblings, 0 replies; 23+ messages in thread
From: Henry Bent @ 2025-04-29 21:03 UTC (permalink / raw)
  To: chet.ramey; +Cc: tuhs

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

On Tue, 29 Apr 2025 at 14:36, Chet Ramey via TUHS <tuhs@tuhs.org> wrote:

> On 4/29/25 1:00 PM, Warner Losh wrote:
>
> > And then they branched out, using their V6 license to do a number of
> other
> > things:
> > * Eunice for VMS (4BSD environment for VMS)
>
> "Congratulations.  You aren't running Eunice."


Perl has some good quips hidden in Configure but that was always one of my
favorites, even well before I had any real idea what Eunice was.

Personally I want a t-shirt that says "configure: error: cannot guess host
type; you must specify one" which nicely sums up my experiences with both
historic computing and my general life.

-Henry

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 18:46       ` Al Kossow
  2025-04-29 19:07         ` Al Kossow
@ 2025-04-29 23:27         ` Jonathan Gray
  1 sibling, 0 replies; 23+ messages in thread
From: Jonathan Gray @ 2025-04-29 23:27 UTC (permalink / raw)
  To: Al Kossow; +Cc: tuhs

On Tue, Apr 29, 2025 at 11:46:19AM -0700, Al Kossow wrote:
> On 4/29/25 11:25 AM, Clem Cole wrote:
> > Yes, that was one of the RTS compilers for the NU machine.  John Romkey
> > may have done it, as he was the primary person behind PCIP, but I can
> > not claim I remember who did the 8086 backend.  IIRC Jack Test did the
> > 68K backend.  The RTS crew had the NU machine and NU bus that went with
> > it.   Very tean project Neat project.  Similar idea, in fact to what CMU
> > was doing with the Intel Mutlibus called the distributed front end (we
> > had started with LSI-11 and cost reduced it to 8086 on a Intel
> > Multibus).  Andy Bechtolsheim would take with him to Stanford and rework
> > with a 68K which became the Stanford Network Terminal - which used the
> > RTS's C compilers.   It's all very mixed up. [ Don't tell me there was
> > not an open source culture back in the old days by the way].
> > 
> > Anyway the MIT RTS foilks made hardware and PCC back ends for the 68K,
> > Z8000 and 8086.  I believe that each had separate assemblers, tjt who
> > sometimes reads this list might know more, as he wrote the 68K
> > assembler.  IIRC they had a common linker which is was rewrite/extension
> > to the original V7 linker or maybe the 4.1 linker.
> > 
> > Anyone with a V7 license could get it.   If you had a PC license you get
> > get the source to Romkey's PCIP.   If you did not a license, you could
> > only get a binary kit.
> 
> I have an image of the "MIT Compiler Tape" with a bunch of different PCC ports from a couple of different institutions.
> 
> On the Stanford side, SUMACC was a hack of the compiler to work with the Macintosh
> I had the source for it at one point, but haven't been able to find it on any of my backups.

in the TUHS archive
Distributions/UCB/4.3BSD/new.tar.gz

contains sumacc.tar.Z which has source

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29  7:54 ` [TUHS] " Jonathan Gray
@ 2025-04-30  7:08   ` arnold
  0 siblings, 0 replies; 23+ messages in thread
From: arnold @ 2025-04-30  7:08 UTC (permalink / raw)
  To: jsg, arnold; +Cc: tuhs

Thanks for this, and to everyone else who replied. I'm guessing
the hardware problems prevented the system from being used further.

Thanks,

Arnold

Jonathan Gray <jsg@jsg.id.au> wrote:

> On Tue, Apr 29, 2025 at 12:55:05AM -0600, arnold@skeeve.com wrote:
> > > From: Tom Lyon <pugs78@gmail.com>
> > >
> > > I was pleased to learn that the first port of S to UNIX was on the
> > > Interdata 8/32, which I had my part in enabling.
> > 
> > I would love to hear more about the Interdata port and what
> > happened with it afterwards. Interdata seems to have disappeared
> > into the dustbin of history.  And Unix on it apparently never
> > got out of Bell Labs; I don't think the code for it is in the
> > TUHS archives.
>
> Tom described some of the C portability problems in
> Inter-UNIX Portability
>
> https://archive.org/details/CLanguagePortability_Sept77/page/n15/mode/2up
> https://akapugsblog.wordpress.com/wp-content/uploads/2018/05/inter-unix_portability.pdf
>
> > 
> > Was the Interdata system in use at Bell Labs for actual work once
> > the port was complete?
> > 
> > ISTR there was a meeting with Interdata about changes in the architecture
> > that Bell Labs wanted, that Interdata didn't want to make. What
> > was the full story?
>
> Steve Johnson on the hardware problems
> https://www.tuhs.org/pipermail/coff/2023-August/001672.html
>
> > 
> > Any other info would be welcome.
> > 
> > Thanks,
> > 
> > Arnold
> > 

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29 17:35   ` Al Kossow
@ 2025-04-30  7:21     ` arnold
  2025-04-30  7:35       ` Bakul Shah via TUHS
  0 siblings, 1 reply; 23+ messages in thread
From: arnold @ 2025-04-30  7:21 UTC (permalink / raw)
  To: tuhs, aek

Al Kossow <aek@bitsavers.org> wrote:

> Two different ports.
> TWG's port was written at the University of Wollongong, extensive
> documentation and SIMH emulation survives.

Ah! I was shown a V6 port on SIMH, but Bell Labs didn't do
a port of V6. This explains it.

> No trace of the BTL port exists that I know of
>
> Interdata was bought by Perkin-Elmer, Perkin-Elmer sold it to
> Concurrent Computer Corp.

CCI made the Tahoe that 4.4 ran on, but I'm guessing it's
a different architecture than the Interdata?

Thanks,

Arnold

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-30  7:21     ` arnold
@ 2025-04-30  7:35       ` Bakul Shah via TUHS
  2025-04-30  7:39         ` Bakul Shah via TUHS
  0 siblings, 1 reply; 23+ messages in thread
From: Bakul Shah via TUHS @ 2025-04-30  7:35 UTC (permalink / raw)
  To: arnold; +Cc: tuhs, aek

On Apr 30, 2025, at 12:21 AM, arnold@skeeve.com wrote:
> 
> Al Kossow <aek@bitsavers.org> wrote:
> 
>> Two different ports.
>> TWG's port was written at the University of Wollongong, extensive
>> documentation and SIMH emulation survives.
> 
> Ah! I was shown a V6 port on SIMH, but Bell Labs didn't do
> a port of V6. This explains it.

The story of this first port (by Richard Miller) here:

https://www.tuhs.org/Archive/Distributions/Other/Interdata/uow103747.pdf

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-30  7:35       ` Bakul Shah via TUHS
@ 2025-04-30  7:39         ` Bakul Shah via TUHS
  0 siblings, 0 replies; 23+ messages in thread
From: Bakul Shah via TUHS @ 2025-04-30  7:39 UTC (permalink / raw)
  To: arnold; +Cc: tuhs, aek

On Apr 30, 2025, at 12:35 AM, Bakul Shah <bakul@iitbombay.org> wrote:
> 
> On Apr 30, 2025, at 12:21 AM, arnold@skeeve.com wrote:
>> 
>> Al Kossow <aek@bitsavers.org> wrote:
>> 
>>> Two different ports.
>>> TWG's port was written at the University of Wollongong, extensive
>>> documentation and SIMH emulation survives.
>> 
>> Ah! I was shown a V6 port on SIMH, but Bell Labs didn't do
>> a port of V6. This explains it.
> 
> The story of this first port (by Richard Miller) here:
> 
> https://www.tuhs.org/Archive/Distributions/Other/Interdata/uow103747.pdf

More details in Richard's invited talk @ Usenix:

https://www.usenix.org/legacy/publications/library/proceedings/usenix98/invited_talks/miller.ps



^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29  6:55 [TUHS] Any Interdata war stories? arnold
  2025-04-29  7:54 ` [TUHS] " Jonathan Gray
  2025-04-29 17:00 ` Warner Losh
@ 2025-04-30 21:17 ` Greg A. Woods
  2025-05-01  4:44 ` Tom Lyon
  3 siblings, 0 replies; 23+ messages in thread
From: Greg A. Woods @ 2025-04-30 21:17 UTC (permalink / raw)
  To: The Unix Heritage Society mailing list

At Tue, 29 Apr 2025 00:55:05 -0600, arnold@skeeve.com wrote:
Subject: [TUHS] Any Interdata war stories?
> 
> > From: Tom Lyon <pugs78@gmail.com>
> >
> > I was pleased to learn that the first port of S to UNIX was on the
> > Interdata 8/32, which I had my part in enabling.
> 
> I would love to hear more about the Interdata port and what
> happened with it afterwards. Interdata seems to have disappeared
> into the dustbin of history.  And Unix on it apparently never
> got out of Bell Labs;

In about 1981 or 1982 the chemistry (IIRC) department at University of
Calgary had an Interdata 8/32 that was, at least for some time around
then, running Unix.  I remember poking around on it briefly, but I don't
remember much more than that about it.

-- 
					Greg A. Woods <gwoods@acm.org>

Kelowna, BC     +1 250 762-7675           RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com>     Avoncote Farms <woods@avoncote.ca>

^ permalink raw reply	[flat|nested] 23+ messages in thread

* [TUHS] Re: Any Interdata war stories?
  2025-04-29  6:55 [TUHS] Any Interdata war stories? arnold
                   ` (2 preceding siblings ...)
  2025-04-30 21:17 ` Greg A. Woods
@ 2025-05-01  4:44 ` Tom Lyon
  3 siblings, 0 replies; 23+ messages in thread
From: Tom Lyon @ 2025-05-01  4:44 UTC (permalink / raw)
  To: arnold; +Cc: tuhs

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

I found this USENIX paper from Steve Johnson that has a lot of detail about
the
Interdata port (postscript format):

"C and the AT&T Unix Port--A Personal History"
https://www.usenix.org/legacy/publications/library/proceedings/usenix98/invited_talks/johnson.ps


On Mon, Apr 28, 2025 at 11:55 PM <arnold@skeeve.com> wrote:

> > From: Tom Lyon <pugs78@gmail.com>
> >
> > I was pleased to learn that the first port of S to UNIX was on the
> > Interdata 8/32, which I had my part in enabling.
>
> I would love to hear more about the Interdata port and what
> happened with it afterwards. Interdata seems to have disappeared
> into the dustbin of history.  And Unix on it apparently never
> got out of Bell Labs; I don't think the code for it is in the
> TUHS archives.
>
> Was the Interdata system in use at Bell Labs for actual work once
> the port was complete?
>
> ISTR there was a meeting with Interdata about changes in the architecture
> that Bell Labs wanted, that Interdata didn't want to make. What
> was the full story?
>
> Any other info would be welcome.
>
> Thanks,
>
> Arnold
>

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

^ permalink raw reply	[flat|nested] 23+ messages in thread

end of thread, other threads:[~2025-05-01  4:45 UTC | newest]

Thread overview: 23+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-04-29  6:55 [TUHS] Any Interdata war stories? arnold
2025-04-29  7:54 ` [TUHS] " Jonathan Gray
2025-04-30  7:08   ` arnold
2025-04-29 17:00 ` Warner Losh
2025-04-29 17:18   ` Jon Forrest
2025-04-29 17:25     ` Warner Losh
2025-04-29 17:35   ` Al Kossow
2025-04-30  7:21     ` arnold
2025-04-30  7:35       ` Bakul Shah via TUHS
2025-04-30  7:39         ` Bakul Shah via TUHS
2025-04-29 17:58   ` Rich Salz
2025-04-29 18:25     ` Clem Cole
2025-04-29 18:38       ` Warner Losh
2025-04-29 18:46       ` Al Kossow
2025-04-29 19:07         ` Al Kossow
2025-04-29 19:10           ` Warner Losh
2025-04-29 19:45           ` Clem Cole
2025-04-29 20:14             ` segaloco via TUHS
2025-04-29 23:27         ` Jonathan Gray
2025-04-29 18:28   ` Chet Ramey via TUHS
2025-04-29 21:03     ` Henry Bent
2025-04-30 21:17 ` Greg A. Woods
2025-05-01  4:44 ` Tom Lyon

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).