Re: [systemd-devel] Systemd-cryptsetup triggers a black screen after upgrading to 6.4.1

2023-07-10 Thread Lennart Poettering
On Do, 06.07.23 18:07, Felix Rubio (fe...@kngnt.org) wrote: > Using arch linux, I have had my kernel upgraded from 6.3.9 to 6.4.1. After > regenerating the UKI, that works, I get just a black screen when > systemd-cryptsetup should be either using the TPM to unlock the drive or to > ask me the res

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

2023-07-10 Thread Marc Haber
On Mon, Jul 10, 2023 at 12:11:01PM +0200, Lennart Poettering wrote: > ProtectHome= protects /home/, nothing else. Hence you can use it, and > it should not collide with bind's use of the home dir, because it's > not in /home. > > Actually, correcting myself: use ReadOnlyBindPaths= for this. client

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

2023-07-10 Thread Lennart Poettering
On Mo, 10.07.23 11:37, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > Hi Lennart, > > On Mon, Jul 10, 2023 at 10:28:52AM +0200, Lennart Poettering wrote: > > On So, 09.07.23 20:14, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > > > > > > It should suffice bind mounting just the notify so

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

2023-07-10 Thread Marc Haber
Hi Lennart, On Mon, Jul 10, 2023 at 10:28:52AM +0200, Lennart Poettering wrote: > On So, 09.07.23 20:14, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > > > > It should suffice bind mounting just the notify socket, not the full > > > dir. > > > > Is it intended behavior that an empty file is

Re: [systemd-devel] bind-mount of /run/systemd for chrooted bind9/named

2023-07-10 Thread Lennart Poettering
On So, 09.07.23 20:14, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > > It should suffice bind mounting just the notify socket, not the full > > dir. > > Is it intended behavior that an empty file is left at the "mount point" > (what Where= points to) after the unit was stopped? We need an i