On Thursday, 10/13/2005 at 08:53 ZE8, John Summerfied <[EMAIL PROTECTED]> wrote:
> Are people happy that they will not be able to use these functions from > the commandline or from a shell script? The earlier suggestion (not > mine) was to do it in a posix shell. But it doesn't make sense to have all of the diagnose functions available from the command line anyway. And if a script greps stdout, and it decides that the user should see the output, it can write the output back to stdout itself. (I do this all the time in REXX execs - handle the return codes I can deal with myself and dump to the console if I don't recognize it. Is Linux so different?) vmcp is a Linux command interface to a CP command interface (diag 8). The rest of the diagnose functions are programming interfaces of one sort or another. This isn't some new limitation being proposed; this is inherent in the limitations of the [e.g. bash] shell scripting language, is it not? I can certainly envision some userspace apps in the package that do common things with those diags, making them useful in a command environment, but I don't think we need a command interface to the diags themselves. Integrate some into /proc and others into /dev. Add the userspace apps on top. Rob's analysis seemed right on the money to me. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
