* Allow system configuration without a bootloader
@ 2020-01-01 15:31 kanichos
2020-01-01 21:12 ` Julien Lepiller
0 siblings, 1 reply; 5+ messages in thread
From: kanichos @ 2020-01-01 15:31 UTC (permalink / raw)
To: guix-devel
Hello.
I am very happy with manually setting up my boot programs. On UEFI systems I don’t use a standalone bootloader at all, because I think it is so unnecessary, and rely on Linux ‘EFI stub’ functionality. I don’t ever want any automatic scripts to intervene.
For a couple of years I have used this:
(bootloader (grub-configuration (target "/dev/null")))
It works, but produces an ugly error during configuration.
I believe the field should actually be made optional.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Allow system configuration without a bootloader
2020-01-01 15:31 Allow system configuration without a bootloader kanichos
@ 2020-01-01 21:12 ` Julien Lepiller
2020-01-01 21:39 ` kanichos
0 siblings, 1 reply; 5+ messages in thread
From: Julien Lepiller @ 2020-01-01 21:12 UTC (permalink / raw)
To: guix-devel, kanichos
Le 1 janvier 2020 10:31:08 GMT-05:00, kanichos@yandex.ru a écrit :
>Hello.
>
>I am very happy with manually setting up my boot programs. On UEFI
>systems I don’t use a standalone bootloader at all, because I think it
>is so unnecessary, and rely on Linux ‘EFI stub’ functionality. I don’t
>ever want any automatic scripts to intervene.
>
>For a couple of years I have used this:
>(bootloader (grub-configuration (target "/dev/null")))
>It works, but produces an ugly error during configuration.
>
>I believe the field should actually be made optional.
Have tried to use --no-bootloader when reconfiguring?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Allow system configuration without a bootloader
2020-01-01 21:12 ` Julien Lepiller
@ 2020-01-01 21:39 ` kanichos
2020-01-02 22:28 ` Ludovic Courtès
0 siblings, 1 reply; 5+ messages in thread
From: kanichos @ 2020-01-01 21:39 UTC (permalink / raw)
To: Julien Lepiller, guix-devel@gnu.org
Yes, AFAIR it only works with ‘init’ and has no effect at all with ‘reconfigure’.
02.01.2020, 00:12, "Julien Lepiller" <julien@lepiller.eu>:
> Le 1 janvier 2020 10:31:08 GMT-05:00, kanichos@yandex.ru a écrit :
>> Hello.
>>
>> I am very happy with manually setting up my boot programs. On UEFI
>> systems I don’t use a standalone bootloader at all, because I think it
>> is so unnecessary, and rely on Linux ‘EFI stub’ functionality. I don’t
>> ever want any automatic scripts to intervene.
>>
>> For a couple of years I have used this:
>> (bootloader (grub-configuration (target "/dev/null")))
>> It works, but produces an ugly error during configuration.
>>
>> I believe the field should actually be made optional.
>
> Have tried to use --no-bootloader when reconfiguring?
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Allow system configuration without a bootloader
2020-01-01 21:39 ` kanichos
@ 2020-01-02 22:28 ` Ludovic Courtès
2020-01-02 23:01 ` kanichos
0 siblings, 1 reply; 5+ messages in thread
From: Ludovic Courtès @ 2020-01-02 22:28 UTC (permalink / raw)
To: kanichos@yandex.ru; +Cc: guix-devel@gnu.org
Hi,
"kanichos@yandex.ru" <kanichos@yandex.ru> skribis:
> Yes, AFAIR it only works with ‘init’ and has no effect at all with ‘reconfigure’.
‘--no-bootloader’ should definitely work for ‘reconfigure’; could you
double-check and report a bug if it doesn’t work?
Now, if that’s useful, we could easily define a “noop” bootloader in
(gnu bootloader noop), along these lines:
(define noop-bootloader
(bootloader
(name 'noop)
(package #f)
(installer #~(cons #t))
(configuration-file #f)
(configuration-file-generator #f)))
Thanks,
Ludo’.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Allow system configuration without a bootloader
2020-01-02 22:28 ` Ludovic Courtès
@ 2020-01-02 23:01 ` kanichos
0 siblings, 0 replies; 5+ messages in thread
From: kanichos @ 2020-01-02 23:01 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel@gnu.org
Yes, I just checked and it actually does work. I must have misremembered something.
I also should have looked into how the bootloaders are defined. Since it is just a public record type, I guess there is no problem whatsoever in reality.
Thanks.
03.01.2020, 01:28, "Ludovic Courtès" <ludo@gnu.org>:
> Hi,
>
> "kanichos@yandex.ru" <kanichos@yandex.ru> skribis:
>
>> Yes, AFAIR it only works with ‘init’ and has no effect at all with ‘reconfigure’.
>
> ‘--no-bootloader’ should definitely work for ‘reconfigure’; could you
> double-check and report a bug if it doesn’t work?
>
> Now, if that’s useful, we could easily define a “noop” bootloader in
> (gnu bootloader noop), along these lines:
>
> (define noop-bootloader
> (bootloader
> (name 'noop)
> (package #f)
> (installer #~(cons #t))
> (configuration-file #f)
> (configuration-file-generator #f)))
>
> Thanks,
> Ludo’.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-01-02 23:01 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-01-01 15:31 Allow system configuration without a bootloader kanichos
2020-01-01 21:12 ` Julien Lepiller
2020-01-01 21:39 ` kanichos
2020-01-02 22:28 ` Ludovic Courtès
2020-01-02 23:01 ` kanichos
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.