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
platform.
On my machine, my current 2.4.17 kernel is about 1.1 megs.
-Original Message-
From: scott.list [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 05, 2002 3:06 PM
To: [EMAIL PROTECTED]
Subject: Kernel Size
Greeting:
I need to rebuild a kernel on a remote machine. I'
Greeting:
I need to rebuild a kernel on a remote machine. I'm proficient enough
at the build steps but in the past I got the lernel too big and it
wouldn't run.
How can I tell what "size" the kernel is before I reboot with it to
know it will not be too large?
Thanks,
Scott
___
>
>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 B
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
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?
I got the error message at the very end
