Kamis, 20 Agustus 2026

FOSS Weekly #26.34: StillOS Review, Kernel 7.2 Released, PINE Trouble, Beautifying GNOME, Terminal Multiplexers and More

FOSS Weekly

LightDM 1.33.0 is out after a four-year gap, now under community maintainership rather than Canonical's. Two new maintainers, one behind Ubuntu Cinnamon Remix and the other a long-time Fedora and openSUSE contributor, have stepped up.

Nitrux has given a name to what it's been building since dropping Plasma for Hyprland last year. The Workspace Environment brings four in-house QML components together, a workspace bar, a dock, a settings app, and a lock screen.

A busy point release for Linux has just landed. AMD Radeon picks up HDMI 2.1 support, Apple M3 MacBooks can boot Linux for the first time, and Btrfs large folio support is on by default.

Canonical's VP of Engineering has said that Ubuntu's growth rate inside WSL is outpacing its growth rate on native desktops, which got picked up everywhere (including here 🤐) as "Ubuntu is growing faster on Windows than Linux." He's since clarified that the comparison was about growth rate only.

The Xen Project recently launched a Safety Committee to build the shared documentation, test evidence, and certification artifacts that companies deploying Xen in automotive, avionics, and industrial automation keep having to produce independently.

Privacy company Murena now offers Fairphone Gen 6 with its /e/OS, a private alternative to Android.

PINE64 is halting the production of its Linux-based tablets. Reason? The soaring RAM prices have made it impossible to keep the pricing reasonable for such hobbyist devices. And the RAM prices are increasing due to AI boom. Big Tech has already put their hands on the supply with bulk orders for their data centers and now the consumers are struggling as prices for disks and RAMs have gone up multiple folds.

🧠 What We’re Thinking About

Don't remember if I shared it in the newsletter or not. A few days ago, it was found that some AI companies are buying rare books to train their LLMs. And in the process, they were also cutting (read destroying) the books because it is easier to scan the books page by page that way.

404 Media (paywalled content) has tracked one such shipment to the Amazon AI training facility. So at least we have one culprit identified.

🧮 Linux Tips, Tutorials, and Learnings

Most people look no further than Tmux and Screen. But what if I told you there were terminal multiplexers that shared sessions over SSH, restored your workspace exactly as you left it, or brought tiling WM concepts straight into your terminal?

A detailed guide on apt that covers updating the package database, installing and removing packages, searching, showing package info, listing upgradable software, and cleaning up leftover dependencies.

Want your GNOME desktop to look like those Catppuccin or Nord riced screenshots without spending an afternoon in config files? Rewaita is a Flatpak app that applies color palettes to GTK and Libadwaita apps through CSS overrides.

Desktop Linux is mostly neglected by the industry but loved by the community. For the past 14 years, It's FOSS has been helping people use Linux on their personal computers. And we are now facing the existential threat from AI models stealing our content.

If you like what we do and would love to support our work, please become It's FOSS Plus member. It costs $49 a year (less than the cost of a McDonald's burger a month), and you get an ad-free reading experience with the satisfaction of helping the desktop Linux community. And there are also free Linux ebooks.

Join It's FOSS Plus

👷 AI, Homelab and Hardware Corner

Proton has come up with a tool that tells you how many secrets you have spilled over to an AI chatbot.

✨ Apps and Projects Highlights

stillOS is a new distro that's built on an AlmaLinux base with atomicity as its main selling point.

📽️ Videos for You

I show you a wonderful dock for GNOME users. See it in action in this week's video.

💡 Quick Handy Tip

On GNOME inside the Nautilus file manager (aka Files), press CTRL+F to start a search in the current directory and CTRL+SHIFT+F to search everywhere. You can also select the result and use CTRL+ALT+O to open that location in file manager.

0:00
/0:14

🎋 Fun in the FOSSverse

If you went through the apt guide earlier, why not test your knowledge with a quick quiz?

The beginning is always simple. 😆

using linux makes you lose your mind meme

🗓️ Tech Trivia: On August 22, 1955, representatives from seventeen companies that had bought IBM's new 704 mainframe met at RAND Corp in Santa Monica and formed SHARE, the first computer user group, so members could trade code and documentation instead of duplicating each other's work.

🧑‍🤝‍🧑 From the Community: A long-time FOSSer has returned, kicking off a thread on how Windows enabled bitlocker without asking him, resulting in considerable wear on the attached storage disks.



