From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Microkernel & guix Date: Sat, 31 Dec 2016 00:29:37 +0100 Message-ID: <87d1g9807y.fsf@gnu.org> References: <871sx1l1pm.fsf@gnu.org> <87inqc8aqv.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40635) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cN6cJ-0001qc-87 for help-guix@gnu.org; Fri, 30 Dec 2016 18:29:44 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cN6cG-0007Nx-3r for help-guix@gnu.org; Fri, 30 Dec 2016 18:29:43 -0500 In-Reply-To: (David Craven's message of "Sat, 24 Dec 2016 21:06:28 +0100") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: David Craven Cc: help-guix@gnu.org David Craven skribis: > 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 :) Sounds like fun anyway. :-) Ludo=E2=80=99.