From: "Tomáš Čech" <sleep_walker@gnu.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27007@debbugs.gnu.org
Subject: bug#27007: boot-parameters are not documented
Date: Tue, 23 May 2017 11:57:03 +0200 [thread overview]
Message-ID: <20170523095703.wvay4ganh4kynny3@penguin.suse.cz> (raw)
In-Reply-To: <86r2zfkjhb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
On Tue, May 23, 2017 at 11:31:12AM +0200, Mathieu Othacehe wrote:
>
>Hello,
>
>> So how does the ‘menu-entry’ example that Tomáš gave translate with this
>> new API? (Apologies for asking, I admit I haven’t fully adjusted to the
>> new API mentally. :-))
>
>Well it's still moving :)
>
>We can ask him but I guess something like that :
>
>--8<---------------cut here---------------start------------->8---
>(boot-parameters
> (label "openSUSE")
> (root-device #f)
> (boot-name 'grub)
> (store-device #f)
> (store-mount-point "/")
> (kernel "(hd0,msdos1)/vmlinuz")
> (kernel-arguments (list "root=/dev/penguin/opensuse" "init=/usr/lib/systemd/systemd"))
> (initrd "(hd0,msdos1)/initrd"))
>--8<---------------cut here---------------end--------------->8---
>
>Note that root-device, boot-name, store-device and store-mount-point are
>useless here.
I came with something similar:
(boot-parameters
(label "openSUSE")
(root-device "/dev/penguin/opensuse")
(boot-name 'grub)
(store-device "(hd0,msdos1)")
(store-mount-point "/")
(kernel "(hd0,msdos1)/vmlinuz")
(kernel-arguments '("root=/dev/penguin/opensuse"
"init=/usr/lib/systemd/systemd"))
(initrd "(hd0,msdos1)/initrd"))))))
Unfortunately useless entries were still required (I didn't have that
idea with setting them to #f).
I couldn't verify the result configuration yet as I'm facing another,
unrelated problem.
Thanks,
S_W
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-23 9:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 20:00 bug#27007: boot-parameters are not documented Tomáš Čech
2017-05-20 20:31 ` Mathieu Othacehe
2017-05-20 21:07 ` Leo Famulari
2017-05-20 21:43 ` Tomáš Čech
2017-05-20 20:52 ` Danny Milosavljevic
2017-05-20 21:00 ` Tomáš Čech
2017-05-22 15:55 ` Ludovic Courtès
2017-05-22 17:31 ` Mathieu Othacehe
2017-05-23 8:13 ` Ludovic Courtès
2017-05-23 9:31 ` Mathieu Othacehe
2017-05-23 9:57 ` Tomáš Čech [this message]
2017-05-23 11:23 ` Ludovic Courtès
2017-05-23 11:40 ` Mathieu Othacehe
2017-05-23 12:24 ` Ludovic Courtès
2017-05-31 7:23 ` bug#27007: [PATCH 0/2] Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-05-31 7:23 ` bug#27007: [PATCH 1/2] bootloader: " Mathieu Othacehe
2017-05-31 22:11 ` Danny Milosavljevic
2017-06-01 8:34 ` Mathieu Othacehe
2017-06-01 11:14 ` Danny Milosavljevic
2017-06-02 9:29 ` Mathieu Othacehe
2017-06-02 14:30 ` Marius Bakke
2017-06-01 11:22 ` Ludovic Courtès
2017-06-05 10:23 ` Ludovic Courtès
2017-06-06 8:14 ` Mathieu Othacehe
2017-05-31 7:23 ` bug#27007: [PATCH 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-05-31 21:57 ` Danny Milosavljevic
2017-06-05 10:38 ` Ludovic Courtès
2017-06-05 10:36 ` Ludovic Courtès
2017-06-05 14:11 ` Danny Milosavljevic
2017-06-06 22:51 ` Ludovic Courtès
2017-06-08 10:59 ` Mathieu Othacehe
2017-06-06 9:20 ` Mathieu Othacehe
2017-05-24 20:11 ` bug#27007: boot-parameters are not documented Danny Milosavljevic
2017-05-26 8:47 ` Ludovic Courtès
2017-05-26 9:03 ` ng0
2017-06-08 10:57 ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-06-08 10:57 ` bug#27007: [PATCH v2 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-06-08 12:39 ` Ludovic Courtès
2017-06-08 14:33 ` Mathieu Othacehe
2017-06-08 12:36 ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries Ludovic Courtès
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=20170523095703.wvay4ganh4kynny3@penguin.suse.cz \
--to=sleep_walker@gnu.org \
--cc=27007@debbugs.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).