Re: June 2025 stabilization week

> On 23. Jun 2025, at 10:01, Gleb Smirnoff <glebius@FreeBSD.org> wrote:
> 
>  Hi FreeBSD/main users & developers:
> 
> This is an automated email to inform you that the June 2025 stabilization week
> started with FreeBSD/main at main-n278153-b2e0dfc808c1, which was tagged as
> main-stabweek-2025-Jun.
> 
> Those who want to participate in the stabilization week are encouraged to
> update to the above revision/tag and test their systems.
> 
> The tag main-stabweek-2025-Jun has been published at Gleb Smirnoff's github repo.
> To connect this repo as an additional remote you need to run:
> 
>  git remote add glebius https://github.com/glebius/FreeBSD
> 
> Once remote is configured, to checkout the tag run:
> 
>  git fetch glebius --tags
>  git checkout main-stabweek-2025-Jun
> 
> If you want to use only the official FreeBSD repo, then update to
> the revision:
> 
>  git pull
>  git checkout b2e0dfc808c1
> 
> Developers are encouraged to avoid pushing new features to FreeBSD/main during
> the stabilization week, but focus on bugfixes instead.  The stabilization week
> runs up to Friday 18:00 UTC, but if there is consensus that any regressions
> discovered by participants have been fixed, it will end early.
> 
> Once that happens, the advisory freeze of FreeBSD/main branch is thawed.
Hi Gleb,

I observed one issue when building world/kernel.

In /etc/devfs.conf I have

own bpf* root:network
perm bpf* 0660

and this results in
tuexen@epyc:~ % ls -l /dev/bpf*
crw-rw----  1 root network 0x27 Apr 26 20:13 /dev/bpf
lrwxr-xr-x  1 root wheel      3 Apr 26 20:13 /dev/bpf0 -> bpf

This allows members of the network group to capture traffic.

However, with main-n278173-81e6c0168d46 I get
tuexen@epyc:~ % ls -l /dev/bpf*
crw-------  1 root wheel 0x27 Jun 24 12:25 /dev/bpf
lrwxr-xr-x  1 root wheel    3 Jun 24 12:25 /dev/bpf0 -> bpf

It looks like the devd did not what it did in the past.

Any idea what is going wrong?

Best regards
Michael
> 
> --
> Gleb Smirnoff