from It's FOSS https://ift.tt/dOxJm9n
via IFTTT

PINE64 is Halting its Linux Hardware Line, and The AI Bubble is to Blame

two pine64 devices, the pinetab2 and the pinenote are shown above with the pine64 logo and a trashcan illustration below

The open hardware manufacturer recently posted an update on its Mastodon account, and it's not great news if you were hoping to grab new Linux-powered PINE64 hardware.

The disruptions in DRAM and eMMC supply are to blame, as PINE64 says its Linux hardware production pipeline is empty for now, with nothing new planned while component costs stay high.

Whether that changes depends on component pricing after mid-2027, and they aren't promising anything before then. They expect stocks for the PineNote and PineTab2 to run out in three months.

Once that happens, there's no more new launches or restocks to cover the outgoing stock.

Not everything is affected though. PINE64's microcontroller lineup, the PineTime, PineVoice, and Pinecil, will keep shipping as usual since they don't rely on the same memory chips.

Concluding their announcement, they gave everyone a status update on the upcoming PineTime Pro:

As for the PineTime Pro, currently the demo firmware has basic drivers for the display, touch, motion, GPS, buttons, heat rate sensor (chip id only), battery charger, motor, microphone and the speaker. Though some issues do need to be ironed out first before a pilot batch begins production.
That's it for this post, all in all it's a bit bleak for the Linux devices, but in the meantime PineStore still have a great lineup of MCU powered devices which will continue to expand with more exciting devices.

The unnamed culprit

PINE64 never actually says the word "AI" in their post, choosing to keep the announcement focused on the DRAM/eMMC shortage. But you have to look further to see where that shortage is actually originating from.

Memory prices have been climbing for months, and DDR5 has taken the hardest hit of all. Companies running AI data centers have been locking up global memory supply well into next year, leaving everyone else fighting over what's left.

Executives across the memory industry aren't optimistic either. SK Hynix's CEO recently said that the worst is still ahead, with supply expected to lag behind demand for years to come.

Not the only ones

PINE64 isn't the only Linux-focused hardware provider caught in this price surge.

The Orange Pi Neo, a Linux-first handheld built with Manjaro, has been sitting on ice since earlier this year for the same reason. The project has been in development for two years and still has no launch date, all because DDR5 and SSD prices refuse to come back down.

I am sure these aren't the only projects affected; smaller ones still in the crowdfunding or conceptualization phase must be facing the same problem.

What worries me is that the AI bubble will eventually burst, but small Linux-focused projects are the ones getting choked out right now. If these component prices stay this absurd, we are going to lose the few independent hardware choices we actually have left.


Suggested Read 📖: Omarchy Bets Its Future on AI Agents While the Linux World Stays Cautious



from It's FOSS https://ift.tt/xjCSeRa
via IFTTT

Warp Launches Factories to Let Engineering Teams Build Their Own Cloud Software Factories

warp logo with some pixel-styled text below it, an illustration of a factory with clouds passing above it on the rgit
▶️ Warp has introduced Factories, infrastructure for running your own cloud software factory with fleets of agents.
▶️ Agents handle triage, specs, implementation, and review; humans step in only when needed.
▶️ Works with any model or harness, and all runs are tracked via built-in metrics.
▶️ Closed beta only; apply for early access.

How software gets built at an organization has evolved a lot over the years. Long before AI agents entered the scene, engineering teams were already turning development into a series of repeatable actions that brought together shared components and defined processes while minimizing reinvention.

That approach has made teams faster and more consistent. In the age of AI, it needs to transform yet again. Warp is convinced it has figured out what's next.

The company has introduced Warp Factories as an open infrastructure offering meant to help engineering teams build and run their own cloud software factories. Here, fleets of coding agents do the work instead of an agent limited to a developer's laptop.

The short explanation is that it's Warp's attempt to turn "run an agent in the cloud" into an actual assembly line, with clear steps, real numbers to track, and humans stepping in only when it matters.

📋
If you use an ad blocker like uBlock, the text with Warp links won't show up for you.

An assembly line for development

Warp Factories acts as an infrastructure layer for running fleets of coding agents across the entire software development lifecycle. In Warp's own framing, that makes it a cloud software factory, an automated loop where agents handle the work from intake through to a shipped result.

Agents handle triage, write specs, implement changes, review the work, verify it, and monitor the result, while humans only step in at decision points that actually need a person to verify what's been done.

Think of it like a car assembly line. One station welds, another paints, another does final inspection, and the vehicle doesn't move forward until the station before it signs off. Warp's version applies that same logic to code.

