users

users@lists.genode.org

2285 discussions

linux uart driver
by Prashanth Mundkur 16 Feb '17

16 Feb '17

Hi, I'm exploring writing a simple uart driver for linux in order to get terminal_mux working on linux. When I disable the linux spec check in terminal_mux.run, the build always picks up: Program drivers/uart/spec/x86/uart_drv even though I created a drivers/uart/spec/linux/ and changed drivers/uart/spec/linux/target.mk to read REQUIRES = linux and the etc/specs.conf in the build directory to read: SPECS += linux x86_64 I'd like to know how I can get the build to say Program drivers/uart/spec/linux/uart_drv Thanks, --prashanth

2 2

Q2 - build demo error
by Philip Rhoades 14 Feb '17

14 Feb '17

People, Using Fedora 25 x86_64 I get: Program drivers/framebuffer/spec/sdl/fb_sdl COMPILE fb_sdl.o COMPILE input.o LINK fb_sdl /usr/bin/ld: cannot find -lsupc++ collect2: error: ld returned 1 exit status /root/genode/repos/base/mk/prg.mk:174: recipe for target 'fb_sdl' failed make[3]: *** [fb_sdl] Error 1 var/libdeps:375: recipe for target 'fb_sdl.prg' failed make[2]: *** [fb_sdl.prg] Error 2 Makefile:270: recipe for target 'gen_deps_and_build_targets' failed make[1]: *** [gen_deps_and_build_targets] Error 2 make[1]: Leaving directory '/root/genode/build.lx' Error: Genode build failed Makefile:307: recipe for target 'run/demo' failed make: *** [run/demo] Error 252 The only relevant Google result taslked about static linking . . but I thought it better to ask here first . . Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@...479...

2 1

Smallest supported OS ?
by Philip Rhoades 14 Feb '17

14 Feb '17

People, I have only just signed up - I was led to Genode by a post on the MaidSAFE forum and so I am quite interested in the prospects for Genode and I want to get involved. First question - from searching the archives I can't see any info on one of things I am interested in - what is the smallest bootable OS that can be set up with Genode? - could it be small enough to fit on a floppy disk? Thanks, Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@...479...

2 2

Re: USB storage detachment / reattachment
by Boris Mulder 13 Feb '17

13 Feb '17

Dear Genode developers, Following Martijn's mail at the end of last year, which stated: >> As a way to support detachment / reattachment of USB storage I’m >> thinking about placing the rump_fs and part_blk components in a child >> subtree of the CLI component that is spawned on demand and cleaned-up >> after use. But this seems a bit like overkill. > That's exactly the right solution. I don't think that it's overkill > either. Spawning up rump_fs and part_blk dynamically is certainly quick > enough. Memory-wise, it does not take more resources that a static > scenario either. By letting your CLI component implement the protocol > outlined above, you have full control over chain of events. Also the > aborting rump_fs is nothing fatal anymore but can be gracefully handled > by the CLI component. As another benefit, the solution does not need us > to supplement the notion of hot-plugging to the file-system and block > session interfaces, which would otherwise inflate the complexity of > these interfaces (and thereby all the clients that rely on them). Martijn and I have been thinking of a way to implement this, and came to the conclusion that instead of spawning the stack as children of the CLI component, it might be better to use a new management component in-between. As Josef said earlier: > A custom runtime/management component could monitor the > usb_drv device report and spawn the whole stack if it detects a USB > storage device. The usb_drv's device report does not contain the device > class so far though but adding that to the report is easy. This is exactly what we're trying to do now. We want to create a custom component called "media" that monitors usb devices by reading the report. It provides a service to other components through which they can request a filesystem session in order to read-write from/to the usb-stick. For this, it spawns the part_blk and rump_fs components as children if the usb is plugged in, and kills them once the usb is plugged out. It roughly looks like this: rump_fs part_blk | | CLI media USB_drv | | | init But this raises a few questions. First, the filesystem interface needs to be presented to the client somehow. To avoid adding another layer of indirection into media, essentially duplicating rump_fs's entire API, we would like the client (in this case CLI) to be directly connected to rump_fs. The client can then ask media if the USB is connected before calling a function from rump_fs. However, this means that rump_fs provides a service, announces it to its parent (media), and media has to decide what to do with that announce. It can implement rump_fs as a slave, but that way the entire API needs to be copied into media so media can present it as its own service to the client. So we would like media to announce the filesystem service to its parent (in this case init), so any client can use this service. In the same way, any session request will be passed from CLI to its parent (init), init has to pass it to media, and media passes it to rump_fs. However, the current implementation and specification of genode does not allow services of any server to exist in any level above the server's parent. Services can only be provided to direct parents, and to other components in the parent's subtree. Therefore, copying the API from the child to the parent seems unavoidable. Another problem that pops up is that media has to spawn all these subcomponents as children. In order to route block session requests from rump-fs to part-blk, media needs to implement some routing policy and effectively serves the same role for these two components as init serves for the system. So we could: 1. Copy all necessary code for routing from init to media (which is almost all code if we want to be generic). 2. Let media spawn another init child component (let's call it sub-init for now) which in turn spawns rump-fs and part-blk and does the routing. To us, the second option seems much more clean as it involves no code-copying. However, services announced by rump-fs can not be used by other components that are not children of the new init, and are kind of useless. Their announcements can not be passed on to the parents, leaving us with the same problem as we had with rump_fs but with the additional problem that even if there would be a custom way to forward service announces and requests to the parent/child respectively, sub-init has no such policy, and this functionality has to be included in sub-init's code as well, adding a lot of complexity. Eventually both cases bottle down to the same problem: service announcements to a parent cannot automatically be forwarded to that parent's parent, and likewise, service requests need to be able to be delegated to children of children without a lot of hassle. The only option if I'm correct is implementing this functionality manually, but this does not work if the parent is an existing component that does not support it. Is there a reason this is never done? For init it is clear that it would never pass an announce to its parent (usually core) or receive session requests from it. But how about the general case? And how should we solve cases such as the above scenario? kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

