From: Grzegorz Kulewski <kangur@polcom.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, klibc@zytor.com
Subject: Re: [PATCH - RFC] Move initramfs configuration to "General setup"
Date: Mon, 8 Aug 2005 16:19:50 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.63.0508081610400.29195@alpha.polcom.net> (raw)
In-Reply-To: <20050808135936.GA9057@mars.ravnborg.org>
On Mon, 8 Aug 2005, Sam Ravnborg wrote:
> At present the configuration items for initramfs is located in:
> Device drivers | Block Drivers | xxx
>
> This is maybe not the most natural place to have it.
> So with the following patch it is moved below "General setup",
> and relevant config items are collected in a file with a new
> home in usr/.
>
> The original reason why I looked into this is the upcoming merge of klibc
> and I missed a good place to include the KLIBC relevant config options.
> With the Kconfig file added to usr/ is will be a simple menuconfig
> in here for all the KLIBC relevant config options.
>
> Any comments?
>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.
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...
Thanks,
Grzegorz Kulewski
next prev parent reply other threads:[~2005-08-08 14:19 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 [this message]
2005-08-08 14:31 ` [klibc] " Olaf Hering
2005-08-08 14:57 ` Grzegorz Kulewski
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.0508081610400.29195@alpha.polcom.net \
--to=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 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®