linux-kernel - Re: tip: bzip2/lzma now in tip:x86/setup-lzma

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: <alpine.LSU.2.00.0902181012130.5116@fbirervta.pbzchgretzou.qr>
Date:	Wed, 18 Feb 2009 10:20:47 +0100 (CET)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Alain Knaff <alain@...ff.lu>
cc:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	linux-kernel@...r.kernel.org
Subject: Re: tip: bzip2/lzma now in tip:x86/setup-lzma


On Wednesday 2009-02-18 08:48, Alain Knaff wrote:
>
>>  The sanest thing to do is to 
>> compress with all the compressors that are configured into the kernel, 
>> and then use the smallest image of the ones that can be produced, 
>> *including the uncompressed image*.
>
>... so, if I understood correctly, that would mean compressing the
>kernel 4 times, and keeping the smallest?
>Given the relatively low speed of compression, I feel that such a
>feature would really annoy people who compile their kernel often (such
>as kernel or module developers).

I would expect of *module* developers to build their code by means of
an out-of-tree directory, thereby not causing regeneration of the
vmlinux binary or initramfs image. Even if they stayed within the
Linux srctree, they could take a shortcut by explicitly stating the
target (`make that/foo.ko`). modpost is still something that takes
much more time with allmodconfig than compressing the kernel and/or
changed modules over and over.

>Btw, what *is* the standard work flow of supplying your own built-in
>initramfs? Do such developers usually supply a directory tree, or do
>they already cpio it before supplying it to the kernel? Or do they even
>compress it themselves?

As for me: a separate staging directory that is totally unrelated to
the Linux tree, and manually running the cpio command. And not
embodying it into the kernel because all bootloaders used so far
support reading an extra initramfs image.
--
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/