<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sbin, branch main</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=main</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2026-07-23T20:57:07Z</updated>
<entry>
<title>Fix namespace listing for old NVMe devices</title>
<updated>2026-07-23T20:57:07Z</updated>
<author>
<name>Alexander Motin</name>
<email>mav@FreeBSD.org</email>
</author>
<published>2026-07-23T20:57:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=86182d89020159697391375cf475893d4cd859c0'/>
<id>urn:sha1:86182d89020159697391375cf475893d4cd859c0</id>
<content type='text'>
Commit 9e1db51d4b5fc made nvmecontrol devlist get list of active
namespaces from the device instead of iterating through all possible
IDs.  The problem is that this request is not supported before NVMe
1.1, and in particular by Intel Optane 905P drives.  This change
reintroduces iteration for devices before NVMe 1.2.

Reviewed by:	imp
Differential Revision:  https://reviews.freebsd.org/D58010
</content>
</entry>
<entry>
<title>man: Fix RFC 1918 network prefix lengths</title>
<updated>2026-07-17T16:51:11Z</updated>
<author>
<name>Yusuke Ichiki</name>
<email>public@yusuke.pub</email>
</author>
<published>2026-07-17T14:58:42Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1403ca10189c47ad1de3915eeb030deddc114685'/>
<id>urn:sha1:1403ca10189c47ad1de3915eeb030deddc114685</id>
<content type='text'>
According to RFC 1918, the following IP prefixes are reserved for
private internets:

    10.0.0.0/8
    172.16.0.0/12
    192.168.0.0/16

This PR fixes the prefix lengths in references to private networks
("RFC 1918 networks", "the standard private IP address ranges").
The changes are limited to man pages.

Signed-off-by:	Yusuke Ichiki &lt;public@yusuke.pub&gt;
Pull Request:	https://github.com/freebsd/freebsd-src/pull/2328
MFC after:	3 days
</content>
</entry>
<entry>
<title>pfctl: fix incorrect errno checks</title>
<updated>2026-07-15T11:44:59Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2026-07-14T07:32:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=40c611d0939f187d9a211e9e497291e251deddd3'/>
<id>urn:sha1:40c611d0939f187d9a211e9e497291e251deddd3</id>
<content type='text'>
These calls return an error value, they do not set errno. Check their
return values.

Sponsored by:	Rubicon Communications, LLC ("Netgate")
</content>
</entry>
<entry>
<title>pfctl: fix CREATE_TABLE error handling</title>
<updated>2026-07-15T11:44:59Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2026-07-13T13:14:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ddbf89234312791e65991efff39a18a9e8e4d077'/>
<id>urn:sha1:ddbf89234312791e65991efff39a18a9e8e4d077</id>
<content type='text'>
pfr_add_table() does not set errno, it returns an error (now).
Read the error code from the return value so we display the correct
error message to the user.

Sponsored by:	Rubicon Communications, LLC ("Netgate")
</content>
</entry>
<entry>
<title>init(8): extract reroot transient code into reroot_seed</title>
<updated>2026-07-14T15:43:45Z</updated>
<author>
<name>Konstantin Belousov</name>
<email>kib@FreeBSD.org</email>
</author>
<published>2026-07-10T19:02:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=4c9f648852629d757165796bb3cd97bb84a0e483'/>
<id>urn:sha1:4c9f648852629d757165796bb3cd97bb84a0e483</id>
<content type='text'>
Since init become dynamically linked, reroot appeared to be broken
because init copies itself into a transient tmpfs mount to continue
controlling execution right after the reboot(REROOT) syscall.  Because
the binary is dynamically linked, it cannot be properly executed.

Provide a minimal static binary 'reroot_seed' embedded into the init as
byte stream, which performs what the 'init -r' did, namely, the second
phase reroot.

For the static build of init as part of the /rescue crunch, keep the
inline reroot code.

Reported and tested by:	markj
Sponsored by:	The FreeBSD Foundation
MFC after:	1 week
Differential revision:	https://reviews.freebsd.org/D58164
</content>
</entry>
<entry>
<title>bluetooth: signal devd on netgraph device events</title>
<updated>2026-07-12T18:28:15Z</updated>
<author>
<name>-k</name>
<email>slowdive@me.com</email>
</author>
<published>2026-07-12T18:16:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=ad91d47db306738cc29f30c4d506509a3f5eeb8c'/>
<id>urn:sha1:ad91d47db306738cc29f30c4d506509a3f5eeb8c</id>
<content type='text'>
Currently, devd emits events for external adapters only.

