[EMAIL PROTECTED] wrote:
I agree with much of your post. Though rather than using the
execution PATH, why not
use the function call 'isatty' to change the behavior only in an
interactive session, and leave
scripts un-touched. As it this is already used by several commands in
Solaris, where is it a
problem with simple commands like df?
But that means that you can't easily write a script which expects
"new" output.
Ok before the call was for compatibility to not break existing
scripts. Now people
want to not break new scripts. Maybe we need a vote. Do we want -
a) Status Quo - Break new scripts, command line needed arguments for
humans.
b) Linux Version - Possibly breaks old scripts. Human friendly.
c) Alternative 1 - Old scripts work. New scripts need to be adjusted.
Human friendly output.
d) Alternative 2 - All of above. Binaries to suite everybody. New
scripts need to change for new path. Possible path conflicts.
A mixture of Paths and Environment variables fixes all peoples
problems. Diskspace is cheap!
e) Distribution dependant. i.e. Open Solaris keeps code for all
alternatives.
f) ???
Please make a choice. The solution is only code :)
Doug
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
