|
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/All+Images)
(Single Column)
- Debian Samba Critical Access Bypass Remote Code Exec Advisory DSA-6297-1
Several vulnerabilities have been discovered in Samba, a SMB/CIFS file, print, and login server for Unix, which might result in bypass of access checks, overwrite of files in unintended situations using the WORM vfs module, installing CA certificates over http without verification when auto-enrollment GPO is enabled, denial of service or remote code
- [$] LWN.net Weekly Edition for May 28, 2026
Inside this week's LWN.net Weekly Edition:
Front: Dirk and Linus talk; BPF and GCC; private memory modes; BPF page-cache policies; major page faults; LLM kernel review; tiered-memory support; transparent huge pages; page mappings; Model Openness Tool. Briefs: Stenberg security stress; GTK PDF problems; Morton 2004 keynote; OpenBSD 7.9; Bambu's AGPLv3 violations; Quotes; ... Announcements: Newsletters, conferences, security updates, patches, and more.
- Interview session with Jonathan Corbet
The Linux Foundation will be hosting alive interview with LWN co-founder Jonathan Corbet. The event willtake place on Tuesday, June 2 at 8:00AM Pacific daylight time (UTC-7).Registration is open for those who would like to attend.
- [$] MOT: a tool to fight openwashing in AI
Many large language models (LLMs) are described as open source, butif one looks a bit deeper it turns out that is not actually so; themodel may be free to download, it may be "open weight", but itdoes not fit the Open SourceInitiative (OSI) Open SourceDefinition (OSD). Assessing the actual openness of models is noteasy, as Arnaud Le Hors explained in his talk about the Model Openness Tool (MOT) at OpenSource Summit North America 2026. The tool is designed to helpusers of LLMs understand to what degree a model is (or is not) open,and to combat the openwashingthat is prevalent with LLMs.
- Andrew Morton's 2004 OLS keynote
I recently presented a brief tribute to Andrew Morton at the 2026 Linux Storage, Filesystem, MemoryManagement, and BPF Summit; it included a suggestion that reading (orre-reading) his 2004 Ottawa Linux Symposium keynote would be instructive.This talk, given immediately after the KernelSummit session that decided to fundamentally change the kernel'sdevelopment model, tells a lot about how the kernel project got to where itis today. The text of that speech was hosted on Groklaw, and has sincebeen replaced by crypto spam, which is rather less useful. In the hopes ofpreserving this seminal moment, the transcript has been rescued thanks to theWayback Machine and is presented here.
- [$] Further progress toward removing the page map count
The mapcount field was created to track the number of mappings(page-table entries) that refer to the given page. Among other things, amapcount of zero means that the page has no references and can bereclaimed. Maintaining mapcount has become increasinglychallenging and expensive as the memory-management system has grown incomplexity, so Hildenbrand has been looking for ways to get rid of it.This session was, he said, maybe one of the last times he will have tobring up this topic.
- Security updates for Wednesday
Security updates have been issued by AlmaLinux (bind, buildah, compat-libtiff3, compat-openssl11, containernetworking-plugins, crun, delve, dnsmasq, dovecot, edk2, firefox, freeipmi, gdk-pixbuf2, giflib, git-lfs, glib2, go-fdo-client, go-fdo-server, golang, grafana, grafana-pcp, gstreamer1-plugins-bad-free, gstreamer1-plugins-base, gstreamer1-plugins-good, and gstreamer1-plugins-ugly-free, iputils, jq, kernel, krb5, libcap, LibRaw, libsndfile, libsoup, libsoup3, libssh, libtiff, libvirt, linux-sgx, luksmeta, mingw-glib2, NetworkManager, nginx, nginx:1.24, nginx:1.26, openexr, openssh, openssl, opentelemetry-collector, p11-kit, PackageKit, podman, python-jwcrypto, python-markdown, python-tornado, python3.11, python3.12, python3.14, python3.9, qemu-kvm, rsync, skopeo, sudo, systemd, thunderbird, tomcat, unbound, vim, xorg-x11-server, xorg-x11-server-Xwayland, yggdrasil, and yggdrasil-worker-package-manager), Debian (imagemagick, kdenlive, memcached, node-shell-quote, and samba), Fedora (chromium, curl, editorconfig, haproxy, perl-Crypt-DSA, perl-HTTP-Tiny, poppler, rust-afterburn, rust-coreos-installer, rust-eif_build, rust-rpm-sequoia, rust-sequoia-chameleon-gnupg, rust-sequoia-git, rust-sequoia-keystore-server, rust-sequoia-octopus-librnp, rust-sequoia-openpgp, rust-sequoia-sop, rust-sequoia-sq, rust-sequoia-sqv, and uriparser), Oracle (compat-libtiff3, dnsmasq, firefox, freeipmi, kernel, and uek-kernel), Slackware (mozilla), SUSE (assimp, firefox, glibc, gnutls, go1.25-openssl, go1.26-openssl, kernel, kubevirt, leancrypto, libarchive, libsndfile, mcphost, nginx, openssh, podman, python-GitPython, rsync, and samba), and Ubuntu (ayttm, dnsmasq, libssh2, linux-azure, linux-azure, linux-azure-6.17, linux-iot, linux-lowlatency-hwe-5.15, ngtcp2, onnx, opencc, protobuf, python-git, samba, xdg-dbus-proxy, and xmlrpc-c).
- Arias: Human proof for FOSS contributions
Rodrigo Arias Mallo, maintainer of the Dillo web browser, has written ablog postwith a proposal on one way to ensure that a contribution is written bya human and not AI; he suggests asking new contributors to recordtheir programming session using asciinema.
In the same way that LLMs generate patches, they can also generatethe asciinema recordings themselves. Then, the contributors can lie tothe reviewers pretending to have made the edits. Perhaps surprisingly,this is not a easy task for LLMs, at least from my observations. Thecorpus of recordings of developers making mistakes and thinking thewhole process of editing a file is not as large as the corpus of FOSSprograms and patches in which to train an LLM. During my very simpletests I haven't been able to generate an asciinema session thatremotely resembles what I would expect from a human, and even less sofrom a human with a nice editor theme and editing an existing Dillosource file.
The Dillo project is not yet requiring asciinema recordings, but hesaid that he would like to test the theory further. LWN covered asciinema inJanuary 2026.
- Stenberg: The pressure
Curl maintainer Daniel Stenberg writes aboutthe stress of keeping up with the current flood of security reports.
This is a never-before seen or experienced pressure on the curl project and its security team members. An avalanche of high priority work that trumps all other things in the project that is primarily mental because we certainly could ignore them all if we wanted, but we feel a responsibility, we have a conscience and we are proud about our work. We feel obliged to fix security problems in the software we have helped shipped to every device on the globe. This is personal to us.
With about half the release cycle left until the pending release ships, we already have twelve confirmed vulnerabilities meaning twelve pending CVE announcements. That's a new project record and it also means we will reach thirty published CVEs in 2026 even before half the calendar year has passed. The projected total amount of curl CVEs published through the whole year is therefore at least double this number!
- [$] Better automatic management of transparent huge pages
Huge pages can improve performance by increasing translation lookasidebuffer (TLB) utilization and reducing memory-management overhead.Transparent huge pages (THPs) are supposed to make huge-page usage,well, transparent, Nico Pache said at the beginning of his session in thememory-management track of the 2026 Linux Storage,Filesystem, Memory Management, and BPF Summit. That transparency hasnever worked as well as many would like; he has been working onimprovements to make it easier for applications to use huge pages on Linuxsystems. A following session, led by David Hildenbrand, was focused on howTHPs could be taken away from processes that are not using them fully.
- Security updates for Tuesday
Security updates have been issued by Debian (postorius and spip), Fedora (bind, bind-dyndb-ldap, linux-firmware, tor, and unbound), Mageia (ffmpeg, nginx, perl-Imager, and tigervnc, x11-server, x11-server-xwayland), Oracle (firefox and kernel), Red Hat (buildah, git-lfs, go-toolset:rhel8, golang, golang-github-openprinting-ipp-usb, grafana, grafana-pcp, gvisor-tap-vsock, java-1.8.0-openjdk, java-17-openjdk, java-21-openjdk, opentelemetry-collector, osbuild-composer, podman, rhc, rhc-worker-playbook, skopeo, and yggdrasil), SUSE (amazon-ecs-init, assimp, azure-storage-azcopy, busybox, firefox, gnutls, graphicsmagick, helm, kernel, leancrypto, libpng16, libppsdocument4_0-6, libsndfile, mcphost, nano, nginx, perl-http-tiny, perl-XML-LibXML, python-urllib3, python-urllib3_1, python311-ocrmypdf, python312, rclone, rsync, xen, and xz), and Ubuntu (dotnet8, dotnet9, dotnet10, linux-intel-iot-realtime, linux-lowlatency, linux-nvidia-6.8, linux-nvidia-tegra, linux-nvidia-tegra-igx, nltk, simpleeval, and vim).
- ReactOS Now Running On ARM64 In Experimental Form
ReactOS as the "open-source Windows" project working to implement binary compatibility for computer programs and drivers for Microsoft Windows now has experimental support for running on 64-bit ARM...
- Websites Have a New Way To Spy On Visitors: Analyzing Their SSD Activity
An anonymous reader quotes a report from Ars Technica: Now sites have a new way to spy on their visitors: measuring subtle interactions with their solid-state drives. The technique, named FROST (fingerprinting remotely using OPFS-based SSD timing), allows sites to monitor other sites a visitor is viewing and what apps are open on their devices. The technique, laid out in a research paper (PDF), exploits a side channel, a form of leak resulting from physical manifestations such as electromagnetic emanations, data caches, or the time required to complete a task. By measuring the manifestations, attackers can decrypt encrypted traffic and infer other confidential data. The attack that FROST uses is known as a contention side channel, which measures the interaction of various processes all using (or competing for) a given resource. By measuring the timing of certain I/O (input-output) operations of the SSD a visitor is using, the researchers were able to determine the websites open in other tabs -- even on other browsers -- and the apps that were open on the visitor's device. FROST requires no interaction from the visitor other than opening the site hosting the attack. [...] Unlike previous contention side-channel attacks on SSDs, FROST runs exclusively in the browser. It uses JavaScript that interacts with the OPFS (origin private file system), an allocated storage space that's reserved for a specific site to run code needed to complete a given task. Websites can create one with no interaction required by the visitor. While each file system is sandboxed, meaning it's isolated from other websites and from the device system itself, the JavaScript can measure the I/O interactions. Then, by running those interactions through a pretrained convolutional neural network -- a system that uses deep learning to analyze text, audio, and images -- the attacker can deduce various apps and websites open on the device. "The attacker continuously measures SSD contention by performing random reads from a large OPFS file," the researchers explained. "SSD contention caused by user activity causes measurable latency differences for these read operations. By training a convolutional neural network (CNN) on these traces, the attacker can fingerprint user activity on the host system by classifying new traces using the trained model."
 
