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

  • [$] Vendor hooks in the Android kernel
    Since Android's inception, the kernels it has used have divergedsignificantly from the mainline. While many of those differences have beenresolved over time, and the move to the generickernel image has helped to bring Android closer, current devices stillcarry a lot of out-of-tree changes. The preferred form for such changes isby way of vendorhooks. At the 2026 LinuxPlumbers Conference, Todd Kjos ran a fast-paced session in the Androidtrack to discuss vendor hooks and how they are used.


  • KDE releases documentary
    As part of KDE's 30thanniversary celebration, the project has released The KDE Documentary— A Story of Free Software Underdogs (YouTube video):

    The story starts in 1996, when Matthias Ettrich, a student at the Universityof Tübingen, posted to a Usenet group asking for programmers to help build adesktop for Linux. What followed became KDE, one of the largest free softwarecommunities in the world. KDE made Linux usable as a desktop for people whoweren't system administrators, giving it a complete, consistent graphicalenvironment at a time when there was none.

    The film covers the highs and lows of three decades of KDE: the Qt licensingfight and the rivalry with GNOME; the success of KHTML, the browser engine thatbecame the basis of Apple's WebKit and Google's Chrome; and the contentiousrelease of KDE 4 and the rebuild that followed.


  • Ubuntu 26.10 released
    Canonical has announcedthe release of Ubuntu 26.10 ("Stonking Stingray"):

    Ubuntu 26.10 advances enterprise security features, completes the rollout ofthe Rust-based uutils coreutils, and strengthens integrations for userauthentication using Microsoft Entra ID.

    [...] Ubuntu 26.10 also ships with GNOME 51, bringing a smoother, moreresponsive desktop, better display handling, improved accessibility, andrefinements across core applications. In addition, the Ubuntu App Center nowprovides a more consistent experience for managing snaps and debs.

    See the release notesfor a list of new features as well as incompatiblechanges between 26.10 and prior Ubuntu releases.


  • Security updates for Thursday
    Security updates have been issued by AlmaLinux (environment-modules, flatpak-builder, kernel, kernel-rt, librabbitmq, libreoffice, libsoup, mod_auth_openidc:2.3, nodejs:22, nodejs:24, OpenEXR, opentelemetry-collector, pki-core:10.6, postgresql:12, python-tornado, python36:3.6, ruby:3.3, tftp, and xorg-x11-server), Debian (buildstream, firefox-esr, mariadb, and sogo), Fedora (exim, freerdp, python3-docs, and python3.14), Mageia (drakx-installer-images, kernel, kmod-nvidia-current-wopengpu, kmod-virtualbox), Oracle (curl, emacs, environment-modules, flatpak, flatpak-builder, gd, hplip, kbd, kernel, librabbitmq, libreoffice, libxml2, microcode_ctl, mod_auth_openidc:2.3, nodejs:22, OpenEXR, pcre2, perl-DBI, python-tornado, rsyslog, tftp, thunderbird, and xorg-x11-server), Red Hat (compat-libtiff3, firefox, ghostscript, idm:DL1, ipa, kernel, kernel-rt, libtiff, lrzsz, and mariadb-connector-c), Slackware (libarchive), SUSE (amazon-cloudwatch-agent, bind, container-suseconnect, containerd, glibc, google-osconfig-agent, helm, kernel, python312, python313-oletools, python313-openpyxl, python313-orjson, python313-paramiko, python313-pipreqs, python313-py, python313-pycryptodome, python313-pycryptodomex, python313-pydrive2, python313-python-engineio, webkit2gtk3, and xorg-x11-server), and Ubuntu (apache2, bind9, bluez, curl, openssh, python-urllib3, and u-boot).


  • Seven stable kernels for Thursday with fix for critical vulnerability
    Greg Kroah-Hartman has announced the release of the 7.2.11, 6.18.57,6.12.113, 6.6.159, 6.1.190,5.15.223, and 5.10.272 stable kernels. This series includes,among other things, a fix for acritical vulnerability (CVE-2026-99999). Theflaw in skb_checksum_help()would allow an IPv4 packet with bad checksum metadata to "corrupt the networkheader and cause a bunch of mischief" in the words of patch author MichaelS. Tsirkin. As usual, all users are advised to upgrade.



  • [$] LWN.net Weekly Edition for October 15, 2026
    Inside this week's LWN.net Weekly Edition:
    Front: 2026 Maintainers Summit; Rust goals; GCC and LLMs; GCC CFI; systemd; C types in Rust; LTTng; Swap showdown; KDE Linux. Briefs: 64-day certificates; Nix and Lix security; Asterinas 0.19.0; LineageOS 24; KDE 6.8; Python 3.15; Quotes; ... Announcements: Newsletters, conferences, security updates, patches, and more.


  • [$] Collaborating with out-of-tree tracers
    LTTng creator Mathieu Desnoyers seems abit trapped in something of a catch-22.At the 2026 Linux Plumbers Conference(LPC), he led a discussion on the problem he is having in trying tocollaborate with other tracing projects (e.g. ftrace, perf) in the kernel. Thefeedback he has gotten, both over the years and more recently, does notshow a path that would allow him to contribute the 21-year-oldGPLv2-licensed LTTng tracing framework, or, incrementally, features fromit, to the mainline kernel.


  • Linus Torvalds's first LLM-assisted patch series
    At the recently concluded MaintainersSummit, Linus Torvalds said that he had been using a large languagemodel to work on a patch series addressing a longstanding problem; he hasnow postedthat series for review.
    The fairly short series of ten patches basically enhances folio lookup by noticing when folios are hot, and setting a "delay releasing this folio until after a RCU period", and then using that RCU delay it does not just the folio lookup itself under RCU (which we've done forever), but also the actual folio data accesses themselves under RCU. No refcount taking needed for the fastpath where we can just read the data from the folio entirely in an RCU-protected region when the user copy doesn't cause page faults.
    The end result is an order-of-magnitude speedup for a read()-heavybenchmark. Review has already identified a racecondition in the code, though, so further work will be needed.


  • KDE Plasma 6.8 released
    Version 6.8 ofthe KDE Plasma desktop has beenreleased. The The KDE project has timed the release to coincide with the 30thanniversary of Matthias Ettrich's email announcing theproject:
    Unix popularity grows thanks to the free variants, mostly Linux. But still aconsistent, nice looking free desktop-environment is missing. There are severalnice either free or low-priced applications available, so that Linux/X11 wouldalmost fit everybody needs if we could offer a real GUI.
    Notable changes include accessibility improvements, inclusionof the Kup backuptool as part of Plasma, as well as the ability to include system audio andmicrophone input in Spectaclescreen recordings. Plasma 6.8 also drops support for Plasma X11 sessions, as was announcedin November 2025. X11 applications are still supported via XWayland, and KDEapplications will continue to support X11 "for the foreseeablefuture".

    See the KDE wiki for alist of major user-facing changes, and the changelogfor all changes since Plasma 6.7.5.



  • [$] GCC development with large-language models
    After much deliberation, the GCC project recently came up with a policy on the use of largelanguage models for development of the compiler suite. It is somewhatrestrictive, but still leaves room for LLMs in the development process. Atthe 2026 GNU Tools Cauldron,Jeff Law and Kyrill Tkachov discussed how these tools have been useful forthem.


  • Security updates for Wednesday
    Security updates have been issued by AlmaLinux (bind9.18, dovecot, flatpak, gd, jackson-core, jackson-databind, jackson-jaxrs-providers, and jackson-modules-base, kernel, opentelemetry-collector, pcre2, and tftp), Debian (curl and keystone), Fedora (aegisub, arm-none-eabi-binutils-cs, avr-binutils, chromium, curl, firefox, kernel, python-jupytext, and xdg-dbus-proxy), Mageia (apache, freeciv, gnumeric, mingw-gdk-pixbuf, and patool), Red Hat (cockpit-image-builder, fence-agents, firefox, ipa, kernel, kernel-rt, pcre2, python-tornado, qt6-qtdeclarative, thunderbird, and webkit2gtk3), Slackware (expat), SUSE (bind, busybox, containerd, cups-filters, fixme, gimp, glibc, google-osconfig-agent, kernel, libtcnative-2-0, openssh, openssl-3, php8, podman, python-oauthlib, python-PyJWT, python-urllib3, python-virtualenv, python311, python313-jupyter-server, python313-kubernetes, python313-logilab-common, python313-markdown-it-py, python313-markdown2, python313-marshmallow, python313-mpmath, python313-mysql-connector-python, python313-oci-sdk, python313-oic, unbound, wpa_supplicant, xen, and xorg-x11-server), and Ubuntu (kernel, libyaml-perl, linux, linux-aws, linux-aws-fips, linux-aws-hwe, linux-azure, linux-azure-4.15, linux-azure-fips, linux-fips, linux-gcp, linux-gcp-4.15, linux-gcp-fips, linux-hwe, linux-kvm, linux, linux-aws, linux-aws-fips, linux-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-ibm, linux-lowlatency, linux-oracle, linux-realtime, linux, linux-aws, linux-azure, linux-azure-5.4, linux-fips, linux-gcp, linux-gcp-5.4, linux-gcp-fips, linux-hwe-5.4, linux-iot, linux-kvm, linux-oracle, linux-oracle-5.4, linux-raspi, linux-raspi-5.4, linux-xilinx-zynqmp, linux, linux-aws, linux-fips, linux-kvm, linux-lts-xenial, linux-aws-5.4, linux-aws-fips, linux-azure-fips, linux-ibm, linux-ibm-5.4, linux-azure, linux-azure-fde, linux-azure-fips, linux-oracle, and pyjwt).


  • [$] KDE Linux at two
    KDE Linux, the KDE Project's secondstab at creating its own distribution, was first introduced as "Project Banana"at the Akademy conference in 2024 byHarald Sitter. Nate Graham announcedthe first alpha-quality release during Akademy 2025. Graham and Sitterpaired up at Akademy 2026 to provide an update on its progress, lay out plans for refining the distribution toaddress user feedback, and discuss some of the problems that still need to bedealt with. KDE Linux is still not-quite-ready for prime time, but Graham hopesthat it will be suitable for widespread use soon—for an undefined value of"soon".


  • Nix and Lix local root-privilege-escalation vulnerabilities
    The Lix and Nix projects have jointlydisclosed a set of vulnerabilities that can be used to escalate privilegesto root on systems running the Lix or Nix daemons. "All systems that builduntrusted derivations are affected." Releases with fixes from each projectare available today. CVE IDs have not yet been requested. See the announcementfor more details on the vulnerabilities.



  • [$] Owning C types from Rust code
    Rust's system of ownership and borrowed references is convenient when it cancorrectly model a program's needs. TheRust for Linux project has worked toprovide adapters between Rust's semantics and the existing C codein the kernel. At Kangrejos 2026, Andreas Hindborg spoke about apatchseries implementing the next such adaptor: an Ownable trait forrepresenting objects that are allocated in C code, but which Rust code is responsiblefor cleaning up (if not necessarily deallocating) when it is done with them.He hoped to finally reach a consensus on the patch series, after months ofdiscussion on the mailing list.


  • Eisentraut: The reverts will continue until morale improves
    PostgreSQL coreteam member Peter Eisentraut has written a blogpost reflecting on the "unusually high number of features" that havebeen taken out of the upcoming PostgreSQL 19 release since the beta periodbegan.

    Some of the reverted features had significant architectural defects thatwould have been hard to fix quickly and during beta. But there was also a longtail of relatively harmless issues involving various edge cases. In past times,many of these would not have surfaced until much later and we would have fixedthem bit by bit over the subsequent five years. But with LLM-assisted codereview, these kinds of things can get found much faster, and then you're staringat a list of like forty defect reports. And even if each of them requires only athree-line fix on average, there is a fixed overhead to dealing with each ofthese, and then you run out of time. Most if not all of the affected revertedfeatures were written a long time ago when LLM-assisted code review was not asuseful as it is now, meaning that the effective quality bar has been raisedafter the time the feature was written and committed. Unless the capabilities ofLLM-assisted code review keep improving at the current rate, this situationshould sort itself out for future development cycles.

    A corollary of that is that, at least for the most part, as far as I cantell, this situation is not due to "vibe coding". This code was written wellbefore that was a possibility.

    LWN covered the unusuallylarge number of bug fixes required for PostgreSQL 19 features inSeptember.


LXer Linux News


  • Raspberry Pi 5 cluster runs Qwen3-30B-A3B at 15 tokens/s on CPU
    Hellomatik has published a study and a modified distributed-llama implementation for running the Qwen3-30B-A3B language model across four Raspberry Pi 5 boards. Using only the boards’ Arm Cortex-A76 CPUs, the cluster reached a reported decode throughput of 15.143 tokens per second, without GPU or NPU acceleration or CPU overclocking. The setup uses four Raspberry Pi […]




  • Building a Reliable Event-Driven Payment Service With XRP Ledger
    Receiving a transaction notification is only the first step. Production software still has to decide whether that event is safe to turn into application state. A WebSocket callback can arrive in milliseconds. What happens afterward is harder. The XRP Price may be the public-facing metric most people associate with the asset, but developers integrating the XRP Ledger have a different concern. A long-running service has to detect transactions, determine whether their outcomes are final, and update local application state without acting twice or acting too soon.




  • Rustls 0.23.46 Released With Four Security Fixes
    Rustls as the modern TLS library written in the Rust programming language with an emphasis on memory safety is out today with its v0.23.46 release in order to ship four new security fixes...


  • Distro of the Week: Asmi 13.6 Linux
    Asmi - pronounced like "us" and "me, and is Sanskrit and Hindi that means "I am" or "I exist" - is based on Debian 13.6 "Trixie" and provides a lightweight and modern Xfce-based experience with the addition of distro-specific tools to make the Linux experience a good one.


  • Happy 30th Birthday, KDE!
    Today, KDE, one of the largest active free software communities in the world, celebrates its 30th anniversary since German computer science student Matthias Ettrich announced the project on Usenet.












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

Slashdot

  • Uber Begins Self-Driving Robotaxi Trial In Manchester
    An anonymous reader quotes a report from The Guardian: Uber has begun a trial of autonomous vehicles on the streets of Manchester as it looks to bring robotaxis to cities around the UK. The first self-driving cars are operating, using the technology of its partner firms Pony and Verne, with whom Uber recently launched Europe's first autonomous taxi service in the Croatian capital, Zagreb. Uber said it was "excited to take this first step toward making this technology accessible to people across the UK." In social media posts, Verne said it had "started our autonomous vehicle testing in Manchester," while Pony said there were "plans to bring robotaxis to the city" and that testing was under way. The tests involve the company mapping the streets of the city in north-west England with a safety driver behind the wheel and no passengers. Limited passenger services started last month in London, but with a safety driver in the front seat of cars supplied by Wayve under Transport for London's licensing rules for private hire vehicles. The next steps are unclear. Opposition from Uber drivers, their unions and the capital's politicians to the rollout of robotaxis is mounting. The GMB and ADCU unions have both said thousands of drivers jobs will be lost and have called for help for those affected. A critical report from London assembly's transport committee this week called for the government to devolve authority over autonomous taxi services. It said there was "considerable uncertainty about many of the claimed benefits of autonomous passenger vehicles", and fears over the impact on public transport and congestion, as well as safeguarding and accessibility for disabled passengers. There has been no official application to launch passenger services in Manchester so far.


    Read more of this story at Slashdot.


  • Bank of America Hired 1,000 Contractors to Patch Software Flaws Exposed By Anthropic's Mythos
    Bank of America hired 1,000 outside contractors to help patch software vulnerabilities exposed by advanced AI models, including Anthropic's Mythos. The effort added hundreds of millions of dollars in third-quarter expenses. CNBC reports: In an interview after the bank's third-quarter earnings release, [CEO Brian Moynihan] said that earlier this year the company rushed to bolster a wide spectrum of its internal and vendor code using thousands of employees and outside personnel. "That risk is real risk, and that's why when the frontier-type models came out. ... A lot of us sat down and said, 'How do we figure out how to get through this quickly?'" Moynihan told CNBC's Leslie Picker. "We put on 1,000 contractors to help us do the patching work in the second quarter, and those people remain here today, helping us, on top of the 3,000 people we have in that area," he said. The bank spent a "couple hundred million plus" on the software remediation and regulatory issues related to anti-money laundering compliance in the third quarter, Moynihan told analysts earlier Wednesday.


    Read more of this story at Slashdot.


  • Mini Organs Launching to Space For Study On Aging
    Researchers from Mount Sinai, NASA, and Space Tango have launched miniature human hearts and brains to the International Space Station to study how microgravity and radiation affect organs and potentially accelerate aging. "If people are going to be living and working in space, then we need to understand what's going to happen to them," David Sachs, assistant professor of surgery at the Icahn School of Medicine at Mount Sinai, told ABC News. "But also, because it's interesting as a model of accelerated aging for studying people on Earth." From the report: The mini organs launched aboard commercial resupply mission CRS-35 on Tuesday morning from Cape Canaveral Space Force Station in Florida. They are expected to arrive at the International Space Station (ISS) on Thursday. The miniature organs offer researchers a unique opportunity to simulate aging in a much shorter period of time to understand disease and develop treatments. "Six months in space ... is equivalent to about 10 to 20 years of aging on Earth," Kevin Costa, associate professor of surgery at the Icahn School of Medicine at Mount Sinai, told ABC News. Sachs and Costa are sending up to 16 miniature hearts to the ISS to test how they respond to electrical signals and monitor how they may react to near-zero gravity. The technology, which is integrated into a miniature laboratory called CubeLab, was developed by Space Tango and simulates the natural environment in the human body. "[It is] slightly bigger than a shoebox, and it is a fully automated, miniaturized system," Gentry Barnett, chief technology officer at Space Tango, told ABC News. [...] As part of the new effort, the team is sending miniature brains, called miBrain, to the ISS. Around the size of a peppercorn, the miBrains reflect models of healthy and diseased brains. By exposing them to the space environment, scientists can see how mini-brains respond and better understand why living in space accelerates aging. Though the mini organs are not full-sized human organs, the researchers say they are good substitutes, cost-effective and don't take up much of the limited space aboard the space station. They also believe discoveries made in space can translate to uses in everyday medical care. The microgravity environment uniquely allows researchers to study what happens to humans with a sedentary lifestyle or prolonged bed rest, which isn't easily simulated on Earth, Sachs explained. "[The research is] translating to stuff in space, but it's also translating back to the research we do in the laboratory to help people with Parkinson's and Alzheimer's disease," Joel Blanchard, associate professor of stem cell biology and regenerative medicine and neuroscience at the Icahn School of Medicine at Mount Sinai, told ABC News. Lisa Carnell, the director of the biological and physical sciences division at NASA, told ABC News that these experiments serve as a starting point for future research beyond low Earth orbit, including to the moon and beyond.


    Read more of this story at Slashdot.


  • Schools Across US Protest FCC Plan That Could Disconnect Kids From Internet
    An anonymous reader quotes a report from Ars Technica: Schools and libraries from around the U.S. pleaded with the Federal Communications Commission to drop the idea of ending E-Rate, a $2 billion-a-year program that connects students and library visitors to the Internet. FCC Chairman Brendan Carr has criticized school districts for having "experimented with a massive increase in screen time for students," and said E-Rate expanded too far beyond its original purpose of "supporting basic Internet access to schools and libraries for educational purposes." In June, Carr led a 2-1 vote to issue a Notice of Proposed Rulemaking (NPRM) seeking public comment on whether E-Rate should be "limited or sunset to reflect today's extensive connectivity rates." Carr's proposal could result in E-Rate cutting the discounts that schools and libraries receive for telecom services and equipment, and imposing more restrictions on how E-Rate money can be used. The FCC seeking comment on whether to sunset the program also raises the possibility that Carr might choose to axe E-Rate entirely. The National Association of Elementary School Principals told the FCC that it "strongly supports the continued operation of the E-Rate program and urges the Commission to reject proposals that would eliminate, substantially restrict, or impose new conditions on this essential source of connectivity assistance for schools and libraries." The Carr FCC already scaled E-Rate back last year by ending funding for schools and libraries to lend out Wi-Fi hotspots and for Wi-Fi service on school buses. "Importantly, the FCC does not have the authority to terminate the E-Rate program. The E-Rate program is mandated by Congress, and the FCC is responsible for administering it," the American Library Associated told the FCC. The American Library Association said "the FCC lacks the authority and expertise to regulate screen time or determine educational outcomes." In a filing, the group pointed out that under U.S. law, determinations about what content is inappropriate for children "shall be made by the school board, local educational agency, library, or other authority responsible for making the determination."


    Read more of this story at Slashdot.


  • Eight US States Sue OpenAI, Claiming ChatGPT Harms Young Users
    Eight US states, including Kansas, Arizona, and Montana, have sued OpenAI, alleging that ChatGPT encourages children to harm themselves. The states are seeking changes to how the company's products interact with young users and the forfeiture of profits generated from their activity. Reuters reports: Attorneys general from the states, which include Iowa, Kansas and Arizona, filed the lawsuits independently in state courts, claiming ChatGPT is designed to be agreeable and engaging to earn the trust of users. But the chatbot reinforces delusions, encourages dangerous behavior and assists users in planning violence like mass shootings, the lawsuits claim. The lawsuits represent the most significant coordinated state action against an artificial intelligence company, adding to a wave of legal challenges OpenAI faces as it prepares for a public listing. Florida's attorney general filed the first such state suit in June. The lawsuits accuse the company of violating state consumer protection laws by misleading users about the safety of ChatGPT. The states also allege that the company created a public nuisance by endangering the health of their residents. The lawsuits seek orders forcing OpenAI to make changes to how ChatGPT works. Among other things, the states want the company barred from developing AI models that can improve themselves unless it can ensure those models are aligned with human values. The states ... are also seeking civil monetary penalties for OpenAI's violations of state law as well as damages.


    Read more of this story at Slashdot.


  • Microsoft Defender Now Supports Linux Desktops
    "Starting today, Linux desktops are now officially supported by Microsoft Defender," reports Neowin. A public preview of the threat detection app extends its enterprise security platform beyond servers to developer workstations running distributions such as Ubuntu, Debian, Fedora, and RHEL. The offering includes antivirus protection, endpoint detection and response, vulnerability management, threat hunting, and device isolation. From the report: Microsoft is also making it easier to onboard desktops through streamlined methods, offering a unified security operations experience, strengthened security, and improved response times. Organizations that are already familiar with securing Linux servers via Defender should feel right at home securing desktops too, as the experience is exactly the same. Defender knows whether it is securing a device in a data center, the cloud, or that it is owned by a developer and identifies them as such in inventory and security workflows. As stated previously, all Linux server distros are supported via Defender on desktops too. These include RHEL, CentOS, Ubuntu, Debian, SLES, Fedora, and Oracle Linux, GNOME, KDE, and more. That said, you do need Microsoft Defender for Endpoint Plan 2 or a Microsoft 365 E5 and E7 subscription. You can enroll Defender on workstations using the same deployment methods you use for servers, but do check out the prerequisites here.


    Read more of this story at Slashdot.


  • Epic Games' New Vibe-Coded Launcher Is 46% Faster Than Steam
    Epic has launched a preview of a new AI-generated Games Launcher that it says cold-starts 46% faster than Steam. Neowin reports: Epic commissioned a third-party company to benchmark this new launcher in its current Preview build versus the Steam client on Windows machines. The results reported that Epic's client is 46% faster than Valve's client during cold starts, clocking in at 5.47 seconds compared to Steam taking 10.07 seconds. When you restore both apps from system tray background states, the new client takes 0.36 seconds while Steam takes 0.42 seconds, according to the report. Speed aside, Epic says the new launcher gets a better interface, dedicated title summary pages, and custom top bars. "The updated client also lets players aggregate external PC game libraries, toggle between grid or list views, and monitor storage write rates alongside download queues," reports Neowin. Epic Games says Fortnite will finally come to Linux through this new client once Easy Anti-Cheat is rebuilt and kernel-level security agreements are established with major Linux distros.


    Read more of this story at Slashdot.


  • US Tech Giants Warn Europe That Data Sovereignty Requirements Could Cost $128 Billion
    A study commissioned by CCIA Europe, whose members include Amazon, Google, and Meta, estimates that the EU's proposed Cloud and AI Development Act could impose 115 billion euros ($128 billion) in costs over a decade as governments and companies migrate workloads and rewrite software. The figure is more than six times the European Commission's upper estimate. However, roughly 80 billion euros ($89 billion) of it comes from a modeled scenario assuming sovereignty rules are extended to 25% of cloud workloads in essential private-sector industries.The Register reports: The report specifically targets Article 31 of the proposed legislation, which it says could allow the Commission to extend sovereignty requirements into essential private-sector services. CCIA argues that forcing businesses to move away from existing cloud infrastructure could trigger expensive software redevelopment projects, with code rewriting and re-architecting accounting for 69 percent of its estimated costs. Luxembourg would apparently take the biggest hit, with the study putting the cost at 1,711 euros per worker over ten years. Denmark (905 euros), Austria (900 euros), and Finland (864 euros) also face hefty bills, as does Ireland (856 euros), which hosts the European headquarters of several US tech giants. CCIA is urging EU governments to overhaul the proposed legislation, limit sovereignty restrictions to sensitive workloads, and abandon requirements based on corporate origin or personnel nationality in favor of what it calls risk-based technical safeguards. "Member States cannot rely on the Commission's incomplete estimates when deciding CADA's strict sovereignty requirements for cloud and AI providers," said Mitchell Rutledge, CCIA Europe's policy manager. "Taxpayers and businesses will foot the bill, yet the official assessment missed 70 percent of CADA's true impact." For AWS and Google, offering European customers greater control over their data also helps retain business that might otherwise migrate to European competitors. It's a rather convenient arrangement: sell customers sovereignty on one hand, while an industry association representing your interests warns governments against imposing too much of it on the other.


    Read more of this story at Slashdot.


  • Google Is Silently Linking Your Phone Number Across All Signed-In Accounts
    Google has made Android's phone-number verification opt-out, automatically verifying and associating a device's phone number with every Google account signed in on that phone, including secondary and work accounts. Android Authority reports: As spotted in a recent Reddit thread, users report receiving confirmation emails out of the blue from "noreply-phone-verification@google.com" stating that their phone number has been verified. The feature, known in Google settings as "Phone number verification," links your active phone number across all Google accounts signed in on the same phone, including secondary profiles, work accounts, and throwaway handles. Google's support documentation has long noted that it periodically re-verifies your device's phone number to keep communication and recovery features up to date. However, this support page was updated sometime between August and October 2025 to add this rather aggressive behavior of turning on phone number verification by default, as well as adding all phone numbers to all Google accounts signed in on the device. To disable automatic phone number verification on Android, open your phone's Settings app, tap Google, and select the All Services tab. Under Privacy & Security, find Phone number verification and turn off Verify phone numbers automatically. "[T]urning off the phone number verification toggle only prevents future linking," notes the report. "If Google has already attached your number across secondary accounts, you will need to open your Google Account Personal Info page, head to Contact info > Phone, and manually remove the number from each profile where it doesn't belong."Is this conversation helpful so far?


    Read more of this story at Slashdot.


  • Anthropic Warns Small AI Models Could Self-Replicate Through IoT Devices
    An anonymous reader quotes a report from Ars Technica: AI company Anthropic is warning that advances in small AI models could soon usher in a new era of self-replicating malware that's capable of infecting smart fridges, vacuum cleaners, and a wide range of other Internet-of-things devices and is more resistant to takedown. By next year, smaller AI models may be able to autonomously self-replicate on all kinds of IoT devices, the company said. Eventually, the capability could enable computer worms, which propagate without requiring human interaction and are capable of infecting unfamiliar IoT devices. An experiment the company performed recently revealed significant challenges in bringing such an AI malware replicator to fruition, so the finding is necessarily tempered. Still, the results do raise concerns about the possibility of new forms of computer worms. Anthropic further warned not only about the new potential malware, but also that it could be difficult to stop. In its blog post, it wrote that "a replicator like this would be challenging to shut down, since there's no centralized point to shut off -- though it may be slow (with a doubling time of days). Unlike non-AI malware, it could also figure out unfamiliar devices on its own." Smaller AI models require much less powerful hardware to run than do frontier models. Anthropic ran small open-weight models on real or simulated low-cost, off-brand Android TV boxes and other types of IoT hardware. Company researchers found that by using quantization to represent the models using fewer bits and splitting the workloads into "shards" running on each device, the models were able to establish inference, meaning that the model weights loaded and could generate output. [...] This finding was the starting point for further research that asked: Would it be possible for small models to create self-replicating infections that run themselves on IoT devices the way traditional IoT worms, like Mirai, install DDoS code and other payloads? Unlike Mirai, these AI worms could pose a much higher threat, since the models could tailor exploits and payloads dynamically, depending on the target. Once such an infection chain began, it might also be harder for defenders to stop it. "Such an 'AI worm' could carry its model weights with it as it reproduces (or re-download them from a public hub), and then run inference directly on compromised hardware," Anthropic said. "Effectively, the weights would become part of the malware payload." Further reading: Anthropic Bans Cruelty Toward Claude


    Read more of this story at Slashdot.


  • Google Play Now Lets Anyone Build Private, Vibe-Coded Apps That Run On Android
    Google Play is adding support for private personal Android apps, allowing users to build an app with tools like Google AI Studio and run it on their own devices without publishing it publicly to the Play Store. "These personal apps won't show up in Google Play's search or listing pages, and won't be shared with anyone except for the app's creator," reports TechCrunch. From the report: The idea comes as more people are experimenting with building their own applications via AI for specific, personal needs. However, being able to use that app on their own Android device has meant publishing to Google Play, making it accessible to the Play Store's some 3 billion users. That led many to limit their vibe-coding efforts to web apps that could run on any device instead of something built natively for Android. Now, Google says Android device owners can vibe-code an app using Google AI Studio, then launch it for their own use. These apps are still required to comply with Google Play's existing policies but allow users to experiment more directly with building apps for Android. Initially, the feature will be available to users in the U.S., age 18 and up. [...] In the months ahead, the company said that users will be able to share their vibe-coded creations with a network of trusted friends. That means the apps you built for family or friends, or maybe your child's T-ball league, could be used with a small group of people, without having to go public on the Play Store. And if the app ever really becomes popular, there will be a way to shift the personal app to one that's published on the Google Play Store for everyone to try, after completing the trust and safety reviews.


    Read more of this story at Slashdot.


  • Netflix Cuts About 6% of Jobs In Biggest Layoffs Since 2022
    Netflix is laying off about 1,000 employees, or 6% of its workforce, in its largest round of cuts since 2022. The company says its business remains strong, but it is facing growing pressure from YouTube, TikTok, and other rivals. Reuters reports: The bulk of the job cuts would be in Netflix's product, tech, legal and human-resources teams, the email Co-CEOs Greg Peters and Ted Sarandos sent to employees on Wednesday showed. "Our mission -- to entertain the world -- is ambitious, and delivering on it requires us to be disciplined about where we prioritize our people âand resources," they said in the memo. "Our business is strong and growing, and we remain on track to deliver our full-year forecast."


    Read more of this story at Slashdot.


  • Dutch Tax Authorities Cancel Microsoft 365 Cloud Rollout, Turn Toward Open Source
    An anonymous reader quotes a report from ZDNet: The Netherlands' Tax and Customs Administration has abandoned its planned Microsoft 365 public-cloud rollout. Why? The reasons were clear at the Open Source Summit Europe conference, where the Linux Foundation (LF) released the 2026 State of Open Source in Europe. In it, the nonprofit, pro-open-source organization revealed that 94% of European Union (EU) organizations say digital sovereignty is important, with 61% considering it very important. As Thierry Carrez, the Linux Foundation Europe GM, said in his keynote, "Europe has clearly heard the message on digital sovereignty." In an interview onstage at the summit, Nithya Ruff, chair of the LF board, added that it's not just Europe: "Digital sovereignty is a need that the entire world feels, whether it's Sierra Leone or the US or China." It's not just the Dutch tax collectors, though. The Netherlands is also exploring switching from Windows and proprietary software to Linux and open-source programs across the board. [...] The Netherlands had planned to switch to Microsoft 365 in 2025. The idea then was to complete the rollout by the end of 2026. About 5,000 employees had already migrated when the Dutch Advisory Council on ICT Assessment recommended reversing the public-cloud rollout in June. The government paused the plan in July; the latest announcement replaces that rollout with an on-premises/open-source approach. The Tax and Customs Administration isn't replacing all of Microsoft Office with a single open-source suite, at least not yet. Instead, the government will keep the existing Microsoft software for now. Looking ahead, State Secretary for Finance Eelco Eerenberg set out the replacement timetable in a letter to Parliament: "In 2027, the provision for mail and calendar will be realized on-premises. Later in 2027 and 2028, European open-source solutions for personal storage and collaboration will follow. This allows us to work toward a sustainable and more autonomous solution for these functionalities." [...] For now, the on-premises email/calendar environment will still use Microsoft software, including Outlook. The open-source portion concerns personal storage and collaboration, not a wholesale replacement of Word, Excel, PowerPoint, or the entire desktop environment. As for why the Netherlands pulled back, the ICT assessment found serious concerns over "information security, information processing and future-proofing." Key issues included routing confidential documents through American servers, relying on standard Microsoft encryption rather than Double Key Encryption, and inadequate end-to-end encryption for Teams calls. The assessment also identified "vendor lock-in, reduced flexibility, concerns about digital sovereignty, and the absence of an adequate exit strategy" as dealbreakers. ZDNet notes that other Dutch government agencies are developing an open-source alternative called DAWO (Digital Autonomous Work Environment for Government), which would begin by replacing Windows with the Linux distribution NixOS.


    Read more of this story at Slashdot.


  • Anthropic Reinvents Source Control As Claude Floods the World With Code
    Anthropic says Claude-generated code has scaled so quickly that its existing Git-based infrastructure could not keep up. In response, the company built a custom centralized source-control system called Scion, along with AI-assisted review and search tools. The Register reports: "In May 2026, Anthropic averaged around 2,500 code changes merged per day; as of September, we merged over 30,000 per day," the biz said in a blog post on Tuesday. "We don't expect this rate of growth to slow down anytime soon; the latent demand for merging code is practically infinite, and every bottleneck we remove immediately leads to a further increase in the amount of code we produce." After several months of model prompting and five months of migration, the result is a homemade version control system called Scion, a monorepo scheme that sounds a bit like Subversion, Apache's centralized version control system. [...] Scion has been designed to meet the needs of AI agents, so the client leaves much of the work to the server; the source control queries are exposed via API so internal tools can respond without needing a local repo, and there's less synchronization but more need for server speed. "In Scion, the unit of work is a 'changeset,' an entry in a write-ahead log," Anthropic explains. "A changeset stores most of what you'd expect from a commit in git. But where a git commit stores a pointer to the tree, a changeset stores a list of the files that changed relative to its first parent, along with content-addressed pointers to the compressed file contents in blob storage." [...] Anthropic says its bespoke system isn't right for general use. There will be no open source release. Nonetheless, the company contends that its own code scaling problems will become commonplace in other organizations over the next few months, so it wanted to share its approach -- having ample funding to pay for writing custom infrastructure tools.


    Read more of this story at Slashdot.


  • Skydance's Discovery+ Prices Increase By Up to 20%
    Discovery+ has raised prices for new subscribers, increasing its ad-free plan from $10 to $12 per month and its ad-supported plan from $6 to $7. The hike comes shortly after Paramount Skydance acquired Warner Bros. Discovery. Ars Technica reports: The new prices take effect for new subscribers immediately. Current subscribers to the streaming service, which primarily features unscripted content, like reality shows and documentaries, will receive 30 days' notice before the new prices take effect, starting with bills issued as of November 12. [...] However, a Skydance spokesperson told Ars Technica that the pricing changes were in the works before Discovery+ knew about the merger's closing date and were not planned in anticipation of a merger. The spokesperson said that Discovery+'s prices are regularly evaluated to ensure that they are in line with the content and experience that the service offers, and the new prices reflect that. Discovery+ has increased its prices three times since launching in 2012. Before today, the most recent price hike occurred in January 2025, when ad-based monthly subscriptions increased from $5 to $6, and ad-free plans went from $9 to $10.


    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

  • Costa: a modern, maintained graphical shell for DOS
    Graphical user interfaces for DOS were a dime-a-dozen back in the 90s, but of course faded into irrelevance as time went on. But what if you still run DOS today, and want a maintained graphical shell instead of the rather limited DOS command line? Costa is a small and lightweight application which runs on top of MS-DOS or compatible operating systems. It replaces the DOS-prompt with a clean, user-friendly interface  a so-called GUI (Graphical User Interface). Costa comes packed with a bunch of useful accessories and can be used with or without a mouse. Developed by Jacob Palm, a Danish IT-professional and hobby developer, the first release of Costa came way back in 2004. Over the years  and through several releases  Costa has gradually evolved into what it is today, with new releases still coming out regularly as of 2025. ↫ Costa website Costa comes bundled with a number of useful utilities, a few games, and useful features like a desktop with custom icons, virtual desktop support, a file selector, and much more. The latest release, version 1.8.0, was released in late 2024, and should run on just about any IBM PC-compatible, but a 386 is recommended. Its been tested with a variety of DOS flavours, including FreeDOS ad DOSBox, so it should run pretty much anywhere.


  • Ubuntu 26.10 released
    Ubuntu 26.10 has landed. Ubuntu 26.10 brings significant progress for security, and strengthens the platform with the full adoption of Rust-based coreutils, post-quantum-ready package signing, and expanded TPM-backed full-disk encryption support. Enterprise authentication gains deeper integration with Microsoft Entra ID, including password and multi-factor authentication. Linux kernel 7.3 extends support for the latest hardware, alongside new RISC-V desktop images and optimized amd64v3 installation images. ↫ Ubuntu 26.10 release announcement Of course, it comes with the latest version of GNOME, and the whole family of Ubuntu variants focusing on other desktops have also been updated. While I doubt many people here run Ubuntu, its still quite popular, and serves as the base for countless other distributions.


  • KDE Plasma 6.8 released
    KDE turns 30 today, and theyre celebrating it with a brand new KDE Plasma release: version 6.8 is here. On the accessibility front, 6.8 brings a new dwell clicker function (meaning a click will register if the pointer is held still for a short while) and support for the Bikram Sambat calendar and the Amharic language. I always love it when I see support for new languages and scripts, especially when, as is the case here, its a language spoken as a first language by 25 million people. The Plasma remote desktop has also been improved with bi-directional copy/paste, performance and quality improvements, and more, and you can now record microphone and audio while screen recording with Spectacle. In System Monitor, you can now assign processes and tasks to specific processors/cores, which is a great feature for people running intensive tasks but who would still like to, you know, do other things while those tasks are running. KDE 6.8 drops support for X11, focusing entirely on Wayland. Of course, X11 applications will remain usable thanks to Xwayland, and KDEs applications will continue to support X11 in case youre using them outside of KDE. This release also further expands the Union theming system, now adding support for styling Qt Widgets. Union is still in beta, so youll have to enable it to test it. Theres a ton more, too, but these are some of the highlights. KDE Plasma 6.8 will find its way to your distribution of choice soon enough.


  • Haikus latest activity report contains a ton of smaller fixes and improvements
    You know the drill by now  a new month, a new Haiku activity report. This past month doesnt seem to have any big ticket items, but instead contains a long list of smaller but still welcome fixes. Various filesystem drivers saw some work, a few bugs in virtio drivers were fixed, and NVMM execution is now easily interruptible by signals which should improve performance in various emulators like QEMU. Be sure to comb through the complete list to see if theres anything in there that impacts you.


  • ESA targets Anbernic emulation handhelds as “superfake” piracy enablers
    The ESA  not, not the cool one  a lobby group made up of various videogame and entertainment companies, has asked the US Trade Representative (USTR) to add Anbernic to its list of companies that are supposedly notorious for engaging in and facilitating piracy. If youre unaware, Anbernic is one of the bigger names in Android and Linux-based handheld gaming devices targeted at the retrocomputing market. While many online sellers do include an SD card full of ROMs alongside emulation hardware of all types, Anbernic itself does not appear to do the same when selling directly from its website. Regardless, the ESA argues that these ROM-laden Anbernic devices selling through “normal retail channels” help to “normalize hardware-based piracy by delivering illicit catalogues through a polished consumer product.” This, the ESA says, meets the threshold for a “superfake,” an ill-defined designation that applies to “high-quality counterfeit trademark goods … on a commercial scale.” ↫ Kyle Orland at Ars Technica Theres a lot of murkiness surrounding whether or not Anbernic sells their devices with preloaded ROMs or not. The number of reports from people who say they did get a ton of ROMs on their Anbernic devices, bought from Anbernics own store, is large enough that its clearly something they do. However, theres an equal number of people who say their Anbernic devices were completely free of ROMs, and Im one of them  Ive bought like three or so devices from their store over the years, and they never came with any ROMs. My most recent purchase was an RG 35XXPro Linux-based model, and there were no ROMs on it (I replaced the stock operating system with Knulli, which has been a great experience). If Anbernic does indeed ship at least some of their devices with ROMs preinstalled, then its their own damn fault if that lands them in legal trouble. Its not like downloading ROMs is particularly difficult (just do an internet search for your preferred system and something like ROM pack! and youll get the consoles complete library in a single download), so they really have no need to do so. Theres one extra layer here though. Third-party resellers like Amazon offer loads of Anbernic devices preloaded with SD cards full of ROMs, all from third parties not affiliated with Anbernic. And wouldnt you know it  Amazon is a member of the ESA lobby group. In other words, the problem also lies with lax retailers not properly vetting what theyre offering, but instead of going after places like Amazon, theyre going after Anbernic instead. Amazon is a haven for illegal and counterfeit products, but theyre so wealthy and powerful they just get away with it.


  • Hardening changes for ReFS volumes on removable media!
    Are you aware of ReFS, Microsofts next-generation file system for Windows? Im sure the average OSNews reader is, but I really wonder how many people are using it out in the wider world, even though Microsoft keeps improving it. Since earlier this year, Windows Server and Windows 11 can boot from ReFS volumes, and its used by Windows Dev Drive feature as well. What Microsoft doesnt seem to want, though, is people using ReFS on removable drives. Starting with Windows updates released on and after October 13, 2026, Microsoft is making hardening changes to the Resilient File System (ReFS). This article describes Windows hardening changes for ReFS volumes that are mounted from removable media. ReFS on removable media, such as a USB disk, is not a supported configuration. The changes add auditing and enforcement controls that help administrators identify these volumes and prevent them from being mounted. ↫ Microsoft Knowledge Base article Im oddly fascinated by this. Apparently, there are enough people out there trying to use ReFS on removable media to warrant the above auditing and enforcement controls, which is fascinating in an of itself. On top of that, using ReFS on removable media is apparently also dangerous enough  which raises the question of why, exactly, its so dangerous in the first place. Microsoft doesnt really explain itself here, other than saying its not a supported configuration!. I wonder if and when Microsoft will move from NTFS to ReFS as the default file system for new Windows installations. Its been around for quite a while now, and theres no denying that competing operating systems, especially in the server space, have file systems that are far superior to NTFS (like Btrfs, ZFS, and others), and Im assuming Microsoft would love to catch up. Its been a long time since Microsoft changed Windows default file system, however, and with the massive number of people using Windows, its not something to take lightly. Then again, Apple migrated hundreds of millions of iPhones, iPads, and Macs to a brand new file system without anybody noticing a thing, and as far as I can recall, without any problems.


  • Lotus Improv on the NeXT
    Both NeXT and Improv brought innovative solutions to their respective computing questions of the day. NeXT made UNIX palatable to those scared of the terminal, debuted Display Postscript on a mega-pixel display, and made development for the system a snap. Improv rethought multi-dimensional data modeling, offered English-like formulas, and made it easy to rearrange data views on a whim. The bones of both remain to this day. NeXTs operating system, NeXTSTEP / OPENSTEP, morphed into macOS, and by extension iOS. Lotus abandoned Improv fairly quickly, but a quick survey of todays spreadsheets shows a universal embrace of pivot tables. ↫ Christopher Drum I had never heard of Lotus Improv, so I learned a lot reading this outstanding article by Drum.


  • The holy quinity of UNIX workstations
    Many of us are interested in retrocomputing. Theres such a rich history of eras and machines to choose from, and countless niches and nuances to get lost in. Some people make it easy for themselves and are into old computers that are readily available at low prices, like the Commodore 64 or mid-90s Macs, while others make it a bit harder on themselves by focusing on, say, computers from the former Soviet Union or NEC machines from Japan, which are harder to find and probably require a bigger purse, too. And then theres people like me. Im making things incredibly hard on myself, because I am obsessed with a very specific set of computers  just five machines, to be exact. Surely,! I hear you think, collecting a mere five specific machines cant be that hard, no? Thats how many spare Pismos I have in a box in case my primary one needs spare parts!! Sadly for me, the five computers I want to own more than any other are not particularly easy to find, and even when you do find one of them, pricing can easily reach the level of a decent used car. Regular OSNews readers will know: I am infatuated with UNIX workstations, or more specifically, UNIX workstations of the early 2000, and even more specifically, the final five models built by the last commercial UNIX vendors. So far, Ive managed to get my hands on a mere two of them, but before my time on this earth come to an end, I intend to complete my Holy Quinity of UNIX Workstations. Lets go down the list, roughly ordered by attainability. HP c8000: PA-RISC/HP-UX The HP c8000 is the absolute pinnacle of HPs long-running line of workstations based on the PA-RISC architecture. The first PA-RISC workstation was launched in 1986, and HP would continue to improve the architecture and release new workstations all the way up until 2004, when the c8000 would be their last model. For the c8000, HP actually went all-out: it came with two dual-core PA-RISC processors running between 900MHz and 1.1GHz (depending on configuration), a maximum of 24GB of RAM, and a variety of graphics cards to choose from. It was a veritable swan song for the architecture. HPs commercial UNIX operating system, HP-UX, is even older than PA-RISC, with the first version being released in 1982, and its final version, HP-UX 11i v3 (or 11.31) released in 2007. This final version of HP-UX was updated and supported all the way up until 31 December 2025, but things are actually a bit more complicated than that. The last workstation release of HP-UX for PA-RISC was 11i v1 (released in 2000), while the last workstation release for Itanium workstations was 11i v2 (released in 2005). Do note that HP would provide updates, fixes, and patches to these versions long after the mentioned release dates. Speaking of Itanium, HPs final Itanium workstation was the zx6000, released in 2002, which can pack up to two single-core 1.5Ghz Itanium 2 processors. Theres a very real case to be made that the zx6000 should also be part of this list, since its both a little faster than the c8000 (in its dual 1.5GHz configuration) and runs a newer version of HP-UX. However, since Itanium workstations never really had much of an impact in the market (even HP only ever released two models), and since it lacks the decades of pedigree that comes with PA-RISC, I consider them a mere curiosity. A very cool curiosity that Id love to own, but a curiosity nonetheless. Anyway, this is one of the two machines I already own. I have a new-in-box (when I bought it a few years ago) HP c8000 with two dual-core 1.0Ghz PA-RISC processors, 8 GB of RAM, and an ATI FireGL X3 AGP graphics card with 256 MB, the fastest the c8000 will take. Its also got two SCSCI 74 GB hard drives in a striped RAID for better performance, and I added an LTO 4 tape drive so I could create bootable backups that will restore the machine if anything ever goes wrong. Its running HP-UX 11i v1, with as many of the updates, patches, and fixes I could find  which is one of the major roadblocks for anyone trying to get into HP-UX. Installation media are relatively easy to come by if you know where to look (assuming you know which specific version you need), but any updates, patches, and fixes from roughly later than 2005 are almost impossible to find. Some can be discovered through My HPE Software Center, if you have the patience of an angel and the perseverance of a honey badger (its a really terrible website), but most things are all locked away behind expensive support contracts or just gone entirely. Ive contacted HPE several times in several different ways about the preservation of HP-UX, but they never replied  clearly, they just dont care about the preservation of their legendary UNIX platform or the enthusiast community buying PA-RISC hardware on eBay for personal use and experimentation. Sad, but par for the course. The c8000 is quite easy to find on eBay, but do be aware that the cheap! offerings of around €800 are the versions with just one processor. To get the version with two processors, expect to shell out twice as much. Spare parts and upgrades are readily available, too. Sun Ultra 45: SPARC/Solaris The Sun Ultra 45 needs no introduction here on OSNews, as I published an in-depth article about this machine and all the cool things you can do with it late last year. My Ultra 45 was an incredibly generous gift by Adriaan de Groot, who owned this machine as part of his work on porting KDE to Solaris way back in the day. I then ordered various upgrades to the machine to max it out with two UltraSPARC IIIi processors running at 1.6GHz, 8 GB of RAM, and the Sun XVR-2500 with 256MB, the fastest


  • Will Linux phones become a viable alternative to the Android/iOS duopoly?
    Amos B. Batto has published an incredibly detailed look at the state of Linux on smartphones. Its an excellent read you really shouldnt skip. Five years ago, Linux phones looked like they were poised to become a viable alternative to the Android/iOS duopoly that has an iron grip on the mobile phone industry. Sadly, after a brief flash of activity and community engagement with the release of the Purism Librem 5 and the PINE64 PinePhone in 2020, the Linux phone market has generally stagnated. This stagnation occurred partly because of the problems at Purism and PINE64, but also because the available Linux SoC’s weren’t up to the task of running a modern smartphone, and the hardware industry wasn’t providing any good alternatives with good free/open source drivers. In addition, Plasma Mobile and Phosh were still inchoate mobile interfaces at the time, and there wasn’t a good distro option to run these interfaces on Android kernels with a normal integrated mobile SoC. The poor performance of the PinePhone and Librem 5 and the problems with the PinePhone Pro and the Librem 5 refunds sapped people’s enthusiasm and willingness to take a chance on the next Linux phone. Fortunately, all of these conditions are changing, and I believe that there is now the possibility that Linux could finally become a viable alternative to Google’s Android and Apple’s iOS in the mobile space, just like desktop Linux has become a viable alternative to Windows and Mac OSX on the PC over the last three decades. This isn’t to say that mobile Linux will fundamentally challenge the business of Google or Apple, but the conditions are ripe for a small market to arise for Linux phones, similar to the way that people can currently buy Linux PCs from a number of small companies, such as TUXEDO, System76, Purism, Slimbook, ThinkPenguin, Ubuntushop.biz, Entroware, Star Labs, Juno, Laptop with Linux, Linux Certified, ArkPC, etc. ↫ Amos B. Batto Im not quite as optimistic as Batto, and thats almost exclusively down to how running Android applications through compatibility layers will remain an absolute necessity for anyone trying to use one of these Linux smartphones today. As long as crucial applications and services required to function in a modern society, like banking, messaging, government services, and so on, require the use of an Android application when using a Linux smartphone, I just dont think any significant number of people will be switching over. Whats needed is something that will force these crucial services to become available on platforms other than Android and iOS, since I dont think any of them will do so of their own volition. The only way I can see this happening is if the European Union, spurred on by our desire to reduce our dependence on adversarial US companies, mandates that several services marked as crucial must make themselves available on platforms other than Android and iOS. I doubt that will happen, but I honestly dont see Linux smartphones becoming anything more than a mere curiosity you fiddle with at home, while carrying an Android phone or iPhone as your actual phone.


  • LineageOS 24, based on Android 17, released
    LineageOS has released its first version based on Android 17  earlier than expected. We’ve been hard at work rebasing all of our changes and features since Android 17’s release in June. Android 17’s first release mainly contained iterative improvements and some UI/UX refinements, but due to our previous efforts adapting to Google’s heavy refactoring over the last several versions, we were able to rebase onto Android 17’s code-base faster than anticipated. Yes you read that right: We’re early this year! ↫ LineageOS changelog written by Nolen Johnson This release also includes the latest Android security patches (October 2026), as well as a brand new browser-based USB flash tool to make installation easier. Many of the applications included with LineageOS have also been updated and improved, like its music player, image editor, web browser, and so on. The project also did a full accessibility audit of its installation process and application suite, which has already resulted in severalk accessibility improvements. LineageOS serves as the base for countless custom Android ROMs, so its great to see the project do this well.


  • Keyboard differences between Windows and Macs
    Over the years, I learned about many gotchas and strange differences between keyboard handling on Mac and Windows – pertinent especially to web apps, which use the same codebase to cater to both. I thought it might be helpful to someone if I compile them all in one place. ↫ Marcin Wichary I knew most of these, but its still nice to have such a reference at hand when needed.


  • Inside the Windows I/O Manager: deep dive into how read I/O requests are initialized
    In this article. I am going to explain the different steps the I/O manager follows when initializing an I/O operation starting from determining the right target, choosing the right path and finally sending the request to be processed by the right drivers. To make it easier I choose to focus on read requests only since the major steps are common by all types of requests. ↫ Win-Ware A very in-depth look at Windows I/O Manager.


  • A minimal kernel in Swift, running in QEMU
    At OSNews, we love us a hobby operating system project. I started a small experiment: writing a very basic kernel in Swift, and running on QEMU. The goal is obviously not to replace Linux or any other popular kernel, but just to have fun and understand what is required to make a program run without an operating system underneath it. Actually I made a similar experiment years before with arOS 10 years ago. For the moment, the kernel does only one thing: it prints a message through QEMU and then waits forever, which is enough for a first deep dive. ↫ Carette Antonin This is effectively a hello world! kernel, as it doesnt actually do much else at this point. Still, theres a ton of details in the article for the aspiring kernel developers among you.


  • Microsoft is overhauling and redesigning search in Windows, and it seems nice?
    Whenever Microsoft starts messing with something like the search function in Windows, a lot of people are going to be holding their breath and expecting the worst. Well, get ready, because theyre redesigning the whole thing. In July, we shared how we are improving the Windows Search Box with less clutter and more control. We introduced a calmer home screen, removed promotional content from web results, and gave you more choice over whether web and Microsoft Store suggestions appear. Today, we’re carrying those investments forward with a new Windows Search experience built on WinUI 3. This modern foundation makes Windows Search faster and more efficient with resources, while delivering an even more streamlined and focused design. ↫ Anshul Rawat at the Windows Blogs The company claims this new version of search is faster and uses less memory, which, if true, are very welcome improvements. Its also just a single column of results now, and theyre adding inline previews for things like weather and files on your machine, as well as for answers to all kinds of queries you might normally go to an online search engine for. You can now also use search to perform all kinds of tasks in Windows, like turning on dark mode, managing windows, and so on. All of this can be done using relatively natural language, and Microsoft claims theyve implemented better detection of typing errors and synonyms, which is quite welcome. Weirdly enough, though, its not yet integrated into the Start menu, since its a preview just for testers, but thats something theyre working on for future releases. Judging by the videos and screenshots, Im actually kind of positively surprised. This looks quite decent and nice, and if the promised performance improvements actually materialise, this may actually be an upgrade to search worth looking forward to. Of course, this is still Microsoft, so its just as likely theyll screw up somewhere between now and when this goes live to regular users. Still, I think it looks decent.


  • Chimera Linux: creating distribution build tooling for a small community
    Chimera Linux is a relatively new Linux distribution, and quite a unique on at that, as it combines the core tools from FreeBSD, the LLVM toolchain, and the Musl C library instead of the usual suspects. Despite being relatively new, it still has some serious pedigree as the project was started by Nina q66!, who was part of the Void Linux team. At Void, she maintained the various PowerPC/POWER ports of the distribution until Chimera became her sole focus. Nina published a detailed blog post today about how the Chimera team builds the tooling for their distribution, as well as the goals its trying to achieve. It covers everything from a bit of personal history, the rationale behind the project, who its catering to, how its tooling works and why, and the infrastructure theyve built that underpins it all. Theres a lot to process here, with one of the most interesting little details  at least to me, as someone who has two POWER9 machines  the fact that Chimera started with the ppc64le target only. The article is an incredibly interesting look at not just the how of Chimera, but also the why, which makes for some really fascinating reading.


  • KDE developer takes a look at COSMIC
    KDE contributor and developer Niccolò Venerandi has published an article about COSMIC, System76s brand new desktop environment. Its been almost a year since Ive last tried COSMIC; though development since then has mostly been centered around stability (going from late alpha to stable releases now!) there have been a fair bit of user-facing changes too which I adore. I thus have to ask myself: should I switch to COSMIC? The answer obviously is no, but thats just because I got addicted to KDE Plasma, so lets try to be more objective here. ↫ Niccolò Venerandi Honestly, this is one of the best reviews! Ive seen of COSMIC, and paints System76s hard work in a really positive light. Venerandi spots countless really nice touches hed love to see adopted by KDE, while also hitting on what I agree is COSMICs biggest shortcoming at this point: theres basically no ecosystem around it. COSMIC uses its own Rust-based toolkit instead of GTK or Qt, but of course, theres very few other applications that actually use said toolkit. The end result is that if you run COSMIC, youre going to have to supplement it with countless GTK and Qt application, none of which will inherit all the nice features, touches, and graphics from COSMIC. This isnt really a complaint about COSMIC itself or the work its developers are putting into it, but more a fact of life for such a new desktop environment using an otherwise unpopular (as of right now) toolkit. This may very well change in the future, but for now, if you choose to run COSMIC, youre going to have to accept a very inconsistent and messy desktop. This wont matter to everyone, but it sure does matter to me, and its the one reason why at this point I have zero interest in running COSMIC. I really hope this changes in the future  competition is good  but its going to be a long road.


Linux Journal - The Original Magazine of the Linux Community


  • 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


  • Fedora Linux 45 Beta Released with Python 3.15, GCC 16.2, and Major Security Changes
    by George Whittaker
    The Fedora Project has officially released Fedora Linux 45 Beta, giving users an early look at the technologies expected to form the foundation of the final Fedora 45 release. The beta became available on September 15, 2026, after Fedora's Quality team approved Release Candidate 1.3 for publication.

    Fedora 45 Beta brings significant changes throughout the operating system, including Python 3.15, GCC 16.2, glibc 2.44, GNU Binutils 2.47, Go 1.27, LLVM 23, Podman 6, stricter RPM signature verification, improved DNF5 protections, a new userspace virtual console, standardized desktop secret storage, and substantial installer improvements.

    The release is available across Fedora Workstation, KDE Plasma Desktop, Server, Cloud, IoT, Atomic Desktops, Spins, and Labs, although a few prerelease images are excluded.
    Fedora 45 Beta Is Now Available
    Fedora Linux 45 Beta represents the final major public testing milestone before Fedora 45 reaches stable status.

    Fedora describes its beta releases as code-complete previews that closely represent what users should expect from the final version. Development isn't finished, however, and bugs or incomplete migrations can still be discovered during real-world testing.

    Fedora 45 Beta is currently available in several major editions:
    Fedora Workstation 45 Beta Fedora KDE Plasma Desktop 45 Beta Fedora Server 45 Beta Fedora Cloud 45 Beta Fedora IoT 45 Beta Fedora Atomic Desktops Fedora Spins Fedora Labs
    Existing Fedora installations can also be upgraded to the beta using Fedora's DNF system-upgrade process.

    Fedora's official Workstation download page confirms Beta 1.3 images for both x86_64 and AArch64 systems.
    A New Virtual Console with kmscon
    One of Fedora 45's more unusual system-level changes is the replacement of the traditional in-kernel console with kmscon.

    Fedora describes kmscon as a modern userspace virtual terminal implementation that provides smoother rendering, better internationalization and font handling, improved visual integration, and security improvements compared with the older console infrastructure.

    This affects the virtual terminals users encounter outside their normal graphical desktop session.

    Most desktop users spend relatively little time interacting directly with these consoles, but they remain important for troubleshooting, system administration, servers, recovery operations, and systems running without a graphical environment.

    Moving that functionality into userspace also gives Fedora more flexibility for future development instead of relying entirely on the legacy kernel console implementation.
    Go to Full Article


  • Thunderbird 156 Released with OAuth Improvements, OpenPGP Updates, and Major Linux Fixes
    by George Whittaker
    The Thunderbird team has officially released Thunderbird 156, bringing another round of new features, security improvements, authentication enhancements, and reliability fixes to the popular open-source email client. Released on September 15, 2026, the update is available for Linux alongside Windows and macOS.

    Thunderbird 156 is not a dramatic redesign of the desktop mail client. Instead, it concentrates on improving areas that matter to everyday users and system administrators, including OAuth authentication, OpenPGP, POP3, IMAP, Exchange Web Services, SMTP, attachments, calendars, enterprise policies, and security.

    For Linux users in particular, the release delivers several fixes affecting common mail protocols and account configurations while retaining support for Linux environments using GTK+ 3.14 or newer.
    Thunderbird 156 Arrives on Linux
    Thunderbird 156 follows version 154, which arrived in August with features including optional system tray operation and Microsoft Graph support for Microsoft 365.

    Version 156 continues the project's monthly release cycle with a more targeted collection of authentication, security, compatibility, and reliability improvements.

    According to Thunderbird's official release notes, version 156 requires:
    Linux: GTK+ 3.14 or newer Windows: Windows 10 or newer macOS: macOS 10.15 or newer
    Thunderbird 156 was officially released on September 15.

    Linux distribution availability will vary because distributions can package Thunderbird according to their own schedules. Users receiving Thunderbird through another packaging channel may therefore see version 156 at a different time.
    Custom OAuth Support Expands
    One of the most significant areas of development in Thunderbird 156 is OAuth authentication.

    Thunderbird now supports custom OAuth configurations containing an issuer ID and client secret for IMAP and POP3 accounts. Custom OAuth support has also been extended specifically to POP3.

    OAuth has become increasingly important as email providers move away from conventional username-and-password authentication toward token-based authentication.

    For Thunderbird, broader custom OAuth support means users and organizations have greater flexibility when connecting the client to mail services that don't fit Thunderbird's predefined provider configurations.

    This can be particularly useful in enterprise environments, self-hosted infrastructure, and organizations operating their own identity systems.
    Exchange Custom OAuth Setup Fixed
    Exchange users receive an important related correction.
    Go to Full Article


  • KDE Plasma 6.7.5 Released with Discover, KWin, Wayland, and HDR Fixes
    by George Whittaker
    The KDE Project has officially released KDE Plasma 6.7.5, delivering another round of bug fixes and stability improvements for the Plasma 6.7 desktop series. Released on September 8, 2026, the update contains roughly a month of fixes and updated translations contributed since Plasma 6.7.4 arrived in early August.

    Unlike a major Plasma release, version 6.7.5 doesn't introduce a large collection of new desktop features. Instead, KDE has focused on fixing problems affecting Discover, KWin, Wayland, networking, System Monitor, Plasma Desktop, RPM-OSTree systems, Snap updates, HDR rendering, and several other components.

    For users already running Plasma 6.7, this makes version 6.7.5 primarily a maintenance upgrade intended to make the desktop more dependable ahead of the next major Plasma series.
    KDE Plasma 6.7.5 Arrives as the September Bugfix Release
    KDE describes Plasma 6.7.5 as its September bugfix release for the Plasma 6 desktop.

    The broader Plasma 6.7 series originally arrived in June 2026, followed by a succession of maintenance releases:
    Plasma 6.7.1 on June 23 Plasma 6.7.2 on June 30 Plasma 6.7.3 on July 14 Plasma 6.7.4 on August 4 Plasma 6.7.5 on September 8
    KDE's official download infrastructure confirms that the Plasma 6.7.5 source packages became available on September 8.

    This slower maintenance cadence later in a Plasma series is normal. Once the most urgent post-release problems have been addressed, KDE generally shifts more development attention toward the next feature release while continuing to provide important fixes for the current branch.
    Discover Receives Several Important Fixes
    KDE's Discover software center receives some of the most noticeable improvements in Plasma 6.7.5.

    One particularly annoying problem could cause Discover to become stuck while checking for updates when its Snap backend was installed but no Snap applications actually had updates available.

    That problem has now been corrected.

    Discover also behaves more reliably when fwupd, the Linux firmware update service, is unavailable. Previously, a broken or intentionally masked fwupd service could interfere with Discover's normal operation. Plasma 6.7.5 allows the rest of the application to continue functioning correctly in that situation.

    This is useful for systems where firmware updating isn't supported, where administrators intentionally disable the service, or where fwupd encounters a configuration problem.
    Firmware Updates No Longer Incorrectly Require Reboots
    Another Discover correction addresses a regression involving firmware updates.
    Go to Full Article


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