Xref: utzoo comp.unix.questions:14855 comp.bugs.sys5:1030 comp.unix.microport:3554
Path: utzoo!utgpu!watmath!att!tut.cis.ohio-state.edu!rpi!crdgw1!sungod!davidsen
From: davidsen@sungod.crd.ge.com (William Davidsen)
Newsgroups: comp.unix.questions,comp.bugs.sys5,comp.unix.microport
Subject: Re: ksh and sh
Message-ID: <1154@crdgw1.crd.ge.com>
Date: 11 Jul 89 13:18:30 GMT
References: <372@trevan.UUCP>
Sender: news@crdgw1.crd.ge.com
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Followup-To: comp.unix.questions
Organization: General Electric Corp. R&D, Schenectady, NY
Lines: 19

In article <372@trevan.UUCP> trevor@trevan.UUCP (trevor) writes:
| 
| 	Using Microport System V/AT and the korn shell for logins
| I have found if I execute /bin/sh and then execute pwd I get an
| error message pwd: cannot read .. . I suspect it is something to do with
                ^^^^^^^^^^^^^^^^^^^
	What are the permissions on the parent directory? May very well
be a legitimate problem (although a new one to me).

| 	Is there anything wrong in changing the name of ksh to sh or
| is there any incompatability.

  I think you will find that certain shell scripts won't work. I can't
remember if it was 'style' or some other text package, but it use "^"
instead of "|" for pipes. Keep /bin/sh handy by another name if you
rename. I just run ksh as login and leave sh as it came.
	bill davidsen		(davidsen@crdos1.crd.GE.COM)
  {uunet | philabs}!crdgw1!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me