From: Jonathan Brielmaier <jonathan.brielmaier@web.de>
To: Joshua Branson <jbranso@fastmail.com>, guix-devel@gnu.org
Subject: Re: Long term plan for GuixSD security: microkernels, ocap, RISC-V support
Date: Mon, 24 Sep 2018 19:26:15 +0200 [thread overview]
Message-ID: <47875d90-afec-fa27-414c-be04e1fbbf6f@web.de> (raw)
In-Reply-To: <87k1naq5od.fsf@fastmail.com>
On 9/24/18 5:24 PM, Joshua Branson wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
>> We could also mention MINIX, which many of us are already using daily.
>> :-)
>
> That's pretty awesome! I didn't realize gnu developers were using
> MINIX.
I guess it is a little different as you might think.
Regarding to
https://itsfoss.com/fact-intel-minix-case/
almost every modern (as in last 10 years) Intel CPU runs Minix as "base" system for the management engine (Intel ME).
next prev parent reply other threads:[~2018-09-24 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 12:27 Long term plan for GuixSD security: microkernels, ocap, RISC-V support Christopher Lemmer Webber
2018-08-23 12:58 ` Ricardo Wurmus
2018-08-23 13:43 ` Christopher Lemmer Webber
2018-08-24 12:52 ` Ludovic Courtès
2018-08-24 12:46 ` Ludovic Courtès
2018-08-30 12:31 ` Ludovic Courtès
2018-09-24 14:14 ` Ludovic Courtès
2018-09-24 15:24 ` Joshua Branson
2018-09-24 17:26 ` Jonathan Brielmaier [this message]
2018-12-09 23:00 ` Adonay Felipe Nogueira
2018-12-31 16:16 ` Christopher Lemmer Webber
2018-12-25 21:56 ` Plan for Guix security (was Re: Long term plan for GuixSD security: microkernels, ocap, RISC-V support) Alex Vong
2018-12-26 13:42 ` Marius Bakke
2019-01-05 17:47 ` Ludovic Courtès
2018-12-26 17:48 ` Joshua Branson
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=47875d90-afec-fa27-414c-be04e1fbbf6f@web.de \
--to=jonathan.brielmaier@web.de \
--cc=guix-devel@gnu.org \
--cc=jbranso@fastmail.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 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.