linux-kernel - Re: initrd image size of 3.1.0 kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAM_iQpU+8bNFCXNP+NRrEWrsxj7TZRjVF1x3wBuXNubX+4LQEg@mail.gmail.com>
Date:	Thu, 27 Oct 2011 16:11:56 +0800
From:	Américo Wang <xiyou.wangcong@...il.com>
To:	Brad Tilley <brad@...ystems.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: initrd image size of 3.1.0 kernel

On Wed, Oct 26, 2011 at 8:51 PM, Brad Tilley <brad@...ystems.com> wrote:
> I built a vanilla stable kernel using the most recent 3.1.0 stable source.
> I built it like this:
>
> make silentoldconfig
> make deb-pkg
>
> The kernel boots and runs fine. However, the size (greater than 100 MB) of
> the initrd image surprised me. Doing the same sort of build for a 3.0.x
> kenerl produces a much smaller image:
>
> -rw-r--r--  1 root root  12M Sep  6 11:57 initrd.img-3.0.4
> -rw-r--r--  1 root root 107M Oct 26 08:03 initrd.img-3.1.0
>
> I only want to point this out. Perhaps I missed something in the
> documentation that explains the size difference, or something in my old
> config or toolset caused it.

Hi,

I am not a Debian user, so what is the 'mkinitrd' on Debian? The tool
to make the initrd image. I think it is its fault, rather than the kernel.
It is unlikely some kernel modules increases the size so much...

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/