blocklist: Add vendor import instructions
Add vendor import instructions for blocklist.
It includes a "freebsd-changes.sh" script that takes care of adapting
paths and functions into FreeBSD.
Reviewed by: emaste
MFC after: 1 week
Differential Revision: https://reviews.freebsd.org/D49510
x11-wm/xdgmenumaker: Update 2.3 => 2.4, take maintainership
Commit log:
https://github.com/gapan/xdgmenumaker/compare/2.3...2.4
Port changes:
- Switch to DISTVERSION instead.
- Specify LICENSE_FILE.
- Use ${PORTNAME} variable for SHEBANG_FILES instead.
- Polish Makefile with portclippy and portfmt.
- Add NO_ARCH - "no architecture specific files found".
- Submitter take maintainership.
PR: 291698
thunderbolt: Remove PNP info
So it isn't matched by devmatch(8) and automatically loaded. The PNP
info will be readded once the USB4 driver is more complete.
PR: 290827
Reported by: fuz, Marco Siedentopf <siedentm at me.com>
Fixes: 2ed9833791f2 (thunderbolt: Import USB4 code)
Sponsored by: The FreeBSD Foundation
Uses/go.mk: Add support for requesting a minimum version
This adds support for requesting a minimum Go version instead of an
exact one. If USES contains something like go:X.Y+, we walk the list
of valid Go versions backward and pick the first element that matches
either the requested version or the default version. Assuming the
list of valid versions is sorted semantically, this means we will
pick the requested version if it is newer than the default version,
and the default version otherwise.
This is somewhat imprecise, but it's hard to do better without a
comparison operator that understands semantic versioning, which bmake
lacks. Simply comparing versions lexicographically or numerically
would produce incorrect results, since e.g. 1.3 precedes 1.29 but is
both lexicographically and numerically larger.
Note that specifying a version that does not yet exist in the ports tree
will have the same effect as specifying a version that has been retired:
silently fall back to the default version.
[10 lines not shown]
many: Unpin Go ports
* Ports that were pinned to a deprecated version of Go (1.23 or older)
have been unpinned.
* Ports that were pinned to a still-supported version of Go (1.24 or
newer) have been converted to requesting that as their minimum Go
version.
* Ports that had been forcibly deprecated for pinning an expired Go
version have been undeprecated.
www/codeberg-pages-server: Update to 6.4
The current version (6.2.1) is not only outdated, it appears to have
been re-rolled, and therefore fails the checksum.
Approved by: maintainer
Reviewed by: adamw
Differential Revision: https://reviews.freebsd.org/D54112
ctfmerge: fix segfault when building on macOS
The barrier code was using semaphores which have been deprecated in
macOS and not working at all, causing a race condition. Since macOS
does not have pthread_barrier_*(), this change uses a condition
variable instead.
PR: 290958
Reported by: wosch
Reviewed by: imp, markj
Differential Revision: https://reviews.freebsd.org/D54018
(cherry picked from commit 732b4aa05d78ca6831d02e67a43f34ad104f4f01)
ctfmerge: fix segfault when building on macOS
The barrier code was using semaphores which have been deprecated in
macOS and not working at all, causing a race condition. Since macOS
does not have pthread_barrier_*(), this change uses a condition
variable instead.
PR: 290958
Reported by: wosch
Reviewed by: imp, markj
Differential Revision: https://reviews.freebsd.org/D54018
(cherry picked from commit 732b4aa05d78ca6831d02e67a43f34ad104f4f01)
ctfmerge: fix segfault when building on macOS
The barrier code was using semaphores which have been deprecated in
macOS and not working at all, causing a race condition. Since macOS
does not have pthread_barrier_*(), this change uses a condition
variable instead.
PR: 290958
Reported by: wosch
Reviewed by: imp, markj
Differential Revision: https://reviews.freebsd.org/D54018
(cherry picked from commit 732b4aa05d78ca6831d02e67a43f34ad104f4f01)
ipfw: create a bpf tap point for every log rule
Dynamically allocate bpf tap points for every rule that has "log".
The name is "ipfw%u", where %u is substituted to the rule number.
The default catch all "ipfw0" tap still exists for compatibility
and it will catch packets in case if there are no bpf listeners
on a per-rule tap.
Reviewed by: ae
Differential Revision: https://reviews.freebsd.org/D53877
ipfw: create "ipfw0" and "ipfwlog0" bpf tapping points without ifnet(9)
As a free bonus the tapping points are now able to match packet direction.
Reviewed by: ae
Differential Revision: https://reviews.freebsd.org/D53875
ifconfig: print warning and return success on ipfw0, ipfwlog0 cloning
This should provide people a chance to remove ipfw0 and ipfwlog0 from
cloned_interfaces in their rc.conf during FreeBSD 16.x lifetime.
Differential Revision: https://reviews.freebsd.org/D53876
bpf: modularize ifnet(9) part of bpf
Imagine that bpf(9) tapping can happen at any point in the network stack,
not necessarily at interface transmit or receive. To achieve that we need
a thin layer of abstraction defined by struct bif_methods, that defines
how generic bpf layer works with a tap point of this kind.
Implement ifnet(9) specific methods in a separate file bpf_ifnet.c. At
this point there is 100% compatibility for all existing interfaces, there
is no KPI change, yet. The legacy attaching KPI is layered over new ifnet
agnostic KPI. The new KPI may change though, as we can implement multiple
DLTs per single tap point in a prettier fashion.
The new abstraction layer allows us to move all the 802.11 radio injection
hacks out of bpf.c into ieee80211_radiotap.c, so do that immediately as a
good proof of concept.
Reviewed by: bz
Differential Revision: https://reviews.freebsd.org/D53872
