On 7/24/20 3:26 AM, Stefan Raspl wrote: > Hi Mark, Hi, Stefan,
> The problem with that is that you will get into trouble as soon as you > consider > 2nd-level installs where you have multiple guests and hypervisors to > display/query. We'd need multiple switches to address the different levels of > guests, and things get ugly pretty fast. Any ideas how to address that? I believe you're over-thinking this. Based on the origin of this thead and the responses to it, I would argue that people aren't interested in all that. They want to know: - What's *my* name - What's the name of the host system - What LPAR am I running in - What CPC am I running on That's why I said this: >> I can't say for sure >> if many people would be interested in finding out they're running 6 >> layers of virtualization deep and what each of those is. If someone does >> want that, they should speak up. -snip- > I would argue that if you want to script, what you really want is a front-end > in > qclib that can be accessed by scripts. Yes, querying qclib is certainly more > complicated than interacting with a command line tool like you layed out > above, > but unless we come up with a smart way for that tool's cmdline switches, it > will > likely not do what you need. I would say that the limited program I'm suggesting would do exactly what people want. Remember, I proposed this as a way for people to not have to write all sorts of REXX execs and bash scripts to figure out this small set of information. There may be others out there that are interested in much more than this, but so far they haven't said so (on this mailing list anyway). Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www2.marist.edu/htbin/wlvindex?LINUX-390
