From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750894AbVHHOb5 (ORCPT ); Mon, 8 Aug 2005 10:31:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750900AbVHHOb5 (ORCPT ); Mon, 8 Aug 2005 10:31:57 -0400 Received: from mx1.suse.de ([195.135.220.2]:62430 "EHLO mx1.suse.de") by vger.kernel.org with ESMTP id S1750893AbVHHOb4 (ORCPT ); Mon, 8 Aug 2005 10:31:56 -0400 Date: Mon, 8 Aug 2005 16:31:51 +0200 From: Olaf Hering To: Grzegorz Kulewski Cc: Sam Ravnborg , klibc@zytor.com, linux-kernel@vger.kernel.org Subject: Re: [klibc] Re: [PATCH - RFC] Move initramfs configuration to "General setup" Message-ID: <20050808143151.GA6332@suse.de> References: <20050808135936.GA9057@mars.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-DOS: I got your 640K Real Mode Right Here Buddy! X-Homeland-Security: You are not supposed to read this line! You are a terrorist! User-Agent: Mutt und vi sind doch schneller als Notes (und GroupWise) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 08, Grzegorz Kulewski wrote: > >From my recent experiments it looks like in order to be able to use > initramfs not compiled into the kernel image but loaded from separate file > by GRUB or LILO one must also build initrd into the kernel. The file passed from the bootloader to the kernel, which is later eventually recognized as an initrd, can be everything. But the kernel code to deal with the memory range containing the file is behind CONFIG_BLK_DEV_INITRD. The new config options should depend on BLK_DEV_INITRD