One agent triages an incoming ticket, another drafts a spec if the change is complex enough to need one, another implements the fix, and another reviews it before a human approves the merge.

Warp is leaning hard on the idea of AI sovereignty to explain why this needs to exist as infrastructure. Teams can bring their own hosting, and every agent conversation, evaluation, and memory record can be kept on infrastructure the company controls instead of Warp's.

Data can also be kept out of any training pipeline entirely through zero-data-retention options.

The founder and CEO of Warp, Zach Lloyd, further points out that:

Our vision is providing you all with the core components to get to this point as quickly as possible. In an age where time to ship is arguably your most important competitive advantage, you should be standing up and operating a factory today, not six months from now.

More of its capabilities

the warp factories "factory app" is shown here being used to manage a warp factory, this image was sourced from warp

Factories also ships with a dashboard the company calls the "factory app," basically a control room where you can watch live and past agent runs, check what's pending, and review every automation in one place.

You're not locked into Warp's own models or its own agent either. Factories works with any model, open-weight ones too, and any harness, so Claude Code or Codex can sit in the implementation seat instead of Warp's native agent.

All of that activity gets measured automatically, with cost, throughput, and code quality metrics feeding into evaluation and benchmark tools that track how a factory's performance shifts over time.

Get started

Warp Factories isn't available for everyone right now. If you or your organization wants to try it out, then you will need to request access through Warp Factories' early access portal.

Qualifying organizations can get up to $10,000 in factory usage credits.



from It's FOSS https://ift.tt/U8YclXf
via IFTTT

Rabu, 19 Agustus 2026

Book Review: The Ultimate AI Guide for Linux Engineers

Even Linus Torvalds is fine with AI being used in Linux kernel development these days, and it's everywhere else in the Linux and tech world too. The time has come to stop ignoring AI and start using it as a tool and to use it well, especially if you are a professional sysadmin or DevOps.

That's why seasoned Linux professionals, Ezequiel Lanza and Eduardo Spotti wrote the book The Ultimate AI Guide for Linux Engineers that I am reviewing here. The book is published by Packt and you can find it on Packt, O'Reilly and Amazon.

Note that the book is written for people who already know and use Linux professionally. That means sysadmins, devops, SREs, system engineers, network engineers. The book collectively calls them "Linux engineers" and I like that term.

Basically, it is for the people who are more used to doing things the old way and unsure where and how to fit AI into their regular workflow.

A book for seasoned Linux professionals

The book opens with "Linux engineers have always been expected to do more with less," and that's the core idea of the book: using AI effectively to improve efficienncy.

The examples are good, and if you've managed servers and infrastructure before, you'll relate to them. That's what makes the book interesting: it's written from a sysadmin/DevOps perspective.

To reduce the risk of letting AI agents loose on your systems, the authors suggest best practices like role-based access, limiting operations to read-only wherever possible, and logging all AI actions for auditing.

There are also examples and sample code you can adapt for your own workflow with some modification, like an anomaly detector you could plug into your Linux observability stack.

Although the book has 12 chapters and runs over 300 pages, I find that the book is divided into four core sectors:

1. Foundational knowledge

The book starts by explaining AI, machine learning (ML), and large language models (LLMs) specifically in Linux contexts, covering the practical differences between training, fine-tuning, and inference.

This sets up the technical foundation for building an AI-ready Linux environment, with an emphasis on Python as the primary language and virtual environments and containerization for safe, reproducible workflows.

2. Intelligent automation and LinuxOps agents

A major focus of the book is the shift from static automation to intelligent automation. AI-assisted automation shows how to combine AI with traditional tools like Ansible, Bash, and systemd to generate safe, validated commands from natural language intent.

The book also teaches how to build autonomous agents that can perceive system problems, reason through multi-step plans, and execute tasks while following least-privilege principles and safeguards.

3. Intelligent observability and RAG

The authors push for moving from passive monitoring to a "dialogue model" of observability, through log dialogue pipelines. So, instead of manually grepping through logs, you build pipelines that compress and correlate multi-source logs into actionable knowledge.

The book also covers building RAG systems that index system logs, internal runbooks, documentation, and past incident reports to give you context-aware answers instead of hallucinated ones. This is where AI actually shines. When it has context, its analysis is far more accurate.

4. Production deployment and security

