The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] Etymology of shell
@ 2015-12-26  2:50 Noel Chiappa
  0 siblings, 0 replies; 3+ messages in thread
From: Noel Chiappa @ 2015-12-26  2:50 UTC (permalink / raw)


    > From: John Cowan

    > Rather than starting another process, the Multics shell mapped the
    > executable program the user requested into its own space .. then jumped
    > into it. The equivalent of exit() simply jumped back to the shell code.

This is from memory, so apply the proverbial grain, but ISTR that the
original concept for the Multics shell was just like that for Unix - i.e.
each command would be a separte child process. This was given up when Multics
processes turned out to be so computationally expensive, and they went to
commands being subroutines that were dynamically linked in (very easy with
Multics, where dynamic linking was a fundamental system capability) and
called from the shell.

	Noel



^ permalink raw reply	[flat|nested] 3+ messages in thread
* [TUHS] Etymology of shell
@ 2015-12-26  1:02 Warren Toomey
  2015-12-26  2:44 ` John Cowan
  0 siblings, 1 reply; 3+ messages in thread
From: Warren Toomey @ 2015-12-26  1:02 UTC (permalink / raw)


So what is the etymology of "shell", then? I see that Multics has a shell. Was the CTSS user interface also called a shell?

Cheers, Warren
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20151226/76c871bd/attachment.html>


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

end of thread, other threads:[~2015-12-26  2:50 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-26  2:50 [TUHS] Etymology of shell Noel Chiappa
  -- strict thread matches above, loose matches on Subject: below --
2015-12-26  1:02 Warren Toomey
2015-12-26  2:44 ` John Cowan

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