Computing power has emerged as a vital resource for economies around the world. China is no exception, and the country has invested heavily into domestic CPU capabilities. Loongson is at the forefront of that effort. We previously covered the company’s 3A5000 CPU, a quad core processor that delivered reasonable performance per clock, but clocked too low to be competitive. Now, we’re going to look at Loongson’s newer 3A6000 CPU. The 3A6000 is also a quad core 2.5 GHz part, but uses the newer LA664 core. Compared to the 3A5000’s LA464 cores, LA664 is a major and ambitious evolution. While Loongson has kept the same general architecture, LA664 has a larger and deeper pipeline with more execution units. To sweeten the pie, LA664 gets SMT support. When properly implemented, SMT can increase multithreaded performance with minimal die area overhead. But SMT can be challenging to get right. ↫ Chips and Cheese I’m always fascinated by China’s attempts at catching up to Intel and AMD, but at the same time, there’s no chance in hell I’d ever use any of it.

Google’s Project Zero reports that memory safety vulnerabilities—security defects caused by subtle coding errors related to how a program accesses memory—have been “the standard for attacking software for the last few decades and it’s still how attackers are having success”. Their analysis shows two thirds of 0-day exploits detected in the wild used memory corruption vulnerabilities. Despite substantial investments to improve memory-unsafe languages, those vulnerabilities continue to top the most commonly exploited vulnerability classes. In this post, we share our perspective on memory safety in a comprehensive whitepaper. This paper delves into the data, challenges of tackling memory unsafety, and discusses possible approaches for achieving memory safety and their tradeoffs. We’ll also highlight our commitments towards implementing several of the solutions outlined in the whitepaper, most recently with a $1,000,000 grant to the Rust Foundation, thereby advancing the development of a robust memory-safe ecosystem. ↫ Alex Rebert and Christoph Kern at Google’s blog Even as someone who isn’t a programmer, it’s impossible to escape the rising tide of memory-safe languages, with Rust leading the charge. If this makes the software we all use objectively better, I’ll take the programmers complaining they have to learn something new.

There’s a channel on YouTube called The Proper People. It’s two guys who travel all over the United States (and in a few cases, elsewhere too) exploring abandoned buildings, and recording both the exteriors and interiors for posterity, since many of these buildings suffer from massive decay and are often slated for demolition. These buildings have histories and stories that otherwise would be lost to time. They are incredibly respectful of the buildings they explore, and they will not break open locked doors or windows, and only traverse open and unlocked doors or openings borne out of natural decay. They never take anything from the sites they visit, and abhor what urban explorers call “staging”, where you move furniture and objects around to invoke or imply stories and things that aren’t there. Their videos are also very calm, muted, quiet, and only occasionally use atmospheric music for some of the more artistic shots. As a sidenote, they also happen to have the absolute best intro music of all time. One of the things you quickly notice as you see these buildings, and explore their interiors, is just how solidly made and beautifully detailed they were. Whether they’re exploring an 19th century Kirkbride mental asylum, an early 19th century power plant, or a mid-20th century hospital – they all tend to be made not just to serve a function, but also to be beautiful and solid, both inside and out. Walls, ceilings, and doorways are beautifully detailed in masonry or woodwork, light fittings are solid and ornate, and even access corridors or storage basements have gorgeous vaulted ceilings, decorated walls, and ornate pillars. The contrast to modern buildings couldn’t be starker. Buildings and workplaces of today are littered with drop ceilings, flimsy dividers, open plans, endless amounts of glass, all in styles so minimalist it just makes spaces feel cold, uninviting, and lacking in human scale. Modern buildings and interiors are temporary, ephemeral, built not for humans, but to a bottom line and some designer’s fancy – these old hospitals, factories, and even power plants are permanent, enduring, and made to human scale. They served as much as a status symbol for whatever ruthless capitalist owned the building as they did as a place for that same ruthless capitalist to extract wealth from mistreated workers. This juxtaposition, of the minimalist, soulless, flimsy and cheap-looking exteriors and interiors of modern buildings on the one hand, and the beautifully detailed, skillfully crafted, and human-scale exteriors and interiors from these older buildings on the other, is something that kept creeping back into my mind during my use of the MNT Reform. This is a device built by people who deeply care, who are very opinionated, and know exactly what they want to make – very much the opposite of the cookie-cutter dime-a-dozen laptops that flood the market today. MNT was so kind as to send me a Reform, at some risk to them because I am definitely not the kind of customer the Reform is typically aimed at. Yet, after a few months of use, I can confidently say this is one of the most unique devices I’ve ever used, and one that’s worth every cent. Let’s explore why. Brutalist hardware Let’s first dive into what, exactly, the Reform is. At its core, it’s an ARM-based laptop designed to run Linux, developed and built by a small team of people in Berlin. The Reform is unique in that it is designed to be open hardware, fully repairable and highly modular and upgradeable. It consists of a mainboard with an mPCIe slot, an M.2 slot for NVME SSDs, 16GB eMMC storage, and uniquely, a slot for a System-on-Chip module roughly the size of an SO-DIMM module that contains the processor and RAM. The keyboard and pointing device are internally connected through USB 2.0 and easily replaceable, too. The Reform is defined as much by what it does not have as by what it does have. You won’t find any surveillance devices inside the Reform – no webcam, no microphones, nothing. There have been laptops with little privacy switches or sliding covers for the webcam, but I don’t think I’ve seen a modern laptop that eschews cameras and microphones since the late ’90s. It’s one of the many examples of the Reform’s opinionated design choices. The configuration MNT sent me consists of the aforementioned mainboard, coupled with one of the processor modules they offer – in my case, the RCM4 A311D, which sports four 2.2GHz Cortex-A73 cores and two 1.8GHz Cortex-A53 cores, 4GB of LP-DDR4 RAM, and an ARM Mali G52 MP4 GPU that supports OpenGL/ES 3.1 through Panfrost. This module also supports Wi-Fi 5 and Bluetooth 5.0 through the integrated RTL8822CS. The A311D is just one of many modules available for purchase for the Reform, and during the writing of this review, MNT also added a brand new SoC module to its lineup – the RK3588, the most powerful option available for the Reform. It packs 4 ARM Cortex-A76 cores (up to 2.4GHz) and 4 ARM Cortex-A55 cores (up to 2.2GHz), 16GB or 32GB of RAM, and 128GB or 256GB of eMMC storage. It also sports an ARM Mali-G610 MP4 4-core GPU. Like with all other modules, the drivers for the A311D in my model are completely open source. When it comes to firmware, however, the A311D is not fully open source; there’s closed-source code in the Wi-Fi firmware and the boot/TF-A firmware. The other modules all also have various bits of closed firmware, except for the RKX7 module that uses a Kintex-7 FPGA and hence comes with a hefty price tag. Using the RKX7 module, you can have a fully open source laptop, from operating system down to the firmware, which is, as far as I can tell, unique. However, the amount of closed firmware code for each of the other boards is relatively small, and in some cases – such as with the LS1028A – can be avoided, too. If you care about

