Re: Second attempt: Problems getting ipvs installed on kernel 2.4.8. Anyideas?

["Jesse W. Asher" <jasher1@xxxxxxxxxxxxxxx>]

First, thanks to those that replied.

I'm replying to make sure this gets into the mailing list archive for future
help for others.  I'm not quite sure which planets aligned to help get this
working, but it is working now.  Below are some things that I did differently
that may have effected things so your mileage may vary.

This was caused by a variety of errors on my part.  One little step I left
out of this was that I was moving the compiled kernel to my firewall/load
balancer box since it did not have a compiler and I couldn't compile the
kernel on that box.  Although I'm not sure what effect it may have had, I
was not copying the System.map and map files over to /boot before rebooting.
 I made sure to do that just in case it was causing problems.

Second, I did not compile in the sequence I should have although, again,
I'm not sure how much of an effect this had.  At one point, I had done a
"make dep" and then applied the patches for a module-based kernel.  I also
noticed in the README file that there was mention that those patches had
been tested with a 2.4.9 kenel and above and I was using a 2.4.8 kernel.
 I moved to the 2.4.10 kernel.  I performed the following exact steps to
get this to work (which is very detailed for any newbies out there that like
blow by blow instructions):

1) Uncompressed 2.4.10 kernel source file in /usr/src and linked /usr/src/linux
to linux-2.4.10.
2) Applied patches (linux_kernel_ksyms_c.diff and linux_net_netsyms_c.diff)
to source in /usr/src/linux (which is now pointing to /usr/src/linux-2.4.10)
3) Did a "make config" 
4) Did a "make dep"
5) Did a "make bzImage"
6) Did a "make modules"
7) Did a "make modules_install"
8) Did a "make install"  (I know, I know, all this is the long way around)
9) Copied /boot/vmlinuz-2.4.10, /boot/System.map-2.4.10, and /boot/map over
to firewall box (see above for reason for this).
10) Copied over /lib/modules/2.4.10 to firewall box
11) Did a "make" in ./ipvs-0.9.4/ipvs and a "make -C ipvsadm"
12) Copied ./ipvs-0.9.4 over to firewall box
13) Modified /etc/lilo.conf and ran lilo on firewall box.
14) Rebooted firewall box
15) Ran "make install" in ./ipvs-0.9.4 which successfully loaded ip_vs.o
16) Copied ipvsadm related binaries to their new homes

Hope this helps someone in the future and if anyone has any insight as to
what really fixed the problem it may be of use to others.

I do have one further question though:  Where is the best place to put the
newly created ipvs modules?  What directory should they go in so they get
loaded properly?

Joseph Mack wrote:
> "Jesse W. Asher" wrote:
> > Any ideas as to w hat is going on here??  Any help would be appreciated....
> >     
>
> apparently no-one has a clue or you would have got a reply by now.
> I'm using 2.4.9 with 0.9.3
>
> From your posting you seem to know what to do. I suspect something
> silly is going on that you haven't seen
> There's enough people on this list compiling the code
> that if there were any problems like you see, that
> many people would have seen them by now
>
> > > ip_vs.o: unresolved symbol add_wait_queue_Rb3f23e74
> > >         
> >         
>
> I picked this symbol at random from your posting and it's in ip_vs_sync.o
> Do you have this file?
>
> Joe
>
>         
        
-- 
Jesse W. Asher
Virtual Avalon, Inc.

"Security is mostly a superstition.  It does not exist in nature...  Life
is either a daring adventure or it is nothing."  - Helen Keller