Simply:
1) use bzImage and not zImage
2) If the make processes tells you at the end that the kernel/system is
too big, it's too big
3) If, when you update /etc/lilo and run /sbin/lilo to update the MBR, you
get some error similar to #2, it's too big
4) Everything else will work :)
On Fri, 5 Ap
Are you sure the kernel wouldn't run? It's common to receive a
warning that the kernel may be too large, but I believe that warning applies
to older systems or floppy boot disks. The kernel is the file
/arch/i386/boot/bzImage. That's assuming your building for a i386 platform.
On my mac
>
>This is my first foray into the world of Linux kernel building. I have
> built kernels
> for other commercial unix systems, without any real problems.I noticed
> that
> I built a kernel that was too big. I think it was 1.2 meg. Why is this
> too big?
Well, the build process
> In my understanding, the kernel size is limited by the size of the
> master-boot-record,
>
[PT] Nope. It is due to the size of the Intel processor's
real mode versus its protected mode. All PC clones
still boot into real mode (640KB) because the BIOS
is still
Dear Greg,
In my understanding, the kernel size is limited by the size of the
master-boot-record, because part of your kernel gets stored there (LILO) in
order to enable you to boot. What you could try is using "make bzImage" instead
of "make zImage" this should do the trick. If you realy need a
