Darren J Moffat wrote:
> James C. McPherson wrote:
>> Darren J Moffat wrote:
>>> James C. McPherson wrote:
>> ....
>>>> We've got a unique hash which identifies "binary X". We can create
>>>> a publishable mapping (ie, on sunsolve) between that hash and the
>>>> version of the source that it is based on.
>>>
>>> Why is it needed that you map a given random binary to source files ?
>>> The wsdiff tool may help here though.
>>
>> ignore wsdiff for the moment, and remember that not everybody
>> out there in Services-land cares about the source, just the
>> mapping of patch numbers to bugids. That is why we need it.
>
> Patch numbers to bugids is nothing to do with the source and sunsolve
> already provides that mapping via the patch readmes.
No, the mapping that is needed, I believe, is patch numbers to binary
objects. (I.e. what version of the nfs patch am I running _right now_?)
The ::showrev mdb output achieves this, but only for ON objects. There
is a compelling need to expand on this to a) make it available to 3rd
parties (both in and out of the WOS), b) make it documented, c) make it
easy for an end user to use.
Extended modinfo to read the data from an extended ELF section, and
providing a tool to populate that section during build time (perhaps a
new mcs flag?), would serve this need nicely.
-- Garrett
--
Garrett D'Amore, Principal Software Engineer
Tadpole Computer / Computing Technologies Division,
General Dynamics C4 Systems
http://www.tadpolecomputer.com/
Phone: 951 325-2134 Fax: 951 325-2191
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
