From: Timothy Sample <samplet@ngyro.com>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Help with writing custom boot-loader configuration
Date: Wed, 05 Jun 2019 09:36:40 -0400 [thread overview]
Message-ID: <87muiw6tnb.fsf@ngyro.com> (raw)
In-Reply-To: 18883b91119efe33ba03ba118449e1cb1f82cfea.camel@disroot.org
Hi Raghav,
Raghav Gururajan <rvgn@disroot.org> writes:
>>
>> My first thought after reading your question was
>> <https://lists.gnu.org/archive/html/help-guix/2019-05/msg00275.html>.
>
> Yes, I was looking for a method other than using (const ~#t).
Heh. I didn’t see this before. Sorry for sending you code you already
had!
>> However, I guess you need something else, but I'm not sure what it is. Can
>> you explain more what you're trying to do? Thanks!
>
> I was looking for a way to directly alter the behaviour of grub-installer. The
> two of all functions of grub-installer are "grub-install" and "grub-mkconfig".
> The former install grub binaries on disk and the latter generates grub
> configuration file inside root partition under boot directory. I was thinking if
> there is a straight-forward way to make the grub-installer to invoke ONLY "grub-
> mkconfig" and NOT "grub-install"??
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?
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.
-- Tim
next prev parent reply other threads:[~2019-06-05 13:36 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 [this message]
2019-06-05 15:30 ` Raghav Gururajan
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
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=87muiw6tnb.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=help-guix@gnu.org \
--cc=rvgn@disroot.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.
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).