All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Grzegorz Kulewski <kangur@polcom.net>
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, 08 Aug 2005 08:37:57 -0700	[thread overview]
Message-ID: <42F77C55.9040501@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508081610400.29195@alpha.polcom.net>

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.
> 
> Am I right? If so, could somebody split initramfs and initrd (not only 
> at configuration level but also at code level)? Shouldn't they be 
> separated (and possibly initrd removed after some time)? In the mean 
> time it should be documented in *config help.
> 

Actually, most of CONFIG_INITRD is about being able to pick up the 
second load datum, so it makes sense on the code level at least.

> Also somebody should add more documentation about initramfs (generating, 
> writing scripts, producing image, the right method for chroot / 
> pivot_root / ...). It took me whole week to find it out myself and I 
> still have some doubths...

Yes, that would be good.

	-hpa

      parent reply	other threads:[~2005-08-08 15:38 UTC|newest]

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

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=42F77C55.9040501@zytor.com \
    --to=hpa@zytor.com \
    --cc=kangur@polcom.net \
    --cc=klibc@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.