DIRDEPS_BUILD: Update dependencies.Sponsored by: Dell EMC Isilon
usr.sbin: normalize paths using SRCTOP-relative paths or :H when possibleThis simplifies make logic/outputMFC after: 1 monthSponsored by: Dell EMC Isilon
META MODE: Update dependencies with 'the-lot' and add missing directories.This is not properly respecting WITHOUT or ARCH dependencies in target/.Doing so requires a massive effort to rework targe
META MODE: Update dependencies with 'the-lot' and add missing directories.This is not properly respecting WITHOUT or ARCH dependencies in target/.Doing so requires a massive effort to rework targets/ to do so. Abetter approach will be to either include the SUBDIR Makefiles directlyand map to DIRDEPS or just dynamically lookup the SUBDIR. These losethe benefit of having a userland/lib, userland/libexec, etc, though andresults in a massive package. The current implementation of targets/ isvery unmaintainable.Currently rescue/rescue and sys/modules are still not connected.Sponsored by: EMC / Isilon Storage Division
show more ...
Convert usr.sbin to LIBADDReduce overlinking
Promote libevent to lib/ level and fold ftp-proxy into its parent Makefile.This allows us to use libevent for other application in the future.For now libevent is still INTERNALLIB and no shared li
Promote libevent to lib/ level and fold ftp-proxy into its parent Makefile.This allows us to use libevent for other application in the future.For now libevent is still INTERNALLIB and no shared library is installed.MFC after: 1 month
Revert r267233 for now. PIE support needs to be reworked.1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries.2. Another 40% is fixed by generati
Revert r267233 for now. PIE support needs to be reworked.1. 50+% of NO_PIE use is fixed by adding -fPIC to INTERNALLIB and other build-only utility libraries.2. Another 40% is fixed by generating _pic.a variants of various libraries.3. Some of the NO_PIE use is a bit absurd as it is disabling PIE (and ASLR) where it never would work anyhow, such as csu or loader. This suggests there may be better ways of adding support to the tree. Many of these cases can be fixed such that -fPIE will work but there is really no reason to have it in those cases.4. Some of the uses are working around hacks done to some Makefiles that are really building libraries but have been using bsd.prog.mk because the code is cleaner. Had they been using bsd.lib.mk then NO_PIE would not have been needed.We likely do want to enable PIE by default (opt-out) for non-tree consumers(such as ports). For in-tree though we probably want to only enable PIE(opt-in) for common attack targets such as remote service daemons and setuidutilities. This is also a great performance compromise since ASLR is expectedto reduce performance. As such it does not make sense to enable it in allutilities such as ls(1) that have little benefit to having it enabled.Reported by: kib
In preparation for ASLR [1] support add WITH_PIE to support building with -fPIE.This is currently an opt-in build flag. Once ASLR support is ready and stableit should changed to opt-out and be ena
In preparation for ASLR [1] support add WITH_PIE to support building with -fPIE.This is currently an opt-in build flag. Once ASLR support is ready and stableit should changed to opt-out and be enabled by default along with ASLR.Each application Makefile uses opt-out to ensure that ASLR will be enabled bydefault in new directories when the system is compiled with PIE/ASLR. [2]Mark known build failures as NO_PIE for now.The only known runtime failure was rtld.[1] http://www.bsdcan.org/2014/schedule/events/452.en.htmlSubmitted by: Shawn Webb <[email protected]>Discussed between: des@ and Shawn Webb [2]
o Create directory sys/netpfil, where all packet filters should reside, and move there ipfw(4) and pf(4).o Move most modified parts of pf out of contrib.Actual movements:sys/contrib/pf/net/*.
o Create directory sys/netpfil, where all packet filters should reside, and move there ipfw(4) and pf(4).o Move most modified parts of pf out of contrib.Actual movements:sys/contrib/pf/net/*.c -> sys/netpfil/pf/sys/contrib/pf/net/*.h -> sys/net/contrib/pf/pfctl/*.c -> sbin/pfctlcontrib/pf/pfctl/*.h -> sbin/pfctlcontrib/pf/pfctl/pfctl.8 -> sbin/pfctlcontrib/pf/pfctl/*.4 -> share/man/man4contrib/pf/pfctl/*.5 -> share/man/man5sys/netinet/ipfw -> sys/netpfil/ipfwThe arguable movement is pf/net/*.h -> sys/net. There arefuture plans to refactor pf includes, so I decided not tobreak things twice.Not modified bits of pf left in contrib: authpf, ftp-proxy,tftp-proxy, pflogd.The ipfw(4) movement is planned to be merged to stable/9,to make head and stable match.Discussed with: bz, luigi
Update packet filter (pf) code to OpenBSD 4.5.You need to update userland (world and ports) toolsto be in sync with the kernel.Submitted by: mlaierSubmitted by: eri
Add missing newline in last line of file.Uncovered via: fromcvs vs. svnApproved by: ed (co-mentor)
The last big commit: let usr.sbin/ use WARNS=6 by default.
Link pf 4.1 to the build: - move ftp-proxy from libexec to usr.sbin - add tftp-proxy - new altq mtag linkApproved by: re (kensmith)