|
63.
|
|
|
create a monolithic instead of a modularized kernel
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:528
|
|
65.
|
|
|
learn more about linux kernels
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:538
|
|
68.
|
|
|
To compile a kernel the Debian way, you need some packages: <classname>fakeroot</classname>, <classname>kernel-package</classname>, <classname>linux-source-2.6</classname> and a few others which are probably already installed (see <filename>/usr/share/doc/kernel-package/README.gz</filename> for the complete list).
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:552
|
|
70.
|
|
|
Note that you don't <emphasis>have</emphasis> to compile your kernel the <quote>Debian way</quote>; but we find that using the packaging system to manage your kernel is actually safer and easier. In fact, you can get your kernel sources right from Linus instead of <classname>linux-source-2.6</classname>, yet still use the <classname>kernel-package</classname> compilation method.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:569
|
|
72.
|
|
|
Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory<footnote> <para> There are other locations where you can extract kernel sources and build your custom kernel, but this is easiest as it does not require special permissions. </para> </footnote>. We'll also assume that your kernel version is &kernelversion;. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using <userinput>tar xjf /usr/src/linux-source-&kernelversion;.tar.bz2</userinput> and change to the directory <filename>linux-source-&kernelversion;</filename> that will have been created.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:585
|
|
75.
|
|
|
Now, compile the kernel: <userinput>fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image</userinput>. The version number of <quote>1.0</quote> can be changed at will; this is just a version number that you will use to track your kernel builds. Likewise, you can put any word you like in place of <quote>custom</quote> (e.g., a host name). Kernel compilation may take quite a while, depending on the power of your machine.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:625
|
|
76.
|
|
|
Once the compilation is complete, you can install your custom kernel like any package. As root, do <userinput>dpkg -i ../linux-image-&kernelversion;-<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</userinput>. The <replaceable>subarchitecture</replaceable> part is an optional sub-architecture, <phrase arch="i386"> such as <quote>686</quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -i</userinput> will install the kernel, along with some other nice supporting files. For instance, the <filename>System.map</filename> will be properly installed (helpful for debugging kernel problems), and <filename>/boot/config-&kernelversion;</filename> will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:635
|
|
78.
|
|
|
For more information on Debian kernels and kernel compilation, see the <ulink url="&url-kernel-handbook;">Debian Linux Kernel Handbook</ulink>. For more information on <classname>kernel-package</classname>, read the fine documentation in <filename>/usr/share/doc/kernel-package</filename>.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:660
|
|
79.
|
|
|
Recovering a Broken System
|
|
|
Tag: title
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:676
|
|
80.
|
|
|
Sometimes, things go wrong, and the system you've carefully installed is no longer bootable. Perhaps the boot loader configuration broke while trying out a change, or perhaps a new kernel you installed won't boot, or perhaps cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</filename>. Regardless of the cause, you'll need to have a system to work from while you fix it, and rescue mode can be useful for this.
|
|
|
Tag: para
|
|
|
|
(no translation yet)
|
|
|
|
Located in
post-install.xml:677
|