From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Embedded Linux mailing list <linux-embedded@vger.kernel.org>
Subject: can initrd and initramfs be made independent?
Date: Wed, 3 Jun 2009 13:10:45 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0906031307580.7946@localhost.localdomain> (raw)
as it stands, when configuring the kernel, you can't select
initramfs capability without also selecting initrd. but isn't it
feasible that you might want initramfs and have no need for initrd?
if you make those selections independent, the help info suggests you
can save 15Kb by not having RAM disk (initrd) support.
or is there an interdependence here that's not so obvious?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
reply other threads:[~2009-06-03 17:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.2.00.0906031307580.7946@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