From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Dualbooting with guixsd not handling grub installation
Date: Tue, 06 Feb 2018 15:25:34 +0300 [thread overview]
Message-ID: <87k1vqnw3l.fsf@gmail.com> (raw)
In-Reply-To: <87mv0nd1bm.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 05 Feb 2018 14:15:57 +0100")
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> I think we should keep ‘menu-entry’ bootloader-independent.
What does mean “independent”? Do you mean that it's working only for
Grub now? I guess others bootloaders could have this if they need to
generate a configuration file like “/boot/grub/grub.cfg”.
> I’m actually not sure what problem we’re trying to solve: is it that
> the ‘root’ variable in GRUB gets set to the wrong partition when you
> try to dual-boot?
The problem is I cannot get a Grub “menu-entry” in “/boot/grub/grub.cfg”
which should look like:
--8<---------------cut here---------------start------------->8---
menuentry "Another distro" {
search --label --set another-disk-label
configfile /boot/grub/grub.cfg
}
--8<---------------cut here---------------end--------------->8---
Also “linux” and “initrd” fields of “menu-entry” are required to be
defined which prevents from generating the snippet above.
Thoughts?
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2018-02-06 12:25 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
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 [this message]
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=87k1vqnw3l.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
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.