From: Pronaip <pronaip@protonmail.com>
To: Vasilii Kolobkov <vasilii@orangeshoelaces.net>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Guix on a microkernel
Date: Mon, 29 Apr 2019 10:21:08 +0000 [thread overview]
Message-ID: <x8TRb2C6zo4bQZeCCVuCwZw-eLb_eoIOZGHKf-xltCuPqglpTSZNoipsIEyrHo3Thkv6RNSuYIXXDNCDYvddB__XnsFjRHBOFQ9LKvRpRqw=@protonmail.com> (raw)
In-Reply-To: <87v9yxaot4.fsf@orangeshoelaces.net>
Not a microkernel, but Plan 9's file system semantics might be worth playing around with. The POSIX emulation probably wouldn't be able to support a full-blown Guix system, but the OS is very well worth taking hints from, at the very least. Overlays would imho be much nicer to work with than path variables.
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Sunday, April 28, 2019 9:54 PM, Vasilii Kolobkov <vasilii@orangeshoelaces.net> wrote:
> My .2 cryptocoins, but you might find it interesting in evaluating HURD
> as a kernerl for Guix system. Frankly, I haven't been following HURD
> development and don't know how much's changed since.
>
> [[http://walfield.org/papers/200707-walfield-critique-of-the-GNU-Hurd.pdf]]
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> v, pgp key 0xFF3C7272972E83A5
next prev parent reply other threads:[~2019-04-29 10:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 0:05 Guix on a microkernel mikadoZero
2019-03-31 6:54 ` znavko
2019-04-01 15:14 ` mikadoZero
2019-03-31 14:08 ` Pjotr Prins
2019-04-01 15:18 ` mikadoZero
2019-04-01 15:33 ` Ludovic Courtès
2019-04-02 17:53 ` Joshua Branson
2019-04-28 19:54 ` Vasilii Kolobkov
2019-04-29 10:21 ` Pronaip [this message]
2019-04-30 16:07 ` mikadoZero
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='x8TRb2C6zo4bQZeCCVuCwZw-eLb_eoIOZGHKf-xltCuPqglpTSZNoipsIEyrHo3Thkv6RNSuYIXXDNCDYvddB__XnsFjRHBOFQ9LKvRpRqw=@protonmail.com' \
--to=pronaip@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=vasilii@orangeshoelaces.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).