Hírolvasó
Még mindig tele vannak a boltok dzsunka USB-töltőkkel, amik még mindig életveszélyesek
Kipróbálható a tízszer gyorsabb TypeScript fordító
Gyorsabban tűnhetnek el az itthon bejelentett illegális tartalmak
Leelőzte a Xiaomi az Apple-t a viselhető kütyükkel
Többéves megállapodást kötött a Google és a TSMC
[$] Development statistics for the 6.15 kernel
Security updates for Monday
Adventures in read-only softraid
Then what to do?
Fix the code and make it work, of course!
The full story is available as “Stay, (write), protected!”, taking us through the steps of adding a feature to OpenBSD. Enjoy!
Még okosabb szövegíróvá válik a windowsos Jegyzettömb
Ez nem vámtarifa, ez iPhone-adó
FORMULA 1 TAG HEUER GRAND PRIX DE MONACO 2025
Tesla tapasztalatok VII. - állásában kajak merül a Tesla?
Megpróbálkozik a Yettel a lehetetlennel: parkolóhelyet találni Budapest belvárosában
Csillagászati értékben vásárolt be az Oracle az Nvidia chipjeiből
Nvidia: Kína kiszolgálása amerikai érdek
The 6.15 kernel has been released
So this was delayed by a couple of hours because of a last-minute bug report resulting in one new feature being disabled at the eleventh hour, but 6.15 is out there now.
Significant changes in 6.15 include smarter timer-ID assignment to make checkpoint/restore operations more reliable, the ability to read status information from a pidfd after the process in question has been reaped, the PIDFD_SELF special pidfd value, nested ID-mapped mounts, zero-copy network-data reception via io_uring, The ability to read epoll events via io_uring, resilient queued spinlocks for BPF programs, guard-page enhancements allowing them to be placed in file-backed memory areas and for user space to detect their presence, the once-controversial fwctl subsystem, the optional sealing of some system mappings, and much more.
See the LWN merge-window summaries (part 1, part 2) and the in-progress KernelNewbies 6.15 page for more information.
New profiling subsystem committed to -current
A longish sequence of commits introduced the changes incrementally, with a summary as follows: List: openbsd-cvs Subject: CVS: cvs.openbsd.org: src From: Theo de Raadt <deraadt () cvs ! openbsd ! org> Date: 2025-05-24 6:49:17 CVSROOT: /cvs Module name: src Changes by: deraadt@cvs.openbsd.org 2025/05/24 00:49:17 Modified files: include : unistd.h sys/sys : exec.h exec_elf.h gmon.h proc.h systm.h sys/kern : exec_elf.c init_sysent.c kern_exec.c kern_exit.c kern_fork.c kern_pledge.c subr_prof.c syscalls.master Log message: In the old gprof profiling subsystem, the simplistic profil() syscall told the kernel about the sample buffer, and then the normal exit-time _mcleanup() would finalize the buffer, open()'ed a file and write out the details. This file opening has become increasingly impossible because of our privsep / privdrop, chroot, setresuid uid-dropping, pledge, unveil, and other efforts. So people stopped using gprof. Programs which needed profiling needed substantial mitigation removal changes to put them under test.