Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site rochester.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!hao!seismo!rochester!quiroz
From: quiroz@rochester.UUCP (Cesar Quiroz)
Newsgroups: net.unix
Subject: Re: Shell Shock
Message-ID: <4514@rochester.UUCP>
Date: Sat, 8-Dec-84 15:56:56 EST
Article-I.D.: rocheste.4514
Posted: Sat Dec  8 15:56:56 1984
Date-Received: Mon, 10-Dec-84 02:47:08 EST
References: <24900002@siemens.UUCP>
Organization: U. of Rochester, CS Dept.
Lines: 22

> 
> Why is a 'shell' called a 'shell'?  What is it covering or protecting?
> 

	If you cannot guess, it obviously succeeds in hiding *whatever*
	was intended to remain hidden ...

	More seriously, any software interface can be seen as protecting
	somebody from having to deal with unnecessary details. You may 
	take the shell as built around the kernel, so it either protects 

	1.-  The user, from the low level weirdnesses of the kernel ...
	or
	2.-  The kernel, from the weirdness of its users :-)

	Now, how the metaphor of a shell *around* a kernel appeared 
	(I guess most people think of the command interpreter as built
	*on top*, not *around* the kernel) will certainly be a nice
	story to know, so let's encourage the First Born of UnixLand 
	to speak and enlighten the Net People.

Cesar