Recent Changes - Search:
NTLUG

Linux is free.
Life is good.

Linux Training
10am on Meeting Days!

1825 Monetary Lane Suite #104 Carrollton, TX

Do a presentation at NTLUG.

What is the Linux Installation Project?

Real companies using Linux!

Not just for business anymore.

Providing ready to run platforms on Linux

Show Descriptions... (Show All) (Two Column)

LWN.net

  • [$] The campaign to push Northstar into Linux distributions
    There is not a broad selection of mature, open-source web-browser enginesfor Linux users. Most of the browsers available for Linux are based on one ofjust three projects: Chromium's Blink, Firefox'sGecko, or WebKit. A new entrant wouldgenerally be seen as a welcome alternative, but the recent campaign to push oneof the LLM-written Nordstjernen browsersinto Debian and Arch Linux has raised some questions aboutthe project's development and security processes.


  • Redox OS ring buffers project summary
    The Redox OS project, which is aUnix-like microkernel-based operating system written in Rust, has published a report on the workthat it has done in the last year to implement io_uring-likeI/O.

    Last year, the Redox team received a grant to develop io_uring-like RingBuffer support at the system task level, as a first step towards ring buffercommunications between the application and the majority of system services. Thisphase of the work finished up in September, as the last pieces were put inplace.

    [...] In addition to implementing the Ring Buffer machinery for our systemservices and drivers that can support it, an io_uring andliburing-like API for applications was completed anddemonstrated. There was also substantial work done on support crates, includingan async executor for drivers.

    And there was some very exciting work on various performance improvements, toallow much faster switching between applications and their system services. ButI will let the team tell you all the technical details.



  • Security updates for Wednesday
    Security updates have been issued by AlmaLinux (emacs, thunderbird, and xdg-dbus-proxy), Debian (bind9, openjdk-21, pdns, php-mongodb, and thunderbird), Fedora (brotli, chromium, clevis, eog, flatpak, ghostscript, kernel, libinstpatch, libreswan, mingw-freetype, mingw-gstreamer1, mingw-gstreamer1-plugins-bad-free, mingw-gstreamer1-plugins-base, mingw-gstreamer1-plugins-good, openssh, perl-Alien-Brotli, perl-DBI, python3.12, rust-onefetch, stargz-snapshotter, util-linux, and webkitgtk), Mageia (cifs-utils, libxml2, packages, perl-Cpanel-JSON-XS, perl-Text-CSV_XS, sogo, util-linux, and weechat), Oracle (brotli, firefox, flatpak, gcc-toolset-15-gcc, kernel, libreswan, nodejs:22, nodejs:24, python-urllib3, skopeo, and xdg-dbus-proxy), Slackware (proftpd), SUSE (azure-storage-azcopy, containerd, corepack24, grok-build, ImageMagick, libsoup-2_4-1, matrix-synapse, podman, psqlODBC, python, python-M2Crypto-doc, python-Twisted-doc, and xen), and Ubuntu (authd).


  • Robinson: Raspberry Pi 5 on Fedora
    Peter Robinson has written a blog post aboutthe current state of Fedora support for Raspberry Pi 5devices. According to Robinson, the upcoming Fedora 45 release willwork—with caveats—onall variants of the Raspberry Pi Model 5B; theCompute Module 5 and Pi 500+ are still works in progress.For Fedora 44 release you need to have a temporary workaround when booting. Ifyou update to the latest kernel/firmware straight away this isn't then neededbeyond the first boot. The workaround isn't needed for Fedora 45 so if you'regoing to try this out I suggest you go and grab your favourite flavour of Fedorafrom the Fedora 45 release candidates and jump straight in there! You will getan accelerated desktop with storage/network/USB. There's not currently anysupport for sound and a number of other things.
    See Robinson's post for instructions on creating an Fedora image to use witha Raspberry Pi 5.



  • [$] Guidelines for panics in kernel code
    Alexandre Courbot spends most of his time working on the kernel doing codereviews. Recently, he's been wondering about what the standards should be forwhen Rust code is allowed to panic, and how it should do error handling moregenerally. Unlike many of the other talks at Kangrejos 2026, his talk was notpresenting some existing work, but rather hoping to solicit opinions on thetopic from the assembled Rust for Linux developers. He brought along a collection of trickycases that he had run into recently to prompt discussion.


  • Security updates for Tuesday
    Security updates have been issued by AlmaLinux (bind, bind9.18, brotli, buildah, container-tools:4.0, container-tools:rhel8, firefox, flatpak, freeipmi, gcc, golang, grafana, httpd, kernel, kernel-rt, libreswan, libX11, lrzsz, nodejs:14, nodejs:18, oci-seccomp-bpf-hook, podman, python-urllib3, python3.9, python38:3.8 and python38-devel:3.8, skopeo, thunderbird, xorg-x11-server, and xz), Debian (inkscape, swupdate, thunderbird, and valkey), Fedora (brotli, dolphin, helix, kernel, libical, mingw-python3, nsd, perl-Alien-Brotli, perl-Plack, perl-Plack-Middleware-ReverseProxy, rust-dua-cli, rust-gengo-bin, rust-gitui, stgit, unshield, and webkitgtk), Mageia (evolution, freetype2, ghostscript, kronosnet, libde265, libical, libjxl, packages, perl-DBI, perl-ExtUtils-Typemaps-Default, perl-Imager, vim, and webkit2), Oracle (bind, bind9.18, brotli, buildah, ca-certificates, firefox, flatpak, freeipmi, grafana, httpd, kernel, libreswan, libX11, lrzsz, nodejs22, nodejs24, nodejs:22, oci-seccomp-bpf-hook, perl-DBI:1.641, perl:5.32, postfix, postgresql16-pgvector, postgresql18-pgvector, python3.9, skopeo, unbound, xorg-x11-server, and xz), Red Hat (grafana, grafana-pcp, python3.12-urllib3, and python3.14-urllib3), SUSE (ca-certificates-mozilla, chromium, gn, cifs-utils, containerd, cpupower, cyrus-sasl, gcc13, gcc7, go1.26, go1.27, google-osconfig-agent, kernel, kubernetes-old, libsoup, libX11, libXi, openssh, podman, python-nltk, python-PyJWT, python-social-auth-core, rekor, runc, suseconnect-ng, and unbound), and Ubuntu (brotli and nginx).


  • [$] Python's experimental JIT to be removed
    Python's experimentaljust-in-time (JIT) compiler, which was added to CPython in 2024 for the 3.13 release,is on its way out. In June, the Python steering council announcedthat it was pausing work on the JIT in CPython's main branch until there was anaccepted Python EnhancementProposal (PEP) that addressed concerns about maintenance, compatibility, andset clear success metrics as well as a timeline for completion. After creatingPEP 836 ("JIT Go Brrr: ThePath to a Supported JIT Compiler for CPython")to try to meet the council's request, and after months of discussion, theJIT maintainers have withdrawn the PEP. For now, it appears that development onthe once-promising project has come to an end.


  • Two stable kernels for Monday
    Greg Kroah-Hartman has announced the release of the 7.2.13 and 6.18.59 stable kernels. Each contains a number offixes throughout the tree. Users are advised to upgrade.



  • Systemd adds support for components written in Rust
    Christian Brauner has announced that hehas merged supportfor writing leaf components of systemd in Rust. Rust will be used only for newleaf components, existing code is not being ported to Rust and nothing thatother components depend on is written in Rust.

    Brauner said that theproject would like to move forward with Rust support in core systemd, "butthere are several blockers in Rust's support for dynamic libraries whichprevents us from doing that without massively bloating every binary webuild". Assuming all goes well, it seems likely this work will appear in thesystemd v263 release expected in December.


  • Security updates for Monday
    Security updates have been issued by AlmaLinux (ca-certificates, cockpit-machines, container-tools:4.0, expat, flute, libbase, libfonts, libformula, liblayout, libloader, libreoffice, librepository, libserializer, pentaho-libxml, pentaho-reporting-flow-engine, and sac, golang-github-openprinting-ipp-usb, grafana-pcp, hplip, kernel, nodejs:14, nodejs:18, openssl, php:7.2, php:7.3, php:8.0, php:8.1, podman, postgresql16-pgvector, postgresql18-pgvector, and python39:3.9 and python39-devel:3.9), Debian (brotli, caddy, imagemagick, libdatetime-timezone-perl, libheif, openjdk-17, openssl, thunderbird, tzdata, varnish, and xdg-dbus-proxy), Fedora (btrfs-backup-ng, chromium, dotnet10.0, dotnet8.0, dotnet9.0, firefox, gegl04, GitPython, ImageMagick, jfrog-cli, libindi, mingw-libpng, mingw-LibRaw, mingw-python-lxml, mupdf, nix, openssh, perl-Badger, perl-CLI-Simple, perl-Cpanel-JSON-XS, perl-CSS-Inliner, perl-Encoding-FixLatin, perl-HTML-Query, perl-Markdown-Render, perl-Text-CSV_XS, perl-Text-Markdown-Discount, pgbouncer, php-pecl-mongodb2, podofo, rt, and thunderbird), Mageia (bind, bluez, iperf, kernel-linus, and nss, rootcerts), Oracle (ca-certificates, cockpit-machines, expat, go-toolset:ol8, golang-github-openprinting-ipp-usb, grafana, grafana-pcp, httpd, iperf3, openssh, and podman), Red Hat (freeipmi), and SUSE (alloy, amazon-ecs-init, aspell, aws-iam-authenticator, ca-certificates-mozilla, cifs-utils, container-suseconnect, cosign, cpupower, docker, elemental3, emacs, expat, fetchmail, ffmpeg-7, firefox-esr, ghostscript, gimp, glibc, go1.26, go1.27, google-osconfig-agent, guava, haproxy, helm, iscsiuio, jfrog-cli, kernel, kernel-devel, krb5, kubernetes, libmodplug, libsbc1, libvpx-devel, libxls-devel, mozilla-nss, mozillafirefox, openssh8.4, openssl-3, php8, python, python-base, python-doc, python-weasyprint, python311, python312, python313, python313-CairoSVG, python313-Django, python313-multidict, python313-sglang, python313-urllib3_1, python313-vllm, python314, python315, rabbitmq-server, rclone, rpcbind, squid, trivy, wpa_supplicant, xorg-x11-server, and xwayland).


