[ksh93-integration-discuss] ksh93 incompatible with /bin/sh

[Chris Quenelle]

Since getting a developer preview 2 machine on our lab network
we noticed two things right away.

1. My shell initialization files produced error output now.
   (My default shell is /bin/sh)

2. Our Sun Studio testing shell scripts won't run anymore

Is there a web page someplace where we can track known issues
with converting other shell to be pointers to ksh93?
Is there a bug keyword to help track these issues?
If not, I'll start a wiki page when I get a chance to investigate 
the failures.  Our testing team needs to temporarily hack 
the /bin link to get our testing working on this platform,
so I'm not sure when I'll get a chance to investigate.

I think the issue that I ran into myself was related to the
number of kind of start up files that are sourced.
I think ksh93 (when run as 'sh') needs to only look in
the start up files that old-style /bin/sh looked in.

I think /bin/sh ignores the files listed in the ENV variable.
Does that sound right?

I think my startup files might depend on the fact that
ENV is ignored by my initial login shell.  

Also please note that you start talking about what is and
isn't "POSIX compatible", I'm only going to lose interest.
I really only care about how much hassle it is to
cope with changes in the Indiana environment.

--chris