networkd: learned DNS server not propagated to rdnss option in RA

Dear all, I'm trying to setup an embedded system as IPv6 router using IPv6 prefix delegation. The system has two network interfaces, eth0 and eth1. eth0 is the upstream interface, but it is part of a bridge interface, but I think this does not play an important role here. The upstream interfaces

Re: [systemd-devel] Manual start of user@.service failed with permission denied

On Tue, Dec 12, 2023 at 6:15 PM Christopher Wong wrote: > Hi Mantas, > > > > After user@1001.service failed, it trigger the stopping process and > become inactive. > Ah yeah, that makes sense, user-runtime-dir@ has StopWhenUnneeded=yes – so of course after user@1001 crashes you're not going to

RE: networkd RetransmitSec - how to make it work on a host?

> -Original Message- > From: Lennart Poettering > Sent: Wednesday, December 13, 2023 7:32 AM > To: Muggeridge, Matt > Cc: systemd-devel@lists.freedesktop.org > Subject: Re: networkd RetransmitSec - how to make it work on a host? > > On Mo, 11.12.23 02:49, Muggeridge, Matt

RE: IPv6 Compliance for networkd

> -Original Message- > From: Lennart Poettering > Sent: Wednesday, December 13, 2023 4:22 AM > To: Muggeridge, Matt > Cc: systemd-devel@lists.freedesktop.org > Subject: Re: IPv6 Compliance for networkd > > On Mo, 11.12.23 19:14, Muggeridge, Matt (matt.muggerid...@hpe.com) > wrote: > >

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Tue, Dec 12, 2023 at 10:02 PM Lennart Poettering wrote: > > If you have 7 cpio initrds then the kernel will allocate a tmpfs and > unpack them all into it, one after the other, on top of each other, > and then jumps into the result. > > if you have an erofs and 7 cpio initds, what are you

Re: networkd RetransmitSec - how to make it work on a host?

On Mo, 11.12.23 02:49, Muggeridge, Matt (matt.muggerid...@hpe.com) wrote: > The RetransmitSec option was introduced in systemd-v255, but I > cannot get it to work for Neighbor Solicitations from a > Host. Instead, I observe that the NS are always transmitted at 1 > second intervals, regardless of

Re: systemd units disabled when calling systemctl daemon-reload

On Di, 12.12.23 19:06, Etienne Cordonnier (ecordonn...@snap.com) wrote: > Hello, > I am debugging some embedded system running systemd. The behavior I am > observing is that many systemd targets such as multi-user.target are > disabled after I run systemctl daemon-reload (as shown by systemctl >

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Di, 12.12.23 21:34, Nils Kattenbeck (nilskem...@gmail.com) wrote: > Hi, while I have been following this thread passively for now I also > wanted to chime in. > > > (The main reason why sd-stub doesn't actually support erofs-initrds, > > is that sd-stub also generates initrd cpios on the fly,

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Tue, 12 Dec 2023 at 20:35, Nils Kattenbeck wrote: > > Hi, while I have been following this thread passively for now I also > wanted to chime in. > > > (The main reason why sd-stub doesn't actually support erofs-initrds, > > is that sd-stub also generates initrd cpios on the fly, to pass > >

Re: [RFC] initoverlayfs - a scalable initial filesystem

Hi, while I have been following this thread passively for now I also wanted to chime in. > (The main reason why sd-stub doesn't actually support erofs-initrds, > is that sd-stub also generates initrd cpios on the fly, to pass > credentials and system extension images to the kernel, and you can't

Re: systemd units disabled when calling systemctl daemon-reload

On Tue, Dec 12, 2023 at 07:06:22PM +0100, Etienne Cordonnier wrote: > Hello, > I am debugging some embedded system running systemd. The behavior I am > observing is that many systemd targets such as multi-user.target are > disabled after I run systemctl daemon-reload (as shown by systemctl >

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Tue, Dec 12, 2023 at 06:40:32PM +0100, Lennart Poettering wrote: > On Mo, 11.12.23 12:48, Eric Curtin (ecur...@redhat.com) wrote: > > > Although the nice thing about a storage-init like approach is there's > > basically zero copies up front. What storage-init is trying to be, is > > a tool to

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Tue, 12 Dec 2023 at 12:38, Lennart Poettering wrote: > On Mo, 11.12.23 12:48, Eric Curtin (ecur...@redhat.com) wrote: > > > Sort of yes, but preferably using that __initramfs_start / > > initrd_start buffer as is without copying any bytes anywhere else and > > without teaching the bootloaders

Re: IPv6 Compliance for networkd

On Mo, 11.12.23 19:14, Muggeridge, Matt (matt.muggerid...@hpe.com) wrote: > Hello, networkd developer community, > > I am hoping to rally support for making networkd IPv6 compliant and > I'm will to help, but cannot do it alone. Is there any interest in > making systemd-networkd IPv6 compliant?

Re: systemd units disabled when calling systemctl daemon-reload

More specifically, basic.target, local-fs.target and multi-user.target are disabled after I run systemctl daemon-reload. On Tue, Dec 12, 2023 at 7:06 PM Etienne Cordonnier wrote: > Hello, > I am debugging some embedded system running systemd. The behavior I am > observing is that many systemd

systemd units disabled when calling systemctl daemon-reload

Hello, I am debugging some embedded system running systemd. The behavior I am observing is that many systemd targets such as multi-user.target are disabled after I run systemctl daemon-reload (as shown by systemctl list-units --type target --all). This causes many systemd units to be disabled, and

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Mo, 11.12.23 17:03, Eric Curtin (ecur...@redhat.com) wrote: > A generic approach is hard, I think it's worth discussing which type of boots > you should actually care about milliseconds of performance for. It would be > nice > if we had an init system that contained the binary data to do the

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Mo, 11.12.23 11:28, Demi Marie Obenour (d...@invisiblethingslab.com) wrote: > I don't think this is "a pretty specific solution to one set of devices" > _at all_. To the contrary, it is _exactly_ what I want to see desktop > systems moving to in the future. > > It solves the problem of large

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Mo, 11.12.23 12:48, Eric Curtin (ecur...@redhat.com) wrote: > Although the nice thing about a storage-init like approach is there's > basically zero copies up front. What storage-init is trying to be, is > a tool to just call systemd storage things, without also inheriting > all the systemd

Re: [RFC] initoverlayfs - a scalable initial filesystem

On Mo, 11.12.23 12:48, Eric Curtin (ecur...@redhat.com) wrote: > Sort of yes, but preferably using that __initramfs_start / > initrd_start buffer as is without copying any bytes anywhere else and > without teaching the bootloaders to do things. > > The "memmap=" approach you suggested sounds like

Re: IPv6 Compliance for networkd

On Tue, 12 Dec 2023 03:51:37 + "Muggeridge, Matt" wrote: > > > > If you need these problems fixed so that you can use systemd-networkd in > > your commercial products, I recommend getting your company to pay > > developers to fix systemd-networkd. > > -- > > Sincerely, > > Demi Marie

Re: [systemd-devel] Manual start of user@.service failed with permission denied

Hi Mantas, After user@1001.service failed, it trigger the stopping process and become inactive. ○ user-runtime-dir@1001.service - User Runtime Directory /run/user/1001 Loaded: loaded

Re: [systemd-devel] Manual start of user@.service failed with permission denied

That sounds like it's getting immediately unmounted (or maybe not being mounted at all despite the program doing so). Does the user-runtime-dir service continue to show as "active" after this, or does it return to "inactive"? Does your /etc/fstab have any mentions of /run/user/1001? Or more

Re: [systemd-devel] Manual start of user@.service failed with permission denied

Hi Andrei, The systemd logs tells me that /run/user/1001 is mounted as uid=1001, but when I list the path /run/user/1001 it is empty and is owned by root. I can’t find the path when I run the “mount” command. However, even for the successful case the path is not listed with the “mount”

Re: [systemd-devel] Manual start of user@.service failed with permission denied

Hi Belanger, Thank you for your suggestion! I tried putting RuntimeDirectory= into the user@.service. I suppose I shouldn’t need to do this since the runtime directory should be fixed by the service user-runtime-dir@.service. Result is

Re: [systemd-devel] Manual start of user@.service failed with permission denied

Hi Mantas, I currently have the following flow: 1. No /run/user/1001 directory 2. systemctl start user@1001.service 3. systemd start user-runtime-dir@1001.service which ends successfully. 4. The directory

Re: [RFC] initoverlayfs - a scalable initial filesystem

[Sorry for the spam to the people in Cc. Now the real address.] Dear Luca, Am 11.12.23 um 22:45 schrieb Luca Boccassi: > On Mon, 11 Dec 2023 at 21:20, Demi Marie Obenour wrote: >> >> On Mon, Dec 11, 2023 at 08:58:58PM +, Luca Boccassi wrote: >>> On Mon, 11 Dec 2023 at 20:43, Demi Marie