[OpenAFS-devel] afsd & libafs module version checking??
Russ Allbery
rra@stanford.edu
Wed, 14 Dec 2005 13:44:21 -0800
Troy Benjegerdes <hozer@hozed.org> writes:
> How about we just dump the CML version as informative info. I have a
> patch available here:
> http://source.scl.ameslab.gov/hg/openafs-misc-fixes?cmd=changeset;node=df929d0767ee2d295c4b0c3139a0aebd9dc37fae
> that does this:
> With matching versions:
> MODLOAD-2.6.14-1-powerpc-SP# ../../afsd/afsd
> afsd: All AFS daemons started.
> With mismatched versions:
> MODLOAD-2.6.14-1-powerpc-SP# insmod ./libafs.ko
> MODLOAD-2.6.14-1-powerpc-SP# ../../afsd/afsd
> afsd: @(#) OpenAFS 1.4.1-rc2 built 2005-12-13 hg-b95a152f628d+ tip
> libafs: @(#) OpenAFS 1.4.1-rc2 built 2005-12-14 hg-b95a152f628d+ tip
> afsd: All AFS daemons started.
> If we add this extra informative information, it will be much easier to
> figure out what people are actually running.. In my case, I'm going to
> keep this in my mercurial tree so I know exactly what source code was
> used to create the binaries.
I'd rather see that data go into syslog than to standard output, but other
than that, it seems like a reasonable idea to me. Note that there will
frequently be a version mismatch if you're using the Debian packages since
the build times will always be different.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>