users

users@lists.genode.org

1 participants
2304 discussions

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

02 Apr '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

1 0

Hard-Links in Genode
by Rumen Mitov 07 Mar '25

07 Mar '25

Hello, Does Genode's VFS have the capability to create hard links? So far as I have been able to tell it is only possible to create symlinks. Best, Rumen

2 1

Announcement: Genode OS Framework version 25.02 released
by Norman Feske 28 Feb '25

28 Feb '25

I'm happy to announce the release of version 25.02 of the Genode OS Framework. https://genode.org/news/genode-os-framework-release-25.02 The first release of the year already pays tribute to our road-map theme "rigidity, clarity, performance" by introducing SIMD-based graphics optimizations, revising and simplifying central parts of our custom base-hw kernel, while also lifting long-standing scalability limitations when using 3rd-party kernels like seL4 and Fiasco.OC. In addition to this careful gardening work, the release is not short of features either. The headlines of the release documentation are the extension of multi-monitor support to the window manager and virtual machines, the updated port of the Chromium engine along with the Falkon web browser, and Qemu as native Genode component. The highlights of the new version at a glance: - Multi-monitor window management - Multi-monitor virtual machines - SIMD optimizations - Port of Qemu via Goa - Web Engine updated to Chromium version 112 - User-space IOMMU support for IRQ remapping - Sculpt OS on Intel Meteor Lake platforms - Goa SDK improved for building shared libraries - New board support for F&S i.MX 8MP armStone All the details behind these (and more) topics of the new version are given in release documentation: https://genode.org/documentation/release-notes/25.02 Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

GDB Hangs After Continue
by Rumen Mitov 26 Feb '25

26 Feb '25

Hello, I was trying to debug my program with GDB, however after connecting to the binary, loading all the appropriate files, and running "continue", GDB just hangs and it does not produce any output. Here are the exact steps I took: 1. Inserted wait_for_continue() in my code 2. make -C build/x86_64/ run/squid KERNEL=linux BOARD=linux & 3. ps -ef | grep squid 4. gdb -p <port number from previous command> 5. symbol-file build/x86_64/debug/squid 6. add-symbol-file build/x86_64/debug/ld-linux.lib.so 7. continue (GDB hangs, I have to CTRL-c it) Did I perhaps miss a step? Best, Rumen

2 1

Goa: Cannot get sub-node from XML
by Rumen Mitov 19 Feb '25

19 Feb '25

Hello, I am trying to migrate my project to the Goa build system. However, when I try running Genode throws 'Genode::Xml_node::Nonexistent_sub_node'. Below I have provided a simplified file containing the isolated code from where the error is thrown along with the full runtime file. Line 13 is the where the error is thrown from. I cannot figure out why this is not working, since it works just fine with the traditional build system (i.e. with make). Any help will be greatly appreciated! Best, Rumen

2 3

Kernel: Cpu 2 error: re-entered lock. Kernel exception
by Pirmin Duss 12 Feb '25

12 Feb '25

Hello Genodians Since we rolled out the update to 24.11 we see the above message about once or twicw a day in the logs of our testing pipeline. It happens on different hardware (Up-Xtreme and imx8mp_iot_gate in the last two days) and in different run scripts. The run scripts range from a fairly simple TPM run script to complicated run scripts that test the resilience of the operating system to stopping/starting of whole subsystems and reboots. Currently we don't have a case where this happens reproducible. It could be related to https://github.com/genodelabs/genode/issues/5382 but also something completely different. How could we narrow down the issue and gather logs to identify the cause of it? Kind regards, Pirmin

2 3

system shell NOT in foreground
by Larry Sevilla 28 Jan '25

28 Jan '25

Hi Genode people, I tried to follow the sculpt documentation up to "Tools -> system shell" The "system shell" displayed on screen,BUT I canNOT type any commands. when I click on the said shell/window, it canNOT be in the "foreground" or be an "active window". Sources: https://genode.org/documentation/articles/sculpt-24-10 File QEMU/KVM: https://genode.org/files/sculpt/sculpt-24-10.img File VirutalBox: https://genode.org/files/sculpt/sculpt-24-10.ova Host A Desktop: i7-8700 32Gb OS: Gentoo GNU/Linux Emulation: QEMU 9.2.0 Trial 1: Note: -cpu remove due to error, -m 1024 too small, use ram fs qemu-system-x86_64 -display sdl -machine q35 \ -m 6144 -drive format=raw,file=sculpt-24-10.img \ -netdev user,id=net0 -device e1000,netdev=net0 Trial 2: Note: -cpu remove due to error, formated ahci-1.fs sculpt.qcow2 20Gb qemu-system-x86_64 -display sdl -machine q35 \ -m 6144 -drive format=raw,file=sculpt-24-10.img \ -drive format=raw,file=sculpt.qcow2 \ -netdev user,id=net0 -device e1000,netdev=net0 Host B Desktop: i7-9700 32Gb OS Windows 11 Emulation: VirtualBox 7.0.22 Trial: imported as Appliance sculpt-24-10.ova VB guest hangs during adding Tools->system shell Note: did NOT test on a desktop PC (no spare)

2 1

Trying to modify Bit_array throws 'Invalid_index_access'
by Rumen Mitov 24 Jan '25

24 Jan '25

Hello, I am facing a problem when using the Bit_array class. I have a class called L1Dir which contains the property freemask which is a Bit_array with L1_SIZE bits. I want to initialize every bit to value 1 in freemask. However, when I try to call freemask.set(0, L1Dir) outside of the L1Dir default constructor the following error is thrown: 'Genode::Bit_array_base::Invalid_index_access'. I have tried changing the call to freemask.set(1,2) but I still get the same exception. I have also tried with freemask.get(...) and freemask.clear(...) with no success. I have initialized freemask with enough space: Genode::Bit_array<L1_SIZE> freemask; This leads me to believe that the problem has something to do with the underlying memory of Bit_array_base. If you know what I am doing wrong, please let me know! Best, Rumen P.S. If you need more context, you can find the current state of my code here: https://github.com/rumenmitov/genode-squid/tree/a726c5da3099a7f5de1d4d3d98a…

2 2

Roadmap 2025
by Norman Feske 22 Jan '25

22 Jan '25