Send Netgraph init/disconnect events to devd so the internal adapter's
state could be asserted from userland.

(adrian - indentation changes.)

Signed-off-by: Kirill Orlov (-k) &lt;slowdive@me.com&gt;
Reviewed-by: adrian, imp
Pull-Request: https://github.com/freebsd/freebsd-src/pull/2196
</content>
</entry>
<entry>
<title>reboot: fix openlog(3) calls</title>
<updated>2026-07-08T05:16:01Z</updated>
<author>
<name>Ricardo Branco</name>
<email>rbranco@suse.de</email>
</author>
<published>2026-06-27T10:04:48Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f723b28c9663b70045e6db07f9fe72422a609c16'/>
<id>urn:sha1:f723b28c9663b70045e6db07f9fe72422a609c16</id>
<content type='text'>
LOG_CONS was OR'd into the facility argument instead of logopt, leaving
logopt as 0.  The correct call is openlog(ident, LOG_CONS, LOG_AUTH),
as shutdown(8) and init(8) already do.

PR:	296315
Signed-off-by: Ricardo Branco &lt;rbranco@suse.de&gt;
Reviewed by: imp, des
Pull Request: https://github.com/freebsd/freebsd-src/pull/2300
</content>
</entry>
<entry>
<title>ping: Fix bell char ordering in -A test cases</title>
<updated>2026-06-30T13:07:59Z</updated>
<author>
<name>Siva Mahadevan</name>
<email>siva@FreeBSD.org</email>
</author>
<published>2026-06-26T12:22:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=f7f916d755fe5b48a2a68a937beea770b7bafa95'/>
<id>urn:sha1:f7f916d755fe5b48a2a68a937beea770b7bafa95</id>
<content type='text'>
Previously, these tests expected the bell chars to arrive
before the initial status line. This appeared to be ok because
ping(8) incorrectly mixed unbuffered and buffered writes by using
printf(3) calls for the initial status, but direct write(2) calls
for the bell chars. 141bb85798 revealed that the test's assertions
only passed because the buffered writes did not get flushed before
the direct writes in the test runs.

8bda488114f3 fixed ping(8) to use POSIX stdio buffered writes
in all cases and guarantee a deterministic output ordering to stdout
observers. This patch fixes the test to match the correct ordering.

Reviewed by:	des
Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>Revert "ping/tests: expect bell chars from stderr after initial status"</title>
<updated>2026-06-30T13:07:47Z</updated>
<author>
<name>Siva Mahadevan</name>
<email>siva@FreeBSD.org</email>
</author>
<published>2026-06-30T13:00:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7ac9995a062ff9f78b634fe403e6a313f5637945'/>
<id>urn:sha1:7ac9995a062ff9f78b634fe403e6a313f5637945</id>
<content type='text'>
This reverts commit 5b8c28adb829b50fb8ac065637fa99f717858bab.

The commit message was wrong.

Reported by:	des
</content>
</entry>
<entry>
<title>pflog: create bpf tapping points without ifnet(9)</title>
<updated>2026-06-28T13:59:35Z</updated>
<author>
<name>Kristof Provost</name>
<email>kp@FreeBSD.org</email>
</author>
<published>2026-06-24T10:21:20Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e4f3ab161a9e149fd2f657f6d8af2ba3c618255f'/>
<id>urn:sha1:e4f3ab161a9e149fd2f657f6d8af2ba3c618255f</id>
<content type='text'>
Just as was done for ipfw's log device stop creating entire struct
ifnet's for pflog devices. Create only a bpf_t.

This does mean we lose the create/destroy infrastructure provided by the
clone interface. Rather than implement this ourselves we allow users to
configure the number of pflog interfaces using the net.pflog.if_count
sysctl. We default to 8 devices, but allow up to 256.

The /etc/rc.d/pflog script will create extra devices as required.

While it was possible to rename pflog devices pfctl expected the pflogX
name, so it's safe to assume users never did this.

Requested by:	glebius
Reviewed by:	glebius
Sponsored by:	Rubicon Communications, LLC ("Netgate")
Differential Revision:	https://reviews.freebsd.org/D57851
</content>
</entry>
</feed>
