public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: lvivier@redhat.com, passt-dev@passt.top
Subject: Re: [PATCH 2/4] Remove stale archivemount support
Date: Sat, 6 Apr 2024 14:02:58 +1100	[thread overview]
Message-ID: <ZhC7YtfCeCAPSWEB@zatzit> (raw)
In-Reply-To: <20240405200921.0a1f0318@elisabeth>

[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]

On Fri, Apr 05, 2024 at 08:09:32PM +0200, Stefano Brivio wrote:
> On Fri, 22 Mar 2024 13:27:37 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > mbuto has two ways of building the initramfs.  One is the typical approach
> > of staging its contents in a temporary directory, then building the
> > initramfs with cpio.  The other is to create an empty initramfs, mount
> > it with archivemount, and copy things into the mounted archive.
> > 
> > However, the archivemount approach is broken.  I'm not entirely sure why,
> > but it appears not to properly unmount the archive and retrieve the final.
> > filled version.  The upshot is that if archivemount is installed, then
> > mbuto generates an empty, gzip-compressed initramfs instead of whatever it
> > was supposed to.  It looks like this has bitrotted from some earlier
> > working version.
> > 
> > The archivemount approach is not necessary, and honestly a pretty strange
> > and roundabout way of building the initramfs.  Remove it.
> 
> There were two reasons behind that: first off, I mistakenly assumed
> that the kernel could see changes made to the initramfs after boot.

Yeah, that was never going to work.

> Second, it was actually convenient for developing this tool as I could
> just make directories and copies in half-working images. I also had
> half a mind about some usage with QEMU rebooting the guest, and the
> initramfs would change across reboots without having to call mbuto
> again, for bisections or suchlike.

That's not really dependent on using archivemount in any case.  If
qemu re-reads the initrd on each boot, then you can still do this by
rebuilding the image between boots (which is all that archivemount
would do anyway).  If qemu doesn't re-read it, then this won't work
even if you are using archivemount.

> But sure, it turned out to be quite complicated to maintain, and it
> looks like it has been broken on Fedora for a while now (probably due
> to differences between fakeroot and fakeroot-ng I didn't take into
> account), so, with some regrets, I'm fine to drop this now.
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-06  3:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-22  2:27 [PATCH 0/4] mbuto: Assorted fixes and simplifications David Gibson
2024-03-22  2:27 ` [PATCH 1/4] ${wd} is always set, no need to test for it David Gibson
2024-03-22  2:27 ` [PATCH 2/4] Remove stale archivemount support David Gibson
2024-04-05 18:09   ` Stefano Brivio
2024-04-06  3:02     ` David Gibson [this message]
2024-04-25  4:47       ` Stefano Brivio
2024-04-26  1:44         ` David Gibson
2024-03-22  2:27 ` [PATCH 3/4] Split "auto" compression mode into its own path David Gibson
2024-04-05 18:10   ` Stefano Brivio
2024-04-06  3:06     ` David Gibson
2024-04-25  4:46       ` Stefano Brivio
2024-04-26  1:46         ` David Gibson
2024-03-22  2:27 ` [PATCH 4/4] Remove unnecessary cpio_init function David Gibson
2024-04-05 18:08   ` Stefano Brivio
2024-04-06  3:11     ` David Gibson
2024-04-25  4:46       ` Stefano Brivio

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=ZhC7YtfCeCAPSWEB@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://passt.top/passt

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 IMAP folder(s).