To move these concepts into real-world use, the book covers scaling and securing AI workloads on Kubernetes: managing GPU resources, implementing autoscaling based on inference-specific metrics, and optimizing performance through techniques like quantization.

It also lays out a full security stack, including threat modeling for AI, PII (personally identifiable information) redaction, prompt injection defenses, and using Open Policy Agent (OPA) to enforce strict guardrails on agent actions. This part matters more than people think; it's usually the part companies skip, right up until they end up trending on social media over a security incident.

The book ends by looking at the future of AI-driven Linux workflows, and the need to balance autonomy with human oversight.

💡
Each chapter comes with practice exercises and additional external resources. There is an accompanied GitHub repo that has the codes and pipelines discussed in the book.

Verdict

Overall, The Ultimate AI Guide for Linux Engineers is a practical, Linux-first handbook designed to help system administrators, SREs, and DevOps professionals fold AI into their daily workflows. Instead of focusing on theory, it lays out a roadmap for evolving from traditional shell scripts to intelligent, autonomous systems.

This book isn't for you if you're completely new to Linux or just a casual desktop user. You may still learn something, but unless you're managing servers, containers, and infrastructure, you probably won't find it as engaging or useful.

I think every Linux professional should start looking for ways to use AI in their workflow. The book gives you ideas, it gives you scenarios and guides you through them. If you ever wanted to start using AI but was unsure because of all the noise around it and didn't know where to begin, the book is definitely worth a read.

The best engineers will not be replaced by AI but will be the ones who know how to use it effectively.

Still unsure? To determine whether the book is for you, I advise checking it on the O'Reilly website. It has chapters of the books and you can expand those chapters to see the sections of those chapters.

Chapter 5 sample of AI Linux book

This will give a clearer picture if you are still indecisive if you should get the book.



from It's FOSS https://ift.tt/yLGT4e1
via IFTTT

Murena Just Made The Fairphone (Gen. 6) Better!

a multi-color banner that shows four murena fairphone (gen. 6+) devices with the logos for murena and /e/os placed nearby

We are used to seeing Murena roll out new devices every now and then. Their whole sales pitch revolves around a de-Googled, privacy-focused Android experience. Not everyone is sold on that approach, sure, but the company has managed to stick around for quite a few years now, which says something.

The latest addition to their lineup is the Fairphone (Gen. 6+) with /e/OS. It sits right next to the standard Gen. 6 model, which is still on sale. The new variant packs better hardware and carries a higher price tag to match.

The new device

the three colorways for the murena fairphone (gen. 6+) are shown here; horizon black, cobalt blue, and forest green
The three colorways: Horizon Black, Cobalt Blue, and Forest Green.

The most significant change is the Snapdragon 7s Gen 4 processor, paired with 12GB of RAM. The base model makes do with the older Gen 3 chip and 8GB of RAM. Though storage stays at 256GB across both, expandable via microSD up to 2TB.

Everything else on the hardware carries over from the base model, including the 6.31-inch 120Hz LTPO OLED display, the 50MP main camera with a 13MP secondary and 32MP selfie shooter, the 4,415mAh removable battery with 30W charging, IP55 water resistance, and Gorilla Glass 7i to protect the display.

There's also a new Cobalt Blue colorway that ties into Fairphone's fair-mined cobalt supply chain efforts. It joins the existing Forest Green and Horizon Black options. The modular design is unchanged, so you can still swap out 12 key components with a regular screwdriver.

The software itself has not changed for this launch. It is still the same privacy-first build Murena has been refining for a while now.

That means no Google tracking baked into the OS, an Advanced Privacy widget that lets you control what data individual apps can see, and a running Wall of Shame that calls out installed apps leaking the most personal information.

The founder and CEO of Murena, Gaël Duval, spoke about the device, saying that:

With devices like Fairphone (Gen. 6+) with /e/OS, users can have a truly ethical device both in terms of hardware and software.

When I developed Mandriva Linux back in the 90s, it was my mission to make the operating system usable for the everyday, non-techie user. This is my goal with Murena – to give the average user access to smartphones that do not hold their privacy to ransom.

Get yours

Pricing depends on which region you order a Murena Fairphone (Gen. 6+) from. For EU, it costs €699, more than the €649 Murena charges for the standard Gen. 6. In the US, the Fairphone (Gen. 6+) is priced at $699, which is more than the standard Gen. 6's $649 price tag.

People who order during the limited-time launch window of 18 August-1 September 2026 get a few extras. In the EU, that's two free accessories of your choice, where you get to pick from a case, screen protector, finger loop, card holder, or lanyard. US buyers get a case and screen protector bundle.

