From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755744AbZBSSEb (ORCPT ); Thu, 19 Feb 2009 13:04:31 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753477AbZBSSEH (ORCPT ); Thu, 19 Feb 2009 13:04:07 -0500 Received: from terminus.zytor.com ([198.137.202.10]:38288 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753396AbZBSSEG (ORCPT ); Thu, 19 Feb 2009 13:04:06 -0500 Message-ID: <499D9EF3.5070903@zytor.com> Date: Thu, 19 Feb 2009 10:03:31 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Alain Knaff CC: Jan Engelhardt , Ingo Molnar , the arch/x86 maintainers , linux-kernel@vger.kernel.org Subject: Re: tip: bzip2/lzma now in tip:x86/setup-lzma References: <200901042146.n04LkHgP005837@hitchhiker.hitchhiker.org.lu.hitchhiker.org.lu> <4961415C.1050708@zytor.com> <49614243.70102@knaff.lu> <496142E4.8040308@zytor.com> <49614491.7020903@knaff.lu> <49614D1F.8020900@zytor.com> <499B267E.2090509@zytor.com> <20090217220825.GA24337@elte.hu> <20090217233708.GA10756@elte.hu> <499B5BCA.8000905@zytor.com> <499BBD62.5090506@knaff.lu> <499BD795.6050602@knaff.lu> <499CF8D2.9080309@knaff.lu> <499D70CE.6050508@zytor.com> <499D7DA6.3060007@knaff.lu> In-Reply-To: <499D7DA6.3060007@knaff.lu> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Alain Knaff wrote: > > Could you please elaborate why you consider this so wrong? > Because in some flows, a large initramfs is built without CONFIG_INITRAMFS_SOURCE. More fundamentally, it's a bad case of trying to guess what the user wants based on unrelated criteria than simply making it configured. What we should have done in the first place is to make the initrd compression selectable just like the kernel compression, with the additional option of uncompressed (which some people want for the main kernel, by the way; we just don't have it at the moment.) I don't know if we can set it up in Kconfig to default to the same compression as the kernel uses, but more importantly we can constrain it to the supported initrd compressions. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.