On Wed, May 2, 2012 at 7:25 PM, Edwin Beasant <[email protected]> wrote: > Hello there to all members! > As you may or may not be aware, after the Oracle acquisition of Sun, > many things changed, and I have ended up dealing extensively with ksh93 on > Solaris 11. > This used to be part of the more internal OS/network consolidation of code, > but recently i have moved it to the more third-party-friendly Userland code > consolidation. This code consolidation does things a little bit differently > to ON, with the result that it is much easier to work with and contribute to > the open-source community: > We have, over time, amassed a number of bug fixes for the 2011 release > of ast-base, some of which have been addressed in the 2012 release of the > ast-base package. I would like to be able to contribute any that you may > consider useful for integration into the codebase, if that is at all possible. > > I would also like to ask if it would be possible to get some pointers > for porting the ast-base package more properly to compile in 64 bit mode > under Solaris 11: Solaris 11 no longer boots a 32 bit kernel, and although it > can easily run the 32-bit version, a matching 64 bit version would be more > elegant and simpler to maintain long term
I don't understand. When Roland Mainz first integrated ksh93 into ON with PSARC 2006/550 it was explicitly, with *severe* resistance from Sun, done with a 64bit ksh93. /bin/sh remained a 32bit ksh93, which was safeguard against out of control memory allocations. A lot of fixes and porting was done to allow a 64bit ksh93 on Solaris, mainly because of the problematic environment and buggy compilers. What exactly did a move from ON to userland do to the project? Irek _______________________________________________ ast-developers mailing list [email protected] https://mailman.research.att.com/mailman/listinfo/ast-developers
