From: David Craven <david@craven.ch>
To: ng0 <ng0@libertad.pw>
Cc: help-guix@gnu.org
Subject: Re: Microkernel & guix
Date: Sat, 24 Dec 2016 21:06:28 +0100 [thread overview]
Message-ID: <CAL1_imnopAqPPRFE_iG0tZFbiU=jE-6GbO3T2ZFVXRFLEEAi_w@mail.gmail.com> (raw)
In-Reply-To: <87inqc8aqv.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>
So after doing some hardcore reading of most of the genode operating
system manual today (excluding the build system, under the hood and
functional specification parts) I think I have a better understanding
of how guix and genode could complement each other and what steps
could be taken. Here are my initial thoughts:
1. genode-build-system would be used for building genode components.
2. genode-operating-system would specify the configuration of genode
components and generate their xml configuration and guix system vm
would assemble a full bootable genode system.
3. guix-daemon component based on the nix-daemon component is needed.
4. using this new component support for generations and genode system
reconfiguration can be added
5. a shepherd component is created and the genode-operating-system is
extended to take one or more operating-system declarations to spawn
guix userspaces. For a genode-operating-system implementing a headless
hypervisor each application can run in it's own shepherd component,
maybe requiring an additional shepherd-multiplexer component. If
building a desktop os it can be run in a single shepherd component
with exclusive access to the framebuffer and input components.
I'll have to see if my time, skill and discipline is enough to
materialize into something useful :)
next prev parent reply other threads:[~2016-12-24 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-21 12:26 Microkernel & guix David Craven
2016-12-21 15:51 ` Ludovic Courtès
2016-12-22 11:27 ` ng0
2016-12-24 20:06 ` David Craven [this message]
2016-12-30 23:29 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL1_imnopAqPPRFE_iG0tZFbiU=jE-6GbO3T2ZFVXRFLEEAi_w@mail.gmail.com' \
--to=david@craven.ch \
--cc=help-guix@gnu.org \
--cc=ng0@libertad.pw \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.