Everyone gets a year of 1TB Murena Workspace and a year of Murena MDM.

Availability differs by region too. The device is shipping now in Europe, with the US listed as a backorder.

Closing thoughts

The ethical smartphone market is still tiny, and it mostly survives on partnerships like this one. Fairphone builds the hardware, Murena handles the software, and together they keep proving that a privacy-first phone does not have to mean a phone stuck in the dark ages.

Whether that is enough to pull people away from Google remains the same open question it was the last time Murena updated their lineup.



from It's FOSS https://ift.tt/TBD07tL
via IFTTT

Selasa, 18 Agustus 2026

This Solo Dev Already Built a Popular Distro. Now He's Trying It Again

stillos screenshot showcasing the app launcher and wallpaper, with a "distro of the month" badge applied on the right

Atomic distros work differently from the Fedora or Ubuntu install you're probably used to. Instead of layering individual packages on top of each other, the entire base system ships as one image, and updates land as a whole swap rather than a slow stream of package changes.

As a result, you get a system that's hard to break, where updates apply cleanly or not at all, rolling back a bad patch is easy, and there's no dependency hell to wade through since every install starts from the same known-good state.

The trade-off is flexibility. You lose the ability to tinker with individual system packages the way you can on a traditional distro, and anything outside the base image needs a workaround instead of a quick apt install or dnf install.

stillOS wants you to consider the upside of that trade-off. It calls itself a "maintenance-free" Linux desktop, built on an AlmaLinux 10 base with bootc handling the atomic updates.

Behind it is Cameron Knauff, who goes by the name "PizzaLovingNerd" in the Linux community, and this isn't his first distro.

His earlier project, risiOS, a Fedora-based distro aimed at smoothing out the rough edges for new users, picked up a solid following before it was absorbed into Nobara Linux, freeing him up to start stillHQ and, down the line, stillOS.

It has potential

I tested stillOS 10.2 on a virtual machine in GNOME Boxes, running on my Fedora Workstation setup. Installation felt familiar right away. stillOS uses the same Anaconda installer AlmaLinux ships with.

If you've installed Fedora, RHEL, or any of their downstream distros before, you already know the steps involved here.

Onboarding is quick and doesn't waste your time. A short welcome screen kicks off Quick Setup, which walks you through installing apps, picking a browser, and grabbing essentials before dropping you onto the desktop.

Once you boot into stillOS, you will see that while the desktop is GNOME underneath, the distro ditches the usual top-panel layout for a taskbar-first interface, closer to Windows 11 than anything GNOME ships by default.

The taskbar carries the usual options like the app drawer, pill-shaped workspace switcher, an update notifier, pinned apps, the calendar, the clock, and quick settings.

Unlike vanilla GNOME, stillOS' version lets you drop icons straight onto the desktop.

Right-clicking gives you quick access to creating new folders and documents, undoing an action, selecting everything, arranging icons, opening the terminal, and some important settings.

The file manager keeps most of that same right-click menu, folders, documents, select all, opening a terminal, alongside the usual "Properties" entry found on Nautilus (Files).

The document creation option is the one that I find very useful, as that’s something I miss on the vanilla GNOME experience. The catch is that it only hands you three formats through ONLYOFFICE: docx, pptx, and xlsx. Considering what The Document Foundation has been pushing for lately, a locked-down proprietary-only shortcut feels like an odd choice.

Installing LibreOffice and removing ONLYOFFICE didn't fix it either. The shortcut still generates files in those same formats; it just opens them in LibreOffice instead.

The file manager looks different too, even though it's the same GNOME Files under the hood. When you launch it, the app opens a "Computer" page that lays out your folders, disks, and removable media in one clean view.

the file manager for stillos that is showing the "computer" page with many folders, storage, and removable media items

The default app selection is generous. You get ONLYOFFICE, Gear Lever, Warp, Mousam, and a good spread of the usual GNOME-focused apps alongside them.

stillOS also ships its own lineup of "still" branded tools. stillTerminal is the default terminal app, built around a customized ZSH setup with container and SSH support.

stillCenter is the curated app store, pulling from Flatpak and other sources with its own stillRating system grading how well an app runs with stillOS.

stillControl handles GNOME layout customization, letting you switch between 12+ preset layouts and manage extensions without digging through GNOME Tweaks. Then there's stillOS Forums, which isn't a native app at all. It's the community forum wrapped as a SWAI web app, so it behaves like part of the desktop instead of a browser tab.

