December 2025 - wlug - list.wlug.org.nz

Austria Military Ditches Microsoft for Open-Source Libreoffice – Here’s Why
by Peter Reutemann 26 Feb '26

26 Feb '26

'Austria's military has completed a major IT overhaul, replacing Microsoft Office with the open-source LibreOffice suite across all its desktop systems. The change, finalized this month, affects approximately 16,000 workstations in the Austrian Armed Forces. This move will substantially reduce Austria's software bill. At $33.75 per user per month, a Microsoft 365 E3 subscription for 16,000 workstations costs approximately $6,480,000 per year, compared to LibreOffice's zero cost. But this move isn't about saving money. The real motivation is to gain digital sovereignty and control over critical data. As Michael Hillebrand of Directorate 6 information and communications technology (ICT) and Cyber Defense, explained: "It was very important for us to show that we are doing this primarily to strengthen our digital sovereignty, to maintain our independence in terms of ICT infrastructure and to ensure that data is only processed in-house."' -- source: https://www.zdnet.com/article/this-european-military-just-ditched-microsoft… Cheers, Peter

2 2

2025 might have been the year for Linux gaming, but there's still a way to go until I switch from Windows
by Lawrence D'Oliveiro 30 Dec '25

30 Dec '25

Here is an article full of praise for the success Linux has been enjoying in handheld PC gaming, being able to run most Windows games better than Windows itself can manage <https://www.pcgamer.com/software/linux/2025-might-have-been-the-year-for-li…>. The writer mentions the one big obstacle to Linux enjoying greater success in this area: kernel-level anti-cheat mechanisms. The vast majority of these are Windows-specific, and many vendors are not only reluctant to support Linux as an alternative platform, they are downright hostile to it. Ultimately, though, I am going to put my bet on free-market Capitalism winning out. The customer is king. It is the game vendors who have to entice the buyers to part with their money in return for something worthwhile, the customers have no obligation to simply hand it over. If the only ace the Windows products have up their sleeve is obnoxious anti-cheat mechanisms, that may not be enough to keep customers flocking to them in droves. In other words, if the Linux-based handhelds continue to offer a superior user experience to the Windows-based ones, then those last remaining holdout vendors will be forced, purely by market forces, to go where the money is: they will ultimately be dragged, kicking and screaming, into supporting Linux gaming in some form.

1 0

Unix V4 Recovered
by Lawrence D'Oliveiro 25 Dec '25

25 Dec '25

A tape containing the only known copy of Bell Labs Unix version 4, dating from 1973, has been found at the University of Utah <https://www.tomshardware.com/software/linux/unix-v4-recovered-from-randomly…>. This was the first version of Unix in which the kernel and core utilities were (re)written in C. This particular tape had been sent to Martin Newell, he of the famous teapot. And yes, the recovered code is now available for you to try running for yourself.

1 0

The Linux Kernel Is Just A Program
by Lawrence D'Oliveiro 24 Dec '25

24 Dec '25

Came across this nifty little article <https://serversfor.dev/linux-inside-out/the-linux-kernel-is-just-a-program/> (found on Bluesky <https://bsky.app/profile/steveklabnik.com/post/3mapj6kf76k2d>) showing that you can run the Linux kernel directly from within a VM in qemu, without installing a distro or anything. It will boot, and then die because it wants to mount a root filesystem and start an init process; so then it’s easy enough to set that up with a few more commands, try booting it again, and there you go -- you have a running VM.

1 0

Linux Kernel Rust Code Sees Its First CVE Vulnerability
by Peter Reutemann 18 Dec '25

18 Dec '25

