* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2009-09-24 20:26 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2009-09-24 20:26 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 09/09/24 20:26:50
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Added real_rootflags info to the handbook. bug 273803. thanks to mpagano for the patch
Revision Changes Path
1.14 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.14&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.14&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.13&r2=1.14
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- hb-install-x86+amd64-bootloader.xml 15 Apr 2009 07:23:57 -0000 1.13
+++ hb-install-x86+amd64-bootloader.xml 24 Sep 2009 20:26:50 -0000 1.14
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.13 2009/04/15 07:23:57 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.14 2009/09/24 20:26:50 nightmorph Exp $ -->
<sections>
-<version>6.3</version>
-<date>2009-04-15</date>
+<version>6.4</version>
+<date>2009-09-24</date>
<section>
<title>Making your Choice</title>
@@ -346,6 +346,13 @@
</p>
<p>
+If your bootloader configuration file contains the real_root parameter use the
+rootflags parameter to set root filesystem mount options. In the case where
+real_root defines the root mount point, the real_rootflags parameter should be
+used.
+</p>
+
+<p>
If you're using a 2.6.7 or higher kernel and you jumpered your harddrive
because the BIOS can't handle large harddrives you'll need to append
<c>sda=stroke</c>. Replace sda with the device that requires this option.
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2014-08-17 16:18 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2014-08-17 16:18 UTC (permalink / raw
To: gentoo-doc-cvs
swift 14/08/17 16:18:31
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #519920 - Drop framebuffer information, it is complicated and outdated
Revision Changes Path
1.40 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.40&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.40&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.39&r2=1.40
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- hb-install-x86+amd64-bootloader.xml 31 Dec 2013 20:29:23 -0000 1.39
+++ hb-install-x86+amd64-bootloader.xml 17 Aug 2014 16:18:31 -0000 1.40
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.39 2013/12/31 20:29:23 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.40 2014/08/17 16:18:31 swift Exp $ -->
<sections>
-<version>23</version>
-<date>2013-12-31</date>
+<version>24</version>
+<date>2014-08-17</date>
<section>
<title>Making your Choice</title>
@@ -26,6 +26,7 @@
</body>
<body test="contains('AMD64 x86', func:keyval('arch'))">
+
<p>
For <keyval id="arch"/>, Gentoo Linux provides <uri
link="#grub2">GRUB2</uri>, <uri link="#lilo">LILO</uri> and
@@ -33,88 +34,12 @@
</p>
</body>
-<body>
-<p>
-But before we install the bootloader, we inform you how to configure
-framebuffer (assuming you want it of course). With framebuffer you can run the
-Linux command line with (limited) graphical features (such as using the nice
-bootsplash image Gentoo provides).
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>Optional: Framebuffer</title>
-<body>
-
-<p>
-<e>If</e> you have configured your kernel with framebuffer support (or you used
-<c>genkernel</c> default kernel configuration), you can activate it by adding a
-a <c>video</c> statement to your bootloader configuration file.
-</p>
-
-<p>
-First of all, you need to know your framebuffer device. You should have used
-<c>uvesafb</c> as the <e>VESA driver</e>.
-</p>
+<body test="contains('IA64', func:keyval('arch'))">
<p>
-The <c>video</c> statement controls framebuffer display options. It needs to be
-given the framebuffer driver followed by the control statements you wish to
-enable. All variables are listed in
-<path>/usr/src/linux/Documentation/fb/uvesafb.txt</path>. The most-used options
-are:
-</p>
-
-<table>
-<tr>
- <th>Control</th>
- <th>Description</th>
-</tr>
-<tr>
- <ti>ywrap</ti>
- <ti>
- Assume that the graphical card can wrap around its memory (i.e. continue at
- the beginning when it has approached the end)
- </ti>
-</tr>
-<tr>
- <ti>mtrr:<c>n</c></ti>
- <ti>
- Setup MTRR registers. <c>n</c> can be:<br/>
- 0 - disabled<br/>
- 1 - uncachable<br/>
- 2 - write-back<br/>
- 3 - write-combining<br/>
- 4 - write-through
- </ti>
-</tr>
-<tr>
- <ti><c>mode</c></ti>
- <ti>
- Set up the resolution, color depth and refresh rate. For instance,
- <c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a
- refresh rate of 85 Hz.
- </ti>
-</tr>
-</table>
-
-<p>
-The result could be something like
-<c>video=uvesafb:mtrr:3,ywrap,1024x768-32@85</c>. Write this setting down; you
-will need it shortly.
-</p>
-
-<p test="func:keyval('arch')='IA64'">
Now, you should install the <uri link="#elilo">elilo bootloader</uri>.
</p>
-<p test="not(func:keyval('arch')='IA64')">
-Now continue by installing <uri link="#grub">GRUB</uri>, <uri
-link="#grub2">GRUB2</uri> <e>or</e> <uri
-link="#lilo">LILO</uri>.
-</p>
-
</body>
</subsection>
</section>
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-12-31 20:29 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-12-31 20:29 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/12/31 20:29:23
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #496558 - make partitioning more consistent, add note about "strange" partitions in example with dualboot
Revision Changes Path
1.39 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.39&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.39&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.38&r2=1.39
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- hb-install-x86+amd64-bootloader.xml 18 Dec 2013 10:13:54 -0000 1.38
+++ hb-install-x86+amd64-bootloader.xml 31 Dec 2013 20:29:23 -0000 1.39
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.38 2013/12/18 10:13:54 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.39 2013/12/31 20:29:23 swift Exp $ -->
<sections>
-<version>22</version>
-<date>2013-12-18</date>
+<version>23</version>
+<date>2013-12-31</date>
<section>
<title>Making your Choice</title>
@@ -433,6 +433,14 @@
line since JFS needs to replay its log before it allows read-write mounting.
</note>
+<note>
+If dualboot with Windows is used, the partitioning example used in this
+book will not be sufficient (our example uses all four primary partitions
+for Linux, whereas at least one would need to be extended if Windows is
+installed on a logical partition). Please proceed with caution and consider
+the listing to be an example that needs to be modified to suit your own needs.
+</note>
+
<pre caption="Example grub.conf">
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment>
default 0
@@ -445,12 +453,12 @@
title Gentoo Linux <keyval id="kernel-version"/>
<comment># Partition where the kernel image (or operating system) is located</comment>
root (hd0,1)
-kernel /boot/<keyval id="kernel-name"/> root=/dev/sda3
+kernel /boot/<keyval id="kernel-name"/> root=/dev/sda4
title Gentoo Linux <keyval id="kernel-version"/> (rescue)
<comment># Partition where the kernel image (or operating system) is located</comment>
root (hd0,1)
-kernel /boot/<keyval id="kernel-name"/> root=/dev/sda3 init=/bin/bb
+kernel /boot/<keyval id="kernel-name"/> root=/dev/sda4 init=/bin/bb
<comment># The next four lines are only if you dualboot with a Windows system.</comment>
<comment># In this case, Windows is hosted on /dev/sda6.</comment>
@@ -469,7 +477,7 @@
<pre caption="GRUB snippet for initramfs-enabled kernel builds">
title Gentoo Linux <keyval id="kernel-version"/>
root (hd0,1)
-kernel /boot/<keyval id="kernel-version"/> <i>real_</i>root=/dev/sda3
+kernel /boot/<keyval id="kernel-version"/> <i>real_</i>root=/dev/sda4
<i>initrd /boot/<keyval id="genkernel-initrd"/></i>
</pre>
@@ -494,7 +502,7 @@
<p>
If you need to pass any additional options to the kernel, simply add them to the
end of the kernel command. We're already passing one option
-(<c>root=/dev/sda3</c> or <c>real_root=/dev/sda3</c>), but you can pass others
+(<c>root=/dev/sda4</c> or <c>real_root=/dev/sda4</c>), but you can pass others
as well, such as the <c>video</c> statement for framebuffer as we discussed
previously.
</p>
@@ -637,7 +645,7 @@
If you want to install GRUB in a certain partition instead of the MBR,
you have to alter the <c>setup</c> command so it points to the right
partition. For instance, if you want GRUB installed in
-<path>/dev/sda4</path>, then the command becomes <c>setup (hd0,4)</c>.
+<path>/dev/sda4</path>, then the command becomes <c>setup (hd0,3)</c>.
Few users however want to do this.
</note>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-12-18 7:38 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-12-18 7:38 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/12/18 07:38:48
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #494526 - GRUB Legacy is an alternative, not optional
Revision Changes Path
1.37 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.37&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.37&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.36&r2=1.37
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:58:38 -0000 1.36
+++ hb-install-x86+amd64-bootloader.xml 18 Dec 2013 07:38:48 -0000 1.37
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.36 2013/12/17 11:58:38 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.37 2013/12/18 07:38:48 swift Exp $ -->
<sections>
-<version>20</version>
-<date>2013-12-17</date>
+<version>21</version>
+<date>2013-12-18</date>
<section>
<title>Making your Choice</title>
@@ -335,7 +335,7 @@
</subsection>
</section>
<section id="grub" test="contains('AMD64 x86',func:keyval('arch'))">
-<title>Optional: Using GRUB Legacy</title>
+<title>Alternative: Using GRUB Legacy</title>
<subsection>
<title>What is Legacy?</title>
<body>
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-12-17 11:58 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-12-17 11:58 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/12/17 11:58:38
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #494526 - GRUB2 is now stable
Revision Changes Path
1.36 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.36&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.36&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.35&r2=1.36
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:55:40 -0000 1.35
+++ hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:58:38 -0000 1.36
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.35 2013/12/17 11:55:40 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.36 2013/12/17 11:58:38 swift Exp $ -->
<sections>
-<version>19</version>
+<version>20</version>
<date>2013-12-17</date>
<section>
@@ -28,16 +28,10 @@
<body test="contains('AMD64 x86', func:keyval('arch'))">
<p>
For <keyval id="arch"/>, Gentoo Linux provides <uri
-link="#grub">GRUB</uri>, <uri link="#grub2">GRUB2</uri> and
-<uri link="#lilo">LILO</uri>.
+link="#grub2">GRUB2</uri>, <uri link="#lilo">LILO</uri> and
+<uri link="#grub">GRUB Legacy</uri>.
</p>
-<note>
-GRUB2 might not be stabilized at the moment of reading this. However,
-stabilization is due very soon so we temporarily document both GRUB and GRUB2
-and will remove the GRUB instructions after stabilization of GRUB2.
-</note>
-
</body>
<body>
<p>
@@ -131,24 +125,11 @@
<body>
<p>
-GRUB2 is provided through the <c>sys-boot/grub</c> package. To deploy GRUB2, use
-the <e>SLOT</e> notation to tell Portage to install GRUB2. SLOTs are a feature
-of Gentoo Linux where multiple versions of the same package can be deployed
-simultaneously on a system. In our case, this means that GRUB Legacy and GRUB2
-can be installed on a system (software-wise) at the same time.
+GRUB2 is provided through the <c>sys-boot/grub</c> package.
</p>
-<note>
-GRUB2 might still be marked as ~<keyval id="arch" />. If that is the case, you
-can either wait and use <uri link="#grub">GRUB Legacy</uri> or unmask the
-package. This is explained in <uri
-link="handbook-amd64.xml?part=3&chap=3#doc_chap2">Mixing Stable with
-Testing</uri>. Once GRUB2 is stabilized, the SLOT operator also is no longer
-mandatory.
-</note>
-
<pre caption="Installing GRUB2">
-# <i>emerge sys-boot/grub:2</i>
+# <i>emerge sys-boot/grub</i>
</pre>
<p>
@@ -365,14 +346,6 @@
version is now dubbed as "GRUB Legacy".
</p>
-<p>
-We recommend to start with GRUB2 as soon as it is available. The migration of
-GRUB to GRUB2 is <uri link="https://wiki.gentoo.org/wiki/GRUB2_Migration">documented
-online</uri>. The instructions in this section relate to "GRUB Legacy" and will
-disappear from the book soon after the stabilization of <uri
-link="#grub2">GRUB2</uri>.
-</p>
-
</body>
</subsection>
<subsection>
@@ -417,7 +390,7 @@
<body>
<p>
-To install GRUB, let's first emerge it:
+To install GRUB Legacy, let's first emerge it:
</p>
<impo test="func:keyval('arch')='AMD64'">
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-12-17 11:55 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-12-17 11:55 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/12/17 11:55:40
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Move GRUB2 as default, mark GRUB Legacy as optional. Shuffle the sections to ordering is more logical. No content change otherwise
Revision Changes Path
1.35 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.35&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.35&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.34&r2=1.35
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:04:50 -0000 1.34
+++ hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:55:40 -0000 1.35
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.34 2013/12/17 11:04:50 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.35 2013/12/17 11:55:40 swift Exp $ -->
<sections>
-<version>18</version>
+<version>19</version>
<date>2013-12-17</date>
<section>
@@ -124,8 +124,237 @@
</body>
</subsection>
</section>
+<section id="grub2" test="contains('AMD64 x86', func:keyval('arch'))">
+<title>Default: Using GRUB2</title>
+<subsection>
+<title>Installing GRUB2</title>
+<body>
+
+<p>
+GRUB2 is provided through the <c>sys-boot/grub</c> package. To deploy GRUB2, use
+the <e>SLOT</e> notation to tell Portage to install GRUB2. SLOTs are a feature
+of Gentoo Linux where multiple versions of the same package can be deployed
+simultaneously on a system. In our case, this means that GRUB Legacy and GRUB2
+can be installed on a system (software-wise) at the same time.
+</p>
+
+<note>
+GRUB2 might still be marked as ~<keyval id="arch" />. If that is the case, you
+can either wait and use <uri link="#grub">GRUB Legacy</uri> or unmask the
+package. This is explained in <uri
+link="handbook-amd64.xml?part=3&chap=3#doc_chap2">Mixing Stable with
+Testing</uri>. Once GRUB2 is stabilized, the SLOT operator also is no longer
+mandatory.
+</note>
+
+<pre caption="Installing GRUB2">
+# <i>emerge sys-boot/grub:2</i>
+</pre>
+
+<p>
+The GRUB2 software is now installed on the system, but not activated yet.
+</p>
+
+</body>
+</subsection>
+<subsection>
+<title>Configuring GRUB2</title>
+<body>
+
+<p>
+First, let us install the necessary GRUB2 files in <path>/boot/grub</path>.
+Assuming the first disk (the one where the system boots from) is
+<path>/dev/sda</path>, the following command will do this for us:
+</p>
+
+<pre caption="Installing the GRUB2 files in /boot/grub">
+# <i>grub2-install /dev/sda</i>
+</pre>
+
+<p>
+Next, we can generate the GRUB2 configuration based on the user configuration
+specified in the <path>/etc/default/grub</path> file and
+<path>/etc/grub.d</path> scripts. In most cases, no configuration is needed
+by users as GRUB2 will automatically detect which kernel to boot (the highest
+one available in <path>/boot</path>) and what the root file system is.
+</p>
+
+<p>
+To generate the final GRUB2 configuration, run the <c>grub2-mkconfig</c>
+command:
+</p>
+
+<pre caption="Generating GRUB2 configuration">
+# <i>grub2-mkconfig -o /boot/grub/grub.cfg</i>
+Generating grub.cfg ...
+Found linux image: /boot/<keyval id="kernel-name" />
+Found initrd image: /boot/<keyval id="genkernel-initrd" />
+done
+</pre>
+
+<p>
+The output of the command <e>must</e> mention that at least one Linux image is
+found, as those are needed to boot the system. If you use initramfs or used
+<c>genkernel</c> to build the kernel, the correct initrd image should be
+detected as well. If this is not the case, go to <path>/boot</path> and check
+the contents using the <c>ls</c> command. If the files are indeed missing, go
+back to the kernel configuration and installation instructions.
+</p>
+
+</body>
+</subsection>
+</section>
+<section id="lilo" test="contains('AMD64 x86', func:keyval('arch'))">
+<title>Alternative: Using LILO</title>
+<subsection>
+<title>Installing LILO</title>
+<body>
+
+<p>
+LILO, the LInuxLOader, is the tried and true workhorse of Linux
+bootloaders. However, it lacks some features that GRUB has (which is
+also the reason why GRUB is currently gaining popularity). The reason
+why LILO is still used is that, on some systems, GRUB doesn't work and
+LILO does. Of course, it is also used because some people know LILO and
+want to stick with it. Either way, Gentoo supports both, and apparently
+you have chosen to use LILO.
+</p>
+
+<p>
+Installing LILO is a breeze; just use <c>emerge</c>.
+</p>
+
+<pre caption="Installing LILO">
+# <i>emerge lilo</i>
+</pre>
+
+</body>
+</subsection>
+<subsection>
+<title>Configuring LILO</title>
+<body>
+
+<p>
+To configure LILO, you must create <path>/etc/lilo.conf</path>. Fire up
+your favorite editor (in this handbook we use <c>nano</c> for
+consistency) and create the file.
+</p>
+
+<pre caption="Creating /etc/lilo.conf">
+# <i>nano -w /etc/lilo.conf</i>
+</pre>
+
+<p>
+Some sections ago we have asked you to remember the kernel-image name
+you have created. In the next example <path>lilo.conf</path> we use the
+example partitioning scheme.
+</p>
+
+<p>
+Make sure you use <e>your</e> kernel image filename and, if appropriate,
+<e>your</e> initrd image filename.
+</p>
+
+<note>
+If your root filesystem is JFS, you <e>must</e> add a <c>append="ro"</c>
+line after each boot item since JFS needs to replay its log before it allows
+read-write mounting.
+</note>
+
+<pre caption="Example /etc/lilo.conf">
+boot=/dev/sda <comment># Install LILO in the MBR</comment>
+prompt <comment># Give the user the chance to select another section</comment>
+timeout=50 <comment># Wait 5 (five) seconds before booting the default section</comment>
+default=gentoo <comment># When the timeout has passed, boot the "gentoo" section</comment>
+
+image=/boot/<keyval id="kernel-name"/>
+ label=gentoo <comment># Name we give to this section</comment>
+ read-only <comment># Start with a read-only root. Do not alter!</comment>
+ root=/dev/sda3 <comment># Location of the root filesystem</comment>
+
+image=/boot/<keyval id="kernel-name"/>
+ label=gentoo.rescue <comment># Name we give to this section</comment>
+ read-only <comment># Start with a read-only root. Do not alter!</comment>
+ root=/dev/sda3 <comment># Location of the root filesystem</comment>
+ append="init=/bin/bb" <comment># Launch the Gentoo static rescue shell</comment>
+
+<comment># The next two lines are only if you dualboot with a Windows system.</comment>
+<comment># In this case, Windows is hosted on /dev/sda6.</comment>
+other=/dev/sda6
+ label=windows
+</pre>
+
+<note>
+If you use a different partitioning scheme and/or kernel image, adjust
+accordingly.
+</note>
+
+<p>
+If, while building the Linux kernel, you opted to include an initramfs to boot
+from, then you will need to change the configuration by referring to this
+initramfs file and telling the initramfs where your real root device is at:
+</p>
+
+<pre caption="LILO snippet for initramfs-enabled kernel builds">
+image=/boot/<keyval id="kernel-name"/>
+ label=gentoo
+ read-only
+ <i>append="real_root=/dev/sda3"</i>
+ <i>initrd=/boot/<keyval id="genkernel-initrd" /></i>
+</pre>
+
+<p>
+If you need to pass any additional options to the kernel, add an
+<c>append</c> statement to the section. As an example, we add the
+<c>video</c> statement to enable framebuffer:
+</p>
+
+<pre caption="Using append to add kernel options">
+image=/boot/<keyval id="kernel-name"/>
+ label=gentoo
+ read-only
+ root=/dev/sda3
+ <i>append="video=uvesafb:mtrr,ywrap,1024x768-32@85"</i>
+</pre>
+
+<p>
+If you're using a 2.6.7 or higher kernel and you jumpered your harddrive
+because the BIOS can't handle large harddrives you'll need to append
+<c>sda=stroke</c>. Replace sda with the device that requires this option.
+</p>
+
+<p>
+<c>genkernel</c> users should know that their kernels use the same boot options
+as is used for the Installation CD. For instance, if you have SCSI devices, you
+should add <c>doscsi</c> as kernel option.
+</p>
+
+<p>
+Now save the file and exit. To finish up, you have to run <c>/sbin/lilo</c> so
+LILO can apply the <path>/etc/lilo.conf</path> to your system (i.e. install
+itself on the disk). Keep in mind that you'll also have to run
+<c>/sbin/lilo</c> every time you install a new kernel or make any changes to
+the menu.
+</p>
+
+<pre caption="Finishing the LILO installation">
+# <i>/sbin/lilo</i>
+</pre>
+
+<p>
+If you have more questions regarding LILO, please consult its <uri
+link="http://en.wikipedia.org/wiki/LILO_(boot_loader)">wikipedia page</uri>.
+</p>
+
+<p>
+You can now continue with <uri link="#reboot">Rebooting the System</uri>.
+</p>
+
+</body>
+</subsection>
+</section>
<section id="grub" test="contains('AMD64 x86',func:keyval('arch'))">
-<title>Default: Using GRUB Legacy</title>
+<title>Optional: Using GRUB Legacy</title>
<subsection>
<title>What is Legacy?</title>
<body>
@@ -453,235 +682,7 @@
</body>
</subsection>
</section>
-<section id="lilo" test="contains('AMD64 x86', func:keyval('arch'))">
-<title>Alternative: Using LILO</title>
-<subsection>
-<title>Installing LILO</title>
-<body>
-
-<p>
-LILO, the LInuxLOader, is the tried and true workhorse of Linux
-bootloaders. However, it lacks some features that GRUB has (which is
-also the reason why GRUB is currently gaining popularity). The reason
-why LILO is still used is that, on some systems, GRUB doesn't work and
-LILO does. Of course, it is also used because some people know LILO and
-want to stick with it. Either way, Gentoo supports both, and apparently
-you have chosen to use LILO.
-</p>
-
-<p>
-Installing LILO is a breeze; just use <c>emerge</c>.
-</p>
-
-<pre caption="Installing LILO">
-# <i>emerge lilo</i>
-</pre>
-
-</body>
-</subsection>
-<subsection>
-<title>Configuring LILO</title>
-<body>
-
-<p>
-To configure LILO, you must create <path>/etc/lilo.conf</path>. Fire up
-your favorite editor (in this handbook we use <c>nano</c> for
-consistency) and create the file.
-</p>
-
-<pre caption="Creating /etc/lilo.conf">
-# <i>nano -w /etc/lilo.conf</i>
-</pre>
-
-<p>
-Some sections ago we have asked you to remember the kernel-image name
-you have created. In the next example <path>lilo.conf</path> we use the
-example partitioning scheme.
-</p>
-
-<p>
-Make sure you use <e>your</e> kernel image filename and, if appropriate,
-<e>your</e> initrd image filename.
-</p>
-
-<note>
-If your root filesystem is JFS, you <e>must</e> add a <c>append="ro"</c>
-line after each boot item since JFS needs to replay its log before it allows
-read-write mounting.
-</note>
-
-<pre caption="Example /etc/lilo.conf">
-boot=/dev/sda <comment># Install LILO in the MBR</comment>
-prompt <comment># Give the user the chance to select another section</comment>
-timeout=50 <comment># Wait 5 (five) seconds before booting the default section</comment>
-default=gentoo <comment># When the timeout has passed, boot the "gentoo" section</comment>
-image=/boot/<keyval id="kernel-name"/>
- label=gentoo <comment># Name we give to this section</comment>
- read-only <comment># Start with a read-only root. Do not alter!</comment>
- root=/dev/sda3 <comment># Location of the root filesystem</comment>
-
-image=/boot/<keyval id="kernel-name"/>
- label=gentoo.rescue <comment># Name we give to this section</comment>
- read-only <comment># Start with a read-only root. Do not alter!</comment>
- root=/dev/sda3 <comment># Location of the root filesystem</comment>
- append="init=/bin/bb" <comment># Launch the Gentoo static rescue shell</comment>
-
-<comment># The next two lines are only if you dualboot with a Windows system.</comment>
-<comment># In this case, Windows is hosted on /dev/sda6.</comment>
-other=/dev/sda6
- label=windows
-</pre>
-
-<note>
-If you use a different partitioning scheme and/or kernel image, adjust
-accordingly.
-</note>
-
-<p>
-If, while building the Linux kernel, you opted to include an initramfs to boot
-from, then you will need to change the configuration by referring to this
-initramfs file and telling the initramfs where your real root device is at:
-</p>
-
-<pre caption="LILO snippet for initramfs-enabled kernel builds">
-image=/boot/<keyval id="kernel-name"/>
- label=gentoo
- read-only
- <i>append="real_root=/dev/sda3"</i>
- <i>initrd=/boot/<keyval id="genkernel-initrd" /></i>
-</pre>
-
-<p>
-If you need to pass any additional options to the kernel, add an
-<c>append</c> statement to the section. As an example, we add the
-<c>video</c> statement to enable framebuffer:
-</p>
-
-<pre caption="Using append to add kernel options">
-image=/boot/<keyval id="kernel-name"/>
- label=gentoo
- read-only
- root=/dev/sda3
- <i>append="video=uvesafb:mtrr,ywrap,1024x768-32@85"</i>
-</pre>
-
-<p>
-If you're using a 2.6.7 or higher kernel and you jumpered your harddrive
-because the BIOS can't handle large harddrives you'll need to append
-<c>sda=stroke</c>. Replace sda with the device that requires this option.
-</p>
-
-<p>
-<c>genkernel</c> users should know that their kernels use the same boot options
-as is used for the Installation CD. For instance, if you have SCSI devices, you
-should add <c>doscsi</c> as kernel option.
-</p>
-
-<p>
-Now save the file and exit. To finish up, you have to run <c>/sbin/lilo</c> so
-LILO can apply the <path>/etc/lilo.conf</path> to your system (i.e. install
-itself on the disk). Keep in mind that you'll also have to run
-<c>/sbin/lilo</c> every time you install a new kernel or make any changes to
-the menu.
-</p>
-
-<pre caption="Finishing the LILO installation">
-# <i>/sbin/lilo</i>
-</pre>
-
-<p>
-If you have more questions regarding LILO, please consult its <uri
-link="http://en.wikipedia.org/wiki/LILO_(boot_loader)">wikipedia page</uri>.
-</p>
-
-<p>
-You can now continue with <uri link="#reboot">Rebooting the System</uri>.
-</p>
-
-</body>
-</subsection>
-</section>
-<section id="grub2" test="contains('AMD64 x86', func:keyval('arch'))">
-<title>Alternative: Using GRUB2</title>
-<subsection>
-<title>Installing GRUB2</title>
-<body>
-
-<p>
-GRUB2 is provided through the <c>sys-boot/grub</c> package. To deploy GRUB2, use
-the <e>SLOT</e> notation to tell Portage to install GRUB2. SLOTs are a feature
-of Gentoo Linux where multiple versions of the same package can be deployed
-simultaneously on a system. In our case, this means that GRUB Legacy and GRUB2
-can be installed on a system (software-wise) at the same time.
-</p>
-
-<note>
-GRUB2 might still be marked as ~<keyval id="arch" />. If that is the case, you
-can either wait and use <uri link="#grub">GRUB Legacy</uri> or unmask the
-package. This is explained in <uri
-link="handbook-amd64.xml?part=3&chap=3#doc_chap2">Mixing Stable with
-Testing</uri>. Once GRUB2 is stabilized, the SLOT operator also is no longer
-mandatory.
-</note>
-
-<pre caption="Installing GRUB2">
-# <i>emerge sys-boot/grub:2</i>
-</pre>
-
-<p>
-The GRUB2 software is now installed on the system, but not activated yet.
-</p>
-
-</body>
-</subsection>
-<subsection>
-<title>Configuring GRUB2</title>
-<body>
-
-<p>
-First, let us install the necessary GRUB2 files in <path>/boot/grub</path>.
-Assuming the first disk (the one where the system boots from) is
-<path>/dev/sda</path>, the following command will do this for us:
-</p>
-
-<pre caption="Installing the GRUB2 files in /boot/grub">
-# <i>grub2-install /dev/sda</i>
-</pre>
-
-<p>
-Next, we can generate the GRUB2 configuration based on the user configuration
-specified in the <path>/etc/default/grub</path> file and
-<path>/etc/grub.d</path> scripts. In most cases, no configuration is needed
-by users as GRUB2 will automatically detect which kernel to boot (the highest
-one available in <path>/boot</path>) and what the root file system is.
-</p>
-
-<p>
-To generate the final GRUB2 configuration, run the <c>grub2-mkconfig</c>
-command:
-</p>
-
-<pre caption="Generating GRUB2 configuration">
-# <i>grub2-mkconfig -o /boot/grub/grub.cfg</i>
-Generating grub.cfg ...
-Found linux image: /boot/<keyval id="kernel-name" />
-Found initrd image: /boot/<keyval id="genkernel-initrd" />
-done
-</pre>
-
-<p>
-The output of the command <e>must</e> mention that at least one Linux image is
-found, as those are needed to boot the system. If you use initramfs or used
-<c>genkernel</c> to build the kernel, the correct initrd image should be
-detected as well. If this is not the case, go to <path>/boot</path> and check
-the contents using the <c>ls</c> command. If the files are indeed missing, go
-back to the kernel configuration and installation instructions.
-</p>
-
-</body>
-</subsection>
-</section>
<section id="elilo" test="func:keyval('arch')='IA64'">
<title>Default: Installing elilo</title>
<body>
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-12-17 11:04 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-12-17 11:04 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/12/17 11:04:50
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Bug 489782 - Update paragraph on GRUB/GRUB2 for no-multilib
Revision Changes Path
1.34 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.34&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.34&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.33&r2=1.34
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -r1.33 -r1.34
--- hb-install-x86+amd64-bootloader.xml 17 Dec 2013 10:38:05 -0000 1.33
+++ hb-install-x86+amd64-bootloader.xml 17 Dec 2013 11:04:50 -0000 1.34
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.33 2013/12/17 10:38:05 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.34 2013/12/17 11:04:50 swift Exp $ -->
<sections>
-<version>17</version>
+<version>18</version>
<date>2013-12-17</date>
<section>
@@ -193,10 +193,10 @@
<impo test="func:keyval('arch')='AMD64'">
If you are using a non-multilib <uri
-link="?part=1&chap=6#doc_chap2">profile</uri>, you should <b>not</b> emerge
-<c>grub</c>, but instead you should emerge <c>grub-static</c>. If you plan to
-use a non-multilib profile <e>and</e> you have <b>disabled</b> IA-32 emulation
-in your kernel, then you should use <c>lilo</c>.
+link="?part=1&chap=6#doc_chap2">profile</uri> and still intend to use the
+GRUB Legacy (instead of GRUB2), you should <b>not</b> emerge
+<c>grub:0</c>, but instead you should emerge <c>grub-static</c> (only possible
+if you have enabled IA-32 emulation).
</impo>
<pre caption="Installing GRUB">
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-09-23 17:34 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-09-23 17:34 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/09/23 17:34:28
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #485684 - Use grub:0 for legacy, and add sys-boot category to emerge commands
Revision Changes Path
1.32 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.32&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.32&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.31&r2=1.32
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- hb-install-x86+amd64-bootloader.xml 20 Sep 2013 06:47:50 -0000 1.31
+++ hb-install-x86+amd64-bootloader.xml 23 Sep 2013 17:34:28 -0000 1.32
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.31 2013/09/20 06:47:50 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.32 2013/09/23 17:34:28 swift Exp $ -->
<sections>
-<version>15</version>
-<date>2013-09-19</date>
+<version>16</version>
+<date>2013-09-23</date>
<section>
<title>Making your Choice</title>
@@ -200,7 +200,7 @@
</impo>
<pre caption="Installing GRUB">
-# <i>emerge grub</i>
+# <i>emerge sys-boot/grub:0</i>
</pre>
<p>
@@ -626,7 +626,7 @@
</note>
<pre caption="Installing GRUB2">
-# <i>emerge grub:2</i>
+# <i>emerge sys-boot/grub:2</i>
</pre>
<p>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-09-20 6:47 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-09-20 6:47 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/09/20 06:47:50
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #484144 - Use /boot/grub as grub2 location
Revision Changes Path
1.31 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.31&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.31&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.30&r2=1.31
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- hb-install-x86+amd64-bootloader.xml 15 Aug 2013 17:05:38 -0000 1.30
+++ hb-install-x86+amd64-bootloader.xml 20 Sep 2013 06:47:50 -0000 1.31
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.30 2013/08/15 17:05:38 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.31 2013/09/20 06:47:50 swift Exp $ -->
<sections>
-<version>14</version>
-<date>2013-08-15</date>
+<version>15</version>
+<date>2013-09-19</date>
<section>
<title>Making your Choice</title>
@@ -640,12 +640,12 @@
<body>
<p>
-First, let us install the necessary GRUB2 files in <path>/boot/grub2</path>.
+First, let us install the necessary GRUB2 files in <path>/boot/grub</path>.
Assuming the first disk (the one where the system boots from) is
<path>/dev/sda</path>, the following command will do this for us:
</p>
-<pre caption="Installing the GRUB2 files in /boot/grub2">
+<pre caption="Installing the GRUB2 files in /boot/grub">
# <i>grub2-install /dev/sda</i>
</pre>
@@ -663,7 +663,7 @@
</p>
<pre caption="Generating GRUB2 configuration">
-# <i>grub2-mkconfig -o /boot/grub2/grub.cfg</i>
+# <i>grub2-mkconfig -o /boot/grub/grub.cfg</i>
Generating grub.cfg ...
Found linux image: /boot/<keyval id="kernel-name" />
Found initrd image: /boot/<keyval id="genkernel-initrd" />
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-08-15 17:05 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-08-15 17:05 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/08/15 17:05:38
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #316603 - Add GRUB2 instructions to handbook
Revision Changes Path
1.30 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.30&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.30&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.29&r2=1.30
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- hb-install-x86+amd64-bootloader.xml 15 Aug 2013 08:14:10 -0000 1.29
+++ hb-install-x86+amd64-bootloader.xml 15 Aug 2013 17:05:38 -0000 1.30
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.29 2013/08/15 08:14:10 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.30 2013/08/15 17:05:38 swift Exp $ -->
<sections>
-<version>13</version>
+<version>14</version>
<date>2013-08-15</date>
<section>
@@ -28,9 +28,16 @@
<body test="contains('AMD64 x86', func:keyval('arch'))">
<p>
For <keyval id="arch"/>, Gentoo Linux provides <uri
-link="#grub">GRUB</uri> and <uri link="#lilo">LILO</uri>.
+link="#grub">GRUB</uri>, <uri link="#grub2">GRUB2</uri> and
+<uri link="#lilo">LILO</uri>.
</p>
+<note>
+GRUB2 might not be stabilized at the moment of reading this. However,
+stabilization is due very soon so we temporarily document both GRUB and GRUB2
+and will remove the GRUB instructions after stabilization of GRUB2.
+</note>
+
</body>
<body>
<p>
@@ -109,7 +116,8 @@
</p>
<p test="not(func:keyval('arch')='IA64')">
-Now continue by installing <uri link="#grub">GRUB</uri> <e>or</e> <uri
+Now continue by installing <uri link="#grub">GRUB</uri>, <uri
+link="#grub2">GRUB2</uri> <e>or</e> <uri
link="#lilo">LILO</uri>.
</p>
@@ -117,7 +125,27 @@
</subsection>
</section>
<section id="grub" test="contains('AMD64 x86',func:keyval('arch'))">
-<title>Default: Using GRUB</title>
+<title>Default: Using GRUB Legacy</title>
+<subsection>
+<title>What is Legacy?</title>
+<body>
+
+<p>
+GRUB has been reworked and a new release dubbed GRUB2 is made available. The new
+GRUB2 codebase is quite different from the current GRUB, which is why this GRUB
+version is now dubbed as "GRUB Legacy".
+</p>
+
+<p>
+We recommend to start with GRUB2 as soon as it is available. The migration of
+GRUB to GRUB2 is <uri link="/doc/en/grub2-migration.xml">documented
+online</uri>. The instructions in this section relate to "GRUB Legacy" and will
+disappear from the book soon after the stabilization of <uri
+link="#grub2">GRUB2</uri>.
+</p>
+
+</body>
+</subsection>
<subsection>
<title>Understanding GRUB's terminology</title>
<body>
@@ -574,6 +602,86 @@
</body>
</subsection>
</section>
+<section id="grub2" test="contains('AMD64 x86', func:keyval('arch'))">
+<title>Alternative: Using GRUB2</title>
+<subsection>
+<title>Installing GRUB2</title>
+<body>
+
+<p>
+GRUB2 is provided through the <c>sys-boot/grub</c> package. To deploy GRUB2, use
+the <e>SLOT</e> notation to tell Portage to install GRUB2. SLOTs are a feature
+of Gentoo Linux where multiple versions of the same package can be deployed
+simultaneously on a system. In our case, this means that GRUB Legacy and GRUB2
+can be installed on a system (software-wise) at the same time.
+</p>
+
+<note>
+GRUB2 might still be marked as ~<keyval id="arch" />. If that is the case, you
+can either wait and use <uri link="#grub">GRUB Legacy</uri> or unmask the
+package. This is explained in <uri
+link="handbook-amd64.xml?part=3&chap=3#doc_chap2">Mixing Stable with
+Testing</uri>. Once GRUB2 is stabilized, the SLOT operator also is no longer
+mandatory.
+</note>
+
+<pre caption="Installing GRUB2">
+# <i>emerge grub:2</i>
+</pre>
+
+<p>
+The GRUB2 software is now installed on the system, but not activated yet.
+</p>
+
+</body>
+</subsection>
+<subsection>
+<title>Configuring GRUB2</title>
+<body>
+
+<p>
+First, let us install the necessary GRUB2 files in <path>/boot/grub2</path>.
+Assuming the first disk (the one where the system boots from) is
+<path>/dev/sda</path>, the following command will do this for us:
+</p>
+
+<pre caption="Installing the GRUB2 files in /boot/grub2">
+# <i>grub2-install /dev/sda</i>
+</pre>
+
+<p>
+Next, we can generate the GRUB2 configuration based on the user configuration
+specified in the <path>/etc/default/grub</path> file and
+<path>/etc/grub.d</path> scripts. In most cases, no configuration is needed
+by users as GRUB2 will automatically detect which kernel to boot (the highest
+one available in <path>/boot</path>) and what the root file system is.
+</p>
+
+<p>
+To generate the final GRUB2 configuration, run the <c>grub2-mkconfig</c>
+command:
+</p>
+
+<pre caption="Generating GRUB2 configuration">
+# <i>grub2-mkconfig -o /boot/grub2/grub.cfg</i>
+Generating grub.cfg ...
+Found linux image: /boot/<keyval id="kernel-name" />
+Found initrd image: /boot/<keyval id="genkernel-initrd" />
+done
+</pre>
+
+<p>
+The output of the command <e>must</e> mention that at least one Linux image is
+found, as those are needed to boot the system. If you use initramfs or used
+<c>genkernel</c> to build the kernel, the correct initrd image should be
+detected as well. If this is not the case, go to <path>/boot</path> and check
+the contents using the <c>ls</c> command. If the files are indeed missing, go
+back to the kernel configuration and installation instructions.
+</p>
+
+</body>
+</subsection>
+</section>
<section id="elilo" test="func:keyval('arch')='IA64'">
<title>Default: Installing elilo</title>
<body>
@@ -660,7 +768,6 @@
</body>
</section>
-
<section id="reboot">
<title>Rebooting the System</title>
<subsection>
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2013-08-15 8:14 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2013-08-15 8:14 UTC (permalink / raw
To: gentoo-doc-cvs
swift 13/08/15 08:14:11
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #467034 - Info on virtio disks and device mapping table
Revision Changes Path
1.29 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.29&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.29&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.28&r2=1.29
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- hb-install-x86+amd64-bootloader.xml 11 Sep 2012 22:49:21 -0000 1.28
+++ hb-install-x86+amd64-bootloader.xml 15 Aug 2013 08:14:10 -0000 1.29
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.28 2012/09/11 22:49:21 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.29 2013/08/15 08:14:10 swift Exp $ -->
<sections>
-<version>12</version>
-<date>2012-09-11</date>
+<version>13</version>
+<date>2013-08-15</date>
<section>
<title>Making your Choice</title>
@@ -325,6 +325,16 @@
</pre>
<p>
+When using Linux virtio disks, we need to tell grub where to find the disks as
+the <c>grub-install</c> command will otherwise fail. This is done by adding the
+device definition to the <path>device.map</path> file:
+</p>
+
+<pre caption="Adding the virtio disk to the device map table">
+# <i>echo "(hd0) /dev/vda" >> /boot/grub/device.map</i>
+</pre>
+
+<p>
Now we can install GRUB using <c>grub-install</c>:
</p>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2012-08-05 1:21 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2012-08-05 1:21 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 12/08/05 01:21:49
Modified: hb-install-x86+amd64-bootloader.xml
Log:
fix real_root for lilo. bug #429940
Revision Changes Path
1.27 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.27&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.27&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.26&r2=1.27
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- hb-install-x86+amd64-bootloader.xml 22 Apr 2012 17:44:07 -0000 1.26
+++ hb-install-x86+amd64-bootloader.xml 5 Aug 2012 01:21:49 -0000 1.27
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.26 2012/04/22 17:44:07 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.27 2012/08/05 01:21:49 nightmorph Exp $ -->
<sections>
-<version>10</version>
-<date>2012-04-22</date>
+<version>11</version>
+<date>2012-08-04</date>
<section>
<title>Making your Choice</title>
@@ -510,7 +510,7 @@
image=/boot/<keyval id="kernel-name"/>
label=gentoo
read-only
- <i>real_</i>root=/dev/sda3
+ <i>append="real_root=/dev/sda3"</i>
<i>initrd=/boot/<keyval id="genkernel-initrd" /></i>
</pre>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2012-04-22 17:44 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2012-04-22 17:44 UTC (permalink / raw
To: gentoo-doc-cvs
swift 12/04/22 17:44:07
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #413097 - Typo on GRUB
Revision Changes Path
1.26 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.26&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.26&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.25&r2=1.26
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- hb-install-x86+amd64-bootloader.xml 22 Apr 2012 10:31:29 -0000 1.25
+++ hb-install-x86+amd64-bootloader.xml 22 Apr 2012 17:44:07 -0000 1.26
@@ -4,11 +4,11 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.25 2012/04/22 10:31:29 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.26 2012/04/22 17:44:07 swift Exp $ -->
<sections>
-<version>9</version>
+<version>10</version>
<date>2012-04-22</date>
<section>
@@ -236,7 +236,7 @@
initramfs file and telling the initramfs where your real root device is at:
</p>
-<pre caption="GUB snippet for initramfs-enabled kernel builds">
+<pre caption="GRUB snippet for initramfs-enabled kernel builds">
title Gentoo Linux <keyval id="kernel-version"/>
root (hd0,0)
kernel /boot/<keyval id="kernel-version"/> <i>real_</i>root=/dev/sda3
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2012-04-22 10:31 Sven Vermeulen (swift)
0 siblings, 0 replies; 21+ messages in thread
From: Sven Vermeulen (swift) @ 2012-04-22 10:31 UTC (permalink / raw
To: gentoo-doc-cvs
swift 12/04/22 10:31:29
Modified: hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #413029 - Reintroduce real_root for genkernel initramfs builds
Revision Changes Path
1.25 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.25&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.25&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.24&r2=1.25
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- hb-install-x86+amd64-bootloader.xml 27 Mar 2012 17:47:19 -0000 1.24
+++ hb-install-x86+amd64-bootloader.xml 22 Apr 2012 10:31:29 -0000 1.25
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.24 2012/03/27 17:47:19 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.25 2012/04/22 10:31:29 swift Exp $ -->
<sections>
-<version>8</version>
-<date>2011-05-09</date>
+<version>9</version>
+<date>2012-04-22</date>
<section>
<title>Making your Choice</title>
@@ -221,8 +221,6 @@
<comment># Partition where the kernel image (or operating system) is located</comment>
root (hd0,0)
kernel /boot/<keyval id="kernel-name"/> root=/dev/sda3 init=/bin/bb
-<comment># The initrd line is needed when you have built an initramfs (or used genkernel)</comment>
-initrd /boot/<keyval id="genkernel-initrd"/>
<comment># The next four lines are only if you dualboot with a Windows system.</comment>
<comment># In this case, Windows is hosted on /dev/sda6.</comment>
@@ -233,6 +231,19 @@
</pre>
<p>
+If, while building the Linux kernel, you opted to include an initramfs to boot
+from, then you will need to change the configuration by referring to this
+initramfs file and telling the initramfs where your real root device is at:
+</p>
+
+<pre caption="GUB snippet for initramfs-enabled kernel builds">
+title Gentoo Linux <keyval id="kernel-version"/>
+root (hd0,0)
+kernel /boot/<keyval id="kernel-version"/> <i>real_</i>root=/dev/sda3
+<i>initrd /boot/<keyval id="genkernel-initrd"/></i>
+</pre>
+
+<p>
If you used a different partitioning scheme and/or kernel image, adjust
accordingly. However, make sure that anything that follows a GRUB-device (such
as <path>(hd0,0)</path>) is relative to the mountpoint, not the root. In other
@@ -471,8 +482,6 @@
label=gentoo <comment># Name we give to this section</comment>
read-only <comment># Start with a read-only root. Do not alter!</comment>
root=/dev/sda3 <comment># Location of the root filesystem</comment>
-<comment># The initrd line is only needed if you built an initramfs (or used genkernel)</comment>
- initrd=/boot/<keyval id="genkernel-initrd"/>
image=/boot/<keyval id="kernel-name"/>
label=gentoo.rescue <comment># Name we give to this section</comment>
@@ -492,6 +501,20 @@
</note>
<p>
+If, while building the Linux kernel, you opted to include an initramfs to boot
+from, then you will need to change the configuration by referring to this
+initramfs file and telling the initramfs where your real root device is at:
+</p>
+
+<pre caption="LILO snippet for initramfs-enabled kernel builds">
+image=/boot/<keyval id="kernel-name"/>
+ label=gentoo
+ read-only
+ <i>real_</i>root=/dev/sda3
+ <i>initrd=/boot/<keyval id="genkernel-initrd" /></i>
+</pre>
+
+<p>
If you need to pass any additional options to the kernel, add an
<c>append</c> statement to the section. As an example, we add the
<c>video</c> statement to enable framebuffer:
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2010-07-17 20:18 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-07-17 20:18 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 10/07/17 20:18:42
Modified: hb-install-x86+amd64-bootloader.xml
Log:
add <c> tags around grub, no content change
Revision Changes Path
1.20 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.20&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.20&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.19&r2=1.20
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- hb-install-x86+amd64-bootloader.xml 16 Jul 2010 23:19:06 -0000 1.19
+++ hb-install-x86+amd64-bootloader.xml 17 Jul 2010 20:18:41 -0000 1.20
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.19 2010/07/16 23:19:06 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.20 2010/07/17 20:18:41 nightmorph Exp $ -->
<sections>
@@ -166,9 +166,9 @@
<impo test="func:keyval('arch')='AMD64'">
If you are using a non-multilib <uri
link="?part=1&chap=6#doc_chap2">profile</uri>, you should <b>not</b> emerge
-grub, but instead you should emerge <c>grub-static</c>. If you plan to use a
-non-multilib profile <e>and</e> you have <b>disabled</b> IA-32 emulation in your
-kernel, then you should use <c>lilo</c>.
+<c>grub</c>, but instead you should emerge <c>grub-static</c>. If you plan to
+use a non-multilib profile <e>and</e> you have <b>disabled</b> IA-32 emulation
+in your kernel, then you should use <c>lilo</c>.
</impo>
<pre caption="Installing GRUB">
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2010-07-16 23:19 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-07-16 23:19 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 10/07/16 23:19:06
Modified: hb-install-x86+amd64-bootloader.xml
Log:
update grub documentation links, bug 328679
Revision Changes Path
1.19 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.19&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.19&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.18&r2=1.19
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- hb-install-x86+amd64-bootloader.xml 6 Apr 2010 03:56:02 -0000 1.18
+++ hb-install-x86+amd64-bootloader.xml 16 Jul 2010 23:19:06 -0000 1.19
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.18 2010/04/06 03:56:02 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.19 2010/07/16 23:19:06 nightmorph Exp $ -->
<sections>
-<version>6.6</version>
-<date>2010-01-01</date>
+<version>6.7</version>
+<date>2010-07-16</date>
<section>
<title>Making your Choice</title>
@@ -351,8 +351,9 @@
<p>
If you have more questions regarding GRUB, please consult the <uri
-link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the
-<uri link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>.
+link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri>, the <uri
+link="http://grub.enbug.org/GrubLegacy">GRUB Wiki</uri>, or read <c>info
+grub</c> in your terminal.
</p>
<p>
@@ -419,8 +420,9 @@
<p>
If you have more questions regarding GRUB, please consult the <uri
-link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri> or the <uri
-link="http://www.gnu.org/software/grub/manual/">GRUB Manual</uri>.
+link="http://www.gnu.org/software/grub/grub-faq.html">GRUB FAQ</uri>, the <uri
+link="http://grub.enbug.org/GrubLegacy">GRUB Wiki</uri>, or read <c>info
+grub</c> in your terminal.
</p>
<p>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2010-04-06 3:56 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-04-06 3:56 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 10/04/06 03:56:02
Modified: hb-install-x86+amd64-bootloader.xml
Log:
typo fix, no content change
Revision Changes Path
1.18 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.18&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.18&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.17&r2=1.18
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- hb-install-x86+amd64-bootloader.xml 10 Jan 2010 18:18:21 -0000 1.17
+++ hb-install-x86+amd64-bootloader.xml 6 Apr 2010 03:56:02 -0000 1.18
@@ -4,7 +4,7 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.17 2010/01/10 18:18:21 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.18 2010/04/06 03:56:02 nightmorph Exp $ -->
<sections>
@@ -282,7 +282,7 @@
If you need to pass any additional options to the kernel, simply add them to the
end of the kernel command. We're already passing one option
(<c>root=/dev/sda3</c> or <c>real_root=/dev/sda3</c>), but you can pass others
-as well, such as the <c>video</c>> statement for framebuffer as we discussed
+as well, such as the <c>video</c> statement for framebuffer as we discussed
previously.
</p>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2010-01-10 18:18 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-01-10 18:18 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 10/01/10 18:18:21
Modified: hb-install-x86+amd64-bootloader.xml
Log:
typo in date; spotted by keytoaster. no content change.
Revision Changes Path
1.17 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.17&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.17&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.16&r2=1.17
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- hb-install-x86+amd64-bootloader.xml 1 Jan 2010 17:45:26 -0000 1.16
+++ hb-install-x86+amd64-bootloader.xml 10 Jan 2010 18:18:21 -0000 1.17
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.16 2010/01/01 17:45:26 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.17 2010/01/10 18:18:21 nightmorph Exp $ -->
<sections>
<version>6.6</version>
-<date>20109-01-01</date>
+<date>2010-01-01</date>
<section>
<title>Making your Choice</title>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2010-01-01 17:45 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2010-01-01 17:45 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 10/01/01 17:45:26
Modified: hb-install-x86+amd64-bootloader.xml
Log:
rewrite real_rootflags stuff to make sense. from bug 273803 comment 17
Revision Changes Path
1.16 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.16&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.16&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.15&r2=1.16
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- hb-install-x86+amd64-bootloader.xml 17 Nov 2009 05:55:40 -0000 1.15
+++ hb-install-x86+amd64-bootloader.xml 1 Jan 2010 17:45:26 -0000 1.16
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.15 2009/11/17 05:55:40 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.16 2010/01/01 17:45:26 nightmorph Exp $ -->
<sections>
-<version>6.5</version>
-<date>2009-11-16</date>
+<version>6.6</version>
+<date>20109-01-01</date>
<section>
<title>Making your Choice</title>
@@ -287,10 +287,8 @@
</p>
<p>
-If your bootloader configuration file contains the real_root parameter use the
-rootflags parameter to set root filesystem mount options. In the case where
-real_root defines the root mount point, the real_rootflags parameter should be
-used.
+If your bootloader configuration file contains the real_root parameter, use the
+real_rootflags parameter to set root filesystem mount options.
</p>
<p>
^ permalink raw reply [flat|nested] 21+ messages in thread
* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2009-11-17 5:55 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2009-11-17 5:55 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 09/11/17 05:55:40
Modified: hb-install-x86+amd64-bootloader.xml
Log:
ripped out VESA/VGA stuff in favor of only uvesafb, as it's in all kernels, not just gentoo-sources. bug 293455
Revision Changes Path
1.15 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.15&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.15&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.14&r2=1.15
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- hb-install-x86+amd64-bootloader.xml 24 Sep 2009 20:26:50 -0000 1.14
+++ hb-install-x86+amd64-bootloader.xml 17 Nov 2009 05:55:40 -0000 1.15
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.14 2009/09/24 20:26:50 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.15 2009/11/17 05:55:40 nightmorph Exp $ -->
<sections>
-<version>6.4</version>
-<date>2009-09-24</date>
+<version>6.5</version>
+<date>2009-11-16</date>
<section>
<title>Making your Choice</title>
@@ -49,76 +49,19 @@
<p>
<e>If</e> you have configured your kernel with framebuffer support (or you used
<c>genkernel</c> default kernel configuration), you can activate it by adding a
-<c>vga</c> and/or a <c>video</c> statement to your bootloader configuration
-file.
+a <c>video</c> statement to your bootloader configuration file.
</p>
<p>
-First of all, you need to know what type of framebuffer device you're using. If
-you use a Gentoo patched kernel tree (such as <c>gentoo-sources</c>) you will
-have had the possibility of selecting <c>uvesafb</c> as the <e>VESA driver</e>.
-If this is the case, you are using <c>uvesafb</c> and <e>do not need</e> to set
-a <c>vga</c> statement. Otherwise you are using the <c>vesafb</c> driver and
-<e>need</e> to set the <c>vga</c> statement.
+First of all, you need to know your framebuffer device. You should have used
+<c>uvesafb</c> as the <e>VESA driver</e>.
</p>
<p>
-The <c>vga</c> statement controls the resolution and color depth of your
-framebuffer screen for <c>vesafb</c>. As stated in
-<path>/usr/src/linux/Documentation/fb/vesafb.txt</path> (which gets installed
-when you install a kernel source package), you need to pass the VESA number
-corresponding to the requested resolution and color depth to it.
-</p>
-
-<p>
-The following table lists the available resolutions and color depths and
-matches those against the value that you need to pass on to the <c>vga</c>
-statement.
-</p>
-
-<table>
-<tr>
- <ti></ti>
- <th>640x480</th>
- <th>800x600</th>
- <th>1024x768</th>
- <th>1280x1024</th>
-</tr>
-<tr>
- <th>256</th>
- <ti>0x301</ti>
- <ti>0x303</ti>
- <ti>0x305</ti>
- <ti>0x307</ti>
-</tr>
-<tr>
- <th>32k</th>
- <ti>0x310</ti>
- <ti>0x313</ti>
- <ti>0x316</ti>
- <ti>0x319</ti>
-</tr>
-<tr>
- <th>64k</th>
- <ti>0x311</ti>
- <ti>0x314</ti>
- <ti>0x317</ti>
- <ti>0x31A</ti>
-</tr>
-<tr>
- <th>16M</th>
- <ti>0x312</ti>
- <ti>0x315</ti>
- <ti>0x318</ti>
- <ti>0x31B</ti>
-</tr>
-</table>
-
-<p>
The <c>video</c> statement controls framebuffer display options. It needs to be
given the framebuffer driver followed by the control statements you wish to
enable. All variables are listed in
-<path>/usr/src/linux/Documentation/fb/vesafb.txt</path>. The most-used options
+<path>/usr/src/linux/Documentation/fb/uvesafb.txt</path>. The most-used options
are:
</p>
@@ -148,7 +91,6 @@
<tr>
<ti><c>mode</c></ti>
<ti>
- (<c>uvesafb</c> only)<br/>
Set up the resolution, color depth and refresh rate. For instance,
<c>1024x768-32@85</c> for a resolution of 1024x768, 32 bit color depth and a
refresh rate of 85 Hz.
@@ -157,8 +99,7 @@
</table>
<p>
-The result of those two statements could be something like <c>vga=0x318
-video=vesafb:mtrr:3,ywrap</c> or
+The result could be something like
<c>video=uvesafb:mtrr:3,ywrap,1024x768-32@85</c>. Write this setting down; you
will need it shortly.
</p>
@@ -185,7 +126,7 @@
The most critical part of understanding GRUB is getting comfortable with how
GRUB refers to hard drives and partitions. Your Linux partition
<path>/dev/sda1</path> will most likely be called <path>(hd0,0)</path> under
-GRUB. Notice the parentheses around the <path>hd0,0</path> - they are
+GRUB. Notice the parentheses around the <path>hd0,0</path> - they are
required.
</p>
@@ -338,11 +279,11 @@
</p>
<p>
-If you need to pass any additional options to the kernel, simply add
-them to the end of the kernel command. We're already passing one option
+If you need to pass any additional options to the kernel, simply add them to the
+end of the kernel command. We're already passing one option
(<c>root=/dev/sda3</c> or <c>real_root=/dev/sda3</c>), but you can pass others
-as well, such as the <c>video</c> and/or <c>vga</c> statements for framebuffer
-as we discussed previously.
+as well, such as the <c>video</c>> statement for framebuffer as we discussed
+previously.
</p>
<p>
@@ -605,7 +546,7 @@
label=gentoo
read-only
root=/dev/sda3
- <i>append="video=vesafb:mtrr,ywrap,1024x768-32@85"</i>
+ <i>append="video=uvesafb:mtrr,ywrap,1024x768-32@85"</i>
</pre>
<p>
^ permalink raw reply [flat|nested] 21+ messages in thread* [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml
@ 2009-04-15 7:23 Joshua Saddler (nightmorph)
0 siblings, 0 replies; 21+ messages in thread
From: Joshua Saddler (nightmorph) @ 2009-04-15 7:23 UTC (permalink / raw
To: gentoo-doc-cvs
nightmorph 09/04/15 07:23:57
Modified: hb-install-x86+amd64-bootloader.xml
Log:
updated lilo info for the AMD64 handbook, bug 245419
Revision Changes Path
1.13 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.13&view=markup
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.13&content-type=text/plain
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?r1=1.12&r2=1.13
Index: hb-install-x86+amd64-bootloader.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- hb-install-x86+amd64-bootloader.xml 10 Sep 2008 23:40:52 -0000 1.12
+++ hb-install-x86+amd64-bootloader.xml 15 Apr 2009 07:23:57 -0000 1.13
@@ -4,12 +4,12 @@
<!-- The content of this document is licensed under the CC-BY-SA license -->
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.12 2008/09/10 23:40:52 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml,v 1.13 2009/04/15 07:23:57 nightmorph Exp $ -->
<sections>
-<version>6.2</version>
-<date>2008-09-10</date>
+<version>6.3</version>
+<date>2009-04-15</date>
<section>
<title>Making your Choice</title>
@@ -31,10 +31,6 @@
link="#grub">GRUB</uri> and <uri link="#lilo">LILO</uri>.
</p>
-<warn test="func:keyval('arch')='AMD64'">
-Using LILO on the AMD64 architecture is not recommended.
-</warn>
-
</body>
<body>
<p>
@@ -229,7 +225,9 @@
<impo test="func:keyval('arch')='AMD64'">
If you are using a non-multilib <uri
link="?part=1&chap=6#doc_chap2">profile</uri>, you should <b>not</b> emerge
-grub, but instead you should emerge <c>grub-static</c>.
+grub, but instead you should emerge <c>grub-static</c>. If you plan to use a
+non-multilib profile <e>and</e> you have <b>disabled</b> IA-32 emulation in your
+kernel, then you should use <c>lilo</c>.
</impo>
<pre caption="Installing GRUB">
@@ -492,10 +490,6 @@
<title>Installing LILO</title>
<body>
-<warn test="func:keyval('arch')='AMD64'">
-Using LILO on the AMD64 architecture is not recommended.
-</warn>
-
<p>
LILO, the LInuxLOader, is the tried and true workhorse of Linux
bootloaders. However, it lacks some features that GRUB has (which is
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2014-08-17 16:18 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-09-24 20:26 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-bootloader.xml Joshua Saddler (nightmorph)
-- strict thread matches above, loose matches on Subject: below --
2014-08-17 16:18 Sven Vermeulen (swift)
2013-12-31 20:29 Sven Vermeulen (swift)
2013-12-18 7:38 Sven Vermeulen (swift)
2013-12-17 11:58 Sven Vermeulen (swift)
2013-12-17 11:55 Sven Vermeulen (swift)
2013-12-17 11:04 Sven Vermeulen (swift)
2013-09-23 17:34 Sven Vermeulen (swift)
2013-09-20 6:47 Sven Vermeulen (swift)
2013-08-15 17:05 Sven Vermeulen (swift)
2013-08-15 8:14 Sven Vermeulen (swift)
2012-08-05 1:21 Joshua Saddler (nightmorph)
2012-04-22 17:44 Sven Vermeulen (swift)
2012-04-22 10:31 Sven Vermeulen (swift)
2010-07-17 20:18 Joshua Saddler (nightmorph)
2010-07-16 23:19 Joshua Saddler (nightmorph)
2010-04-06 3:56 Joshua Saddler (nightmorph)
2010-01-10 18:18 Joshua Saddler (nightmorph)
2010-01-01 17:45 Joshua Saddler (nightmorph)
2009-11-17 5:55 Joshua Saddler (nightmorph)
2009-04-15 7:23 Joshua Saddler (nightmorph)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox