Roland Mainz <roland.mainz at nrubsig.org> wrote:
> The only points of where we found scripts to fail are:
> - Two scripts (from opensource projects) were found which simply failed
> because they were using the the ksh93 builtin commands instead those
> from /usr/bin/. This is a Solaris-specific issue as those scripts fail
> because they depend on Solaris-specific features of the commands in
> /usr/bin/ while the ksh93 builtin commands are a POSIX implementation.
> This is clearly a portabilty issue in the script, however we fixed the
> problem in the meantime in ksh93.
Please try to be a bit more precise with this kind of descriptions.
The Solaris tools are also verified POSIX applications. If another program
does not implement the extensions from the Solaris tools, this is not a
problem of the Solaris tools.
I thought we did discuss this already.
> - Solaris |libc::wordexp()| does not work with ksh93 because Solaris ksh
> has a "secret", nonstandard option ("-^E") to call into Solaris ksh
> internal code. That has been addressed via creating a new version of
> |libc::wordexp()| (which also addresses multiple bugs in the old version
> of |libc::wordexp()|, including thread-safeness and improved security
> (the ksh93 used by the new |libc::wordexp()| version is run in
> restricted shell mode whzen doing the word expansion when WRE_NOCMD is
> requested))
This sounds good.
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