'Longtime Linux developer Greg Kroah-Hartman announced that the Linux kernel has received its first CVE tied to Rust code. Phoronix reports: This first CVE (CVE-2025-68260) for Rust code in the Linux kernel pertains to the Android Binder rewrite in Rust. There is a race condition that can occur due to some noted unsafe Rust code. That code can lead to memory corruption of the previous/next pointers and in turn cause a crash. This CVE for the possible system crash is for Linux 6.18 and newer since the introduction of the Rust Binder driver. At least though it's just a possible system crash and not any more serious system compromise with remote code execution or other more severe issues. ' -- source: https://it.slashdot.org/story/25/12/17/2034233 Cheers, Peter

1 0

Blocking ads with OpenWRT router
by Peter Reutemann 16 Dec '25

16 Dec '25

Hi everyone Found out on the weekend that I can install AdBlock straight on my router that is running OpenWRT: https://openwrt.org/docs/guide-user/services/ad-blocking?s%5B%5D=adblock Gets rid of (a large portion of) ads on mobile devices, like Android phones, when they are connected via WiFi. Cheers, Peter

1 0

New Rule Forbids GNOME Shell Extensions Made Using AI-Generated Code
by Peter Reutemann 15 Dec '25

15 Dec '25

'Phoronix reports: Due to the growing number of GNOME Shell extensions looking to appear on extensions.gnome.org that were generated using AI, it's now prohibited. The new rule in their guidelines note that AI-generated code will be explicitly rejected: "Extensions must not be AI-generated While it is not prohibited to use AI as a learning aid or a development tool (i.e. code completions), extension developers should be able to justify and explain the code they submit, within reason. Submissions with large amounts of unnecessary code, inconsistent code style, imaginary API usage, comments serving as LLM prompts, or other indications of AI-generated output will be rejected." In a blog post, GNOME developer Javad Rahmatzadeh explains that "Some devs are using AI without understanding the code..."' -- source: https://tech.slashdot.org/story/25/12/14/0453227 Cheers, Peter

1 0

New FreeBSD 15 Retires 32-Bit Ports and Modernizes Builds
by Peter Reutemann 08 Dec '25

08 Dec '25

'FreeBSD 15.0-RELEASE arrived this week, notes this report from The Register, which calls it the latest release "of the Unix world's leading alternative to Linux." As well as numerous bug fixes and upgrades to many of its components, the major changes in this version are reductions in the number of platforms the OS supports, and in how it's built and how its component software is packaged. FreeBSD 15 has significantly reduced support for 32-bit platforms. Compared to FreeBSD 14 in 2023, there are no longer builds for x86-32, POWER, or ARM-v6. As the release notes put it: "The venerable 32-bit hardware platforms i386, armv6, and 32-bit powerpc have been retired. 32-bit application support lives on via the 32-bit compatibility mode in their respective 64-bit platforms. The armv7 platform remains as the last supported 32-bit platform. We thank them for their service." Now FreeBSD supports five CPU architectures — two Tier-1 platforms, x86-64 and AArch64, and three Tier-2 platforms, armv7 and up, powerpc64le, and riscv64. Arguably, it's time. AMD's first 64-bit chips started shipping 22 years ago. Intel launched the original x86 chip, the 8086 in 1978. These days, 64-bit is nearly as old as the entire Intel 80x86 platform was when the 64-bit versions first appeared. In comparison, a few months ago, Debian 13 also dropped its x86-32 edition — six years after Canonical launched its first x86-64-only distro, Ubuntu 19.10. Another significant change is that this is the first version built under the new pkgbase system, although it's still experimental and optional for now. If you opt for a pkgbase installation, then the core OS itself is installed from multiple separate software packages, meaning that the whole system can be updated using the package manager. Over in the Linux world, this is the norm, but Linux is a very different beast... The plan is that by FreeBSD 16, scheduled for December 2027, the restructure will be complete, the old distribution sets will be removed, and the current freebsd-update command and its associated infrastructure can be turned off. Another significant change is reproducible builds, a milestone the project reached in late October. This change is part of a multi-project initiative toward ensuring deterministic compilation: to be able to demonstrate that a certain set of source files and compilation directives is guaranteed to produce identical binaries, as a countermeasure against compromised code. A handy side-effect is that building the whole OS, including installation media images, no longer needs root access. There are of course other new features. Lots of drivers and subsystems have been updated, and this release has better power management, including suspend and resume. There's improved wireless networking, with support for more Wi-Fi chipsets and faster wireless standards, plus updated graphics drivers... The release announcement calls out the inclusion of OpenZFS 2.4.0-rc4, OpenSSL 3.5.4, and OpenSSH 10.0 p2, and notes the inclusion of some new quantum-resistant encryption systems... In general, we found FreeBSD 15 easier and less complicated to work with than either of the previous major releases. It should be easier on servers too. The new OCI container support in FreeBSD 14.2, which we wrote about a year ago, is more mature now. FreeBSD has its own version of Podman, and you can run Linux containers on FreeBSD. This means you can use Docker commands and tools, which are familiar to many more developers than FreeBSD's native Jail system. "FreeBSD has its own place in servers and the public cloud, but it's getting easier to run it as a desktop OS as well," the article concludes. "It can run all the main Linux desktops, including GNOME on Wayland." "There's no systemd here, and never will be — and no Flatpak or Snap either, for that matter.' -- source: https://tech.slashdot.org/story/25/12/07/0627214 Cheers, Peter

