From: ngwilliams@gmail.com (Nathan Williams)
To: kernelnewbies@lists.kernelnewbies.org
Subject: want to clarify a couple things about initramfs
Date: Mon, 20 Jun 2016 11:05:34 +1000 [thread overview]
Message-ID: <1466384734.4297.15.camel@linux> (raw)
In-Reply-To: <alpine.LFD.2.20.1606190943310.7465@localhost.localdomain>
On Sun, 2016-06-19 at 09:55 -0400, Robert P. J. Day wrote:
> is all that still accurate? again, i'm sure i can confirm that once
> i start digging through the code. in my case, i don't think i'll need
> an external initramfs if i can cram everything i need into the one
> embedded in the kernel.
Hi Robert,
Yes I believe the documentation is still accurate. An initramfs image
can either be linked into the kernel image, or passed to the kernel by
the bootloader (e.g. U-Boot)
I use Buildroot to build a kernel with an embedded rootfs that has all
the tools I need for testing an embedded system. I've also used
Buildroot to make a cpio archive of the root filesystem and used that as
an external initramfs.
Nathan
prev parent reply other threads:[~2016-06-20 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-19 13:55 want to clarify a couple things about initramfs Robert P. J. Day
2016-06-20 1:05 ` Nathan Williams [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=1466384734.4297.15.camel@linux \
--to=ngwilliams@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).