Well, I've been playing with 2.2.19 kernels, and noticed something
interesting. When I compile on my RH 7.0 box (gcc 2.96) I get a kernel
that's a fair amount larger than the same kernel compiled on my Debian Slink
box (gcc 2.7.2.3).
gcc 2.96 compiled zImage size: 473320
gcc 2.7.2.3 compiled zImage size: 464668
The above are compiled from EXACTLY the same source (rsynced prior to
compile). Anyone know any gory details about how the newer gcc differs in
terms of optimizations, loop unrolling, etc?
I'm also getting close to a kernel source & config set I'm happy with.
Currently, I've got the following patches to the standard 2.2.19 kernel
source:
linuxrc-always-2.2.19.diff
initrd-archive-2.2.19.diff
ip_masq_vpn-2.2.18.patch.gz
ip_masq_h323-dplay-icq-mms.diff
Several ip_masq modules rolled into a single patch:
ip_masq_dplay-0.3.00
ip_masq_h323 Version 2.2.0 - 16 October 2000
ip_masq_icq-0.56
ip_masq_mms Version 0.91
linux-2.2.19-ow1.diff
linux-2.2.19-reiserfs-3.5.33-patch.bz2
I've also applied the IPSec patches to the kernel, which don't add any size
if IPSec is disabled (or compiled as a module).
Once I get some kernels compiled and tested (hopefully today), I'll be
working on the 1.91 release of IPSec.
Charles Steinkuehler
http://lrp.steinkuehler.net
http://c0wz.steinkuehler.net (lrp.c0wz.com mirror)
_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/leaf-devel
