/[gentoo]/xml/htdocs/doc/en/genkernel.xml
Gentoo

Diff of /xml/htdocs/doc/en/genkernel.xml

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.30 Revision 1.31
1<?xml version="1.0" encoding="UTF-8"?> 1<?xml version="1.0" encoding="UTF-8"?>
2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v 1.30 2007/09/21 23:01:43 nightmorph Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v 1.31 2008/06/23 05:07:13 nightmorph Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/genkernel.xml" disclaimer="obsolete"> 5<guide link="/doc/en/genkernel.xml" disclaimer="obsolete">
6<title>Gentoo Linux Genkernel Guide</title> 6<title>Gentoo Linux Genkernel Guide</title>
7 7
8<author title="Author"> 8<author title="Author">
9 <mail link="plasmaroo@gentoo.org">Tim Yamin</mail> 9 <mail link="plasmaroo@gentoo.org">Tim Yamin</mail>
10</author> 10</author>
11
12<!-- folajimi@speakeasy.net --> 11<!-- folajimi@speakeasy.net -->
13<author title="Contributor"> 12<author title="Contributor">
14 Jimi Ayodele 13 Jimi Ayodele
15</author> 14</author>
16
17<!-- thseiler@gmail.com --> 15<!-- thseiler@gmail.com -->
18<author title="NFS Support"> 16<author title="NFS Support">
19 Thomas Seiler 17 Thomas Seiler
20</author> 18</author>
19<author title="Editor">
20 <mail link="nightmorph"/>
21</author>
21 22
22<abstract> 23<abstract>
23This guide intends to provide a reference of all the functions provided by 24This guide intends to provide a reference of all the functions provided by
24genkernel. 25genkernel.
25</abstract> 26</abstract>
26 27
27<license/> 28<license/>
28 29
29<version>1.5</version> 30<version>1.6</version>
30<date>2007-06-20</date> 31<date>2008-06-22</date>
31 32
32<chapter> 33<chapter>
33<title>Introduction</title> 34<title>Introduction</title>
34<section> 35<section>
35<title>Rationale</title> 36<title>Rationale</title>
… …
103and may increase compile time. Below is an illustration of a more efficient 104and may increase compile time. Below is an illustration of a more efficient
104approach, achieved by passing certain flags to genkernel as root: 105approach, achieved by passing certain flags to genkernel as root:
105</p> 106</p>
106 107
107<pre caption="Running genkernel (with flags)"> 108<pre caption="Running genkernel (with flags)">
108# <i>genkernel --bootsplash --no-install --no-clean --menuconfig all</i> 109# <i>genkernel --splash --no-install --no-clean --menuconfig all</i>
109</pre> 110</pre>
110 111
111<p> 112<p>
112The above operation causes genkernel to create a bootsplash-enabled kernel 113The above operation causes genkernel to create a framebuffer splash-enabled
113(<c>--bootsplash</c>) that will have to be manually installed 114kernel (<c>--splash</c>) that will have to be manually installed
114(<c>--no-install</c>). While preparing the kernel source tree, genkernel will 115(<c>--no-install</c>). While preparing the kernel source tree, genkernel will
115refrain from cleaning out any preexisting object files present in the source 116refrain from cleaning out any preexisting object files present in the source
116tree (<c>--no-clean</c>). A menu-driven kernel configuration utility will be 117tree (<c>--no-clean</c>). A menu-driven kernel configuration utility will be
117displayed that allows the user to select which modules will be built for the 118displayed that allows the user to select which modules will be built for the
118system (<c>--menuconfig</c>). 119system (<c>--menuconfig</c>).
… …
378enabling certain features on the system. 379enabling certain features on the system.
379</p> 380</p>
380 381
381<ul> 382<ul>
382 <li> 383 <li>
383 <b>--<c>no-</c>bootsplash</b>: Activates <e>[or deactivates]</e> support
384 for <uri link="http://www.bootsplash.org/">bootsplash</uri> in the
385 genkernel-built initrd image. The bootsplash feature is supported on a
386 limited number of architectures, and a kernel that supports bootsplash is
387 also required.
388 </li>
389 <li>
390 <b>--<c>no-</c>gensplash</b>: Activates <e>[or deactivates]</e> support for 384 <b>--<c>no-</c>splash</b>: Activates <e>[or deactivates]</e> support for
391 <uri 385 <uri link="http://fbsplash.berlios.de/wiki/doku.php">framebuffer
392 link="http://dev.gentoo.org/~spock/projects/gensplash/">gensplash</uri> 386 splash</uri> support in the genkernel-built initrd image. To override the
393 support in the genkernel-built initrd image. The gensplash utility is 387 default theme used by fbsplash, use <b>--splash=<c>PreferredTheme</c></b>
394 intended to be a replacement for bootsplash, and is designed for use with 388 (where <c>PreferredTheme</c> is the title of one of the directories inside
395 2.6.x series kernels. To override the default theme used by gensplash, use 389 the <path>/etc/splash/</path> directory.
396 <b>--gensplash=<c>PreferredTheme</c></b> (where <c>PreferredTheme</c> is
397 the title of one of the directories inside the <path>/etc/splash/</path>
398 directory.
399 </li>
400 <li> 390 </li>
391 <li>
401 <b>--gensplash-res=<c>PreferredResolution</c></b>: This flag allows you to 392 <b>--splash-res=<c>PreferredResolution</c></b>: This flag allows you to
402 select which splash screen resolutions will be supported in the initrd 393 select which splash screen resolutions will be supported in the initrd
403 during the start-up of the system. This is useful for two reasons: First, 394 during the start-up of the system. This is useful for two reasons: First,
404 you are able to select only the splash screen resolution(s) relevant to 395 you are able to select only the splash screen resolution(s) relevant to your
405 your system. Second, you avoid the unnecessary increase in the disk space 396 system. Second, you avoid the unnecessary increase in the disk space
406 required by initrd (since the initrd does not have to support resolutions 397 required by initrd (since the initrd does not have to support resolutions
407 that are irrelevant for your system configuration.) However, you may want 398 that are irrelevant for your system configuration.) However, you may want to
408 to omit this flag if the kernel is being compiled for an Installation CD; 399 omit this flag if the kernel is being compiled for an Installation CD; this
409 this allows gensplash support for all possible resolutions. 400 allows splash support for all possible resolutions.
410 </li> 401 </li>
411 <li> 402 <li>
412 <b>--do-keymap-auto</b>: Force keymap selection during the boot sequence. 403 <b>--do-keymap-auto</b>: Force keymap selection during the boot sequence.
413 </li> 404 </li>
414 <li> 405 <li>
… …
539 Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters 530 Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters
540 passed to the kernel image, if <path>/dev/hda3</path> contains your root 531 passed to the kernel image, if <path>/dev/hda3</path> contains your root
541 partition. 532 partition.
542 </li> 533 </li>
543 <li> 534 <li>
544 If you are using bootsplash, add a suitable mode line such as 535 If you are using splash, add a suitable mode line such as <c>vga=0x317</c>
545 <c>vga=0x317</c> to the parameters passed to the kernel and also add 536 to the parameters passed to the kernel and also add <c>splash=verbose</c> or
546 <c>splash=verbose</c> or <c>splash=silent</c> depending on the verboseness 537 <c>splash=silent</c> depending on the verboseness you require from your
547 you require from your bootloader. 538 bootloader.
548 </li> 539 </li>
549 <li> 540 <li>
550 Add the initrd information as required by the bootloader. Consult the <uri 541 Add the initrd information as required by the bootloader. Consult the <uri
551 link="/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10">Bootloader 542 link="/doc/en/handbook/handbook-x86.xml?part=1&amp;chap=10">Bootloader
552 Configuration Chapter</uri> of the Gentoo Handbook for details on how to 543 Configuration Chapter</uri> of the Gentoo Handbook for details on how to
… …
568Passing flags to genkernel from the command line can be cumbersome, especially 559Passing flags to genkernel from the command line can be cumbersome, especially
569if you have about a dozen flags: 560if you have about a dozen flags:
570</p> 561</p>
571 562
572<pre caption="Running genkernel (overloaded with flags)"> 563<pre caption="Running genkernel (overloaded with flags)">
573# <i>genkernel --debuglevel=5 --no-color --no-mrproper --clean --gensplash \ 564# <i>genkernel --debuglevel=5 --no-color --no-mrproper --clean --splash \
574--kerneldir=/path/to/alternate/kernel/sources --install --menuconfig \ 565--kerneldir=/path/to/alternate/kernel/sources --install --menuconfig \
575--kernel-config=/path/to/preferred/configfile --save-config --mountboot all</i> 566--kernel-config=/path/to/preferred/configfile --save-config --mountboot all</i>
576</pre> 567</pre>
577 568
578<p> 569<p>
… …
640By choosing the appropriate options in <path>/etc/genkernel.conf</path>, you 631By choosing the appropriate options in <path>/etc/genkernel.conf</path>, you
641can halve the number of flags passed to genkernel from the command line: 632can halve the number of flags passed to genkernel from the command line:
642</p> 633</p>
643 634
644<pre caption="Running genkernel (with flags), after employing genkernel.conf"> 635<pre caption="Running genkernel (with flags), after employing genkernel.conf">
645# <i>genkernel --gensplash --kerneldir=/path/to/alternate/kernel/sources \ 636# <i>genkernel --splash --kerneldir=/path/to/alternate/kernel/sources \
646--kernel-config=/path/to/preferred/configfile --install all</i> 637--kernel-config=/path/to/preferred/configfile --install all</i>
647</pre> 638</pre>
648 639
649<p> 640<p>
650Identical results are obtained from both approaches, but the latter has most of 641Identical results are obtained from both approaches, but the latter has most of
Legend:
Removed from v.1.30  
changed lines
  Added in v.1.31
  ViewVC Help
Powered by ViewVC 1.1.20