> There are much better and more reliable tools for determining which
> revision of a particular binary you have than source keywords. They
> include (either on their own or in combination) but are not limited to:
> pkgchk, pkg(5) [IPS], digest, md5sum, bart, showrev, elfsign, the online
> fingerprint database.
Those won't show which module is actually loaded into kernel, will they
? (I don't know bart and online fingerprint database). I.e. you have
crash dump, how can you find out which module version was loaded ?
Not that the current keywords would be always ideal solution, but it was
at least something ...
Wouldn't it be solution to use hg log, something like
hg log -l 1 --template '{node|short}\n' file
It prints node id of last commit which changed given file (or even
directory !). And it's much faster than 'hg id'. The only disadvantage I
can see is that you can't find which node id is older than other just by
looking at it.
--
Vlad
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 193 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/scm-migration-dev/attachments/20080703/072681e4/attachment.bin>
