From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-lf0-f50.google.com ([209.85.215.50]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from ) id 1fYzgN-0007Op-7Z for ptxdist@pengutronix.de; Fri, 29 Jun 2018 22:07:52 +0200 Received: by mail-lf0-f50.google.com with SMTP id n24-v6so7638386lfh.3 for ; Fri, 29 Jun 2018 13:07:51 -0700 (PDT) MIME-Version: 1.0 References: <20180618094946.evuufmqncbqsol3h@pengutronix.de> <20180619143115.dsudbzwieqztzo3c@pengutronix.de> In-Reply-To: <20180619143115.dsudbzwieqztzo3c@pengutronix.de> From: Jon Ringle Date: Fri, 29 Jun 2018 16:07:38 -0400 Message-ID: Subject: Re: [ptxdist] initramfs List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: ptxdist@pengutronix.de Content-Type: multipart/mixed; boundary="===============1531339826==" Errors-To: ptxdist-bounces@pengutronix.de Sender: "ptxdist" To: ptxdist@pengutronix.de --===============1531339826== Content-Type: multipart/alternative; boundary="000000000000f57017056fcd6636" --000000000000f57017056fcd6636 Content-Type: text/plain; charset="UTF-8" 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 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 --000000000000f57017056fcd6636 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Sorry for the delay in response on this. My laptop di= ed and spent a couple days rebuilding it and catching up on work before goi= ng on vacation...

On Tue, Jun 19, 2018 at 10:31 AM Michael Olbrich <m.olbrich@pengutronix.de> wr= ote:
> 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 ne= eded.
>
> 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 o= f
> 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 recover= y 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 othe= r tools

2. As a means of performing firmware updat= es.
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.
=C2=A0
3. Mounting the rea= l rootfs

-Jon
--000000000000f57017056fcd6636-- --===============1531339826== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcHR4ZGlzdCBt YWlsaW5nIGxpc3QKcHR4ZGlzdEBwZW5ndXRyb25peC5kZQ== --===============1531339826==--