> Hi,
>
> I just compiled a kernel for the first time, and although there are some
> glitches (probably didn't configure well enough, gotta do it again ;-)), I am
> planning to compile a few more which I want to test side by side. Problem is
> that when custom configuring the kernel, the modules directory becomes
> /lib/modules/<kernelversion>custom, which is fine for a single custom kernel,
> but no good if I want 3 or 4 of them with separate modules dirs.
>
> How do I force another naming scheme?
>
> Also, anybody built the 2.4.19-pre8 from Alan Cox? Is it stable enough? I need
> some of the new functionality there.
>
> Arie Folger
> --
> It is absurd to seek to give an account of the matter to a man
> who cannot himself give an account of anything; for insofar as
> he is already like this, such a man is no better than a vegetable.
> -- Book IV of Aristotle's Metaphysics
>
I have not built 2.4.19-pre8 from Alan Cox.
As for the differentiating the same kernel, maybe some LDP kernel related HOWTO will
be of some help?
Debian's make-kpkg can do it quite simply, although I don't know exactly how. I
mention this because I am giving below a somewhat long paragraph from make-kpkg man
page which contains hints for what is really done.
--append_to_version foo
This argument ( foo ) is appended to the value of
the EXTRAVERSION variable present in the kernel
Makefile. Since EXTRAVERSION is a component of the
kernel version, it is also added to the Debian
package name, and, as such must obey the policy
governing the package name. That means it may con-
tain only lowercase alphanumerics and the charac-
ters - + . (full stop, hyphen, and plus). Uppercase
letters are not permitted under the Policy for a
new package. This over rides the environment vari-
ble APPEND_TO_VERSION Please note that you must
run a make-kpkg clean after configuring the kernel
using make (x|menu)?config, since that creates the
file include/linux/version.h without the
append_to_version data (foo). This file won't be
updated by the make-kpkg run (make-kpkg creates
version.h if it doesn't exist, but doesn't touch if
exists), so the final kernel will _not_ have the
append_to_version data in its version number it
shall look for the modules and symbols in all the
wrong places. The simpliest solution is either to
remove include/linux/version.h after configuring
and before compiling, or running make-kpkg clean
after configuring, before compiling. Note also
that once you use --append_to_version foo for con-
figuring, or building the kernel-image, you need to
also use the same option in any later invocation of
make-kpkg (say, for building stand alone modules,
or something). make-kpkg does not remember the
argument foo in between invocations (this is dif-
ferent from the behaviour of --revision, which we
do remember in between invocations). If you are
annoyed by make-kpkg whining about using
--append_to_version and there already being a file
from before, you can set the environment variable
VERSION_H_OK which shall shut off the warning.
--
Shaul Karl, [EMAIL PROTECTED] e t
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
