* [gentoo-commits] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-kernel.xml hb-install-x86+amd64-bootloader.xml
@ 2012-03-27 17:47 Sven Vermeulen (swift)
0 siblings, 0 replies; only message in thread
From: Sven Vermeulen (swift) @ 2012-03-27 17:47 UTC (permalink / raw
To: gentoo-commits
swift 12/03/27 17:47:20
Modified: hb-install-x86+amd64-kernel.xml
hb-install-x86+amd64-bootloader.xml
Log:
Fix bug #408691 - Update instructions with initramfs information, bug #406961 - update kernel configuration entries
Revision Changes Path
1.46 xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.46&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?rev=1.46&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml?r1=1.45&r2=1.46
Index: hb-install-x86+amd64-kernel.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- hb-install-x86+amd64-kernel.xml 22 Feb 2012 21:27:45 -0000 1.45
+++ hb-install-x86+amd64-kernel.xml 27 Mar 2012 17:47:19 -0000 1.46
@@ -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-kernel.xml,v 1.45 2012/02/22 21:27:45 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-kernel.xml,v 1.46 2012/03/27 17:47:19 swift Exp $ -->
<sections>
@@ -13,8 +13,8 @@
explains how to configure your kernel.
</abstract>
-<version>15</version>
-<date>2012-02-22</date>
+<version>16</version>
+<date>2012-03-27</date>
<section>
<title>Timezone</title>
@@ -236,7 +236,7 @@
<pre caption="Selecting PPPoE necessary drivers">
Device Drivers --->
- Networking device Support --->
+ Network device support --->
<*> PPP (point-to-point protocol) support
<*> PPP support for async serial ports
<*> PPP support for sync tty ports
@@ -342,6 +342,59 @@
# <i>cp arch/<keyval id="arch-sub"/>/boot/bzImage /boot/<keyval id="kernel-name"/></i>
</pre>
+</body>
+</subsection>
+<subsection id="initramfs">
+<title>(Optional) Building an Initramfs</title>
+<body>
+
+<p>
+If you use a specific partition layout where important file system locations
+(like <path>/usr</path> or <path>/var</path>) are on separate partitions, then
+you will need to setup an initramfs so that this partition can be mounted before
+it is needed.
+</p>
+
+<p>
+Without an initramfs, you risk that the system will not boot up properly as the
+tools that are responsible for mounting the file systems need information that
+resides on those file systems. An initramfs will pull in the necessary files
+into an archive which is used right after the kernel boots, but before the
+control is handed over to the <c>init</c> tool. Scripts on the initramfs will
+then make sure that the partitions are properly mounted before the system
+continues booting.
+</p>
+
+<p>
+To install an initramfs, install <c>genkernel</c> first, then have it
+generate an initramfs for you.
+</p>
+
+<pre caption="Building an initramfs">
+# <i>emerge genkernel</i>
+# <i>genkernel --install initramfs</i>
+</pre>
+
+<p>
+If you need specific support in the initramfs, such as lvm or raid, add in the
+appropriate options to genkernel. See <c>genkernel --help</c> for more
+information, or the next example which enables support for LVM and software raid
+(mdadm):
+</p>
+
+<pre caption="Building an initramfs with support for LVM and software raid">
+# <i>genkernel --lvm --mdadm --install initramfs</i>
+</pre>
+
+<p>
+The initramfs will be stored in <path>/boot</path>. You can find the file by
+simply listing the files starting with <path>initramfs</path>:
+</p>
+
+<pre caption="Checking the initramfs file name">
+# <i>ls /boot/initramfs*</i>
+</pre>
+
<p>
Now continue with <uri link="#kernel_modules">Kernel Modules</uri>.
</p>
1.24 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.24&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/handbook/hb-install-x86+amd64-bootloader.xml?rev=1.24&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.23&r2=1.24
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.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- hb-install-x86+amd64-bootloader.xml 9 May 2011 19:47:22 -0000 1.23
+++ hb-install-x86+amd64-bootloader.xml 27 Mar 2012 17:47:19 -0000 1.24
@@ -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.23 2011/05/09 19:47:22 nightmorph Exp $ -->
+<!-- $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 $ -->
<sections>
@@ -187,24 +187,11 @@
</pre>
<p>
-Now we are going to write up a <path>grub.conf</path>. Below you'll find two
-possible <path>grub.conf</path> for the partitioning example we use in this
-guide. We've only extensively commented the first <path>grub.conf</path>. Make
+Now we are going to write up a <path>grub.conf</path>. Make
sure you use <e>your</e> kernel image filename and, if appropriate, <e>your</e>
initrd image filename.
</p>
-<ul>
- <li>
- The first <path>grub.conf</path> is for people who have not used
- <c>genkernel</c> to build their kernel
- </li>
- <li>
- The second <path>grub.conf</path> is for people who have used
- <c>genkernel</c> to build their kernel
- </li>
-</ul>
-
<note>
Grub assigns device designations from the BIOS. If you change your BIOS
settings, your device letters and numbers may change, too. For example, if you
@@ -216,7 +203,7 @@
line since JFS needs to replay its log before it allows read-write mounting.
</note>
-<pre caption="grub.conf for non-genkernel users">
+<pre caption="Example grub.conf">
<comment># Which listing to boot as default. 0 is the first, 1 the second etc.</comment>
default 0
<comment># How many seconds to wait before the default listing is booted.</comment>
@@ -234,6 +221,8 @@
<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>
@@ -243,23 +232,6 @@
chainloader +1
</pre>
-<pre caption="grub.conf for genkernel users">
-default 0
-timeout 30
-splashimage=(hd0,0)/boot/grub/splash.xpm.gz
-
-title Gentoo Linux <keyval id="kernel-version"/>
-root (hd0,0)
-kernel /boot/<keyval id="genkernel-name"/> real_root=/dev/sda3
-initrd /boot/<keyval id="genkernel-initrd"/>
-
-<comment># Only in case you want to dual-boot</comment>
-title Windows XP
-rootnoverify (hd0,5)
-makeactive
-chainloader +1
-</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
@@ -475,18 +447,9 @@
<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. There are two separate parts:
+example partitioning scheme.
</p>
-<ul>
- <li>
- One for those who have not used <c>genkernel</c> to build their kernel
- </li>
- <li>
- One for those who have used <c>genkernel</c> to build their kernel
- </li>
-</ul>
-
<p>
Make sure you use <e>your</e> kernel image filename and, if appropriate,
<e>your</e> initrd image filename.
@@ -504,11 +467,12 @@
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>
-<comment># For non-genkernel users</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>
+<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>
@@ -516,13 +480,6 @@
root=/dev/sda3 <comment># Location of the root filesystem</comment>
append="init=/bin/bb" <comment># Launch the Gentoo static rescue shell</comment>
-<comment># For genkernel users</comment>
-image=/boot/<keyval id="genkernel-name"/>
- label=gentoo
- read-only
- append="real_root=/dev/sda3"
- initrd=/boot/<keyval id="genkernel-initrd"/>
-
<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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-03-27 17:47 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-27 17:47 [gentoo-commits] gentoo commit in xml/htdocs/doc/en/handbook: hb-install-x86+amd64-kernel.xml hb-install-x86+amd64-bootloader.xml Sven Vermeulen (swift)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox