On 07.07.2010 17:03, Sage Weil wrote:
, how does that work? This would divorce the kclient version from the
server side (which is basically already is, teh CEPH_VERSION* defines are
ignored by the kclient currently) and match it up with the kernel version.
For most people, that is just whatever upstream kernel they downloaded.
Is the goal just to make the standalone/backported code tell you which
version the client code corresponds to? If that's the case, I wonder the
defines should be generated exclusively in the backport branches of the
-standalone.git repo.
yes and yes - this is only needed in ceph-client-standalone.
fact is, that kernels smaller than 2.6.34 will be standard next years -
examples :
* Debian 5.0 2.6.26
* Ubuntu 10.04 LTS: 2.6.32
* Debian 6.0 2.6.32
* RHEL/CentOS 6 2.6.32
they all will need backported ceph modules. if there is no version
output in modinfo it will be hard to say which version is loaded.
- Thomas
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
