ksh as /bin/sh

AndrieDA daa at druxh.UUCP
Tue Jun 19 05:15:05 AEST 1984


<Sacrifice to the God of Net Bugs>

Installing "ksh" as "/bin/sh" may have a few problems.  We started
using "ksh" several months ago, and noted a few problems with
old shell scripts:
      > A common practice here, when needed, was to save the
	current working directory in the variable "PWD",
	and "cd" to it later.  "ksh" changes "PWD" every
	time "cd" is executed.  Important shell scripts should be
	checked for all such reserved words before the change.

While we have not installed "ksh" as "/bin/sh", setting the
variable "SHELL" in the environment simulates this.  We noted that
the performance of "make" was seriously affected (~20%) because every
time "make" started "ksh", "ksh" read in the startup file (set in "ENV").
We consider this unacceptible and will argue with our ComCenter
before allowing "ksh" to replace "/bin/sh".

Donald Andrie (druxh!daa)



More information about the Comp.unix mailing list