Author: jim Date: 2005-04-25 20:26:05 -0600 (Mon, 25 Apr 2005) New Revision: 5083
Added: branches/cross-lfs/BOOK/reboot/colo.xml branches/cross-lfs/BOOK/reboot/grub.xml branches/cross-lfs/BOOK/reboot/kernel-alpha.xml branches/cross-lfs/BOOK/reboot/kernel-ppc.xml branches/cross-lfs/BOOK/reboot/kernel-raq2.xml branches/cross-lfs/BOOK/reboot/kernel.xml branches/cross-lfs/BOOK/reboot/yaboot.xml Modified: branches/cross-lfs/BOOK/introduction/changelog.xml branches/cross-lfs/BOOK/reboot/chapter.xml Log: Added: Final stuff to reboot, still needs to be edited and tested Modified: branches/cross-lfs/BOOK/introduction/changelog.xml =================================================================== --- branches/cross-lfs/BOOK/introduction/changelog.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/introduction/changelog.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -116,6 +116,7 @@ <listitem><para>Fixed Creating directories in reboot.</para></listitem> <listitem><para>Fixed Essential symlinks in reboot.</para></listitem> <listitem><para>Added udev in reboot.</para></listitem> +<listitem><para>Adding the kernel and bootloaders to finish the reboot section.</para></listitem> </itemizedlist> </listitem> </itemizedlist> Modified: branches/cross-lfs/BOOK/reboot/chapter.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/chapter.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/chapter.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -16,5 +16,12 @@ <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="creatingdirs.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="createfiles.xml"/> <xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="pwdgroup.xml"/> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="kernel.xml"/> <!-- x86 --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="kernel-alpha.xml"/> <!-- alpha --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="kernel-ppc.xml"/> <!-- ppc --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="kernel-raq2.xml"/> <!-- raq2 --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="grub.xml"/> <!-- x86 --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="yaboot.xml"/> <!-- ppc --> +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; href="colo.xml"/> <!-- raq2 --> </chapter> Added: branches/cross-lfs/BOOK/reboot/colo.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/colo.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/colo.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,51 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-colo" arch="raq2"> +<title>Making the LFS system bootable</title> +<?dbhtml filename="colo.html"?> + +<indexterm zone="ch-reboot-colo"> +<primary sortas="a-Colo">Colo</primary> +<secondary>configuring</secondary></indexterm> + +<para>Your shiny new LFS system is almost complete. One of the last things to +do is ensure you can boot it. The instructions below apply only to +Colbalt RaQ2/Cube2 servers. Information on <quote>boot +loading</quote> for other architectures should be available in the usual +resource-specific locations for those architectures.</para> + +<para>Boot loading can be a complex area. First, a few cautionary words. You +really should be familiar with your current boot loader and any other +operating systems present on your hard drive(s) that you might wish to keep +bootable. Please make sure that you have an emergency boot disk ready, so that +you can rescue your computer if, by any chance, your computer becomes unusable +(un-bootable).</para> + +<para>Earlier, we compiled and installed the Cobalt boot loader software in +preparation for this step. Now we will configure our system to boot using +Colo. Here is a simpe default.colo to use.</para> + +<screen><userinput>cat > /boot/default.colo << "EOF" +#:CoLo:# +# +# load linux +# +lcd 'Booting 2.6.9...' +load vmlinux-2.6.9.gz +execute root=/dev/hda2 console=ttyS0,115200 ide1=noprobe +EOF</userinput></screen> + +<para>Included in /usr/lib/colo/examples are more examples of a +default.colo file.</para> + +<para>The FHS stipulates that Bootloader's configuration file should be symlinked to +/etc/{Bootloader Name}. To satisfy this requirement for colo, issue the +following command:</para> + +<screen><userinput>mkdir /etc/colo && +ln -s /boot/colo/default.colo /etc/colo</userinput></screen> + +</sect1> Added: branches/cross-lfs/BOOK/reboot/grub.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/grub.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/grub.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,138 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-grub" arch="x86"> +<title>Making the LFS System Bootable</title> +<?dbhtml filename="grub.html"?> + +<indexterm zone="ch-reboot-grub"> +<primary sortas="a-Grub">Grub</primary> +<secondary>configuring</secondary></indexterm> + +<para>Your shiny new LFS system is almost complete. One of the last +things to do is to ensure that the system can be properly booted. The +instructions below apply only to computers of IA-32 architecture, +meaning mainstream PCs. Information on <quote>boot loading</quote> for +other architectures should be available in the usual resource-specific +locations for those architectures.</para> + +<para>Boot loading can be a complex area, so a few cautionary +words are in order. Be familiar with the current boot loader and any other +operating systems present on the hard drive(s) that need to be +bootable. Make sure that an emergency boot disk is ready to +<quote>rescue</quote> the computer if the computer becomes +unusable (un-bootable).</para> + +<para>Earlier, we compiled and installed the Grub boot loader software +in preparation for this step. The procedure involves writing some +special Grub files to specific locations on the hard drive. We highly +recommend creating a Grub boot floppy diskette as a backup. Insert a +blank floppy diskette and run the following commands:</para> + +<screen><userinput>dd if=/boot/grub/stage1 of=/dev/fd0 bs=512 count=1 +dd if=/boot/grub/stage2 of=/dev/fd0 bs=512 seek=1</userinput></screen> + +<para>Remove the diskette and store it somewhere safe. Now, run the +<command>grub</command> shell:</para> + +<screen><userinput>grub</userinput></screen> + +<para>Grub uses its own naming structure for drives and partitions in +the form of <emphasis>(hdn,m)</emphasis>, where <emphasis>n</emphasis> +is the hard drive number and <emphasis>m</emphasis> is the partition +number, both starting from zero. For example, partition <filename +class="partition">hda1</filename> is <emphasis>(hd0,0)</emphasis> to +Grub and <filename class="partition">hdb3</filename> is +<emphasis>(hd1,2)</emphasis>. In contrast to Linux, Grub does not +consider CD-ROM drives to be hard drives. For example, if using a CD +on <filename class="partition">hdb</filename> and a second hard drive +on <filename class="partition">hdc</filename>, that second hard drive +would still be <emphasis>(hd1)</emphasis>.</para> + +<para>Using the above information, determine the appropriate +designator for the root partition (or boot partition, if a separate +one is used). For the following example, it is assumed that the root +(or separate boot) partition is <filename +class="partition">hda4</filename>.</para> + +<para>Tell Grub where to search for its +<filename>stage{1,2}</filename> files. The Tab key can be used +everywhere to make Grub show the alternatives:</para> + +<screen><userinput>root (hd0,3)</userinput></screen> + + +<warning><para>The following command will overwrite the current boot +loader. Do not run the command if this is not desired, for example, if +using a third party boot manager to manage the Master Boot Record +(MBR). In this scenario, it would make more sense to install +Grub into the <quote>boot sector</quote> of the LFS partition. In this +case, this next command would become <userinput>setup +(hd0,3)</userinput>.</para></warning> + +<para>Tell Grub to install itself into the MBR of +<filename class="partition">hda</filename>:</para> + +<screen><userinput>setup (hd0)</userinput></screen> + +<para>If all went well, Grub will have reported finding its files in +<filename class="directory">/boot/grub</filename>. That's all there is +to it. Quit the <command>grub</command> shell:</para> + +<screen><userinput>quit</userinput></screen> + +<para>Create a <quote>menu list</quote> file defining Grub's boot menu:</para> + +<screen><userinput>cat > /boot/grub/menu.lst << "EOF" +<literal># Begin /boot/grub/menu.lst + +# By default boot the first menu entry. +default 0 + +# Allow 30 seconds before booting the default. +timeout 30 + +# Use prettier colors. +color green/black light-green/black + +# The first entry is for LFS. +title LFS &version; +root (hd0,3) +kernel /boot/lfskernel-&linux-version; root=/dev/hda4</literal> +EOF</userinput></screen> + + +<para>Add an entry for the host distribution if desired. It might look +like this:</para> + +<screen><userinput>cat >> /boot/grub/menu.lst << "EOF" +<literal>title Red Hat +root (hd0,2) +kernel /boot/kernel-2.6.5 root=/dev/hda3 +initrd /boot/initrd-2.6.5</literal> +EOF</userinput></screen> + +<para>If dual-booting Windows, the following entry will allow +booting it:</para> + +<screen><userinput>cat >> /boot/grub/menu.lst << "EOF" +<literal>title Windows +rootnoverify (hd0,0) +chainloader +1</literal> +EOF</userinput></screen> + +<para>If <command>info grub</command> does not provide all necessary material, additional +information regarding Grub is located on its website at: +<ulink url="http://www.gnu.org/software/grub/"/>.</para> + +<para>The FHS stipulates that Bootloader's configuration file should be symlinked to +/etc/{Bootloader Name}. To satisfy this requirement for grub, issue the +following command:</para> + +<screen><userinput>mkdir /etc/grub && +ln -s /boot/grub/menu.lst /etc/grub</userinput></screen> + +</sect1> + Added: branches/cross-lfs/BOOK/reboot/kernel-alpha.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/kernel-alpha.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/kernel-alpha.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,165 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-kernel" role="wrap" arch="alpha"> +<title>Linux-&linux-alpha-version;</title> +<?dbhtml filename="kernel.html"?> + +<indexterm zone="ch-reboot-kernel"><primary sortas="a-Linux">Linux</primary></indexterm> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'package'])"/> + +<sect2 role="installation"> +<title>Installation of the kernel</title> + +<para>Building the kernel involves a few steps—configuration, +compilation, and installation. Read the <filename>README</filename> +file in the kernel source tree for alternate methods to the way this +book configures the kernel.</para> + +<para>Prepare for compilation by running the following command:</para> + +<screen><userinput>make mrproper</userinput></screen> + +<para>This ensures that the kernel tree is absolutely clean. The +kernel team recommends that this command be issued prior to each +kernel compilation. Do not rely on the source tree being clean after +un-tarring.</para> + +<para>Also, ensure that the kernel does not attempt to pass +hotplugging events to userspace until userspace specifies that it is +ready:</para> + +<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> + +<para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to +compile the keymap into the kernel, issue the command below:</para> + +<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ + drivers/char/defkeymap.c</userinput></screen> + +<para>For example, if using a Dutch keyboard, use +<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para> + +<para>Configure the kernel via a menu-driven interface:</para> + +<screen><userinput>make menuconfig</userinput></screen> + +<para>Alternatively, <command>make oldconfig</command> may be more appropriate in some +situations. <phrase>This will build a basic system with no modules and +ext2 support only.</phrase> See the <filename>README</filename> file for more +information.</para> + +<para>If desired, skip kernel configuration by copying the kernel +config file, <filename>.config</filename>, from the host system +(assuming it is available) to the unpacked <filename +class="directory">linux-&linux-alpha-version;</filename> directory. However, +we do not recommend this option. It is often better to explore all the +configuration menus and create the kernel configuration from +scratch.</para> + +<para>For POSIX-shared memory support, ensure that the kernel config +option <quote>Virtual memory file system support</quote> is enabled. +It resides within the <quote>File systems</quote> menu and is normally +enabled by default.</para> + +<para>LFS bootscripts make the assumption that either both +<quote>Support for Host-side USB</quote> and <quote>USB device +filesystem</quote> have been compiled directly into the kernel, or +that neither is compiled at all. Bootscripts will not work properly +if it is a module (usbcore.ko).</para> + +<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in +this case &gcc-version;. Compiling with 2.95.x is known to cause failures in +the glibc test suite, so it is not recommended to compile the kernel +with gcc 2.95.x.</para></note> + +<para>Compile the kernel image and modules:</para> + +<screen><userinput>make</userinput></screen> + +<para>If using kernel modules, an +<filename>/etc/modprobe.conf</filename> file may be needed. +Information pertaining to modules and kernel configuration is +located in the kernel documentation in the <filename +class="directory">linux-&linux-alpha-version;/Documentation</filename> +directory. The <emphasis>modprobe.conf</emphasis> man page may also be +of interest.</para> + +<para>Be very careful when reading other documentation because it +usually applies to 2.4.x kernels only. As far as we know, kernel +configuration issues specific to Hotplug and Udev are not documented. +The problem is that Udev will create a device node only if Hotplug or +a user-written script inserts the corresponding module into the +kernel, and not all modules are detectable by Hotplug. Note that +statements like the one below in the +<filename>/etc/modprobe.conf</filename> file do not work with +Udev:</para> + +<para><screen>alias char-major-XXX some-module</screen></para> + +<para>Because of the complications with Hotplug, Udev, and modules, we +strongly recommend starting with a completely non-modular kernel +configuration, especially if this is the first time using Udev.</para> + +<para>Install the modules, if the kernel configuration uses them:</para> + +<screen><userinput>make modules_install</userinput></screen> + +<para>If there are many modules and very little space, consider +stripping and compressing the modules. For most users, such +compression is not worth the time, but if the system is pressed for +space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> + +<para>After kernel compilation is complete, additional steps are +required to complete the installation. Some files need to be copied to +the <filename class="directory">/boot</filename> directory.</para> + +<para><!--The path to the kernel image may vary depending on the platform +being used. -->Issue the following command to install the kernel:</para> + +<screen><userinput>cp vmlinux /boot/vmlinux-&linux-version;</userinput></screen> + +<para><filename>System.map</filename> is a symbol file for the kernel. +It maps the function entry points of every function in the kernel API, +as well as the addresses of the kernel data structures for the running +kernel. Issue the following command to install the map file:</para> + +<screen><userinput>cp System.map /boot/System.map-&linux-alpha-version;</userinput></screen> + +<para>The kernel configuration file <filename>.config</filename> +produced by the <command>make menuconfig</command> step +above contains all the configuration selections for the kernel +that was just compiled. It is a good idea to keep this file for future +reference:</para> + +<screen><userinput>cp .config /boot/config-&linux-alpha-version;</userinput></screen> + +<para>It is important to note that the files in the kernel source +directory are not owned by <emphasis>root</emphasis>. Whenever a +package is unpacked as user <emphasis>root</emphasis> (like we did +inside chroot), the files have the user and group IDs of whatever +they were on the packager's computer. This is usually not a problem +for any other package to be installed because the source tree is +removed after the installation. However, the Linux source tree is +often retained for a long time. Because of this, there is a chance +that whatever user ID the packager used will be assigned to somebody +on the machine. That person would then have write access to the kernel +source.</para> + +<para>If the kernel source tree is going to retained, run +<command>chown -R 0:0</command> on the <filename +class="directory">linux-&linux-alpha-version;</filename> directory to ensure +all files are owned by user <emphasis>root</emphasis>.</para> +</sect2> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'content'])"/> + +</sect1> + Added: branches/cross-lfs/BOOK/reboot/kernel-ppc.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/kernel-ppc.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/kernel-ppc.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,173 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-kernel" role="wrap" arch="ppc"> +<title>Linux-&linux-version;</title> +<?dbhtml filename="kernel.html"?> + +<indexterm zone="ch-reboot-kernel"><primary sortas="a-Linux">Linux</primary></indexterm> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'package'])"/> + +<sect2 role="installation"> +<title>Installation of the kernel</title> + +<para>Building the kernel involves a few steps—configuration, +compilation, and installation. Read the <filename>README</filename> +file in the kernel source tree for alternate methods to the way this +book configures the kernel.</para> + +<para>Prepare for compilation by running the following command:</para> + +<screen><userinput>make mrproper</userinput></screen> + +<para>This ensures that the kernel tree is absolutely clean. The +kernel team recommends that this command be issued prior to each +kernel compilation. Do not rely on the source tree being clean after +un-tarring.</para> + +<para>Also, ensure that the kernel does not attempt to pass +hotplugging events to userspace until userspace specifies that it is +ready:</para> + +<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> + +<para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to +compile the keymap into the kernel, issue the command below:</para> + +<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ + drivers/char/defkeymap.c</userinput></screen> + +<para>For example, if using a Dutch keyboard, use +<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para> + +<para>Configure the kernel via a menu-driven interface:</para> + +<screen><userinput>make menuconfig</userinput></screen> + +<para>Alternatively, <command>make oldconfig</command> +may be more appropriate in some +situations. <phrase>This will build a basic system with no modules and +ext2 support only.</phrase> See the <filename>README</filename> file for more +information.</para> + +<note><para>When configuring the kernel, be sure to enable the +<quote>Support for hot-pluggable devices</quote> option under the +<quote>General Setup</quote> menu. This enables hotplug events that +are used by <command>udev</command> to populate the <filename +class="directory">/dev</filename> directory with device +nodes.</para></note> + +<para>If desired, skip kernel configuration by copying the kernel +config file, <filename>.config</filename>, from the host system +(assuming it is available) to the unpacked <filename +class="directory">linux-&linux-version;</filename> directory. However, +we do not recommend this option. It is often better to explore all the +configuration menus and create the kernel configuration from +scratch.</para> + +<para>For POSIX-shared memory support, ensure that the kernel config +option <quote>Virtual memory file system support</quote> is enabled. +It resides within the <quote>File systems</quote> menu and is normally +enabled by default.</para> + +<para>LFS bootscripts make the assumption that either both +<quote>Support for Host-side USB</quote> and <quote>USB device +filesystem</quote> have been compiled directly into the kernel, or +that neither is compiled at all. Bootscripts will not work properly +if it is a module (usbcore.ko).</para> + +<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in +this case &gcc-version;. Compiling with 2.95.x is known to cause failures in +the glibc test suite, so it is not recommended to compile the kernel +with gcc 2.95.x.</para></note> + +<para>Compile the kernel image and modules:</para> + +<screen><userinput>make</userinput></screen> + +<para>If using kernel modules, an +<filename>/etc/modprobe.conf</filename> file may be needed. +Information pertaining to modules and kernel configuration is +located in the kernel documentation in the <filename +class="directory">linux-&linux-version;/Documentation</filename> +directory. The <emphasis>modprobe.conf</emphasis> man page may also be +of interest.</para> + +<para>Be very careful when reading other documentation because it +usually applies to 2.4.x kernels only. As far as we know, kernel +configuration issues specific to Hotplug and Udev are not documented. +The problem is that Udev will create a device node only if Hotplug or +a user-written script inserts the corresponding module into the +kernel, and not all modules are detectable by Hotplug. Note that +statements like the one below in the +<filename>/etc/modprobe.conf</filename> file do not work with +Udev:</para> + +<para><screen>alias char-major-XXX some-module</screen></para> + +<para>Because of the complications with Hotplug, Udev, and modules, we +strongly recommend starting with a completely non-modular kernel +configuration, especially if this is the first time using Udev.</para> + +<para>Install the modules, if the kernel configuration uses them:</para> + +<screen><userinput>make modules_install</userinput></screen> + +<para>If there are many modules and very little space, consider +stripping and compressing the modules. For most users, such +compression is not worth the time, but if the system is pressed for +space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> + +<para>After kernel compilation is complete, additional steps are +required to complete the installation. Some files need to be copied to +the <filename class="directory">/boot</filename> directory.</para> + +<para><!--The path to the kernel image may vary depending on the platform +being used. -->Issue the following command to install the kernel:</para> + +<screen><userinput>cp vmlinux /boot/lfskernel-&linux-version;</userinput></screen> + +<para><filename>System.map</filename> is a symbol file for the kernel. +It maps the function entry points of every function in the kernel API, +as well as the addresses of the kernel data structures for the running +kernel. Issue the following command to install the map file:</para> + +<screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen> + +<para>The kernel configuration file <filename>.config</filename> +produced by the <command>make menuconfig</command> step +above contains all the configuration selections for the kernel +that was just compiled. It is a good idea to keep this file for future +reference:</para> + +<screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen> + +<para>It is important to note that the files in the kernel source +directory are not owned by <emphasis>root</emphasis>. Whenever a +package is unpacked as user <emphasis>root</emphasis> (like we did +inside chroot), the files have the user and group IDs of whatever +they were on the packager's computer. This is usually not a problem +for any other package to be installed because the source tree is +removed after the installation. However, the Linux source tree is +often retained for a long time. Because of this, there is a chance +that whatever user ID the packager used will be assigned to somebody +on the machine. That person would then have write access to the kernel +source.</para> + +<para>If the kernel source tree is going to retained, run +<command>chown -R 0:0</command> on the <filename +class="directory">linux-&linux-version;</filename> directory to ensure +all files are owned by user <emphasis>root</emphasis>.</para> +</sect2> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'content'])"/> + +</sect1> + Added: branches/cross-lfs/BOOK/reboot/kernel-raq2.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/kernel-raq2.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/kernel-raq2.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,171 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-kernel" role="wrap" arch="raq2"> +<title>Linux-&linux-raq2-version;</title> +<?dbhtml filename="kernel.html"?> + +<indexterm zone="ch-reboot-kernel"><primary sortas="a-Linux">Linux</primary></indexterm> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'package'])"/> + +<sect2 role="installation"> +<title>Installation of the kernel</title> + +<para>Building the kernel involves a few steps—configuration, +compilation, and installation. Read the <filename>README</filename> +file in the kernel source tree for alternate methods to the way this +book configures the kernel.</para> + +<para>The following patch fixes some issues with MIPS based processors +and the kernel:</para> + +<screen><userinput>patch -Np1 -i ../linux-&linux-raq2-version;-raq2_fix-3.patch</userinput></screen> + +<para>Prepare for compilation by running the following command:</para> + +<screen><userinput>make mrproper</userinput></screen> + +<para>This ensures that the kernel tree is absolutely clean. The +kernel team recommends that this command be issued prior to each +kernel compilation. Do not rely on the source tree being clean after +un-tarring.</para> + +<para>Also, ensure that the kernel does not attempt to pass +hotplugging events to userspace until userspace specifies that it is +ready:</para> + +<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> + +<para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to +compile the keymap into the kernel, issue the command below:</para> + +<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ + drivers/char/defkeymap.c</userinput></screen> + +<para>For example, if using a Dutch keyboard, use +<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para> + +<para>Configure the kernel via a menu-driven interface:</para> + +<screen><userinput>make menuconfig</userinput></screen> + +<para>Alternatively, <command>make cobalt_defconfig</command> may be more appropriate in some +situations. <phrase>This will build a basic system with no modules and +ext2 support only.</phrase> See the <filename>README</filename> file for more +information.</para> + +<para>If desired, skip kernel configuration by copying the kernel +config file, <filename>.config</filename>, from the host system +(assuming it is available) to the unpacked <filename +class="directory">linux-&linux-raq2-version;</filename> directory. However, +we do not recommend this option. It is often better to explore all the +configuration menus and create the kernel configuration from +scratch.</para> + +<para>For POSIX-shared memory support, ensure that the kernel config +option <quote>Virtual memory file system support</quote> is enabled. +It resides within the <quote>File systems</quote> menu and is normally +enabled by default.</para> + +<para>LFS bootscripts make the assumption that either both +<quote>Support for Host-side USB</quote> and <quote>USB device +filesystem</quote> have been compiled directly into the kernel, or +that neither is compiled at all. Bootscripts will not work properly +if it is a module (usbcore.ko).</para> + +<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in +this case &gcc-version;. Compiling with 2.95.x is known to cause failures in +the glibc test suite, so it is not recommended to compile the kernel +with gcc 2.95.x.</para></note> + +<para>Compile the kernel image and modules:</para> + +<screen><userinput>make</userinput></screen> + +<para>If using kernel modules, an +<filename>/etc/modprobe.conf</filename> file may be needed. +Information pertaining to modules and kernel configuration is +located in the kernel documentation in the <filename +class="directory">linux-&linux-raq2-version;/Documentation</filename> +directory. The <emphasis>modprobe.conf</emphasis> man page may also be +of interest.</para> + +<para>Be very careful when reading other documentation because it +usually applies to 2.4.x kernels only. As far as we know, kernel +configuration issues specific to Hotplug and Udev are not documented. +The problem is that Udev will create a device node only if Hotplug or +a user-written script inserts the corresponding module into the +kernel, and not all modules are detectable by Hotplug. Note that +statements like the one below in the +<filename>/etc/modprobe.conf</filename> file do not work with +Udev:</para> + +<para><screen>alias char-major-XXX some-module</screen></para> + +<para>Because of the complications with Hotplug, Udev, and modules, we +strongly recommend starting with a completely non-modular kernel +configuration, especially if this is the first time using Udev.</para> + +<para>Install the modules, if the kernel configuration uses them:</para> + +<screen><userinput>make modules_install</userinput></screen> + +<para>If there are many modules and very little space, consider +stripping and compressing the modules. For most users, such +compression is not worth the time, but if the system is pressed for +space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> + +<para>After kernel compilation is complete, additional steps are +required to complete the installation. Some files need to be copied to +the <filename class="directory">/boot</filename> directory.</para> + +<para><!--The path to the kernel image may vary depending on the platform +being used. -->Issue the following command to install the kernel:</para> + +<screen><userinput>cp vmlinux /boot/vmlinux-&linux-version; +gzip -9 /boot/vmlinux-&linux-version;</userinput></screen> + +<para><filename>System.map</filename> is a symbol file for the kernel. +It maps the function entry points of every function in the kernel API, +as well as the addresses of the kernel data structures for the running +kernel. Issue the following command to install the map file:</para> + +<screen><userinput>cp System.map /boot/System.map-&linux-raq2-version;</userinput></screen> + +<para>The kernel configuration file <filename>.config</filename> +produced by the <command>make menuconfig</command> step +above contains all the configuration selections for the kernel +that was just compiled. It is a good idea to keep this file for future +reference:</para> + +<screen><userinput>cp .config /boot/config-&linux-raq2-version;</userinput></screen> + +<para>It is important to note that the files in the kernel source +directory are not owned by <emphasis>root</emphasis>. Whenever a +package is unpacked as user <emphasis>root</emphasis> (like we did +inside chroot), the files have the user and group IDs of whatever +they were on the packager's computer. This is usually not a problem +for any other package to be installed because the source tree is +removed after the installation. However, the Linux source tree is +often retained for a long time. Because of this, there is a chance +that whatever user ID the packager used will be assigned to somebody +on the machine. That person would then have write access to the kernel +source.</para> + +<para>If the kernel source tree is going to retained, run +<command>chown -R 0:0</command> on the <filename +class="directory">linux-&linux-raq2-version;</filename> directory to ensure +all files are owned by user <emphasis>root</emphasis>.</para> +</sect2> + +<xi:include xmlns:xi="http://www.w3.org/2003/XInclude"; + href="kernel.xml" + xpointer="xpointer(/sect1/[EMAIL PROTECTED]'content'])"/> + +</sect1> + Added: branches/cross-lfs/BOOK/reboot/kernel.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/kernel.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/kernel.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,234 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-reboot-kernel" role="wrap" arch="x86"> +<title>Linux-&linux-version;</title> +<?dbhtml filename="kernel.html"?> + +<indexterm zone="ch-reboot-kernel"><primary sortas="a-Linux">Linux</primary></indexterm> + +<sect2 role="package"><title/> +<para>The Linux package contains the kernel and the header files.</para> + +<segmentedlist> +<segtitle>&buildtime;</segtitle> +<segtitle>&diskspace;</segtitle> +<seglistitem><seg>4.20 SBU</seg> +<seg>181 MB</seg></seglistitem> +</segmentedlist> + +<segmentedlist> +<segtitle>&dependencies;</segtitle> +<seglistitem><seg>Bash, Binutils, Coreutils, Findutils, +GCC, Glibc, Grep, Gzip, Make, Modutils, Perl, and Sed</seg></seglistitem> +</segmentedlist> +</sect2> + +<sect2 role="installation"> +<title>Installation of the kernel</title> + +<para>Building the kernel involves a few steps—configuration, +compilation, and installation. Read the <filename>README</filename> +file in the kernel source tree for alternate methods to the way this +book configures the kernel.</para> + +<para>Prepare for compilation by running the following command:</para> + +<screen><userinput>make mrproper</userinput></screen> + +<para>This ensures that the kernel tree is absolutely clean. The +kernel team recommends that this command be issued prior to each +kernel compilation. Do not rely on the source tree being clean after +un-tarring.</para> + +<para>Also, ensure that the kernel does not attempt to pass +hotplugging events to userspace until userspace specifies that it is +ready:</para> + +<screen><userinput>sed -i 's@/sbin/hotplug@/bin/true@' kernel/kmod.c</userinput></screen> + +<para>If, in <xref linkend="ch-scripts-console" role=","/> it was decided to +compile the keymap into the kernel, issue the command below:</para> + +<screen><userinput>loadkeys -m /usr/share/kbd/keymaps/<replaceable>[path to keymap]</replaceable> > \ + drivers/char/defkeymap.c</userinput></screen> + +<para>For example, if using a Dutch keyboard, use +<filename>/usr/share/kbd/keymaps/i386/qwerty/nl.map.gz</filename>.</para> + +<para>Configure the kernel via a menu-driven interface:</para> + +<screen><userinput>make menuconfig</userinput></screen> + +<para>Alternatively, <command>make oldconfig</command> +may be more appropriate in some +situations. <phrase>This will build a basic system with no modules and +ext2 support only.</phrase> See the <filename>README</filename> file for more +information.</para> + +<note><para>When configuring the kernel, be sure to enable the +<quote>Support for hot-pluggable devices</quote> option under the +<quote>General Setup</quote> menu. This enables hotplug events that +are used by <command>udev</command> to populate the <filename +class="directory">/dev</filename> directory with device +nodes.</para></note> + +<para>If desired, skip kernel configuration by copying the kernel +config file, <filename>.config</filename>, from the host system +(assuming it is available) to the unpacked <filename +class="directory">linux-&linux-version;</filename> directory. However, +we do not recommend this option. It is often better to explore all the +configuration menus and create the kernel configuration from +scratch.</para> + +<para>For POSIX-shared memory support, ensure that the kernel config +option <quote>Virtual memory file system support</quote> is enabled. +It resides within the <quote>File systems</quote> menu and is normally +enabled by default.</para> + +<para>LFS bootscripts make the assumption that either both +<quote>Support for Host-side USB</quote> and <quote>USB device +filesystem</quote> have been compiled directly into the kernel, or +that neither is compiled at all. Bootscripts will not work properly +if it is a module (usbcore.ko).</para> + +<note><para>NPTL requires the kernel to be compiled with GCC 3.x, in +this case &gcc-version;. Compiling with 2.95.x is known to cause failures in +the glibc test suite, so it is not recommended to compile the kernel +with gcc 2.95.x.</para></note> + +<para>Compile the kernel image and modules:</para> + +<screen><userinput>make</userinput></screen> + +<para>If using kernel modules, an +<filename>/etc/modprobe.conf</filename> file may be needed. +Information pertaining to modules and kernel configuration is +located in the kernel documentation in the <filename +class="directory">linux-&linux-version;/Documentation</filename> +directory. The <emphasis>modprobe.conf</emphasis> man page may also be +of interest.</para> + +<para>Be very careful when reading other documentation because it +usually applies to 2.4.x kernels only. As far as we know, kernel +configuration issues specific to Hotplug and Udev are not documented. +The problem is that Udev will create a device node only if Hotplug or +a user-written script inserts the corresponding module into the +kernel, and not all modules are detectable by Hotplug. Note that +statements like the one below in the +<filename>/etc/modprobe.conf</filename> file do not work with +Udev:</para> + +<para><screen>alias char-major-XXX some-module</screen></para> + +<para>Because of the complications with Hotplug, Udev, and modules, we +strongly recommend starting with a completely non-modular kernel +configuration, especially if this is the first time using Udev.</para> + +<para>Install the modules, if the kernel configuration uses them:</para> + +<screen><userinput>make modules_install</userinput></screen> + +<para>If there are many modules and very little space, consider +stripping and compressing the modules. For most users, such +compression is not worth the time, but if the system is pressed for +space, see <ulink url="http://www.linux-mips.org/archives/linux-mips/2002-04/msg00031.html"/>.</para> + +<para>After kernel compilation is complete, additional steps are +required to complete the installation. Some files need to be copied to +the <filename class="directory">/boot</filename> directory.</para> + +<para><!--The path to the kernel image may vary depending on the platform +being used. -->Issue the following command to install the kernel:</para> + +<screen><userinput>cp arch/i386/boot/bzImage /boot/lfskernel-&linux-version;</userinput></screen> + +<para><filename>System.map</filename> is a symbol file for the kernel. +It maps the function entry points of every function in the kernel API, +as well as the addresses of the kernel data structures for the running +kernel. Issue the following command to install the map file:</para> + +<screen><userinput>cp System.map /boot/System.map-&linux-version;</userinput></screen> + +<para>The kernel configuration file <filename>.config</filename> +produced by the <command>make menuconfig</command> step +above contains all the configuration selections for the kernel +that was just compiled. It is a good idea to keep this file for future +reference:</para> + +<screen><userinput>cp .config /boot/config-&linux-version;</userinput></screen> + +<para>It is important to note that the files in the kernel source +directory are not owned by <emphasis>root</emphasis>. Whenever a +package is unpacked as user <emphasis>root</emphasis> (like we did +inside chroot), the files have the user and group IDs of whatever +they were on the packager's computer. This is usually not a problem +for any other package to be installed because the source tree is +removed after the installation. However, the Linux source tree is +often retained for a long time. Because of this, there is a chance +that whatever user ID the packager used will be assigned to somebody +on the machine. That person would then have write access to the kernel +source.</para> + +<para>If the kernel source tree is going to retained, run +<command>chown -R 0:0</command> on the <filename +class="directory">linux-&linux-version;</filename> directory to ensure +all files are owned by user <emphasis>root</emphasis>.</para> +</sect2> + + +<sect2 id="contents-kernel" role="content"><title>Contents of Linux</title> + +<segmentedlist> +<segtitle>Installed files</segtitle> +<seglistitem><seg>kernel, kernel headers, +and System.map</seg></seglistitem> +</segmentedlist> + +<variablelist><bridgehead renderas="sect3">Short Descriptions</bridgehead> +<?dbfo list-presentation="list"?> +<?dbhtml list-presentation="table"?> + +<varlistentry id="kernel"> +<term><filename>kernel</filename></term> +<listitem> +<para>The engine of the Linux system. When turning on the computer, +the kernel is the first part of the operating system that gets loaded. +It detects and initializes all components of the computer's hardware, +then makes these components available as a tree of files to the +software and turns a single CPU into a multitasking machine capable +of running scores of programs seemingly at the same time.</para> +<indexterm zone="ch-reboot-kernel kernel"><primary sortas="b-kernel">kernel</primary></indexterm> +</listitem> +</varlistentry> + +<varlistentry id="kernel-headers"> +<term><filename>kernel headers</filename></term> +<listitem> +<para>Defines the interface to the services that the kernel provides. +The headers in the system's <filename +class="directory">include</filename> directory should +<emphasis>always</emphasis> be the ones against which Glibc was +compiled and therefore, should <emphasis>not</emphasis> be replaced +when upgrading the kernel.</para> +<indexterm zone="ch-reboot-kernel kernel-headers"><primary sortas="e-kernel-headers">kernel headers</primary></indexterm> +</listitem> +</varlistentry> + +<varlistentry id="System.map"> +<term><filename>System.map</filename></term> +<listitem> +<para>A list of addresses and symbols; it maps the entry points and +addresses of all the functions and data structures in the +kernel</para> +<indexterm zone="ch-reboot-kernel System.map"><primary sortas="e-/boot/System.map">/boot/System.map</primary></indexterm> +</listitem> +</varlistentry> +</variablelist> + +</sect2> + +</sect1> + Added: branches/cross-lfs/BOOK/reboot/yaboot.xml =================================================================== --- branches/cross-lfs/BOOK/reboot/yaboot.xml 2005-04-26 02:21:26 UTC (rev 5082) +++ branches/cross-lfs/BOOK/reboot/yaboot.xml 2005-04-26 02:26:05 UTC (rev 5083) @@ -0,0 +1,15 @@ +<?xml version="1.0" encoding="ISO-8859-1"?> +<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"; [ + <!ENTITY % general-entities SYSTEM "../general.ent"> + %general-entities; +]> +<sect1 id="ch-yaboot-yaboot" arch="ppc"> +<title>Making the LFS system bootable</title> +<?dbhtml filename="yaboot.html"?> + +<indexterm zone="ch-yaboot-yaboot"> +<primary sortas="a-Yaboot">Yaboot</primary> +<secondary>configuring</secondary></indexterm> + +<para>This is a place holder for yaboot</para> +</sect1> -- http://linuxfromscratch.org/mailman/listinfo/lfs-book FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
