The split between /bin and /sbin is not useful, and also unused. The original split was to have “important” binaries statically linked in /sbin which could then be used for emergency and rescue operations. Obviously, we don’t do static linking anymore. Later, the split was repurposed to isolate “important” binaries that would only be used by the administrator. While this seems attractive in theory, in practice it’s very hard to categorize programs like this, and normal users routinely invoke programs from /sbin. Most programs that require root privileges for certain operations are also used when operating without privileges. And even when privileges are required, often those are acquired dynamically, e.g. using polkit. Since many years, the default $PATH set for users includes both directories. With the advent of systemd this has become more systematic: systemd sets $PATH with both directories for all users and services. So in general, all users and programs would find both sets of binaries. ↫ Proposal on the Fedora wiki I think Arch already made this move a while ago, and it seems to make sense to me. There’s a lot of needless, outdated cruft in the directory structure of most Linux distributions that ought to be cleaned up, and it seems a lot more distributions have started taking on this task recently.

The venerable Enlightenment project has pushed out a new release, one mainly focused on bug fixes. There are a few new features, too, however, such as a watchdog thread, enabled by default, to detect mainloop hangs, bigger task previews, an API to play sounds for notifications, a DDC option in backlight settings, and a lot more.

KWin now supports ICC profiles: In display settings you can set one for each screen, and KWin will use that to adjust the colors accordingly. The Plasma 6 beta is already shipping with that implementation in KWin, and with a few additional steps you can play most HDR capable games in the Wayland session. ↫ Xaver Hugl I’ll admit colour management and HDR is a bit outside my wheelhouse, but I do know both are essentially vital for quite a few digital professions, and that support for them on Wayland specifically has been subpar or missing entirely. It seems progress is being made on these topics, and that’s good news.

I also had another set of addressable lights on my desk. While decorating my office for Christmas, I decided to invest some time in connecting them to Home Assistant using the BJ_LED code as a template. It should have been straightforward, right? Well, yes, but also no. ↫ Will Cooke We all love a good reverse-engineering story, especially if it involves bricking Christmas lights.

Advertisements are a part of our lives, including our digital ones. They are in the websites we browse, the search results we receive, and the online news we read. Tired of receiving so many ads, some users try to avoid them by installing an adblocker. But is this a legal practice? Is using adblockers an act of restricting market autonomy, or do they help achieve user freedom? Imagine a scenario where website owners hold copyright over their websites, including whatever ads they place, and could effectively sue for copyright infringement if users were to remove or suppress ads when visiting these websites. This hypothetical situation would enable any website copyright holder to use the legal system to stop any ordinary user on the internet who tries to bypass these ads. This would lead to an internet where unsolicited information and advertisements are imposed on users. Fortunately, recent court decisions have at least prevented this hypothetical from becoming a reality in Germany. ↫ FSFE Good. My position has always been clear: your computer, your rules. Block ads to your heart’s content. Even on OSNews – block away if you want. There are far better ways to support us, anyway (Patreon, Ko-Fi, Liberapay, merch).

CP/M is an operating system dating to the mid-1970s that found its niche giving cheap 8-bit home computers the flexibility, if not the power, of expensive workstations. The Brother SuperPowerNote was a fancy and “very weird” portable typewriter from the early 1990s. David Given ported the former to the latter, creating a freakishly versatile laptop. The source code is on github! ↫ Rob Beschizza And now I’m browsing eBay for electronic/digital typewriters again. There’s so many of them! And they all look so awesome and fun! Please stop me! One day I’ll finally pull the trigger.

