Subject: Re: Current MoL rsync does not build against benh's 2.4.6-pre3
From: Samuel Rydh (samuel@ibrium.se)
Date: Thu Jun 28 2001 - 17:21:24 MDT
On Thu, Jun 28, 2001 at 08:29:36PM +0200, Olaf Hering wrote:
> I didnt pull yet, but I took the patch that you posted a few days ago.
> I disabled the _SEGREG stuff in mmu.c and compile went fine.
I found one bug in the patch which will cause instability
problems - i.e. don't put together a RPM based on it.
This problem is not present in the developer tree.
> The only thing left is:
>
> mango:~ # depmod -ae
> depmod: *** Unresolved symbols in /lib/modules/2.4.6/misc/molsymglue2.o
> depmod: mol_interface
>
> Should I only package symglue1.o for the recent kernels?
Different kernel versions export a slightly different
set of symbols. There are three cases:
molsymglue0.o
This is the fallback solution. The symbols MOL needs are
extracted from the Symbol.map file and passed to the kernel
modules as module parameters.
molsymglue1.o
This is for compatibility with the latest 2.4 kernels.
molsymgle2.o
This is for compatibility with old 2.4 kernels which
was compiled with the CONFIG_MOL option (which was
removed in 2.4.3-something I think).
In all cases, only one molsymglue is ever loaded. It is safe to
trash the molsymglue2 variant if the kernel is a recent one.
/Samuel
----------------------------------------------------------
E-mail <samuel@ibrium.se> WWW: <http://www.ibrium.se>
Phone/fax: (home) +46 8 4418431, (work) +46 8 7908470
----------------------------------------------------------
This archive was generated by hypermail 2a24 : Thu Jun 28 2001 - 16:27:12 MDT