fork
Executable do scripts

Let the os handle the shebang.
Dennis Ritchie has enumerated the advantages:

	1) It makes shell scripts more like real executable files,
	because they can be the subject of 'exec.'

	2) If you do a 'ps' while such a command is running, its real
	name appears instead of 'sh'.
	Likewise, accounting is done on the basis of the real name.

	3) Shell scripts can be set-user-ID.

	4) It is simpler to have alternate shells available;
	e.g. if you like the Berkeley csh there is no question about
	which shell is to interpret a file.

	5) It will allow other interpreters to fit in more smoothly.

	To take advantage of this wonderful opportunity,
	put

		#! /bin/sh

	at the left margin of the first line of your shell scripts.
	Blanks after ! are OK.  Use a complete pathname (no search is done).
	At the moment the whole line is restricted to 16 characters but
	this limit will be raised.