On 01/21/10 06:29, Andras Spitzer wrote:
> Mike,
> 
> Thanks for the clarification. This question will be a bit off-topic, but as 
> far as I know today there is no possible way/command to view the 
> configurations stored on the SC, is this correct? We can add, remove, or 
> activate configurations on the SC, but we can't view their contents.

Yes, that's correct.

The format of the SP config's is a set of binary Machine
Descriptions (MDs) - the same format as what you'd get from
/dev/mdesc.  We have crude dump utilities for
the binaries, but no "pretty printer".  Nothing close
to something that could be given to a user.

And, FWIW, the autosave configs are stored as a set of
these MD binaries also (each with a 296 byte "autosave header"
prepended) at: /var/opt/SUNWldm/autosave-<config_name>/*
if you want to look at them.  Doing a 'strings' on the files may
give you some clue what the config looks like (e.g.
if you do 'strings hv-md.bin', the ldom domain names
are part of the output, usually at the end, I think).

If you're booted on a config, and it hasn't already been autosaved,
you can force an autosave of it by doing some innocuous change of
the config, like a set-var.

> If that's the case, at least do we have an RFE for this? That would be really 
> handy to see a config on the SC from the OS before I decide to select it and 
> boot it.

I'm not aware of an RFE for this.  And there isn't really an
easy way to grab a config off the SP to (say) a file on the
control domain, so you'd need that functionality also.
I vaguely remember an RFE for grabbing a copy of an SP config,
but I can't find it right now.

Mike

Reply via email to