![](https://seccdn.libravatar.org/avatar/be57f3b805fac8f81a214dd74cb790e1.jpg?s=120&d=mm&r=g)
I believe that when you use: make zImage -- it makes that file if you type: make zlilo -- instead, the kernel will be compressed and installed automatically hope that helps mc TEX wrote:
Thanks for explaining why the kernel comes from where it does. I have been trying to figure that one out. When does it get compressed and called zImage?
Thanks again..
Michael Clark wrote:
Lawrence Sayre wrote:
thing that I did on my first few attempts to manually compile my own kernels was trying to install the uncompressed kernel. When I would compile the kernel, I would copy the kernel to /vmlinuz and run lilo.
/usr/src/linux/vmlinuz about 870k, kernel too big
/usr/src/linux/arch/i386/boot/zImage about 360k, works great!! :-)
It sounds like this may be the problem. If not, maybe this will save someone else headaches.
mc
-- - - -- IMHO BEST Beginners book so far. Sams' Teach Yourself Linux in 24 hours. redhat press.
- Celis Gran Cru and Linux; Nowhere but South Austin Texas. - - - TEX <A HREF="http://www.ccms.net/~mhtexcollins/78704.htm"><A HREF="http://www.ccms.net/~mhtexcollins/78704.htm</A">http://www.ccms.net/~mhtexcollins/78704.htm</A</A>>
__ / / __ _ _ _ _ __ __ / /__ / / / \// //_// \ \/ / /____/ /_/ /_/\/ /___/ /_/\_\ ...for IQs GREATER than 95/98?... ---
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e