4 10

Volume names of partitions
by Boris Mulder 10 Feb '17

10 Feb '17

Hi, Many file system formats support a name tag. Is there any way in Genode to read or write this "volume name"? -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 1

Thoughts about FOSDEM 2017
by Norman Feske 08 Feb '17

08 Feb '17

Hello, hereby I'd like to share my impressions from FOSDEM this year. I looked forward to FOSDEM very much - in particular to the microkernel devroom - and all I can say is that it was a pleasure to attend. Thanks to everyone who contributed to it! The following points stood out to me: * The topics in the devroom were nicely diverse, ranging from kernel design, over the use of microkernels in microcontrollers (F9), entertaining experience stories (MINIX), to practical walk throughs (HURD). Even though the projects are not directly working together in term of code developments, the collaborative spirit was clearly there. What a nice and friendly gathering! * I found David Teller's (Redox) take on explaining the benefits of microkernels quite refreshing - highlighting practical aspects like an easier upgrade path for system components compared to monolithic systems. As a side node, it was stunning to see the popularity of the Redox project according to crowd watching the talk. * Martin Decky (HelenOS) briefly presented the idea of forming an open-source microkernel umbrella organization, i.e., to increase the chance of acceptance to GSoC. Admittedly, we (Genode Labs) haven't planned to apply to GSoC (we tried once but were rejected with no feedback). However, personally, I'd support the idea of a joint application of the larger community. Martin and Jakub proposed to use the FOSDEM devroom and thereby the same community that is behind microkernel.info as umbrella organization. This sounds sensible to me as this community already exists to the mutual benefit of everyone involved, and is open for everyone to join. I wonder, do you (the people of the Genode community) have an opinion about this idea, and GSoC in general? * I got very excited about the presentation of the WireGuard project, which is a new take on virtual private networking for the Linux kernel. Not only was the presentation a joy to follow, the project seems to be a perfect fit for a distributed Genode system. It addresses my main concern about existing open-source solutions like OpenVPN and IPSec, namely their daunting complexity. I am not a VPN expert though. From those of you who are familiar with both VPN solutions and Genode, I'd love to hear your thoughts on WireGuard! * I found the SAFE network talk very inspiring in that the project presents a holistic architectural solution to many problems that plague the internet today. Since having watched the talk, I wonder if it would make any sense to have the SAFE launcher available on Genode? Again, thanks to all participants of the devroom (especially Josef), and for the many vivid discussions at FOSDEM. See you next year! Cheers Norman -- 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

1 1

Fwd: Re: [Genode] Suggestion about mailing list subject
by Martin Stein 07 Feb '17

07 Feb '17

-------- Weitergeleitete Nachricht -------- Betreff: Re: [Genode] Suggestion about mailing list subject Datum: Tue, 7 Feb 2017 09:48:44 -0500 Von: Jeroen "Slim" van Gelderen <askslim@...9...> An: martin.stein@...1... The redundant information clutters up small screens and makes subject lines difficult to read on mobile. I'm not sure what the problem is with filtering messages for these folks. On 7 Feb 2017 07:52, "Martin Stein" <martin.stein@...1... <mailto:martin.stein@...1...>> wrote: I personally let my mail client filter my mails by the destination address into separate folders. This works fine for me. But if an additional prefix is desired, why not. Cheers, Martin Am 07.02.2017 um 12:20 schrieb Parfait Tokponnon: > Hello, > Personally, I think this is very useful, > I receive mails from various mailing lists and this is the best way I > can distinguish at a glance the origin of the mail. > cheers > > 2017-02-07 11:08 GMT+01:00 Christian Helmuth > <christian.helmuth@...1... <mailto:christian.helmuth@...1...> > <mailto:christian.helmuth@...1... <mailto:christian.helmuth@...1...>>>: > > Hello Martín, > > On Mon, Jan 30, 2017 at 07:57:33AM -0500, Martin Iturbide wrote: > > I was wondering if it can be useful to configure the mailing list to > > include on the subject (before the text) something like [Genode] or > > [Genode-Main] . I know that it is easy to set a rule and folder for the > > mailing list messages on the mail client, but in some other cases I like to > > identify visually and fast the messages that are from this mailing list in > > a group of mails. > > > > This is just a thought, I don't know how hard or easy will be to configure > > this on the sourceforge mailing lists. > > Technically this is pretty simple by means of the Mailman > subject_prefix feature. I personally do not like all subject lines > written by users of the list cluttered with some prefix text. But, if > other members of the list also express their demand for this feature > and there's no overly resistance voiced I would enable it > nevertheless. > > Greets > -- > Christian Helmuth > Genode Labs > > https://www.genode-labs.com/ · https://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 > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > genode-main mailing list > genode-main(a)lists.sourceforge.net <mailto:genode-main@lists.sourceforge.net> > <mailto:genode-main@lists.sourceforge.net <mailto:genode-main@lists.sourceforge.net>> > https://lists.sourceforge.net/lists/listinfo/genode-main <https://lists.sourceforge.net/lists/listinfo/genode-main> > <https://lists.sourceforge.net/lists/listinfo/genode-main <https://lists.sourceforge.net/lists/listinfo/genode-main>> > > > > > -- > Parfait T. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > _______________________________________________ > genode-main mailing list > genode-main(a)lists.sourceforge.net <mailto:genode-main@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/genode-main <https://lists.sourceforge.net/lists/listinfo/genode-main> > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ genode-main mailing list genode-main(a)lists.sourceforge.net <mailto:genode-main@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/genode-main <https://lists.sourceforge.net/lists/listinfo/genode-main>

