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 17:05:58 -0400
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Jan Engelhardt" <jengelh@...putergmbh.de>
Cc:	"Bernd Petrovitsch" <bernd@...mix.at>,
	"Sam Ravnborg" <sam@...nborg.org>,
	"Dan Stromberg" <dstromberglists@...il.com>,
	<linux-kernel@...r.kernel.org>
Subject: Re: Building a kernel-source RPM (not a kernel RPM)?


On Wed, 12 Sep 2007, Jan Engelhardt wrote:

>
> On Sep 12 2007 20:23, Bernd Petrovitsch wrote:
>> On Wed, 2007-09-12 at 20:16 +0200, Sam Ravnborg wrote:
>>>>
>>>> But we are talking[0] about a kernel-source-$VERSION.$ARCH.rpm's
>>>> which contain the kernel sources (read: lots of .c and .h files,
>>>> etc.) - including a matching .config and after `make oldconfig` - so
>>>> that one can build out-of-tree modules after installing it with
>>>> "KSRC=" (or whatever the Makefile parameter is usually called).
>>>
>>> You need certain things of the kernel built before you can build
>>> external modules (if they use a sane build approach). Just including
>>> the .config with the kernel source is far from enough.
>>
>> ACK. That all must be done/prepared correctly for the
>> kernel-source-*.rpm. And nobody said it is trivial or easy.
>
> Trivial as far as SUSE goes. Install the binary package and you get all
> the symvers, modvers, and everything of the O= part that is needed. That
> is because symvers are per-binary image and not per-source.
>
> Remain the Makefiles, which are in (the big) kernel-source rpm :-/
>
>
>
> 	Jan

If his base package was RedHat, he can just download the sources
he wants, from ftp.kernel.org, un-tar the *.gz file into /usr/src,
then copy the .config used to build the existing kernel from /boot.
It is called /boot/config-`uname -r`. Copy that to the new
kernel tree as ".config" then chdir to that tree and execute
`make oldconfig`. Some questions will have to be answered because
the newer kernel will have additional drivers.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.30 BogoMips).
My book : http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