linux-kernel - Re: Building a kernel-source RPM (not a kernel RPM)?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 12 Sep 2007 20:03:06 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Dan Stromberg <dstromberglists@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?


On Sep 12 2007 10:31, Dan Stromberg wrote:
>
>>> I'm on a SuSE system.
>>> 
>>> I'm working on automating the install of said system, but it needs a
>>> Linus kernel - 2.6.21.7 specifically, and it needs kernel source too so
>>> that we can build modules in the field as needed.
>> 
>> Find a kernel-source.*.src.rpm or kernel-*.src.rpm or whatever SuSE 
>> uses for nameing convention and reverse engineer the .spec file. 
>> Fedora BTW abandoned kernel-source* and they have now a website with 
>> a description how to produce a configured kernel source tree (e.g. 
>> for out-of-tree modules).
>
>So this is as smooth as producing kernel-source RPM's gets?
>
>I might be better off sticking with a .tar.bz2 and repointing symlinks.

Do that for a handful of machines and it gets tiresome.

>>> I see you can make an rpm of a bootable kernel with "make rpm".
>> 
>> Well, then there must be a .spec file somewhere which just wants to be
>> extended.
>
>I'm not sure this is going to be any easier to automate, if that's what's
>required.

The 'proper' (though this is not an authoritative answer) way is to 
build the rpm the same way SUSE did. This ensures best compatibility and 
the fewest surprises. I am not saying it is easy, though.

>>> Is there a streamlined way of building a corresponding kernel-source
>>> RPM?  Or do people pretty much all just dump the source in /usr/src, and
>> 
>> Yes, you put all the steps you do by hand into the .spec file. That's
>> it.
>
>I may just stick them in a bash script and forget about the RPM.  Or are
>there other packages that are going to be cranky, dependencywise, if I
>ignore the RPM?

Somewhat. The kernel rpm and 3rd party kernel module rpms share symbols 
so that upgrading will upgrade all the necessary things. (Instead of 
having to go through it all manually.)

>>> manually update symlinks as needed?  If the latter, what symlinks need
>>> to be updated?
>> 
>> Actually nowadays usually there no "sym-link updating" anymore necessary
>
>On OpenSuSE 10.2, there appears to be:

It is not necessary. rpm -Uhv'ing the kernel-source rpm will repoint the 
symlink to the version you just installed.

>> just put the correct ones in /lib/modules/$(uname -r)/ and the full 
>> name in /boot/grub/menu.lst.
>
>Which correct "ones"?  Sometimes pronouns aren't shortcuts :)


Use http://benjiweber.co.uk:8080/webpin/ , and be happy.




	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/