Re: Kernel upgrade 7.0

[ABrady <kcsmart kc rr com>]

On Sat, 8 Sep 2001 20:38:31 -0500 "Steve Thom"
<steve foxvalleyconsulting com> imparted to us:

> I need some help.
> 
> I have been putting some old 486 and slowww pentium machines to work
> as
> firewalls using RH 7.0 (due to limited ram). I usually throw an old
> ISA nic
> in the machine and do an FTP install from a machine on my network.
> It's a
> beautiful thing, I can get a nice ipmasq machine running in a couple
> of
> hours (tedious installation time on these old boxes). I have a need
> for a
> firewall that allows inbound PPTP to a local VPN server, as well as
> outbound
> PPTP as needed. This shouldn't be a big deal, there are plenty of
> how-to's
> on getting it done.
> 
> The patches that make this possible require an upgrade from 2.2.16-22
> kernel
> to something higher. I went to the RH how-to and got a bunch of RPM's
> -
> kernel-source-2.2.19-7.0.8.i386.rpm, as well as ibcs, pcmcia-cs, etc.
> The
> how-to mentioned kernel-header, but I didn't see it in the 7.0
> upgrades. I
> am assuming it is an older kernel module or something. The how-to
> mentions
> mkinitrd, SysVinit ans initscripts rpm's, but I didn't see them. Are
> they
> necessary?
> 
> When I try to run rpm -ivh kernel-2.2.19-7.0.8.i386.rpm, I get the
> following
> failed dependencies messages:
> 
> mount < 2.10r conflicts with kernel-2.2.19-7.0.8
> nfs-utils < 0.3.1 conflicts kernel-2.2.19-7.0.8
> 
> Am I missing something here? I tried upgrading those two, but still
> get the
> message, even after rebuilding the rpm database.

Not using any of the 2.2.X kernels anymore, I can't be absolutely sure
of the situation. But, sometimes in the past the files within packages
get switched around. In this case it appears that files in mount and
nfs-utils are now appearing in kernel RPMs in newer releases. In such a
case, there are 3 ways you can handle it.

1. Download the mentioned packages & upgrade them at the same time. This
is going to cause some frustration. You don't want to rpm -U a
kernel.And, you'll need to rpm -U the new packages. You already see what
happens with the kernel. If you try doing a -U on the packages, some
other complaint is going to crop up that the files that are no longer in
the new RPMs. So rpm -U --force works as might rpm -U --nodeps. You
will, after all, be fulfilling the need for the other files when you
install the new kernel.

2. You can rpm -i the new kernel with the added option --replacefiles to
overwrite the existing files that conflict. That might cause problems in
the future if you need to upgrade the others. I haven't seen it and have
been using it for awhile.

3. You can install the kernel with --force and it will take care of
whatever needs to be done. Again, their might be repercussions later. I
try to avoid --force so I can't speak much to that.

I personally use them in the order 2,1, think about it awhile, 3 if I
decide to chance it. When I use 2 I generally end up upgrading the
others as well, so it's tantamount to using option 1.

-- 
If Bill Gates had a dime for every time a Windows box crashed...
...Oh, wait a minute, he already does.