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.
Patches really have very little to do with putbacks/changesets because
of the way patch breakdown and rollup occurs.
Sun already has the finger print database which maps the binaries
going back all the way to Solaris 2.0 and patches to MD5 hashes.
I was wondering when you'd bring that up.
As I mentioned to Rich Lowe on irc a little while ago, this has
turned into one of those "oh, we've got a nifty tool to do that
already ... just nobody used it" kinda scenarios. Time, I think,
for some evangelising on the fingerprint db.
Maybe if the link on the front page of the internal and external
sunsolve for it was moved from the security section people might use it
more :-)
--
Darren J Moffat
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
