On 10/7/05, Ingo Adlung <[EMAIL PROTECTED]> wrote: > I beg you pardon, but i don't like the CP return code approach. While a VM > "widget" it is nonetheless a Linux module and should adhere to Linux return > code principles. But your point is well taken, it would certainly be > valuable > to describe how those get mapped to Linux values.
I beg two pardons, but you both may be missing a level of virtualization here. 1) The fact whether the Linux thing did what it should do for diag8 and did not suffer from problems getting the command to CP or obtain the result (out of memory, result truncated, etc) 2) The return code from CP on the command that you issued (e.g. userid not logged on, device not in directory) What a VM user would expect to get when he issues a CP command is two things: a) return code from CP b) output of the command It gets hairy when you mix the two. CMS Pipelines does this by a secondary output stream, but that is the kind of plumbing we don't have here. I expect it is rare that the Linux thing itself did not work (1) so we could stuff that in stderr. The CP return code (a) is useful for the user, and I was thinking you could have that one as the return code of the vmcp command. This gives an easy way to get hold of it as I learned. Rob -- Rob van der Heij rvdheij @ gmail.com ---------------------------------------------------------------------- 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
