On Aug 7, 2007, at 10:53 AM, Chris Pickett wrote: > On 8/6/07, Keith Bierman <[EMAIL PROTECTED]> wrote: >> >> On Aug 6, 2007, at 3:36 PM, Mark Phalan wrote: >> That way, Solaris.Next could still have ksh88, and usual utilities >> and etc. and users who set the right configuration option >> (systemwide, per user, whatever, defer to PSARC) would be able to >> accept Indiana interoperability nearly, but not quite transparently. > > I don't understand why you want to keep ksh88 around. Could you > explain why you want to keep 20 year old and unmaintained software > around? After reading lots of community messages I think the opinion > outside Sun is that /bin/ksh and /bin/sh need to be updated ASAP. > Otherwise Indiana will not be able to compete with other open source > operating system projects such as Linux.
Being able to run existing Solaris scripts is a requirement for the standard Solaris distribution. That they depend on a shell that is otherwise an orphan isn't really an issue. Write once, run forever. It's more than just a motto ;> But for those that aren't trying to run old scripts, it's certainly an issue. Hence the discussion to date ; Keith H. Bierman [EMAIL PROTECTED] | [EMAIL PROTECTED] Strategic Engagement Team | AIM: kbiermank <speaking for myself, not Sun*> Copyright 2007 _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
