On 16.09.2023 07:53, Philip Couling wrote:
I'm trying to understand what a system is timing out waiting for a device
in /etc/fstab when a simple "mount -av" will succeed.
To reach systemd, initramfs has already mounted the device as the base
layer to an overlay mount used as the root file system
.device units wait for *udev* to broadcast the uevent about that device
being added, which happens after udev has 1. received the initial kernel
uevent (either real or produced by systemd-udev-trigger.service) and 2.
finished processing all its .rules for that device (which means everything
that ru
I'm trying to understand what a system is timing out waiting for a device
in /etc/fstab when a simple "mount -av" will succeed.
To reach systemd, initramfs has already mounted the device as the base
layer to an overlay mount used as the root file system, so it's definitely
ready to use in the Linu
Ian Pilcher https://mailto:[email protected]>> wrote:
> Why are you running systemd-networkd at all?
That’s a really good question — the decision wasn’t made by me. I think the
people in charge of updating the device’s Linux distribution were just thinking
along general principles that syst
Will appreciate any pointers about debugging and fixing this!
On Tue, Sep 12, 2023 at 2:55 AM Aleksandar Kostadinov
wrote:
>
> On Mon, Sep 11, 2023 at 2:57 PM Lennart Poettering
> wrote:
> >
> > On Mo, 11.09.23 14:48, Aleksandar Kostadinov ([email protected]) wrote:
> >
> > > Hi again. I tried
