Hírolvasó
MP-safe tcp_input() committed
List: openbsd-cvs Subject: CVS: cvs.openbsd.org: src From: Alexander Bluhm <bluhm () openbsd ! org> Date: 2025-04-26 13:58:08 CVSROOT: /cvs Module name: src Changes by: bluhm@cvs.openbsd.org 2025/04/26 07:58:08 Modified files: sys/netinet : in_proto.c sys/netinet6 : in6_proto.c Log message: Run TCP input in parallel on multiple CPUs.
Farigcsál a Meta a pénzégető Reality Labs részlegen
A Huawei nem áll meg, az Ascend 910D már verheti a H100-at
Kernel prepatch 6.15-rc4
OpenBSD 7.7 released
OpenBSD 7.7 Released
The OpenBSD project has announced OpenBSD 7.7, its 58th release.
The new release contains a number of significant improvements, including but certainly not limited to:
- Multiple SMP improvements have been made. TCP output and TCP timers now run in parallel. Only TCP input still uses exclusive netlock.
- drm(4) has been updated to to Linux 6.12.21
- Performance policy specification is now more flexible. [See earlier report]
- sysctl(8) now supports an input file. [See earlier report]
- Improvements to network hardware support include new drivers ice(4) for Intel E810 Ethernet devices, and ixv(4) for virtual functions of Intel 82598EB, 82559, and X540.
- By default, sysupgrade(8) now upgrades to the next release. [See earlier report]
- fw_update(8) now supports arbitrary dmesg files. [See earlier report]
- Support for FRAME sockets was added. [See earlier report]
- ifconfig scan can now detect/display WPA3 access points.
- (Limited) EFI boot manager support has been added to installboot(8).
- unwind(8) now supports wildcards in block list. [See earlier report]
- rpki-client(8) now has a stricter aging policy for Trust Anchor certificates. [See earlier report]
- LibreSSL 4.1.0 [See earlier report for version 4.0.0]
- OpenSSH 10.0 [See earlier reports on sshd(8) splitting, and on release]
See the full changelog for more details of the changes made over this latest six month development cycle.
The Installation Guide details how to get the system up and running with a fresh install, while those who already run earlier releases should follow the Upgrade Guide, in most cases using sysupgrade(8).
Readers are encouraged to celebrate the new release by donating to the project to support further development of our favourite OS!
Nagypapa által 40 éven át hordott Rolex Datejust karbantartása
[$] Debian debates AI models and the DFSG
The Debian project is discussing a General Resolution (GR) that would, if approved, clarify that AI models must include training data to be compliant with the Debian Free Software Guidelines (DFSG) and be distributed by Debian as free software. While GR discussions are sometimes contentious, the discussion around the proposal from Debian developer Mo Zhou has been anything but—there seems to be consensus that AI models are not DFSG-compliant if they lack training data. There are, however, some questions about the exact language and questions about the impact the GR will have on existing packages in the Debian archive.
GCC 15.1 released
Four stable kernel updates
Security updates for Friday
Ma éppen a Yahoo venné meg a Chrome-ot
Szorul a hurok a TP-Link nyaka körül az USA-ban
Magyar Péter hirtelen "szentes" "lett"
Minden Amerikába szánt iPhone-t Indiában gyárthatnak
USA Tech Hub: ahonnan a passzátszél fúj
Tízéves lett a világ legnépszerűbb okosóra-sorozata
Introducing an OpenBSD LLDP daemon
List: openbsd-tech Subject: LLDP daemon and display tool From: David Gwynne <david () gwynne ! id ! au> Date: 2025-04-24 3:49:53 this adds a small daemon and command line tool for receiving and displaying LLDP messages from neighbors connected to Ethernet interfaces. the daemon is called olldpd(8) to avoid colliding with the existing lldpd from ports. the command line tool is lldp(8). it uses the AF_FRAME sockets that were recently added rather than BPF. this means it retains fewer privileges while it's running because it doesn't have to open and configure BPF devices when new interfaces appear in the system. avoiding BPF means it has basically 0 impact on the kernel packet path because AF_FRAME is handled as a last resort for packets rather than up front for every packet on an interface.