users May 2025

users@lists.genode.org

6 participants
4 discussions

Announcement: Genode OS Framework version 25.05 released
by Christian Helmuth 28 May '25

28 May '25

Hello everyone, I'm happy to announce the May 2025 release of Genode. https://genode.org/documentation/release-notes/25.05 According to this year's motto "rigidity, clarity, and performance", the Genode 25.05 release focuses on API safety, consolidation work, and developer tooling.The most prominent change in this release is the much revised framework API that no longer relies on the C++ exception mechanism but precisely encodes all possible error conditions as sum types, an inspiration taken from the Rust-language community. This approach rules out several classes of programming errors by design and, thus, enforces the conscious handling of error conditions, eliminates the accidental leakage of pointers, as well as promotes clarity of object ownership and lifetimes. The fair amount of consolidation work in the this release includes, for example, the unified integration of the Linux and lwIP TCP/IP stacks paving the ground for subsequent network-protocol improvements and optimizations. Feature-wise, we add a new VFS plugin for generating pseudo random numbers, support for touch gestures, and display rotation and flipping on Intel hardware. Also following our biennial update routine, we use a recent tool chain based on GCC 14.2, binutils 2.44, and GDB 16.3 starting with this release for the next 24 months. Further, the Goa SDK now mitigates security risks while importing, building, and testing projects of unvetted origin by sandboxing all tools and tightly restricting the reach of its own configuration files. The current release contains the following changes and new features: - Tool chain upgraded to GCC 14.2 and binutils 2.44 - Hardened API, leveraging sum types for error handling - Security-enhanced Goa SDK - New support for touch gestures - New VFS plugin for generating pseudo random numbers - Revisited integration of the Linux and lwIP TCP/IP stacks - Display rotation and flipping on Intel hardware - Dynamic mode switching and reporting of the VESA display driver Read the complete release documentation for the version 25.05 here https://genode.org/documentation/release-notes/25.05 Best regards -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ https://de.linkedin.com/company/genodelabs Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

Determine total resources consumed within a nested init
by Sid Hussmann 27 May '25

27 May '25

Dear Genodians, I want to determine the total resources consumed within a deeply nested subsystem. The only apparent way to do this is to iterate through all the init state reports of the children and their ancestors down to the leaf and accumulate the respective `ram_used` and `caps_used` attributes of the `child` nodes. Is this the way? Intuitively, the parent at the tree's root should be aware of this information. However, after digging through the documentation and the code, I found that this `total_ram_used`/`total_caps_used` information is not available out of the box within an init component/sandbox library. I assume the reason for this is that there is no (easy) way to communicate this information all the way back to the parent. On the other hand, implementing a monitor component that goes through all these recursive init state reports, not knowing how deep the tree is, and assuming that all the sub-inits correctly report their state seems quite error-prone. Is my assumption correct that the only way to determine a subsystem's resource consumption is to aggregate the init state reports down to the leaf? Cheers, Sid -- Sid Hussmann CTO & Founder Gapfruit AG Baarerstrasse 135 6300 Zug - Switzerland sid.hussmann(a)gapfruit.com https://gapfruit.com

1 0

laptop boots fine into 25.04
by Guido 16 May '25

16 May '25

Hi Genodians, At the Hack-n-Hike, I ran into a boot loop after upgrading Sculpt 24.10 to 25.04. However, when I test with a fresh 25.04 image from the website (sha256: 54e8bd...), the very same laptop boots OK. However, I do run into an issue when I upgrade from 24.10 to 25.04 but I'll investigate first before reporting or requesting help. Thanks for the wonderful HnH. Cheers, Guido.

2 2

Extending the VFS with hard-links
by Rumen Mitov 02 May '25

02 May '25

Hello, I need some help with extending the VFS for my project. I need hardlink support, so I added the following to repos/os/include/vfs/directory_service.h's Directory_service struct: virtual int hardlink(char const *path, char const *hardlink_path) { (void) path; (void)hardlink_path; Genode::error("not implemented!"); return 0; } I have the Lwext4 plugin (https://codeberg.org/jws/genode-wundertuete/src/branch/import-lwext4_from_w…) setup for my project so I then extended repos/wundertuete/src/lib/vfs/lwext4/vfs.cc's Lwext4_vfs_file_system struct: int hardlink(char const *path, char const *hardlink_path) override { return ext4_flink(path, hardlink_path); } The problem is that hardlink uses the default implementation in my main code: squidutils->_vfs_env.root_dir().hardlink(p2.string(), p1.string()); // Prints 'not implemented' From what I have read online the issue is that squidutils->_vfs_env.root_dir() is of type Directory_service, whereas I need it to be Lwext4_vfs_file_system. However, Lwext4_vfs_file_system is declared in the vfs.cc file above as opposed to being declared in a header. Is there a way to use Lwext4_vfs_file_system without copying the entire source of Lwext4 into my project's source code? Or am I perhaps going in the wrong direction with all of this? Best, Rumen

4 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users May 2025