Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site druxh.UUCP Path: utzoo!watmath!clyde!floyd!vax135!houxz!houxm!ihnp4!drutx!druxh!daa From: daa@druxh.UUCP (AndrieDA) Newsgroups: net.unix Subject: Re: ksh as /bin/sh Message-ID: <770@druxh.UUCP> Date: Mon, 18-Jun-84 15:15:05 EDT Article-I.D.: druxh.770 Posted: Mon Jun 18 15:15:05 1984 Date-Received: Thu, 21-Jun-84 00:53:25 EDT Organization: AT&T Information Systems Laboratories, Denver Lines: 19Installing "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)