Building an atlas Kernel
This assumes that a stable linux kernel source tree already exists on a machine (bob, /srv/kernel/linux-stable), cloned via
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
our Atlas kernel should live in the atlas-3.2 branch (assuming kernel 3.2 is wanted)
git checkout -b atlas-3.2
For different kernel versions there are multiple directories like
/srv/kernel/linux-stable-3.XX
.
ensure it is up to date
fetch latest changes (but
DO NOT pull)
git fetch
remote: Counting objects: 121068, done.
remote: Compressing objects: 100% (20355/20355), done.
Receiving objects: 100% (95278/95278), 25.43 MiB | 4.23 MiB/s, done.
remote: Total 95278 (delta 79514), reused 89120 (delta 73891)
Resolving deltas: 100% (79514/79514), completed with 9298 local objects.
From git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable
ab78f67..ce05b1d linux-3.0.y -> origin/linux-3.0.y
8432d22..f1e79c6 linux-3.2.y -> origin/linux-3.2.y
763c71b..0d0eef5 linux-3.4.y -> origin/linux-3.4.y
* [new branch] linux-3.5.y -> origin/linux-3.5.y
76e10d1..28a33cb master -> origin/master
* [new tag] v3.0.38 -> v3.0.38
* [new tag] v3.2.24 -> v3.2.24
* [new tag] v3.4.7 -> v3.4.7
* [new tag] v3.5 -> v3.5
From git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable
* [new tag] v3.4.6 -> v3.4.6
* [new tag] v3.5-rc1 -> v3.5-rc1
* [new tag] v3.5-rc2 -> v3.5-rc2
* [new tag] v3.5-rc3 -> v3.5-rc3
* [new tag] v3.5-rc4 -> v3.5-rc4
* [new tag] v3.5-rc5 -> v3.5-rc5
* [new tag] v3.5-rc6 -> v3.5-rc6
* [new tag] v3.5-rc7 -> v3.5-rc7
now rebase against against latest version tag, e.g. v3.2.24
git rebase v3.2.24
which should re-apply all local patched
Special patches
See attached list
With the 2013 network change and kernels from 3.10 onwards it seems we don't need the NIC patch anymore.
build kernel
export INSTALL_MOD_STRIP=1
make -j 8 deb-pkg
when this is done, the new kernel packages are one level up.
--
CarstenAulbert - 21 Jan 2010