- wlug - list.wlug.org.nz

slowroads.io
by Lawrence D'Oliveiro 09 Apr '25

09 Apr '25

Found this website which does ... nothing, really. No points to win, no money to pay, no prize, no goal, just drive ... on and on ... with various choices of vehicle and terrain (including some off-Earth). Seems a paid version is being promised for Steam, but in the meantime ... just enjoy your sophisticated Web browser generating absolutely pointless real-time 3D graphics.

1 0

Ubuntu 25.04 “Plucky Puffin” Enters Public Beta Testing with Linux 6.14, GNOME 48
by Peter Reutemann 09 Apr '25

09 Apr '25

'Canonical released today the beta version of the upcoming Ubuntu 25.04 (Plucky Puffin) release for public beta testing, so it’s time to take a look at what to expect from the final release. Powered by the recently released Linux 6.14 kernel and featuring the latest and greatest GNOME 48 desktop environment, Ubuntu 25.04 (codename Plucky Puffin) promises many goodies like the triple buffering feature from Ubuntu, Papers as the default document viewer replacing Evince, and BeaconDB-powered geolocation services. The Ununtu Desktop installer received a new option to replace an existing Ubuntu installation and improvements to dual boot user experience with a focus on BitLocker-protected Windows systems. Users can now install Ubuntu alongside existing BitLocker partitions if enough unallocated space and dual boot support is now available for encrypted installations and other advanced scenarios. Netplan received support for wpa-psk-sha256 Wi-Fi connections, support for configuring routing-policy on the NetworkManager backend, and support for a new functionality in systemd-networkd-wait-online to wait for DNS servers to be configured and reachable before considering an interface to be online.' -- source: https://9to5linux.com/ubuntu-25-04-plucky-puffin-enters-public-beta-testing… Cheers, Peter

1 0

Akamai becomes the official distributor of the Linux kernel
by Peter Reutemann 09 Apr '25

09 Apr '25

Open Source watch reports: 'When I was a young--well, younger anyway--squirt, I ftped my Linux kernel code from Ted T’so, one of the first Linux kernel developers, personal PC, tsx-11.mit.edu. I was glad to do it! Before T'so set up his repository, you had to download the files from Linus Toravalds' machine in Helsinki, Finland, which was s l o w. Mind you, at the time, I recall I downloaded it at a "blazing" fast 64 Kilobits per second (Kbps) over an ISDN line. Hey, it was great in its day. Things have gotten orders of magnitude faster since those days! Now, Akamai, the well-known content delivery network (CDN) and cloud company, has announced a multi-year partnership with the Linux Kernel Organization. This collaboration aims to provide critical infrastructure support for the development and distribution of the Linux kernel, ensuring uninterrupted access for its global network of developers. Akamai will leverage its infrastructure to support kernel.org, the primary platform for Linux kernel source code distribution. This partnership is crucial for maintaining Linux security and performance.' -- source: https://opensourcewatch.beehiiv.com/p/akamai-becomes-the-official-distribut… Cheers, Peter

1 0

20 Years Of Git
by Lawrence D'Oliveiro 08 Apr '25

08 Apr '25

The Git version control system for software development is now 20 years old <https://www.tomshardware.com/software/git-turns-20-as-we-celebrate-decades-…>.

1 0

Comparison Of Python Asyncio-Supporting Web Frameworks
by Lawrence D'Oliveiro 08 Apr '25

08 Apr '25

Trying to decide whether Quart or Starlette was the better bet for a higher-level web framework, I came across this comparison, from just a few years ago, of those two and some other possibilities at different levels <https://www.laac.dev/blog/should-you-use-asyncio-next-python-web-applicatio…>. As far as I can tell, it’s only slightly out of date: the Stripe issue they link to shows that that now includes async support for its Python API.

1 0

The Rise Of “Frankenstein” Laptops In New Delhi’s Repair Markets
by Lawrence D'Oliveiro 08 Apr '25

08 Apr '25

India has long had a, shall we say, “informal engineering” culture, where backstreet operators put together improvised machinery of various kinds from whatever parts are available. Now this extends to assembling working laptops out of the parts of broken ones <https://www.theverge.com/tech/639126/india-frankenstein-laptops>. This allows Indians on low incomes (which is much of the country) an alternative to unaffordable new-built machines. There is a downside to these operations, and that is the health risks from exposure to toxic materials. Seems the Indian Government is becoming aware that it can be helpful to these homegrown industries if it passed some good right-to-repair laws, as is happening in many Western countries. One question that isn’t answered in the article is: what OS are these recycled/refurbished machines running? I can’t imagine that Microsoft would offer Windows licences for them at anything resembling OEM prices. And I don’t think the company would accept that there is such a thing as a “secondhand” Windows licence.

1 0

Open-Source Tool Designed To Throttle PC and Server Performance Based On Electricity Pricing
by Peter Reutemann 04 Apr '25

04 Apr '25

