What's a script?

[Karl F. Larsen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Steve Flynn wrote:
> On Mon, Jul 13, 2009 at 1:52 PM, Siggy Brentrup<ubuntu at psycho.i21k.de> wrote:
> 
>>> What if the first line of the script is
>>>
>>> #! /bin/ksh
>>>
>>> indicating that the following commands should be interepreted by the
>>> Korn Shell. Should it still be referred to as a "bash file" even if
>>> the script relies on specific builtin commands only implemented by the
>>> Korn shell?
>> Though correct, I think this doesn't clear things up for the OP.
>>
>> Since the early days of Unix[tm] files containing commands interpreted
>> by the shell (usually /bin/sh) were called "shell scripts". I just
>> can't recall if the term is already used in the faumous '70 article in
>> Bell Journal.  </nitpick>
> 
> I cmpletely agree. I've used the term shell script since I was first
> introduced to a VT-52 terminal around 1981. Calling a collection of
> commands a "bash file" is a misnomer which is what I was attempting to
> point out to K. F. Larsen.
> 
> 
	The term bash file comes from the similarity of it to a Windows bat
file. Both are executable and they do a useful thing but not a large
thing. I discovered the bash language to be superior to the Windows
version.

	Just a question. You were using a form of Unix in 1984. Linux came a
bit later.



73 Karl


- --

	Karl F. Larsen, AKA K5DI
	Linux User
	#450462   http://counter.li.org.
        Key ID = 3951B48D

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKWz6LNuSIOjlRtI0RAnwYAJoDD9I/aetOk+jrSz9YhFaJjMwPHgCfUAuA
345aOCzvqHK7xHA0zkrt0DI=
=aYPc
-----END PGP SIGNATURE-----