Re: Rebuild Kernel for Qube 2 on sarge and LCD Status Display like woody
Marcus Schwarz wrote:
> Thiemo Seufer wrote:
> >No, just install all the build dependencies listed in <dir>/debian/control
> >(most notably kernel-source-2.4.26), then change to that directory and run
> >e.g. "dpkg-buildpackage -us -uc -rfakeroot -b" to create all kernel udebs.
> What does this thing exactly do ??
> build a new kernel ? Or just patches the kernel installed in /usr/src ?
It builds the full set of debian kernels. It unpacks the debian kernel
tree in a subdir, patches it with the mips-specific stuff, and creates
all the debian kenrel packages for mips/mipsel (depending on which
machine it runs).
> Sorry but I'm a bit confused ;)
> How do I build a new kernel ?
> I know the way to :
> cd /usr/src/Kernel_Dir
> make menuconfig
> make dep && make clean && make bzImage && make modules && make
This leaves you with a plain kernel unknown to the packaging system,
so you'll have to keep track of it manually instead of using dpkg.
With the debian source, you can do that as well, by calling
"fakeroot debian/rules patch" in the kernel-patch-2.4.26-mips-2.4.26
dir. This will create an already patched tree in the build-tmp subdir.
The debian kernel config files are in the /config subdir, copy it
over to <tree_root>/.config.
Now you can do:
make dep vmlinux modules
Be aware that "fakeroot debian/rules clean" removes the whole tree, so
make sure to save your changes outside before you do that
(dpkg-buildpackage does that by default).
> How does it work on this platform ?
The idea is to allow automated builds of debian packages, with the same
dpkg-buildpackage working for _all_ debian packages. For a modified
kernel, you would create a patchfile for the modification and supply it
as a dpatch in the debian/patches directory (it must be executable and
added to 00list as well.). Once you did that, you can use the
dpkg-buildpackage command to create a complete set of kernel packages
with your modification. If you are only interested in the cobalt
kernel, comment out the other subarchitectures in the debian/rules
For more information about debian packaging, see the various documents