users

users@lists.genode.org

2 participants
2342 discussions

FUSE + VFS
by Samuel Hall 19 Jan '16

19 Jan '16

Hi, I'm looking into FUSE in genode. Since there is hardly any documentation I am having trouble understanding what exactly is going on. Especially I have trouble understanding where and how FUSE interacts with genodes VFS. Do you have any tips where to look? For better understanding I made a chart of the dependencies I found: http://fs5.directupload.net/images/160119/7ejysxf7.jpg Kind regards Hall Samuel

2 1

Yet another problem with Genode+Nova_x86_64+VirtualBox on USB stick
by 1 2 19 Jan '16

19 Jan '16

1 0

How to calculate the TCB size
by JaeminPark 19 Jan '16

19 Jan '16

I’m working with Genode to implement the ARM TZ-based idea. For evaluation, I’d like to count the line of code of the TCB. In the build folder, I could find "var/libcache" folder, and there the compiled files for my build configuration could be found. Do I need to check all files listed in each .d files in “var/libcache” or is there any efficient way to count the number of lines for the TCB?

3 2

Creating new ROM sessions at runtime
by Georg Guba 18 Jan '16

18 Jan '16

Hi all, I'm trying to start new child components from ELF binaries received at run-time and stored in a server-local buffer. Basically, I am trying to implement a server that can receive task descriptions and matching binaries and then start them at run-time (disregarding security concerns for the moment). It appears, however, that all ROM connections must reference binaries that are available at boot-time and adding to the ROM FS is not possible without accessing Genode's internal code which I'd like to avoid. So, how would I best go about creating entirely new ROM sessions at runtime? Best regards, Georg

3 3

Roadmap 2016
by Norman Feske 18 Jan '16

18 Jan '16

Hello, the end of the year 2015 is approaching. So it is time for planning our activities for the upcoming year. I plan to finalize the roadmap until mid of January. Hereby, I'd like to kick off the discussion. It goes without saying that everyone of you is invited to join in! Before I come to my suggestions for 2016, let me briefly revisit the outcome of the roadmap for the past year. One year ago, I suggested three main topics to work on, namely the use of Genode as general-purpose OS, the advancement of our custom base-hw kernel platform, and the use of the seL4 kernel. In the discussions following my posting, many further points were raised, most prominently the need for through documentation, package management, and a sustainable quality of the base system in terms of stability and performance. In top of that, we received quite a few wishes of higher-level functionality such as a modern web browser or other typical desktop-computing features. Of course, we were not able to address all those topics but I am overly happy that we reached the point where a hand full of us (including me) are using Genode as their day-to-day OS. When I initially switched to using the Turmvilla scenario [1] at the end of May, the experience was admittedly a bit painful. But now, just a few months later, the beauty of the system becomes apparent as all the pieces come so nicely together. The performance, stability, and device-driver support have reached a level that leaves people impressed every time I have the chance to show off my system. Once people become interested, there is now the book available, which provides a smooth introduction into Genode. The feedback I receive about the book is overwhelmingly positive. So we did something right in 2015. :-) After having passed the point where a few of us are able to use Genode as day-to-day OS, we should put the emphasis of the upcoming year on ways to make Genode accessible for a wider community. In a recent posting [2], I identified two possible ways to do that. The first way would be publishing a series of step-by-step guides that explain how to put Genode components together in order to create custom system scenarios. Those articles could be accompanied by screencasts or live-system images. Example scenarios could be the Turmvilla scenario, building a home-computer-like system for kids using the Raspberry Pi (like the Genode system my kids are using), building a network appliance like a data diode, tinkering with the USB Armory, etc. Those articles should be inviting to people who enjoy the building of systems. The second way would be to showcase a system with practical value to end users. I am thinking along the lines of a disposable OS like Tails that allows the user to browse the internet via the Tor network. But that is just an idea. In this spirit, I propose the overall focus of 2016 to be: Let us make Genode accessible to the world outside the inner circle of us enthusiasts. On a technical level, this motive implicates the following topics: * The deployment and management of Genode systems, i.e., by bringing forward Emery's work on the Nix package manager. This direction also reinforces the need to achieve binary compatibility between the various base platforms to make the distribution of binary packages, reproduceable builds, and continues test-and-integration scalable. * Supplementing Genode with user-friendly means to configure the system (e.g., wireless network, audio, display settings). Right now, I use Vim as configuration front end, which is cool, but also intimidating to less technical-minded users. * Accommodation of common desktop use cases like plugging in a USB stick to work with the files stored on it. Also disk encryption comes into mind. * Optimization of Genode for the use on a laptop, e.g., addressing fan control, power management, suspend/resume, and similar features. There are also other possible avenues to support the stated goal: * Identifying ways of how Genode could play a role in related projects like Qubes OS. For example, we could promote the use of Genode as a tool for building App VMs as Qubes subsystems. Granted, this scenario leaves the architectural benefits of Genode with respect to its small TCB complexity unused as Qubes still relies on Xen, and Linux as Dom0. But Genode would still (possibly) provide value to the Qubes project. Maybe, there would be the prospect to replace Dom0 with Genode in the longer term? However, to drive this direction of work, we would certainly need someone who is actually using Qubes and has the natural incentive to work on such an integration. * Making Genode-based systems easily deployable on Amazon's EC2. Similar to the previous point, it would be beneficial to have someone working on this topic who is naturally interested in cloud computing. * Foster the cross-pollination of the seL4 and Genode communities. I got enthusiastic responses about my seL4-related work. There is definitely a strong interest in this kernel and a growing anticipation for formally verified software. Today, seL4 lacks a scalable user-level architecture. This would be the perfect place where Genode could step in. Genode would ultimately allow the seL4 community to move beyond static system scenarios. Assuming that we succeed in drawing the attention of a broader audience to our project, we should make sure that Genode's API won't undergo major changes soon after this point. Today, I still see a number of deficiencies in the current API. In the past year, we successively moved to a new model of the API (dubbed server API) that promotes the construction of components as state machines rather than procedural programs. All recent components are designed in this style to the great benefit of their robustness. We should finally promote this style towards the base API and get rid of some mistakes we made in the past, in particular the reliance on side effects by using the globally visible Genode::env. I think that we should finalize this API renovation until the mid of 2016. This will also be right the time for updating the Genode book. These are my thoughts about the upcoming year. Now I am curious about yours! :-) Cheers Norman [1] https://github.com/genodelabs/genode/issues/1552 [2] https://github.com/genodelabs/genode/issues/1000#issuecomment-161260312 -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

