Puppy Linux Discussion Forum

[01micko]

Preface

This kit is designed to make it easy to compile a kernel.

For about a year now, nearly all puppy kernels have been compiled using build scripts. Barry has his own scripts which you can find at http://bkhome.org/sources (user,pass required). This kit was originally designed by Iguleder.

A limitation of Barry's way is that a full install is required. Any type of install should work with this as long as the script is run on a Linux filesystem.

This kit will download,patch (aufs and others) and compile the kernel, extract the headers, make the kernel and install it into a directory ready for manual running of dir2pet and build the kernel source sfs without manual intervention.

History

A bit over a year ago, Iguleder introduced kernel-kit. Myself and pemasu have been using it to produce kernels for Slacko, Dpup-Exprimo, Upup and Saluki ever since. We have both added our own refinements and it has evolved to the point where almost anyone can compile a kernel for Puppy.

Prerequisites

* you must be comfortable with scripts and command line usage
* a late model Puppy install (YMMV with older pups, but it may work)
* deps: gcc, git, mksquashfs
* patience

Hardware

* at least 512 RAM (may work with less)
* any architecture supported by Puppy
* at least 2 GB disk space

--------------------------------------------------------------------------------------------------------

from the README;

[mavrothal]

Hi Mick,
I believe the aufs lopback patch is not needed some time now (ref 1, ref 2)
Actually XO kernels run fine without it.

[01micko]

Hi mavrothal

One time there I was not including that patch. I think it was beta testing for one of the slacko versions, forget which, but on Barry's advice I put it back. It was after the dates of your references.

ref1: From: <sfjro@us...> - 2010-07-25 23:48

ref2: From: <sfjro@us...> - 2010-03-23 09:03, From: Barry Kauler <bkauler@gm...> - 2010-03-24 00:04

Barry's patch in Precise:2011-05-11

[Iguleder]

Thanks for sharing, 01micko!

While I'm waiting for my Raspberry Pi to arrive, I'm doing some automation work and I think it would be nice to have a kernel building kit for kernel 3.2.x, since the Raspberry Pi guys maintain a tree with all the modifications required for it.

Since it's a LTS kernel (and because the next Slacko is going to use it), it's a great fit for Puppy.

[pemasu]

build.sh script for compiling 3.7.X kernel.
It needed modification to the aufs_type.h files, to copy them into 2 locations in kernel source.

[anikin]

Is there a way to inject CFLAGS into this kit?

[01micko]

[anikin]

I want to compile the kernel with a list of predefined, machine specific CFLAGS - "march=native etc, etc,(as a noob, I have a long and dangerous list)." So that every bit of performance could be squeezed out of my equipment. Is there a way to "stick" the CFLAGS and make them permanent in this kit and ideally for any compilation task? Do once and forget about it approach?

Thank you in advance

[01micko]

anikin


When you run ./build.sh, after the sources are downloaded, extracted and patched you are given the option to alter the configuration. It may take some time, but I recommend the first option which gives a dialog interface to configuration. Go through it fastidiously and check all the things related to your processor and what hardware you want supported. You can get a very specific kernel this way tuned exactly how you want. The configs supplied are very general to support as much hardware as possible.

------------------------------------------------------------------------------------------------------------

For anyone interested, I have found patches for k3.7 that support f2fs. They apply cleanly. Just put them into the patches directory in the kit. Attached also is a config I used. Vary it how you want. I haven't yet tested the resulting kernel. Soon.

Apparently patches can be applied to k3.6 for f2fs, but I didn't find them. They will be around somewhere, maybe even these ones will work. Probably not on anything earlier though.

Here is the original source of the patches. I only had to edit patch 16 because it didn't know about aufs, only 1 line.

EDIT: patches and config removed, while the kernel worked fine, f2fs was failing to mount, so stick to >= 3.8x if you want f2fs file system.