src-test2/usr.sbin/ppp/Makefile, branch masterFreeBSD source treehttps://cgit-dev.freebsd.org/src-test2/atom?h=master2019-12-16T21:06:24ZRemove all the RELEASE_CRUNCH defines, they are useless.2019-12-16T21:06:24ZWarner Loshimp@FreeBSD.org2019-12-16T21:06:24Zurn:sha1:6ee8575cd71be8ba9ce88a28feddd523cac9f333
RELEASE_CRUNCH has been broken for a very long time. Remove the
last remants from the tree.
Retire the -DRELEASE_CRUNCH define.2019-07-12T06:19:25ZWarner Loshimp@FreeBSD.org2019-07-12T06:19:25Zurn:sha1:28c8ec2f7edccd280e5acce98d26f273cfa2a7f5
The RELEASE_CRUNCH ifdefs save about 100 bytes of text space. The
complexity is not worth it as they eliminate error messages.
Left the RELEASE_CRUNCH ifdef to eliminate a lot of stuff in place.
That saves an interesting amount of space and change some behaviors,
so absent a more detailed analysis, maintain the status quo.
Remove the NATM framework including the en(4), fatm(4), hatm(4), and2017-04-24T21:21:49ZBrooks Davisbrooks@FreeBSD.org2017-04-24T21:21:49Zurn:sha1:a7dc31283a053a6c0444813d1432fa83e6ccba9f
patm(4) devices.
Maintaining an address family and framework has real costs when we make
infrastructure improvements. In the case of NATM we support no devices
manufactured in the last 20 years and some will not even work in modern
motherboards (some newer devices that patm(4) could be updated to
support apparently exist, but we do not currently have support).
With this change, support remains for some netgraph modules that don't
require NATM support code. It is unclear if all these should remain,
though ng_atmllc certainly stands alone.
Note well: FreeBSD 11 supports NATM and will continue to do so until at
least September 30, 2021. Improvements to the code in FreeBSD 11 are
certainly welcome.
Reviewed by: philip
Approved by: harti
Fix build of ppp when WITHOUT_PAM is set2016-07-04T21:18:57ZBaptiste Daroussinbapt@FreeBSD.org2016-07-04T21:18:57Zurn:sha1:7059692f3a581b83c9a816f813ccca7c76386e48
PR: 210658
Reported by: madpilot
Tested by: madpilot
Approved by: re@ (kib)
Revert r301137 and r301163, and implement a correct fix2016-06-01T20:44:28ZGlen Barbergjb@FreeBSD.org2016-06-01T20:44:28Zurn:sha1:ea580d0b45f1ab5573c1fc1221a1b1629ef9fa49
for the CONFS issue with dma.conf and ppp.conf.
Thank you very much to Bryan Drewery for looking into the
problem and providing this fix.
Pointyhat: gjb
Sponsored by: The FreeBSD Foundation
Revert r289096:2016-06-01T16:45:08ZGlen Barbergjb@FreeBSD.org2016-06-01T16:45:08Zurn:sha1:efe50fa18a1cfc24942dc61c2bbad17d789392ff
Files listed in 'CONFS' are not properly included in new
installations (missing from base.txz), for reasons I still
do not fully understand.
This reverts the change excluding /etc/ppp/ppp.conf from
a new installation. /etc/dma/dma.conf is also affected,
but requires a different solution, still being investigated.
Reported by: Ben Woods
Sponsored by: The FreeBSD Foundation
Use existing CONFDIR instead of adding a new CONFIGDIR2015-10-11T19:25:39ZBaptiste Daroussinbapt@FreeBSD.org2015-10-11T19:25:39Zurn:sha1:f98f68bd504c0e53fd75bd3b5a102ddf4afe9393
Reported by: jbeich
Install bsd.confs.mk2015-10-10T10:48:09ZBaptiste Daroussinbapt@FreeBSD.org2015-10-10T10:48:09Zurn:sha1:2c9976e37efeae3b6ab5d59259465bc3e1be244c
Rename ETCDIR into CONFIGDIR to avoid conflicts with the ports tree
Move ppp.conf into the ppp sources2015-10-09T23:57:07ZBaptiste Daroussinbapt@FreeBSD.org2015-10-09T23:57:07Zurn:sha1:23c7816115e1293f38444fd562c8651ef1bc5bcdConditionalize building radius support into libpam, ppp, etc via2015-02-04T06:53:45ZEnji Cooperngie@FreeBSD.org2015-02-04T06:53:45Zurn:sha1:31a741f47311cb5a2f1d4ef2a2b9067a8dcb7cb6
MK_RADIUS_SUPPORT
MFC after: 1 week
Sponsored by: EMC / Isilon Storage Division