xfs
[Top] [All Lists]

Re: /boot/kernel.h

To: Arjan van de Ven <arjanv@xxxxxxxxxx>
Subject: Re: /boot/kernel.h
From: Alan Eldridge <alane@xxxxxxxxxxxx>
Date: Mon, 9 Jul 2001 18:53:45 -0400
Cc: SGI XFS Dev List <linux-xfs@xxxxxxxxxxx>
In-reply-to: <20010709174000.D15119@devserv.devel.redhat.com>; from arjanv@redhat.com on Mon, Jul 09, 2001 at 05:40:00PM -0400
References: <20010709174000.D15119@devserv.devel.redhat.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Mon, Jul 09, 2001 at 05:40:00PM -0400, Arjan van de Ven wrote:
>Hi,
>
>I saw, while reading the XFS mailinglist, that you had some problems with
>/boot/kernel.h. This file is created ON BOOT to represent the currently
>running kernel, and also on rpm -i of a kernel rpm. Why your system doesn't
>have a /boot/kernel.h is a big questionmark for me, but it has nothing to do
>with which package has the file...

Yup, /sbin/mkkerneldoth creates it. That was the piece of the puzzle I was
having trouble finding. "find /etc/rc.d -type f |xargs grep kernel.h" didn't
turn up anything. "find /sbin ...." did. Once I found that, the rest was
easy.

When you install a new kernel, it is supposed to get run as part of %post.
When you erase a kernel RPM, rpm tries to get rid of the old one as part of
   %postun.

Somehow, installing one kernel RPM and then erasing an earlier one led to
the file getting zapped to empty. Happened a second time, too, same sequence
of operations, but I was watching for it that time.

-- 
Alan Eldridge
from std_disclaimer import *

<Prev in Thread] Current Thread [Next in Thread>
  • Re: /boot/kernel.h, Alan Eldridge <=