And as always: help is more then welcome. If you want to get involved,
please contact us at #debian-systemd on OFTC
Am Mi., 18. Jan. 2023 um 16:57 Uhr schrieb Michael Biebl :
>
> Quite simple:
> stable releases: Debian policy is rather strict regarding stable
> uploads and some of the changes
Quite simple:
stable releases: Debian policy is rather strict regarding stable
uploads and some of the changes that landed in systemd-stable are not
really considered suitable for a stable upload to Debian. That's why
we only cherry-pick select fixes.
If the Debian policy was more lax in that
On 18.01.20233 04:06, Andrei Borzenkov wrote:
> On 17.01.2023 18:28, Thomas Burghout wrote:
> > inet 169.254.146.171/16 brd 169.254.255.255 scope link eth0
>
> Is it output from the correct system? Because address is different. I do
> not see how "ping -I 169.254.1.2" can work with this.
We are building systemd in Yocto:honister systemd_249.7.bb
If we run ”reboot”, the system goes down but stops after printing out
Reached Target System Reboot
Nothing happens after that.
If we run ”poweroff” then the system goes down.
It prints out ”Reached Target System Power Off”
Then it runs
Apologies, was not subscribed previously but would also seek the input
of systemd-devel on the matter below.
Regards, tok
On 18.01.23 10:05, tok wrote:
Hi,
This is not meant as blame but I sincerely would like to understand the
mechanisms/approach and apparent complexities behind it: I was