1 0

Deprecated warnings
by Boris Mulder 07 Feb '17

07 Feb '17

Hi all, Whenever I compile my source with the latest version of Genode, I am getting hundreds and hundreds of deprecated warnings. I understand you might fix them in the future, but they clog my compiler output and make reading other compiler errors a pain. Is there some easy point in the makefiles where I can change it so that I can disable all of them temporarily? I tried appending it to global.mk: CC_WARN ?= -Wall -Wno-deprecated but this still gave me the warnings. Where can I disable it? Regards, Boris -- Met vriendelijke groet / kind regards, Boris Mulder Cyber Security Labs B.V. | Gooimeer 6-31 | 1411 DD Naarden | The Netherlands +31 35 631 3253 (office)

2 3

Some questions
by Hack 06 Feb '17

06 Feb '17

Hi, I am currently using Qubes OS, but with the next release, I will have to upgrade my hardware. And it will cost me a lot. Anyway, I started to look at Genode OS, but I can't find an hardware support list. Questions: 1. How to know if my current configuration will be supported? 2. Is there any 3d support with Genode OS? 3. Is it possible to use Genode OS as desktop OS? Thanks

2 3

tcp_terminal on linux
by Prashanth Mundkur 03 Feb '17

03 Feb '17

Hi, I'm trying to use tcp_terminal on linux. It of course prominently says: # TODO: Add support for Linux via user-level networking (using the # tun/tap proxy driver at os/src/drivers/nic/linux) After disabling the have_spec check, I can compile and run it. After setting the suid bit on drivers/nic/spec/linux/nic_drv to allow it to access /dev/net/tun, I get the following output: genode build completed using 'core-linux' as 'core' using 'ld-linux.lib.so' as 'ld.lib.so' using 'linux_timer_drv' as 'timer' spawn ./core Genode 16.11-146-gc16ee83 <local changes> 17592186044415 MiB RAM assigned to init [init] parent provides [init] service "ROM" [init] service "RAM" [init] service "IRQ" [init] service "IO_MEM" [init] service "IO_PORT" [init] service "PD" [init] service "RM" [init] service "CPU" [init] service "LOG" [init] child "timer" [init] RAM quota: 798720 [init] ELF binary: timer [init] priority: 0 [init] provides service Timer [init] child "nic_drv" [init] RAM quota: 3944448 [init] ELF binary: nic_drv [init] priority: 0 [init] provides service Nic [init] child "tcp_terminal" [init] RAM quota: 2371584 [init] ELF binary: tcp_terminal [init] priority: 0 [init] provides service Terminal [init] child "test-terminal_echo" [init] RAM quota: 798720 [init] ELF binary: test-terminal_echo [init] priority: 0 [init] child "nic_drv" announces service "Nic" [init -> test-terminal_echo] Warning: using legacy main function, please convert to 'Component::construct' [init] child "timer" announces service "Timer" [init -> tcp_terminal] using the pipe libc plugin [init -> tcp_terminal] init_nic_dhcp [init -> tcp_terminal] Using DHCP for interface configuration. [init -> tcp_terminal] using the lwIP libc plugin [init -> nic_drv] no config provided, using tap0 [init -> tcp_terminal] Warning: '<config> <libc> <vfs/>' is deprecated, please move to '<config> <vfs/>' [init -> tcp_terminal] --- TCP terminal started --- [init] child "tcp_terminal" announces service "Terminal" [init -> tcp_terminal] listening on port 8888 with socket 16... [init -> tcp_terminal] adding listen sock 16 to select set Though I can see the tap device, 15: tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether c2:60:31:f8:52:fc brd ff:ff:ff:ff:ff:ff I don't see any listening socket on port 8888. So clearly there is some missing plumbing. What do I need to do to fill that in? Thanks, --prashanth

2 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users