Re: [systemd-devel] MulticastDNS Responder Hostname in Early Boot

2024-04-29 Thread Justin Brown
Yes, all of the command output was run within the initramfs, not the fully booted system. /etc/hostname exists in the initramfs. I ran a couple of tests using systemd.hostname as a kcmdline parameter: => cat /etc/hostname testvm => cat /proc/cmdline bgrt_disable systemd.hostname=testvm => journal

Re: [systemd-devel] MulticastDNS Responder Hostname in Early Boot

2024-04-29 Thread Mantas Mikulėnas
On Mon, Apr 29, 2024 at 9:16 AM Justin Brown wrote: > Hello, > > I'm having some trouble the resolved as a multicast DNS responder in early > boot. I'm trying to setup a headless system with full disk encryption, and > I need to connect remotely (currently using tinyssh) to unlock sysroot and > o

[systemd-devel] MulticastDNS Responder Hostname in Early Boot

2024-04-28 Thread Justin Brown
Hello, I'm having some trouble the resolved as a multicast DNS responder in early boot. I'm trying to setup a headless system with full disk encryption, and I need to connect remotely (currently using tinyssh) to unlock sysroot and other volumes before the boot continues. I use networkd to setup t