public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Kris Shannon <kris.shannon.kernel@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Separate Initramfs dependency on initrd (and therefore ramdisks)
Date: Tue, 11 Apr 2006 12:57:10 +0400	[thread overview]
Message-ID: <443B6F66.3020302@tls.msk.ru> (raw)
In-Reply-To: <5d4799ae0604101855o72f01453l438d0d4d628bbb7@mail.gmail.com>

Kris Shannon wrote:
> A number of distributions (most importantly for me - Debian) use the
> initrd as initramfs facility.  I assumed that the passing of the data
> block would be independent of ram disks seeing as not using a ram
> disk was one of the major reasons for initramfs,  but it seems that
> you need CONFIG_BLK_DEV_INITRD=y which depends on
> CONFIG_BLK_DEV_RAM=y
> 
> Would a patch separating out the init image handling from the initrd
> handling be welcome and if so should the resulting init image code
> be dependant on a CONFIG variable or always on (like initramfs is now)
> 
> The only reference to this I found in the archives was:
> 
> http://www.uwsg.indiana.edu/hypermail/linux/kernel/0508.1/0097.html

http://www.ussg.iu.edu/hypermail/linux/kernel/0603.1/0969.html

/mjt

      reply	other threads:[~2006-04-11  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-17 16:20 Separate Initramfs dependency on initrd (and therefore ramdisks) Kris Shannon
2006-04-11  1:55 ` Kris Shannon
2006-04-11  8:57   ` Michael Tokarev [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=443B6F66.3020302@tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=kris.shannon.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.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