From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Dualbooting with guixsd not handling grub installation
Date: Mon, 11 Dec 2017 10:39:24 +0100 [thread overview]
Message-ID: <87bmj54n8z.fsf@gnu.org> (raw)
In-Reply-To: <878teabyjb.fsf@gmail.com> (Mathieu Othacehe's message of "Sun, 10 Dec 2017 12:41:28 +0100")
Hello,
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
>>> This could be done by adding a cli argument for reconfigure or allowing
>>> an empty string in (grub-configuration (target "")).
>>>
>>> WDYT?
>>>
>
> An already available option would be to override the grub-installer like
> this :
>
> (define no-op-installer
> #~(lambda (bootloader device mount)
> (display "no op")))
>
> (bootloader (bootloader
> (inherit grub-bootloader)
> (installer no-op-installer))
We could even define and document it as ‘no-bootloader’ or something
like that.
> I admit this is not ideal, so I would propose two options :
>
> * Allow for target field to be #f and do not call the installer when
> this happends.
Sounds reasonable.
> * Precise the --no-bootloader parameter of guix system to deal with
> multiple cases, for example :
>
> --bootloader=[default|no-config-file|no-install|...]
>
> WDYT ?
What would it do in the ‘no-config-file’ case? Run ‘grub-install’ (or
similar) without regenerating ‘grub.cfg’? Does that make sense?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-12-11 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-09 23:35 Dualbooting with guixsd not handling grub installation Martin Castillo
2017-12-10 1:11 ` Jelle Licht
2017-12-10 11:41 ` Mathieu Othacehe
2017-12-11 9:39 ` Ludovic Courtès [this message]
2017-12-14 2:27 ` Martin Castillo
2017-12-15 14:53 ` Ludovic Courtès
2017-12-17 12:29 ` Oleg Pykhalov
2017-12-18 9:21 ` Ludovic Courtès
2018-02-01 6:14 ` Oleg Pykhalov
2018-02-01 8:06 ` Félicien Pillot
2018-02-02 22:34 ` Oleg Pykhalov
2018-02-05 13:15 ` Ludovic Courtès
2018-02-06 12:25 ` Oleg Pykhalov
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=87bmj54n8z.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=m.othacehe@gmail.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.