To: Hunter Thomas archangelq@email.com
Cc: sluglug@sluglug.ucsc.edu
Subject: Re: [SlugLUG] More on the old laptop linux
install...
From: Ben Gertzfield ben@cse.ucsc.edu
Date: 23 Jul 1999 15:32:10 -0700
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4
(Emerald)
>>>>> "Hunter" == Hunter Thomas archangelq@email.com writes:
Hunter> Actually, I need to get it onto the other machine
before I
Hunter> connect it via laplink. What are the options I need to
use
Hunter> for make-kpkg? I'll most likely use a floppy to get
it
Hunter> onto my the laptop, I don't see the kernel I'm going
to
Hunter> compile to be that big.
That will work. To use make-kpkg, in your unpacked kernel source directory, run:
fakeroot make-kpkg kernel_image
the 'fakeroot' is a little trick library preload that makes tar and whatnot think they're running as root so they can create tar files with entries owned by anyone. useful for package building!
A good idea is to put a revision in the debian package version:
fakeroot make-kpkg --revision ben.19990723 kernel_image
like so. You'll get a .deb in the .. directory when it's done building.
--
Brought to you by the letters Q and V and the number 0.
"Whoa. I know Kung Fu."
Debian GNU/Linux maintainer of Gimp and GTK+ -- http://www.debian.org/
Date: Mon, 22 Dec 2003 15:26:35 +1100
From: Daniel Stone <daniel@fooishbar.org>
To: luv@luv.asn.au
Subject: Re: Packaging the kernel (was Re: Some advice trying out 2.6...)
Debian-wise, you need the kernel-package and fakeroot packages installed; just configure your kernel, then type: "make-kpkg build --revision=`hostname`.1 && fakeroot debian/rules kernel-image-deb".
You'll then have a shiny kernel-image-nn.nn.nn_hostname.1_i386.deb sitting in the directory above - just install this, and enjoy!
Date: Fri, 16 Dec 2016 19:32:44 +0100
From: Adam Borowski <kilobyte@angband.pl>
To: dng@lists.dyne.org
Subject: Re: [DNG] Won't boot after dist-upgrade
> www.kernel.org, e.g. one that does not have that bug (which seems to
> have been introduced by one of the Debian patches) and produce a deb
> package for it using kernel-package. You might find this tutorial
> somehow useful:
>
> https://www.debian.org/releases/jessie/i386/ch08s06.html.enI'd recommend against using kernel-package, it is basically unmaintained and produces broken packages, at least for modern kernels. If you're trying to compile a recent kernel, you'll be far better off using "make bindeb-pkg".
Date: Sat, 17 Dec 2016 11:44:42 +0100
From: Klaus Ethgen <Klaus+dyne@Ethgen.ch>
To: dng@lists.dyne.org
Subject: [DNG] bindeb-pkg (Was: Won't boot after dist-upgrade)
Am Fr den 16. Dez 2016 um 19:32 schrieb Adam Borowski:
> I'd recommend against using kernel-package, it is basically unmaintained
> and produces broken packages, at least for modern kernels. If you're
> trying to compile a recent kernel, you'll be far better off using
> "make bindeb-pkg".
Never seen that bindeb-pkg... I always build my kernels with make-kpkg.
With "make bindeb-pkg", is there a way to build additional modules like it is with make-kpkg?
I use oss4 and nvidia modules and I depend on them. So I need a way to build them too.
Date: Sat, 17 Dec 2016 21:56:34 +0100
From: Adam Borowski
Subject: Re: [DNG] bindeb-pkg (Was: Won't boot after dist-upgrade)
On Sat, Dec 17, 2016 at 11:44:42AM +0100, Klaus Ethgen wrote:
> Never seen that bindeb-pkg... I always build my kernels with
> make-kpkg.
It's a new thing in upstream kernels.
deb-pkg came first but it produces tons of useless cruft, bindeb-pkg is there since 4.3.
> With "make bindeb-pkg", is there a way to build additional modules
> like it is with make-kpkg?
No idea about out-of-tree modules, I build nvidia and virtualbox with dkms.
> I use oss4 and nvidia modules and I depend on them. So I need a way to > build them too.
How come you use nvidia modules with make-kpkg? https://bugs.debian.org/772681 makes -headers incapable of building nvidia unless you manually rm -rf include/asm after every kernel upgrade.
There are other severe bugs: fork bombing when attempting parallel compilation unless you remember to unset build flags; glancing at the bug list I see it fails to compile 4.9 kernels (ie, those that stretch will have) -- I haven't tested that but this kind of failures has been handled on kbuild side during mid-rc, kernel-package would need an update. Manoj is a skilled maintainer but apparently he's been seriously neglecting this package.