Seconded. This goes to Keith Bierman's discussion about large Linux customers moving to Solaris. Everything has to compile/build/work seamlessly for those kind of environments to contemplate the move. Inevitably things go wrong during migrations of that sort...it seems to me you don't do yourself a favor by choosing a migration that's you know is going to hit significant roadblocks ahead of time.
-J On 8/7/07, Chris Pickett <[EMAIL PROTECTED]> wrote: > On 8/6/07, Josh Hurst <[EMAIL PROTECTED]> wrote: > > On 8/6/07, I. Szczesniak <[EMAIL PROTECTED]> wrote: > > > On 8/6/07, Richard Lowe <[EMAIL PROTECTED]> wrote: > > > > Roland's current work is to integrate ksh93 as ksh93. He also has a > > > > build flag to build it as 'ksh'. > > > > > > I hope Indiana is going to set this build flag to 'ksh' by default. > > > > +1 > > +1 > > I think we have a bigger problem than /bin/ksh: Does Indiana or > Opensolaris want to address the problem that Opensolaris still uses > the original bourne shell as /bin/sh? Most modern Unices use either > bash or ksh as /bin/sh, creating porting problems for Opensolaris > developers because basics like functions with separate scope, arrays > or $() aren't working in scripts and makefiles. This really needs to > be a top priority. > > Chris > -- > ^---^ > (@)v(@) Chris Pickett > | / IT consultant > ===m==m=== [EMAIL PROTECTED] > _______________________________________________ > indiana-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/indiana-discuss > _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