LXer Linux News


  • DietPi v10.6 Adds Orange Pi and Odroid Images
    DietPi v10.8 introduces a dedicated WireGuard management utility, named software package identifiers, and an updated HAProxy installation package. The October release also improves network configuration, expands storage device support on Quartz64 platforms, and addresses several bugs affecting system management and applications. DietPi: DietPi is a lightweight, Debian-based operating system0


  • Distro of the Week: Noid Linux KDE Plasma
    Of all the distros available that are based on Void, Algeria's Noid Linux stands out in a few ways. But not the least of which is this: Some might argue that it's the perfect entry point into the Void-based family of distros due to its polished Linux experience while letting the user dive deep when he or she chooses.






  • Ubuntu firmware HWE will prevent issues on older kernel
    Ubuntu is planning a new linux-firmware-hwe package, in an effort to reduce the risk of firmware updates for newer kernels causing problems for users running older ones. On Ubuntu long-term support (LTS) releases, you can stick with the standard (GA) kernel it was released with for the duration of its support period, or you can install the HWE update, which brings newer Linux kernel versions to0



  • Robinson: Raspberry Pi 5 on Fedora
    Peter Robinson has written a blog post about the current state of Fedora support for Raspberry Pi 5 devices. According to Robinson, the upcoming Fedora 45 release will workwith caveatson all variants of the Raspberry Pi Model 5B; the Compute Module 5 and Pi 500+ are still works in progress. For Fedora 44 release you need to have a temporary0


Error: It's not possible to reach RSS file http://services.digg.com/2.0/story.getTopNews?type=rss&topic=technology ...

