<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>0f0d52fd - sbin: build ping if at least one of INET &amp; INET6 is enabled</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#0f0d52fd</link>
        <description>sbin: build ping if at least one of INET &amp; INET6 is enabledIt does not build (and serves no purpose) if neither is true (i.e.,building WITHOUT_INET and WITHOUT_INET6).  Also add an explicit errorin ping to make this case clear.PR:		260082Sponsored by:	The FreeBSD Foundation(cherry picked from commit a4ef9e58bc0c07110a54ba0fa88eb118c5377e6f)OptionalObsoleteFiles: remove ping with INET &amp; INET6 disabledReported by:	kevansFixes:		a4ef9e58bc0c (&quot;sbin: build ping if at least one of...&quot;)Sponsored by:	The FreeBSD Foundation(cherry picked from commit 0179739a0096c62cb3c9665d68246046255ab849)

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Sun, 28 Nov 2021 17:50:13 +0000</pubDate>
        <dc:creator>Ed Maste &lt;emaste@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>3cde9171 - Merge ping6 to ping</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#3cde9171</link>
        <description>Merge ping6 to pingThere is now a single ping binary, which chooses to use ICMP or ICMPv4based on the -4 and -6 options, and the format of the address.Submitted by:	J&#225;n Su&#269;an &lt;sucanjan@gmail.com&gt;Sponsored by:	Google LLC (Google Summer of Code 2019)MFC after:	NeverDifferential Revision:	https://reviews.freebsd.org/D21377

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Thu, 26 Nov 2020 04:29:30 +0000</pubDate>
        <dc:creator>Alan Somers &lt;asomers@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>f5a95d9a - Remove NAND and NANDFS support</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#f5a95d9a</link>
        <description>Remove NAND and NANDFS supportNANDFS has been broken for years. Remove it. The NAND drivers thatremain are for ancient parts that are no longer relevant. They arepolled, have terrible performance and just for ancient armhardware. NAND parts have evolved significantly from this early workand little to none of it would be relevant should someone need toupdate to support raw nand. This code has been off by default foryears and has violated the vnode protocol leading to panics since itwas committed.Numerous posts to arch@ and other locations have found no actual usersfor this software.Relnotes:	YesNo Objection From: arch@Differential Revision: https://reviews.freebsd.org/D20745

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Tue, 25 Jun 2019 04:50:09 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>eb12b8ea - Add verifying manifest loader for mac_veriexec</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#eb12b8ea</link>
        <description>Add verifying manifest loader for mac_veriexecThis tool will verify a signed manifest and load contents intomac_veriexec for storageSponsored by:	Juniper NetworksDifferential Revision:	D16575

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Tue, 26 Feb 2019 06:17:23 +0000</pubDate>
        <dc:creator>Simon J. Gerraty &lt;sjg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>b252313f - New pfil(9) KPI together with newborn pfil API and control utility.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#b252313f</link>
        <description>New pfil(9) KPI together with newborn pfil API and control utility.The KPI have been reviewed and cleansed of features that were plannedback 20 years ago and never implemented.  The pfil(9) internals havebeen made opaque to protocols with only returned types and functiondeclarations exposed. The KPI is made more strict, but at the same timemore extensible, as kernel uses same command structures that userlandioctl uses.In nutshell [KA]PI is about declaring filtering points, declaringfilters and linking and unlinking them together.New [KA]PI makes it possible to reconfigure pfil(9) configuration:change order of hooks, rehook filter from one filtering point to adifferent one, disconnect a hook on output leaving it on input only,prepend/append a filter to existing list of filters.Now it possible for a single packet filter to provide multiple rulesetsthat may be linked to different points. Think of per-interface ACLs inCisco or Juniper. None of existing packet filters yet support that,however limited usage is already possible, e.g. default ruleset canbe moved to single interface, as soon as interface would pride theirfiltering points.Another future feature is possiblity to create pfil heads, that providenot an mbuf pointer but just a memory pointer with length. That wouldallow filtering at very early stages of a packet lifecycle, e.g. whenpacket has just been received by a NIC and no mbuf was yet allocated.Differential Revision:	https://reviews.freebsd.org/D18951

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Thu, 31 Jan 2019 23:01:03 +0000</pubDate>
        <dc:creator>Gleb Smirnoff &lt;glebius@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>5952343e - Rename be(1) to bectl(8); continues to live in /sbin</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#5952343e</link>
        <description>Rename be(1) to bectl(8); continues to live in /sbinDiscussed with:	rpokala, allanjude

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Tue, 24 Jul 2018 13:21:44 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>28f16a0f - Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-head</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#28f16a0f</link>
        <description>Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-head

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Tue, 24 Jul 2018 13:17:40 +0000</pubDate>
        <dc:creator>Kyle Evans &lt;kevans@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>aa571745 - Makefiles: remove outdated comments</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#aa571745</link>
        <description>Makefiles: remove outdated comments

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Sun, 24 Jun 2018 09:39:40 +0000</pubDate>
        <dc:creator>Eitan Adler &lt;eadler@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>f0f8a1af - NVME support is only for x86 and powerpc64.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#f0f8a1af</link>
        <description>NVME support is only for x86 and powerpc64.Implement MK_NVME now that the expression for where NVMe iscomplicated. Default it to &quot;yes&quot; for x86 and powerpc64 andno everywhere else. Use it in camcontrol to define WITH_NVMEfor those platforms where we support nvme.This should fix the newly introduced nvme files to camcontrolwhich were building everywhere.Pointy Hat To: impSponsored by: Netflix

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Thu, 14 Jun 2018 01:15:19 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>590682b6 - Move devmatch to sbin from usr/sbin.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#590682b6</link>
        <description>Move devmatch to sbin from usr/sbin.Since we want to use devmatch in context before a split /,/usr systemhas mounted /usr, move devmatch to /sbin.Sponsored by: Netflix

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Mon, 12 Feb 2018 14:44:21 +0000</pubDate>
        <dc:creator>Warner Losh &lt;imp@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>93b09f58 - Remove badsect(8).</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#93b09f58</link>
        <description>Remove badsect(8).Failure modes of the modern (that is, produced in the last 25 years)hard drives and SSDs made the utility outdated.  Since the kernelinterface to support it was removed in r324853, cut the userspaceremnants as well.Discussed with:	bde (who does not like the removal)Sponsored by:	The FreeBSD FoundationMFC after:	2 weeks

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Sun, 05 Nov 2017 22:00:54 +0000</pubDate>
        <dc:creator>Konstantin Belousov &lt;kib@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>01df7d10 - Remove SUBDIR ordering/uniquifying in *bin/Makefile</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#01df7d10</link>
        <description>Remove SUBDIR ordering/uniquifying in *bin/MakefileAfter the addition of SUBDIR.yes, uniquifying/ordering the SUBDIRs doesn&apos;tmake a whole lot of sense, and it&apos;s in effect a half measure.Ordering SUBDIR (after adding SUBDIR.yes to it) in bsd.subdir.mk is aseparate change that warrants more discussion/testing, because whilethe SUBDIR_PARALLEL work largely fixed dependency ordering for SUBDIRs,there might be downstream FreeBSD consumers that rely on the SUBDIRordering.MFC after:	2 monthsReviewed by:	bdreweryDifferential Revision:	D11398

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Thu, 06 Jul 2017 04:15:30 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>a7dc3128 - Remove the NATM framework including the en(4), fatm(4), hatm(4), and</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#a7dc3128</link>
        <description>Remove the NATM framework including the en(4), fatm(4), hatm(4), andpatm(4) devices.Maintaining an address family and framework has real costs when we makeinfrastructure improvements.  In the case of NATM we support no devicesmanufactured in the last 20 years and some will not even work in modernmotherboards (some newer devices that patm(4) could be updated tosupport apparently exist, but we do not currently have support).With this change, support remains for some netgraph modules that don&apos;trequire 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 atleast September 30, 2021.  Improvements to the code in FreeBSD 11 arecertainly welcome.Reviewed by:	philipApproved by:	harti

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Mon, 24 Apr 2017 21:21:49 +0000</pubDate>
        <dc:creator>Brooks Davis &lt;brooks@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>480f31c2 - Add support for encrypted kernel crash dumps.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#480f31c2</link>
        <description>Add support for encrypted kernel crash dumps.Changes include modifications in kernel crash dump routines, dumpon(8) andsavecore(8). A new tool called decryptcore(8) was added.A new DIOCSKERNELDUMP I/O control was added to send a kernel crash dumpconfiguration in the diocskerneldump_arg structure to the kernel.The old DIOCSKERNELDUMP I/O control was renamed to DIOCSKERNELDUMP_FREEBSD11 forbackward ABI compatibility.dumpon(8) generates an one-time random symmetric key and encrypts it usingan RSA public key in capability mode. Currently only AES-256-CBC is supportedbut EKCD was designed to implement support for other algorithms in the future.The public key is chosen using the -k flag. The dumpon rc(8) script can do thisautomatically during startup using the dumppubkey rc.conf(5) variable.  Once thekeys are calculated dumpon sends them to the kernel via DIOCSKERNELDUMP I/Ocontrol.When the kernel receives the DIOCSKERNELDUMP I/O control it generates a randomIV and sets up the key schedule for the specified algorithm. Each time thekernel tries to write a crash dump to the dump device, the IV is replaced bya SHA-256 hash of the previous value. This is intended to make a possibledifferential cryptanalysis harder since it is possible to write multiple crashdumps without reboot by repeating the following commands:# sysctl debug.kdb.enter=1db&gt; call doadump(0)db&gt; continue# savecoreA kernel dump key consists of an algorithm identifier, an IV and an encryptedsymmetric key. The kernel dump key size is included in a kernel dump header.The size is an unsigned 32-bit integer and it is aligned to a block size.The header structure has 512 bytes to match the block size so it was required tomake a panic string 4 bytes shorter to add a new field to the header structure.If the kernel dump key size in the header is nonzero it is assumed that thekernel dump key is placed after the first header on the dump device and the coredump is encrypted.Separate functions were implemented to write the kernel dump header and thekernel dump key as they need to be unencrypted. The dump_write function encryptsdata if the kernel was compiled with the EKCD option. Encrypted kernel textdumpsare not supported due to the way they are constructed which makes it impossibleto use the CBC mode for encryption. It should be also noted that textdumps don&apos;tcontain sensitive data by design as a user decides what information should bedumped.savecore(8) writes the kernel dump key to a key.# file if its size in the headeris nonzero. # is the number of the current core dump.decryptcore(8) decrypts the core dump using a private RSA key and the kerneldump key. This is performed by a child process in capability mode.If the decryption was not successful the parent process removes a partiallydecrypted core dump.Description on how to encrypt crash dumps was added to the decryptcore(8),dumpon(8), rc.conf(5) and savecore(8) manual pages.EKCD was tested on amd64 using bhyve and i386, mipsel and sparc64 using QEMU.The feature still has to be tested on arm and arm64 as it wasn&apos;t possible to runFreeBSD due to the problems with QEMU emulation and lack of hardware.Designed by:	def, pjdReviewed by:	cem, oshogbo, pjdPartial review:	delphij, emaste, jhb, kibApproved by:	pjd (mentor)Differential Revision:	https://reviews.freebsd.org/D4712

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Sat, 10 Dec 2016 16:20:39 +0000</pubDate>
        <dc:creator>Konrad Witaszczyk &lt;def@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>97371ba2 - zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#97371ba2</link>
        <description>zfsbootcfg: a simple tool to set next boot (one time) options for zfsboot(gpt)zfsboot will read one-time boot directives from a special ZFS poolarea.  The area was previously described as &quot;Boot Block Header&quot;, butcurrently it is know as Pad2, marked as reserved and is zeroed out onpool creation.  The new code interprets data in this area, if any, usingthe same format as boot.config.  The area is immediately wiped out.Failure to parse the directives results in a reboot right after thecleanup.  Otherwise the boot sequence proceeds as usual.zfsbootcfg writes zfsboot arguments specified on its command line to thePad2 area of a disk identified by vfs.zfs.boot.primary_pool andvfs.zfs.boot.primary_vdev kenv variables that are set by loader duringboot.  Please see the manual page for more.Thanks to all who reviewed, contributed and made suggestions!  There aremany potential improvements to the feature, please see the review fordetails.Reviewed by:	wblock (docs)Discussed with:	jhb, tsoomeMFC after:	3 weeksRelnotes:	yesDifferential Revision: https://reviews.freebsd.org/D7612

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Sat, 29 Oct 2016 14:09:32 +0000</pubDate>
        <dc:creator>Andriy Gapon &lt;avg@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>014db25b - Update ^/vendor/NetBSD/tests/dist to a more recent snapshot</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#014db25b</link>
        <description>Update ^/vendor/NetBSD/tests/dist to a more recent snapshotPulled on &quot;Thu Aug 11 18:01:19 PDT 2016&quot;

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Fri, 12 Aug 2016 01:05:07 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>c501d73c - Convert casperd(8) daemon to the libcasper.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#c501d73c</link>
        <description>Convert casperd(8) daemon to the libcasper.After calling the cap_init(3) function Casper will fork from it&apos;s originalprocess, using pdfork(2). Forking from a process has a lot of advantages:1. We have the same cwd as the original process.2. The same uid, gid and groups.3. The same MAC labels.4. The same descriptor table.5. The same routing table.6. The same umask.7. The same cpuset(1).From now services are also in form of libraries.We also removed libcapsicum at all and converts existing program using Casperto new architecture.Discussed with:		pjd, jonathan, ed, drysdale@google.com, emastePartially reviewed by:	drysdale@google.com, bdreweryApproved by:		pjd (mentor)Differential Revision:	https://reviews.freebsd.org/D4277

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Thu, 25 Feb 2016 18:23:40 +0000</pubDate>
        <dc:creator>Mariusz Zaborski &lt;oshogbo@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>6f42d16f - Convert to SUBDIR.yes format.</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#6f42d16f</link>
        <description>Convert to SUBDIR.yes format.Reviewed by:	impSponsored by:	EMC / Isilon Storage DivisionDifferential Revision:	https://reviews.freebsd.org/D4182

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Wed, 18 Nov 2015 17:52:38 +0000</pubDate>
        <dc:creator>Bryan Drewery &lt;bdrewery@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>87d352d5 - Remove duplicate MK_ISCSI block and sort the conditional blocks so this error</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#87d352d5</link>
        <description>Remove duplicate MK_ISCSI block and sort the conditional blocks so this errorwon&apos;t crop up again in the futureReported by: gjbMFC after: 1 week

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Mon, 02 Feb 2015 10:31:35 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
<item>
        <title>c01f300b - Build sbin/iscontrol again if MK_ISCSI != no</title>
        <link>http://172.16.0.5:8080/history/freebsd-13.1/sbin/Makefile#c01f300b</link>
        <description>Build sbin/iscontrol again if MK_ISCSI != noMFC after: 13 daysX-MFC with: r277675Pointyhat to: me

            List of files:
            /freebsd-13.1/sbin/Makefile</description>
        <pubDate>Mon, 26 Jan 2015 06:29:07 +0000</pubDate>
        <dc:creator>Enji Cooper &lt;ngie@FreeBSD.org&gt;</dc:creator>
    </item>
</channel>
</rss>
