I posted a long message yesterday in theSuSE security mailing list,
which was pretty much off-topic (only tangentially related to security
issues with kernel 2.2.3). But I had been through several attempts to
compile and install the 2.2.3 kernel, without much success.
I have a cable modem and a home LAN, using an AMD 5x86 as my
router/gateway. It has two NICs. The one to the LAN is a Linksys
NE2000 clone. The one to the cable modem is a 3Com 3c509 that was
provided by the cable company, Mediaone. The problem I had with 2.2.3
was that it wouldn't recognize either of the NICs.
Hearing that there was a 2.2.5 kernel out, I downloaded it, and prepared
to install it. I provided a blow-by-blow description of my attempt to
compile and install a new kernel. Below is the description I posted:
Here's what I've done so far. I went into /usr/src
and did "rm -rf /usr/src/linux". Then I redid "ln -s
/usr/src/linux-2.2.5
/usr/src/linux". I typed "cd linux" and I was in /usr/src/linux. I
typed
"make menuconfig". I got a whole bunch of text, and then the menuconfig
screen appeared. Well, all of the settings were just like they were the
last time I did a make menuconfig.
After I verified that that was the case, I saved the config settings.
This dropped me down to a message that told me to check the top level
Makefile and then type "make dep". I took a look at the "top level
Makefile",
which I assume is the one in /usr/src/linux, but as always, it's just a
script,
and I don't know what I'm looking at. When this message appears, I sort
of expect to see a list of additional things to do, but there isn't.
Just
the script.
OK, I did "make dep" and now it's done. The last two lines are "make
[2]:
Leaving directory '/usr/src/linux-2.2.5/arch/i386/lib'" and then "make
[1]:Leaving directory '/usr/scr/linux-2.2.5'"
Now I'm at the prompt, no further instructions. Following the list in a
message from W.D. McKinney, I'm going to type either make clean, or make
bzImage (or maybe just "make zImage", if I don't think the kernel will
be
too big). But why the "make clean"? To remove all of the previous
connections, in case some of them are "bad"? (like the time I
accidentally
compiled for a Pentium, when I only have an AMD 5x86).
I'll do it. [type 'make clean']. Here goes. Ah, it's rm'ing a bunch
of stuff. Last few
lines:
if [ -d modules ]; then \
rm -f core 'find modules/ -type f -print'; \
fi
rm -f submenu*
and now I'm at the prompt. Here goes make zImage. It'll take a while.
[It's a] Half hour later. Kernel too big [is the message I see]. The
last few lines are:
Boot sector is 512 bytes
Setup is 1272 bytes
System is 564 kB
System is too big. Try using bzImage or modules
make[1]: * * * [zImage] Error 1
make[1]: Leaving directory '/usr/src/linux-2.2.5/arch/i386/boot'
make: * * *[zImage] Error 2
And back to the prompt. OK, so let's do bzImage.
That was quick [it took about 3-5 minutes!]. No errors. Now, how about
make modules? OK, start that. I got a couple of warnings. "unused
variable ei_local"
for one. A bunch of messages "nothing to be done for modules", but I
think that's
just referring to specific functions that haven't been modularized.
Now, make modules_install. I got two. net and ipv4.
Now to copy the bzImage to /boot/vmlinuz, /sbin/lilo, and reboot. OK,
here goes nothing.
We're on. OK, it's got the devices [it recognized both NICs]. But
nothing's going out [ip forwarding isn't working]. There was that mod
probe error (char-something-4?), and ipfwadm isn't working (why should
it--this is a 2.2.x kernel--I need ipchains, right?).
Well, I feel better. I think I can fix this, and in the meantime, I can
reboot from the boot disk.
And I *will* look over the changes file, and see what needs to be
upgraded.
It *can* be done. But I may get 6.1 anyway....
That was what I posted last night. The only thing I forgot to add was
that when I type route or route -n each entry appears twice. Odd. But
mainly, IP forwarding isn't working. I have IP_FORWARDING = yes in
rc.config, so don't ask about that. When I first installed SuSE 6.0 I
couldn't get onto the internet from my LAN, but it was because I hadn't
prepared a FW-INOUT file and I had turned that variable on in rc.config.
So if anyone has any helpful suggestions as to why ip-forwarding isn't
working, let me know. Thanks.
Stan Koper
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
