From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27007@debbugs.gnu.org
Subject: bug#27007: [PATCH 2/2] doc: Adapt to multiple bootloader support.
Date: Mon, 05 Jun 2017 12:36:28 +0200 [thread overview]
Message-ID: <87zidmd8lv.fsf@gnu.org> (raw)
In-Reply-To: <20170531072328.16116-3-m.othacehe@gmail.com> (Mathieu Othacehe's message of "Wed, 31 May 2017 09:23:28 +0200")
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
> * doc/guix.texi (GRUB configuration): Rename to "Bootloader
> configuration".
> Adapt occurences of "GRUB" in other sections.
Awesome, thanks for reviewing and updating all the doc!
Some minor comments/suggestions:
> -@node GRUB Configuration
> -@subsection GRUB Configuration
> +@node Bootloader Configuration
> +@subsection Bootloader Configuration
>
> -@cindex GRUB
> +@cindex Bootloader
Lowercase please.
> +The operating system supports multiple bootloaders. The bootloader is
> +configured using @code{bootloader-configuration} declaration. All the
> +fields of this structure are bootloader agnostic except for one field,
> +@code{bootloader} that indicates the bootloader to be configured and
> +installed.
Nitpick: please make sure to leave two spaces after an end-of-sentence
period.
> @c FIXME: Write documentation once it's stable.
> -Themes are created using the @code{grub-theme} form, which is not
> -documented yet.
> +Fow now only GRUB has theme support. GRUB Themes are created using
s/Themes/themes/
> +It also adds a bootloader menu entry for the new OS configuration,
> +---unless @option{--no-bootloader} is passed. For GRUB, it moves
> +entries for older configurations to a submenu.
s/to a submenu/to a submenu, allowing you to choose an older system
generation at boot time should you need it/
What happens with other bootloaders? Do we get older boot entries? It
might be worth mentioning.
> @item switch-generation
> @cindex generations
> Switch to an existing system generation. This action atomically
> -switches the system profile to the specified system generation. It also
> -rearranges the system's existing GRUB menu entries. It makes the menu
> -entry for the specified system generation the default, and it moves the
> -entries for the other generations to a submenu. The next time the
> -system boots, it will use the specified system generation.
> +switches the system profile to the specified system generation. It
> +also rearranges the system's existing bootloader menu entries. It
> +makes the menu entry for the specified system generation the default,
> +and it moves the entries for the other generations to a submenu. The
> +next time the system boots, it will use the specified system
> +generation.
What happens to the bootloader itself? Does it change the bootloader to
the one that was chosen back then?
Thank you!
Ludo’.
next prev parent reply other threads:[~2017-06-05 10:37 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
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 [this message]
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=87zidmd8lv.fsf@gnu.org \
--to=ludo@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).