Re: [systemd-devel] Failed to start up manager. Freezing execution.

2023-04-29 Thread Caeri Tech
So my next question is under what circumstances does systemd issue this message? On Tue., Apr. 25, 2023, 9:18 a.m. Caeri Tech, wrote: > Interesting. If I downgrade systemd and systemd-libs from 253 to 252 it > works as before. > > Is there perhaps a dependency that I'm now required to include

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Dan Nicholson
For Endless OS we went the opposite way under the idea that we don't want to have to go add an entry for every service that might get added when the packages change. Basically we work under the assumption that a package included in the OS that provides a service usually should be enabled. So, we

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Daan De Meyer
Disabling manually will still get overridden by preset on first boot. Debian does not ship 99-disable.preset because deb-systemd-helper relies on systemctl preset to enable services on install. Shipping that file would break backwards compat because no services would be enabled anymore. If I were

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Martin Petzold
Dear Daan, Am 29.04.23 um 17:43 schrieb Daan De Meyer: Systemd does a preset on first boot when there's no machine ID yet. If no preset from a preset file applies, the default is to enable it. Since debian does not ship a 99-disable.preset with disable * in it, all services are enabled on

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Daan De Meyer
Systemd does a preset on first boot when there's no machine ID yet. If no preset from a preset file applies, the default is to enable it. Since debian does not ship a 99-disable.preset with disable * in it, all services are enabled on firstboot on Debian. Cheers, Daan On Sat, 29 Apr 2023, 17:27

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Martin Petzold
Dear Paul, Am 29.04.23 um 17:13 schrieb Paul Menzel: Dear Martin, Am 29.04.23 um 16:12 schrieb Martin Petzold: we are building our OS with debootstrap (Debian bullseye). Our image shall be flashed on embedded devices. In order to get a unique machine-id we removed '/etc/machine-id' as

Re: [systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Paul Menzel
Dear Martin, Am 29.04.23 um 16:12 schrieb Martin Petzold: we are building our OS with debootstrap (Debian bullseye). Our image shall be flashed on embedded devices. In order to get a unique machine-id we removed '/etc/machine-id' as instructed in [1] and also removed

[systemd-devel] systemd enables custom service units on firstboot

2023-04-29 Thread Martin Petzold
Hi, we are building our OS with debootstrap (Debian bullseye). Our image shall be flashed on embedded devices. In order to get a unique machine-id we removed '/etc/machine-id' as instructed in [1] and also removed '/var/lib/dbus/machine-id' as instructed in [2]) from the golden image.

Re: [systemd-devel] systemd-resolved not working in a realistic scenario

2023-04-29 Thread Reto
On Thu, Apr 27, 2023 at 02:46:09PM +0200, Farkas Levente wrote: > What I'd like to achieve: > - if the vpn is not connected > - all dns query goes to 8.8.8.8 > - if vpn is connected: > - netbird.cloud goes to 100.76.1.2 > - a.com goes through wt0 to 1.2.3.4 > - b.com goes through wt0 to

Re: [systemd-devel] systemd-resolved not working in a realistic scenario

2023-04-29 Thread Farkas Levente
On 2023. 04. 29. 12:18, Reto wrote: On Thu, Apr 27, 2023 at 02:46:09PM +0200, Farkas Levente wrote: What I'd like to achieve: - if the vpn is not connected - all dns query goes to 8.8.8.8 - if vpn is connected: - netbird.cloud goes to 100.76.1.2 - a.com goes through wt0 to 1.2.3.4 -