Running other software worked without any surprises. I selected Zen Browser during onboarding specifically to see how it handled a non-default browser, and it ran cleanly, without any visual bugs, lags, or crashes to speak of.

The pill-shaped workspace switcher held up well through all of this too, letting me flip between workspaces and open apps without any lag or fumbling. Though this was a given seeing that it is a well-tested component from GNOME.

And before you assume that this is some obscure Linux distro that will fade into irrelevance very soon, know that development is still quite active. The recent stillOS 10.2 release introduced most of what's covered above.

Cameron says that:

stillOS has now reached the point where it fits that initial vision. There is obviously more work to do, and there always will be, but the foundation is here. Now I want to focus on building the community around it.
The goal is to keep stillOS innovative while also building a Linux system that literally anyone can use. Those ideas do not have to conflict. Linux can try new things without becoming confusing, and it can be approachable without becoming boring.

Download it now

You can grab the latest stillOS ISO from SourceForge, which lists all the images released by the project so far.

Once you're up and running, know that updates aren't handled through AlmaLinux's usual dnf-based flow.

Instead, you can rely on the distro to handle it for you, as it checks for updates automatically 15 minutes after boot, then every 24 hours after that for as long as your machine stays on.

terminal window that shows the successful running of this command: sudo bootrc upgrade

If you can't wait, then you can run the following command in the terminal to force an update check:

sudo bootc upgrade


from It's FOSS https://ift.tt/sPKmwDe
via IFTTT

The Xen Project is Serious About Safety, So It Formed a Committee

xen project logo, three people sat on a desk, and a flying kick panda who looks rad af

Xen is a hypervisor that runs on various kinds of hardware, where a crash can have massive consequences. It is deployed in fields like automotive, industrial automation, robotics, and avionics. These are all safety-critical fields where certification matters.

So far, it has been on a good trajectory with increasing adoption and enhancements that keep it relevant for enterprise use. What it hasn't had is a structured, collaborative way to help the companies building on it actually get certified for that kind of work.

It has launched the Xen Safety Committee, a group tasked with building the safety documentation and test evidence that member companies can lean on instead of starting from scratch.

The committee's job covers software safety requirements, architecture specifications, MISRA-related engineering, DFMEA analysis, testing frameworks, tooling, code coverage, and process documentation.

Founding contributors AMD, EPAM, and Renesas are credited with doing most of the legwork for the above, forming the initiative's early foundation.

The point is to stop every company from solving the same problem on their own. Sharing this foundation should cut costs, avoid duplicated effort, and get products through certification faster for anyone building on Xen.

Nothing changes about how Xen itself gets built. Source code, licensing, and the existing open contribution and review process stay exactly as they are. The Safety Committee runs as a parallel governance layer, not a replacement for how maintainers already work.

Though joining the committee isn't all that open. Organizations will need to sign up for the right kind of membership. More on that below. 👇

A call for new members

the xen project webpage is shown here, specifically the members page with lots of informational text

Membership at Xen Project works like most Linux Foundation projects. It funds shared infrastructure, test environments, events, and coordination, while day-to-day technical decisions stay with maintainers through open contribution.

Paying to join doesn't buy influence over the codebase. 🤓

AMD, ARM, AWS, Boeing, EPAM, Ford, Honda, Renesas, Vates, and XenServer are all listed as current members. These represent chipmakers, cloud providers, automotive, aerospace, and a few other sectors.

A new membership tier, "Premier Plus" sits above the existing tiers, granting voting representatives on both the Xen Advisory Board and the Safety Committee, a say in setting priorities and roadmap, and access to the committee-managed safety artifacts.

This way, instead of producing every requirement and test in house, members can hand the committee's existing artifacts to their own safety assessors for audits and assessments.

Speaking on the topic, Kate Stewart, Vice President, Dependable Embedded Systems, The Linux Foundation, stated that:

Systems with safety considerations need a trusted hypervisor to provide the foundation for other open source components, such as Zephyr and Linux, to support mixed criticality embedded applications.
The Zephyr and Xen projects have been exchanging best practices over the last few years as a pathway to achieve safety certification of open source components. We welcome the Xen Safety Initiative to accelerate the journey of Xen achieving formal certification.

Suggested Read 📖: Proxmox Virtual Environment Officially Runs on ARM64



from It's FOSS https://ift.tt/qrJlN3Y
via IFTTT