From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Embedded Linux mailing list <linux-embedded@vger.kernel.org>
Subject: is it worth separating initrd from initramfs support?
Date: Mon, 4 Aug 2008 14:53:26 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0808041449420.9561@localhost.localdomain> (raw)
not sure if i asked this here once upon a time but, in the current
kernel, you get to select support for *both* initrd and initramfs with
a single selection (CONFIG_BLK_DEV_INITRD).
however, folks who have been around a while generally associate the
feature INITRD with, well, an initrd image, while initramfs is
something a bit newer.
in the context of embedded linux, is there any value in separating
these features and letting one select them individually? isn't it
reasonable to think that one might need initramfs support but have
absolutely no use for "initrd" support? or is that not worth worrying
about?
rday
--
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
Have classroom, will lecture.
http://crashcourse.ca Waterloo, Ontario, CANADA
========================================================================
next reply other threads:[~2008-08-04 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 18:53 Robert P. J. Day [this message]
2008-08-04 20:16 ` is it worth separating initrd from initramfs support? Leon Woestenberg
2008-08-04 20:29 ` Robert P. J. Day
2008-08-04 23:07 ` Robert P. J. Day
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=alpine.LFD.1.10.0808041449420.9561@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=linux-embedded@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;
as well as URLs for NNTP newsgroup(s).