Re: [systemd-devel] Permissions problems with systemd-networkd and others.

2024-02-07 Thread Dave Howorth
On Wed, 7 Feb 2024 20:41:40 + "Murrell, Robert A." wrote: > I finally got everything working. Here is what I did to fix the > problem: > > adduser systemd-network root > adduser systemd-resolve root > adduser bind root > find /etc -type d -exec chmod 755 {} + > > I don’t know who does this

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/7/24 19:55, Andrei Borzenkov wrote: You can add drop-in to either unit (and add generator to do it automatically), but I do not quite see what is it going to buy you. Hello, thanks for your answer and sorry for the previous confusions I made. What do you call generator here ? A custom

Re: [systemd-devel] Permissions problems with systemd-networkd and others.

2024-02-07 Thread Murrell, Robert A.
I finally got everything working. Here is what I did to fix the problem: adduser systemd-network root adduser systemd-resolve root adduser bind root find /etc -type d -exec chmod 755 {} + I don’t know who does this on a full linux image. I’m posting it here for the next person who has this pro

[systemd-devel] ConditionNeedsUpdate, read-only /usr, and sysext

2024-02-07 Thread Valentin David
Hello everybody, The behavior of ConditionNeedsUpdate is that if /etc/.updated is older than /usr/, then it is true. I have some issues with this. But maybe I do not use it the right way. First, when using a read-only /usr partition (updated through sysupdate), the time of /usr is of the build

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Andrei Borzenkov
On 07.02.2024 19:20, Thomas HUMMEL wrote: On 2/7/24 11:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. Well, forget about

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Andrei Borzenkov
On 07.02.2024 13:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit It is generated by systemd-fstab-generator as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. If doc for s

Re: [systemd-devel] Permissions problems with systemd-networkd and others.

2024-02-07 Thread Murrell, Robert A.
I should have added that I am building a very stripped down image. These are the Debian packages that are being installed: linux-image-6.2.0 - locally built firmware-imx-epdc - locally built firmware-imx-sdma - locally built firmware-imx-vpu - locally built firmware-realtek - locally built busyb

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/7/24 11:50, Thomas HUMMEL wrote: Still I cannot understand where the Requires= comes in remote-fs.target unit as doc for special target only describes a Wants= dep added by systemd-fstab-generator in the case of auto mounts. Well, forget about that Wants= dep which is to the mount uni

Re: [systemd-devel] Submitting a service activation to remote mounts success

2024-02-07 Thread Thomas HUMMEL
On 2/6/24 17:06, Silvio Knizek wrote: Hi Thomas, RequiresMountsFor=3D should be your friend. It just takes a space- separated list of paths and does all the other stuff by itself. Hello, thanks for your reply. Actually RequiresMountsFor is not what I need because I'd have to point some fi