Plasma 6 is coming together nicely on the desktop! Coming back from hiatus, I was pleasantly greeted by a much more working session than when I last saw it in May; I have now completely switched over to it on my main machine! On the other hand, there is still a lot of work to do on mobile to prepare it for the Plasma 6 release in February. I will outline the current situation and the work I have done in the past few months in order to make Plasma 6 a possibility for Plasma Mobile. ↫ Devin at espi.dev The linked blog post provides a great overview of the work that is being done and needs to be done on Plasma Mobile for Plasma 6, and I have to say that it’s definitely looking good and I’m quite interested is somehow giving Plasma Mobile a go. The problem, however, is one that’s all too familiar to anyone who’s tried to run anything but Android or iOS as their main mobile operating system over the past 15 years or so: the lack of the kind of applications that you need to be a part of modern society. I don’t like it, but without my banking applications, identity applications I need in Sweden, things like WhatsApp, Signal, Discord – my phone would basically be a curious toy instead of a useful tool. Add needing the best possible smartphone camera to the equation – I have two small kids – and using anything but iOS and Android is simply out of the question. One alternative smartphone operating system knew this, and implemented fairly transparent Android application compatibility – Sailfish – through their Aliendalvik tool. It seems Jonas Dreßler, who works on GNOME Shell for mobile, was curious, and decided to take a closer look at Aliendalvik, to see if there’s anything there that the teams working on bringing KDE and GNOME to smartphones can make something of it. Sadly, Aliendalvik is not open source, so some reverse-engineering was required. The interesting thing here is that due to the fairly standard userspace Sailfish is using, the Android integration is mostly using standard freedesktop APIs to integrate with the host OS: Running Android apps are exposed as individual Wayland surfaces/windows, notifications from Android appear as org.freedesktop.Notification messages on DBus, music player controls are exposed using MPRIS, and even text input for android apps can be provided using the Wayland text input protocol. This means that basically Aliendalvik should work just as well on a standard Linux distribution like Fedora, Arch Linux, or Debian. The Android container can be started using standard linux container tooling and the host integration binaries are compiled for ARM64 and mostly link to various open source Qt libraries. ↫ Jonas Dreßler After a few days of reverse-engineering, hacking, and lots of other hard work, Dreßler managed to get Aliendalvik to work on GNOME Shell running on Arch on a smartphone, with all the integration between the Android applicatins and the underlying Arch installation working, and the code and instructions are up on Github. He also posted a video showing it working, and it’s indeed as impressive as it sounds. Sadly, the elephant in the room here is, of course, the fact that Aliendalvik is not open source. Jolla could potentially offer it for purchase on non-Sailfish Linux-based smartphones, or perhaps even release it as open source entirely, but I’m not entirely sure if Jolla would be interested in any of that. The company is… In a bit of an odd state, and I feel like it’s mostly been in limbo with not as much progress as they once hoped they’d make. Releasing one of their crown jewels as open source seems unlikely. My personal conviction is that if we ever want a Linux smartphone that is somewhat viable but isn’t Android, it’s going to have to be either Plasma Mobile or GNOME Shell on mobile, running on one of the popular, mainstream distributions that already run on ARM, are interested in mobile, and have a huge community to power the whole thing. Things like Sailfish or even Ubuntu Touch, as interesting and impressive as they are, just don’t seem viable to me in the long term when the entirety of the KDE and GNOME communities are working on their own projects.

One of the changes Google is forced to make because of the antitrust trial vs. Epic concerns how sideloading works on Android. Right now, sideloading an app on Android requires users to open an APK and, if the source app is not already approved, follow a link to settings where that option can be enabled before they can return to the installation process. Following the changes outlined in this settlement, Android will be required to simplify this process by condensing it down to one screen. Android will still be able to outline the risks of sideloading on this screen, but it will be a one-step process. The new screen will say: ↫ Ben Schoon at 9to5Google I’m not sure if this is a better approach. The way I have sideloading set up on my Android devices is that only File, Google’s file manager for Android, is allowed to install any APK, so even if, for some reason, I download a harmful APK accidentally through a phishing email or my browser, it will just sit inert in my downloads folder until I were to actively open Files and install said APK. It’s safeguard I most likely don’t need, but I do like having installing APKs limited to just the Google file manager for my own peace of mind. This change would, if I’m reading things correctly, make it so that any application can more easily be given the permission to install APKs, which seems like it’s not going to encourage many more people to intentionally sideload, but will perhaps make people accidentally grant random applications the permission to do so. It’s an odd change, for sure, and I hope there’s some way to disable this if Google implements this outside of the US as well.

