<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/sbin/Makefile, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2020-11-26T04:29:30Z</updated>
<entry>
<title>Merge ping6 to ping</title>
<updated>2020-11-26T04:29:30Z</updated>
<author>
<name>Alan Somers</name>
<email>asomers@FreeBSD.org</email>
</author>
<published>2020-11-26T04:29:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=3cde9171d2d50852ab782e90acf734f416246e86'/>
<id>urn:sha1:3cde9171d2d50852ab782e90acf734f416246e86</id>
<content type='text'>
There is now a single ping binary, which chooses to use ICMP or ICMPv4
based on the -4 and -6 options, and the format of the address.

Submitted by:	Ján Sučan &lt;sucanjan@gmail.com&gt;
Sponsored by:	Google LLC (Google Summer of Code 2019)
MFC after:	Never
Differential Revision:	https://reviews.freebsd.org/D21377
</content>
</entry>
<entry>
<title>Remove NAND and NANDFS support</title>
<updated>2019-06-25T04:50:09Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2019-06-25T04:50:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=f5a95d9a07941650493461c255408f5727d0638b'/>
<id>urn:sha1:f5a95d9a07941650493461c255408f5727d0638b</id>
<content type='text'>
NANDFS has been broken for years. Remove it. The NAND drivers that
remain are for ancient parts that are no longer relevant. They are
polled, have terrible performance and just for ancient arm
hardware. NAND parts have evolved significantly from this early work
and little to none of it would be relevant should someone need to
update to support raw nand. This code has been off by default for
years and has violated the vnode protocol leading to panics since it
was committed.

Numerous posts to arch@ and other locations have found no actual users
for this software.

Relnotes:	Yes
No Objection From: arch@
Differential Revision: https://reviews.freebsd.org/D20745
</content>
</entry>
<entry>
<title>Add verifying manifest loader for mac_veriexec</title>
<updated>2019-02-26T06:17:23Z</updated>
<author>
<name>Simon J. Gerraty</name>
<email>sjg@FreeBSD.org</email>
</author>
<published>2019-02-26T06:17:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=eb12b8ea5e7fd3b2dd6386de0e96185d94f57249'/>
<id>urn:sha1:eb12b8ea5e7fd3b2dd6386de0e96185d94f57249</id>
<content type='text'>
This tool will verify a signed manifest and load contents into
mac_veriexec for storage

Sponsored by:	Juniper Networks
Differential Revision:	D16575
</content>
</entry>
<entry>
<title>New pfil(9) KPI together with newborn pfil API and control utility.</title>
<updated>2019-01-31T23:01:03Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2019-01-31T23:01:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=b252313f0b3a4659c02e61d3a0bba471c89bcfa9'/>
<id>urn:sha1:b252313f0b3a4659c02e61d3a0bba471c89bcfa9</id>
<content type='text'>
The KPI have been reviewed and cleansed of features that were planned
back 20 years ago and never implemented.  The pfil(9) internals have
been made opaque to protocols with only returned types and function
declarations exposed. The KPI is made more strict, but at the same time
more extensible, as kernel uses same command structures that userland
ioctl uses.

In nutshell [KA]PI is about declaring filtering points, declaring
filters 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 a
different 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 rulesets
that may be linked to different points. Think of per-interface ACLs in
Cisco or Juniper. None of existing packet filters yet support that,
however limited usage is already possible, e.g. default ruleset can
be moved to single interface, as soon as interface would pride their
filtering points.

Another future feature is possiblity to create pfil heads, that provide
not an mbuf pointer but just a memory pointer with length. That would
allow filtering at very early stages of a packet lifecycle, e.g. when
packet has just been received by a NIC and no mbuf was yet allocated.

Differential Revision:	https://reviews.freebsd.org/D18951
</content>
</entry>
<entry>
<title>Rename be(1) to bectl(8); continues to live in /sbin</title>
<updated>2018-07-24T13:21:44Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2018-07-24T13:21:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=5952343e02ab1ecabc7241a755241284418ea2ad'/>
<id>urn:sha1:5952343e02ab1ecabc7241a755241284418ea2ad</id>
<content type='text'>
Discussed with:	rpokala, allanjude
</content>
</entry>
<entry>
<title>Import libbe(3)/be(1) from socsvn/soc2017/kneitinger/libbe-head</title>
<updated>2018-07-24T13:17:40Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2018-07-24T13:17:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=28f16a0f1985b32a97075a540236e8abebaeadf1'/>
<id>urn:sha1:28f16a0f1985b32a97075a540236e8abebaeadf1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Makefiles: remove outdated comments</title>
<updated>2018-06-24T09:39:40Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-06-24T09:39:40Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=aa571745a668010cb1b4ca39180b5de6991e5493'/>
<id>urn:sha1:aa571745a668010cb1b4ca39180b5de6991e5493</id>
<content type='text'>
</content>
</entry>
<entry>
<title>NVME support is only for x86 and powerpc64.</title>
<updated>2018-06-14T01:15:19Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2018-06-14T01:15:19Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=f0f8a1af01576a8f4777fe6139d651de7faa394a'/>
<id>urn:sha1:f0f8a1af01576a8f4777fe6139d651de7faa394a</id>
<content type='text'>
Implement MK_NVME now that the expression for where NVMe is
complicated. Default it to "yes" for x86 and powerpc64 and
no everywhere else. Use it in camcontrol to define WITH_NVME
for those platforms where we support nvme.

This should fix the newly introduced nvme files to camcontrol
which were building everywhere.

Pointy Hat To: imp
Sponsored by: Netflix
</content>
</entry>
<entry>
<title>Move devmatch to sbin from usr/sbin.</title>
<updated>2018-02-12T14:44:21Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2018-02-12T14:44:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=590682b6e6b2b86fc0bc8c9507444e4392c6efd2'/>
<id>urn:sha1:590682b6e6b2b86fc0bc8c9507444e4392c6efd2</id>
<content type='text'>
Since we want to use devmatch in context before a split /,/usr system
has mounted /usr, move devmatch to /sbin.

Sponsored by: Netflix
</content>
</entry>
<entry>
<title>Remove badsect(8).</title>
<updated>2017-11-05T22:00:54Z</updated>
<author>
<name>Konstantin Belousov</name>
<email>kib@FreeBSD.org</email>
</author>
<published>2017-11-05T22:00:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=93b09f581a60c198819b854e767524e30deeed53'/>
<id>urn:sha1:93b09f581a60c198819b854e767524e30deeed53</id>
<content type='text'>
Failure modes of the modern (that is, produced in the last 25 years)
hard drives and SSDs made the utility outdated.  Since the kernel
interface to support it was removed in r324853, cut the userspace
remnants as well.

Discussed with:	bde (who does not like the removal)
Sponsored by:	The FreeBSD Foundation
MFC after:	2 weeks
</content>
</entry>
</feed>
