mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grzegorz Kulewski <kangur@polcom.net>
To: Olaf Hering <olh@suse.de>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	klibc@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [klibc] Re: [PATCH - RFC] Move initramfs configuration to "General setup"
Date: Mon, 8 Aug 2005 16:57:37 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0508081654280.29195@alpha.polcom.net> (raw)
In-Reply-To: <20050808143151.GA6332@suse.de>

On Mon, 8 Aug 2005, Olaf Hering wrote:

> 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

[ Depend or select? ]

So this code should be separated from initrd and put in some other place 
and depend on initrd || initramfs.

>From what I saw reading the code initrd is much more than this code so why 
keep it together?


Thanks,

Grzegorz Kulewski

  reply	other threads:[~2005-08-08 14:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 13:59 Sam Ravnborg
2005-08-08 14:19 ` Grzegorz Kulewski
2005-08-08 14:31   ` [klibc] " Olaf Hering
2005-08-08 14:57     ` Grzegorz Kulewski [this message]
2005-08-08 15:37   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.63.0508081654280.29195@alpha.polcom.net \
    --to=kangur@polcom.net \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olh@suse.de \
    --cc=sam@ravnborg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®