From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] initramfs
Date: Fri, 29 Jun 2018 16:07:38 -0400 [thread overview]
Message-ID: <CAMwGMjxVt=aCXsABa8MJAZu474t=BobQ7+W-R07kf011J9-3DQ@mail.gmail.com> (raw)
In-Reply-To: <20180619143115.dsudbzwieqztzo3c@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1320 bytes --]
Sorry for the delay in response on this. My laptop died and spent a couple
days rebuilding it and catching up on work before going on vacation...
On Tue, Jun 19, 2018 at 10:31 AM Michael Olbrich <m.olbrich@pengutronix.de>
wrote:
> I'd still like to know a bit more about your use-case. I know very little
> about what other people out there are doing with PTXdist, so it's
sometimes
> hard to decide if I can rip out some old stuff of if it's still needed.
>
> It it a initramfs only setup, or is there a normal rootfs as well? In the
> later case, how do you create the initramfs? Which packages are part of
> initramfs?
We have separate ptxdist projects that build the real rootfs vs the linux
kernel image with an embedded initramfs image.
The initramfs content is simply whatever packages are selected and whatever
they install via the targetinstall for each package.
Our initramfs has 3 purposes:
1. Emergency recovery console (mainly used as a means to break out of a
reboot loop encountered during development)
For this we have busybox, ash and a few other tools
2. As a means of performing firmware updates.
I use the initramfs-tools to provide the init script and use the script
hooks it provides to check if a firmware update is needed before the real
rootfs is mounted.
3. Mounting the real rootfs
-Jon
[-- Attachment #1.2: Type: text/html, Size: 1831 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-06-29 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 16:37 Jon Ringle
2018-06-18 9:49 ` Michael Olbrich
2018-06-18 12:11 ` Jon Ringle
2018-06-19 14:31 ` Michael Olbrich
2018-06-29 20:07 ` Jon Ringle [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='CAMwGMjxVt=aCXsABa8MJAZu474t=BobQ7+W-R07kf011J9-3DQ@mail.gmail.com' \
--to=jon@ringle.org \
--cc=ptxdist@pengutronix.de \
/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