From: Mike Fedyk <mfedyk@matchmail.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unnecessary objects built in 2.6.0-test4?
Date: Mon, 1 Sep 2003 14:04:29 -0700 [thread overview]
Message-ID: <20030901210429.GD31760@matchmail.com> (raw)
In-Reply-To: <200309010231.39329.rob@landley.net>
On Mon, Sep 01, 2003 at 02:31:39AM -0400, Rob Landley wrote:
> I'm running 2.6.0-test4 on my laptop, and it's quite nice. (Haven't beaten
> also into submission yet, and it won't suspend, and kde is dropping some
> events, but everything else is chugging along quite nicely...)
>
> But the kernel is huge, an I'm curious why. So I did this in the build
> directory:
>
Yes, I have seen this too, but the kernel image size wasn't affected, only
the modules sizes.
I have posted a message on this recently, but nothing came from it... :(
Sorted by date:
7.7M Jul 14 15:03 ../kernel-image-2.6.0-test1_nmf.1_i386.deb
7.7M Jul 16 12:12 ../kernel-image-2.6.0-test1-drv-debug1_nmf.1_i386.deb
6.3M Jul 16 17:19 ../kernel-image-2.6.0-test1-mm1-06int_nmf.1_i386.deb
6.3M Jul 18 17:53 ../kernel-image-2.6.0-test1-mm1-07int_nmf.1_i386.deb
5.5M Jul 21 13:53 ../kernel-image-2.4.22-pre7_nmf.1_i386.deb
6.4M Jul 22 16:29 ../kernel-image-2.6.0-test1-mm2_nmf.1_i386.deb
6.3M Jul 25 11:36 ../kernel-image-2.6.0-test1-g2_nmf.1_i386.deb
6.4M Jul 28 19:00 ../kernel-image-2.6.0-test2-mm1_nmf.1_i386.deb
5.4M Aug 8 14:03 ../kernel-image-2.4.22-rc1_nmf.1_i386.deb
34M Aug 15 19:17 ../kernel-image-2.6.0-test3-mm2_nmf.1_i386.deb
34M Aug 24 15:43 ../kernel-image-2.6.0-test3-mm3_nmf.1_i386.deb
33M Aug 26 19:37 ../kernel-image-2.6.0-test4-mm1_nmf.1_i386.deb
33M Aug 29 13:54 ../kernel-image-2.6.0-test4-mm3-1-mdfail_nmf.1_i386.deb
33M Aug 30 19:39 ../kernel-image-2.6.0-test4-mm4_nmf.1_i386.deb
prev parent reply other threads:[~2003-09-01 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 6:31 Unnecessary objects built in 2.6.0-test4? Rob Landley
2003-09-01 21:04 ` Mike Fedyk [this message]
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=20030901210429.GD31760@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
/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