News: 0001596274

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

FreeBSD 15.0 Now Officially Available With Many Software Updates, Reproducible Builds

([BSD] 4 Hours Ago FreeBSD 15.0-RELEASE)


[1]FreeBSD 15.0 is officially released as the newest major update to this leading BSD operating system.

FreeBSD 15.0 features a plethora of software updates from the latest OpenZFS file-system code to upgraded OpenSSL, OpenSSH, and countless other software upgrades.

FreeBSD 15.0-RELEASE also can build all release artifacts without needing root privileges and also now passing reproducible builds. The FreeBSD base system can also now be installed and managed using the pkg package manager.

The FreeBSD 15.0 kernel also has great improvements like a native inotify implementation and numerous device driver updates. The FreeBSD-on-laptops effort has also resulted in many WiFi improvements, graphics driver enhancements, suspend/resume fixes, and other improvements.

Some of the other driver improvements in FreeBSD 15.0 include Intel E800 series networking with the ICE driver, Tiger Lake through Meteor Lake support from Intel in different drivers, the BNXT driver now supporting Thor2 and 400G speed modules, and the Intel IWX driver for WiFi 6 hardware support. The AGP bus driver meanwhile is deprecated and planned for removal in FreeBSD 16.

FreeBSD 15.0 benchmarks coming up soon on Phoronix. Downloads and more details on today's FreeBSD 15.0 release via [2]FreeBSD.org .



[1] https://www.phoronix.com/search/FreeBSD+15.0

[2] https://www.freebsd.org/releases/15.0R/announce/



There has also been some work to allow the interesting use of macro names.
For example, if you wanted all of your "creat()" calls to include read
permissions for everyone, you could say

#define creat(file, mode) creat(file, mode | 0444)

I would recommend against this kind of thing in general, since it
hides the changed semantics of "creat()" in a macro, potentially far away
from its uses.
To allow this use of macros, the preprocessor uses a process that
is worth describing, if for no other reason than that we get to use one of
the more amusing terms introduced into the C lexicon. While a macro is
being expanded, it is temporarily undefined, and any recurrence of the macro
name is "painted blue" -- I kid you not, this is the official terminology
-- so that in future scans of the text the macro will not be expanded
recursively. (I do not know why the color blue was chosen; I'm sure it
was the result of a long debate, spread over several meetings.)
-- From Ken Arnold's "C Advisor" column in Unix Review