Slashdot

  • FCC Approves Amazon Leo's $11.5 Billion Acquisition of Globalstar
    The FCC has approved (PDF) Amazon Leo's $11.5 billion acquisition of satellite operator Globalstar, giving the Starlink rival additional infrastructure and spectrum to expand into direct-to-device satellite connectivity. Engadget reports: You may not know Globalstar but have possibly used its services, as the company provides Apple's emergency satellite connectivity for compatible iPhones and Watches. Interestingly, Apple also held a 20 percent stake in Globalstar prior to its takeover. As part of the deal, Leo will power satellite services for supported iPhone and Apple Watch models. Leo, a rival to SpaceX's Starlink, has been active of late. The company recently announced that it has 400 satellites in orbit and revealed last month that it had launched high-quality satellite internet service in Uzbekistan. It's teaming up with Delta to eventually bring satellite internet to flights, as well. Amazon recently added six new Arianespace launches and aims to have more than 3,000 low-earth orbit satellites up in the near future, still well short of SpaceX's 11,000 satellites.


    Read more of this story at Slashdot.


  • Google Begins Certifying Registered App Stores For Android
    An anonymous reader quotes a report from Ars Technica: Running an app ecosystem has gotten a lot more complex for Google after its loss in the Epic Games antitrust case. While U.S. users can access app stores in Google Play by court order, international users will use Google's voluntary Registered App Stores program. Google has announced that stores wishing to be part of that program are now free to apply, and support will roll out to some Android devices later this year. App stores accepted into the program will enjoy preferential treatment on the Android platform. Users of approved stores will be able to install apps with a single click, similar to the experience in the Play Store. These stores will also be allowed to update apps silently in the background like Google's store does. [...] Registered App Stores are still happening on Android, but they won't be supported in the U.S. -- you can go to Google Play for alternative stores stateside, but so far, Aptoide remains the only one listed. Those operating Android app storefronts who want to be included in the international program can now review the program and begin the enrollment process. Any store hoping to get approval will have to adhere to a number of requirements, including protecting intellectual property, removing illegal content, and publishing a privacy policy for both users and developers. Google also requires several ongoing security measures to ensure the stores do not give malware easier access to Android devices. As part of the application process, store operators must provide documentation for all these points (in English) and upload copies of all their apps. It costs $10,000 per year to participate in the Android Registered App Stores program, and that fee must be paid before Google will review the application. Google says this fee covers the additional support necessary to run the program. There may also be additional review fees if Google detects a store has a problem with malware. Google plans to roll out support in dozens of nations, which includes most of the world outside of the U.S. and Europe. The program goes live on December 1, but it will only work on Android devices running the latest builds of Android 17. Google says support will start with Android 17 QPR2, which is expected to arrive on Pixel phones in the coming weeks.


    Read more of this story at Slashdot.


  • Astronomers May Have Just Discovered Our Solar System's Sixth Dwarf Planet
    Astronomers using the Vera C. Rubin Observatory have discovered 2026 ED138, a large object beyond Neptune that could become the solar system's sixth recognized dwarf planet if further observations confirm it is massive enough to be round. Located about 46 times farther from the Sun than Earth, the object is estimated to be 600 to 1,500 kilometers wide and had remained hidden because it lies against a particularly crowded field of Milky Way stars. Scientific American reports: The discovery was made by running billions of pieces of data collected by the Rubin Observatory through a search code developed by Center for Astrophysics | Harvard & Smithsonian astronomers Matthew Holman and Kevin Napier. "My first reaction was one of excited disbelief," Holman said in a statement. "Objects like this are very rare, so I immediately started checking whether I or the code had done something wrong." When Holman and his colleague Mario Juric of the University of Washington went to double-check, they found 30 more observations of the object by Rubin that dated to between March and July 2026. Looking at other observation tools, the pair found even more sightings going back to 2016. Together, these data allowed the astronomers to begin mapping out 2026 ED138's orbit. The suspected dwarf planet is about 46 times as far from the sun as Earth, making it even more remote than Pluto, which is just 40 times as far. The object is also tilted off the solar system's plane by around 25 degrees, an arrangement that could be linked to disruptions caused by Neptune's gravitational pull. Initial measurements indicate that 2026 ED138 has a diameter between 600 and 1,500 kilometers (373 and 932 miles), which makes it one of the largest dwarf planet candidates yet detected. But size isn't all that matters: further observations are required to determine if the object has enough mass to be pulled into a round shape, which is a key requirement for a dwarf planet. Despite its size, 2026 ED138 was able to avoid detection for all these years because it's located in a part of the night sky that's crowded with stars whose light drowned it out.


    Read more of this story at Slashdot.


  • CDC Warns of Rising Threat of Drug-Resistant Germs
    The CDC estimates that 19 drug-resistant pathogens cause 9.7 million infections and more than 50,000 deaths annually in the U.S., with resistance continuing to outpace development of new treatments. "The agency considers this problem to be one of our most urgent public health threats," reports NBC News. From the report: The report is the CDC's first comprehensive assessment of these drug-resistant pathogens in seven years. [...] The new report offers a detailed picture of these threats in the U.S., including a ranking of which are the most urgent concerns, based on the number and severity of infections they cause and how easily preventable or transmissible they are. The ranking also factors in how many treatment options exist and their costs. [...] The report estimates that 19 drug-resistant germs cause 9.7 million infections annually in the U.S. Of these, four pathogens are ranked as most worrisome, including the fungus Candida auris and the bacteria that causes gonorrhea, which has become resistant to all but one class of antibiotics used to treat it. The other two urgent threats, according to the CDC, are the bacteria Acinetobacter and Enterobacterales, both of which are resistant to a class of antibiotics widely considered a "last resort" for patients. In addition, the report adds a new bacteria to the list of "concerning" threats, which are considered less worrisome but still warrant monitoring: neisseria meningitidis, which causes meningococcal disease. The rare but life-threatening illness can be prevented through childhood vaccinations, but the bacteria that causes it is slowly developing a resistance to penicillin and another antibiotic called ciprofloxacin. The report also offers some good news: The CDC determined that the bacteria Clostridioides difficile, or "C. diff," which causes diarrhea and inflammation of the colon and can be deadly, is causing fewer cases year over year. The agency downgraded it to a serious threat, whereas it was categorized as urgent in the prior version of the report, which came out in 2019.


    Read more of this story at Slashdot.


  • Greenhouse Gas Levels Set Records In 2025, UN Says
    An anonymous reader quotes a report from CBS News: Greenhouse gas concentrations in the atmosphere rose to record highs in 2025, locking in climate impacts that will persist for centuries, the United Nations said on Tuesday. Levels of the three main greenhouse gases -- the climate-warming carbon dioxide, methane and nitrous oxide -- all rose to unprecedented figures in 2025, the U.N.'s weather and climate agency said. The World Meteorological Organization said the rise would lead to more long-term temperature increases for the planet. The bulletin looks at greenhouse gas concentrations -- the amount of those gases in the atmosphere -- rather than new annual emissions amounts as the world burns more coal, oil and gas. In 2025, carbon dioxide concentrations were at 426.8 parts per million (ppm); methane at 1,948 parts per billion, and nitrous oxide at 339.1 parts per billion. That takes them, respectively, to 153%, 267% and 126% of the pre-industrial levels witnessed before 1750. Of the three major greenhouse gases, CO2 accounts for about 66% of the warming effect on the climate. Around half of the total CO2 emitted each year remains in the atmosphere; the rest is absorbed by the land and oceans. From 2024 to 2025, the global average concentration of CO2 rose by 2.8 ppm -- smaller than the record surge from 2023 to 2024 of 3.6 ppm. WMO senior scientific officer Oksana Tarasova said this reflected the "recovery of the land carbon sinks and reduced fire carbon emissions in 2025 after the strong 2023/2024 El Nino," the naturally occurring, climate-warming weather phenomenon. "However, a 2.8 ppm annual increase is still a substantial addition of carbon to the atmosphere from fossil fuel burning." It is also above the average growth rate for the past decade of 2.6 ppm -- a figure that stood at 0.8 ppm in the 1960s. "Another year, another new record," said WMO Deputy Secretary-General Ko Barrett. "Greenhouse gases are trapping an unprecedented amount of heat in the atmosphere, providing energy for more extreme weather and associated risks to our economies and societies. Further reading: UN Says Breaching 1.5C Warming Limit Is 'Imminent and Unavoidable'


    Read more of this story at Slashdot.


  • Ford's Most Affordable EV Will Offer Built-In Bidirectional Home Charging
    Ford's upcoming $28,350 Fathom electric truck will include a built-in inverter capable of supplying up to 10 kW of AC power to a home, bringing bidirectional charging to a significantly cheaper EV. Owners will still need additional Ford home hardware for features like outage backup and peak-rate energy management, but the company expects the necessary equipment to cost substantially less than its previous-generation system. CNET reports: The upcoming Fathom will be based on what Ford calls its Universal EV Platform, designed with the aid of its 2023 acquisition, startup Auto Motive Power, with bidirectional power on the plate from the start. The hardware required to invert the battery's DC energy to an estimated 10 kW of AC home power will be built into the truck, so it won't require a separate wall-mounted inverter box. Ford says the Fathom's system will meet all applicable UL 1741 requirements and IEEE 1547 standards to ensure the vehicle is safely connected to the grid. As for the actual hardware you plug into your car, all signs point to the Fathom using the NACS plug type pioneered by Tesla and now widely adopted by new EVs in North America. In terms of the communication standard -- the one that governs how AC power is routed from the slim wall box to the car's onboard charger -- that'll be via SAE J3068, a software protocol developed for high-power, heavy-duty AC charging. [...] However, while Fathom's Universal EV Platform eliminates the need for a wall inverter box, it doesn't completely bypass the need for additional hardware to make your home ready to accept bidirectional power. Say you wanted to take advantage of the Home Power Management feature to draw energy into the Fathom's battery when power is cheapest, and then use that energy to offset peak-hour usage when power is most expensive. You'll have to install at least the Ford Home Power Station in your home, at an additional cost. The automaker hasn't specified pricing, but says that it's working to reduce costs and expects this component alone to cost half as much as the first-generation Ford Home Energy system, which debuted at around $1,300. That could put the new system at roughly $650.


    Read more of this story at Slashdot.


  • Growing List of Firms Object to OKX-ICE Tokenized Stock Plans
    Intel, Oracle, IBM and IonQ have joined a growing list of companies objecting to having tokenized versions of their shares traded through OKX and Intercontinental Exchange's blockchain venture, bringing the total number of objections to 26. About 37% of the companies on OKXICE's original list have now opted out, according to CoinDesk. From the report: The four companies were named in an updated public notice (PDF) dated Monday, Oct. 26, from OKXICE, the two firms' joint venture. They join earlier objectors including Microsoft, Alphabet, Goldman Sachs, Cisco and Wells Fargo. The growing list underscores a hurdle for OKXICE and the SEC's new framework for tokenized stock trading: building a market that issuers are willing to join. The agency's five-year "Innovation Exemption" gives qualifying venues room to test round-the-clock blockchain-based trading of stocks, and it also gives public companies an option to block their shares from being offered. OKXICE issued its initial public notice on Oct. 4, outlining plans to use Uniswap v4 liquidity pools on OKX's XLayer blockchain, with transactions settled in stablecoins. The venue would use automated market makers -- software that executes trades through pools of assets rather than matching buyers and sellers through a conventional order book. Under the framework, venues must notify issuers and give them 30 days to object before offering tokenized versions of their shares.


    Read more of this story at Slashdot.


  • Code-Execution Flaw In UEFI Firmware Threatens Most Servers On Planet Earth
    Ars Technica's Dan Goodin reports: Defenders across the world face the burden of responding to yet another botched code-execution vulnerability, this time in boot-time firmware used by most of the world's server vendors and data centers. The vulnerability, with a severity rating of 9.5 out of 10, resides in the TianoCore EDK II, an open source codebase that hardware makers and cloud providers use to create the UEFI firmware that runs during the boot-up sequence. Last year, a representative of the UEFI Forum called (PDF) EDK2 the "preeminent solution / implementation of the UEFI specifications." Virtually all UEFI suppliers (sometimes still called IBVs or independent BIOS vendors), including AMI, Insyde, and Phoenix, use the reference code extensively. Project Mu, Microsoft's hardened EDK2 fork, used the code containing the vulnerable component as well. The vulnerability, tracked as CVE-2026-97631, is a memory-corruption flaw in an ICMP component that attackers can exploit to execute malicious code that runs before the operating system and firmware can implement defenses like Secure Boot, which establishes a chain of trust for all code, including the Trusted Platform Module (TPM), loaded during boot. While final payloads delivered by CVE-2026-97631 have no persistence -- meaning they run only once -- they can give attackers a wide opening to install other payloads that also run each time early in the boot process. The parties that discovered CVE-2026-97631 -- Alex Matrosov of Anthropic and Dan Holmes of Google -- had arranged for it to stay under wraps until a coordinated disclosure that was scheduled for January. AMI, a maker of motherboards and other hardware, published this pull request last month that detailed the vulnerability and included a code fix. Once the post came to the attention of the discovering parties, TianoCore Project members published a public advisory last week. With publicly available patch code, it will be trivial for advanced hackers to learn how the vulnerability is triggered and to build working exploits. Further compounding the urgency, patching UEFI code vulnerabilities in millions of end devices sold and used by thousands of hardware makers and cloud providers is cumbersome and time-consuming.


    Read more of this story at Slashdot.


  • Google's Genie 4 World Model Adds Audio, More Realistic Worlds
    An anonymous reader quotes a report from TechCrunch: Google DeepMind released its newest world model, Genie 4, in research preview on Tuesday. The latest model generates the most photorealistic and interactive worlds yet, allowing users to type prompts mid-simulation to change the scene. The model also generates real-time audio that matches the simulated world, including music, ambient noises, and interactive dialogue. [...] Google released its predecessor, Genie 3, as a research preview a little over a year ago. Aside from being far more photorealistic and featuring audio, Genie 4 allows for freeform edits, like changing the weather or camera angle in real time or adding new people or objects. It can maintain a consistent scene for up to two minutes, double its predecessor's limit, and offers better physics and more human-like characters. Gemini, Google's AI model, is also mo "What we'll increasingly see in the future are these hybrid world models, where you have a combination of Gemini writing code and text, and Genie ingesting that in real time and simulating reality at different levels of abstraction," Tejas Kulkarni, research director at Google, said during a briefing. Genie 4 is now available to select testers, with a broader rollout planned in the coming weeks for Google AI Ultra subscribers. You can watch a demo of Genie 4 on YouTube.


    Read more of this story at Slashdot.


  • Anduril Partners With Qualcomm to Build Laptops On US Soil
    Longtime Slashdot reader fadethepolice writes: Anduril, arguing that its manufacturing capabilities are directly applicable to laptop manufacturing, is starting a project for a fully 100% U.S.-sourced laptop. The computer will use a Qualcomm Snapdragon SoC. I did not see any information about the OS, but I'm assuming that, given the type of processor, this will be Linux-based? "Other companies might design their computers in the U.S., Anduril makes them here,â the Anduril founder Palmer Luckey said in a YouTube video. "We're making parts out of metals that the U.S. knows how to extract, knows how to refine, knows how to process, and knows how to mill at scale at a reasonable price; and that goes for the entire laptop. The same thing goes for the battery technology." The project, called BlueChip, "will take a phased approach, beginning with expanding domestic sourcing and manufacturing, progressing toward eliminating reliance on foreign suppliers, and ultimately establishing an end-to-end American supply chain." The first device is expected in April 2027. A press release with additional information is available here.


    Read more of this story at Slashdot.


