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

Re: [systemd-devel] soft-reboot and surviving it

2024-04-29 Thread Thorsten Kukuk
Sorry for the late response, we had a conference last week. On Sat, Apr 20, 2024 at 8:18 PM Luca Boccassi wrote: > Having no dependency on the rootfs is a core requirement that we > cannot change, the filesystem used is irrelevant. It's not going to > work, it will break immediately if you are l

Re: [systemd-devel] soft-reboot and surviving it

2024-04-29 Thread Thorsten Kukuk
On Sat, Apr 20, 2024 at 8:21 PM Luca Boccassi wrote: > > On Sat, 20 Apr 2024 at 01:45, Cristian Rodríguez > wrote: > > > > On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > > > > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > > > wrote: > > > > > > > However, logging should work ou

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