Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #66320
| From | Sam Hartman <hartmans@debian.org> |
|---|---|
| Newsgroups | linux.debian.devel, linux.debian.kernel |
| Subject | Re: Producing verifiable initramfs images |
| Date | 2020-02-06 03:40 +0100 |
| Message-ID | <zwFfb-8av-1@gated-at.bofh.it> (permalink) |
| References | <zwDGp-7bq-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
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
Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Producing verifiable initramfs images Matthew Garrett <mjg59@google.com> - 2020-02-06 02:00 +0100 Re: Producing verifiable initramfs images Sam Hartman <hartmans@debian.org> - 2020-02-06 03:40 +0100
csiph-web