From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: kbuild make deb patch
Date: Mon, 14 Jun 2004 10:30:25 +0200 [thread overview]
Message-ID: <20040614083025.GH20632@lug-owl.de> (raw)
In-Reply-To: <20040613061957.GA3012@mars.ravnborg.org>
[-- Attachment #1: Type: text/plain, Size: 2600 bytes --]
On Sun, 2004-06-13 08:19:57 +0200, Sam Ravnborg <sam@ravnborg.org>
wrote in message <20040613061957.GA3012@mars.ravnborg.org>:
> On Wed, Jun 09, 2004 at 04:21:41PM +0200, Jan-Benedict Glaw wrote:
> > On Tue, 2004-06-08 23:08:46 +0200, Sam Ravnborg <sam@ravnborg.org>
> > wrote in message <20040608210846.GA5216@mars.ravnborg.org>:
> > > On Mon, Jun 07, 2004 at 04:13:53PM +0200, Wichert Akkerman wrote:
> > > I'm in progress of doing some infrastructure work to better support building
> > > different packages. I have requests for .tar.gz, tar.gz2 as well
> > > as deb.
> >
> > (Being a Debian user...) I really *love* to see a .tar.{gz,bz2} target.
> > For my in-house use (as well in in the company I work for) we do have a
> > script to basically install modules (+ vmlinuz + vmlinux + .config +
> > System.map), adding some identifier to the filenames (of the last four
> > files mentioned) and preparing a .tar.gz from that.
>
> Could you try to be more specific in what you expect to see in a .tar.gz'ed kernel.
> A script that creates a .tar.gz from current kernel would be fine :-)
I'd expect something that you can extract with:
~# cd /
/# tar xzf /path/to/kernel.tar.gz --no-same-owner
That tar file should contain:
./boot/vmlinux-<version> # unstripped vmlinux file for debugging
./boot/vmlinuz-<version> # bootable file - non-i386 archs obviously
# need different files
./boot/System.map-<version> # Map file for 'ps' and for me
./boot/config-<version> # To recreate the kernel
./boot/patch-<version> # Only if it was requested at .tar.gz
# build time, containing a -Nurp style
# diff to a clean source tree (which
# needs to be specified then)
./lib/modules/<kversion>/* # Modules
The tricky part is the <version> and/or <kversion> part. For my personal
use, version is like kversion, but extended with whatever the user
specified. kversion is Makefile's $(KERNELRELEASE).
As I stated, it's clumsy at ./lib/modules/<kversion>/*, because you'll
probably overwrite other modules of the same kernel version with a
different(ly compiled) .tar.gz . The tarball's name should exactly
contain <version> in it's name so that a script that extracts is can
place a proper symlink within ./boot easily.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-06-14 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 14:13 Wichert Akkerman
2004-06-07 14:36 ` David Vrabel
2004-06-07 14:39 ` Wichert Akkerman
2004-06-07 15:13 ` Flavio Stanchina
2004-06-07 15:20 ` Wichert Akkerman
2004-06-08 21:08 ` Sam Ravnborg
2004-06-09 14:21 ` Jan-Benedict Glaw
2004-06-13 6:19 ` Sam Ravnborg
2004-06-14 8:30 ` Jan-Benedict Glaw [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040614083025.GH20632@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®