Hundreds of technical experts from many of China’s biggest state-owned and private companies, including the Industrial and Commercial Bank of China (ICBC), China Telecom, Meituan, and Baidu, all gathered in Beijing last month. The purpose behind the meeting was for their staff to receive training so they could be certified as developers on Huawei’s Harmony Operation System (OS). While most observers were looking the other way, Huawei has been quietly building an independent Chinese operating system that isn’t subject to U.S. sanctions. In the four years after the telecom giant was banned from using Google apps, the Shenzhen-based company has been making significant strides toward achieving its long-term goal: To dethrone Android and make its HarmonyOS the default operating system in China. ↫ Nina Xiang for Forbes Asia HarmonyOS is poised to succeed in beating iOS and Android where others have failed, if only because the Chinese state is pushing homegrown solutions hard. It’s already hit 10% market share in China, closing in on iOS’ 17%, but still kilometres away from Android’s 72%. However, with both local governments and the government in Beijing enacting all kinds of laws and guidelines to force companies, institutions, and people to switch to homegrown solutions, it wouldn’t surprise me to see this market share climb fast. And that’s actually okay! Setting aside the fact the Chinese government is a genocidal totalitarian surveillance nightmare apparatus, I think it’s entirely understandable, reasonable, and a good investment to have homegrown technology solutions and platforms. I wish the European Union did something similar, but that ship has probably sailed after we let Microsoft gut whatever was left of Nokia after Apple was done with it.

Starting on February 22, 2024, you can no longer use Google Groups (at groups.google.com) to post content to Usenet groups, subscribe to Usenet groups, or view new Usenet content. You can continue to view and search for historical Usenet content posted before February 22, 2024 on Google Groups. In addition, Google’s Network News Transfer Protocol (NNTP) server and associated peering will no longer be available, meaning Google will not support serving new Usenet content or exchanging content with other NNTP servers. ↫ Google Groups Help According to Google, the reason for removing Usenet support is the declining popularity of Usenet, claiming that “much of the content being disseminated via Usenet today is binary (non-text) file sharing, which Google Groups does not support, as well as spam”. I can’t validate that claim, but regardless, relying on Google to access Usenet was never a good idea in the first place. There’s countless proper Usenet clients out there that won’t perform a classic Google rug pull.

You may have seen the news that Red Hat Enterprise Linux 10 plans to remove Xorg. But Xwayland will stay around, and given the name overloading and them sharing a git repository there’s some confusion over what is Xorg. So here’s a very simple “picture”. ↫ Peter Hutterer A more useful visualisation than I expected.

A recent discovery that overclocking AMD’s latest chips blows a fuse to denote the chip has been overclocked has led to slightly misleading claims that it will automatically void the chips’ warranty for any type of failure. However, AMD clarified to Tom’s Hardware that overclocking AMD’s Ryzen Threadripper Pro 7000 (Storm Peak) and non-Pro lineup, among the best workstation CPUs, doesn’t automatically void the processor’s warranty. ↫ Zhiye Liu at Tom’s Hardware Something about these fuses in processors doesn’t sit right with me.

In collaboration with Polar Signals we have committed that beginning with Ubuntu 24.04 LTS, our GNU Compiler Collection (GCC) package will enable frame pointers by default for 64-bit platforms. All packages in Ubuntu, with very few exceptions, will be rebuilt with frame pointers enabled, making them easier to profile and subsequently optimise. “I’ve enabled frame pointers at huge scale for Java and glibc and studied the CPU overhead for this change, which is typically less than 1% and usually so close to zero that it is hard to measure. Frame pointers allow more complete CPU profiling and off-CPU profiling. The performance wins that these can provide far outweigh the comparatively tiny loss in performance. Ubuntu enabling frame pointers by default will be a huge win for performance engineering and the default developer experience”. said Brendan Gregg, computer performance expert and Intel Fellow. ↫ Oliver Smith on the official Ubuntu blog So I guess the very minor performance regression is supposed to be compensated for by optimisations in individual packages that frame pointers will help realise.

Three years after Fortnite-maker Epic Games sued Apple and Google for allegedly running illegal app store monopolies, Epic has a win. The jury in Epic v. Google has just delivered its verdict — and it found that Google turned its Google Play app store and Google Play Billing service into an illegal monopoly. After just a few hours of deliberation, the jury unanimously answered yes to every question put before them — that Google has monopoly power in the Android app distribution markets and in-app billing services markets, that Google did anticompetitive things in those markets, and that Epic was injured by that behavior. They decided Google has an illegal tie between its Google Play app store and its Google Play Billing payment services, too, and that its distribution agreement, Project Hug deals with game developers, and deals with OEMs were all anticompetitive. ↫ Sean Hollister for The Verge Good news, of course, but it does make one wonder why a judge in Epic’s case versus Apple ruled the exact opposite as the jury did today. We don’t yet know what this verdict will mean for Google in a practical sense – that’s up to the judge, and Google intends to appeal, for course – so if consumers will actually see any benefit from this remains to be seen.