Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: unreadable XML proplists from drvctl(8)

On Wed, Jan 18, 2012 at 09:22:56PM +0200, Alan Barrett wrote:
> On Mon, 16 Jan 2012, Paul Goyette wrote:
> >I had included a sample of the new output from 'drvctl -p' (show 
> >propery dictionary) which includes the new information.  Here it is 
> >again:
> >
> ># drvctl -p atabus0
> >Properties for device `atabus0':
> ><?xml version="1.0" encoding="UTF-8"?>
> ><!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" 
> >"";>
> ><plist version="1.0">
> ><dict>
>  [snip unreadable XML]
> Why do we have a command that outputs XML proplists, without the 
> option of a human readable alternative?  When XML proplists were 
> introduced some years ago, we were promised that they would not be 
> exposed in user interfaces.  This seems to violate that promise.

Can we get 'drvctl -r xyzbus0' to return an error if more then one
property is available and return the supported values at the same
time too, in a human readable output?

That would make it more easier to use it.


Home | Main Index | Thread Index | Old Index