Distributions
GNU Guix as an alternative to the Yocto Project
This talk demonstrates how to use GNU Guix to build a root filesystem for an
embedded device (Pine A64 LTS).
I will also try to answer the question:
could GNU Guix be a viable alternative to the Yocto project and what would be
the benefits of using GNU Guix?
Working as an embedded software engineer, I've been using Yocto and Buildroot
projects to create root filesystems for embedded devices. While Buildroot is
only suitable for small embedded systems, Yocto does scale well, but is a
really complex tool.
Plus, both tools are difficult to handle for developers without a strong
understanding of Linux system integration, and on the other hand, do not
provide APIs and introspection tools for integrators.
In this talk, I want to explore the possibility of using GNU Guix as an
alternative to the Yocto project to generate embedded root filesystems.
With 7 years of existence, more than 10000 packages and 4 supported
architectures, GNU Guix can be used as a transactional package manager and an
advanced distribution of the GNU operating system running on the Linux kernel.
What would be missing to cover all Yocto features? How could the embedded
developer benefit from GNU Guix features such as its high level Scheme API,
package substitution mechanism, strong reliability and reproducibility?
To provide some real world application, I'll compare the process of adding
support for a new board (Pine A64 LTS) on Yocto and GNU Guix. Then I'll
compare how to configure, build and flash a small root filesystem for
that same board, on the two tools.
Additional information
| Type | devroom |
|---|
More sessions
| 2/2/20 |
In the beginning there was compiling and static linking. My first programs when I was 10 years old worked like that. Then, we discovered dynamic linking. This was great because we could now patch one library and all of the programs would pick up the change on restart. But we created another problem - dependencies. Throughout the history of computing we have solved one problem and created another. Containers are no different. This talk will walk through why we invented Linux distros and why we ...
|
| 2/2/20 |
What are the new features in the upcoming R1/beta2? How did the packaging system work out? How to make your software easier to port to it, and how to contribute?
|
| 2/2/20 |
A talk about the Homebrew package manager and how we've been working with our users to introduce new features to subsets of users, encouraging users to donate to the project and communicating both these to as many users as possible without being annoying.
|
| 2/2/20 |
There is a multitude of software or code ecosystems: Linux distribution packages, language-specific (e.g. Python or node.js) modules, third-party desktop themes, git repositories, and recently also Flatpak and Snap. Users thus obtain software and code mainly from the network. This talk explores what can go wrong in such code delivery mechanisms, and what actually went wrong when a new threat has materialized: networks in certain countries started to be unreliable "thanks" to the governments ...
|
| 2/2/20 |
The concept of home directories on Linux/UNIX has little changed in the last 39 years. It's time to have a closer look, and bring them up to today's standards, regarding encryption, storage, authentication, user records, and more. In this talk we'll talk about "systemd-homed", a new component for systemd, that reworks how we do home directories on Linux, adds strong encryption that makes sense, supports automatic enumeration and hot-plugged home directories and more.
|
| 2/2/20 |
Systemd provides a bunch of features which can be used to contain and secure services, making security and isolation primitives provided by the kernel accessible to system programs. This allows service authors to write much simpler code, and often to avoid any integration with the operating system for security purposes. Unfortunately, those features are still not widely used, possibly because developers want to maintain compatibility with a wide range of systems. I'll talk about the features ...
|
| 2/2/20 |
systemD has a very distribution-friendly way of providing it's configuration, with distributions providing defaults in /usr and users being able to override things either selectively or entirely with their own files in /etc. This is especially nice for distributions wishing to be in some way stateless, support a read-only root filesystem, or provide some kind of factory-reset. libeconf is a newly written C library to ease the adoption of similar configuration layering in other programs across ...
|
