Re: unreadable XML proplists from drvctl(8)

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

On Fri, 20 Jan 2012 23:19:45 -0500
Matthew Mondor <mm_lists%pulsar-zone.net@localhost> wrote:

Various corrections, I should have re-read before posting (it's been a
long day):

> wd0.device-driver = wd
> wd0.device-unit = 0
> wd0.disk-info.geometry.cylenders-per-unit = 620181
> wd0.disk-info.geometry.sector-size = 512
> wd0.disk-info.geometry.sectors-per-track = 63
> wd0.disk-info.geometry.sectors-per-unit = 625142448
> wd0.disk-info.geometry.tracks-per-cylinder = 16
> wd0.type = ESDI
wd0.disk-info.type = ESDI

> Which could be generated with some function such as:
> 
> int prop_object_externalize_mib(const char *parent, prop_object_t, FILE *);
> 
> Where in this case <parent> could be "wd0"...  which if NULL would not
> include a top-level parent.  Yet now I'm wondering, would arrays be
> output such as [ 1 2 3 4 ... ] ?  There different various formats
> output by some multi-value sysctl klobs at the moment.
There are various formats output by the multi-value sysctl knobs at the
moment.

Thanks,
-- 
Matt