> ----------
> From: Richard Adams[SMTP:[EMAIL PROTECTED]]
> Reply To: [EMAIL PROTECTED]
> Sent: 27 April 1999 01:02
> To: Maurice Hendrix
> Cc: [EMAIL PROTECTED]
> Subject: Re: compiling many kernels
>
> 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
>
But then I won't be able to start an older version of the kernel. I'd have
the modules still but the kernel wouldn't be able to find them. I'd have to
boot, change the symlink and reboot. ... :-\ Nah. I want to be able to
decide which kernel to start at the LILO prompt and start it. So, in some
way it should be (made) possible to point the kernel to a unique location
for the modules. I've seen that the version number of the kernel also
defines the name of the directory in /lib where the modules will be stored.
> 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 think I came across something there. IIRC it *was* in rc.sysinit... I'm
starting to see the light. I'll try somethings tonight when I get home and
let you know later.
> 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".
>
Don't you hate it when different distributions do things differently?
> 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.
>
Thanks. I'll try it myself first. I've found that doing things by yourself
is still the best way to learn.
> > [blabla...]
> > 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.
>
It was just an example ;-)
> >
> > 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.
>
Perhaps I meant the Makefile. I'm not sure anymore. It's been some weeks ago
since I tried, failed and abandoned the whole idea ;-)
> Groeten uit Goes.
Groeten uit Tilburg.
> --
> Regards Richard.
> [EMAIL PROTECTED]
>
--
Maurice Hendrix
