unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: 27007@debbugs.gnu.org
Subject: bug#27007: boot-parameters are not documented
Date: Sat, 20 May 2017 22:31:59 +0200	[thread overview]
Message-ID: <87wp9bl16o.fsf@gmail.com> (raw)
In-Reply-To: <20170520200015.7lkqfgp5pju3clvf@penguin.suse.cz>


Hi Tomáš,

> My question without answer is - how can I specify bootloader menu entries now?

You're right, you have to pass a <boot-parameters> now. The
documentation patch is still in review, you can find it here :

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26339#489

The example has been updated :

--8<---------------cut here---------------start------------->8---
 @example
-(menu-entry
+(boot-parameters
   (label "The Other Distro")
-  (linux "/boot/old/vmlinux-2.6.32")
-  (linux-arguments '("root=/dev/sda2"))
+  (root-device "my-root")
+  (boot-name 'grub)
+  (store-device "my-root")
+  (store-mount-point "/")
+  (kernel "/boot/old/vmlinux-2.6.32")
+  (kernel-arguments '("root=/dev/sda2"))
   (initrd "/boot/old/initrd"))
 @end example
--8<---------------cut here---------------end--------------->8---

It will maybe change again in the future, I'm not sure <boot-parameters>
are our best option here.

Anyway, let me now if it works for you.

Thanks,

Mathieu

  reply	other threads:[~2017-05-20 20:33 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 [this message]
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
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=87wp9bl16o.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=27007@debbugs.gnu.org \
    --cc=sleep_walker@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 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).