/[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.10 Revision 1.14
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.10 2004/09/21 09:16:23 neysx Exp $ --> 2<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/genkernel.xml,v 1.14 2005/06/11 10:41:31 plasmaroo Exp $ -->
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 4
5<guide link="/doc/en/genkernel.xml"> 5<guide link="/doc/en/genkernel.xml">
6<title>Gentoo Linux Genkernel Guide</title> 6<title>Gentoo Linux Genkernel Guide</title>
7 7
9 <mail link="plasmaroo@gentoo.org">Tim Yamin</mail> 9 <mail link="plasmaroo@gentoo.org">Tim Yamin</mail>
10</author> 10</author>
11 11
12<abstract> 12<abstract>
13This guide intends to provide a reference of all the functions 13This guide intends to provide a reference of all the functions
14provided by Genkernel. 14provided by genkernel.
15</abstract> 15</abstract>
16 16
17<license/> 17<license/>
18 18
19<version>1.1</version> 19<version>1.1.2.1</version>
20<date>August 19, 2004</date> 20<date>June 11, 2005</date>
21 21
22<chapter> 22<chapter>
23<title>Introduction</title> 23<title>Introduction</title>
24<section> 24<section>
25<title>Introduction</title> 25<title>Introduction</title>
84<section> 84<section>
85<title>Supported platforms</title> 85<title>Supported platforms</title>
86<body> 86<body>
87 87
88<p> 88<p>
89As of genkernel 3.0.2; the following platforms should be 89As of genkernel 3.0.2, the following platforms should be
90supported: alpha, amd64, parisc, parisc64, ppc, ppc64, sparc, sparc64, and x86. If 90supported: alpha, amd64, parisc, parisc64, ppc, ppc64, sparc, sparc64, and x86.
91you believe that there is a bug with the support code, and not with
92genkernel, please file a bug at the <uri
93link="http://bugs.gentoo.org">Gentoo Bugzilla.</uri>
94</p> 91</p>
95 92
96</body> 93</body>
97</section> 94</section>
98</chapter> 95</chapter>
150 <li> 147 <li>
151 <b>--kernel-ld=<c>someLinker</c></b>: This specifies a linker which would 148 <b>--kernel-ld=<c>someLinker</c></b>: This specifies a linker which would
152 be used for compiling your kernel. 149 be used for compiling your kernel.
153 </li> 150 </li>
154 <li> 151 <li>
155 <b>--kernel-make=<c>someMake</c></b>: This specifies an alternate GNU Make 152 <b>--kernel-make=<c>someMake</c></b>: This specifies an alternate GNU make
156 which would be used for compiling your kernel. 153 which would be used for compiling your kernel.
157 </li> 154 </li>
158</ul> 155</ul>
159 156
160<ul> 157<ul>
169 <li> 166 <li>
170 <b>--utils-ld=<c>someLinker</c></b>: This specifies a linker which would be 167 <b>--utils-ld=<c>someLinker</c></b>: This specifies a linker which would be
171 used for compiling the support utilities. 168 used for compiling the support utilities.
172 </li> 169 </li>
173 <li> 170 <li>
174 <b>--utils-make=<c>someMake</c></b>: This specifies an alternate GNU Make 171 <b>--utils-make=<c>someMake</c></b>: This specifies an alternate GNU make
175 which would be used for compiling the support utilities. 172 which would be used for compiling the support utilities.
176 </li> 173 </li>
177</ul> 174</ul>
178 175
179<ul> 176<ul>
180 <li> 177 <li>
181 <b>--makeopts=<c>-jJobs</c></b>: This specifies the flags which would be 178 <b>--makeopts=<c>-jJobs</c></b>: This specifies the flags which would be
182 passed to GNU Make when the kernel and utilities are being compiled. 179 passed to GNU make when the kernel and utilities are being compiled.
183 </li> 180 </li>
184</ul> 181</ul>
185 182
186</body> 183</body>
187</section> 184</section>
199 <li> 196 <li>
200 <b>--callback="echo Hello"</b>: This routine calls the specified 197 <b>--callback="echo Hello"</b>: This routine calls the specified
201 arguments after the kernel and the relevant modules have been built; but 198 arguments after the kernel and the relevant modules have been built; but
202 before the initrd has been built. This is useful where you might want 199 before the initrd has been built. This is useful where you might want
203 external modules installed to the initrd by emerging the relevant item 200 external modules installed to the initrd by emerging the relevant item
204 using the callback and then redefinining a Genkernel module group. 201 using the callback and then redefinining a genkernel module group.
205 </li> 202 </li>
206 <li> 203 <li>
207 <b>--<c>no-</c>clean</b>: This runs <e>or does not 204 <b>--<c>no-</c>clean</b>: This runs <e>or does not
208 run</e> <c>make clean</c> before compiling your kernel. This 205 run</e> <c>make clean</c> before compiling your kernel. This
209 causes all object files and dependencies to be removed. 206 causes all object files and dependencies to be removed.
210 </li> 207 </li>
211 <li> 208 <li>
212 <b>--<c>no-</c>mrproper</b>: This runs <e>or does not 209 <b>--<c>no-</c>mrproper</b>: This runs <e>or does not
213 run</e> <c>make mrproper</c> before compiling your kernel. This 210 run</e> <c>make mrproper</c> before compiling your kernel. This
214 causes all object files, dependencies <b> and your 211 causes all object files, dependencies <b>and your
215 configuration</b> to be removed. 212 configuration</b> to be removed.
216 </li> 213 </li>
217</ul> 214</ul>
218 215
219<ul> 216<ul>
238 also required. 235 also required.
239 </li> 236 </li>
240 <li> 237 <li>
241 <b>--<c>no-</c>menuconfig</b>: This runs <e>or does not run</e> the kernel 238 <b>--<c>no-</c>menuconfig</b>: This runs <e>or does not run</e> the kernel
242 menu-based configurator before building your kernel, after <c>make 239 menu-based configurator before building your kernel, after <c>make
243 oldconfig</c> has ran. 240 oldconfig</c> has run.
244 </li> 241 </li>
245</ul> 242</ul>
246 243
247<ul> 244<ul>
248 <li> 245 <li>
291<ul> 288<ul>
292 <li> 289 <li>
293 <b>--minkernpackage=<path>/output/to/yourkernel.tar.bz2</path></b>: This 290 <b>--minkernpackage=<path>/output/to/yourkernel.tar.bz2</path></b>: This
294 flag outputs a tarball of the kernel, named as <path>kernel</path> and the 291 flag outputs a tarball of the kernel, named as <path>kernel</path> and the
295 initrd named as <path>initrd</path> to the specified file. No path 292 initrd named as <path>initrd</path> to the specified file. No path
296 information or modules will be includes in the tarball. 293 information or modules will be included in the tarball.
297 </li> 294 </li>
298</ul> 295</ul>
299 296
300</body> 297</body>
301</section> 298</section>
308necessary flags as root. For example: 305necessary flags as root. For example:
309</p> 306</p>
310 307
311<pre caption="Running genkernel"> 308<pre caption="Running genkernel">
312# genkernel --menuconfig --no-clean --no-install --bootsplash all 309# genkernel --menuconfig --no-clean --no-install --bootsplash all
313<comment>(Would produce a kernel, asking you what how to configure it 310<comment>(Would produce a kernel, asking you how to configure it
314to your desire, leaving alone any compiled object files, enabling 311to your desire, leaving alone any compiled object files, enabling
315bootsplash support but not installing anything.)</comment> 312bootsplash support but not installing anything.)</comment>
316</pre> 313</pre>
317 314
318<p> 315<p>
319If you want genkernel to install your kernel as well, you must ensure 316If you want genkernel to install your kernel as well, you must ensure
320that your <path>/boot</path> partition is mounted - recent Genkernels 317that your <path>/boot</path> partition is mounted - recent genkernels
321would automatically attempt to do this for you if MOUNTBOOT is set to 318would automatically attempt to do this for you if MOUNTBOOT is set to
322"yes" in <path>/etc/genkernel.conf</path>. 319"yes" in <path>/etc/genkernel.conf</path>.
323</p> 320</p>
324 321
325<pre caption="Mounting your /boot manually"> 322<pre caption="Mounting your /boot manually">
347 Add <c>root=/dev/ram0</c> and <c>init=/linuxrc</c> to the 344 Add <c>root=/dev/ram0</c> and <c>init=/linuxrc</c> to the
348 kernel parameters passed to the kernel image. 345 kernel parameters passed to the kernel image.
349 </li> 346 </li>
350 <li> 347 <li>
351 Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters 348 Add <c>real_root=/dev/hda3</c>, for example, to the kernel parameters
352 passed to the kernel image if <path>/dev/hda3</path> contains your root 349 passed to the kernel image, if <path>/dev/hda3</path> contains your root
353 partition. 350 partition.
354 </li> 351 </li>
355 <li> 352 <li>
356 If you are using bootsplash, add a suitable modeline such as 353 If you are using bootsplash, add a suitable modeline such as
357 <c>vga=0x317</c> to the parameters passed to the kernel and also add 354 <c>vga=0x317</c> to the parameters passed to the kernel and also add
370<section> 367<section>
371<title>Kernel Configuration Files</title> 368<title>Kernel Configuration Files</title>
372<body> 369<body>
373 370
374<p> 371<p>
375genkernel will save your kernel config in <path>/etc/kernels</path> and use that 372Genkernel will save your kernel config in <path>/etc/kernels</path> and use that
376config whenever you issue <c>genkernel</c> again. If you want to start off again 373config whenever you issue <c>genkernel</c> again. If you want to start off again
377with the defaults, rename the file in <path>/etc/kernels</path>. genkernel will 374with the defaults, rename the file in <path>/etc/kernels</path>. Genkernel will
378then use the kernel config located in 375then use the kernel config located in
379<path>/usr/share/genkernel/&lt;arch&gt;</path> instead. 376<path>/usr/share/genkernel/&lt;arch&gt;</path> instead.
380</p> 377</p>
381 378
382</body> 379</body>
389<title>Introduction</title> 386<title>Introduction</title>
390<body> 387<body>
391 388
392<p> 389<p>
393Provided your architecture has all the required libraries and utilties 390Provided your architecture has all the required libraries and utilties
394which genkernel requires, which includes but it not limited to a 391which genkernel requires, which includes but it is not limited to a
395working kernel for your architecture, working compiler suite, GNU 392working kernel for your architecture, working compiler suite, GNU
396Make, and a working busybox distribution, you're all set to go! 393make, and a working busybox distribution, you're all set to go!
397</p> 394</p>
398 395
399<p> 396<p>
400For each architecture, genkernel uses 397For each architecture, genkernel uses
401<path>/usr/share/genkernel/archName</path> for configuration files for 398<path>/usr/share/genkernel/$archName</path> for configuration files for
402that architecture. 399that architecture.
403</p> 400</p>
404 401
405</body> 402</body>
406</section> 403</section>

Legend:
Removed from v.1.10  
changed lines
  Added in v.1.14

  ViewVC Help
Powered by ViewVC 1.1.20