From: Charles Johnson (charlesnjohnson_at_tds.net)
Date: Sat Oct 19 2002 - 05:00:11 CEST
To Sam Sgro and Paul Wouters my thanks!
It works!
Now, then, I haven't re-booted, yet, but it compiles against the latest
Red Hat kernel 2.4.18-17.8.0 without errors. /sbin/service ipsec start
brings it up.
My thanks, too, to those who got the steps put together...
Now, if we could just get an RPM put together... :-)
Seriously, my thanks.
-----Original Message-----
From: users-admin_at_lists.freeswan.org
[mailto:users-admin_at_lists.freeswan.org] On Behalf Of Sam Sgro
Sent: Friday, October 18, 2002 4:13 AM
To: Charles Johnson
Cc: users_at_lists.freeswan.org
Subject: Re: [Users] Related RedHat 8.0 error -- What did I forget?
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 17 Oct 2002, Charles Johnson wrote:
> 3. Applied the patch supplied by Tom Hughes to remove the
> gcc2_compiled.: line.
Of course, I see that *after* I hit send. Don't you hate that? Sorry...
> ipsec_setup: /lib/modules/2.4.18-14/kernel/net/ipsec/ipsec.o was
> compiled for kernel version 2.4.18-14custom
> ipsec_setup: while this kernel is version 2.4.18-14.
The kernel version is defined in the main Makefile, and it does include
"custom" as part of EXTRAVERSION. I belive RedHat's intent with this is
to
ensure that if you recompile your own kernel, the original 2.4.18-14
modules
won't be overwritten accidentally. You'll always be able to go back to
the old
config.
Edit your kernel source's Makefile, and strip out the "custom" at the
end of
EXTRAVERSIONS. Now, issue make mrproper, copy the .config, run
menuconfig and
dep. Now, go to the freeswan 1.98b sources, and run "make oldmod". Once
this
has finished, *don't* run make minstall. Instead, go directly to the
/usr/src/linux-2.4.18-14/net/ipsec/ directory, and copy the newly made
ipsec.o
into place (in /lib/modules/linux-2.4.18-14/kernel/net/ipsec)
Why no make minstall? I'm finding that it actually results in the
deletion of
your existing modules. Copying it by hand works properly. (Or so it
seems.)
There's probably a nicer way to do this. But since we'll have RPMs for
RH 8.0
very shortly, this will hopefully be an academic issue.
Let me know if any of the steps above fail to make this a painless
process. :)
- --
Sam Sgro
sam_at_freeswan.org
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: For the matching public key, finger the Reply-To: address.
iQCVAwUBPa/Qt0OSC4btEQUtAQFZ0wQAqs88BHVZmZlzVUXdkPNSgFjWVVTYHovl
EGjxQ2tPeCZLaul3g18zYHGWdNNZUZKXBEF0yBl4g6Ejn26hb3EVmahI0fd/1uMx
V8H8UlZs38pX69UFMcjhuB+syIinI7zhs+OahorjmUxaEF9rdVDZsPVqH9F26UKI
wHIu5Q7uI88=
=yMoa
-----END PGP SIGNATURE-----
_______________________________________________
Users mailing list
Users_at_lists.freeswan.org
http://lists.freeswan.org/mailman/listinfo/users
--- Remember the heroes of UAL Flight 93 _______________________________________________ Users mailing list Users_at_lists.freeswan.org http://lists.freeswan.org/mailman/listinfo/users
This archive was generated by hypermail 2.1.5 : Sun Oct 20 2002 - 05:20:29 CEST