public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matěj Laitl" <matej@laitl.cz>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] dev/scarabeus:master commit in: docs/
Date: Tue, 11 Oct 2011 19:35:58 +0000 (UTC)	[thread overview]
Message-ID: <721f29eb03e1d4f4fe88e09964ebe383cc0d27ea.matej@gentoo> (raw)

commit:     721f29eb03e1d4f4fe88e09964ebe383cc0d27ea
Author:     Matěj Laitl <matej <AT> laitl <DOT> cz>
AuthorDate: Tue Oct 11 19:14:35 2011 +0000
Commit:     Matěj Laitl <matej <AT> laitl <DOT> cz>
CommitDate: Tue Oct 11 19:14:35 2011 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=dev/scarabeus.git;a=commit;h=721f29eb

GRUB 2 Guide: move 'Pre-Configuring GRUB 2 to use EFI' section where it chronologically belongs

---
 docs/grub-2-guide.xml |  128 ++++++++++++++++++++++++------------------------
 1 files changed, 64 insertions(+), 64 deletions(-)

diff --git a/docs/grub-2-guide.xml b/docs/grub-2-guide.xml
index a28bea3..a0d1e8f 100644
--- a/docs/grub-2-guide.xml
+++ b/docs/grub-2-guide.xml
@@ -177,70 +177,7 @@ failed.
 </section>
 
 <section>
-<title>Configuring GRUB 2</title>
-<body>
-
-<impo>
-Gentoo installs all grub commands renamed to grub2. So if you read any other guide you
-should replace all grub mentions with grub2 <i>(grub-mkconfig -> grub2-mkconfig)</i>.
-</impo>
-
-<p>
-Compared to GRUB Legacy, GRUB 2 uses automatic generation to generate
-all the required entries for you to boot. This is handled by <i>grub2-mkconfig</i>
-command that probes your system for all the required data. Cooperating with
-<i>sys-boot/os-prober</i>, it detects even other OSes on all disks.
-</p>
-
-<impo>
-If you updated from GRUB Legacy then your <path>/boot/grub/menu.lst</path>
-was converted to <path>/boot/grub2/grub.cfg</path> to ensure that your system
-can boot even if you forget to generate the config. Never the less you should
-take time and migrate the configuration to be automatically generated, because
-next time GRUB 2 is installed it will use automatic generation and ignore
-GRUB Legacy files.
-</impo>
-
-<pre caption="Generating the GRUB 2 config">
-grub2-mkconfig -o /boot/grub2/grub.cfg
-</pre>
-
-<p>
-Tweaking the options is to be done in the <path>/etc/defaults/grub</path> file.
-Simple text file configuration with description of some default values.
-All the options are described in grub2 info pages.
-</p>
-
-<note>
-This file is created by Gentoo and if you find an interesting option not used
-in there just open a bugreport (possibly with a patch).
-</note>
-
-<p>
-Sometimes, if automatic detection of GRUB 2 does not suffice, the file <path>
-/etc/grub.d/40_custom</path> should be used to store custom entries. Full
-description how to configure such with examples can be found in grub2 info
-pages.
-</p>
-
-<pre caption="Custom menu entry">
-menuentry "My Shiny Gentoo Kernel" {
-	set root=(hd0,1)
-	search --no-floppy --fs-uuid --set &lt;UUID&gt;
-	linux /boot/gentookernel-5.3.2-generic root=UUID=&lt;UUID&gt;
-	initrd /boot/initrd.img-5.3.2
-}
-</pre>
-
-<warn>
-Remember to replace the <i>&lt;UUID&gt;</i> with your device UUID.
-</warn>
-
-</body>
-</section>
-
-<section>
-<title>Pre-Configuring GRUB 2 to use EFI</title>
+<title>Variant B: Pre-Configuring GRUB 2 to use EFI</title>
 <body>
 
 <p>
@@ -356,6 +293,69 @@ configuration.
 </section>
 
 <section>
+<title>Configuring GRUB 2</title>
+<body>
+
+<impo>
+Gentoo installs all grub commands renamed to grub2. So if you read any other guide you
+should replace all grub mentions with grub2 <i>(grub-mkconfig -> grub2-mkconfig)</i>.
+</impo>
+
+<p>
+Compared to GRUB Legacy, GRUB 2 uses automatic generation to generate
+all the required entries for you to boot. This is handled by <i>grub2-mkconfig</i>
+command that probes your system for all the required data. Cooperating with
+<i>sys-boot/os-prober</i>, it detects even other OSes on all disks.
+</p>
+
+<impo>
+If you updated from GRUB Legacy then your <path>/boot/grub/menu.lst</path>
+was converted to <path>/boot/grub2/grub.cfg</path> to ensure that your system
+can boot even if you forget to generate the config. Never the less you should
+take time and migrate the configuration to be automatically generated, because
+next time GRUB 2 is installed it will use automatic generation and ignore
+GRUB Legacy files.
+</impo>
+
+<pre caption="Generating the GRUB 2 config">
+grub2-mkconfig -o /boot/grub2/grub.cfg
+</pre>
+
+<p>
+Tweaking the options is to be done in the <path>/etc/defaults/grub</path> file.
+Simple text file configuration with description of some default values.
+All the options are described in grub2 info pages.
+</p>
+
+<note>
+This file is created by Gentoo and if you find an interesting option not used
+in there just open a bugreport (possibly with a patch).
+</note>
+
+<p>
+Sometimes, if automatic detection of GRUB 2 does not suffice, the file <path>
+/etc/grub.d/40_custom</path> should be used to store custom entries. Full
+description how to configure such with examples can be found in grub2 info
+pages.
+</p>
+
+<pre caption="Custom menu entry">
+menuentry "My Shiny Gentoo Kernel" {
+	set root=(hd0,1)
+	search --no-floppy --fs-uuid --set &lt;UUID&gt;
+	linux /boot/gentookernel-5.3.2-generic root=UUID=&lt;UUID&gt;
+	initrd /boot/initrd.img-5.3.2
+}
+</pre>
+
+<warn>
+Remember to replace the <i>&lt;UUID&gt;</i> with your device UUID.
+</warn>
+
+</body>
+</section>
+
+<section>
 <title>Configuring with LVM</title>
 <body>
 



             reply	other threads:[~2011-10-11 19:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 19:35 Matěj Laitl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-11-02 12:30 [gentoo-commits] dev/scarabeus:master commit in: docs/ Matěj Laitl
2011-10-23 19:49 Matěj Laitl
2011-10-23 17:45 Matěj Laitl
2011-10-11 22:06 Matěj Laitl
2011-10-11 22:06 Matěj Laitl
2011-10-11 19:35 Matěj Laitl
2011-10-11 19:35 Matěj Laitl
2011-10-11 19:35 Matěj Laitl
2011-10-11  7:45 Tomas Chvatal
2011-09-30 12:13 Tomas Chvatal

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=721f29eb03e1d4f4fe88e09964ebe383cc0d27ea.matej@gentoo \
    --to=matej@laitl.cz \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox