On Thu, 06 Apr 2023 at 18:56:49 +0200, William Desportes wrote: > with cryptsetup it does not like rescue mode initramfs updates.
Hm? Installing cryptsetup-initramfs, and letting it unlock devices (incl. those holding the root FS) at early boot stage, definitely doesn't prevent rescue mode or getting an initramfs shell. > That said I have a new one (I did not install the basic system utilities): > > It now says: init-premount/dropbear: line 366: ipconfig: not found > > And right after the message about net-*.conf dropbear-initramfs doesn't call ipconfig or configure the network directly. All it does is: call initramfs-tools' configure_networking() at init-premount stage, and bring the interface down at init-bottom stage. > The system does not have ipconfig installed, What do you mean? Your main system (outside) initramfs stage might lack /usr/bin/ipconfig but that is irrelevant. What matters is that the binary is available at initramfs stage. > I would say this is a bug that should be fixed in the dropbear script. > Or added a as a package dependency/requirement ? Nope. The /usr/bin/ipconfig binary from the initramfs image comes from /usr/lib/klibc/bin/ipconfig which dropbear-initramfs indirectly has a hard Depends: on… Anyway, the ‘/run/net-*.conf’ glob and the ipconfig call both come initramfs-tools' configure_networking(). As I wrote before if these fail it's most likely because there is nothing blocking at initramfs stage, so execution is handed over to init(1) before configure_networking() has a chance to terminate (it runs in the background). This, again, smells like #1015810. -- Guilhem.
signature.asc
Description: PGP signature
