From: Daniel Egger <degger@fhm.edu>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Kernel bloat 2.4 vs. 2.5
Date: 06 Mar 2003 04:25:15 +0100 [thread overview]
Message-ID: <1046921111.484.10.camel@sonja> (raw)
In-Reply-To: <20030304154105.7a2db7fa.akpm@digeo.com>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Am Mit, 2003-03-05 um 00.41 schrieb Andrew Morton:
> Please specify the compiler which was used, and use /usr/bin/size to report
> image sizes.
The compiler was in both cases:
gcc version 3.2.3 20030228 (Debian prerelease)
2.4.20:
2271565 Feb 25 17:08 vmlinux
text data bss dec hex filename
1730302 112564 176676 2019542 1ed0d6 vmlinux
2.5.63:
2561828 Mar 4 16:50 vmlinux
text data bss dec hex filename
1867787 167450 140292 2175529 213229 vmlinux
As I said, the 2.4 kernel has almost everything built in while 2.5 was
stripped down to minimum size possible. The latter is still unusable
since modules do not work. :/
--
Servus,
Daniel
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-06 3:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 22:42 Kernel bloat 2.4 vs. 2.5 Daniel Egger
2003-03-04 23:41 ` Andrew Morton
2003-03-05 1:59 ` Chris Wedgwood
2003-03-05 2:11 ` Andrew Morton
2003-03-05 2:23 ` Robert Love
2003-03-05 2:32 ` Andrew Morton
2003-03-05 2:37 ` Robert Love
2003-03-05 3:13 ` Steven Cole
2003-03-05 3:06 ` Chris Wedgwood
2003-03-05 2:35 ` Kai Germaschewski
2003-03-06 3:25 ` Daniel Egger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-06 14:22 Felipe Alfaro Solana
2003-03-06 19:51 ` Daniel Egger
2003-03-06 23:34 ` Andreas Boman
2003-03-06 23:44 ` Joel Becker
2003-03-07 13:33 ` Daniel Egger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1046921111.484.10.camel@sonja \
--to=degger@fhm.edu \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox