public inbox for initramfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Hartman <hartmans-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Matthew Garrett <mjg59-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Cc: debian-devel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org,
	debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org,
	initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Producing verifiable initramfs images
Date: Wed, 05 Feb 2020 20:53:21 -0500	[thread overview]
Message-ID: <tslzhdwh46m.fsf@suchdamage.org> (raw)
In-Reply-To: <CACdnJutwsCPERLR=tF65O=2tCgf+BHbWmsC6bpVrhwyOXcKCxA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> (Matthew Garrett's message of "Wed, 5 Feb 2020 16:37:39 -0800")

This is not a disagreement with anything you write.

I've noticed that there is a lot more configuration that gets encoded in
the initramfs than I thought.
The most surprising for me is that if you want to control the names of
network devices or anything else set by the .link file,
that ends up needing to go on the initramfs, because udevd will set up
network devices even if they are not needed to find the root.
Unfortunately, that means that initramfs udev configuration (including
/etc/systemd/network/*.link) tends to need to be on the initramfs.

I realize you only gave crypttab as an example, but the set of initramfs
configuration is larger than I at least expected.

--Sam

  parent reply	other threads:[~2020-02-06  1:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  0:37 Producing verifiable initramfs images Matthew Garrett
     [not found] ` <CACdnJutwsCPERLR=tF65O=2tCgf+BHbWmsC6bpVrhwyOXcKCxA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2020-02-06  1:53   ` Sam Hartman [this message]
2020-02-06  7:31   ` Niels Thykier

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=tslzhdwh46m.fsf@suchdamage.org \
    --to=hartmans-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
    --cc=debian-devel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
    --cc=debian-kernel-0aAXYlwwYIJuHlm7Suoebg@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mjg59-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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