public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jimmy bahuleyan <knight.camelot@gmail.com>
To: Christoph Pleger <Christoph.Pleger@cs.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Size of kernel modules
Date: Wed, 06 Jun 2007 21:29:56 +0530	[thread overview]
Message-ID: <4666D9FC.8030002@gmail.com> (raw)
In-Reply-To: <20070606170534.67b5dea9.Christoph.Pleger@cs.uni-dortmund.de>

Christoph Pleger wrote:
> Hello,
> 
[snip]
> After the new kernel package had been created, I installed it. After
> that, I looked into the directory /boot and was very surprised: The
> initial ramdisk of the new kernel was much larger than the initrd of the
> old kernel. To find out the cause for this, I investigated how
> directories /lib/modules/$old and /lib/modules/$new differ. I found out
> that the filenames are the same, but the size of the files differs very
> much. I found a module file in the new directory that was almost five
> times as large as the file with the same name in the old directory.
> 

sounds more like you have debug options enabled?

-jb
-- 
Tact is the art of making a point without making an enemy.

  parent reply	other threads:[~2007-06-06 16:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 15:05 Size of kernel modules Christoph Pleger
2007-06-06 15:51 ` Jesper Juhl
2007-06-06 16:56   ` Jan Engelhardt
2007-06-06 17:17   ` Sam Ravnborg
2007-06-06 15:59 ` jimmy bahuleyan [this message]
2007-06-06 17:22 ` Sam Ravnborg
2007-06-06 18:40 ` Joseph Fannin
2007-06-08  3:44 ` Kyle McMartin
2007-06-08 12:40   ` Robert P. J. Day
2007-06-08 18:59     ` Chuck Ebbert
2007-06-09  7:55     ` Jan Engelhardt
2007-06-09 12:08       ` Jon Masters
2007-06-09 13:59         ` Jan Engelhardt
2007-06-09 16:14           ` Jon Masters
2007-06-09 18:56           ` Satyam Sharma
2007-06-10 13:13           ` Sergey Vlasov

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=4666D9FC.8030002@gmail.com \
    --to=knight.camelot@gmail.com \
    --cc=Christoph.Pleger@cs.uni-dortmund.de \
    --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