> > It's actually pdksh, wh/was +/- based off of ksh88, w/Korn's blessings, > > from back in day when ATT was less amenable to open source licenses. > > On Solaris /bin/ksh is ksh88+ >
If pdksh is compatible with the existing /sbin/sh, why not use that as its replacement? I've been using OpenBSD for a couple of years now and find it a perfectly usable shell. I'm afraid I'm no POSIX expert, so I'm not clear on whether the Bourne/Korn test below implies POSIX compatibility *only* if Korn-style is returned; but if using a POSIXy shell for /sbin/sh will cause widespread Windows Update-style brokenness then this should be a clear no-go. I'm just after a working backspace key (sorry Jörg - IBM keyboards may be ill-designed but I'm not seeing many other types in my server room or workshop), an editable command history, tab completion and possibly $(cmd) expansion. I think it would remove some of the "Gah!" factor for people coming to the operating system to have these usability features out-of-the-box. Chris > > > Now let us do a simple POSIX check that does _not_ rely on PATH > but starts up the way POSIX requires it: > > Linux: > getconf PATH > /bin:/usr/bin > bash-3.2$ PATH=`getconf PATH` > bash-3.2$ sh > sh-3.2$ sh -c 'foo=Bourne-style; echo Korn-style | read foo; eval echo $foo' > Bourne-style > > Solaris: > getconf PATH > /usr/xpg4/bin:/usr/ccs/bin:/usr/bin:/opt/SUNWspro/bin > $ PATH=`getconf PATH` > $ sh > $ sh -c 'foo=Bourne-style; echo Korn-style | read foo; eval echo $foo' > Korn-style >
_______________________________________________ opensolaris-discuss mailing list [email protected]
