all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: guix-devel@gnu.org
Subject: Re: Long term plan for GuixSD security: microkernels, ocap, RISC-V support
Date: Sun, 9 Dec 2018 21:00:41 -0200	[thread overview]
Message-ID: <ef3ee2b5-08a3-a4fb-7e8c-09c7a2b8f2e1@hyperbola.info> (raw)
In-Reply-To: <87bm8nugmv.fsf@inria.fr>


[-- Attachment #1.1: Type: text/plain, Size: 2030 bytes --]

Em 24/09/2018 11:14, Ludovic Courtès escreveu:
> Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
>>    - There's also Google's recent work with Magenta/Fuschia.  From what
>>      I've read, architecturally this looks right.  I think the reason
>>      for worry here is the same difficulty the community has had to
>>      build actual community and libre distributions on top of the
>>      Android ecosystem could apply here.
> 
> Indeed.
> 
> We could also mention MINIX, which many of us are already using daily.
> :-)
> 
> Putting aside Fuschia, I think the Hurd and MINIX are by far the
> solutions that require the less work to be in a state where people with
> “regular needs” like the rest of us to switch (MINIX is probably in that
> state already.)
> 
> The Hurd already has a very advanced POSIX C library, which is not
> negligible, especially compared to the other OSes.  Much progress has
> been made in recent years wrt. drivers (using the Rump kernel in
> particular.)  There are of course serious shortcomings, in particular
> lack of 64-bit and SMP support.  But fixing these is relatively “little
> work” in the grand scheme of things.
> 
> To put this in perspective, consider Linux namespaces: they have already
> seen years of evolution, and the story of user namespaces shows that
> it’s far from complete.

I don't know if what I'll say will be off-topic here given that this
list is about Guix development, not on general free/libre software
activism, but please forgive me anyways.

So, my worry is that if we somehow were to support Fuchsia and if it
were to be not strong auto-upgradable copyleft with community-oriented
enforcement, then we could actually loose the freedoms of the software
for the end user. This thought was initially presented by Eben Moglen
during one of his talks[1], but I just tried to bring the issue to Guix.

[1]
https://media.libreplanet.org/u/libreplanet/m/the-free-software-movement-in-the-age-of-trump/


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  parent reply	other threads:[~2018-12-09 23:01 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
2018-12-09 23:00   ` Adonay Felipe Nogueira [this message]
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=ef3ee2b5-08a3-a4fb-7e8c-09c7a2b8f2e1@hyperbola.info \
    --to=adfeno@hyperbola.info \
    --cc=guix-devel@gnu.org \
    /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.