Nearly one year ago Intel published the X86S specification (formerly stylized as “X86-S”) for simplifying the Intel architecture by removing support for 16-bit and 32-bit operating systems. X86S is a big step forward with dropping legacy mode, 5-level paging improvements, and other modernization improvements for x86_64. With the Linux 6.9 kernel more x86S bits are in place for this ongoing effort. ↫ Michael Larabel I doubt we’ll see much fallout from these changes.

Oracle Solaris 11.4 SRU 66 is now available via ‘pkg update’ from the support repository or by downloading the SRU from My Oracle Support Doc ID 2433412.1. Highlights of the changes in this release are given in the release announcement and important information to read before installing it is provided in the Readme linked from the above support document. This blog post provides more details about selected new features and interface changes in this SRU, as well as some preparation work for changes coming in future SRUs. ↫ Alan Coopersmith and Jan Pechanec Oracle is still developing Solaris. I still find it very difficult to care after Oracle’s bullshittery.

Roku customers are threatening to stop using, or to even dispose of, their low-priced TVs and streaming gadgets after the company appears to be locking devices for people who don’t conform to the recently updated terms of service (ToS). This month, users on Roku’s support forums reported suddenly seeing a message when turning on their Roku TV or streaming device reading: “We’ve made an important update: We’ve updated our Dispute Resolution Terms. Select ‘Agree’ to agree to these updated Terms and to continue enjoying our products and services. Press * to view these updated Terms.” A large button reading “Agree” follows. The pop-up doesn’t offer a way to disagree, and users are unable to use their device unless they hit agree. ↫ Scharon Harding at Ars Technica The best part of this story? And by best I mean worst? You have to send a letter – a paper one, with stamps and everything, like in the before times – to Roku’s lawyer in California containing the names of all the people opting out, the devices and services in question, and a damn purchase receipt. They’re one step away from wanting your passport and your firstborn child.

Highlights of Linux kernel 6.8 include LAM (Linear Address Masking) virtualization and guest-first memory support for KVM, a basic online filesystem check and repair mechanism for the Bcachefs file system introduced in Linux kernel 6.7, support for the Broadcom BCM2712 processor in Raspberry Pi 5, AMD ACPI-based Wi-Fi band RFI mitigation feature (WBRF), zswap writeback disabling, fscrypt support for CephFS, a new Intel Xe DRM driver, and a multi-size THP (Transparent Huge Pages) sysfs interface. ↫ Marius Nestor at 9to5Linux There’s way more going on in this new release, of course, such as further Rust support, for instance in the Loongson architecture, additional support for tons of newer Intel processors , specific support patches for various laptops, and so, so much more.

