[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Help with writing custom boot-loader configuration
From: |
Timothy Sample |
Subject: |
Re: Help with writing custom boot-loader configuration |
Date: |
Wed, 05 Jun 2019 09:36:40 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux) |
Hi Raghav,
Raghav Gururajan <address@hidden> 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