61cf0dc9a0
The linux targets have become more than confusing over time. We used to have "linux2628" to match the features available in kernels 2.6.28 and above, without consideration for the libc, and due to many new features appearing later in kernels, some other options were added that are not enabled by default in linux2628, so this target doesn't make any sense anymore. The older ones (linux 2.2, linux 2.4, ...) do not make sense either since these versions are not supported anymore. Let's clean things up by creating a new "linux-glibc" target that matches what is available by default on Linux kernels and glibc present on supported distros at the time of release. Other libc implementation may use a custom or generic target or be added later if needed. All the older linux targets were removed. |
||
---|---|---|
.github/ISSUE_TEMPLATE | ||
contrib | ||
doc | ||
ebtree | ||
examples | ||
include | ||
reg-tests | ||
scripts | ||
src | ||
tests | ||
.cirrus.yml | ||
.gitignore | ||
.travis.yml | ||
CHANGELOG | ||
CONTRIBUTING | ||
INSTALL | ||
LICENSE | ||
MAINTAINERS | ||
Makefile | ||
README | ||
ROADMAP | ||
SUBVERS | ||
VERDATE | ||
VERSION |
README
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)