linux-kernel - Re: Auto generate .config.

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]

Date:	Fri, 12 Dec 2008 11:34:59 -0500
From:	Jon Masters <jonathan@...masters.org>
To:	Marcello Henrique <faraohh@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Auto generate .config.

On Fri, 2008-12-12 at 14:20 -0200, Marcello Henrique wrote:

> I understand that this is possible, but would not be possible to
> generate one .config of modules that are running to compile a kernel
> optimized?
> 
> The idea is that the kernel of my distribution is too fat and I only
> generate a kernel module that I use automatically from a kernel fat.
> understand?

Several people have written scripts over the years to do this. I don't
have one handy, but I suspect the LKML (linux-kernel) archives know.

Note that module overhead is not /too/ bad these days. It used to be
that loading modules significantly affected boot time, but some recent
improvements have helped - including a few fixes to module-init-tools:
binary trie based index files (v3.5), shortened naming (v3.6), etc. I
think that, really, at this point module loading overhead is small.

Jon.

--
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/