From: Paul Boddie <paul@boddie.org.uk>
To: radoslaw@chmielarz.xyz
Cc: help-guix@gnu.org
Subject: Re: Guix and sel4
Date: Mon, 15 Jan 2018 22:17:54 +0100 [thread overview]
Message-ID: <201801152217.55105.paul@boddie.org.uk> (raw)
In-Reply-To: <9b985bf236a0f43870259bf105f6f36d@chmielarz.xyz>
On Monday 15. January 2018 21.44.08 radoslaw@chmielarz.xyz wrote:
>
> It wasn't entirely what I was hoping for but thank You for answering. So
> to dig a little deeper how closely is guix connected to linux kernel?
Some people are using Guix with the Hurd, so maybe they can explain the
relationship between Guix and things other than the Linux kernel.
I would guess that Guix shouldn't really care too much about the underlying
system below a certain level, but then again I haven't looked into the details
of the project that was mentioned involving Nix and Genode and why the Genode
developers subsequently decided to do their own thing.
The L4Re (as opposed to Genode) sources contains package modules that are
reminiscent of things in the source trees of distributions like OpenWrt and
OpenEmbedded (if I remember the latter correctly), but I don't think there is
any notion of installing these packages while running the system. Instead,
they appear to be bundled in the payload deployed to a system, at least within
the scope of my own experiments.
But package installation would mostly involve making files available in the
filesystem that can then be accessed and executed, so I can imagine that with
filesystem and program launching capabilities, you could have a package
manager for L4Re. Maybe one already exists.
All this said, I'm obviously still learning about L4Re and associated
technologies, so I should probably investigate further before saying anything
else. ;-)
Paul
next prev parent reply other threads:[~2018-01-15 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 21:16 Guix and sel4 radoslaw
2018-01-14 23:26 ` Paul Boddie
2018-01-15 20:44 ` radoslaw
2018-01-15 21:17 ` Paul Boddie [this message]
2018-01-15 21:18 ` Efraim Flashner
2018-01-16 16:23 ` 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=201801152217.55105.paul@boddie.org.uk \
--to=paul@boddie.org.uk \
--cc=help-guix@gnu.org \
--cc=radoslaw@chmielarz.xyz \
/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.