|
On Fri, Jun 13, 2008 at 4:24 PM, Joseph Mack NA3T <jmack@xxxxxxxx> wrote:
> As a user, I'd prefer only one version of ipvsadm, which handles all the
> versions of the kernel (at least backwards compatible). Sure the code will
> have new stuff tacked on down the bottom for updates, but it will run the
> old kernels too. I'm not asking that backward compatibility be maintained -
> if it breaks, then people can go back and dig up an older version. I've
> asked Horms about this years ago and he preferred to have separate versions
> of ipvsadm for each kernel. However since the matter of ipvsadm has come up,
> I'm putting in my $0.02
Not sure if I understood completely what you wanted to have compatible
with what. My opinion is that we should only worry about not breaking
the kernel interface:
- have the old ipvsadm still work with the new kernel (by keeping the
old sockopt interface in parallel)
- have the new ipvsadm _only_ work with the new kernel (so we only
have to support netlink in the new ipvsadm)
That way the worst that can happen is people upgrading ipvsadm without
upgrading their kernel, but that shouldn't be our (or a big) problem.
Julius
--
Google Switzerland GmbH
--
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|