Polish Linux

  • Security: Why Linux Is Better Than Windows Or Mac OS
    Linux is a free and open source operating system that was released in 1991 developed and released by Linus Torvalds. Since its release it has reached a user base that is greatly widespread worldwide. Linux users swear by the reliability and freedom that this operating system offers, especially when compared to its counterparts, windows and [0]


  • Essential Software That Are Not Available On Linux OS
    An operating system is essentially the most important component in a computer. It manages the different hardware and software components of a computer in the most effective way. There are different types of operating system and everything comes with their own set of programs and software. You cannot expect a Linux program to have all [0]


  • Things You Never Knew About Your Operating System
    The advent of computers has brought about a revolution in our daily life. From computers that were so huge to fit in a room, we have come a very long way to desktops and even palmtops. These machines have become our virtual lockers, and a life without these network machines have become unimaginable. Sending mails, [0]


  • How To Fully Optimize Your Operating System
    Computers and systems are tricky and complicated. If you lack a thorough knowledge or even basic knowledge of computers, you will often find yourself in a bind. You must understand that something as complicated as a computer requires constant care and constant cleaning up of junk files. Unless you put in the time to configure [0]


  • The Top Problems With Major Operating Systems
    There is no such system which does not give you any problems. Even if the system and the operating system of your system is easy to understand, there will be some times when certain problems will arise. Most of these problems are easy to handle and easy to get rid of. But you must be [0]


  • 8 Benefits Of Linux OS
    Linux is a small and a fast-growing operating system. However, we can’t term it as software yet. As discussed in the article about what can a Linux OS do Linux is a kernel. Now, kernels are used for software and programs. These kernels are used by the computer and can be used with various third-party software [0]


  • Things Linux OS Can Do That Other OS Cant
    What Is Linux OS?  Linux, similar to U-bix is an operating system which can be used for various computers, hand held devices, embedded devices, etc. The reason why Linux operated system is preferred by many, is because it is easy to use and re-use. Linux based operating system is technically not an Operating System. Operating [0]


  • Packagekit Interview
    Packagekit aims to make the management of applications in the Linux and GNU systems. The main objective to remove the pains it takes to create a system. Along with this in an interview, Richard Hughes, the developer of Packagekit said that he aims to make the Linux systems just as powerful as the Windows or [0]


  • What’s New in Ubuntu?
    What Is Ubuntu? Ubuntu is open source software. It is useful for Linux based computers. The software is marketed by the Canonical Ltd., Ubuntu community. Ubuntu was first released in late October in 2004. The Ubuntu program uses Java, Python, C, C++ and C# programming languages. What Is New? The version 17.04 is now available here [0]


  • Ext3 Reiserfs Xfs In Windows With Regards To Colinux
    The problem with Windows is that there are various limitations to the computer and there is only so much you can do with it. You can access the Ext3 Reiserfs Xfs by using the coLinux tool. Download the tool from the  official site or from the  sourceforge site. Edit the connection to “TAP Win32 Adapter [0]


