[OpenAFS-devel] take 2: openafs 1.3.64 on linux 2.6 -- what am I missing now?

[Matthew Miller]

On Wed, May 12, 2004 at 10:49:16PM -0400, chas williams (contractor) wrote:
> >First, I needed to make some minor tweaks to get the thing to build at all
> >-- in src/rx/LINUX/rx_knet.c, the sock_create call is missing its final
> >parameter. I'm just guessing, so I put in a 0. This may be horribly wrong,
> >but at this point, I'm still trying to get the thing to _build_, and I can
> >worry about _build correctly_ after that. :)
> the standard 2.6.5 sources seem to have a 4 argument sock_create().

src/libafs/netinet/net.h has a 5-argument version; the final parameter is
"int kernpriv".


> >Then, src/afs/LINUX/osi_module.c seemed to want a 
> >"#if !defined(AFS_LINUX24_ENV)" put around the "sys_settimeofdayp = 0;".
> that code is only triggered if you dont have sys_call_table exported.
> you will need to patch the 2.6 kernel to get the afs module to load.

(See other messages.)

> >Then, I needed to have a kernel tree to which I had write access -- it wants
> >to make some symlinks there. (That doesn't seem so good....)
> ?

It tries to make a bunch of symlinks into the kernel tree in src/libafs. One
of these is "mach", pointing to include/asm-i386/mach-default in the kernel
tree. And then it tries to make mach/mach-default under that, pointing to
the same place.


> >And perhaps most troubling, the whole thing didn't seem happy at all unless
> >I made a change to ./configure -- there's no "i386_linux26" section, so I
> >created one by just copying the i386_linux24 part. This is probably not
> >sufficient, and is probably what leads to my current state of affairs:
> i guess i didnt manage to submit that part.  the 26 stuff is the same
> as the 24 stuff (which is really just the same as the 22 basically)

Which is what I did, although obviously the m4 fix is the right one.


> >With the above-mentioned changes, everything builds, but the kernel modules
> >generated are 'libafs-2.6.5-1.358custom.o' and
> >'libafs-2.6.5-1.358custom.mp.o'. They're not the fancy new .ko format, and
> >insmod tells me:
> > error inserting 'libafs-2.6.5-1.358custom.o': -1 Invalid module format
> it doesnt have to be called .ko  anything in the output of dmesg?

Yep -- "No module found in object".




-- 
Matthew Miller           mattdm@mattdm.org        <http://www.mattdm.org/>
Boston University Linux      ------>                <http://linux.bu.edu/>