all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adonay Felipe Nogueira <adfeno@openmailbox.org>
To: guix-devel@gnu.org
Subject: Re: GuixSD Success with grub-efi
Date: Mon, 29 May 2017 17:35:48 -0300	[thread overview]
Message-ID: <87y3tfwgd7.fsf@openmailbox.org> (raw)
In-Reply-To: <87tw43zr0u.fsf@jamestechnotes.com> (James Richardson's message of "Mon, 29 May 2017 10:17:21 -0400")

Interesting, that would surely be something useful to document.

I wonder if it's possible to use GuixSD with Secure Boot. Remember,
however, that we should embrace Secure Boot and reject Restricted Boot
([[https://media.libreplanet.org/u/libby/m/embracing-secure-boot-and-rejecting-restricted-boot-matthew-garrett/]]). The
reference given show that they're different concepts for free/libre
software activists. Secure Boot allows the user to manage the keys,
while Restricted Boot doesn't allow that. So the difference isn't a
matter of having an "on-off" switch.

One thing sounds odd, though: When you say you had to disable Secure
Boot, did you mean that you had to disable it before installing GuixSD, and
then enable Secure Boot after instalation in order for you to use GuixSD
with it? Or did you keep it disabled even after instalation?

-- 
- [[https://libreplanet.org/wiki/User:Adfeno]]
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre, por isso não uso. Iguais a ele prefiro
  GNU Ring, ou Tox. Quer outras formas de contato? Adicione o vCard
  que está no endereço acima aos teus contatos.
- Pretende me enviar arquivos .doc, .ppt, .cdr, ou .mp3? OK, eu
  aceito, mas não repasso. Entrego apenas em formatos favoráveis ao
  /software/ livre. Favor entrar em contato em caso de dúvida.

  reply	other threads:[~2017-05-29 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 14:17 GuixSD Success with grub-efi James Richardson
2017-05-29 20:35 ` Adonay Felipe Nogueira [this message]
2017-05-30 15:59 ` Marius Bakke

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=87y3tfwgd7.fsf@openmailbox.org \
    --to=adfeno@openmailbox.org \
    --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.