14 47

QT5 Linux_x86
by Torsten Thoben 15 Jan '16

15 Jan '16

Hello Genode Community, I'm new to Genode and i want to use QT5 with the Linux_x86 Kernel. The demo example works well, but if i try to run qt5_quicktest or other qt5 run files, the only thing i see is a empty window and a Mouse Courser. I use Ubuntu 14.04.3 LTS. I add these lines to the build.conf: REPOSITORIES += $(GENODE_DIR)/repos/libports REPOSITORIES += $(GENODE_DIR)/repos/gems MAKE += -j4 And this is my Output: Genode 15.08 int main(): --- create local services --- int main(): --- start init --- int main(): transferred 17592186044415 MB to init int main(): --- init created, waiting for exit condition --- Quota exceeded! amount=24576, size=4096, consumed=24576 [init] upgrading quota donation for Env::CPU (8192 bytes) Quota exceeded! amount=32768, size=4096, consumed=32768 [init] upgrading quota donation for Env::CPU (8192 bytes) [init -> fb_sdl] Could not open ROM session for module "config" [init -> fb_sdl] Could not obtain config file [init -> wm] Could not open ROM session for module "focus" [init -> wm] Uncaught exception of type 'N6Genode14Rom_connection21Rom_connection_failedE' (use 'c++filt -t' to demangle) [init -> wm] abort called - thread: 'desktop_ep' [init -> fb_sdl] creating virtual framebuffer for mode 1024x768@...64... [init -> nitpicker] create session with args: label="pointer", ram_quota=28672 [init -> qt_quicktest] tar archive 'qt5_fs_qt_quicktest.tar' local at 2b92ca739000, size is 665600 [init -> qt_quicktest] void init_libc_lock_pipe(): init_libc_lock_pipe() [init -> qt_quicktest] using the pipe libc plugin [init -> qt_quicktest] read_rtc: rtc not configured, returning 0 [init -> qt_quicktest] pid_t getpid(): getpid not implemented I hope you can help me to get the qt5 examples running correct. Best regards, Torsten

2 2

RPC parameters
by Bilal ma 14 Jan '16

14 Jan '16

HI,Genode is new to me . I just start playing with it. I was looking at the Hello program and the RPC mechanism. as i understood RPC does not support passing pointer as parameter how i can pass a parameter by reference where i need to change its value in the server side. I found in the rpc.h that the parameter could be input and output in the same time. How i can use this ? are there any implemented examples . should i defined an my output structure if the remote procedure return multiple outputs. best.

2 4

Secure GUI Programs
by Nobody III 14 Jan '16

14 Jan '16

