On Sunday 14 July 2002 4:40 pm, J. Craig Woods wrote:

> Okay, let's try to simplify this situation. As previously stated, I am
> attempting to upgrade my kernel on a LMDK 8.0 box. The Mandrake security
> recommendation states to upgrade to kernel-2.4.18.8.2mdk-1-3mdk. OK,
> simple enough, I wget the kernel src rpm, and build my rpm binaries. OK,
> so far? Now I realize there are is NO kernel headers rpm. My LMDK 8.0
> has the upgraded glibc rpms, i.e. glibc-2.2.2-6.1mdk (glibc, profile,
> and devel included). OK, so far? Now where do I find the version of
> kernel headers that match my glibc level? And, Charles, are you saying
> that is must be named kernel-headers with the current glibc version
> numbers in the name, i.e. kernel-headers-2.2.2-6.1mdk? Mandrake has lost
> me, please refer me to the documentation on this radical change in
> building a set of kernel rpms. I have searched high and low only to find
> nothing, not even on the mandrake kernel upgrade page. Thanks to all who
> are contributing to this thread. I fear James may be right in saying
> that mandrake has foobarred us with this new strategy. I hope I am
> wrong....
>
> drjung

If you recompiled the kernel as you have stated. Simply type this command:

ls /boot/kern*

if you can see anything along the lines of kernel.h or kernel.h-(kernel 
version). There you will find your kernel headers alla no kernel header rpm. 
Thus, hopefully that will shed some light on the concept of the revised 
kernel-header-rpm-with-the-glibc -marriage concept.
-- 
------------------------------------------------------------------------
Altoine B
Maximum Time Unlimited
Chicago Based and Operated
------------------------------------------------------------------------
Good day for a change of scene.  Repaper the bedroom wall.
---------------------------
2.4.18-21mdk
Mandrake Linux release 8.3 (Cooker) for i586
------------------------------------------------------------------------


Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to