Hello everyone, the turn of years is approaching, which prompts me to pick up our fine tradition of jointly brainstorming the topics of the year to come. Below, I'm not speaking for the project but share my personal perspective. Let me start with a brief reflection on 2024, followed by my ambitions for 2025. Review of 2024 Following our past year's discussion, we settled on "Sculpt OS usability" as the primary focus for 2024. The items on the roadmap envisioned a broad variety of topics, ranging from challenging low-level mechanisms to end-user conveniences. From my perspective, the two biggest breakthroughs had been suspend/resume on x86 (added in May) and multi-monitor support (added in October). Both topics were not merely approached as singular features but as architectural enhancements. Suspend/resume challenged our perspective on driver life-cycles, externalizing state, device re-acquisition, up to the dynamic driver management by Sculpt OS. Our desire for multi-monitor support culminated in a largely redesigned GUI stack, as a system-holistic endeavor. Both lines of work made the architecture of Sculpt OS much stronger. Regarding my original plans for user conveniences (file browser etc.), I must declare defeat. Instead of working on these user-visible features, I turned a significant part of my attention to consolidation work: Gradually removing the use of C++ exceptions, cultivating C++20, improving code safety, and accelerating our workflows be refining our build system and tools. Outside my own working topics, I vastly enjoyed watching our team embracing DDE-Linux to full extent. Reflecting upon our small team's ability to track the current Linux kernel for our large driver base with such an agility makes me more than happy. A similar source of happiness is the way of how the Goa SDK and the new Applications book evolved. It reveals plainly and clearly how all the parts of the machinery fit super nicely together. Any regrets? Two things come into mind. First, my over-promising to deliver user conveniences. Topics like the on-target docs view or a file manager are user-visible and fun to build. But I was not able to justify prioritizing those over the work on framework internals as my core expertise. I somewhat regret having promised too much. Second, the PinePhone hasn't become a regular part of my life. That's not the fault of the PinePhone. But I came to terms that I may simply not be a phone person, never having owned a smart phone after all. Once I called the exciting ride of bringing Genode to the PinePhone a success, my personal motivation to push things further forward plummeted somewhat. My plans for 2025 I want to focus my Genode work on rigidity, clarity, and performance. 1. Following my consolidation work of 2024, I long for getting the C++ runtime removed from the base framework. Another tempting idea for simplification is the merging of core's CPU service into the PD service. This work will make Genode more simple and thereby more trustworthy. 2. I'm very curious to explore the idea of replacing XML, outlined at https://genodians.org/nfeske/2024-12-20-moving-on-from-xml If this goes as intended, Genode and Sculpt OS will gain in terms of interactive ergonomics, clarity, and joy to develop for. 3. Given how easy the porting of software has become, thanks to Goa, I'd strive for moving more of my work outside a Linux VM. For this, libraries like the libc and VFS require further optimization. This goes hand in hand with the need for better tools for analysing performance bottlenecks of complex dynamic workloads. As an iconic goal, it would be fantastic to have a simple version of Goa running directly on Sculpt OS by the end of 2025. In addition, I'd like to catch up on my plans of 2024 regarding user-visible Sculpt OS features, introducing a documentation view, a simple file manager, and a convenient way to save settings. I will also definitely wrap up the multi-monitor window management that I have built during the past two months. My wishes for 2025 Outside the realm of my own working topics, I'd love to eventually switch to the base-hw kernel on my Framework laptop. I'd also highly appreciate an update of the Chromium engine for the Falkon web browser. Don't we all want to participate in https://genode.discourse.group using a browser directly on Sculpt OS? ;-) What is your perspective on Genode in 2024 and for 2025? - Has Genode's development during 2024 been in your interest? - Or do you find important aspects neglected? - How was your practical experience with Genode in 2024? - Which directions would you regard as most exciting or pressing? - What are your personal interests and plans for 2025? I'm looking forward to learn about your experiences, plans, and ideas. Like every year, I'll do my best to distill a rough plan for 2025 out from our joint discussion. The road map will be finalized around mid of January. Cheers Norman Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

14 29

Announcement for the restructuring of the world repository
by Josef Söntgen 17 Jan '25

17 Jan '25

Hi, We plan to convert world from a Genode repository into a repository housing goa [1] projects and while doing so tidy things up. At the moment there is no ample schedule, so treat this announcement as a heads-up, but we would like to finish the restructuring process by the beginning of 2026. The following text briefly goes into the reasoning behind this decision and outlines the process. [1] https://github.com/genodelabs/goa The world repository was created as a gathering place for interesting components that enrich the Genode ecosystem but are not strictly placed under the same scrutiny as the ones in the base repositories. This lowers the bar for community contributions and makes it the perfect fit for ported applications and their dependencies. By now the recommended way to bring existing applications over to Genode is by using goa instead of imposing Genode's build-system on the contrib sources. We would like to reinforce that and anticipate that down the road goa will play a vital role also in creating new and non-ported Genode components. The restructuring is thus intended to give goa projects that should be maintained by and large by the community a focal point and keeps the spirit of the world repository alive. As a first step we are going to move the existing content of the world repository into the newly created 'legacy' sub-directory and will adapt the documentation, e.g. REPOSITORIES += $(GENODE_DIR)/repos/world/legacy retains the current state. Next we would like to convert components into goa projects on a case by case basis choosing which we would like to keep maintaining, e.g. Java, and which are eventually destined for removal. And this brings the community, i.e. you, into focus - please get in touch if there are components in world that you are currently use and plan on keep using, potentially becoming the custodian yourself. Regards Josef -- Josef Söntgen Genode Labs http://www.genode-labs.com/ · http://genode.org/

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users