> When … wifi cards stopped having good blob support it became less tenable. Maybe that all improved after I jumped ship.
The work to modernize the wifi stack has been underway since 2020. There was an update on it in 2021.[1] Based on the wiki, this work is still happening.[2] But they can probably use help.
[1] https://blog.netbsd.org/tnf/entry/wifi_project_status_update
[2] https://wiki.netbsd.org/Converting_drivers_to_the_new_wifi_s...
Re:I Feel for the NetBSD Community
by cryptonector on Saturday January 07, 2023 @12:22AM
(#34285481)
When you have DTrace, eBPF isn't as urgent.
You've seen what nlnet labs are doing with XDP managing and monitoring dns flows in kernel? Wire speed packet classification. Cool stuff. But.. it demands modern ebpf.
Security is more important. And dTrace implements a full stack, from kernel, user space to apps.
eBPF is an Linux-only insecure island, they can keep.
Re:I Feel for the NetBSD Community
by cryptonector on Saturday January 07, 2023 @10:03PM
(#34295591)
Eh, a bytecode like DTrace's, or eBPF, can be safe. The original BPF certainly was (IIRC).
I also ran NetBSD from it's birth right up to the first modern laptop I got that it couldn't drive nicely. I miss some of the robust simplicity of it.
When DSDT started not being fully implemented for thinkpads so S1/S2 sleep states didn't work and wifi cards stopped having good blob support it became less tenable. Maybe that all improved after I jumped ship.
I also ran pkgsrc on OSX for a while. It's pretty good as a proper portable build environment.
I feel like NetBSD the way I feel about nvi versus vim