|
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)
- [$] The 2026 Maintainers Summit
The Maintainers Summit is a one-day, invitation-only gathering of about 30kernel developers; it is held once each year to discuss policy-related issuesthat are not always amenable to resolution via email. The 2026 event wasscheduled for October 8 in Prague, Czechia. Unsurprisingly, the discussionthere was dominated by large language models (LLMs) and their effect on thedevelopment community, but some time was also found to talk about securitybugs and long-term succession planning.
- LineageOS 24 released
The LineageOS project, which produces anAndroid-based distribution for mobile devices, has announced the release ofLineageOS 24.0.
We're a bit sentimental about this release, as it precedes a really funupcoming milestone.
On December 24, 2026, LineageOS will celebrate 10 years. It's a remarkablemilestone for a project built by a passionate community of developers,maintainers, contributors, and users who have kept so many devices alive alongthe way.
[...] We've been hard at work rebasing all of our changes and features sinceAndroid 17's release in June. Android 17's first release mainly containediterative improvements and some UI/UX refinements, but due to our previousefforts 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. Yesyou read that right: We're early this year!
- Security updates for Monday
Security updates have been issued by AlmaLinux (cjose, compat-openssl10, compat-openssl11, curl, dogtag-pki, dovecot, emacs, glibc, kernel, openssl, python3.12, python3.14, and sssd), Debian (chromium, ghostscript, tor, and vips), Fedora (kernel, libical, markdownlint-cli2, openbao, openvpn, php-getid3, python3.10, python3.11, and python3.13), Mageia (capnproto, chirp, flatpak, freetype2, hamlib, mingw-pcre2, pcre2, openssl, tomcat, tomcat-native, and xdg-dbus-proxy), Oracle (bind, cjose, dogtag-pki, dovecot, firefox, kernel, nodejs:24, openssl, pki-core:10.6, python3.12, python3.14, ruby:2.5, rust-sequoia-sq, sssd, and tftp), Red Hat (libxml2), Slackware (mutt), SUSE (apache-sshd, bind, ccache, chromium, cpp13, dash, expat, fetchmail, flatpak, golang-github-prometheus-prometheus, grafana, system-user-grafana, incus, libpng16-16, libsoup, logback, openssh8.4, perl-DBI, php8, python3-paramiko, python312, python313-asyncpg, python313-azure-identity, python313-Babel, python313-Beaker, python313-bjoern, python313-black, python313-Brotli, python313-CairoSVG, python313-Flask-Cors, python313-FontTools, python313-Jinja2, python313-jwcrypto, python313-MechanicalSoup, python313-oauthlib, python313-PyJWT, python313-PyMySQL, python313-PyYAML, python313-virtualenv, python313-XStatic-jquery-ui, qemu, rsyslog, shadowsocks-rust, squid, stunnel, swtpm, trivy, unbound, wpa_supplicant, and yast2-users), and Ubuntu (libdbi-perl).
- Kernel prepatch 7.3-rc7
The 7.3-rc7 kernel prepatch is out fortesting. According to Linus: "As always, I would have preferred to see a smallerrc, but it's not like anything in here looks like a reason to delaythe final release. So that's still set for next weekend unlesssomething new comes up."
One notable change that slipped into the mainline this week is the deprecationof the ext4 data=journal mode; it will be removed entirely at thebeginning of 2028.
- Python 3.15 released
Version3.15 of the Python programming language has been released. Notable changesin this release include the addition of the sentinel and frozendict built-in types,the use of UTF-8 encoding by default, packagestart-up configuration files, as well as improvements in the experimentalJIT compiler. See the "What's new in Python3.15" article for an in-depth look at new features in this release, and thechangelogfor a full list of changes.
- [$] Adding kernel control-flow-integrity checking to GCC
While many developers are struggling to keep up with the flood ofvulnerability reports, others are still focused on preventing those reportsfrom happening in the first place. Control-flow integrity (CFI) is theterm for preventing (or at least detecting) exploits that divert the flowof control from its intended paths. At the 2026 GNU Tools Cauldron, Kees Cookpresented his changes to the GCC compiler suite to support forward-edge CFIfor the kernel.
- [$] The state of systemd: 2026 edition
At the 2026 All Systems Go!conference, systemd maintainers Luca Boccassi and Zbigniew Jędrzejewski-Szmekdelivered the traditional "state of the project" session with an overview of thesystemd project's accomplishments in the past year. That was followed by amaintainer round table where Boccassi, Jędrzejewski-Szmek, Daan De Meyer, andproject leader Lennart Poettering fielded questions about systemd's size,health, and if it might replace Kubernetes. (It will not.)
- Let's Encrypt moving to 64-day certificate lifetimes in 2027
Let'sEncrypt, the nonprofit that provides free TLS certificates for millions ofsites, has announced thatit will be moving to certificates with 64-day lifetimes on February 10,2027:
This means that any certificate we issue or renew on and after that date willhave a 64 day validity period, and we expect the last 90-day certificate toexpire on May 11, 2027. We will not revoke valid certificates as a part of thisprocess.
This is the second stage of Let's Encrypt's plan, announced in 2025,to move to 45-day certificate lifetimes as required by the the CA/BrowserForum Baseline Requirements. In 2028, Let's Encrypt will switch to 45-day certificates.
- Security updates for Friday
Security updates have been issued by AlmaLinux (bind, bind9.16, freerdp, glibc, kbd, mod_auth_openidc, openssl, perl-DBI, python3.12, python3.14, and tftp), Debian (rails and twitter-bootstrap3), Fedora (barman, cockpit, hcloud, libmodsecurity, nginx-mod-modsecurity, perl-DBI, sudo, and xorg-x11-server-Xwayland), Mageia (libxfont2), Oracle (bind9.18, firefox, kernel, nodejs24, perl-DBI, and vim), Red Hat (kernel, libreswan, opentelemetry-collector, osbuild-composer, rhc, and runc), SUSE (alloy, amazon-ecs-init, bind, busybox, distribution, emacs, ghostscript, glibc, GraphicsMagick, hauler, helm, helm3, jackson-annotations, jackson-core, jackson-databind, kernel, libpoppler-cpp3, libxtst, logback, nvidia-open-driver-G07-signed, perl-DBI, php-composer2, pi-coding-agent, portprotonqt, pvetui, python-hpack, python313-GitPython, and wpa_supplicant), and Ubuntu (apache2, bluez, libarchive, libde265, libgit2, libpng1.6, libxml2, linux, linux-aws, linux-aws-6.8, linux-aws-fips, linux-fips, linux-realtime, linux-realtime-6.8, linux-aws-7.0, linux-azure, linux-azure-6.8, linux-azure-fde, linux-azure-fde-6.8, linux-azure-fips, linux-azure-7.0, linux-azure-fde-7.0, linux-gcp, linux-gcp-6.8, linux-gcp-fips, linux-gcp-7.0, linux-hwe-7.0, linux-oracle-7.0, linux-gke, linux-gkeop, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency, linux-oracle, linux-ibm-6.8, linux-nvidia, and linux-oem-6.17).
- (Updated) 32-channel logic analyzer supports 1.4GS/s sampling and USB 3.2 Gen2 streaming
Sipeed’s SLogic32U3 is a 32-channel logic analyzer designed for high-speed digital capture over USB 3.2 Gen2. The device supports configurable sample rates based on the number of active channels, direct streaming to a host system, optional analog acquisition modules, and software support across Windows, Linux, and macOS. According to the campaign, the SLogic32U3 can sample […]
- Ubuntu's Myna Speech-To-Text Now Available In Tech Preview
A few months ago Canonical announced Myna as a speech-to-text solution for Ubuntu 26.10 as part of their effort for building a context-aware desktop. Myna as of today is available in "tech preview" form not only for Ubuntu 26.10 but also the LTS releases...
- Linus Torvalds "Did What I Preach", Used AI To Make Code Decipherable & Uncovered More Bugs
After using Claude Code to draft code to help make a fundamental improvement to the Linux kernel, Linux creator Linus Torvalds continued using AI this weekend and talking up its benefits. Beyond generating initial patches and a test program for that noted I/O enhancement, he separately talked up using AI/LLMs for making patches more decipherable to understand in the process the AI noted more long-standing bugs within the Linux kernel...
- After a 10-Year Redemption Arc, No Man's Sky Is Coming to the iPhone and iPad
No Man's Sky is coming to iPhone and iPad on October 28, more than a decade after its rocky launch and long-running redemption arc. The title will cost $19.99, but a free trial will let users try it out before purchasing. Ars Technica reports: It will run on devices as far back as the iPhone 11 and the third-generation iPad Air. No Man's Sky might not have the most cutting-edge AAA graphics (though they're still strong, and they've come a long way since launch via updates), but the game's uncommon method of generating galaxies of incomprehensible scale on device consistently for all players from a single-seed happening on a phone is remarkable for those of us who remember phones performing far behind consoles or desktop PCs. This version of the game includes all of the content and systems updates to the game that have been added over the years -- the expansions that famously took the game from a rocky launch reception to a widely beloved redemption story. There are a couple of compromises, though, and it's similar to what we saw with No Man's Sky on the Nintendo Switch. Hello Games says the ability to build and explore player-made planetary settlements is limited to the iPhone 15 Pro and later, and multiplayer is not supported on any iOS device. "We are excited to see player feedback on iOS, and will support it appropriately based on how many folks are playing," the company says, leaving the door open to perhaps not supporting all future content updates if the player base isn't there to justify it.
Read more of this story at Slashdot.
- A New 'Super Ice' Is 10 Times Stronger, Bringing It Close to The Strength of Concrete
Researchers have created a strengthened "BioPykrete" by combining ice with cellulose nanocrystals and a custom protein that binds the plant-based crystals to the ice structure. In small-scale tests, the material was about 10 times stronger than regular ice and absorbed 70 times more energy before breaking. ScienceAlert reports: Instead of wood pulp's larger, disordered fibers, the researchers used cellulose nanocrystals here. Cellulose is the main structural material in plants, and in nanocrystal form, it can act as a microscopic strengthening agent for other materials, including ice -- essentially stopping cracks from spreading easily. The protein used here was called CBM3a-AFPIII, a combination of an antifreeze protein (AFP) and a carbohydrate-binding module (CBM). Its job was to act like glue, keeping the cellulose nanocrystals and ice bonded together. It's a clever approach, and the researchers think that by tweaking their ingredients and methods, they might be able to improve their 'super ice' even further. "Optimizing solidification kinetics and freezing protocols, alongside developing diverse AFP-CBM variants, could yield even higher-strength composites," write the researchers. Besides further tests of the durability of the material, the researchers are also keen to take a closer look at how cracks propagate through BioPykrete, to confirm that the underlying strengthening mechanisms are what they think they are. Further down the line, this approach could open up a whole new landscape for materials used in packaging, construction, and more: Using a custom protein to bring two unlikely compounds (ice and cellulose) together. "By bridging the gap between recombinant protein design and structural engineering, we have developed a high-performance material specifically engineered for the rigors of the world's most extreme environments," write the researchers. The findings have been published in the journal Colloids and Surfaces B: Biointerfaces.
Read more of this story at Slashdot.
- Linus Torvalds On Why AI Works For Him
An anonymous reader quotes a report from ZDNet: Many open-source developers still dislike AI. The latest example is System76 banning AI-generated content from its COSMIC desktop. At Open Source Summit Europe, Linux creator Linus Torvalds offered a different take: "I actually really like using AI," Torvald told Dirk Hohndel, his good friend and head of Ericsson Software Technology, in their latest discussion. [...] Torvalds said, "I think that you need to be very careful using AI when you're doing something real and important." Torvalds explained he hadn't always felt that way about AI programming. "I used to think it was just not very good -- but now I'm at the point where I actually really like using AI." "To be fair," he continued, "I don't do a lot of kernel programming. I'm a maintainer. The Linux kernel is a project where other people do the real work, and I act as the collection point. But I still enjoy programming immensely. I think AI is a wonderful tool if you use it correctly and treat it as a tool, and I find it makes programming much more enjoyable." Torvalds recalled, "I started programming in 1981 or so, and back then computers were much simpler, and you could understand what they were doing, and also the programs you compared your own programs to were much simpler." "It's a different story today," Torvalds said. "The bar in software engineering has grown so high that it's hard to see your own small efforts as worth anything, because you're used to all these polished, professional programs. [...] A lot of people make fun of vibe coding, but I think it's a wonderful way to find joy in programming. It makes you feel like you're doing something relevant. It allows you, as a new programmer, to do things that you would otherwise have a really hard time with." He continued: "I love the concept of AI as a gateway drug because I was working on my own toy project, the guitar pedal, and I knew what I was doing. I had a user interface that I had written myself in C that was running on a microcontroller that was running on this small screen, and I was like, "This is just stupid. It looks like something from the '80s; I wanted it to look like something from this century. But I don't do Java. I do kernels." "So, I use AI to do the things that I'm bad at," Torvalds went on, "I'd seen all the same YouTube videos you have. Give AI a prompt, and it will do it. So I gave it a prompt, and it did it, and it was horrendous. Then I said, 'Hey, look! I already did this in C. I did it the right way. It's just ugly." Torvalds acknowledged that AI tools are helping identify security vulnerabilities and improve the Linux kernel, but at the cost of overwhelming maintainers with questionable bug reports and superficial fixes. He called some submissions "mindless band-aid kind of patches." That said, despite AI's growing influence, Torvalds believes Linux's success comes from steady, incremental development rather than sweeping changes. "I'm a big believer in the whole incremental small changes that, over time, turn into big features," he said. The development goal remains "incremental improvement and steady progress all the time."
Read more of this story at Slashdot.
- Firefox 158 Now Available With JPEG-XL Support By Default
Firefox 158 is now available with JPEG XL image support enabled by default, making .jxl images a standard part of the browser rather than an experimental feature. The release also adds JPEG XL to Firefox's default image Accept header, improves Smart Window form filling, and brings new CSS typed-arithmetic support for developers. Phoronix reports: At long last, Firefox 158 is ready to go with JPEG-XL image support as an alternative to the likes of WebP, JPEG, PNG, and GIF. The default HTTP Accept header for image requests also now supports "image/jxl" for the JPEG-XL image format. Prior releases of Firefox had JPEG-XL gated by an experimental option. Firefox 158 also now supports filling forms faster in Smart Window when clicking into a form field or selecting Fill from sources. On the developer side, CSS typed arithmetic are now supported to use functions like calc() to divide two values of the same data type even if of different units. Developer changes and release binaries can be found at their respective links.
Read more of this story at Slashdot.
- Epic Games Delays Disney Project, Asks Developers To Use More AI
An anonymous reader quotes a report from Bloomberg: Epic Games delayed the release of an upcoming video-game collaboration with Walt Disney and told its developers to use more artificial intelligence tools to finish the game, according to people familiar with the project. The title had been slated for release in March, but is now delayed with no new date communicated, said the people familiar, who asked to not be identified because they weren't authorized to speak publicly. Developers on the game, a shooter featuring characters from the Marvel and Star Wars franchises, were instructed to implement an "AI first" production model using tools such as Anthropic's Claude. Humans will then manage and guide that work. "No more hand-written code," one of the game's directors told staff in an internal message reviewed by Bloomberg. The director added that all art for the game would be "generated with full AI workflows." Even before this announcement, the maker of the popular Fortnite game had been pushing hard for the use of AI across all of its divisions. But this is the first time a major video-game company has attempted to build a title primarily with AI. "We're embracing AI-accelerated development, led by Epic developers who are the visionaries and creative drivers for everything we do," said Jake Jones, communications director at Epic Games, in a statement to Bloomberg News.
Read more of this story at Slashdot.
- Mark Zuckerberg Says Meta Has Reached AI 'Frontier', Rejects Calls For Slowdown
Meta CEO Mark Zuckerberg says the company has reached the AI "frontier" with its new Muse Wonder model and will be offered as a closed, paid product for businesses. Zuckerberg also rejected calls for an industry-wide slowdown, arguing that AI can be managed with conventional guardrails as Meta continues spending heavily on models, infrastructure, and talent. The Financial Times reports: Speaking with the FT as Meta releases its Muse Wonder AI model on Monday, the billionaire chief executive claimed the new system was "going to allow much more sophisticated behaviours that are at the frontier of what is being done in the AI field." [...] "Getting to this point both required a large amount of compute and investment, and a lot of very rigorous scientific work by the group working on it over an extended period of time," said Zuckerberg. [...] Meta said Muse Wonder outperforms Anthropic's Claude Opus 5.5 and Fable 5.1 and OpenAI's GPT-6 Astra on some technical benchmarks. It said the new model can be used to carry out complex tasks from "understanding a lease to making sense of financial or health information." However, Muse Wonder will also be "closed," with its best versions sold directly to businesses. That pits it against Anthropic and OpenAI for corporate AI contracts in a serious test of its ambitions. Zuckerberg signaled further spending as Meta was "already working on the next step up," adding that its model development would "probably feel like it'll go quite a bit faster from here." However, he also shrugged off mounting fears that the technology was advancing at a rate that will soon surpass human control. [...] The Meta chief declined to be drawn on his figure for "P(doom)" -- a much-discussed Silicon Valley term to describe the probability that AI will lead to mass destruction. Instead, he argued that responsibility should fall on the individual lab to ensure model safety. "I'm much closer to the belief that AI is a technology that can be engineered with normal guardrails and built responsibly than the anthropomorphic vision of AI, which is that it is just going to go do its own thing," he said. Zuckerberg has previously rejected calls by the heads of AI labs such as Anthropic's Dario Amodei and OpenAI's Sam Altman for an industry-wide "slowdown" in AI development. He also played a key role in crafting US President Donald Trump's White House "Accord on Super Intelligence," setting out principles for self-regulation of the industry, which critics say falls far short of a formal global AI governance regime.
Read more of this story at Slashdot.
- Google's Fitbit Edge Debuts a Replaceable Battery, Brings Back the Screen
Google has introduced the $179 Fitbit Edge, a new fitness tracker with a 1.34-inch OLED display, built-in GPS, ECG support, week-long battery life, and Fitbit's first user-replaceable battery. "And unlike the Pixel Watch, it's compatible with Android and iPhones via the Google Health app," reports Wired. From the report: The Edge has a user-replaceable battery, a Fitbit first, aligning with Google's efforts to make its Pixel Watch more repairable. (Likely also due to new battery regulations set to take effect next year in the European Union.) Repair options will vary by region and availability. If you find the Pixel Watch's round face too bulky, the Edge's capsule-shaped alternative might suit smaller wrists better. If the Charge 6's 1.04-inch display was too small, the Edge upgrades it to a larger 1.34-inch screen. The difference is noticeable, and that extra real estate could make a real impact when glancing at your metrics mid-workout. The Edge borrows a few more attributes from the Pixel Watch, including an altimeter that uses atmospheric pressure to measure elevation changes. That means it can record elevation gain and loss during outdoor activities, track floors climbed, and add more context to your outdoor stats. It also has a far-field skin temperature sensor, replacing the standard device temperature sensor found in other Fitbits. By bringing some of the Pixel Watch's more advanced hardware to a fitness-first wearable, Google is giving the Edge a compelling middle-ground position in its lineup at a Fitbit-friendly price. The Edge inherits the Fitbit Air's improvements while restoring several Charge 6 features the screenless tracker lacks, including built-in GPS and electrical sensors that work with the electrocardiogram (ECG) app. You can also control music playback on a connected Bluetooth device, as you could with the Charge 6, and Google Maps turn-by-turn directions will arrive later this year. [...] With a Google Health Premium subscription, the Edge can track blood pressure trends without manual calibration and insulin resistance trends without requiring a blood draw. Google first announced these capabilities alongside the Pixel Watch 5's debut, but they only became available at the end of September. They're also available on the Air, keeping Google's screenless tracker up to date as its lineup expands.
Read more of this story at Slashdot.
- Russia Was Not Ready For the Data Center War It Started With Ukraine
An anonymous reader quotes a report from Ars Technica: When Russia began attacking Ukrainian data centers and telecommunication infrastructure, it apparently failed to prepare for possible retaliation. Now Russia's digital services are facing widespread outages after Ukrainian drone strikes knocked out three of the largest data centers owned by Russian tech giant Yandex within several days. Pro-Kremlin bloggers are warning that Russia's centralized digital economy could collapse because the country is not prepared for the "data center war" it started, according to posts translated by the pseudonymous independent researcher ChrisO_wiki. The Russian commentators also suggested that Ukraine's decentralized digital services could prove more resilient than Russia's system if the countries continue trading such blows. Russia initially launched a drone strike campaign targeting Ukrainian data centers and mobile phone networks in late September. The attacks temporarily disrupted Internet and cell phone service for up to 100,000 households in the Ukrainian capital of Kyiv and came as part of a broader long-range strike campaign that has involved Russian missiles and jet-powered drones hitting Ukraine's power grid infrastructure, transportation hubs, and even residential apartment building blocks. But Ukraine soon began striking back at data centers owned by the Russian company Yandex, also known as "Russia's Google," in what Ukrainian President Volodymyr Zelenskyy has described as a "symmetrical response." [...] More importantly for Russian society, the damage to Yandex's data centers has reportedly caused interruptions or outages to popular Russian payment apps and digital banking services, email, e-commerce platforms, video streaming services, ride-hailing and food delivery apps, and navigation and map services. Yandex's search engine also accounts for about 70 percent of the market share in Russia. The disruptions are even more widespread, because the data center damage also impacts Yandex's cloud computing service, which counts some of Russia's largest companies as customers, according to The Moscow Times, an independent newspaper. These include large grocery and fast-food chains as well as a household appliance retailer.
Read more of this story at Slashdot.
- Hackers Heat French Supermarket Fridges, Sparking Fires and Spoiling Food
Hackers remotely manipulated connected refrigeration systems at hundreds of French supermarkets, reportedly pushing some fridges and freezers to 50C (122F), spoiling food and even sparking fires. According to Reuters, French Prime Minister Sebastien Lecornu ordered a cybersecurity investigation into the hacks, with similar incidents reported in Spain, Portugal, Poland, Germany, and Belgium. In France, Carrefour reported 80 affected stores, Monoprix said 5% of its locations were hit, and Les Mousquetaires said refrigerators at roughly 150 Intermarche stores were heated to 50C for six hours. From the report: Supermarket cold aisles are typically run by control panels that manage an entire store's fridges and freezers and can be accessed over the internet, which lets maintenance companies adjust them from anywhere. The source close to Lecornu said ANSSI had identified a vulnerability in software supplied by Danish company Danfoss. Danfoss said it was "aware of incidents in France affecting a limited number of refrigeration management systems." The affected units "were running outdated firmware," Danfoss said, adding that it had "long advised customers to keep supported systems updated with the latest firmware and to migrate legacy systems to current-generation solutions." On August 9, cybersecurity firm Claroty's Team82 published research detailing vulnerabilities in the Danfoss AK-SM 800A controller. According to the report, software updates issued by Danfoss addressed issues that could have allowed attackers to bypass authentication controls and execute code on compromised devices.
Read more of this story at Slashdot.
- AI Coding Agents Generate More Code, But Not More Software
A study of more than 700 software firms found that AI coding agents significantly increase the amount of code developers produce, but not the amount of software companies actually ship. Ars Technica reports: A recent study (PDF) of actual coding practices across hundreds of firms finds that human code review forms a significant "bottleneck" for the overall efficiency of AI coding tools, resulting in "little evidence that firms increase software output or reduce employment" by using them. Any efficiency increased during the actual coding phase, the study authors find, is "absorbed by downstream constraints in the production process"; as "the code review process significantly increases in length, pull requests are more likely to require revisions, and reviewers leave more comments." [...] In terms of raw code being produced, the results are clear and stark. The introduction of AI coding agents at a firm leads to a 30 percent increase in total lines of code generated, a 20 percent rise in the number of total commits, and a 23 percent increase in pull requests on average, the researchers write. But all that extra code doesn't translate directly into improved software output on the firm level. On the contrary, the resolution rate for Issues and Epics (i.e. wholesale software features) tracked by tools like Jira did not change in a statistically significant way after AI tools were introduced (the researchers also found no "compositional shift" in the size or complexity of those Jira-tracked issues across the AI introduction). The reason for that discrepancy can be found directly in the code review process, which takes markedly longer on average after the introduction of AI coding agents. Overall, the average "review process" time between a pull request getting submitted and it being merged into the codebase balloons 49 percent on average after AI agents are introduced. That effect can be seen in more granular data, too, with "the share of pull requests with changes requested nearly doubl[ing], and the number of comments per pull request increas[ing] by 35%" following the AI agent shift, the researchers write. In response to this change, the researchers found a 14 percent increase in the share of workers performing code reviews after AI agents' introduction. They also write that they "cannot attribute significant employment changes to AI" after looking at total active workers across Jellyfish and cross-referencing with LinkedIn data at those firms. While AI could also theoretically help with this review process, the researchers found that, so far, that impact has been marginal. Although 80 percent of measured firms used some form of AI code review by March 2026, AI agents were only responsible for 23.3 percent of all review comments and 10.8 percent of all pull requests, suggesting humans were still responsible for the vast majority of this work.
Read more of this story at Slashdot.
- 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]
- 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.
- Microsoft claims its optimising Windows for 8GB of RAM
Speaking of Windows and performance, how about that RAM crisis? Microsoft is feeling the squeeze too, and is apparently doing work up and down the Windows stack to improve its memory consumption. Microsoft’s Windows chief Pavan Davuluri has admitted that the rising cost of memory is pushing the company to make Windows 11 use less RAM. Microsoft is working on the Windows memory manager, memory compression, WinUI 3 and WebView2, and has made “memory optimization for 8GB and above” an official priority for the rest of 2026. ↫ Abhijith M B at Windows Latest This might be the only positive consequence of the RAM crisis.
- 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
- Slackware 16 Alpha 1 Released with Linux 6.18 LTS, GCC 16.2, and Plasma 6
by George Whittaker
One of Linux's oldest surviving distributions is moving closer to its next major release. Slackware 16 Alpha 1 became available on September 5, 2026, marking the first formal alpha milestone on the road toward Slackware Linux 16. The release follows a major rebuild of Slackware-current using a substantially newer GNU toolchain and brings together several upgrades that have accumulated since Slackware 15.0 arrived more than four years ago.
The alpha combines Linux 6.18 LTS, GCC 16.2.0, glibc 2.44, GNU Binutils 2.47, KDE Plasma 6, and numerous updated user-space packages while retaining much of the deliberately traditional architecture that has distinguished Slackware for decades.
For longtime Slackware users, Alpha 1 is particularly significant because it provides the clearest indication yet that the lengthy Slackware 16 development cycle is moving toward an eventual stable release.
Slackware 16 Finally Reaches Alpha
Slackware doesn't operate according to the predictable six-month or annual release schedules used by many other Linux distributions.
Instead, development takes place continuously through the Slackware-current branch. Patrick Volkerding and other contributors update that development tree until it reaches a state considered suitable for a stable release.
The previous major version, Slackware 15.0, was released in February 2022. More than four and a half years later, Slackware-current has now officially reached the first alpha milestone for version 16.
Volkerding marked the milestone following a complete rebuild of the distribution with its newly upgraded compiler, C library, and binary utilities.
The short changelog announcement even suggested there might finally be "a light at the end of the tunnel," a promising indication for Slackware users waiting for version 16.
The Entire Distribution Was Rebuilt
One of the most consequential changes behind Alpha 1 is a complete package rebuild.
Slackware's development toolchain has moved to:
GCC 16.2.0 glibc 2.44 GNU Binutils 2.47
After introducing those components, Slackware rebuilt the distribution's packages against the updated environment.
A full rebuild is much more significant than simply replacing three packages.
GCC is responsible for compiling much of the software distributed with Slackware, glibc provides fundamental C library functionality used throughout Linux user space, and Binutils supplies essential development utilities including the GNU assembler and linker.
Rebuilding the distribution against these versions gives Slackware 16 a considerably newer foundation than its predecessor.
Go to Full Article
|