Read more of this story at Slashdot.
- Meta To Start Testing AI Subscription Services
Meta will begin testing paid subscriptions for its Meta AI app and website, with a $7.99/month Meta One Plus plan and a more capable $19.99/month Meta One Premium plan offering. The test will start next month in Singapore, Guatemala, and Bolivia as Meta looks for AI revenue beyond advertising while continuing to offer a free tier. CNBC reports: Naomi Gleit, the head of product at Meta, revealed the subscription testing in an Instagram video, announcing that the plans "give people who use Meta AI more to work with, more capacity, bigger, more complex requests, and more room to create for businesses and creators." Meta One Plus will cost $7.99 a month and the Meta One Premium plan will cost $19.99 a month, the company confirmed. The more expensive version offers users additional computing capacity to produce more comprehensive responses and other advanced features. The company will continue to provide a free version of the app and site. "We're offering premium tools that allow you to enhance presence, supercharge content, automate tasks, and protect your brand," Gleit said in the post. "We're also thinking about how to bring this all together in a way that makes sense."
Read more of this story at Slashdot.
- Nvidia To Spend $150 Billion a Year In Taiwan
Nvidia CEO Jensen Huang says the company plans to spend around $150 billion a year in Taiwan, calling it the "epicenter of the AI revolution." "Four years ago, five years ago, Nvidia was spending about $10, $15 billion dollars a year in Taiwan. Now we're spending $100, going to $150 billion dollars in Taiwan each year," Huang said. Reuters reports: Huang was speaking at a launch celebration in Taipei for the chip company's planned Taiwan headquarters, which he said will break ground this year and aims to become operational in 2030. He did not provide a timeframe for the number of years the company plans to invest $150 billion. The Taiwan headquarters will bring Nvidia closer to TSMC, the world's largest contract chipmaker which makes many of the advanced semiconductors powering the trend towards AI and is a major supplier to the U.S. tech company. "Taiwan is booming," Huang said on stage at the celebration which was attended by his parents, wife, daughter and son in addition to around 1,000 employees. "Taiwan is the epicentre of the AI revolution. This is where the chips come, packaging comes, this is where the systems are made, this is where AI supercomputers were created. The number of partners we work with here in Taiwan, incredible."
Read more of this story at Slashdot.
- Rust Will Save Linux From AI, Says Greg Kroah-Hartman
Linux stable kernel maintainer Greg Kroah-Hartman says Rust can help Linux deal with a flood of AI-discovered security bugs (namely Dirty Frag, Copy Fail, and Fragnesia) by preventing common C mistakes around memory, locking, error handling, and untrusted data at build time rather than during human review. It's "not a silver bullet" and does not mean rewriting the whole kernel, but he said new drivers and subsystems will increasingly use Rust as Linux evolves forward. ZDNet reports: Kroah-Hartman illustrated those pitfalls with real C bugs in the kernel, including a 15-year-old Bluetooth bug that dereferenced a pointer without checking it and a Xen bug where "we forgot to unlock" in an error path. "The majority of the bugs in the kernel are this tiny, minor stuff," he explained. "Error conditions aren't checked, locks aren't forgotten, unreleased memories leak, and vulnerabilities add up over time. They crash the kernel. This is what we live with in C. This is why we don't like it." Kroah-Hartman argued that the "best beauty of Rust" is catching those mistakes at build time rather than in review. For example, when it comes to locking, he highlighted Rust's locking abstractions in the kernel: "The only way you can get access to inner pointers of structures is by grabbing that lock, and releasing the lock automatically. The compiler does it, it's guarded, the lock happens, everything's happy. You just can't write code to access these values...without grabbing the lock. The compiler will not let you." Those properties, he argued, directly remove a huge fraction of the bugs he sees: "This is going to save us those two things. First, 60% of the bugs in the kernel right there, they're gone. Thank you." The payoff is earlier, more automated enforcement: "If this happens at build time, not review time, don't make me a maintainer who has to read your code [and] say, 'Oh, then you properly check that error value. Oh, did you properly grab the locks in the right spot?' Rust gives us that for free. This is the best thing ever." Even if Rust vanished tomorrow, Kroah-Hartman argued, it has already forced the kernel to clean up C code and interfaces. He credited Rust's influence outright: "We stole this from Rust. Thank you. It's a good idea, so if Rust disappeared tomorrow, we have cleaned up the C code in the kernel so much and taken in the ideas. We thank you, you've made Linux better with it just by existing." [...] What ultimately sold a number of core maintainers, including him, on Rust was how it "makes reviewing code easier." With CI [Continuous Integration] bots enforcing builds and Rust's type system enforcing key invariants, maintainers can "focus on the logic" rather than resource bookkeeping: "I can care about that one function. I don't have to worry about the rest of this stuff, because I assume that it works properly, because it was built properly." Internally, he said, the top maintainers have already made their call on Rust's status: "The Linux kernel maintainers, we get together every year and talk about what the processes are doing. Last year, we said the Rust experiment is over. It's not an experiment. This is for real." The rationale: "The people behind it are real. We trust them. We know what they're doing. They've shown and put in the work to make Rust a viable language in the kernel, and we're going to make this stick. Let's go full speed ahead. And, as always," he said wryly, "world domination proceeds." "If you never remember anything else in my talk, just remember these four words. It came from Microsoft Security many, many years ago," Kroah-Hartman told attendees. "They realized all input is evil. You have to validate all input."
Read more of this story at Slashdot.
- The AI Fight Brewing Inside the New York Times
An anonymous reader quotes a report from The Verge: How newsrooms should use AI -- or if they should at all -- has been a recurrent debate within the media industry over the last several years. Increasingly, these rules are being hammered out at the bargaining table between unions and publishers. Right now, employees at The New York Times are gearing up for a fight. Unionized staff with the Tech Guild say Times management has refused to provide the union with information related to how the company has used AI, its plans for AI use in the future, and how it will affect employees' jobs and workflow. (The union filed an unfair labor practice charge earlier this month.) The Tech Guild, a NewsGuild of New York unit of around 700 software engineers, designers, product and project managers, and data analysts, also filed grievances saying Times management violated their collective bargaining agreement when it started using two internal AI tools that track and evaluate employee performance and activity. [...] Both the Tech Guild and the Times Guild (which represents 1,500 editorial, ad sales, and support staff at the Times) filed unfair labor practice charges against the Times, saying that company violated labor law by refusing to respond to their requests for information around AI use at the outlet. The Times did not respond to specific questions about how it uses DX and Glean, but spokesperson Danielle Rhoades Ha said in an email that the company disagrees with the characterizations made in grievances and that it would respond as part of its "normal contractual process." "Likewise, we will respond to this Request for Information (RFI) in due course as we've done with 80+ other RFIs from the Guild in recent years," Rhoades Ha said. The Times Guild is currently bargaining a new contract, pushing for robust protections against AI, like requirements that a human is behind any AI tool being used, that any journalism utilizing AI is transparently labeled, and that staff are compensated for AI model training deals the company might make. The Times deploys artificial intelligence tools for some reporting, like using it to parse millions of documents related to Jeffrey Epstein or scan satellite images of Gaza to try to find where Israel had dropped a specific kind of bomb. [...] [Ben Harnett, a software engineer at the Times and chair of the unit's generative AI committee] emphasizes that the unit's position is not that AI shouldn't ever be used, but that workers should have a say in how it's deployed. Metrics like how many tokens an employee uses or how often they're using AI to do their jobs create pressure to do more and incentives that don't align with doing quality work. "It's going to distract [you] from actually doing a good job, which is what we think the company should want," he says. Two of the contentious AI tools mentioned in the report are DX and Glean. DX is an engineering productivity tool that tracks a developer's output, generative AI use, efficiency, and other related metrics. Meanwhile, Glean is an internal knowledge-search tool that indexes materials like wikis, GitHub documents, Google Docs, and emails so employees can query company information. The concern, according to Times Tech Guild members, is that data meant to measure broader developer experience is now being applied to individuals and cited in performance or disciplinary contexts. There's also worry that it could be used to monitor individual contributions and produce false or misleading results.
Read more of this story at Slashdot.
- YouTube To Automatically Detect, Label AI-Generated Videos
YouTube will begin automatically labeling videos when its systems detect "significant" photorealistic AI use, while also making AI-content disclosures more visible below long-form videos and directly on Shorts. "We've heard consistently from our community that they value transparency when it comes to generative AI content," YouTube said in a blog post. "These changes are designed to balance transparency with creator control." Variety reports: Under YouTube's guidelines, creators will still be required to manually disclose when they use realistic AI. But starting this week, it also will roll out a new internal system to help identify AI-generated content. "If a creator doesn't specify whether or not they used AI, but our systems detect significant photorealistic AI use, we will now automatically apply a label," YouTube said. YouTube creators who believe their content was incorrectly flagged as AI-generated can modify the disclosure status using the YouTube Studio tool. However, according to YouTube, the AI labels will "remain permanent" in some cases, including for content created using YouTube's own AI tools (such as Veo or Dream Screen) and for content that contains C2PA metadata (based on standards from the Coalition for Content Provenance and Authenticity) that indicates it was fully AI-generated. In addition, YouTube is moving the disclosure label for photorealistic and meaningfully AI-altered or AI-generated content to a more prominent position. Until now, YouTube labeled AI content in a video's expanded description. Going forward, for long-form videos, the AI label will now appear directly below the video player and above the description. For YouTube Shorts, the label will appear as an overlay on the video itself. "The goal here is context at a glance. If it looks real but was made with AI, viewers will know immediately," said Rene Ritchie, YouTube head of editorial and creator liaison. He added that the AI labels alone "do not affect how our videos are recommended or whether they can earn money. This is purely about giving viewers the right information at the right time."
Read more of this story at Slashdot.
- Roku Updates Its UI For the First Time In a Decade
Roku is rolling out its first major homescreen update in a decade. The UI doesn't look too dramatically different, but users will notice more personalization-driven changes, including frequently used apps, "top picks," household-specific layouts, and recommendations based on viewing habits. Rest assured, Engadget adds, "Everything is still in various shades of purple and Roku City is still available as a screensaver." From the report: Today's update certainly brings more clutter into the mix, including a new "marquee" ad spot that takes up a large chunk of the screen. It's worth remembering that Roku makes most of its money on ads and not its hardware. "More than 100 million households will feel the difference the moment they turn on their TV -- and it opens up a better, more powerful experience for our partners as well," CEO Anthony Wood wrote in a blog post. The update does bring one novel feature, according to The Hollywood Reporter. The company says the new homescreen platform will adapt to how households use Roku devices. This is to accommodate "multiple people living in homes." For instance, a child's bedroom TV might have a different homescreen than TV in the living room, and so forth. This expansion is rolling out right now to US-based customers, though it might take a while to reach every user. Roku says "additional countries will follow in the coming months."
Read more of this story at Slashdot.
- Tech CEOs Are Apparently Suffering From AI Psychosis
An anonymous reader quotes a report from TechCrunch: There is a certain wildness in the tech industry these days that both mimics previous eras of large changes, like cloud computing (runaway costs in the early days), and is like nothing we've ever seen before (record revenues accompanied by mass layoffs). One possible explanation: tech executives, especially CEOs, are collectively suffering from delusions of AI grandeur. And at least one tech CEO has said as much out loud: Box founder Aaron Levie. "CEOs are uniquely prone to AI psychosis because they're sufficiently distant from the last mile of work that still has to happen to generate most value with AI," Levie wrote on X. CEOs "play with AI," develop a prototype, or generate a contract, to use Levie's examples, and then make the leap to believing agents can do the work. But these top-level executives aren't the people who have to review code, discover bugs, and identify calls to hallucinated libraries before software is deployed. They aren't responsible for training AI models on a company's idiosyncratic contract terms, nor do they have to spend days combing through contracts to find sneaky terms, as Levie indicates. In other words, Levie's theory posits, CEOs don't really understand processes well enough to know what really can and can't be automated. But that lack of knowledge doesn't stop them from acting on their beliefs. [...] So what are CEOs to do instead? Levie advises CEOs to use AI "a ton" to really see what it can and can't do, "and come out the other side with an appreciation for both the upside and the real work."
Read more of this story at Slashdot.
- Dropbox CEO Drew Houston To Step Down After 19 Years
Dropbox founder Drew Houston is stepping down as CEO after 19 years and will become executive chairman, with product chief Ashraf Alkarmi set to take over after a co-CEO transition period. CNBC reports: Drew Houston founded Dropbox nearly two decades ago at age 24, eventually becoming a household name in Silicon Valley and the first tech entrepreneur to take a company from the Y Combinator incubator program all the way to the public market. Now, at 43, Houston is ready to do something else. [...] By almost any measure, Houston has had a great run at Dropbox, helping pioneer the cloud storage market, competing head-to-head with Google and Apple and building a net worth of more than $2 billion, thanks to substantial ownership in his company. But in the land of outsized expectations, Houston has overseen a company that peaked too soon and never became a generation-defining brand. Dropbox's current market cap of just over $6 billion is down by half from the high price on its first day of trading in 2018, and is below the $10 billion valuation it was ascribed by private market investors in 2014. [...] In its latest quarterly earnings report, Dropbox said it has more than 18 million paying users, and the service remains popular with media professionals, graphic designers, architects, and others who share files and photos as part of their daily work. "Part of me has always thought, oh yeah, I'll be the CEO of Dropbox until my last gasp of my career," he said. "There's never a perfect time, there was no part of me where I was like, 'oh, this date is the date where it's going to happen.'" Since Alkarmi joined Dropbox from Vimeo in late 2024, the company has "become a lot more responsive to our customers and is taking bigger swings on innovation," Houston said. "I trust the right leader," he said. "The company's in the right place."
Read more of this story at Slashdot.
- Company Behind School Bus AI Cameras Wants To Share Footage With Police
joshuark writes: BusPatrol, a company that has installed AI-powered cameras in tens of thousands of school buses around the U.S., now plans to turn those cameras into automatic license plate readers (ALPRs), capturing the location of every vehicle the buses drive past, and give that data to law enforcement, 404 Media has learned. BusPatrol has already taken steps to share the collected data with law enforcement contracting giant Axon, according to leaked BusPatrol documents and a source with knowledge of the plans. BusPatrol has acknowledged how controversial its plan to collect and share this data is, pointing specifically to concerns about ICE using license plate data, but emphasizes the likely success of selling the angle of protecting children. "Who would have thought that school buses would be turned into the mass surveillance state?," Michael Soyfer, an attorney from the Institute for Justice, which has various ongoing ALPR-related lawsuits The Institute for Justice argues that warrantless use of ALPR systems is unconstitutional, describing similar systems as a "dragnet." Kate Spree, senior manager of brand communications at BusPatrol, said in an email "This inquiry is based on a false premise and inaccurate information. BusPatrol does not pool or sell data across communities; student safety program data is used only to support the BusPatrol program in the community where that data was created." When 404 Media asked clarifying questions and said that the reporting is based on leaked BusPatrol material, Spree stopped replying to text messages and emails. This plan gives new meaning to the animated cartoon series "The Magic School Bus"... Further reading: FBI Wants to Buy Nationwide Access to License Plate Readers
Read more of this story at Slashdot.
- From DHCP to SZTP – The Trust Revolution
By Juha Holkkola, FusionLayer Group The Dawn of Effortless Connectivity In the transformative years of the late 1990s, a quiet revolution took place, fundamentally altering how we connect to networks. The introduction of DHCP answered a crucial question, Where are you on the network?!, by automating IP address assignment. This innovation eradicated the manual configuration [0]
The post From DHCP to SZTP – The Trust Revolution appeared first on Linux.com.
- Using OpenTelemetry and the OTel Collector for Logs, Metrics, and Traces
OpenTelemetry (fondly known as OTel) is an open-source project that provides a unified set of APIs, libraries, agents, and instrumentation to capture and export logs, metrics, and traces from applications. The project’s goal is to standardize observability across various services and applications, enabling better monitoring and troubleshooting. Read More at Causely
The post Using OpenTelemetry and the OTel Collector for Logs, Metrics, and Traces appeared first on Linux.com.
- Mesa 26.0.8 Released To End Out The Series
Eric Engestrom announced the release of Mesa 26.0.8 today as the latest stable point release of that Q1'2026 driver series and the last planned update for that stable series...
- Linux Developers Looking At Retiring The x32 ABI
The Linux x32 ABI for x86_64 processors allow making use of the full 64-bit register file and wide data path but retaining 32-bit pointers to provide for a smaller memory footprint when not needing 64-bit pointers. Linux x32 came to the party late and didn't enjoy much adoption over the years and is now looking at possible removal from the Linux kernel...
- Intel TDX Runtime Updates Looks Like It Will Land For Linux 7.2
A feature that has been worked on for a while now by Intel Linux engineers is for allowing run-time updates of the Trusted Domain Extensions (TDX) module without having to reboot the running server. For Linux 7.2 it looks like that feature will be all-set for allowing the easier roll-out of security updates and the like for this confidential computing capability on modern Intel Xeon servers...
- ReactOS Now Running On ARM64 In Experimental Form
ReactOS as the "open-source Windows" project working to implement binary compatibility for computer programs and drivers for Microsoft Windows now has experimental support for running on 64-bit ARM...
- The exemptions in age-verification laws for open source operating systems are bad, actually
Weve talked about the various age verification laws in the United States, and theres been a development recently that a lot of people seem to think is a good thing: both the age verification laws in California and Colorado have received exemptions for open source operating systems. I fail to see how this is a good thing, and luckily, I dont even have to explain why because Liam Squires-Hand from GamingOnLinux already did it for me. When all these laws get stamped and approved, what happens when you run an operating system (lets say Fedora or Ubuntu) and some web service or application is forced to do age checking and verification (or they face massive fines). Unless Linux distributions / desktop environments do end up implementing something that correctly adheres to these laws, what do you think will happen? Those services / apps could very likely just entirely block Linux in certain regions or even all regions if its Linux to prevent any issues for them. ↫ Liam Squires-Hand at GamingOnLinux Thats the core of it, right there. These nebulous exemptions are not solutions; theyre barely even band-aids. Windows, macOS, iOS, and Android will implement whatever fascist anti-privacy age-verification nonsense governments can come up with, and virtually all services and applications that need to implement support for it will just follow along as well. Do you really think theyre going to craft exceptions for the few percent of their users running Linux? The past three decades of computing history has made it very clear that no, they will not. But the exceptions have already achieved their goal: the Linux world is happy and lulled right back into a sense of complacency. What could possibly go wrong?
- Gemini, gophers, and fingers: alternative internets beyond HTTPS
But what I want to write about today are three protocols that have their own ecosystems, their own communities, and their own aesthetics. finger://, gopher://, and gemini://. Two predate the World Wide Web entirely, but one was created in 2019, the same year the first black hole photograph circled the planet. None of them require a GUI. None of them require JavaScript. All three of them run in a terminal. ↫ Brennan Day I ran an OSNews Gemini capsule from my office for quite a while, but managing it from my own workstation computer became a little annoying and cumbersome. I should take a weekend off at some point and devise an easy way to convert our RSS feed into separate files for Gopher and Gemini and serve them from my Proxmox mini PC, if only to do my part in contributing to the success of independent protocols.
- Microsoft tries to obscure AI! features behind flowery design language
Now that my one-month sentence of using Windows 11 has begun (you can follow along!), Im also a bit more perceptive of news and developments regardingMicrosofts latest and greatest operating system version. Despite claims to the contrary, we already know the company isnt really removing AI! features from Windows, merely renaming them instead, but it turns out theyre planning something more all encompassing: the Copilot Design System. Long-time Microsoft veteran Jon Friedman published a blog post introducing this new concept. As Copilot steadily evolves into a thought partner—an intelligent presence woven into your workflow—its backbone will become the Copilot Design System, an AI-forward design system we’re crafting to feel intentional and humane. From orchestration patterns to iconography, the experience we’re building will ultimately have components that work together to amplify thinking, guide decisions, and unlock creativity—seamlessly, wherever you work. Anchored in customer feedback around creating better experiences, a fundamental question guides our system’s evolution: how would a thoughtful partner look and behave? ↫ Jon Friedman at Microsofts design blog Ive read the whole post and I still have no idea what most of it is supposed to mean in practice. It feels like the written equivalent of someone trying to put lipstick on a pig, and pretty much anyone is going to see right through the fancy words and phrases and realise what were really dealing with here: a company trying to figure out just how far they can shove AI! down your throat before you gag reflex kicks in. You can hide behind flowery language all you want, but if youre selling shit, its going to stink regardless. The only concrete user interface idea thats come out of this Copilot Design System was a floating Copilot button that permanently floated on top of your workspace area in Word, Excel, and so on, obscuring the actual things you were working on. Users hated it so much that Microsoft had to quickly release what is essentially a hotfix to give people the ability to remove that floating button, putting it in a toolbar instead. Like I said: people see right through these thinly-veiled attempts at baiting them into using your pachinko machine. Anyway, yes, Im working from Windows 11 now, just as you people paid me to do. Heres the proof: Only 30 days left to go. I can do this.
- Sailfish OS reviews are always the same
João Carrasqueira at XDA Developers has taken a look at the current state of Sailfish OS, and concludes: As an idea, I love Sailfish OS. Not only does it bring a wholly unique interface to mobile devices at a time when things seem more unified than ever, but it also has the potential to bring the full power of Linux to a smartphone you actually want to use. But the lack of apps makes it hard for it to become anyones daily driver, and the power of Linux is somewhat hampered because it relies on dedicated repositories that, again, dont get much support. The community as a whole would benefit if the UI for Sailfish OS could also be open-sourced and made available as a desktop environment other distros could adopt. I can see a world where many more Linux distros might be ported to mobile devices using this UI, and leading to more apps being ported to the platform as well. Its unlikely, but taking that step could make a big difference. ↫ João Carrasqueira It seems like Sailfish OS, much like any other mobile operating system that isnt Android or iOS, is still stuck in application hell, where theyve always been. Windows Phone, BlackBerry 10, postmarketOS, Sailfish OS they all suffer from the fact that the services and associated applications people actually need to use in their day-to-day life just simply arent there, and never will be unless something utterly drastic happens. Youre pretty much forced to fall back on possible Android application compatibility layers, at which point youre basically just running Android in an worse way. As an extremely early customer of the original Jolla Phone, and owner of the very rare Jolla Tablet, I considered if I should add the new Jolla Phone as an incentive for the current fundraiser, but I decided against it because I already know what the review is going to be like. Interesting user interface, very limited set of often buggy native applications, constant reliance on often buggy Android compatibility layer, €750 is a lot of money for a barely mid-range phone. Oh, and the UI layer is closed source. I dont need an expensive phone I wont use after the review period to write any of that. Theres very little new to write about or discover when it comes to mobile operating systems other than Android and iOS, and thats not through the fault of the people developing these platforms. All the smart developers working on postmarketOS, Salfish, Ubuntu Touch, and others are doing a great job and the very best they can, but in the end these platforms are limited by the fact that the services we all depend on just do not work on any of them. I dont have the solution for the problem other than very heavy-handed regulation to demand open APIs, which I support but will never happen so the status quo will remain as it is. Its a sad state of affairs when even Google-free Android is almost a non-starter at this point.
- The Nokia N8 has a brand new, modern, actively maintained, and regularly updated Symbian ROM
I have a Nokia N8, and its one of my favourite retro (?) devices I own. It was one of Nokias last efforts to make Symbian happen in the post-iPhone era, and while the hardware was quite nice, Symbian just wasnt made for multitouch devices. It didnt move the needle much for an already dying Nokia, and things just got worse from there. A bright spot with the Nokia N9, some decent Windows Phone devices, and then the end. We all know the story. The Nokia N8, though, seems to have been given a new lease on life recently. This smartphone, released in 2010, can be turned into a usable, capable device again, thanks to a brand new, modern custom Symbian ROM called Reborn. It takes the latest stock Symbian version for the N8, removes any and all applications/links/etc. that dont work anymore, and then proceeds to make a ton of things work again. Modern TLS for HTTPS support, updated certificates, modern email support, a brand new application store, a new update application with a steady stream of OTA updates to fix issues, a bunch of security fixes, a whole slew of quality-of-life touches, and so, so much more. This is absolutely amazing work. Clearly a labour of love, theres already been tons of updates over the past year since the ROMs initial release, and I obviously cant not install this on my own N8, assuming it still works. A video by Janus Cycle covering the project is also available, for the more visually-oriented among us.
- Microsoft continues beating the agentic! Windows drum
Were a mere €124 away from the first incentive during our fundraiser: making me use stock Windows 11 for a month. Since the writing appears to be on the wall, and the donation pulling us across the line can come in any moment, I figured Id better take a peek at how things stand with Windows. I came across a story about Yusuf Mehdi, an executive vice president and consumer chief marketing officer, who apparently became the face of Microsofts AI! push. After 35 years, hes leaving the company, but not after pledging to continue pushing AI! deeper into Windows 11. Despite this intense backlash, Mehdi is doubling down on the AI vision during his final months at the company. In his LinkedIn announcement, he stated: “I will work through the next fiscal year to help reimagine Windows for the agentic era, grow Microsoft 365 services, and bring our One Copilot vision to life.” Microsoft has recently scaled back on some intrusive Copilot features in Notepad, Snipping Tool, and Photos, but the executive leadership team still views AI agents as the inevitable future of the Windows desktop experience. ↫ Abhijith M B at Windows Latest The numbers for Microsoft and every other software company who dove head-first into AI! are clear: its one of the biggest bottomless pits of all time, and theyre all throwing money down the pit hoping itll eventually fill up and overflow. Meanwhile, 100 metres down in the pit, a dude in a leather jacket is holding out a bucket and collecting some of the money before it disappears into the void below. For Microsoft, AI! represents a $235 billion loss (so far!), so the company had to do something anything to stop the bleeding. They tried shoving Copilot buttons in every nook and cranny of its products, but users rightfully and understandably revolted. Theyre toning it down in Windows, and recently, theyve also had to tone it down in Office as users were horrified to discover a floating Copilot button in Word, Excel, and so on. People really do not want this shit, which puts these companies in a hugely precarious position: just how badly can they abuse the geese? Well see just how much Microsoft will actually roll back its force-feeding practices, and Im not excited to be partaking in the Windows 11 experiment soon.
- On C extensions, portability, and alternative compilers
Anyone whos written C knows that full ISO C standard-adhering code is an impractical rarity. Most real world C code out there relies on non-standard behaviors and language extensions to varying extents, and a lot of this isnt for extra features, but just to work around bugs and gaps in different compilers and libraries. A lot of codebases will try somewhat to support various environments, mostly through the use of preprocessor checks and guards, but these attempts are finicky at best and straight up broken at worst. I have ran into many of these situations while working on my C compiler, so heres a small list of some of them. ↫ lemon/Sofia Sometimes I wonder how computers even get anything done at all.
- Flatpak will depend on systemd
If you visit the Flatpak website today, it lists, as the very first advantage of the project: Build for every distro: create one app and distribute it to the entire Linux desktop market.! If you then move on to the list of supported distributions, youll see the usual suspects, but also distributions like Void Linux, Guix, and Alpine. These last three all have one thing in common: they use an init system other than systemd, because Flatpak doesnt care what init system you use. It seems that for the next major version of Flatpak, however, thats going to change: systemd will probably become a dependency for Flatpak. Speaking at the Linux App Summit, Arian Vovk and Sebastian Wick held a great talk about the future of Flatpak. The current version of Flatpak will continue to see a ton of improvements, but at the same time, the limits of what can be done with its decades-old design have become harder and harder to work around. As such, theyre also planning for and working on what they call Flatpak Next, or perhaps Flatpak 2.0, which is effectively a rewrite of Flatpak based on what theyve learned over the years, making use of modern technologies and ideas that have gained ground since the initial design of Flatpak 1.x. Its important to note that everything discussed during the talk is planning, and not a single line of code has been written yet. This means that all of these plans are subject to change, and as the work progresses over the coming years, the end result may turn out very different from whats been detailed in the talk. In addition, and I cant stress this enough: if anything in this discussion gives you even the smallest of inklings to go and harass, attack, insult, or otherwise bother anyone involved in Flatpak, systemd, or related technologies, please be so kind as to book an appointment for a yoga class or whatever. It seems like you need it. Right at the onset of the talk, Vovk and Wick explain that they want to move the permission management from Flatpak into the service layer, through a new service called systemd-appd. Systemd-appd gives applications an identifier and stores their permissions, and then this data can be queried by the rest of the system. In turn, this enables a slew of other features, not least of which is subsandboxing. At the moment, the plan is to introduce this feature in the current version of Flatpak, thereby introducing a dependency on systemd into Flatpak. From what I understand from Vovk, they were intending to be super considerate! of distributions and people not using systemd, which I take to mean wed eventually end up in a situation very similar to systemd-logind, which was extracted from systemd into a separate daemon, elogind, so that distributions using other init systems could still make use of desktop environments depending on systemd-logind. I imagine Flatpak developers wanted to make as many affordances as realistically possible for something similar to happen to systemd-appd, thus ensuring Flatpak would remain available on distributions not using systemd. Obviously, people who are using distributions like Void or Alpine were concerned about the future of Flatpak on their systems. If Flatpak gains a hard dependency on systemd, Flatpak would no longer work on distributions without systemd, so the talk raised questions sadly, it seems the questions were directed at someone not technically involved with Flatpak development, and his replies were not particularly helpful and often just downright insulting and inflammatory. Even though hes not involved in Flatpak development, enough people assumed that he was, and a toxic brew stirred. Users with genuine, friendly questions about the future of Flatpak on their systems were met with derision and insults, and it spiraled out of control from there, drawing in the rabid anti-systemd Red Hat conspiracy lunatics (and worse). Things got progressively worse for everyone involved, particularly for Flatpaks developers. And so we ended up at the situation where everyones mad and Flatpaks developers are not feeling inclined to spend time on that shit anymore! when it comes to accommodating and making affordances for distributions and people not using systemd. The end result will most likely be that any future Flatpak dependency on systemd will be stricter, and making any independent elogind-like daemon will be much harder than it was going to be. Nobody wins, everybody loses, all because some people thought it necessary and productive to be insulting and inflammatory. As things currently stands, its very likely that over the coming years, Flatpak will gain a dependency on systemd, possibly without any affordances for an independent daemon to replicate systemd-appd functionality on distributions that do not use systemd. In other words, Flatpak would no longer be able to boast that it enables Build for every distro: create one app and distribute it to the entire Linux desktop market.!, as it would no longer be distribution-agnostic. And thats a shame, because Flatpak fills a real need for users, regardless of whatever init system they use. Which is apparently something some people base their entire identity on, because theyre weirdos.
- Long-term support! does not mean what you think it does
You may think you know what long-term support! means when picking a Linux distribution and version, but judging by the multitude of utterly wrong takes and deeply confused users I come across online, Im starting to get the feeling that in fact, no, you dont know what it means. KDEs Nate Graham is seeing the same confusion, and has published a blog post going over what LTS really means in the Linux world. People seem to think that an LTS release means its going to be more stable, have fewer bugs, and receive support for a certain set period of time. The reality is that only that last one really applies, sort-of. LTS generally means youre going to be using a Linux distribution version where youll get security fixes and possibly maintenance updates for a set number of years, but you wont be getting updates with new features or other updates that arent security fixes. The purpose of an LTS release is to more or less freeze itself and its packages in time, so that users know exactly what theyre getting. However, part of being frozen in time means any bugs, crashes, and hardware support are also frozen in time. The end result is that LTS releases will often have wildly outdated package versions, and those outdated package versions will most likely contain a ton of bugs and issues that have long been fixed in subsequent releases subsequent releases youre not getting, because youre on an LTS release. LTS releases are fairly stable and reliable as long as you use the most popular software from their included software repositories. So in the circumstances when this stops being the case, I think sometimes people can feel betrayed. They think, “I thought this was supposed to be stable! Why didn’t anyone fix this bug yet? Where’s my long-term support?” But Debian, Ubuntu, and Kubuntu never promised any level of stability, reliability, or absence of bugs. They promised that the version-locked software in their repos would receive security fixes for a certain number of years. Ubuntu and Kubuntu also offered a certain amount of non-guaranteed best-effort hardware compatibility improvements and non-security bug fixes. ↫ Nate Graham This causes major problems for upstream developers. People who use an LTS release will be using versions of packages that are out of date and full of bugs that have already been fixed in later versions, but they dont know that, so they end up reporting these old bugs that have been fixed ages ago as if theyre new. If youre an LTS user and you experience a persistent bug and subsequent crash in Kwin, youre most likely going to complain at the Kwin developers, even if the Kwin developers have already fixed this bug 18 months ago. Every week theres at least a few developers in my Fedi timeline rolling their eyes at Debian users reporting bugs fixed ages ago and getting mad when told they should complain at Debian developers for not backporting the fix. So many LTS users seem to think that LTS equals increased stability, fewer bugs, and fewer crashes, but thats just not what LTS is for or what it claims to offer. Sticking to specific (major) versions of packages means not youre not only missing out on new features and changes which might be desirable for you but also on bug fixes. With LTS, as they say, the bugs are also stable.
- Gnutella: a protocol outliving the world that created it
Now thats a name I havent heard in a long time. Gnutella is a file sharing protocol that many have forgotten and it has the story of a decentralized technology adopted by millions of casual users who did not care to learn what a peer-to-peer system was. Users showed up because the protocol solved real problems at scale and the solution just so happened to be decentralized. No one ever pretended to use Gnutella in hopes their GnutellaCoinTM would go up in value later. They just downloaded MP3s. The network exploded in popularity, then plateaued for almost a decade, then settled into a permanent long tail state of continued but diminished use. Welcome to my overly enthusiastic love letter to Gnutella. ↫ Rick Carlino I genuinely didnt know or I had forgotten, more likely that Gnutella formed the backbone of LimeWire, another name I havent heard in a long time. Im quite sure I used LimeWire over 25 years ago, but details are fuzzy and I might be confusing it with other filesharing networks of a similar vintage. I was an avid CD buyer and MiniDisc user (I used MD well into the smartphone age), so I didnt have much need for downloading MP3s. Gnutella is also apparently still active, and there are still clients you can download and use. Of course, its a mere shadow of its former self, but this, too, was news to me. Im kind of inclined to see if its still hosting MP3s.
- EU OS: A Bold Step Toward Digital Sovereignty for Europe
Image 
A new initiative, called "EU OS," has been launched to develop a Linux-based operating system tailored specifically for the public sector organizations of the European Union (EU). This community-driven project aims to address the EU's unique needs and challenges, focusing on fostering digital sovereignty, reducing dependency on external vendors, and building a secure, self-sufficient digital ecosystem.
What Is EU OS?
EU OS is not an entirely novel operating system. Instead, it builds upon a Linux foundation derived from Fedora, with the KDE Plasma desktop environment. It draws inspiration from previous efforts such as France's GendBuntu and Munich's LiMux, which aimed to provide Linux-based systems for public sector use. The goal remains the same: to create a standardized Linux distribution that can be adapted to different regional, national, and sector-specific needs within the EU.
Rather than reinventing the wheel, EU OS focuses on standardization, offering a solid Linux foundation that can be customized according to the unique requirements of various organizations. This approach makes EU OS a practical choice for the public sector, ensuring broad compatibility and ease of implementation across diverse environments.
The Vision Behind EU OS
The guiding principle of EU OS is the concept of "public money – public code," ensuring that taxpayer money is used transparently and effectively. By adopting an open-source model, EU OS eliminates licensing fees, which not only lowers costs but also reduces the dependency on a select group of software vendors. This provides the EU’s public sector organizations with greater flexibility and control over their IT infrastructure, free from the constraints of vendor lock-in.
Additionally, EU OS offers flexibility in terms of software migration and hardware upgrades. Organizations can adapt to new technologies and manage their IT evolution at a manageable cost, both in terms of finances and time.
However, there are some concerns about the choice of Fedora as the base for EU OS. While Fedora is a solid and reliable distribution, it is backed by the United States-based Red Hat. Some argue that using European-backed projects such as openSUSE or KDE's upcoming distribution might have aligned better with the EU's goal of strengthening digital sovereignty.
Conclusion
EU OS marks a significant step towards Europe's digital independence by providing a robust, standardized Linux distribution for the public sector. By reducing reliance on proprietary software and vendors, it paves the way for a more flexible, cost-effective, and secure digital ecosystem. While the choice of Fedora as the base for the project has raised some questions, the overall vision of EU OS offers a promising future for Europe's public sector in the digital age.
Source: It's FOSS
European Union
- Linus Torvalds Acknowledges Missed Release of Linux 6.14 Due to Oversight
Linus Torvalds Acknowledges Missed Release of Linux 6.14 Due to Oversight
Linux kernel lead developer Linus Torvalds has admitted to forgetting to release version 6.14, attributing the oversight to his own lapse in memory. Torvalds is known for releasing new Linux kernel candidates and final versions on Sunday afternoons, typically accompanied by a post detailing the release. If he is unavailable due to travel or other commitments, he usually informs the community ahead of time, so users don’t worry if there’s a delay.
In his post on March 16, Torvalds gave no indication that the release might be delayed, instead stating, “I expect to release the final 6.14 next weekend unless something very surprising happens.” However, Sunday, March 23rd passed without any announcement.
On March 24th, Torvalds wrote in a follow-up message, “I’d love to have some good excuse for why I didn’t do the 6.14 release yesterday on my regular Sunday afternoon schedule,” adding, “But no. It’s just pure incompetence.” He further explained that while he had been clearing up unrelated tasks, he simply forgot to finalize the release. “D'oh,” he joked.
Despite this minor delay, Torvalds’ track record of successfully managing the Linux kernel’s development process over the years remains strong. A single day’s delay is not critical, especially since most Linux users don't urgently need the very latest version.
The new 6.14 release introduces several important features, including enhanced support for writing drivers in Rust—an ongoing topic of discussion among developers—support for Qualcomm’s Snapdragon 8 Elite mobile chip, a fix for the GhostWrite vulnerability in certain RISC-V processors from Alibaba’s T-Head Semiconductor, and a completed NTSYNC driver update that improves the WINE emulator’s ability to run Windows applications, particularly games, on Linux.
Although the 6.14 release went smoothly aside from the delay, Torvalds expressed that version 6.15 may present more challenges due to the volume of pending pull requests. “Judging by my pending pile of pull requests, 6.15 will be much busier,” he noted.
You can download the latest kernel here.
Linus Torvalds kernel
- AerynOS 2025.03 Alpha Released with GNOME 48, Mesa 25, and Linux Kernel 6.13.8
Image 
AerynOS 2025.03 has officially been released, introducing a variety of exciting features for Linux users. The release includes the highly anticipated GNOME 48 desktop environment, which comes with significant improvements like HDR support, dynamic triple buffering, and a Wayland color management protocol. Other updates include a battery charge limiting feature and a Wellbeing option aimed at improving user experience.
This release, while still in alpha, incorporates Linux kernel 6.13.8 and the updated Mesa 25.0.2 graphics stack, alongside tools like LLVM 19.1.7 and Vulkan SDK 1.4.309.0. Additionally, the Moss package manager now integrates os-info to generate more detailed OS metadata via a JSON file.
Future plans for AerynOS include automated package updates, easier rollback management, improved disk handling with Rust, and fractional scaling enabled by default. The installer has also been revamped to support full disk wipes and dynamic partitioning.
Although still considered an alpha release, AerynOS 2025.03 can be downloaded and tested right now from its official website.
Source: 9to5Linux
AerynOS
- Xojo 2025r1: Big Updates for Developers with Linux ARM Support, Web Drag and Drop, and Direct App Store Publishing
Image 
Xojo has just rolled out its latest release, Xojo 2025 Release 1, and it’s packed with features that developers have been eagerly waiting for. This major update introduces support for running Xojo on Linux ARM, including Raspberry Pi, brings drag-and-drop functionality to the Web framework, and simplifies app deployment with the ability to directly submit apps to the macOS and iOS App Stores.
Here’s a quick overview of what’s new in Xojo 2025r1:
1. Linux ARM IDE Support
Xojo 2025r1 now allows developers to run the Xojo IDE on Linux ARM devices, including popular platforms like Raspberry Pi. This opens up a whole new world of possibilities for developers who want to create apps for ARM-based devices without the usual complexity. Whether you’re building for a Raspberry Pi or other ARM devices, this update makes it easier than ever to get started.
2. Web Drag and Drop
One of the standout features in this release is the addition of drag-and-drop support for web applications. Now, developers can easily drag and drop visual controls in their web projects, making it simpler to create interactive, user-friendly web applications. Plus, the WebListBox has been enhanced with support for editable cells, checkboxes, and row reordering via dragging. No JavaScript required!
3. Direct App Store Publishing
Xojo has also streamlined the process of publishing apps. With this update, developers can now directly submit macOS and iOS apps to App Store Connect right from the Xojo IDE. This eliminates the need for multiple steps and makes it much easier to get apps into the App Store, saving valuable time during the development process.
4. New Desktop and Mobile Features
This release isn’t just about web and Linux updates. Xojo 2025r1 brings some great improvements for desktop and mobile apps as well. On the desktop side, all projects now include a default window menu for macOS apps. On the mobile side, Xojo has introduced new features for Android and iOS, including support for ColorGroup and Dark Mode on Android, and a new MobileColorPicker for iOS to simplify color selection.
5. Performance and IDE Enhancements
Xojo’s IDE has also been improved in several key areas. There’s now an option to hide toolbar captions, and the toolbar has been made smaller on Windows. The IDE on Windows and Linux now features modern Bootstrap icons, and the Documentation window toolbar is more compact. In the code editor, developers can now quickly navigate to variable declarations with a simple Cmd/Ctrl + Double-click. Plus, performance for complex container layouts in the Layout Editor has been enhanced.
What Does This Mean for Developers?
Xojo 2025r1 brings significant improvements across all the platforms that Xojo supports, from desktop and mobile to web and Linux. The added Linux ARM support opens up new opportunities for Raspberry Pi and ARM-based device development, while the drag-and-drop functionality for web projects will make it easier to create modern, interactive web apps. The ability to publish directly to the App Store is a game-changer for macOS and iOS developers, reducing the friction of app distribution.
How to Get Started
Xojo is free for learning and development, as well as for building apps for Linux and Raspberry Pi. If you’re ready to dive into cross-platform development, paid licenses start at $99 for a single-platform desktop license, and $399 for cross-platform desktop, mobile, or web development. For professional developers who need additional resources and support, Xojo Pro and Pro Plus licenses start at $799. You can also find special pricing for educators and students.
Download Xojo 2025r1 today at xojo.com.
Final Thoughts
With each new release, Xojo continues to make cross-platform development more accessible and efficient. The 2025r1 release is no exception, delivering key updates that simplify the development process and open up new possibilities for developers working on a variety of platforms. Whether you’re a Raspberry Pi enthusiast or a mobile app developer, Xojo 2025r1 has something for you.
Xojo ARM
- New 'Mirrored' Network Mode Introduced in Windows Subsystem for Linux
Microsoft's Windows Subsystem for Linux (WSL) continues to evolve with the release of WSL 2 version 0.0.2. This update introduces a set of opt-in preview features designed to enhance performance and compatibility.
Key additions include "Automatic memory reclaim" which dynamically optimizes WSL's memory footprint, and "Sparse VHD" to shrink the size of the virtual hard disk file. These improvements aim to streamline resource usage.
Additionally, a new "mirrored networking mode" brings expanded networking capabilities like IPv6 and multicast support. Microsoft claims this will improve VPN and LAN connectivity from both the Windows host and Linux guest.
Complementing this is a new "DNS Tunneling" feature that changes how DNS queries are resolved to avoid compatibility issues with certain network setups. According to Microsoft, this should reduce problems connecting to the internet or local network resources within WSL.
Advanced firewall configuration options are also now available through Hyper-V integration. The new "autoProxy" feature ensures WSL seamlessly utilizes the Windows system proxy configuration.
Microsoft states these features are currently rolling out to Windows Insiders running Windows 11 22H2 Build 22621.2359 or later. They remain opt-in previews to allow testing before final integration into WSL.
By expanding WSL 2 with compelling new capabilities in areas like resource efficiency, networking, and security, Microsoft aims to make Linux on Windows more performant and compatible. This evolutionary approach based on user feedback highlights Microsoft's commitment to WSL as a key part of the Windows ecosystem.
Windows
- Linux Threat Report: Earth Lusca Deploys Novel SprySOCKS Backdoor in Attacks on Government Entities
The threat actor Earth Lusca, linked to Chinese state-sponsored hacking groups, has been observed utilizing a new Linux backdoor dubbed SprySOCKS to target government organizations globally.
As initially reported in January 2022 by Trend Micro, Earth Lusca has been active since at least 2021 conducting cyber espionage campaigns against public and private sector targets in Asia, Australia, Europe, and North America. Their tactics include spear-phishing and watering hole attacks to gain initial access. Some of Earth Lusca's activities overlap with another Chinese threat cluster known as RedHotel.
In new research, Trend Micro reveals Earth Lusca remains highly active, even expanding operations in the first half of 2023. Primary victims are government departments focused on foreign affairs, technology, and telecommunications. Attacks concentrate in Southeast Asia, Central Asia, and the Balkans regions.
After breaching internet-facing systems by exploiting flaws in Fortinet, GitLab, Microsoft Exchange, Telerik UI, and Zimbra software, Earth Lusca uses web shells and Cobalt Strike to move laterally. Their goal is exfiltrating documents and credentials, while also installing additional backdoors like ShadowPad and Winnti for long-term spying.
The Command and Control server delivering Cobalt Strike was also found hosting SprySOCKS - an advanced backdoor not previously publicly reported. With roots in the Windows malware Trochilus, SprySOCKS contains reconnaissance, remote shell, proxy, and file operation capabilities. It communicates over TCP mimicking patterns used by a Windows trojan called RedLeaves, itself built on Trochilus.
At least two SprySOCKS versions have been identified, indicating ongoing development. This novel Linux backdoor deployed by Earth Lusca highlights the increasing sophistication of Chinese state-sponsored threats. Robust patching, access controls, monitoring for unusual activities, and other proactive defenses remain essential to counter this advanced malware.
The Trend Micro researchers emphasize that organizations must minimize attack surfaces, regularly update systems, and ensure robust security hygiene to interrupt the tactics, techniques, and procedures of relentless threat groups like Earth Lusca.
Security
- Linux Kernel Faces Reduction in Long-Term Support Due to Maintenance Challenges
The Linux kernel is undergoing major changes that will shape its future development and adoption, according to Jonathan Corbet, Linux kernel developer and executive editor of Linux Weekly News. Speaking at the Open Source Summit Europe, Corbet provided an update on the latest Linux kernel developments and a glimpse of what's to come.
A major change on the horizon is a reduction in long-term support (LTS) for kernel versions from six years to just two years. Corbet explained that maintaining old kernel branches indefinitely is unsustainable and most users have migrated to newer versions, so there's little point in continuing six years of support. While some may grumble about shortened support lifecycles, the reality is that constantly backporting fixes to ancient kernels strains maintainers.
This maintainer burnout poses a serious threat, as Corbet highlighted. Maintaining Linux is largely a volunteer effort, with only about 200 of the 2,000+ developers paid for their contributions. The endless demands on maintainers' time from fuzz testing, fixing minor bugs, and reviewing contributions takes a toll. Prominent maintainers have warned they need help to avoid collapse. Companies relying on Linux must realize giving back financially is in their interest to sustain this vital ecosystem.
The Linux kernel is also wading into waters new with the introduction of Rust code. While Rust solves many problems, it also introduces new complexities around language integration, evolving standards, and maintainer expertise. Corbet believes Rust will pass the point of no return when core features depend on it, which may occur soon with additions like Apple M1 GPU drivers. Despite skepticism in some corners, Rust's benefits likely outweigh any transition costs.
On the distro front, Red Hat's decision to restrict RHEL cloning sparked community backlash. While business considerations were at play, Corbet noted technical factors too. Using older kernels with backported fixes, as RHEL does, risks creating divergent, vendor-specific branches. The Android model of tracking mainline kernel dev more closely has shown security benefits. Ultimately, Linux works best when aligned with the broader community.
In closing, Corbet recalled the saying "Linux is free like a puppy is free." Using open source seems easy at first, but sustaining it long-term requires significant care and feeding. As Linux is incorporated into more critical systems, that maintenance becomes ever more crucial. The kernel changes ahead are aimed at keeping Linux healthy and vibrant for the next generation of users, businesses, and developers.
kernel
- Linux Celebrates 32 Years with the Release of 6.6-rc2 Version
Today marks the 32nd anniversary of Linus Torvalds introducing the inaugural Linux 0.01 kernel version, and celebrating this milestone, Torvalds has launched the Linux 6.6-rc2. Among the noteworthy updates are the inclusion of a feature catering to the ASUS ROG Flow X16 tablet's mode handling and the renaming of the new GenPD subsystem to pmdomain.
The Linux 6.6 edition is progressing well, brimming with exciting new features that promise to enhance user experience. Early benchmarks are indicating promising results, especially on high-core-count servers, pointing to a potentially robust and efficient update in the Linux series.
Here is what Linus Torvalds had to say in today's announcement:
Another week, another -rc.I think the most notable thing about 6.6-rc2 is simply that it'sexactly 32 years to the day since the 0.01 release. And that's a roundnumber if you are a computer person.Because other than the random date, I don't see anything that reallystands out here. We've got random fixes all over, and none of it looksparticularly strange. The genpd -> pmdomain rename shows up in thediffstat, but there's no actual code changes involved (make sure touse "git diff -M" to see them as zero-line renames).And other than that, things look very normal. Sure, the architecturefixes happen to be mostly parisc this week, which isn't exactly theusual pattern, but it's also not exactly a huge amount of changes.Most of the (small) changes here are in drivers, with some tracingfixes and just random things. The shortlog below is short enough toscroll through and get a taste of what's been going on. Linus Torvalds
- Introducing Bavarder: A User-Friendly Linux Desktop App for Quick ChatGPT Interaction
Want to interact with ChatGPT from your Linux desktop without using a web browser?
Bavarder, a new app, allows you to do just that.
Developed with Python and GTK4/libadwaita, Bavarder offers a simple concept: pose a question to ChatGPT, receive a response, and promptly copy the answer (or your inquiry) to the clipboard for pasting elsewhere.
With an incredibly user-friendly interface, you won't require AI expertise (or a novice blogger) to comprehend it. Type your question in the top box, click the blue send button, and wait for a generated response to appear at the bottom. You can edit or modify your message and repeat the process as needed.
During our evaluation, Bavarder employed BAI Chat, a GPT-3.5/ChatGPT API-based chatbot that's free and doesn't require signups or API keys. Future app versions will incorporate support for alternative backends, such as ChatGPT 4 and Hugging Chat, and allow users to input an API key to utilize ChatGPT3.
At present, there's no option to regenerate a response (though you can resend the same question for a potentially different answer). Due to the lack of a "conversation" view, tracking a dialogue or following up on answers can be challenging — but Bavarder excels for rapid-fire questions.
As with any AI, standard disclaimers apply. Responses might seem plausible but could contain inaccurate or false information. Additionally, it's relatively easy to lead these models into irrational loops, like convincing them that 2 + 2 equals 106 — so stay alert!
Overall, Bavarder is an attractive app with a well-defined purpose. If you enjoy ChatGPT and similar technologies, it's worth exploring.
ChatGPT AI
- LibreOffice 7.5.3 Released: Third Maintenance Update Brings 119 Bug Fixes to Popular Open-Source Office Suite
Today, The Document Foundation unveiled the release and widespread availability of LibreOffice 7.5.3, which serves as the third maintenance update to the current LibreOffice 7.5 open-source and complimentary office suite series.
Approximately five weeks after the launch of LibreOffice 7.5.2, LibreOffice 7.5.3 arrives with a new set of bug fixes for those who have successfully updated their GNU/Linux system to the LibreOffice 7.5 series.
LibreOffice 7.5.3 addresses a total of 119 bugs identified by users or uncovered by LibreOffice developers. For a more comprehensive understanding of these bug fixes, consult the RC1 and RC2 changelogs.
You can download LibreOffice 7.5.3 directly from the LibreOffice websiteor from SourceForge as binary installers for DEB or RPM-based GNU/Linux distributions. A source tarball is also accessible for individuals who prefer to compile the software from sources or for system integrators.
All users operating the LibreOffice 7.5 office suite series should promptly update their installations to the new point release, which will soon appear in the stable software repositories of your GNU/Linux distributions.
In early February 2023, LibreOffice 7.5 debuted as a substantial upgrade to the widely-used open-source office suite, introducing numerous features and improvements. These enhancements encompass major upgrades to dark mode support, new application and MIME-type icons, a refined Single Toolbar UI, enhanced PDF Export, and more.
Seven maintenance updates will support LibreOffice 7.5 until November 30th, 2023. The next point release, LibreOffice 7.5.4, is scheduled for early June and will include additional bug fixes.
The Document Foundation once again emphasizes that the LibreOffice office suite's "Community" edition is maintained by volunteers and members of the Open Source community. For enterprise implementations, they suggest using the LibreOffice Enterprise family of applications from ecosystem partners.
LibreOffice
|
