all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Raghav Gururajan <rvgn@disroot.org>
To: Timothy Sample <samplet@ngyro.com>
Cc: help-guix@gnu.org
Subject: Re: Help with writing custom boot-loader configuration
Date: Wed, 05 Jun 2019 11:30:50 -0400	[thread overview]
Message-ID: <5a8da2409fa4fef22e064d5ac55f0c49b03a51df.camel@disroot.org> (raw)
In-Reply-To: <87muiw6tnb.fsf@ngyro.com>


> Heh.  I didn’t see this before.  Sorry for sending you code you already
> had!

That's okay. No worries.

> I’m not quite sure what you are asking, since Guix does not use
> “grub-mkconfig”.  It has its own way of generating a GRUB configuration
> file.  The “#~(const #t)” trick is the Guix version of running
> “grub-mkconfig” and not “grub-install”.  Is it working for you?

It works. Was curious about other alternatives. Btw, is it possible make guix to
 automatically GPG-Sign the "grub.cfg" it generates during "guix system init" or
"guix system reconfigure" ??

> Is it that you want to use “grub-mkconfig” instead of Guix’s normal
> method?  To be honest, it may be possible, but it’s only for the brave
> of heart (or at least for those who can tolerate a lot of annoying
> difficulties).  :)  The easiest way to do that would be to install GRUB
> and run “grub-mkconfig” manually.

Thanks for the suggestion.

Regards,
RG.

  reply	other threads:[~2019-06-05 15:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30 10:11 Help with writing custom boot-loader configuration Raghav Gururajan
2019-06-03 23:27 ` Raghav Gururajan
2019-06-04  0:49   ` Timothy Sample
2019-06-04 15:40     ` Raghav Gururajan
2019-06-04  1:15   ` Jack Hill
2019-06-04 15:48     ` Raghav Gururajan
2019-06-05 13:36       ` Timothy Sample
2019-06-05 15:30         ` Raghav Gururajan [this message]
2019-06-05 18:01           ` Guix and intrusion detection (was Re: Help with writing custom boot-loader configuration) Giovanni Biscuolo

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=5a8da2409fa4fef22e064d5ac55f0c49b03a51df.camel@disroot.org \
    --to=rvgn@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=samplet@ngyro.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.