DHCPv6 on Linux with 4.3.0
bjorn at mork.no
Tue Mar 18 12:41:47 UTC 2014
Peter Rathlev <peter at rathlev.dk> writes:
> The executable should only enter that part of the code if SO_REUSEPORT
> is defined.
That's a bug.
You cannot determine runtime kernel features by simply looking at a
macro definition. Using headers from kernels newer than the one
currently running, or even installed, must be supported. Noone wants to
rebuild all their binaries when upgrading the kernel just to be sure
that all new features are enabled. Distros depend on this.
Moving binaries between systems with different kernel versions should
also be supported. You cannot expect users to rebuild a binary on every
system they install it on, and you cannot expect all systems to have the
same kernel version. Distros depend on this as well.
More information about the dhcp-users