'Robotics and machine learning engineer Naveen Kul developed WattWise, a lightweight open-source CLI tool that monitors power usage via smart plugs and throttles system performance based on electricity pricing and peak hours. Tom's Hardware reports: The simple program, called WattWise, came about when Naveen built a dual-socket EPYC workstation with plans to add four GPUs. It's a power-intensive setup, so he wanted a way to monitor its power consumption using a Kasa smart plug. The enthusiast has released the monitoring portion of the project to the public now, but the portion that manages clocks and power will be released later. Unfortunately, the Kasa Smart app and the Home Assistant dashboard was inconvenient and couldn't do everything he desired. He already had a terminal window running monitoring tools like htop, nvtop, and nload, and decided to take matters into his own hands rather than dealing with yet another app. Naveen built a terminal-based UI that shows power consumption data through Home Assistant and the TP-Link integration. The app monitors real-time power use, showing wattage and current, as well as providing historical consumption charts. More importantly, it is designed to automatically throttle CPU and GPU performance. Naveen's power provider uses Time-of-Use (ToU) pricing, so using a lot of power during peak hours can cost significantly more. The workstation can draw as much as 1400 watts at full load, but by reducing the CPU frequency from 3.7 GHz to 1.5 GHz, he's able to reduce consumption by about 225 watts. (No mention is made of GPU throttling, which could potentially allow for even higher power savings with a quad-GPU setup.) Results will vary based on the hardware being used, naturally, and servers can pull far more power than a typical desktop -- even one designed and used for gaming. WattWise optimizes the system's clock speed based on the current system load, power consumption as reported by the smart plug, and the time -- with the latter factoring in peak pricing. From there, it uses a Proportional-Integral (PI) controller to manage the power and adapts system parameters based on the three variables.' -- source: https://hardware.slashdot.org/story/25/04/03/0110212 -- blog: https://www.naveen.ing/cli-for-smartplugs/ -- github: https://github.com/naveenkul/WattWise Cheers, Peter

1 0

EndeavourOS Mercury Neo Launches with KDE Plasma 6.3, NVIDIA 570, and Mesa 25
by Peter Reutemann 02 Apr '25

02 Apr '25

'The EndeavourOS team announced today the release and general availability of EndeavourOS Mercury Neo as a maintenance update to the EndeavourOS Mercury release addressing various issues and updating core components. EndeavourOS Mercury landed on February 10th, 2025, powered by Linux kernel 6.13 and featuring the KDE Plasma 6.2.5 desktop environment on both the live environment and the offline installation option. EndeavourOS Mercury Neo is here to bump the kernel to Linux 6.13.7 and the live session to KDE Plasma 6.3.3. In addition, this release improves the installation to automatically create a 2GB EFI partition instead of a 1GB partition when choosing systemd in the auto-install option. According to the devs, this change will give users more space and freedom to install multiple kernels and other desirable options. EndeavourOS Mercury Neo also removes the obsolete NVIDIA options from the NVIDIA boot menu, fixes the Arch Linux mirror ranking bug, and removes the xwaylandvideobridge package from the installation script since it was removed upstream. Moreover, it updates the NVIDIA graphics driver to version 570.124.04, the Mesa graphics stack to version 25.0.1, the Calamares graphical installer to version 25.02.2.1-2, the Mozilla Firefox web browser to version 136.0.2, and the XOrg Server display server to version 21.1.16. EndeavourOS Mercury Neo is available for download right now from the official website. Since EndeavourOS follows a rolling-release model where you install once and receive updates forever, existing users need only to update their installations by running the sudo pacman -Syu command in the Terminal app.' -- source: https://9to5linux.com/endeavouros-mercury-neo-launches-with-kde-plasma-6-3-… Cheers, Peter

1 0

Linux Kernel Might Get Smarter Reboots
by Peter Reutemann 01 Apr '25

01 Apr '25

'Something interesting recently emerged on the Linux kernel front—a new patch series titled “Live Update Orchestrator,” authored by Google’s engineer Pasha Tatashin and built on top of an earlier set of patches commonly referred to as the KHO v5 patch series. It aims to enable smooth kernel updates—referred to as “Live Update”—so that certain devices remain fully operational during the transition from an old kernel to a new one. Essentially, the innovative Live Update Orchestrator (LUO) subsystem intends to minimize system downtime by preserving device states across a reboot, particularly benefiting dynamic cloud environments where even minor disruptions can be unwelcome. According to the developers, this approach uses a state-machine mechanism to orchestrate the transition. The LUO subsystem tracks progress through several states—“normal,” “prepared,” and “updated”—and ties them together through callback APIs. These callbacks allow other kernel subsystems (e.g., KVM, IOMMU, interrupts, the new dev_liveupdate device layer, and memory management) to integrate seamlessly into the live update workflow.' -- source: https://linuxiac.com/linux-kernel-might-get-smarter-reboots/ Cheers, Peter

1 0

Google makes Android development private, will continue open source releases
by Peter Reutemann 27 Mar '25

27 Mar '25

'Google is planning a major change to the way it develops new versions of the Android operating system. Since the beginning, large swaths of the software have been developed in public-facing channels, but that will no longer be the case. This does not mean Android is shedding its open source roots, but the process won't be as transparent. Google has confirmed to Android Authority that all Android development work going forward will take place in Google's internal branch. This is a shift from the way Google has worked on Android in the past, which featured frequent updates to the public AOSP branch. Anyone can access AOSP, but the internal branches are only available to Google and companies with a Google Mobile Services (GMS) license, like Samsung, Motorola, and others. According to the company, it is making this change to simplify things, building on a recent change to trunk-based development. As Google works on both public and private branches of Android, the two fall out of sync with respect to features and API support. This forces Google to tediously merge the branches for every release. By focusing on the internal branch, Google claims it can streamline releases and make life easier for everyone. When new versions of Android are done, Google says it will continue to publish the source code in AOSP as always. Supposedly, this will allow developers to focus on supporting their apps without keeping track of pending changes to the platform in AOSP. Licensed OEMs, meanwhile, can just focus on the lively internal branch as they work on devices that can take a year or more to launch.' -- source: https://arstechnica.com/gadgets/2025/03/google-makes-android-development-pr… Cheers, Peter

1 0