On 10/6/05, Christian Borntraeger <[EMAIL PROTECTED]> wrote: > vmcp shows at least the same amout of information as cpint if you use > the default settings. But if 64kbytes are not enough you can force vmcp > to try allocation lets say 180kb of buffer - which is not possible with > cpint.
You could have asked "any VM person" on what the "right way" would be to address the buffer size. Yes, you want a way to set the buffer size, and otherwise for query commands you want to automagically extend the buffer and retry (but not for all commands, please). I personally would not have suggested an interface where the option can be confused with the actual command: vmcp msg operator why does --buffer= does not work? It's annoying to silently truncate the response, so should you not write something into stderr to point that out? A good default for the buffer appears to be 8K so you avoid CP lock and page in too many guest pages for the duration of the console function. And it tends to be large enough for casual usage. But I probably should shut up since I did not have a time to look at what you did, and I have not been able to see it before you did it. Aber sure, you're right. Everyone can do his own version rather than waste time to do one that fits many needs. Isn't that why we ended up with many incompatible Unix versions? 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
