|
Hi Wensong,
I think you missunderstand my suggestion. My suggestion is not to merge
the code. I think keeping ipvsadm-1.21 and ipvsadm-1.24 is fine.
Its a clean split. What I am talking about is allowing ipvsadm-1.24 to
exec ipvsadm-1.21 if it detects that is the right thing to do.
This is how modprobe and friends work, so you can have both the 2.6 and
2.4 generation tools installed. This is very useful for systems
that want to be able to run both a 2.4 and a 2.6 kernel. And is
simmilarly useful for packagers of distributions that have that
requirement.
Attached is a first cut at implementing this. I borrowed some code
from modprobe. And by default this new feature is not compiled in,
so you get the existing behaviour.
If it is compiled in, and you run ipvsadm on an a system running 2.4,
then it will try and exec PATH/ipvsadm-1.21, else gracefully fail. It
is up to the packager or sysadmin to install ipvsadm-1.21 into
PATH/ipvsadm-1.21 and compile ipvsadm-1.24 with this new feature
if they want this functionality. Again, I am thinking of package
maintainers.
many many thanks for your patch.
thinking of package maintainers, how can i name both packages?
ipvsadm2 for ipvsadm-1.24 and ipvsadm for ipvsadm-1.21?
Best regards,
Alejandro Mery
|
