Vladimir Marek wrote:
>> 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
> ?
and neither does the SCCS keywords when they were printed out as a
supposed version number.
> (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 ?
The /system/object/ objfs(7FS) helps with that. Tools like elfdump,
ctfdump, elfcmp all work on that and can be compared with what is on disk.
> Not that the current keywords would be always ideal solution, but it was
> at least something ...
It was a highly dangerous something though.
You aren't losing functionality, you are losing the illusion that you
ever had anything reliable.
> 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.
That suffers from the same problem as SCCS keywords. It only shows the
revision for a single file and that is utterly bogus and highly
misleading. Most modules aren't a single file.
--
Darren J Moffat