1 0

How Home Assistant Leads a 'Local-First Rebellion'
by Peter Reutemann 08 Dec '25

08 Dec '25

'It runs locally, a free/open source home automation platform connecting all your devices together, regardless of brand. And GitHub's senior developer calls it "one of the most active, culturally important, and technically demanding open source ecosystems on the planet," with tens of thousands of contributors and millions of installations. That's confirmed by this year's "Octoverse" developer survey... Home Assistant was one of the fastest-growing open source projects by contributors, ranking alongside AI infrastructure giants like vLLM, Ollama, and Transformers. It also appeared in the top projects attracting first-time contributors, sitting beside massive developer platforms such as VS Code... Home Assistant is now running in more than 2 million households, orchestrating everything from thermostats and door locks to motion sensors and lighting. All on users' own hardware, not the cloud. The contributor base behind that growth is just as remarkable: 21,000 contributors in a single year... At its core, Home Assistant's problem is combinatorial explosion. The platform supports "hundreds, thousands of devices... over 3,000 brands," as [maintainer Franck Nijhof] notes. Each one behaves differently, and the only way to normalize them is to build a general-purpose abstraction layer that can survive vendor churn, bad APIs, and inconsistent firmware. Instead of treating devices as isolated objects behind cloud accounts, everything is represented locally as entities with states and events. A garage door is not just a vendor-specific API; it's a structured device that exposes capabilities to the automation engine. A thermostat is not a cloud endpoint; it's a sensor/actuator pair with metadata that can be reasoned about. That consistency is why people can build wildly advanced automations. Frenck describes one particularly inventive example: "Some people install weight sensors into their couches so they actually know if you're sitting down or standing up again. You're watching a movie, you stand up, and it will pause and then turn on the lights a bit brighter so you can actually see when you get your drink. You get back, sit down, the lights dim, and the movie continues." A system that can orchestrate these interactions is fundamentally a distributed event-driven runtime for physical spaces. Home Assistant may look like a dashboard, but under the hood it behaves more like a real-time OS for the home... The local-first architecture means Home Assistant can run on hardware as small as a Raspberry Pi but must handle workloads that commercial systems offload to the cloud: device discovery, event dispatch, state persistence, automation scheduling, voice pipeline inference (if local), real-time sensor reading, integration updates, and security constraints. This architecture forces optimizations few consumer systems attempt. "If any of this were offloaded to a vendor cloud, the system would be easier to build," the article points out. "But Home Assistant's philosophy reverses the paradigm: the home is the data center..." As Nijhof says of other vendor solutions, "It's crazy that we need the internet nowadays to change your thermostat."' -- source: https://news.slashdot.org/story/25/12/07/1955259 Cheers, Peter

1 0