On Sat, 2 Feb 2002, Cameron Simpson wrote:
> On 17:59 01 Feb 2002, Ian Firla <[EMAIL PROTECTED]> wrote: > | I've compiled and installed kernel 2.4.16 > [...] > | Here's what's confusing me with my machine: > | > | [kubla@localhost kubla]$ rpm -qa|grep kernel > | kernel-pcmcia-cs-3.1.24-2 > | kernel-2.4.2-2 > | kernel-2.4.9-12 > | kernel-headers-2.4.9-12 > | [kubla@localhost kubla]$ uname -r > | 2.4.16 > | > | Why does uname return the correct kernel version and why does rpm report > | something that I know is patently untrue. How do I update this information > | so that up2date and redcarpet are aware that I'm running a new kernel? > > RPM is reporting the kernel RPM you have installed. > > You are running a kernel which was not installed with RPM. > > Likely you have both 2.4.9 sitting around (from the RPM) and 2.4.16 (which you > are running). There is not wrong or even unusual about this. I _always_ > keep a stock RedHat kernel around. If nothing else, it's a good fallback > if one I've built myself is seriously sick. > > So this is normal and expected. Many thanks. But as Andrew Smith suggested: > Most likely, you didn't use RPM to install the new kernel > thus RPM doens't know anything about it. > If you add any software at all to the computer without using > RPM to install it then you have problems: > 1) RPM doesn't even know it exists > 2) dependencies on "packages" that have been manually installed > without RPM will not work So the trouble now is getting up2date and redcarpet to recognise my own kernel. Is there anyway of adding / editing entries to / in the rpm database? On that topic, I've taken gcc up to 3.02. Am I to understand that since I also did this without using rpm that I might run into trouble if/when up2date is trying to do something that requires an update to gcc 2.96? Best, Ian _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
