On Tue, 6 Jun 2000, Rodent of Unusual Size wrote:
> Yep, RH 6.1. I'd rather not start going down the path of de-syncing
> with the RPMs and dist *too* much.
The kernel is one thing I usually compile from pristine sources. Red Hat
adds a lot of patches to their kernel. They have their reasons, most of them
sound. But it also means you're running something different from the "real"
Linux kernel, which makes kernel-related development difficult. Also, Red Hat
usually doesn't release kernel packages as often as Linus releases stable
kernels.
> There are some updated RH kernel RPMs shown by up2date; is it as simple as
> downloading them and doing the canonical 'rpm -Uvh' on them?
"rpm -Uvh kernel-2.*" will upgrade the kernel package, which includes the
files in /boot and /lib/modules. It may or may not update /etc/lilo.conf and
run /sbin/lilo for you (it depends on whether or not is thinks you've tinkered
with the auto-generated /etc/lilo.conf file). You should manually check
/etc/lilo.conf and run /sbin/lilo to be safe. However, this is unlikely to
fix your problem, unless it is a Red Hat bug (which is always possible).
"rpm -Uvh kernel-sources-2.*" will upgrade the kernel source package (not
the same as the SRPM), which installed Red Hat's patched kernel sources, along
with their config files, in /usr/src/linux/.
>> By far the simplest is to type 'make install' after 'make bzImage'
>> finishes.
>
> Rockin'. I'll try that when I get home.
"make install" is much like the kernel RPM post-install script: It doesn't
always do the right thing, especially if your /etc/lilo.conf file isn't the
way it expects it to be. I highly recommend manually checking lilo.conf
and/or running /sbin/lilo any time you make any kind of change to the boot
configuration.
--
Ben Scott <[EMAIL PROTECTED]>
Net Technologies, Inc. <http://www.ntisys.com>
Voice: (800)905-3049 x18 Fax: (978)499-7839
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
