Re: Problems packaging a kernel using cdbs
On 3/16/07, Roberto C. Sanchez <roberto@connexer.com> wrote:
On Fri, Mar 16, 2007 at 01:50:14PM -0400, Luis R. Rodriguez wrote:
> I've seen some posts on debian-devel from a while back which indicates
> some of you (Robert Millan) you've build a kernel using cdbs. I'm
Perhaps I misunderstand, but can't you use kernel-package?
My goal is to actually generate a debian package which will have a
very small x86 kernel and a very very custom initramfs (bundles of
software) for a PXE boot environment. Kernel-package lets me build a
debian package out of the kernel source tree, but I want to do
something a bit different. I just looked into kernel-package's support
for generating custom initramfs cpio archives but it really lacks
documentation even on the source. I then checked out initramfs-tools
but just installing this package makes it spin an generate an
initramfs for me on /boot/ without even consulting...; then I read the
man page for mkinitramfs and I see this:
---
At boot time, the kernel unpacks that archive into RAM disk,
mounts and uses it as initial root file system. All finding of the
root device hap-
pens in this early userspace.
--
initramfs is not an archive that gets put into a RAM disk, the ramdisk
is only used by initrd... the new design of initramfs replaces that
whole mess and takes advantage of the new tmpfs filesystem. The fact
that the man page has it wrong doesn't make me want to touch that in
any way.
Anyway -- I just tried to use "make-kpkg build" as the build commands
for my "kernel" target and still run into the same problem. Running
"make-kpkg build" manually works though. So there is something about
using cdbs that is not letting me build the kernel right. The include
path gets (./include) is getting ignored completely for some reason.
Luis
Reply to: