unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: mikadoZero <mikadozero@yandex.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix on a microkernel
Date: Sun, 31 Mar 2019 16:08:31 +0200	[thread overview]
Message-ID: <20190331140831.xyn52a2twevacwfu@thebird.nl> (raw)
In-Reply-To: <cuc36n36h7v.fsf@yandex.com>

On Sat, Mar 30, 2019 at 08:05:40PM -0400, mikadoZero wrote:
> * I am curious what others think of microkernels.

Microkernels are of great interest from a security point of view. I
think they will become popular once there is a usable alternative. We
need free software, free software and proper isolation at the OS
level to improve security.

> ### Why Hurd?
> 
> Why the focus on Hurd given other microkernel options?  I ask this
> question out of curiosity and a lack of practical experience with
> microkernels.

Call it an accident of history ;). Being a GNU project we have a stake
in getting the Hurd to a usable level and get people to start using
it for daily work. 

I attended a talk at FOSDEM this year which gave an overview

https://fosdem.org/2019/schedule/event/roadmap_for_the_hurd/attachments/slides/3270/export/events/attachments/roadmap_for_the_hurd/slides/3270/2019_02_01_fosdem_roadmap.pdf

It looks like not a fat lot is needed to make this usable for many
people. Most free software will actually run on Hurd today.

Pj.

  parent reply	other threads:[~2019-03-31 14:13 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 [this message]
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
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=20190331140831.xyn52a2twevacwfu@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    --cc=mikadozero@yandex.com \
    /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).