From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 056E41381F3 for ; Sun, 1 Sep 2013 14:51:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4ABFEE0CED; Sun, 1 Sep 2013 14:51:03 +0000 (UTC) Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1D665E0B93 for ; Sun, 1 Sep 2013 14:51:01 +0000 (UTC) Received: by mail-wg0-f41.google.com with SMTP id b12so1024000wgh.2 for ; Sun, 01 Sep 2013 07:51:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=SmClTHxl5vQPDefwCn4dPbL0dYUcIg/OrL2/iaaNOOE=; b=nSGZ99Oj0zrCQGT/wVU1TX0e1r5s2+Fx8gBFMxz0QHMQlEsdeMdJ+/X0qtmM+d19/P gesQja2tyDNZ/DHKiueEO0MLSOAE9C0a4b1vPxuNSdGdSkl5RbljUIH+s2sVUibGHkd2 U4FUVcyuiY8Du2J1V2j/uu//rrS3WV2phdrUr95LfKf/squPwLTDQVZUSte3qf23jg33 HgEb+B1xiLizYXOFU37U5MaZouEkVEPursLNAykra/K120k4P6wlB20Ahwpt96V+xJrC LVm1KnU/Rb1/OK4bZ05Li3zzzNrEAgfUgGe0a/DBnmulVlIcWkXF71UzsXrcqcn4V0sf jTLg== X-Received: by 10.180.76.48 with SMTP id h16mr9286444wiw.32.1378047060769; Sun, 01 Sep 2013 07:51:00 -0700 (PDT) Received: from [172.20.0.41] (196-210-102-25.dynamic.isadsl.co.za. [196.210.102.25]) by mx.google.com with ESMTPSA id iz19sm10993702wic.9.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Sep 2013 07:51:00 -0700 (PDT) Message-ID: <52235378.1020706@gmail.com> Date: Sun, 01 Sep 2013 16:47:20 +0200 From: Alan McKinnon User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130809 Thunderbird/17.0.8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Optional /usr merge in Gentoo References: <20130831120831.GA25399@pacific.net.au> <5221df6c.WS8p51iIG1y/cHXy%Joerg.Schilling@fokus.fraunhofer.de> <20130901001352.GB19271@waltdnes.org> <20130901035501.GA19963@waltdnes.org> <52234FA0.8060403@libertytrek.org> In-Reply-To: <52234FA0.8060403@libertytrek.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 1c5e91ad-7242-4e4d-aecb-e3fcb3017586 X-Archives-Hash: 0e3d3ab7cf07a0090c9e0d0ca723af66 On 01/09/2013 16:30, Tanstaafl wrote: > On 2013-09-01 12:31 AM, Canek Peláez Valdés wrote: >> Of course, support for an initramfs is not actually a file system >> (it's not even in the File systems section of the kernel >> configuration, is in General setup); it's not possible to have >> initramfs as a module (that would make no sense at all); and it's >> code that is several orders of magnitude more simpler than the one >> used by ext4 (or any other journal file system). > > Is there any reason that the creation, use and maintenance of the > initramfs couldn't be as simple as a checkbox in the kernel config, so > that running 'make' after the kernel was configured would automatically > build it? Then, all I'd have to do is move it into /boot along with the > new kernel (just like I do now), with *nothing* else required, and the > kernel would call it, and things would just work (as long as it was > there and I didn't forget to copy it to /boot). That would require a config file of some sort to define what files you want in the initramfs, and it must be available to the kernel build process. It also has to read your self-defined arbitrary stuff from your userland. The kernel build machinery is a self-contained environment, the kernel devs work very hard to keep userland out of it. So expect Linux to shoot you down in flames for the very suggestion. You keep asking for tools to automate the production of an initramfs; you should realize that the thing has got absolutely nothing to do with building and running a kernel, it's a helper function, and not really tied to the kernel per se. Just rig your kernel update process to add a section where you run the command that builds an initramfs. You already have so many steps where you do exactly that in other areas so it's not a realistic issue, and you take that in your stride. Or at it to the end of your kernel build wrapper script if you wrote such a thing for yourself. -- Alan McKinnon alan.mckinnon@gmail.com