Which policy, which tools? Could you please a bit clearer? Jenny
On Thu, Mar 18, 2010 at 4:53 PM, Stefan Teleman <stefan.teleman at sun.com> wrote: > This project raises a concern in my mind with respect to a very old and > generally accepted UNIX architectural principle: > > "Tools, Not Policy". > > If i understand it correctly, this case effectively vacates the principle > stated above, and replaces it with its exact opposite: > > "Policy, Not Tools". > > Because the only possible rationale for having /usr/gnu/bin/grep > transparently and silently replaced by a shell builtin grep is as a result > of some mandatory policy in effect, which would trump explicit user > selection. > > It would be very helpful if the project team would kindly explain how it > intends to address the architectural concern above, and also how it intends > to mitigate the proliferation of userland commands with identical names, but > providing, in many cases, different semantics. > > Thank you. > > --Stefan > > ------ > > Garrett D'Amore - sun microsystems wrote: > >> This project is an amendment to the Korn Shell 93 Integration project >> (PSARC/2006/550 and PSARC/2007/035, PSARC/2008/094, PSARC/2008/344 >> and PSARC/2008/589) specifying the following additional >> interfaces: >> Addition of /usr/gnu/bin, /usr/xpg4/bin and /usr/bin built in >> mappings in ksh93 > > > > -- > Stefan Teleman > Oracle Corporation > stefan.teleman at Sun.COM > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org > -- Jennifer Pioch, Uni Frankfurt
