10 Jan
2017
10 Jan
'17
8:52 p.m.
I asked:
I wonder where the inspiration for the Unix job
control came from? In
particular, I can't help but notice that Control-Z does something very
similar in the PDP-10 Incompatible Timesharing System.
Jim Kulp answered:
The ITS capabilities were certainly part of the
inspiration. It was a
combination of frustrations and gaps in UNIX with some of those
features found in ITS that resulted in the final package of features.
11 Jan
11 Jan
3:19 a.m.
Yes, ITS and Tenex/TOPS were the inspiration for UNIX ^Z. When I was at
Berkeley, of course we didn't have windowing environments, we had dumb
terminals, and it was nice to be able to interrupt a long-running job
for a shell command. I recall asking for it, and I think Bill put it
into csh.
On 01/10/2017 12:52 PM, Lars Brinkhoff wrote:
I asked:
I wonder where the inspiration for the Unix job
control came from? In
particular, I can't help but notice that Control-Z does something very
similar in the PDP-10 Incompatible Timesharing System.
Jim Kulp answered:
> The ITS capabilities were certainly part of the inspiration. It was a
> combination of frustrations and gaps in UNIX with some of those
> features found in ITS that resulted in the final package of features.
12:37 p.m.
Mary Ann Horton wrote:
Jim Kulp wrote:
Not so much TOPS-20, according to Jim Kulp.
Lars Brinkhoff wrote:
Yes, ITS and Tenex/TOPS were the inspiration for UNIX ^Z. I wonder where the inspiration for the Unix job
control came from? In
particular, I can't help but notice that Control-Z does something very
similar in the PDP-10 Incompatible Timesharing System.
The ITS capabilities were certainly part of the inspiration. It was a
combination of frustrations and gaps in UNIX with some of those
features found in ITS that resulted in the final package of features.
3024
days inactive
3025
days old
2 comments
2 participants
participants (2)
-
Lars Brinkhoff -
Mary Ann Horton