I've been thinking about writing graphical utilities (e.g. a file manager), but I'm not sure whether I should be using Qt. Can I consider Qt secure for things such as rendering filenames from untrusted filesystem servers? If not, what do you suggest? Also, is there a file manager anyone has already started making? Another question: for previews/thumbnails (e.g. for icons), is it reasonably efficient to render the preview for each file in its own process, or should I batch them together?

2 1

Verifiable repository integrity
by Christian Helmuth 13 Jan '16

13 Jan '16

Hi everybody, some days ago, the Genode Labs team had a coffee break discussion about possible means for developers to verify the integrity of the official Genode repository. In the following, I want to explain the current state and put up for discussion what could be improved with some effort. In November 2011, our Git repository on GitHub superseded the Sourceforge Subversion repository and tar archives as main source-code distribution channel. The release history is easily replicable by following Git tags. In 2012, we had a discussion in our issue tracker [1] about signing the release tags and integrated this step in our work flow shortly after. As a result the integrity of a release can be checked by verifying the corresponding Git tag since Genode 12.05. At this time, the interest into our Sourceforge archives already almost vanished, so we never bothered to apply these integrity measures there too. In the above-mentioned discussion, someone brought up Git's support for "signed commits" from the background that each release adds about 250 commits to the repository in three months. This is also the reason why more and more developers intrepidly base their work on the Genode master branch. With signed commits in place, developers may always verify the integrity of the upstream repository revision used (see [3] for an article about Git signed commits). To me this sounds tempting and represents the natural continuation of our open development history. Our current work flow includes two branches of the Genode repository: staging and master. The complete rationale can be found in Section 5.5.1 of [2]. The staging branch is the entrance hall for all contributions to Genode from the community and the core team members alike. Bug fixes, topic branches, and other improvements have to pass our nightly autopilot testing and a thorough review by Norman and me on staging before entering our master branch. As we apply the Git rebase work flow the master history is a linear series of commits with no parallel development branches and merge points. Before a batch of commits from staging is added to master original commits and potential fixup commits are squashed into reasonable commits for master. The work flow explained above does not support the preservation of commit signatures by the author of the original commit because of cherry-picking and potential squashes. Also, the integrity of the master branch is more "you get what the core team reviewed" than "this is what the author committed originally". In my opinion a batch of commits should be signed by the reviewer when added to the master branch. Unfortunately, the Git tool itself does not include an easily usable tool for signing all commits of such a batch before pushing the updated master branch. But, we could sign just the head of batch and get a verifiable update step with git commit --gpg-sign --amend --no-edit && git push origin HEAD:master Among other options the signatures can be checked by git log --show-signature and the head of master would always show "gpg: Good signature...". Does this proposal make sense to you resp. does the explained approach represent the intended improvement for developers caring about upstream repository integrity? [1] Issue 138 https://github.com/genodelabs/genode/issues/138 [2] Genode Foundations http://genode.org/documentation/genode-foundations-15-05.pdf [3] https://mikegerwitz.com/papers/git-horror-story Regards -- Christian Helmuth Genode Labs http://www.genode-labs.com/ · http://genode.org/ https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/ Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

FOSDEM 2016
by Norman Feske 11 Jan '16

11 Jan '16

Hello everyone, hereby, I'd like to remind you of FOSDEM 2016, which takes place during 30 and 31 of January in Brussels. See https://fosdem.org/2016/ to learn more about the world's biggest gathering of open-source and free-software enthusiasts. This year, Genode will show a strong presence again. On Saturday, Emery, Martin, and me will contribute to the microkernel devroom (https://fosdem.org/2016/schedule/track/microkernels/). On Sunday, I'm taking the opportunity to present the Turmvilla scenario at the desktops devroom. Below, you can find the summary of the Genode-related parts of the FOSDEM schedule. Saturday, January 30 -------------------- Microkernel devroom (K.4.601) at *10:40* Norman Feske "An exploration of the seL4 kernel from Genode's perspective" https://fosdem.org/2016/schedule/event/microkernels_genode_sel4/ Microkernel devroom (K.4.601) at *14:10* Emery Hemingway "Porting Nix to Genode - Package management without a canonical file system" https://fosdem.org/2016/schedule/event/microkernels_genode_nix/ Microkernel devroom (K.4.601) at *15:55* Martin Stein "Genode's TrustZone demo on the USB Armory" https://fosdem.org/2016/schedule/event/microkernels_genode_usb_armory/ Sunday, January 31 ------------------ Desktops devroom (K.4.401) at *10:20* Norman Feske "Genode as Desktop OS" https://fosdem.org/2016/schedule/event/genode_as_a_desktop_os/ -- Dr.-Ing. Norman Feske Genode Labs http://www.genode-labs.com · http://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users