On Tue, 3 Jul 2001 23:58, Wolfgang Bornath wrote:
> On Tue, Jul 03, 2001 at 06:43 -0600, Praedor S. Tempus wrote:
> > On Monday 02 July 2001 09:33 pm, you wrote:
> > [...]
> >
> > > > I have a working kernel. It's the plain kernel after the installation
> > > > process is done.
> > > > Now I'll have to compile a new kernel, more custimized to the
> > > > hardware I have. The routine is easy:
> > > >
> > > > make mrproper
> > > > make menuconfig
> >
> > included but it will not boot the new kernel. Instead, if you select
> > your new kernel, you will get an error message about not being able to
> > find the root device (because the default root=306 entry is nonsense).
> > You would either need to add a boot parameter "root=/dev/<whatever your
> > root is>" or boot up your old kernel and fix the lilo.conf problem.
> >
> > If you don't do the "make install" step at the end, then you will simply
> > need to move the new kernel manually to your /boot directory and name it
> > whatever you want.
>
> I know that, but what I mean is
>
> existing kernel = vmlinuz.1
> existing modules = /lib/modules/2.4.3-20mdk
>
> Now I customize the kernel and will have:
>
> new kernel = vmlinuz.2
> existing modules = /lib/modules/2.4.3-20mdk.old
> new modules = /lib/modules/2.4.3-20mdk
>
> When I boot the new kernel it's ok. But what happens when I boot
> vmlinuz.1? It will look for the modules and take the modules from
> /lib/modules/2.4.3-20mdk.
> This will result in some nice error messages b/c this set of modules is
> installed for vmlinuz.2
>
> wobo
Oh that...err, I usually go into the make file and change the minor version
so the new modules are not going to be installed into a directory called
2.4.3-20mdk
Andrew
