Re: kernel-headers rpm ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 17 Jan 2003, Michael Schwendt wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 17 Jan 2003 01:00:17 +0100, Brian Ipsen wrote:
>
> >  One quick question (whcih actually is giving me a lot of trouble
> >  building
> > some other software). My RH 7.2 kernel is 2.4.18-19 - but the latest
> > kernel-headers rpm package available is 2.4.9-34 - how come there is
> > no update to 2.4.18-19 of this package too ??
>
> The kernel headers as necessary for building kernel modules, for
> instance, can be found in the kernel-source binary rpm for your
> kernel version. On the other hand, the headers in the kernel-headers

Some thoughts about the current kernel module compilation issue ...

I've been wondering why require the full kernel source package
(/usr/src/linux-$version) which size is about 137MB installed
at /usr, while the (/usr/src/linux-$version/include) headers
needed to build modules fits fine on 8.5MB.

Often the space in /usr is so short that freeing some space
(provided LVM was not used) is a PITA. Not that I defend bad
fs-planning done earlier, but we all propably have met and
tried upgrade the system which /usr didn't appear as much
free space there once we thought would be enough.

So how about having this very small 8.5MB portion installed
also with binary kernel to /lib/modules/$version/include ?

That would be very tiny tradeoff from root-fs vs. large
lump of more free space at /usr. Building modules for all
installed kernel versions would be a breeze too.

Kernel headers would ofcourse shipped as usual with the kernel-
source too (minor reduncancy), but having full kernel source
installed is plain silly when you need just few header files to
compile modules and get going with thirdparty software like vmware.

It makes sense to me having kernel source installed for those
taking part of developing drivers etc., but not necessarily on
every system in use and where there is need to compile modules.

Those familiar with Linux and Unices know dirty tricks to get
around /usr lack of space with symlinks or extract rpm2cpio,
but it can get much too complicated just to have modules built
and installed for all installed binary kernels at once.

:-) riku

-- 
    [ This .signature intentionally left blank ]



_______________________________________________
Redhat-devel-list mailing list
Redhat-devel-list@redhat.com
https://listman.redhat.com/mailman/listinfo/redhat-devel-list

[Index of Archives]     [Kernel Newbies]     [Red Hat General]     [Fedora]     [Red Hat Install]     [Linux Kernel Development]     [Yosemite News]

  Powered by Linux