OSnews

  • Oldest GUI application that still runs on Windows 11
    Whats the oldest Windows GUI application you can still run on Windows 11 today, without any modifications? For now, the best answer Boris Popik can come up with is an innocuous application from build 347 of Windows NT 3.1, an early prerelease: CDPLAYER.EXE. You cant go any older than that, because earlier prerelease builds had not yet finalised its PE format and calling convention. Neat find. Popik also mentions a few other contenders, but I wont spoil those here.


  • Another month of Redox improvements
    Another month has crumbled to dust under the oppressive boots of time, so its time for another month of Redox improvements. This past month, Redox build system gained support for Clang, SDL2 saw performance improvements, and WebKitGTK3s HTML layout rendering was fixed. Users of Intel Tiger Lake processors can now enjoy external display hot-plugging, and overall system performance has been improved in a variety of ways. And as always, theres the long lists of kernel, relibc, and driver improvements and fixes as well. Redox keeps making big strides every month, and its definitely one of the few alternative operating systems that actually feels like it might, one day, be an actual contender for general purpose use.


  • Microsoft.UI.Reactor: a C#-first way to build WinUI apps
    Thew day ends in a Y, so Microsoft is launching a new way to build Windows applications. Get excited, Windows application developers! If you caught our session at Microsoft Build 2026 or you’ve been watching the repo, you’ve seen this one taking shape in public for a while now, and a lot has changed since Build. Here’s the longer tour: Microsoft.UI.Reactor, an experimental C# framework that brings the MVU (Model-View-Update) pattern to WinUI desktop apps. No XAML files, no code-behind, no ViewModels. Two things before the fun part. Reactor is experimental: no support policy, no API guarantees, published this early on purpose because we’d rather hear we got the design wrong now than once people have shipped on it. And it is not a replacement for XAML or MVVM, which we’ll come back to. ↫ Alexandre Zollinger Chohfi at Microsofts Dev Blogs At multiple points in the linked blog post, Microsoft underlines that no, Reactor is not going to replace XAML. Im sure Windows developers who learned Win32, Silverlight, WinRT XAML, WPF, UWP, WinUI 2 and 3, and all the others, over the past two decades will feel deeply comforted by Microsofts insistence that Reactor will not replace XAML. Microsoft repeats: this wont replace XAML. They swear.


  • MacOS Extensions pack for the Apple Network Server v1.0
    Weve been following along with Carmen Kaisers Apple Network Server exploits, and by now things are really starting to come together for owners of this machine. When we last left off, the ROM to allow Mac OS to run on the machine which normally runs IBMs AIX, but there were still a number of bugs, limitations, and issues to be worked out. A lot of progress on that front has been made. The good news is, many of the issues with the preproduction ROM in Mac OS can be fixed or worked around in software. So Ive fixed or worked around many of them in software: the MACE Ethernet is fixed, the on-board video is now supported, and the ANS can restart properly back into Mac OS. Plus, because its the preproduction ROM, you can still boot AIX, thus preserving the entire historical reason for Shiners existence. Heres the first cut of that software and how it was developed. ↫ Cameron Kaiser Theres still two issues Kaiser wishes to address  the internal SCSI bays dont work, and the ROM doesnt properly register parity RAM  but the progress here is amazing.


  • CoW, which (sort-of) brings FVWM to Wayland, reaches version 0.4
    Thomas Adam, one of the core developers of FVWM, has been working on CoW for a while now. CoW can best be described as FVWM for Wayland!, which uniquely uses the River compositor. River, in turn, is unique in that it does not combine the compositor and window manager into a single program, allowing for a more traditional X11-like approach. Adam released version 0.4 today, which comes with a load of fixes, changes, and minor improvements, as well as one bigger-ticket item: container windows. This PR introduces the concept of a top-level container window. This means a window can be subdivided into columns and rows (called panes) and can be resized independently of one another. The idea for this has been unashamedly stolen from shod. ↫ Thomas Adam Ive been keeping an eye on CoW ever since I learned about it when it was first released, and at some point soon I want to build a desktop around it for myself.


  • The many many missed opportunities of Sonic 06
    Speaking of games, if youve ever heard anything about or even played Sonic 06, you know this wasnt the most polished entry in the hedgehogs franchise. In fact, its probably one of the worst, and considering the average quality of Sonic games, thats quite an achievement. The team thats working on decompiling the game to make it run on the PC obviously had to dive deep into the games inner workings, and the process learned a lot about why, exactly, the game is so notoriously bad. It really makes you wonder what exactly went wrong? If you look at what limited footage we have of beta content, we can see many effects that aren’t present in the final game. Kingdom Valley had full bump maps, Castle Town had more complex geometry and plants, and New City’s collision implies a very different building layout at some point in development. It turns out, much of the cut content is actually still in the game, but is simply not enabled for performance reasons in vanilla. Even with the cut-back visuals, the game struggles to reach target FPS on real hardware. It’s not surprising that given the crunch Sonic Team were under to get the game out the door, these features were among the first to go. ↫ Isaac Marovitz The article details what, exactly, was turned off for the final release, and its quite an interesting read. Of course, the team intends to try and address many of these issues, and they think they can push the game and its engine to much greater heights.


  • How to run a city builder on 16 MHz
    When thinking about impressive technical achievements in retro games, most people will first point to graphical milestones set by action games like Doom or Quake. Rightfully so, but at least I am personally far more impressed by the early examples of the city builder genre. Simulating whole economies on a large scale with a fraction of today’s power seems impossible if modern builder games even struggle on modern machines. Of course this didn’t stop developers in the past to develop and run city builder games on significantly weaker hardware. The original SimCity for example lists Intel’s 386SX as the CPU in it’s system requirements. A CPU which at the time of it’s launch ran at magnificent 16 MHz. ↫ Lars Thießen Whats even more impressive are some of the other systems the origin al SimCity was ported to, which had even more limited hardware than a 386SX. The Super Nintendo got a SimCity port, which even included fun extras like a Mario statue and Bowser taking up the mantle of the Godzilla disaster, and additional systems the PC version didnt have. Hell, they even worked on a port to the NES, but it was cancelled and thought lost, until a relatively complete and working copy was discovered in 2017. Even this NES version contained features not available in the PC version. Hardware limitations really did breed a lot of innovation back in those days, and sometimes I wonder if programmers and developers could benefit from tasking themselves with working within such limitations today, if only to become a bit more prudent with resources.


  • I cant believe PowerShell is actually good!
    Earlier this year, I needed to learn PowerShell scripting for one Windows-related project, and I have tried it out a few more times on Mac. It has quickly become one of my favorite tools for automation and scripting—taking on jobs that I would have otherwise tried to do with Node.js, Shortcuts, macOS Automator, or heaven forbid, Bash scripts. I get it now. PowerShell is great, even if you dont use it as your shell, and even if youre on Mac or Linux. ↫ Corbin Davenport I dont use the shell often enough on any of my main machines to have much of an idea about the strenghths and weaknesses of PowerShell compared to more traditional shells, but this is definitely not the first time Ive heard a lot of praise for it from people otherwise knee-deep in the UNIX and traditional shell world. There really must be something to this, and since PowerShell is also available on Linux and macOS, its pretty straightforward to give it a go without having to deal with Windows.


  • Garmin revamps and opens up Connect developer API program
    Earlier this year, Garmin closed its Connect API developer program because it was being flooded with AI!-generated applications to the point it couldnt handle them anymore. What made it worse was that half of the applications were never actually used, not even once. It also didnt help that Garmin treated every single application to the program the same way, whether it was from a hobbyist just wanting access to their own data, to a massive corporation developing a popular service used by god knows how many people. Today, the company has relaunched the program, and its been considerably overhauled. While hobbyist use of the API is going to be free  which is way better than it was before  once you hit a thousand users, youre going to have to start paying. Still, Garmin’s shift here towards charging for API access will set a dangerous precedent for the industry. Especially for a company that bills itself as a (or the?) premium sports hardware provider. On the flip side, there’s simply no ignoring the flood of mostly AI apps that take up resources at Garmin and elsewhere to support. Heck, my inbox is flooded with these apps daily requesting reviews. It sounds like when Garmin shut off access to the API last spring, they were seeing inbound API requests at a daily scale that they’d previously only seen over a period of weeks. Simply put, there’s no good answer. ↫ Ray Maker at DC Rainmaker The excesses of the easy availability of AI! code generation impacts the entire industry. At least one good thing has come out of this: hobbyists can now access the Connect API developer program much easier than before.


  • Examining the macOS gcc binary
    If you’ve ever written C (or c++) on a mac, you’ll know that the so-called gcc is just clang in disguise. Most people (fairly) assume that this is just an alias, but this is not true! It’s a binary! Now, what is this binary? I naively assumed that it would just be shelling out to clang but it turns out the answer is more interesting than that. ↫ juliethefoxcoon Its all smoke and mirrors.