From the beginning, time zone rules were a component in Mainline, called Time Zone Data or tzdata module. This integration allowed us to react more quickly to government-mandated time zone changes than before. However until 2023 tzdata updates were still bundled with other Mainline changes, sometimes leading to testing complexities and slower deployment. In 2023, we made further investments in Mainline’s infrastructure and decoupled the tzdata module from the other components. With this isolation, we gained the ability to respond rapidly to time zone legislation changes — often releasing updates to Android users outside of the established release cadence. Additionally, this change means time zone updates can reach a far greater number of Android devices, ensuring you as Android users always see the correct time. ↫ Almaz Mingaleev and Masha Khokhlova This is equal parts boring and equal parts amazing. The amount of work developers have to put into making sure timezones work is astonishing, and the fact that a large chunk of it is done by volunteers is even more impressive.

Here you can find everything there is to know about the first version of Windows. ↫ David Simunič And they truly mean everything. This is an exceptional amount of information about Windows 1.0.

A powerful House committee advanced a bill on Thursday that could lead to a nationwide ban against TikTok on all electronic devices, renewing lawmakers’ challenge to one of the world’s most popular social media apps and highlighting unresolved fears that TikTok may pose a Chinese government spying risk. The measure that sailed unanimously through the House Energy and Commerce Committee would prohibit TikTok from US app stores unless the social media platform — used by roughly 170 million Americans — is quickly spun off from its China-linked parent company, ByteDance. ↫ Brian Fung at CNN TikTok obviously needs to be banned. It’s an extension of a genocidal, totalitarian government that has no place on our our phones. Yes, I understand Facebook, Apple, Google, Microsoft also collect vast amounts of data, but at least they are (nominally) beholden to our legal systems, and while there is, of course, a vast power imbalance between us as individuals and them as megacorporations, it’s still nowhere even close as to being an arm of a totalitarian government – they’re just not comparable. China’s state surveillance tools have no place on our devices.

Every window system has windows, as an entity. Usually we think of these as being used for, well, windows and window like things; application windows, those extremely annoying pop-up modal dialogs that are always interrupting you at the wrong time, even perhaps things like pop-up menus. In its original state, X has more windows than that. Part of how and why it does this is that X allows windows to nest inside each other, in a window tree, which you can still see today with ‘xwininfo -root -tree‘. One of the reasons that X has copious nested windows is that X was designed with a particular model of writing X programs in mind, and that model made everything into a (nested) window. Seriously, everything. In an old fashioned X application, windows are everywhere. Buttons are windows (or several windows if they’re radio buttons or the like), text areas are windows, menu entries are each a window of their own within the window that is the menu, visible containers of things are windows (with more windows nested inside them), and so on. ↫ Chris Siebenmann This is wild.

Fedora Workstation has long defaulted to using GNOME’s Wayland session by default, but it has continued to install the GNOME X.Org session for fallback purposes or those opting to use it instead. But for the Fedora Workstation 41 release later in the year, there is a newly-approved plan to no longer have that GNOME X.Org session installed by default. ↫ Michael Larabel Expect more and more of the major distributions to abandon X.org completely. For the KDE version of Fedora, X.org will be dropped entirely in Fedora 40 already, so one release earlier.

The European Union’s Digital Markets Act (DMA) comes into force this week for companies who have been designated. Today, we are sharing some more details about the changes we are making to comply, following product testing we announced earlier this year. ↫ Oliver Bethell on the official Google blog This is Google’s overview of the changes it’s implementing to comply with the DMA, some of which the company already announced months ago. Google’s changes don’t have as much of a direct, noticeable impact as some other company’s changes, mostly since a lot of the more impactful consequences of the DMA, such as allowing sideloading and alternative application stores, were already allowed on Android. Other changes, like to Search, will take longer to be noticed. The one thing that stands out is the tone – compared to Apple’s communication around the DMA. Whereas Apple sounds like a petulant whiny toddler, Google sounds constructive, to the point, and, well, like an adult. That doesn’t mean Google’s post isn’t also full of shit in places, but at least they’re being grown-ups about it.

You heard it here first folks: systemd is coming to postmarketOS! As a mobile oriented OS, our main goal has always been to work for everyone. From technical folks to casual users. postmarketOS should have all the benefits you expect from a Linux based distribution, such as being free software, respecting your privacy, getting updates until your device physically breaks, respecting your attention and not shoving advertisements in your face. Your phone should be a tool you use, not the other way around. This is of course not an easy task, one of the main blockers we found as we collaborate more closely with KDE and GNOME developers is that they have a hard time with our OpenRC-based stack. In order to get KDE and GNOME working at all, we use a lot of systemd polyfills on top of OpenRC. So while we are technically “not using systemd”, in practice we already do use a large chunk of its components to get KDE and GNOME running, just different versions of those components. While we are very grateful for everybody who works on these polyfills, we must point out that most aren’t a full replacement, and take additional effort to support and maintain. As much as we might want to romanticise the idea of spending 6, 12, 24 months attempting to come up with an even vaguely competitive alternative to systemd, we would quite simply rather be working on making postmarketOS better. ↫ postmarketOS blog This is the sensible choice to make, and I’m glad they made it. It makes no sense for a relatively small project that already has to deal with the difficulties of supporting smartphones to also have to deal with shoehorning the smartphone variants of GNOME and KDE into an init system they’re not at all made for.