> 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
Agreed, I should have talked to more VM persons about that. My decision was based on limitations in the linux kernel about getting guest real storage. Nevertheless, I have not seen a problem in real life with normal commands. If anybody faces a problem with the current buffering in vmcp it should be quite simple to change the userspace tool. The kernel part is very flexible about buffering. In other words, if you show me a scenario where vmcp fails, send a bug report and we will try to find a solution. > 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? Rob, using " like in vmcp "msg operator why does --buffer= does not work?" is the UNIX way to pass - or -- in parameters, so there is no problem. I hope that clarifies some of the questions. -- Mit freundlichen Grüßen / Best Regards / Un cordial saludo Christian Bornträger Linux Software Engineer zSeries Linux & Virtualization IBM Deutschland Entwicklung GmbH email: [EMAIL PROTECTED] Tel +49 7031 16 1975 ---------------------------------------------------------------------- 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