Linux Journal - The Original Magazine of the Linux Community

  • Tails 7.15.1 Blocks Compromised HTTPS Certificates in Urgent Privacy Security Fix
    by George Whittaker
    The Tails project has released Tails 7.15.1, an emergency security update addressing a compromised certificate authority that could allow attackers to impersonate legitimate HTTPS websites. Released on October 23, 2026, the update focuses on protecting users against a potentially serious man-in-the-middle attack involving certificates associated with eMudhra, an authority whose intermediate certificates were compromised.

    The emergency release updates Tor Browser to version 15.0.26, addressing CVE-2026-113470, and modifies the distribution's trusted certificate authorities to block all eMudhra certificates. These changes are particularly important for Tails because the operating system routes internet traffic through the Tor network, where malicious exit nodes or other network intermediaries could potentially exploit compromised certificates to impersonate secure websites.

    Unlike a conventional maintenance update, Tails 7.15.1 does not introduce major desktop features, new applications, or significant interface changes. Its purpose is to close a security gap that could undermine the authenticity of HTTPS connections. The developers recommend upgrading promptly, especially for users who rely on Tails for sensitive communications, anonymous research, journalism, or other privacy-critical activities.
    Why Tails 7.15.1 Was Released as an Emergency Update
    Tails, short for The Amnesic Incognito Live System, is a Debian-based Linux distribution designed to help users preserve their privacy and reduce traces of their computing activity. It typically runs from a USB stick and routes internet connections through Tor, making it useful for people who need stronger privacy protections than those provided by a conventional desktop operating system.

    The distribution also emphasizes minimizing persistent data. By default, Tails operates as a live environment and does not retain ordinary session activity after shutdown. Users who need to preserve selected files and settings can configure encrypted Persistent Storage on their USB device, allowing them to maintain important information across sessions without changing the operating system's general amnesic behavior.

    Because Tails is built around privacy and secure communication, problems involving HTTPS certificate validation deserve particular attention. Tor helps obscure the relationship between a user's network location and the websites they visit, but it does not automatically guarantee that every website encountered through an exit node is authentic. HTTPS provides an additional layer of protection by authenticating websites and encrypting communications between the browser and the destination server.
    Go to Full Article


  • Omarchy 4.0.5 Released With Better NVIDIA Laptop Support
    by George Whittaker
    The Omarchy project has released Omarchy 4.0.5, introducing a substantial collection of hardware compatibility improvements, desktop performance optimizations, security fixes, and package updates for the Arch Linux-based operating system. Released on October 18, 2026, the update focuses on refining the existing desktop experience while preparing the distribution for its next major feature release.

    Among the most important changes are improved NVIDIA hybrid graphics support for laptops, an updated Linux 7.2.8 kernel featuring the BORE scheduler, and compatibility improvements for Qt 6.12. The release also resolves boot-related black screens, fixes audio problems affecting certain Dell and USB speaker configurations, corrects Steam graphics driver selection, and improves the reliability of several desktop utilities.

    Although version 4.0.5 is primarily a maintenance release, its improvements extend across many of the components that determine how smoothly a Linux desktop operates. From faster application launches and more responsive desktop panels to stronger security defaults and more reliable hardware detection, the update demonstrates Omarchy's continued emphasis on delivering a preconfigured Linux environment that requires relatively little manual setup.
    Omarchy Continues Refining Its Arch Linux Desktop Experience
    Omarchy is an opinionated Arch Linux-based distribution designed to provide a ready-to-use development and desktop environment built around the Hyprland Wayland compositor. Rather than presenting users with a minimal installation that requires extensive customization, Omarchy combines a carefully selected collection of applications, themes, keyboard shortcuts, and system configurations into a cohesive desktop experience.

    The distribution has attracted attention among developers and experienced Linux users who appreciate keyboard-driven workflows, tiling window management, and the flexibility of Arch Linux without necessarily wanting to configure every component manually. Its desktop environment emphasizes efficient navigation, integrated development tools, and a consistent visual design, while retaining access to Arch's extensive software repositories.

    Version 4.0.5 continues that approach by concentrating on problems that can interrupt everyday workflows. The release improves hardware compatibility, corrects regressions introduced by newer software packages, and reduces unnecessary delays in common desktop operations. Rather than introducing a dramatic redesign, the developers have focused on making the existing environment more predictable and responsive.
    Go to Full Article


  • KDE Plasma 6.8 Marks 30 Years With a Major Shift to Wayland and a More Powerful Linux Desktop
    by George Whittaker
    The KDE Project has officially released KDE Plasma 6.8, introducing a substantial collection of desktop improvements while celebrating three decades of open-source software development. Released on October 14, 2026, exactly 30 years after Matthias Ettrich announced the original KDE project, this anniversary edition brings significant changes to display management, accessibility, graphics performance, remote desktop functionality, system monitoring, and application theming.

    Perhaps the most consequential development is KDE's decision to retire native X11 desktop sessions in Plasma 6.8, completing its transition toward Wayland as the primary display architecture. The release also introduces NVIDIA triple buffering by default, improved HDR support, a more capable remote desktop server, CPU affinity controls in System Monitor, and expanded capabilities for the experimental Union theming engine. These improvements reflect KDE's effort to modernize the Linux desktop while maintaining the customization and flexibility that have defined Plasma for years.

    Plasma 6.8 is therefore more than a commemorative release. It represents an important architectural transition for one of Linux's most widely used desktop environments, with changes that affect both everyday users and developers building applications for the next generation of Linux desktops.
    KDE Celebrates Three Decades of Open-Source Desktop Development
    KDE's history began on October 14, 1996, when Matthias Ettrich proposed creating a consistent graphical desktop environment for Unix-like operating systems. At the time, Linux was becoming increasingly capable as a free operating system, but its graphical experience remained fragmented. Users could choose from several window managers and applications, yet there was no universally integrated desktop environment comparable to the commercial graphical systems available elsewhere.

    The original KDE initiative sought to address that limitation by building a cohesive desktop around the Qt application framework. Over the following decades, the project evolved through several major generations, introducing increasingly sophisticated desktop technologies while expanding into applications, development frameworks, mobile interfaces, and other open-source projects.

    Plasma 6.8 arrives as KDE marks its 30th anniversary, but its development priorities are focused primarily on the future. Rather than introducing a purely cosmetic anniversary edition, KDE has concentrated on modernizing underlying desktop infrastructure while improving accessibility, usability, and performance. The result is a release that combines immediately visible enhancements with architectural changes intended to support future development.
    Go to Full Article



  • Linux Moves Closer to Retiring the x32 ABI After Years of Limited Adoption
    by George Whittaker
    Linux kernel developers are renewing efforts to retire the x32 application binary interface (ABI), a little-used compatibility feature that attempted to combine the advantages of 64-bit processors with the smaller memory footprint of 32-bit applications. A revised patch series submitted on October 8, 2026, proposes the first steps toward disabling the interface, potentially ending support for an architecture experiment introduced more than 14 years ago.

    The latest proposal comes from Sebastian Andrzej Siewior, a Linux kernel developer at Linutronix who has been working on the removal effort throughout 2026. Rather than immediately deleting every component associated with x32, the proposed approach would first prevent the feature from being enabled through normal kernel configuration. This would give remaining users and distribution maintainers an opportunity to respond before the underlying implementation is removed.

    The effort reflects a broader challenge in Linux development: maintaining compatibility with older or rarely used technologies while keeping the kernel manageable, secure, and efficient. Although x32 offered theoretical performance and memory advantages, it never achieved widespread adoption. With conventional x86_64 software dominating modern Linux systems, developers are increasingly questioning whether the additional maintenance burden remains justified.
    Understanding the Linux x32 ABI
    The x32 ABI was introduced with Linux kernel 3.4 in 2012 as an alternative to conventional 32-bit and 64-bit application environments. Its goal was to provide applications with access to the architectural improvements of x86_64 processors while retaining smaller data types and pointers associated with 32-bit software.

    Traditional 32-bit x86 applications use the i386 ABI, which operates with a more limited register set and 32-bit execution conventions. Standard x86_64 applications, meanwhile, benefit from additional general-purpose registers, wider registers, and modern calling conventions, but they normally use 64-bit pointers. Those larger pointers can increase memory consumption in applications that maintain large numbers of pointer-heavy data structures.

    The x32 ABI attempted to offer a compromise. Applications would execute using the x86_64 instruction set and its larger register file while retaining 32-bit integers, long values, and pointers. This programming model is commonly described as ILP32, meaning that integers, long integers, and pointers are all 32 bits wide.

    The distinction can be illustrated by comparing the expected sizes of common C data types:
    Go to Full Article


  • Google's Kage Project Rethinks Linux Kernel Security With Isolated Device Drivers
    by George Whittaker
    Google is exploring a new approach to Linux kernel security that could significantly change how device drivers interact with the operating system. The experimental project, known as Kage, uses compiler-based sandboxing to isolate drivers inside the kernel, potentially limiting the damage caused by memory corruption, programming errors, and exploitable vulnerabilities without requiring drivers to run as separate user-space processes.

    The research was presented at the Linux Plumbers Conference 2026, held October 5–7, with Stanford University and Google researcher Zachary Yedidia discussing how LLVM's Lightweight Fault Isolation (LFI) technology can create restricted execution environments for native kernel code. Unlike conventional isolation techniques, which often depend on separate processes or virtual machines, Kage attempts to preserve the performance advantages of kernel-space execution while reducing the amount of memory individual drivers can access.

    Early prototypes have already demonstrated the concept using NVMe storage, networking, and Wi-Fi drivers. However, Kage remains an experimental research project rather than a feature available in mainstream Linux distributions. Its developers are still investigating performance, hardware access, and compatibility with more complicated drivers, including graphics hardware.
    Why Device Drivers Remain a Major Linux Security Challenge
    Linux device drivers are responsible for connecting the operating system to hardware components, including graphics cards, network adapters, storage controllers, USB devices, and wireless chipsets. Most traditional Linux drivers execute in kernel space, giving them privileged access to system resources and the ability to interact directly with hardware. This architecture is one reason Linux can deliver high performance across such a broad range of devices, but it also creates a significant security challenge.

    When an ordinary application encounters a memory error, the operating system can often terminate that process without affecting the rest of the system. Kernel drivers operate under different conditions. Because they typically share the kernel's address space and privileges, an invalid memory access or exploitable vulnerability can affect unrelated kernel components, potentially resulting in a system crash, privilege escalation, or complete compromise of the operating system.

    The challenge becomes more complicated when considering the enormous number of drivers supported by Linux. Some are maintained by large organizations with extensive testing infrastructure, while others receive contributions from smaller development teams or individual maintainers. Even carefully reviewed drivers can contain bugs, particularly when they interact with complicated hardware, asynchronous operations, and memory-management mechanisms.
    Go to Full Article


  • Speech Synthesis on Linux: Adding a Voice to Scripts and Systems
    by George Whittaker
    Linux users have long had a pragmatic relationship with text-to-speech. The classic open-source engines have been available for years, wired into accessibility tools and the occasional script, dependable but unmistakably robotic. They do the job where the job is simply to convert text to some kind of speech, but the mechanical output has kept them out of anything where the voice actually matters. The arrival of high-quality speech synthesis delivered over an API changes what is possible, letting Linux users add genuinely natural voices to scripts, services, and applications without hosting a heavyweight model themselves.
    The Familiar Trade-Off
    Anyone who has used the traditional Linux speech engines knows the trade-off. They are free, local, and scriptable, which fits the Linux ethos perfectly, but the voices are clearly synthetic. For accessibility and for utilitarian tasks where intelligibility is all that counts, that has been acceptable. For anything user-facing where the quality of the voice shapes the experience, it has not.

    The alternative of running a modern, high-quality speech model locally is possible but comes with real costs: significant computational requirements, model management, and the ongoing maintenance of a demanding piece of infrastructure. For many use cases, particularly on servers, embedded systems, or ordinary workstations, that overhead is disproportionate to the need. This is the gap that an API-based approach fills, offering the quality of a large modern model without the burden of hosting one.
    The API Approach on Linux
    Delivering speech synthesis over an API fits naturally into how Linux users already build things. Rather than installing and maintaining a model, you make a request to a service and receive audio back, which you can then play, save, or pipe into whatever comes next. A Go to Full Article


  • Archinstall 4.5 Released with AArch64 Support, Real-Time Kernels, and Major Installer Fixes
    by George Whittaker
    The Arch Linux project has released Archinstall 4.5, the latest version of its guided text-based installer, bringing expanded AArch64 support, new real-time Linux kernel options, additional translations, security improvements, and numerous fixes for installation workflows.

    Archinstall 4.5 was released on September 29, 2026, roughly three months after Archinstall 4.4. The new version arrives just ahead of Arch Linux's October installation media refresh and has already been packaged as archinstall 4.5-1 for Arch Linux repositories.

    While Archinstall remains optional, it provides users with a guided way to configure an Arch Linux installation without manually performing every step described in the Arch installation guide. Version 4.5 concentrates primarily on hardware support, installer reliability, security, and expanding the range of systems that can use the guided installation process.
    AArch64 Support Gets a Major Upgrade
    One of the biggest changes in Archinstall 4.5 is improved support for AArch64, the 64-bit ARM architecture.

    The installer can now handle GRUB and Limine EFI installations on AArch64 systems. It also gains support for the proper AArch64 root partition type GUID.

    Previously, parts of Archinstall's bootloader configuration were more heavily oriented toward x86_64 installations. The latest changes make its guided installation workflow more useful on ARM64 hardware.

    AArch64 has become increasingly important throughout the Linux ecosystem. The architecture can now be found in cloud servers, development boards, laptops, workstations, and specialized computing platforms.

    Supporting both GRUB and Limine EFI installations gives Archinstall more flexibility when preparing these systems.
    GRUB Can Now Be Installed on AArch64
    GRUB remains one of the most widely used Linux bootloaders, and Archinstall 4.5 extends its installation logic to AArch64 EFI systems.

    This allows ARM64 installations to use a bootloader workflow much closer to what Archinstall already provides on conventional x86_64 UEFI computers.

    The change doesn't mean every ARM device will automatically become compatible with Arch Linux. ARM hardware can still have highly platform-specific firmware and boot requirements.

    It does, however, remove an important Archinstall limitation for AArch64 machines that provide conventional UEFI environments.
    Limine EFI Support Expands to ARM64
    The same architectural expansion applies to Limine.

    Limine is a modern multiprotocol bootloader supported as one of Archinstall's bootloader choices. Archinstall 4.5 extends its EFI installation support to AArch64 as well.
    Go to Full Article


  • systemd 262 Released with Static PID 1, Intel TDX, TPM Improvements, and New Container Features
    by George Whittaker
    The systemd project has officially released systemd 262, delivering another substantial update to the system and service manager used by most major Linux distributions. The final release was tagged on September 22, 2026, following three release candidates earlier in the month.

    Systemd 262 introduces improvements across service management, containers, virtualization, encrypted storage, TPM security, networking, journal recovery, system updates, and unattended installations. Among the most interesting additions are the ability to build systemd as a single statically linked PID 1 binary, Intel TDX support in systemd-vmspawn, Live Update Orchestrator integration, improved TPM-backed encryption, and new fallback unit files embedded directly into the systemd manager.

    The release also contains a rather unusual development safeguard: an AI/LLM canary intended to help identify code contributions generated by AI that haven't been properly reviewed by a human before submission.
    systemd 262 Is Officially Available
    The final systemd 262 source was tagged by systemd developer Luca Boccassi on September 22.

    The upstream tag identifies commit 8cc40e0c5e9234bf45084751ac53b1fbfe70b492 as systemd v262, following release candidates published throughout September.

    The release has already begun reaching Linux distribution development repositories.

    Debian accepted systemd 262-1 into Debian Unstable on September 22, while Fedora has prepared systemd 262 packages for Fedora 45.

    As usual, the speed at which systemd 262 reaches ordinary users will depend on each distribution's update policy.
    systemd Can Now Become a Single Static PID 1 Binary
    One of the most interesting changes in systemd 262 is support for building systemd as a single statically linked PID 1 and executor binary.

    The feature is primarily intended for extremely small container environments.

    Normally, systemd depends on a collection of dynamically linked libraries and supporting components. That architecture makes sense for a complete Linux distribution, but containers sometimes need a much smaller runtime environment.

    The new static configuration makes it possible to create a more self-contained systemd executable suitable for minimal container images.

    These builds avoid dynamically loading optional libraries and use simplified mechanisms for resolving users and groups rather than relying on the complete Name Service Switch infrastructure.

    This doesn't mean normal Linux distributions will suddenly replace their standard systemd packages with a giant static executable. The capability is specifically useful for specialized container and minimal-system deployments.
    Go to Full Article


  • Ubuntu Container Escape Vulnerability Gets Public Exploit Before Kernel Patch Arrives
    by George Whittaker
    Ubuntu administrators running containerized workloads have a new Linux kernel security problem to watch closely. Public exploit code is now available for CVE-2026-80521, a Linux kernel use-after-free vulnerability that can allow an unprivileged process inside a container to escape and obtain root privileges on the underlying host.

    Security firm DepthFirst published its research and exploit on September 22, 2026, demonstrating the attack against Ubuntu 26.04 LTS. The underlying Linux kernel vulnerability had already been fixed upstream on August 6, but as of September 23, Ubuntu's security tracker still lists the main kernel package in Ubuntu 26.04 LTS as "Vulnerable, work in progress," while Ubuntu 24.04 LTS is also listed as vulnerable.

    The situation is particularly important for Docker, Kubernetes, cloud infrastructure, and other environments that run potentially untrusted workloads because the vulnerable kernel functionality can be reached through ordinary operations available inside standard containers.

    There is currently no confirmed evidence that CVE-2026-80521 is being actively exploited in real-world attacks, and the vulnerability isn't listed in CISA's Known Exploited Vulnerabilities catalog. The availability of working public exploit code nevertheless makes the patch gap considerably more important.
    CVE-2026-80521 Is a Linux Kernel Vulnerability
    Although Ubuntu is receiving much of the attention because the newly published exploit specifically targets it, CVE-2026-80521 is fundamentally a Linux kernel vulnerability.

    The problem exists in the kernel's AF_UNIX socket subsystem, specifically within its garbage collection mechanism.

    AF_UNIX sockets, commonly called Unix-domain sockets, provide local inter-process communication between applications running on the same system.

    Unlike conventional network sockets, they don't need to communicate across a network. They are widely used by Linux applications and services for fast communication between local processes.

    They also support passing file descriptors between processes through SCM_RIGHTS messages, and it is the kernel's management of these references that creates the conditions for CVE-2026-80521.
    A Race Condition Leads to Use-After-Free
    At the technical level, CVE-2026-80521 involves a race condition inside the AF_UNIX garbage collector.

    The kernel needs to track references between Unix sockets when file descriptors are passed between processes. Circular references can develop, where one socket effectively references another while that socket references something else in the same group.

    Linux represents these relationships internally and periodically determines which references can safely be removed.
    Go to Full Article


Page last modified on November 02, 2011, at 10:01 PM