According to Maurice Hendrix: While burning my CPU.
>
> Hi,
>
> I installed RH5.2. It comes with a kernel 2.0.36-0.7. Modules are installed
> in a directory called 2.0.36-0.7
>
> Since then I have regularly rebuilt the kernel. But everytime I do this it
> gets a version number of 2.0.36. The -0.7 suffix is gone. Also re-making and
> re-installing the modules will place them in a directory 2.0.36 (I'm unsure
> about the full path) and overwrites any previous versions of those modules.
Symlinks could be one answer, ie, you could make your new kernel and its
modules which will be placed in /usr/lib/modules/2.0.36 after they are
installed do;
cd /lib/modules
mv 2.0.36 2.0.36-1
ln -s 2.0.36-1 2.0.36
You can do that time after time just delete the symlink before making any
new modules, repeat the above for the new directory (-2) (-3) etc, then
reboot.
A small shell script would be handy in this case.
The above is what i have used in the past on RH-4.2 before they introduced
the new rc.sysinit. I have also used the above many times in slackware.
RH does some linking in the modules directory, i belive "prefered" is the
word used, you might want to comment out that part of the boot script before
trying the above. I belive its /etc/rc.d/rc.sysinit.
I dont have rc.sysinit from RH-5.2 but it should be possable to use that to
link your different kernel-modules to its "prefered directory".
If you would like more information about this subject you could send me a
copy of your rc.sysinit, i could then chek and see just what it looks for
and try to see howto link different dir's at bootime, UNLESS anyone has
already done this before with RH-5.2 and sends you the golden tip.
>
> I really would like to have different kernels (for testing or with specific
> configurations) and keep the modules separated. Is there a mechanism in
> Linux that allows be to include a "build"-version? E.g. what I would like is
> this:
>
> 1. Original RedHat distributed kernel v2.0.36-0.7 with modules in dir
> 2.0.36-0.7
>
> 2. Completely monolithic kernel v2.0.36-1 with no modules
>
> 3. Modular kernel v2.0.36-2 with modules in dir 2.0.36-2
>
> 4. Modular kernel v2.0.36-3 with pcmcia-support; modules in dir 2.0.36-3
>
> Suppose a new pcmcia driver (experimental) is released. Then I would want to
> add:
I doubt if that would happen as 2.0.xx is nearing its final completion.
>
> 5. Kernel v2.0.36-4 with experimental pcmcia-support; modules in dir
> 2.0.36-4
>
> Then from LILO I could select the kernel of my choice and the kernel would
> only use the modules that were compiled for it. AFAIK this cannot be done.
Of course you can do it, but it wont "just happen" you will have to follow
certain rules.
You could also tweek the linux source Makefile to install the modules in a
"defined" destination, altho, that would envolve some experimenting.
> I've found a file called version.c (or was it version.h? I don't recall) but
> changing that won't work when I switch to a 2.2.x kernel.
I dont quite understand what you mean by that, ./linux/include/version.h
gets created and deleted by the "make" process and is dependant on the
presant kernel version.
Groeten uit Goes.
>
> Comments please?
> --
> Maurice Hendrix
>
> snailmail: Fuji Photo Film BV Standard disclaimers apply
> Dept. P1LPI
> attn. M. Hendrix
> PO Box 90156
> 5000 LJ Tilburg
> phone: +31 13-579 1370 or fax: +31 13-579 1385
>
> - Still 21 months to go until the next millenium...
>
--
Regards Richard.
[EMAIL PROTECTED]
