Attachment 28125 Details for Bug 44807 – Update to user doc

[patch] Update to user doc

2.6-koutput-user.xml-update.diff (text/plain), 4.81 KB, created by Peter Johanson (RETIRED) on 2004-03-26 16:35:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Peter Johanson (RETIRED)

Created: 2004-03-26 16:35:33 UTC

Size: 4.81 KB

patch

obsolete

>Index: 2.6-koutput-user.xml
>===================================================================
>RCS file: /home/cvsroot/gentoo/xml/htdocs/doc/en/2.6-koutput-user.xml,v
>retrieving revision 1.1
>diff -u -b -B -r1.1 2.6-koutput-user.xml
>--- 2.6-koutput-user.xml	26 Mar 2004 00:25:16 -0000	1.1
>+++ 2.6-koutput-user.xml	27 Mar 2004 00:33:41 -0000
>@@ -21,8 +21,8 @@
> 
> <license/>
> 
>-<version>1.0</version>
>-<date>March 14, 2004</date>
>+<version>1.1</version>
>+<date>March 26, 2004</date>
> 
> <chapter>
> <title>Overview</title>
>@@ -86,6 +86,36 @@
> </section>
> </chapter>
> <chapter>
>+<title>Advantages</title>
>+<section>
>+<body>
>+
>+
>+You may be asking yourself, "Why should I bother?" The problem that inspired
>+this functionality was in fact an issue with kernel module ebuilds like
>+nvidia-kernel or hostap-driver. These ebuilds need to use the kernel build
>+system to compile, however building them would require updating files in
>+<path>/usr/src/linux</path>, and fail because of sandbox violations.
>+
>+
>+<note>
>+Gentoo's sandbox is system that prevents portage from writing to the live
>+filesystem until the final merge step of the package installation.
>+</note>
>+
>+
>+Several dependant steps can be taken to resolve this issue. In short, kernel
>+builds must output all of their files to a different location when they are
>+compiled, and later external module compiles must also do this, only they
>+output to some subdirectory of the temporary build location. By letting the
>+modules output their built files into the permitted build location, those nasty
>+sandbox errors are prevented.
>+
>+
>+</body>
>+</section>
>+</chapter>
>+<chapter>
> <title>Enabling koutput</title>
> <section>
> <body>
>@@ -117,7 +147,7 @@
> 
> 
> <pre caption="Prepare environment with config-kernel">
>-# config-kernel --output-dir=/home/joe/kernels
>+# config-kernel --output-dir /home/joe/kernels
> </pre>
> 
> 
>@@ -128,7 +158,7 @@
> 
> 
> <pre caption="Prepare environment with config-kernel">
>-# config-kernel --output-dir=default
>+# config-kernel --output-dir default
> </pre>
> 
> 
>@@ -138,13 +168,13 @@
> 
> 
> <pre caption="Converting a current kernel">
>-# config-kernel --make-koutput=/usr/src/linux-2.6.3
>+# config-kernel --make-koutput /usr/src/linux-2.6.3
> </pre>
> 
> 
> The above command converts the kernel found in <path>/usr/src/linux-2.6.3</path>
> to outputting to a different directory. If the output directory has been set
>-previously with <c>--output-dir=foo</c>, then that prefix will be used.
>+previously with <c>--output-dir /some/path</c>, then that prefix will be used.
> Otherwise, the Gentoo default of <path>/var/tmp/kernel-output/KV</path> will be
> used.
> 
>@@ -182,6 +212,56 @@
> </tr>
> </table>
> 
>+
>+This change of location is important. Two processes are largely affected by this
>+new file location, copy a kernel config into the proper location when updating
>+kernel sources, and copying a newly compiled bzImage into <path>/boot</path>. In
>+particular, when copying your .config, it's important to remember that you need
>+to copy it from the kernel output location of the original into the kernel
>+output location of the new kernel. To demonstrate how a kernel upgrade would be
>+performed using koutput, an example upgrade from vanilla-sources-2.6.4 to
>+vanilla-sources-2.6.5 is depicted:
>+
>+
>+<note>
>+Here, we assume the output prefix is set to <path>/var/tmp/kernel-output</path>
>+and that both kernel sources are already installed
>+</note>
>+
>+<pre caption="Kernel Upgrade with koutput">
>+# cp /var/tmp/kernel-output/2.6.4/.config /var/tmp/kernel-output/2.6.5/
>+<comment>Copy our .config into the new output directory</comment>
>+# config-kernel --set-symlink 2.6.5
>+# cd /usr/src/linux
>+<comment>Move into our new source tree</comment>
>+# make oldconfig
>+# make &amp;&amp; make modules_install
>+<comment>Compile our new kernel and modules</comment>
>+# mount /boot
>+# cp /var/tmp/kernel-output/2.6.5/arch/i386/boot/bzImage /boot/
>+# umount /boot
>+<comment>Install the new kernel image</comment>
>+</pre>
>+
>+
>+For kernel modules building against kernels using the new system, nothing more
>+should be required beyond emerging the desired kernel module package as usual.
>+At the time of this writing, there are still some kernel modules being converted
>+over to the new setup, or still in testing phase. If the stable version of a
>+kernel module fails, try installing the ~arch version first:
>+
>+
>+<pre>
>+# ACCEPT_KEYWORDS='~x86' emerge foo
>+<comment>The above command installs the testing version of the foo package</comment>
>+</pre>
>+
>+
>+If this still fails, please open a bug at <uri
>+link="http://bugs.gentoo.org">http://bugs.gentoo.org</uri>, and the kernel
>+module ebuild will be updated to the new system as soon as possible.
>+
>+
> </body>
> </section>
> </chapter>

Actions: View | Diff

Attachments on bug 44807: 27435 | 28021 | 28022 | 28125 | 28193